1 Changes in version 0.2.7.5 - 2015-11-20
2 The Tor 0.2.7 release series is dedicated to the memory of Tor user
3 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
4 tirelessly to advocate human rights regardless of national borders,
5 and oppose the encroachments of mass surveillance. He opposed national
6 exceptionalism, he brought clarity to legal and policy debates, he
7 understood and predicted the impact of mass surveillance on the world,
8 and he laid the groundwork for resisting it. While serving on the Tor
9 Project's board of directors, he brought us his uncompromising focus
10 on technical excellence in the service of humankind. Caspar was an
11 inimitable force for good and a wonderful friend. He was kind,
12 humorous, generous, gallant, and believed we should protect one
13 another without exception. We honor him here for his ideals, his
14 efforts, and his accomplishments. Please honor his memory with works
15 that would make him proud.
17 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
19 The 0.2.7 series adds a more secure identity key type for relays,
20 improves cryptography performance, resolves several longstanding
21 hidden-service performance issues, improves controller support for
22 hidden services, and includes small bugfixes and performance
23 improvements throughout the program. This release series also includes
24 more tests than before, and significant simplifications to which parts
25 of Tor invoke which others.
27 (This release contains no code changes since 0.2.7.4-rc.)
30 Changes in version 0.2.7.4-rc - 2015-10-21
31 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
32 fixes some important memory leaks, and a scary-looking (but mostly
33 harmless in practice) invalid-read bug. It also has a few small
34 bugfixes, notably fixes for compilation and portability on different
35 platforms. If no further significant bounds are found, the next
36 release will the the official stable release.
38 o Major bugfixes (security, correctness):
39 - Fix an error that could cause us to read 4 bytes before the
40 beginning of an openssl string. This bug could be used to cause
41 Tor to crash on systems with unusual malloc implementations, or
42 systems with unusual hardening installed. Fixes bug 17404; bugfix
45 o Major bugfixes (correctness):
46 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
47 bug 17401; bugfix on 0.2.7.3-rc.
49 o Major bugfixes (memory leaks):
50 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
51 17398; bugfix on 0.2.6.1-alpha.
52 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
53 17402; bugfix on 0.2.7.3-rc.
54 - Fix a memory leak when reading an expired signing key from disk.
55 Fixes bug 17403; bugfix on 0.2.7.2-rc.
57 o Minor features (geoIP):
58 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
61 o Minor bugfixes (compilation):
62 - Repair compilation with the most recent (unreleased, alpha)
63 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
64 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
65 17251; bugfix on 0.2.7.2-alpha.
66 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
67 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
69 o Minor bugfixes (portability):
70 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
71 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
73 o Minor bugfixes (sandbox):
74 - Add the "hidserv-stats" filename to our sandbox filter for the
75 HiddenServiceStatistics option to work properly. Fixes bug 17354;
76 bugfix on tor-0.2.6.2-alpha. Patch from David Goulet.
78 o Minor bugfixes (testing):
79 - Add unit tests for get_interface_address* failure cases. Fixes bug
80 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
81 - Fix breakage when running 'make check' with BSD make. Fixes bug
82 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
83 - Make the get_ifaddrs_* unit tests more tolerant of different
84 network configurations. (Don't assume every test box has an IPv4
85 address, and don't assume every test box has a non-localhost
86 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
87 - Skip backtrace tests when backtrace support is not compiled in.
88 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
92 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
93 - Note that HiddenServicePorts can take a unix domain socket. Closes
97 Changes in version 0.2.7.3-rc - 2015-09-25
98 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
99 contains numerous usability fixes for Ed25519 keys, safeguards against
100 several misconfiguration problems, significant simplifications to
101 Tor's callgraph, and numerous bugfixes and small features.
103 This is the most tested release of Tor to date. The unit tests cover
104 39.40% of the code, and the integration tests (accessible with "make
105 test-full-online", requiring stem and chutney and a network
106 connection) raise the coverage to 64.49%.
108 o Major features (security, hidden services):
109 - Hidden services, if using the EntryNodes option, are required to
110 use more than one EntryNode, in order to avoid a guard discovery
111 attack. (This would only affect people who had configured hidden
112 services and manually specified the EntryNodes option with a
113 single entry-node. The impact was that it would be easy to
114 remotely identify the guard node used by such a hidden service.
115 See ticket for more information.) Fixes ticket 14917.
117 o Major features (Ed25519 keys, keypinning):
118 - The key-pinning option on directory authorities is now advisory-
119 only by default. In a future version, or when the AuthDirPinKeys
120 option is set, pins are enforced again. Disabling key-pinning
121 seemed like a good idea so that we can survive the fallout of any
122 usability problems associated with Ed25519 keys. Closes
125 o Major features (Ed25519 performance):
126 - Improve the speed of Ed25519 operations and Curve25519 keypair
127 generation when built targeting 32 bit x86 platforms with SSE2
128 available. Implements ticket 16535.
129 - Improve the runtime speed of Ed25519 signature verification by
130 using Ed25519-donna's batch verification support. Implements
133 o Major features (performance testing):
134 - The test-network.sh script now supports performance testing.
135 Requires corresponding chutney performance testing changes. Patch
136 by "teor". Closes ticket 14175.
138 o Major features (relay, Ed25519):
139 - Significant usability improvements for Ed25519 key management. Log
140 messages are better, and the code can recover from far more
141 failure conditions. Thanks to "s7r" for reporting and diagnosing
143 - Add a new OfflineMasterKey option to tell Tor never to try loading
144 or generating a secret Ed25519 identity key. You can use this in
145 combination with tor --keygen to manage offline and/or encrypted
146 Ed25519 keys. Implements ticket 16944.
147 - Add a --newpass option to allow changing or removing the
148 passphrase of an encrypted key with tor --keygen. Implements part
150 - On receiving a HUP signal, check to see whether the Ed25519
151 signing key has changed, and reload it if so. Closes ticket 16790.
153 o Major bugfixes (relay, Ed25519):
154 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
155 0.2.7.2-alpha. Reported by "s7r".
156 - Improve handling of expired signing keys with offline master keys.
157 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
159 o Minor features (client-side privacy):
160 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
161 lifespan when IsolateSOCKSAuth and streams with SOCKS
162 authentication are attached to the circuit. This allows
163 applications like TorBrowser to manage circuit lifetime on their
164 own. Implements feature 15482.
165 - When logging malformed hostnames from SOCKS5 requests, respect
166 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
168 o Minor features (compilation):
169 - Give a warning as early as possible when trying to build with an
170 unsupported OpenSSL version. Closes ticket 16901.
171 - Fail during configure if we're trying to build against an OpenSSL
172 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
173 which started requiring ECC.
175 o Minor features (geoip):
176 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
179 o Minor features (hidden services):
180 - Relays need to have the Fast flag to get the HSDir flag. As this
181 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
182 drop. This change should make some attacks against the hidden
183 service directory system harder. Fixes ticket 15963.
184 - Turn on hidden service statistics collection by setting the torrc
185 option HiddenServiceStatistics to "1" by default. (This keeps
186 track only of the fraction of traffic used by hidden services, and
187 the total number of hidden services in existence.) Closes
189 - Client now uses an introduction point failure cache to know when
190 to fetch or keep a descriptor in their cache. Previously, failures
191 were recorded implicitly, but not explicitly remembered. Closes
194 o Minor features (testing, authorities, documentation):
195 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
196 explicitly manage consensus flags in testing networks. Patch by
197 "robgjansen", modified by "teor". Implements part of ticket 14882.
199 o Minor bugfixes (security, exit policies):
200 - ExitPolicyRejectPrivate now also rejects the relay's published
201 IPv6 address (if any), and any publicly routable IPv4 or IPv6
202 addresses on any local interfaces. ticket 17027. Patch by "teor".
203 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
205 o Minor bug fixes (torrc exit policies):
206 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
207 produce IPv6 wildcard addresses. Previously they would produce
208 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
209 of bug 16069; bugfix on 0.2.4.7-alpha.
210 - When parsing torrc ExitPolicies, we now warn for a number of cases
211 where the user's intent is likely to differ from Tor's actual
212 behavior. These include: using an IPv4 address with an accept6 or
213 reject6 line; using "private" on an accept6 or reject6 line; and
214 including any ExitPolicy lines after accept *:* or reject *:*.
215 Related to ticket 16069.
216 - When parsing torrc ExitPolicies, we now issue an info-level
217 message when expanding an "accept/reject *" line to include both
218 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
219 - In each instance above, usage advice is provided to avoid the
220 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
221 16069; bugfix on 0.2.4.7-alpha.
223 o Minor bugfixes (authority):
224 - Don't assign "HSDir" to a router if it isn't Valid and Running.
225 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
226 - Downgrade log messages about Ed25519 key issues if they are in old
227 cached router descriptors. Fixes part of bug 16286; bugfix
229 - When we find an Ed25519 key issue in a cached descriptor, stop
230 saying the descriptor was just "uploaded". Fixes another part of
231 bug 16286; bugfix on 0.2.7.2-alpha.
233 o Minor bugfixes (control port):
234 - Repair a warning and a spurious result when getting the maximum
235 number of file descriptors from the controller. Fixes bug 16697;
236 bugfix on 0.2.7.2-alpha.
238 o Minor bugfixes (correctness):
239 - When calling channel_free_list(), avoid calling smartlist_remove()
240 while inside a FOREACH loop. This partially reverts commit
241 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
242 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
244 o Minor bugfixes (documentation):
245 - Advise users on how to configure separate IPv4 and IPv6 exit
246 policies in the manpage and sample torrcs. Related to ticket 16069.
247 - Fix the usage message of tor-resolve(1) so that it no longer lists
248 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
249 - Fix an error in the manual page and comments for
250 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
251 required "ORPort connectivity". While this is true, it is in no
252 way unique to the HSDir flag. Of all the flags, only HSDirs need a
253 DirPort configured in order for the authorities to assign that
254 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
257 o Minor bugfixes (Ed25519):
258 - Fix a memory leak when reading router descriptors with expired
259 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
261 o Minor bugfixes (linux seccomp2 sandbox):
262 - Allow bridge authorities to run correctly under the seccomp2
263 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
264 - Allow routers with ed25519 keys to run correctly under the
265 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
267 o Minor bugfixes (open file limit):
268 - Fix set_max_file_descriptors() to set by default the max open file
269 limit to the current limit when setrlimit() fails. Fixes bug
270 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
272 o Minor bugfixes (portability):
273 - Try harder to normalize the exit status of the Tor process to the
274 standard-provided range. Fixes bug 16975; bugfix on every version
276 - Check correctly for Windows socket errors in the workqueue
277 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
278 - Fix the behavior of crypto_rand_time_range() when told to consider
279 times before 1970. (These times were possible when running in a
280 simulated network environment where time()'s output starts at
281 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
282 - Restore correct operation of TLS client-cipher detection on
283 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
285 o Minor bugfixes (relay):
286 - Ensure that worker threads actually exit when a fatal error or
287 shutdown is indicated. This fix doesn't currently affect the
288 behavior of Tor, because Tor workers never indicates fatal error
289 or shutdown except in the unit tests. Fixes bug 16868; bugfix
291 - Unblock threads before releasing the work queue mutex to ensure
292 predictable scheduling behavior. Fixes bug 16644; bugfix
295 o Code simplification and refactoring:
296 - Change the function that's called when we need to retry all
297 downloads so that it only reschedules the downloads to happen
298 immediately, rather than launching them all at once itself. This
299 further simplifies Tor's callgraph.
300 - Move some format-parsing functions out of crypto.c and
301 crypto_curve25519.c into crypto_format.c and/or util_format.c.
302 - Move the client-only parts of init_keys() into a separate
303 function. Closes ticket 16763.
304 - Simplify the microdesc_free() implementation so that it no longer
305 appears (to code analysis tools) to potentially invoke a huge
306 suite of other microdesc functions.
307 - Simply the control graph further by deferring the inner body of
308 directory_all_unreachable() into a callback. Closes ticket 16762.
309 - Treat the loss of an owning controller as equivalent to a SIGTERM
310 signal. This removes a tiny amount of duplicated code, and
311 simplifies our callgraph. Closes ticket 16788.
312 - When generating an event to send to the controller, we no longer
313 put the event over the network immediately. Instead, we queue
314 these events, and use a Libevent callback to deliver them. This
315 change simplifies Tor's callgraph by reducing the number of
316 functions from which all other Tor functions are reachable. Closes
318 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
319 that try to scan or compile every file on Unix won't decide that
321 - Remove the unused "nulterminate" argument from buf_pullup().
324 - Recommend a 40 GB example AccountingMax in torrc.sample rather
325 than a 4 GB max. Closes ticket 16742.
326 - Include the TUNING document in our source tarball. It is referred
327 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
331 - The internal pure-C tor-fw-helper tool is now removed from the Tor
332 distribution, in favor of the pure-Go clone available from
333 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
334 used by the C tor-fw-helper are not, in our opinion, very
335 confidence- inspiring in their secure-programming techniques.
337 - Remove the code that would try to aggressively flush controller
338 connections while writing to them. This code was introduced in
339 0.1.2.7-alpha, in order to keep output buffers from exceeding
340 their limits. But there is no longer a maximum output buffer size,
341 and flushing data in this way caused some undesirable recursions
342 in our call graph. Closes ticket 16480.
345 - Make "bridges+hs" the default test network. This tests almost all
346 tor functionality during make test-network, while allowing tests
347 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
348 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
349 (chutney). Patches by "teor".
350 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
351 by-side in the same parent directory. Closes ticket 16903. Patch
353 - Use environment variables rather than autoconf substitutions to
354 send variables from the build system to the test scripts. This
355 change should be easier to maintain, and cause 'make distcheck' to
356 work better than before. Fixes bug 17148.
357 - Add a new set of callgraph analysis scripts that use clang to
358 produce a list of which Tor functions are reachable from which
359 other Tor functions. We're planning to use these to help simplify
360 our code structure by identifying illogical dependencies.
361 - Add new 'test-full' and 'test-full-online' targets to run all
362 tests, including integration tests with stem and chutney.
363 - Make the test-workqueue test work on Windows by initializing the
364 network before we begin.
365 - New make target (make test-network-all) to run multiple applicable
366 chutney test cases. Patch from Teor; closes 16953.
367 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
368 functions in dns.c. Implements a portion of ticket 16831.
369 - When building Tor with testing coverage enabled, run Chutney tests
370 (if any) using the 'tor-cov' coverage binary.
371 - When running test-network or test-stem, check for the absence of
372 stem/chutney before doing any build operations.
375 Changes in version 0.2.7.2-alpha - 2015-07-27
376 This, the second alpha in the Tor 0.2.7 series, has a number of new
377 features, including a way to manually pick the number of introduction
378 points for hidden services, and the much stronger Ed25519 signing key
379 algorithm for regular Tor relays (including support for encrypted
380 offline identity keys in the new algorithm).
382 Support for Ed25519 on relays is currently limited to signing router
383 descriptors; later alphas in this series will extend Ed25519 key
384 support to more parts of the Tor protocol.
386 o Major features (Ed25519 identity keys, Proposal 220):
387 - All relays now maintain a stronger identity key, using the Ed25519
388 elliptic curve signature format. This master key is designed so
389 that it can be kept offline. Relays also generate an online
390 signing key, and a set of other Ed25519 keys and certificates.
391 These are all automatically regenerated and rotated as needed.
392 Implements part of ticket 12498.
393 - Directory authorities now vote on Ed25519 identity keys along with
394 RSA1024 keys. Implements part of ticket 12498.
395 - Directory authorities track which Ed25519 identity keys have been
396 used with which RSA1024 identity keys, and do not allow them to
397 vary freely. Implements part of ticket 12498.
398 - Microdescriptors now include Ed25519 identity keys. Implements
399 part of ticket 12498.
400 - Add support for offline encrypted Ed25519 master keys. To use this
401 feature on your tor relay, run "tor --keygen" to make a new master
402 key (or to make a new signing key if you already have a master
403 key). Closes ticket 13642.
405 o Major features (Hidden services):
406 - Add the torrc option HiddenServiceNumIntroductionPoints, to
407 specify a fixed number of introduction points. Its maximum value
408 is 10 and default is 3. Using this option can increase a hidden
409 service's reliability under load, at the cost of making it more
410 visible that the hidden service is facing extra load. Closes
412 - Remove the adaptive algorithm for choosing the number of
413 introduction points, which used to change the number of
414 introduction points (poorly) depending on the number of
415 connections the HS sees. Closes ticket 4862.
417 o Major features (onion key cross-certification):
418 - Relay descriptors now include signatures of their own identity
419 keys, made using the TAP and ntor onion keys. These signatures
420 allow relays to prove ownership of their own onion keys. Because
421 of this change, microdescriptors will no longer need to include
422 RSA identity keys. Implements proposal 228; closes ticket 12499.
424 o Major features (performance):
425 - Improve the runtime speed of Ed25519 operations by using the
426 public-domain Ed25519-donna by Andrew M. ("floodyberry").
427 Implements ticket 16467.
428 - Improve the runtime speed of the ntor handshake by using an
429 optimized curve25519 basepoint scalarmult implementation from the
430 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
431 ideas by Adam Langley. Implements ticket 9663.
433 o Major bugfixes (client-side privacy, also in 0.2.6.9):
434 - Properly separate out each SOCKSPort when applying stream
435 isolation. The error occurred because each port's session group
436 was being overwritten by a default value when the listener
437 connection was initialized. Fixes bug 16247; bugfix on
438 0.2.6.3-alpha. Patch by "jojelino".
440 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
441 - Stop refusing to store updated hidden service descriptors on a
442 client. This reverts commit 9407040c59218 (which indeed fixed bug
443 14219, but introduced a major hidden service reachability
444 regression detailed in bug 16381). This is a temporary fix since
445 we can live with the minor issue in bug 14219 (it just results in
446 some load on the network) but the regression of 16381 is too much
447 of a setback. First-round fix for bug 16381; bugfix
450 o Major bugfixes (hidden services):
451 - When cannibalizing a circuit for an introduction point, always
452 extend to the chosen exit node (creating a 4 hop circuit).
453 Previously Tor would use the current circuit exit node, which
454 changed the original choice of introduction point, and could cause
455 the hidden service to skip excluded introduction points or
456 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
459 o Major bugfixes (open file limit):
460 - The open file limit wasn't checked before calling
461 tor_accept_socket_nonblocking(), which would make Tor exceed the
462 limit. Now, before opening a new socket, Tor validates the open
463 file limit just before, and if the max has been reached, return an
464 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
466 o Major bugfixes (stability, also in 0.2.6.10):
467 - Stop crashing with an assertion failure when parsing certain kinds
468 of malformed or truncated microdescriptors. Fixes bug 16400;
469 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
470 by "cypherpunks_backup".
471 - Stop random client-side assertion failures that could occur when
472 connecting to a busy hidden service, or connecting to a hidden
473 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
476 o Minor features (directory authorities, security, also in 0.2.6.9):
477 - The HSDir flag given by authorities now requires the Stable flag.
478 For the current network, this results in going from 2887 to 2806
479 HSDirs. Also, it makes it harder for an attacker to launch a sybil
480 attack by raising the effort for a relay to become Stable to
481 require at the very least 7 days, while maintaining the 96 hours
482 uptime requirement for HSDir. Implements ticket 8243.
484 o Minor features (client):
485 - Relax the validation of hostnames in SOCKS5 requests, allowing the
486 character '_' to appear, in order to cope with domains observed in
487 the wild that are serving non-RFC compliant records. Resolves
489 - Relax the validation done to hostnames in SOCKS5 requests, and
490 allow a single trailing '.' to cope with clients that pass FQDNs
491 using that syntax to explicitly indicate that the domain name is
492 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
493 - Add GroupWritable and WorldWritable options to unix-socket based
494 SocksPort and ControlPort options. These options apply to a single
495 socket, and override {Control,Socks}SocketsGroupWritable. Closes
498 o Minor features (control protocol):
499 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
500 the control protocol. Resolves ticket 15358.
502 o Minor features (directory authorities):
503 - Directory authorities no longer vote against the "Fast", "Stable",
504 and "HSDir" flags just because they were going to vote against
505 "Running": if the consensus turns out to be that the router was
506 running, then the authority's vote should count. Patch from Peter
507 Retzlaff; closes issue 8712.
509 o Minor features (geoip, also in 0.2.6.10):
510 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
511 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
513 o Minor features (hidden services):
514 - Add the new options "HiddenServiceMaxStreams" and
515 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
516 limit the maximum number of simultaneous streams per circuit, and
517 optionally tear down the circuit when the limit is exceeded. Part
520 o Minor features (portability):
521 - Use C99 variadic macros when the compiler is not GCC. This avoids
522 failing compilations on MSVC, and fixes a log-file-based race
523 condition in our old workarounds. Original patch from Gisle Vanem.
525 o Minor bugfixes (compilation, also in 0.2.6.9):
526 - Build with --enable-systemd correctly when libsystemd is
527 installed, but systemd is not. Fixes bug 16164; bugfix on
528 0.2.6.3-alpha. Patch from Peter Palfrader.
530 o Minor bugfixes (controller):
531 - Add the descriptor ID in each HS_DESC control event. It was
532 missing, but specified in control-spec.txt. Fixes bug 15881;
533 bugfix on 0.2.5.2-alpha.
535 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
536 - Check for failures from crypto_early_init, and refuse to continue.
537 A previous typo meant that we could keep going with an
538 uninitialized crypto library, and would have OpenSSL initialize
539 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
540 when implementing ticket 4900. Patch by "teor".
542 o Minor bugfixes (hidden services):
543 - Fix a crash when reloading configuration while at least one
544 configured and one ephemeral hidden service exists. Fixes bug
545 16060; bugfix on 0.2.7.1-alpha.
546 - Avoid crashing with a double-free bug when we create an ephemeral
547 hidden service but adding it fails for some reason. Fixes bug
548 16228; bugfix on 0.2.7.1-alpha.
550 o Minor bugfixes (Linux seccomp2 sandbox):
551 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
552 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
554 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
555 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
556 these when eventfd2() support is missing. Fixes bug 16363; bugfix
557 on 0.2.6.3-alpha. Patch from "teor".
559 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
560 - Fix sandboxing to work when running as a relay, by allowing the
561 renaming of secret_id_key, and allowing the eventfd2 and futex
562 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
564 - Allow systemd connections to work with the Linux seccomp2 sandbox
565 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
568 o Minor bugfixes (relay):
569 - Fix a rarely-encountered memory leak when failing to initialize
570 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
573 o Minor bugfixes (systemd):
574 - Fix an accidental formatting error that broke the systemd
575 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
576 - Tor's systemd unit file no longer contains extraneous spaces.
577 These spaces would sometimes confuse tools like deb-systemd-
578 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
580 o Minor bugfixes (tests):
581 - Use the configured Python executable when running test-stem-full.
582 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
584 o Minor bugfixes (tests, also in 0.2.6.9):
585 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
586 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
588 o Minor bugfixes (threads, comments):
589 - Always initialize return value in compute_desc_id in rendcommon.c
590 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
591 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
592 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
593 - Remove undefined directive-in-macro in test_util_writepid clang
594 3.7 complains that using a preprocessor directive inside a macro
595 invocation in test_util_writepid in test_util.c is undefined.
596 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
598 o Code simplification and refactoring:
599 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
600 to ensure they remain consistent and visible everywhere.
601 - Remove some vestigial workarounds for the MSVC6 compiler. We
602 haven't supported that in ages.
603 - The link authentication code has been refactored for better
604 testability and reliability. It now uses code generated with the
605 "trunnel" binary encoding generator, to reduce the risk of bugs
606 due to programmer error. Done as part of ticket 12498.
609 - Include a specific and (hopefully) accurate documentation of the
610 torrc file's meta-format in doc/torrc_format.txt. This is mainly
611 of interest to people writing programs to parse or generate torrc
612 files. This document is not a commitment to long-term
613 compatibility; some aspects of the current format are a bit
614 ridiculous. Closes ticket 2325.
617 - Tor no longer supports copies of OpenSSL that are missing support
618 for Elliptic Curve Cryptography. (We began using ECC when
619 available in 0.2.4.8-alpha, for more safe and efficient key
620 negotiation.) In particular, support for at least one of P256 or
621 P224 is now required, with manual configuration needed if only
622 P224 is available. Resolves ticket 16140.
623 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
624 on an operating system that has not upgraded to OpenSSL 1.0 or
625 later, and you compile Tor from source, you will need to install a
626 more recent OpenSSL to link Tor against.) These versions of
627 OpenSSL are still supported by the OpenSSL, but the numerous
628 cryptographic improvements in later OpenSSL releases makes them a
629 clear choice. Resolves ticket 16034.
630 - Remove the HidServDirectoryV2 option. Now all relays offer to
631 store hidden service descriptors. Related to 16543.
632 - Remove the VoteOnHidServDirectoriesV2 option, since all
633 authorities have long set it to 1. Closes ticket 16543.
636 - Document use of coverity, clang static analyzer, and clang dynamic
637 undefined behavior and address sanitizers in doc/HACKING. Include
638 detailed usage instructions in the blacklist. Patch by "teor".
640 - The link authentication protocol code now has extensive tests.
641 - The relay descriptor signature testing code now has
643 - The test_workqueue program now runs faster, and is enabled by
644 default as a part of "make check".
645 - Now that OpenSSL has its own scrypt implementation, add an unit
646 test that checks for interoperability between libscrypt_scrypt()
647 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
648 and rely on EVP_PBE_scrypt() whenever possible. Resolves
652 Changes in version 0.2.6.10 - 2015-07-12
653 Tor version 0.2.6.10 fixes some significant stability and hidden
654 service client bugs, bulletproofs the cryptography init process, and
655 fixes a bug when using the sandbox code with some older versions of
656 Linux. Everyone running an older version, especially an older version
657 of 0.2.6, should upgrade.
659 o Major bugfixes (hidden service clients, stability):
660 - Stop refusing to store updated hidden service descriptors on a
661 client. This reverts commit 9407040c59218 (which indeed fixed bug
662 14219, but introduced a major hidden service reachability
663 regression detailed in bug 16381). This is a temporary fix since
664 we can live with the minor issue in bug 14219 (it just results in
665 some load on the network) but the regression of 16381 is too much
666 of a setback. First-round fix for bug 16381; bugfix
669 o Major bugfixes (stability):
670 - Stop crashing with an assertion failure when parsing certain kinds
671 of malformed or truncated microdescriptors. Fixes bug 16400;
672 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
673 by "cypherpunks_backup".
674 - Stop random client-side assertion failures that could occur when
675 connecting to a busy hidden service, or connecting to a hidden
676 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
679 o Minor features (geoip):
680 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
681 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
683 o Minor bugfixes (crypto error-handling):
684 - Check for failures from crypto_early_init, and refuse to continue.
685 A previous typo meant that we could keep going with an
686 uninitialized crypto library, and would have OpenSSL initialize
687 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
688 when implementing ticket 4900. Patch by "teor".
690 o Minor bugfixes (Linux seccomp2 sandbox):
691 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
692 these when eventfd2() support is missing. Fixes bug 16363; bugfix
693 on 0.2.6.3-alpha. Patch from "teor".
696 Changes in version 0.2.6.9 - 2015-06-11
697 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
698 requirements for receiving an HSDir flag, and addresses some other small
699 bugs in the systemd and sandbox code. Clients using circuit isolation
700 should upgrade; all directory authorities should upgrade.
702 o Major bugfixes (client-side privacy):
703 - Properly separate out each SOCKSPort when applying stream
704 isolation. The error occurred because each port's session group was
705 being overwritten by a default value when the listener connection
706 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
709 o Minor feature (directory authorities, security):
710 - The HSDir flag given by authorities now requires the Stable flag.
711 For the current network, this results in going from 2887 to 2806
712 HSDirs. Also, it makes it harder for an attacker to launch a sybil
713 attack by raising the effort for a relay to become Stable which
714 takes at the very least 7 days to do so and by keeping the 96
715 hours uptime requirement for HSDir. Implements ticket 8243.
717 o Minor bugfixes (compilation):
718 - Build with --enable-systemd correctly when libsystemd is
719 installed, but systemd is not. Fixes bug 16164; bugfix on
720 0.2.6.3-alpha. Patch from Peter Palfrader.
722 o Minor bugfixes (Linux seccomp2 sandbox):
723 - Fix sandboxing to work when running as a relaymby renaming of
724 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
725 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
726 - Allow systemd connections to work with the Linux seccomp2 sandbox
727 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
730 o Minor bugfixes (tests):
731 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
732 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
735 Changes in version 0.2.6.8 - 2015-05-21
736 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
737 fixes an authority-side bug in assigning the HSDir flag. All directory
738 authorities should upgrade.
740 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
741 - Revert commit that made directory authorities assign the HSDir
742 flag to relay without a DirPort; this was bad because such relays
743 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
744 on tor-0.2.6.3-alpha.
746 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
747 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
748 a client authorized hidden service. Fixes bug 15823; bugfix
751 o Minor features (geoip):
752 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
753 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
757 Changes in version 0.2.7.1-alpha - 2015-05-12
758 Tor 0.2.7.1-alpha is the first alpha release in its series. It
759 includes numerous small features and bugfixes against previous Tor
760 versions, and numerous small infrastructure improvements. The most
761 notable features are several new ways for controllers to interact with
762 the hidden services subsystem.
764 o New system requirements:
765 - Tor no longer includes workarounds to support Libevent versions
766 before 1.3e. Libevent 2.0 or later is recommended. Closes
769 o Major features (controller):
770 - Add the ADD_ONION and DEL_ONION commands that allow the creation
771 and management of hidden services via the controller. Closes
773 - New "GETINFO onions/current" and "GETINFO onions/detached"
774 commands to get information about hidden services created via the
775 controller. Part of ticket 6411.
776 - New HSFETCH command to launch a request for a hidden service
777 descriptor. Closes ticket 14847.
778 - New HSPOST command to upload a hidden service descriptor. Closes
779 ticket 3523. Patch by "DonnchaC".
781 o Major bugfixes (hidden services):
782 - Revert commit that made directory authorities assign the HSDir
783 flag to relay without a DirPort; this was bad because such relays
784 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
785 on tor-0.2.6.3-alpha.
787 o Minor features (clock-jump tolerance):
788 - Recover better when our clock jumps back many hours, like might
789 happen for Tails or Whonix users who start with a very wrong
790 hardware clock, use Tor to discover a more accurate time, and then
791 fix their clock. Resolves part of ticket 8766.
793 o Minor features (command-line interface):
794 - Make --hash-password imply --hush to prevent unnecessary noise.
795 Closes ticket 15542. Patch from "cypherpunks".
796 - Print a warning whenever we find a relative file path being used
797 as torrc option. Resolves issue 14018.
799 o Minor features (controller):
800 - Add DirAuthority lines for default directory authorities to the
801 output of the "GETINFO config/defaults" command if not already
802 present. Implements ticket 14840.
803 - Controllers can now use "GETINFO hs/client/desc/id/..." to
804 retrieve items from the client's hidden service descriptor cache.
806 - Implement a new controller command "GETINFO status/fresh-relay-
807 descs" to fetch a descriptor/extrainfo pair that was generated on
808 demand just for the controller's use. Implements ticket 14784.
810 o Minor features (DoS-resistance):
811 - Make it harder for attackers to overload hidden services with
812 introductions, by blocking multiple introduction requests on the
813 same circuit. Resolves ticket 15515.
815 o Minor features (geoip):
816 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
817 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
820 o Minor features (HS popularity countermeasure):
821 - To avoid leaking HS popularity, don't cycle the introduction point
822 when we've handled a fixed number of INTRODUCE2 cells but instead
823 cycle it when a random number of introductions is reached, thus
824 making it more difficult for an attacker to find out the amount of
825 clients that have used the introduction point for a specific HS.
828 o Minor features (logging):
829 - Include the Tor version in all LD_BUG log messages, since people
830 tend to cut and paste those into the bugtracker. Implements
833 o Minor features (pluggable transports):
834 - When launching managed pluggable transports on Linux systems,
835 attempt to have the kernel deliver a SIGTERM on tor exit if the
836 pluggable transport process is still running. Resolves
838 - When launching managed pluggable transports, setup a valid open
839 stdin in the child process that can be used to detect if tor has
840 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
841 can be used by implementations to detect this new behavior.
842 Resolves ticket 15435.
844 o Minor features (testing):
845 - Add a test to verify that the compiler does not eliminate our
846 memwipe() implementation. Closes ticket 15377.
847 - Add make rule `check-changes` to verify the format of changes
848 files. Closes ticket 15180.
849 - Add unit tests for control_event_is_interesting(). Add a compile-
850 time check that the number of events doesn't exceed the capacity
851 of control_event_t.event_mask. Closes ticket 15431, checks for
852 bugs similar to 13085. Patch by "teor".
853 - Command-line argument tests moved to Stem. Resolves ticket 14806.
854 - Integrate the ntor, backtrace, and zero-length keys tests into the
855 automake test suite. Closes ticket 15344.
856 - Remove assertions during builds to determine Tor's test coverage.
857 We don't want to trigger these even in assertions, so including
858 them artificially makes our branch coverage look worse than it is.
859 This patch provides the new test-stem-full and coverage-html-full
860 configure options. Implements ticket 15400.
862 o Minor bugfixes (build):
863 - Improve out-of-tree builds by making non-standard rules work and
864 clean up additional files and directories. Fixes bug 15053; bugfix
867 o Minor bugfixes (command-line interface):
868 - When "--quiet" is provided along with "--validate-config", do not
869 write anything to stdout on success. Fixes bug 14994; bugfix
871 - When complaining about bad arguments to "--dump-config", use
874 o Minor bugfixes (configuration, unit tests):
875 - Only add the default fallback directories when the DirAuthorities,
876 AlternateDirAuthority, and FallbackDir directory config options
877 are set to their defaults. The default fallback directory list is
878 currently empty, this fix will only change tor's behavior when it
879 has default fallback directories. Includes unit tests for
880 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
881 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
883 o Minor bugfixes (correctness):
884 - For correctness, avoid modifying a constant string in
885 handle_control_postdescriptor. Fixes bug 15546; bugfix
887 - Remove side-effects from tor_assert() calls. This was harmless,
888 because we never disable assertions, but it is bad style and
889 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
892 o Minor bugfixes (hidden service):
893 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
894 a client authorized hidden service. Fixes bug 15823; bugfix
896 - Remove an extraneous newline character from the end of hidden
897 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
899 o Minor bugfixes (interface):
900 - Print usage information for --dump-config when it is used without
901 an argument. Also, fix the error message to use different wording
902 and add newline at the end. Fixes bug 15541; bugfix
905 o Minor bugfixes (logs):
906 - When building Tor under Clang, do not include an extra set of
907 parentheses in log messages that include function names. Fixes bug
908 15269; bugfix on every released version of Tor when compiled with
911 o Minor bugfixes (network):
912 - When attempting to use fallback technique for network interface
913 lookup, disregard loopback and multicast addresses since they are
914 unsuitable for public communications.
916 o Minor bugfixes (statistics):
917 - Disregard the ConnDirectionStatistics torrc options when Tor is
918 not a relay since in that mode of operation no sensible data is
919 being collected and because Tor might run into measurement hiccups
920 when running as a client for some time, then becoming a relay.
921 Fixes bug 15604; bugfix on 0.2.2.35.
923 o Minor bugfixes (test networks):
924 - When self-testing reachability, use ExtendAllowPrivateAddresses to
925 determine if local/private addresses imply reachability. The
926 previous fix used TestingTorNetwork, which implies
927 ExtendAllowPrivateAddresses, but this excluded rare configurations
928 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
929 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
930 issue discovered by CJ Ess.
932 o Minor bugfixes (testing):
933 - Check for matching value in server response in ntor_ref.py. Fixes
934 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
936 - Set the severity correctly when testing
937 get_interface_addresses_ifaddrs() and
938 get_interface_addresses_win32(), so that the tests fail gracefully
939 instead of triggering an assertion. Fixes bug 15759; bugfix on
940 0.2.6.3-alpha. Reported by Nicolas Derive.
942 o Code simplification and refactoring:
943 - Move the hacky fallback code out of get_interface_address6() into
944 separate function and get it covered with unit-tests. Resolves
946 - Refactor hidden service client-side cache lookup to intelligently
947 report its various failure cases, and disentangle failure cases
948 involving a lack of introduction points. Closes ticket 14391.
949 - Use our own Base64 encoder instead of OpenSSL's, to allow more
950 control over the output. Part of ticket 15652.
953 - Improve the descriptions of statistics-related torrc options in
954 the manpage to describe rationale and possible uses cases. Fixes
956 - Improve the layout and formatting of ./configure --help messages.
957 Closes ticket 15024. Patch from "cypherpunks".
958 - Standardize on the term "server descriptor" in the manual page.
959 Previously, we had used "router descriptor", "server descriptor",
960 and "relay descriptor" interchangeably. Part of ticket 14987.
963 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
964 and always use the internal Base64 decoder. The internal decoder
965 has been part of tor since tor-0.2.0.10-alpha, and no one should
966 be using the OpenSSL one. Part of ticket 15652.
967 - Remove the 'tor_strclear()' function; use memwipe() instead.
971 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
972 fingerprinting we now recommend pluggable transports; for forward-
973 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
974 - Remove the undocumented "--digests" command-line option. It
975 complicated our build process, caused subtle build issues on
976 multiple platforms, and is now redundant since we started
977 including git version identifiers. Closes ticket 14742.
978 - Tor no longer contains checks for ancient directory cache versions
979 that didn't know about microdescriptors.
980 - Tor no longer contains workarounds for stat files generated by
981 super-old versions of Tor that didn't choose guards sensibly.
984 Changes in version 0.2.4.27 - 2015-04-06
985 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
986 could be used by an attacker to crash hidden services, or crash clients
987 visiting hidden services. Hidden services should upgrade as soon as
988 possible; clients should upgrade whenever packages become available.
990 This release also backports a simple improvement to make hidden
991 services a bit less vulnerable to denial-of-service attacks.
993 o Major bugfixes (security, hidden service):
994 - Fix an issue that would allow a malicious client to trigger an
995 assertion failure and halt a hidden service. Fixes bug 15600;
996 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
997 - Fix a bug that could cause a client to crash with an assertion
998 failure when parsing a malformed hidden service descriptor. Fixes
999 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1001 o Minor features (DoS-resistance, hidden service):
1002 - Introduction points no longer allow multiple INTRODUCE1 cells to
1003 arrive on the same circuit. This should make it more expensive for
1004 attackers to overwhelm hidden services with introductions.
1005 Resolves ticket 15515.
1008 Changes in version 0.2.6.7 - 2015-04-06
1009 Tor 0.2.6.7 fixes two security issues that could be used by an
1010 attacker to crash hidden services, or crash clients visiting hidden
1011 services. Hidden services should upgrade as soon as possible; clients
1012 should upgrade whenever packages become available.
1014 This release also contains two simple improvements to make hidden
1015 services a bit less vulnerable to denial-of-service attacks.
1017 o Major bugfixes (security, hidden service):
1018 - Fix an issue that would allow a malicious client to trigger an
1019 assertion failure and halt a hidden service. Fixes bug 15600;
1020 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
1021 - Fix a bug that could cause a client to crash with an assertion
1022 failure when parsing a malformed hidden service descriptor. Fixes
1023 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1025 o Minor features (DoS-resistance, hidden service):
1026 - Introduction points no longer allow multiple INTRODUCE1 cells to
1027 arrive on the same circuit. This should make it more expensive for
1028 attackers to overwhelm hidden services with introductions.
1029 Resolves ticket 15515.
1030 - Decrease the amount of reattempts that a hidden service performs
1031 when its rendezvous circuits fail. This reduces the computational
1032 cost for running a hidden service under heavy load. Resolves
1036 Changes in version 0.2.6.6 - 2015-03-24
1037 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
1039 It adds numerous safety, security, correctness, and performance
1040 improvements. Client programs can be configured to use more kinds of
1041 sockets, AutomapHosts works better, the multithreading backend is
1042 improved, cell transmission is refactored, test coverage is much
1043 higher, more denial-of-service attacks are handled, guard selection is
1044 improved to handle long-term guards better, pluggable transports
1045 should work a bit better, and some annoying hidden service performance
1046 bugs should be addressed.
1048 o Minor bugfixes (portability):
1049 - Use the correct datatype in the SipHash-2-4 function to prevent
1050 compilers from assuming any sort of alignment. Fixes bug 15436;
1051 bugfix on 0.2.5.3-alpha.
1053 Changes in version 0.2.6.5-rc - 2015-03-18
1054 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
1055 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
1057 o Major bugfixes (client):
1058 - Avoid crashing when making certain configuration option changes on
1059 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
1062 o Major bugfixes (pluggable transports):
1063 - Initialize the extended OR Port authentication cookie before
1064 launching pluggable transports. This prevents a race condition
1065 that occured when server-side pluggable transports would cache the
1066 authentication cookie before it has been (re)generated. Fixes bug
1067 15240; bugfix on 0.2.5.1-alpha.
1069 o Major bugfixes (portability):
1070 - Do not crash on startup when running on Solaris. Fixes a bug
1071 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
1074 o Minor features (heartbeat):
1075 - On relays, report how many connections we negotiated using each
1076 version of the Tor link protocols. This information will let us
1077 know if removing support for very old versions of the Tor
1078 protocols is harming the network. Closes ticket 15212.
1080 o Code simplification and refactoring:
1081 - Refactor main loop to extract the 'loop' part. This makes it
1082 easier to run Tor under Shadow. Closes ticket 15176.
1085 Changes in version 0.2.5.11 - 2015-03-17
1086 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
1088 It backports several bugfixes from the 0.2.6 branch, including a
1089 couple of medium-level security fixes for relays and exit nodes.
1090 It also updates the list of directory authorities.
1092 o Directory authority changes:
1093 - Remove turtles as a directory authority.
1094 - Add longclaw as a new (v3) directory authority. This implements
1095 ticket 13296. This keeps the directory authority count at 9.
1096 - The directory authority Faravahar has a new IP address. This
1097 closes ticket 14487.
1099 o Major bugfixes (crash, OSX, security):
1100 - Fix a remote denial-of-service opportunity caused by a bug in
1101 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
1104 o Major bugfixes (relay, stability, possible security):
1105 - Fix a bug that could lead to a relay crashing with an assertion
1106 failure if a buffer of exactly the wrong layout was passed to
1107 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1108 0.2.0.10-alpha. Patch from 'cypherpunks'.
1109 - Do not assert if the 'data' pointer on a buffer is advanced to the
1110 very end of the buffer; log a BUG message instead. Only assert if
1111 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1113 o Major bugfixes (exit node stability):
1114 - Fix an assertion failure that could occur under high DNS load.
1115 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1116 diagnosed and fixed by "cypherpunks".
1118 o Major bugfixes (Linux seccomp2 sandbox):
1119 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
1120 crash during attempts to call wait4. Fixes bug 15088; bugfix on
1121 0.2.5.1-alpha. Patch from "sanic".
1123 o Minor features (controller):
1124 - New "GETINFO bw-event-cache" to get information about recent
1125 bandwidth events. Closes ticket 14128. Useful for controllers to
1126 get recent bandwidth history after the fix for ticket 13988.
1128 o Minor features (geoip):
1129 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1130 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1133 o Minor bugfixes (client, automapping):
1134 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
1135 no value follows the option. Fixes bug 14142; bugfix on
1136 0.2.4.7-alpha. Patch by "teor".
1137 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
1138 14195; bugfix on 0.1.0.1-rc.
1140 o Minor bugfixes (compilation):
1141 - Build without warnings with the stock OpenSSL srtp.h header, which
1142 has a duplicate declaration of SSL_get_selected_srtp_profile().
1143 Fixes bug 14220; this is OpenSSL's bug, not ours.
1145 o Minor bugfixes (directory authority):
1146 - Allow directory authorities to fetch more data from one another if
1147 they find themselves missing lots of votes. Previously, they had
1148 been bumping against the 10 MB queued data limit. Fixes bug 14261;
1149 bugfix on 0.1.2.5-alpha.
1150 - Enlarge the buffer to read bwauth generated files to avoid an
1151 issue when parsing the file in dirserv_read_measured_bandwidths().
1152 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
1154 o Minor bugfixes (statistics):
1155 - Increase period over which bandwidth observations are aggregated
1156 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
1158 o Minor bugfixes (preventative security, C safety):
1159 - When reading a hexadecimal, base-32, or base-64 encoded value from
1160 a string, always overwrite the whole output buffer. This prevents
1161 some bugs where we would look at (but fortunately, not reveal)
1162 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
1166 Changes in version 0.2.4.26 - 2015-03-17
1167 Tor 0.2.4.26 includes an updated list of directory authorities. It
1168 also backports a couple of stability and security bugfixes from 0.2.5
1171 o Directory authority changes:
1172 - Remove turtles as a directory authority.
1173 - Add longclaw as a new (v3) directory authority. This implements
1174 ticket 13296. This keeps the directory authority count at 9.
1175 - The directory authority Faravahar has a new IP address. This
1176 closes ticket 14487.
1178 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
1179 - Fix an assertion failure that could occur under high DNS load.
1180 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1181 diagnosed and fixed by "cypherpunks".
1183 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
1184 - Fix a bug that could lead to a relay crashing with an assertion
1185 failure if a buffer of exactly the wrong layout was passed to
1186 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1187 0.2.0.10-alpha. Patch from 'cypherpunks'.
1188 - Do not assert if the 'data' pointer on a buffer is advanced to the
1189 very end of the buffer; log a BUG message instead. Only assert if
1190 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1192 o Minor features (geoip):
1193 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1194 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1197 Changes in version 0.2.6.4-rc - 2015-03-09
1198 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
1199 attacker might be able to use in order to crash certain Tor
1200 directories. It also resolves some minor issues left over from, or
1201 introduced in, Tor 0.2.6.3-alpha or earlier.
1203 o Major bugfixes (crash, OSX, security):
1204 - Fix a remote denial-of-service opportunity caused by a bug in
1205 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
1208 o Major bugfixes (relay, stability, possible security):
1209 - Fix a bug that could lead to a relay crashing with an assertion
1210 failure if a buffer of exactly the wrong layout is passed to
1211 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1212 0.2.0.10-alpha. Patch from "cypherpunks".
1213 - Do not assert if the 'data' pointer on a buffer is advanced to the
1214 very end of the buffer; log a BUG message instead. Only assert if
1215 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1217 o Major bugfixes (FreeBSD IPFW transparent proxy):
1218 - Fix address detection with FreeBSD transparent proxies, when
1219 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
1222 o Major bugfixes (Linux seccomp2 sandbox):
1223 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
1224 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
1226 - Allow AF_UNIX hidden services to be used with the seccomp2
1227 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
1228 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
1229 crash during attempts to call wait4. Fixes bug 15088; bugfix on
1230 0.2.5.1-alpha. Patch from "sanic".
1232 o Minor features (controller):
1233 - Messages about problems in the bootstrap process now include
1234 information about the server we were trying to connect to when we
1235 noticed the problem. Closes ticket 15006.
1237 o Minor features (geoip):
1238 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1239 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1242 o Minor features (logs):
1243 - Quiet some log messages in the heartbeat and at startup. Closes
1246 o Minor bugfixes (certificate handling):
1247 - If an authority operator accidentally makes a signing certificate
1248 with a future publication time, do not discard its real signing
1249 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
1250 - Remove any old authority certificates that have been superseded
1251 for at least two days. Previously, we would keep superseded
1252 certificates until they expired, if they were published close in
1253 time to the certificate that superseded them. Fixes bug 11454;
1254 bugfix on 0.2.1.8-alpha.
1256 o Minor bugfixes (compilation):
1257 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
1259 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
1262 o Minor bugfixes (testing):
1263 - Fix endianness issues in unit test for resolve_my_address() to
1264 have it pass on big endian systems. Fixes bug 14980; bugfix on
1266 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
1267 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
1268 - When running the new 'make test-stem' target, use the configured
1269 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
1271 - When running the zero-length-keys tests, do not use the default
1272 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
1275 o Directory authority IP change:
1276 - The directory authority Faravahar has a new IP address. This
1277 closes ticket 14487.
1280 - Remove some lingering dead code that once supported mempools.
1281 Mempools were disabled by default in 0.2.5, and removed entirely
1282 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
1286 Changes in version 0.2.6.3-alpha - 2015-02-19
1287 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
1288 the 0.2.6.x series. It introduces support for more kinds of sockets,
1289 makes it harder to accidentally run an exit, improves our
1290 multithreading backend, incorporates several fixes for the
1291 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
1293 If no major regressions or security holes are found in this version,
1294 the next version will be a release candidate.
1296 o Deprecated versions:
1297 - Tor relays older than 0.2.4.18-rc are no longer allowed to
1298 advertise themselves on the network. Closes ticket 13555.
1300 o Major features (security, unix domain sockets):
1301 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
1302 applications can reach Tor without having to create AF_INET or
1303 AF_INET6 sockets, meaning they can completely disable their
1304 ability to make non-Tor network connections. To create a socket of
1305 this type, use "SocksPort unix:/path/to/socket". Implements
1307 - Support mapping hidden service virtual ports to AF_UNIX sockets.
1308 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
1309 Implements ticket 11485.
1311 o Major features (changed defaults):
1312 - Prevent relay operators from unintentionally running exits: When a
1313 relay is configured as an exit node, we now warn the user unless
1314 the "ExitRelay" option is set to 1. We warn even more loudly if
1315 the relay is configured with the default exit policy, since this
1316 can indicate accidental misconfiguration. Setting "ExitRelay 0"
1317 stops Tor from running as an exit relay. Closes ticket 10067.
1319 o Major features (directory system):
1320 - When downloading server- or microdescriptors from a directory
1321 server, we no longer launch multiple simultaneous requests to the
1322 same server. This reduces load on the directory servers,
1323 especially when directory guards are in use. Closes ticket 9969.
1324 - When downloading server- or microdescriptors over a tunneled
1325 connection, do not limit the length of our requests to what the
1326 Squid proxy is willing to handle. Part of ticket 9969.
1327 - Authorities can now vote on the correct digests and latest
1328 versions for different software packages. This allows packages
1329 that include Tor to use the Tor authority system as a way to get
1330 notified of updates and their correct digests. Implements proposal
1331 227. Closes ticket 10395.
1333 o Major features (guards):
1334 - Introduce the Guardfraction feature to improves load balancing on
1335 guard nodes. Specifically, it aims to reduce the traffic gap that
1336 guard nodes experience when they first get the Guard flag. This is
1337 a required step if we want to increase the guard lifetime to 9
1338 months or greater. Closes ticket 9321.
1340 o Major features (performance):
1341 - Make the CPU worker implementation more efficient by avoiding the
1342 kernel and lengthening pipelines. The original implementation used
1343 sockets to transfer data from the main thread to the workers, and
1344 didn't allow any thread to be assigned more than a single piece of
1345 work at once. The new implementation avoids communications
1346 overhead by making requests in shared memory, avoiding kernel IO
1347 where possible, and keeping more requests in flight at once.
1348 Implements ticket 9682.
1350 o Major features (relay):
1351 - Raise the minimum acceptable configured bandwidth rate for bridges
1352 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
1353 20 KiB/sec.) Closes ticket 13822.
1355 o Major bugfixes (exit node stability):
1356 - Fix an assertion failure that could occur under high DNS load.
1357 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1358 diagnosed and fixed by "cypherpunks".
1360 o Major bugfixes (mixed relay-client operation):
1361 - When running as a relay and client at the same time (not
1362 recommended), if we decide not to use a new guard because we want
1363 to retry older guards, only close the locally-originating circuits
1364 passing through that guard. Previously we would close all the
1365 circuits through that guard. Fixes bug 9819; bugfix on
1366 0.2.1.1-alpha. Reported by "skruffy".
1368 o Minor features (build):
1369 - New --disable-system-torrc compile-time option to prevent Tor from
1370 looking for the system-wide torrc or torrc-defaults files.
1371 Resolves ticket 13037.
1373 o Minor features (controller):
1374 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
1375 events so controllers can observe circuit isolation inputs. Closes
1377 - ControlPort now supports the unix:/path/to/socket syntax as an
1378 alternative to the ControlSocket option, for consistency with
1379 SocksPort and HiddenServicePort. Closes ticket 14451.
1380 - New "GETINFO bw-event-cache" to get information about recent
1381 bandwidth events. Closes ticket 14128. Useful for controllers to
1382 get recent bandwidth history after the fix for ticket 13988.
1384 o Minor features (Denial of service resistance):
1385 - Count the total number of bytes used storing hidden service
1386 descriptors against the value of MaxMemInQueues. If we're low on
1387 memory, and more than 20% of our memory is used holding hidden
1388 service descriptors, free them until no more than 10% of our
1389 memory holds hidden service descriptors. Free the least recently
1390 fetched descriptors first. Resolves ticket 13806.
1391 - When we have recently been under memory pressure (over 3/4 of
1392 MaxMemInQueues is allocated), then allocate smaller zlib objects
1393 for small requests. Closes ticket 11791.
1395 o Minor features (geoip):
1396 - Update geoip and geoip6 files to the January 7 2015 Maxmind
1397 GeoLite2 Country database.
1399 o Minor features (guard nodes):
1400 - Reduce the time delay before saving guard status to disk from 10
1401 minutes to 30 seconds (or from one hour to 10 minutes if
1402 AvoidDiskWrites is set). Closes ticket 12485.
1404 o Minor features (hidden service):
1405 - Make Sybil attacks against hidden services harder by changing the
1406 minimum time required to get the HSDir flag from 25 hours up to 96
1407 hours. Addresses ticket 14149.
1408 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
1409 services to disable the anti-scanning feature introduced in
1410 0.2.6.2-alpha. With this option not set, a connection to an
1411 unlisted port closes the circuit. With this option set, only a
1412 RELAY_DONE cell is sent. Closes ticket 14084.
1414 o Minor features (interface):
1415 - Implement "-f -" command-line option to read torrc configuration
1416 from standard input, if you don't want to store the torrc file in
1417 the file system. Implements feature 13865.
1419 o Minor features (logging):
1420 - Add a count of unique clients to the bridge heartbeat message.
1421 Resolves ticket 6852.
1422 - Suppress "router info incompatible with extra info" message when
1423 reading extrainfo documents from cache. (This message got loud
1424 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
1426 - Elevate hidden service authorized-client message from DEBUG to
1427 INFO. Closes ticket 14015.
1429 o Minor features (stability):
1430 - Add assertions in our hash-table iteration code to check for
1431 corrupted values that could cause infinite loops. Closes
1434 o Minor features (systemd):
1435 - Various improvements and modernizations in systemd hardening
1436 support. Closes ticket 13805. Patch from Craig Andrews.
1438 o Minor features (testing networks):
1439 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
1440 and the default on a testing network to 2 minutes. Drop the
1441 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
1442 keep the default on a testing network at 30 seconds. This reduces
1443 HS bootstrap time to around 25 seconds. Also, change the default
1444 time in test-network.sh to match. Closes ticket 13401. Patch
1446 - Create TestingDirAuthVoteHSDir to correspond to
1447 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
1448 HSDir flag for the listed relays regardless of uptime or ORPort
1449 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
1450 Partial implementation for ticket 14067. Patch by "teor".
1452 o Minor features (tor2web mode):
1453 - Introduce the config option Tor2webRendezvousPoints, which allows
1454 clients in Tor2webMode to select a specific Rendezvous Point to be
1455 used in HS circuits. This might allow better performance for
1456 Tor2Web nodes. Implements ticket 12844.
1458 o Minor bugfixes (client DNS):
1459 - Report the correct cached DNS expiration times on SOCKS port or in
1460 DNS replies. Previously, we would report everything as "never
1461 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
1462 - Avoid a small memory leak when we find a cached answer for a
1463 reverse DNS lookup in a client-side DNS cache. (Remember, client-
1464 side DNS caching is off by default, and is not recommended.) Fixes
1465 bug 14259; bugfix on 0.2.0.1-alpha.
1467 o Minor bugfixes (client, automapping):
1468 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
1469 no value follows the option. Fixes bug 14142; bugfix on
1470 0.2.4.7-alpha. Patch by "teor".
1471 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
1472 14195; bugfix on 0.1.0.1-rc.
1473 - Prevent changes to other options from removing the wildcard value
1474 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
1476 - Allow MapAddress and AutomapHostsOnResolve to work together when
1477 an address is mapped into another address type (like .onion) that
1478 must be automapped at resolve time. Fixes bug 7555; bugfix
1481 o Minor bugfixes (client, bridges):
1482 - When we are using bridges and we had a network connectivity
1483 problem, only retry connecting to our currently configured
1484 bridges, not all bridges we know about and remember using. Fixes
1485 bug 14216; bugfix on 0.2.2.17-alpha.
1487 o Minor bugfixes (client, IPv6):
1488 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
1489 flag is not set; and not because the NoIPv4Traffic flag was set.
1490 Previously we'd looked at the NoIPv4Traffic flag for both types of
1491 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
1493 o Minor bugfixes (compilation):
1494 - The address of an array in the middle of a structure will always
1495 be non-NULL. clang recognises this and complains. Disable the
1496 tautologous and redundant check to silence this warning. Fixes bug
1497 14001; bugfix on 0.2.1.2-alpha.
1498 - Avoid warnings when building with systemd 209 or later. Fixes bug
1499 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
1500 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
1501 Addresses ticket 14188.
1502 - Build without warnings with the stock OpenSSL srtp.h header, which
1503 has a duplicate declaration of SSL_get_selected_srtp_profile().
1504 Fixes bug 14220; this is OpenSSL's bug, not ours.
1505 - Do not compile any code related to Tor2Web mode when Tor2Web mode
1506 is not enabled at compile time. Previously, this code was included
1507 in a disabled state. See discussion on ticket 12844.
1508 - Remove the --disable-threads configure option again. It was
1509 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
1510 14819; bugfix on 0.2.6.2-alpha.
1512 o Minor bugfixes (controller):
1513 - Report "down" in response to the "GETINFO entry-guards" command
1514 when relays are down with an unreachable_since value. Previously,
1515 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
1516 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
1517 14116; bugfix on 0.2.2.9-alpha.
1518 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
1519 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
1521 o Minor bugfixes (directory authority):
1522 - Allow directory authorities to fetch more data from one another if
1523 they find themselves missing lots of votes. Previously, they had
1524 been bumping against the 10 MB queued data limit. Fixes bug 14261;
1525 bugfix on 0.1.2.5-alpha.
1526 - Do not attempt to download extrainfo documents which we will be
1527 unable to validate with a matching server descriptor. Fixes bug
1528 13762; bugfix on 0.2.0.1-alpha.
1529 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
1530 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
1531 - Enlarge the buffer to read bwauth generated files to avoid an
1532 issue when parsing the file in dirserv_read_measured_bandwidths().
1533 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
1535 o Minor bugfixes (file handling):
1536 - Stop failing when key files are zero-length. Instead, generate new
1537 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
1538 on all versions of Tor. Patch by "teor".
1539 - Stop generating a fresh .old RSA onion key file when the .old file
1540 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
1541 - Avoid overwriting .old key files with empty key files.
1542 - Skip loading zero-length extrainfo store, router store, stats,
1543 state, and key files.
1544 - Avoid crashing when trying to reload a torrc specified as a
1545 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
1548 o Minor bugfixes (hidden services):
1549 - Close the introduction circuit when we have no more usable intro
1550 points, instead of waiting for it to time out. This also ensures
1551 that no follow-up HS descriptor fetch is triggered when the
1552 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
1553 - When fetching a hidden service descriptor for a down service that
1554 was recently up, do not keep refetching until we try the same
1555 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
1556 - Successfully launch Tor with a nonexistent hidden service
1557 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
1558 14106; bugfix on 0.2.6.2-alpha.
1560 o Minor bugfixes (logging):
1561 - Avoid crashing when there are more log domains than entries in
1562 domain_list. Bugfix on 0.2.3.1-alpha.
1563 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
1565 - Don't log messages to stdout twice when starting up. Fixes bug
1566 13993; bugfix on 0.2.6.1-alpha.
1568 o Minor bugfixes (parsing):
1569 - Stop accepting milliseconds (or other junk) at the end of
1570 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
1571 - Support two-number and three-number version numbers correctly, in
1572 case we change the Tor versioning system in the future. Fixes bug
1573 13661; bugfix on 0.0.8pre1.
1575 o Minor bugfixes (path counting):
1576 - When deciding whether the consensus lists any exit nodes, count
1577 the number listed in the consensus, not the number we have
1578 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
1579 - When deciding whether we have any exit nodes, only examine
1580 ExitNodes when the ExitNodes option is actually set. Fixes part of
1581 bug 14918; bugfix on 0.2.6.2-alpha.
1582 - Get rid of redundant and possibly scary warnings that we are
1583 missing directory information while we bootstrap. Fixes part of
1584 bug 14918; bugfix on 0.2.6.2-alpha.
1586 o Minor bugfixes (portability):
1587 - Fix the ioctl()-based network interface lookup code so that it
1588 will work on systems that have variable-length struct ifreq, for
1590 - Fix scheduler compilation on targets where char is unsigned. Fixes
1591 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
1593 o Minor bugfixes (sandbox):
1594 - Allow glibc fatal errors to be sent to stderr before Tor exits.
1595 Previously, glibc would try to write them to /dev/tty, and the
1596 sandbox would trap the call and make Tor exit prematurely. Fixes
1597 bug 14759; bugfix on 0.2.5.1-alpha.
1599 o Minor bugfixes (shutdown):
1600 - When shutting down, always call event_del() on lingering read or
1601 write events before freeing them. Otherwise, we risk double-frees
1602 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
1605 o Minor bugfixes (small memory leaks):
1606 - Avoid leaking memory when using IPv6 virtual address mappings.
1607 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
1610 o Minor bugfixes (statistics):
1611 - Increase period over which bandwidth observations are aggregated
1612 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
1614 o Minor bugfixes (systemd support):
1615 - Fix detection and operation of systemd watchdog. Fixes part of bug
1616 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
1617 - Run correctly under systemd with the RunAsDaemon option set. Fixes
1618 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
1619 - Inform the systemd supervisor about more changes in the Tor
1620 process status. Implements part of ticket 14141. Patch from
1622 - Cause the "--disable-systemd" option to actually disable systemd
1623 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
1626 o Minor bugfixes (TLS):
1627 - Check more thoroughly throughout the TLS code for possible
1628 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
1630 o Minor bugfixes (transparent proxy):
1631 - Use getsockname, not getsockopt, to retrieve the address for a
1632 TPROXY-redirected connection. Fixes bug 13796; bugfix
1635 o Code simplification and refactoring:
1636 - Move fields related to isolating and configuring client ports into
1637 a shared structure. Previously, they were duplicated across
1638 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
1639 to copy them correctly had been the cause of at least one bug in
1640 the past. Closes ticket 8546.
1641 - Refactor the get_interface_addresses_raw() doom-function into
1642 multiple smaller and simpler subfunctions. Cover the resulting
1643 subfunctions with unit-tests. Fixes a significant portion of
1645 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
1646 only for version <= 0.2.2.24 which is now deprecated. Closes
1648 - Remove a test for a long-defunct broken version-one
1652 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
1653 for writing the OpenBSD-specific tips. Resolves ticket 13702.
1654 - Make the tor-resolve documentation match its help string and its
1655 options. Resolves part of ticket 14325.
1656 - Log a more useful error message from tor-resolve when failing to
1657 look up a hidden service address. Resolves part of ticket 14325.
1659 o Downgraded warnings:
1660 - Don't warn when we've attempted to contact a relay using the wrong
1661 ntor onion key. Closes ticket 9635.
1664 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
1665 longer silently accepted as an alias for "ExitNodes".
1666 - The --enable-mempool and --enable-buf-freelists options, which
1667 were originally created to work around bad malloc implementations,
1668 no longer exist. They were off-by-default in 0.2.5. Closes
1672 - Make the checkdir/perms test complete successfully even if the
1673 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
1674 - Test that tor does not fail when key files are zero-length. Check
1675 that tor generates new keys, and overwrites the empty key files.
1676 - Test that tor generates new keys when keys are missing
1677 (existing behavior).
1678 - Test that tor does not overwrite key files that already contain
1679 data (existing behavior). Tests bug 13111. Patch by "teor".
1680 - New "make test-stem" target to run stem integration tests.
1681 Requires that the "STEM_SOURCE_DIR" environment variable be set.
1682 Closes ticket 14107.
1683 - Make the test_cmdline_args.py script work correctly on Windows.
1684 Patch from Gisle Vanem.
1685 - Move the slower unit tests into a new "./src/test/test-slow"
1686 binary that can be run independently of the other tests. Closes
1688 - Avoid undefined behavior when sampling huge values from the
1689 Laplace distribution. This made unittests fail on Raspberry Pi.
1690 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
1693 Changes in version 0.2.6.2-alpha - 2014-12-31
1694 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
1695 It introduces a major new backend for deciding when to send cells on
1696 channels, which should lead down the road to big performance
1697 increases. It contains security and statistics features for better
1698 work on hidden services, and numerous bugfixes.
1700 This release contains many new unit tests, along with major
1701 performance improvements for running testing networks using Chutney.
1702 Thanks to a series of patches contributed by "teor", testing networks
1703 should now bootstrap in seconds, rather than minutes.
1705 o Major features (relay, infrastructure):
1706 - Complete revision of the code that relays use to decide which cell
1707 to send next. Formerly, we selected the best circuit to write on
1708 each channel, but we didn't select among channels in any
1709 sophisticated way. Now, we choose the best circuits globally from
1710 among those whose channels are ready to deliver traffic.
1712 This patch implements a new inter-cmux comparison API, a global
1713 high/low watermark mechanism and a global scheduler loop for
1714 transmission prioritization across all channels as well as among
1715 circuits on one channel. This schedule is currently tuned to
1716 (tolerantly) avoid making changes in network performance, but it
1717 should form the basis for major circuit performance increases in
1718 the future. Code by Andrea; tuning by Rob Jansen; implements
1721 o Major features (hidden services):
1722 - Make HS port scanning more difficult by immediately closing the
1723 circuit when a user attempts to connect to a nonexistent port.
1724 Closes ticket 13667.
1725 - Add a HiddenServiceStatistics option that allows Tor relays to
1726 gather and publish statistics about the overall size and volume of
1727 hidden service usage. Specifically, when this option is turned on,
1728 an HSDir will publish an approximate number of hidden services
1729 that have published descriptors to it the past 24 hours. Also, if
1730 a relay has acted as a hidden service rendezvous point, it will
1731 publish the approximate amount of rendezvous cells it has relayed
1732 the past 24 hours. The statistics themselves are obfuscated so
1733 that the exact values cannot be derived. For more details see
1734 proposal 238, "Better hidden service stats from Tor relays". This
1735 feature is currently disabled by default. Implements feature 13192.
1737 o Major bugfixes (client, automap):
1738 - Repair automapping with IPv6 addresses. This automapping should
1739 have worked previously, but one piece of debugging code that we
1740 inserted to detect a regression actually caused the regression to
1741 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
1742 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
1745 o Major bugfixes (hidden services):
1746 - When closing an introduction circuit that was opened in parallel
1747 with others, don't mark the introduction point as unreachable.
1748 Previously, the first successful connection to an introduction
1749 point would make the other introduction points get marked as
1750 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
1752 o Directory authority changes:
1753 - Remove turtles as a directory authority.
1754 - Add longclaw as a new (v3) directory authority. This implements
1755 ticket 13296. This keeps the directory authority count at 9.
1757 o Major removed features:
1758 - Tor clients no longer support connecting to hidden services
1759 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
1760 option has been removed. (There shouldn't be any hidden services
1761 running these versions on the network.) Closes ticket 7803.
1763 o Minor features (client):
1764 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
1765 is enabled, reject requests with IP addresses as hostnames.
1766 Resolves ticket 13315.
1768 o Minor features (controller):
1769 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
1770 write an unscheduled heartbeat message to the log. Implements
1773 o Minor features (geoip):
1774 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
1777 o Minor features (hidden services):
1778 - When re-enabling the network, don't try to build introduction
1779 circuits until we have successfully built a circuit. This makes
1780 hidden services come up faster when the network is re-enabled.
1781 Patch from "akwizgran". Closes ticket 13447.
1782 - When we fail to retrieve a hidden service descriptor, send the
1783 controller an "HS_DESC FAILED" controller event. Implements
1785 - New HiddenServiceDirGroupReadable option to cause hidden service
1786 directories and hostname files to be created group-readable. Patch
1787 from "anon", David Stainton, and "meejah". Closes ticket 11291.
1789 o Minor features (systemd):
1790 - Where supported, when running with systemd, report successful
1791 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
1792 - When running with systemd, support systemd watchdog messages. Part
1793 of ticket 11016. Patch by Michael Scherer.
1795 o Minor features (transparent proxy):
1796 - Update the transparent proxy option checks to allow for both ipfw
1797 and pf on OS X. Closes ticket 14002.
1798 - Use the correct option when using IPv6 with transparent proxy
1799 support on Linux. Resolves 13808. Patch by Francisco Blas
1802 o Minor bugfixes (preventative security, C safety):
1803 - When reading a hexadecimal, base-32, or base-64 encoded value from
1804 a string, always overwrite the whole output buffer. This prevents
1805 some bugs where we would look at (but fortunately, not reveal)
1806 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
1808 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
1809 just the part that's used. This makes it harder for data leak bugs
1810 to occur in the event of other programming failures. Resolves
1813 o Minor bugfixes (client, microdescriptors):
1814 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
1815 computing which microdescriptors to download. This keeps us from
1816 erroneous download behavior if two microdescriptor digests ever
1817 have the same first 160 bits. Fixes part of bug 13399; bugfix
1819 - Reset a router's status if its microdescriptor digest changes,
1820 even if the first 160 bits remain the same. Fixes part of bug
1821 13399; bugfix on 0.2.3.1-alpha.
1823 o Minor bugfixes (compilation):
1824 - Silence clang warnings under --enable-expensive-hardening,
1825 including implicit truncation of 64 bit values to 32 bit, const
1826 char assignment to self, tautological compare, and additional
1827 parentheses around equality tests. Fixes bug 13577; bugfix
1829 - Fix a clang warning about checking whether an address in the
1830 middle of a structure is NULL. Fixes bug 14001; bugfix
1833 o Minor bugfixes (hidden services):
1834 - Correctly send a controller event when we find that a rendezvous
1835 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
1836 - Pre-check directory permissions for new hidden-services to avoid
1837 at least one case of "Bug: Acting on config options left us in a
1838 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
1839 - When adding a new hidden service (for example, via SETCONF), Tor
1840 no longer congratulates the user for running a relay. Fixes bug
1841 13941; bugfix on 0.2.6.1-alpha.
1842 - When fetching hidden service descriptors, we now check not only
1843 for whether we got the hidden service we had in mind, but also
1844 whether we got the particular descriptors we wanted. This prevents
1845 a class of inefficient but annoying DoS attacks by hidden service
1846 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
1849 o Minor bugfixes (Linux seccomp2 sandbox):
1850 - Make transparent proxy support work along with the seccomp2
1851 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
1852 by Francisco Blas Izquierdo Riera.
1853 - Fix a memory leak in tor-resolve when running with the sandbox
1854 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
1856 o Minor bugfixes (logging):
1857 - Downgrade warnings about RSA signature failures to info log level.
1858 Emit a warning when an extra info document is found incompatible
1859 with a corresponding router descriptor. Fixes bug 9812; bugfix
1861 - Make connection_ap_handshake_attach_circuit() log the circuit ID
1862 correctly. Fixes bug 13701; bugfix on 0.0.6.
1864 o Minor bugfixes (misc):
1865 - Stop allowing invalid address patterns like "*/24" that contain
1866 both a wildcard address and a bit prefix length. This affects all
1867 our address-range parsing code. Fixes bug 7484; bugfix
1870 o Minor bugfixes (testing networks, fast startup):
1871 - Allow Tor to build circuits using a consensus with no exits. If
1872 the consensus has no exits (typical of a bootstrapping test
1873 network), allow Tor to build circuits once enough descriptors have
1874 been downloaded. This assists in bootstrapping a testing Tor
1875 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
1877 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
1878 header to directory servers. This allows us to obtain consensuses
1879 promptly when the consensus interval is very short. This assists
1880 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
1881 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
1882 - Stop assuming that private addresses are local when checking
1883 reachability in a TestingTorNetwork. Instead, when testing, assume
1884 all OR connections are remote. (This is necessary due to many test
1885 scenarios running all relays on localhost.) This assists in
1886 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
1887 0.1.0.1-rc. Patch by "teor".
1888 - Avoid building exit circuits from a consensus with no exits. Now
1889 thanks to our fix for 13718, we accept a no-exit network as not
1890 wholly lost, but we need to remember not to try to build exit
1891 circuits on it. Closes ticket 13814; patch by "teor".
1892 - Stop requiring exits to have non-zero bandwithcapacity in a
1893 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
1894 ignore exit bandwidthcapacity. This assists in bootstrapping a
1895 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
1896 on 0.2.0.3-alpha. Patch by "teor".
1897 - Add "internal" to some bootstrap statuses when no exits are
1898 available. If the consensus does not contain Exits, Tor will only
1899 build internal circuits. In this case, relevant statuses will
1900 contain the word "internal" as indicated in the Tor control-
1901 spec.txt. When bootstrap completes, Tor will be ready to build
1902 internal circuits. If a future consensus contains Exits, exit
1903 circuits may become available. Fixes part of bug 13718; bugfix on
1904 0.2.4.10-alpha. Patch by "teor".
1905 - Decrease minimum consensus interval to 10 seconds when
1906 TestingTorNetwork is set, or 5 seconds for the first consensus.
1907 Fix assumptions throughout the code that assume larger intervals.
1908 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
1910 - Avoid excluding guards from path building in minimal test
1911 networks, when we're in a test network and excluding guards would
1912 exclude all relays. This typically occurs in incredibly small tor
1913 networks, and those using "TestingAuthVoteGuard *". Fixes part of
1914 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
1916 o Code simplification and refactoring:
1917 - Stop using can_complete_circuits as a global variable; access it
1918 with a function instead.
1919 - Avoid using operators directly as macro arguments: this lets us
1920 apply coccinelle transformations to our codebase more directly.
1921 Closes ticket 13172.
1922 - Combine the functions used to parse ClientTransportPlugin and
1923 ServerTransportPlugin into a single function. Closes ticket 6456.
1924 - Add inline functions and convenience macros for inspecting channel
1925 state. Refactor the code to use convenience macros instead of
1926 checking channel state directly. Fixes issue 7356.
1927 - Document all members of was_router_added_t and rename
1928 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
1929 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
1930 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
1931 constant instead of hardcoded value. Fixes issue 13840.
1932 - Refactor our generic strmap and digestmap types into a single
1933 implementation, so that we can add a new digest256map
1937 - Document the bridge-authority-only 'networkstatus-bridges' file.
1938 Closes ticket 13713; patch from "tom".
1939 - Fix typo in PredictedPortsRelevanceTime option description in
1940 manpage. Resolves issue 13707.
1941 - Stop suggesting that users specify relays by nickname: it isn't a
1942 good idea. Also, properly cross-reference how to specify relays in
1943 all parts of manual documenting options that take a list of
1944 relays. Closes ticket 13381.
1945 - Clarify the HiddenServiceDir option description in manpage to make
1946 it clear that relative paths are taken with respect to the current
1947 working directory. Also clarify that this behavior is not
1948 guaranteed to remain indefinitely. Fixes issue 13913.
1951 - New tests for many parts of channel, relay, and circuitmux
1952 functionality. Code by Andrea; part of 9262.
1953 - New tests for parse_transport_line(). Part of ticket 6456.
1954 - In the unit tests, use chgrp() to change the group of the unit
1955 test temporary directory to the current user, so that the sticky
1956 bit doesn't interfere with tests that check directory groups.
1958 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
1962 Changes in version 0.2.6.1-alpha - 2014-10-30
1963 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
1964 includes numerous code cleanups and new tests, and fixes a large
1965 number of annoying bugs. Out-of-memory conditions are handled better
1966 than in 0.2.5, pluggable transports have improved proxy support, and
1967 clients now use optimistic data for contacting hidden services. Also,
1968 we are now more robust to changes in what we consider a parseable
1969 directory object, so that tightening restrictions does not have a risk
1970 of introducing infinite download loops.
1972 This is the first alpha release in a new series, so expect there to be
1973 bugs. Users who would rather test out a more stable branch should stay
1974 with 0.2.5.x for now.
1976 o New compiler and system requirements:
1977 - Tor 0.2.6.x requires that your compiler support more of the C99
1978 language standard than before. The 'configure' script now detects
1979 whether your compiler supports C99 mid-block declarations and
1980 designated initializers. If it does not, Tor will not compile.
1982 We may revisit this requirement if it turns out that a significant
1983 number of people need to build Tor with compilers that don't
1984 bother implementing a 15-year-old standard. Closes ticket 13233.
1985 - Tor no longer supports systems without threading support. When we
1986 began working on Tor, there were several systems that didn't have
1987 threads, or where the thread support wasn't able to run the
1988 threads of a single process on multiple CPUs. That no longer
1989 holds: every system where Tor needs to run well now has threading
1990 support. Resolves ticket 12439.
1992 o Removed platform support:
1993 - We no longer include special code to build on Windows CE; as far
1994 as we know, nobody has used Tor on Windows CE in a very long time.
1995 Closes ticket 11446.
1997 o Major features (bridges):
1998 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
1999 transports if they are configured via the "TOR_PT_PROXY"
2000 environment variable. Implements proposal 232. Resolves
2003 o Major features (client performance, hidden services):
2004 - Allow clients to use optimistic data when connecting to a hidden
2005 service, which should remove a round-trip from hidden service
2006 initialization. See proposal 181 for details. Implements
2009 o Major features (directory system):
2010 - Upon receiving an unparseable directory object, if its digest
2011 matches what we expected, then don't try to download it again.
2012 Previously, when we got a descriptor we didn't like, we would keep
2013 trying to download it over and over. Closes ticket 11243.
2015 o Major features (sample torrc):
2016 - Add a new, infrequently-changed "torrc.minimal". This file is
2017 similar to torrc.sample, but it will change as infrequently as
2018 possible, for the benefit of users whose systems prompt them for
2019 intervention whenever a default configuration file is changed.
2020 Making this change allows us to update torrc.sample to be a more
2021 generally useful "sample torrc".
2023 o Major bugfixes (directory authorities):
2024 - Do not assign the HSDir flag to relays if they are not Valid, or
2025 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
2027 o Major bugfixes (directory bandwidth performance):
2028 - Don't flush the zlib buffer aggressively when compressing
2029 directory information for clients. This should save about 7% of
2030 the bandwidth currently used for compressed descriptors and
2031 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
2033 o Minor features (security, memory wiping):
2034 - Ensure we securely wipe keys from memory after
2035 crypto_digest_get_digest and init_curve25519_keypair_from_file
2036 have finished using them. Resolves ticket 13477.
2038 o Minor features (security, out-of-memory handling):
2039 - When handling an out-of-memory condition, allocate less memory for
2040 temporary data structures. Fixes issue 10115.
2041 - When handling an out-of-memory condition, consider more types of
2042 buffers, including those on directory connections, and zlib
2043 buffers. Resolves ticket 11792.
2046 - When identity keypair is generated for first time, log a
2047 congratulatory message that links to the new relay lifecycle
2048 document. Implements feature 10427.
2050 o Minor features (client):
2051 - Clients are now willing to send optimistic data (before they
2052 receive a 'connected' cell) to relays of any version. (Relays
2053 without support for optimistic data are no longer supported on the
2054 Tor network.) Resolves ticket 13153.
2056 o Minor features (directory authorities):
2057 - Don't list relays with a bandwidth estimate of 0 in the consensus.
2058 Implements a feature proposed during discussion of bug 13000.
2059 - In tor-gencert, report an error if the user provides the same
2060 argument more than once.
2061 - If a directory authority can't find a best consensus method in the
2062 votes that it holds, it now falls back to its favorite consensus
2063 method. Previously, it fell back to method 1. Neither of these is
2064 likely to get enough signatures, but "fall back to favorite"
2065 doesn't require us to maintain support an obsolete consensus
2066 method. Implements part of proposal 215.
2068 o Minor features (logging):
2069 - On Unix-like systems, you can now use named pipes as the target of
2070 the Log option, and other options that try to append to files.
2071 Closes ticket 12061. Patch from "carlo von lynX".
2072 - When opening a log file at startup, send it every log message that
2073 we generated between startup and opening it. Previously, log
2074 messages that were generated before opening the log file were only
2075 logged to stdout. Closes ticket 6938.
2076 - Add a TruncateLogFile option to overwrite logs instead of
2077 appending to them. Closes ticket 5583.
2079 o Minor features (portability, Solaris):
2080 - Threads are no longer disabled by default on Solaris; we believe
2081 that the versions of Solaris with broken threading support are all
2082 obsolete by now. Resolves ticket 9495.
2084 o Minor features (relay):
2085 - Re-check our address after we detect a changed IP address from
2086 getsockname(). This ensures that the controller command "GETINFO
2087 address" will report the correct value. Resolves ticket 11582.
2089 - A new AccountingRule option lets Relays set whether they'd like
2090 AccountingMax to be applied separately to inbound and outbound
2091 traffic, or applied to the sum of inbound and outbound traffic.
2092 Resolves ticket 961. Patch by "chobe".
2094 o Minor features (testing networks):
2095 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
2096 the "Exit" flag regardless of their uptime, bandwidth, or exit
2097 policy. TestingTorNetwork must be set for this option to have any
2098 effect. Previously, authorities would take up to 35 minutes to
2099 give nodes the Exit flag in a test network. Partially implements
2102 o Minor features (validation):
2103 - Check all date/time values passed to tor_timegm and
2104 parse_rfc1123_time for validity, taking leap years into account.
2105 Improves HTTP header validation. Implemented with bug 13476.
2106 - In correct_tm(), limit the range of values returned by system
2107 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
2108 This means we don't have to deal with negative or too large dates,
2109 even if a clock is wrong. Otherwise we might fail to read a file
2110 written by us which includes such a date. Fixes bug 13476.
2112 o Minor bugfixes (bridge clients):
2113 - When configured to use a bridge without an identity digest (not
2114 recommended), avoid launching an extra channel to it when
2115 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
2117 o Minor bugfixes (bridges):
2118 - When DisableNetwork is set, do not launch pluggable transport
2119 plugins, and if any are running, terminate them. Fixes bug 13213;
2120 bugfix on 0.2.3.6-alpha.
2122 o Minor bugfixes (C correctness):
2123 - Fix several instances of possible integer overflow/underflow/NaN.
2124 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
2126 - In circuit_build_times_calculate_timeout() in circuitstats.c,
2127 avoid dividing by zero in the pareto calculations. This traps
2128 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
2130 - Fix an integer overflow in format_time_interval(). Fixes bug
2131 13393; bugfix on 0.2.0.10-alpha.
2132 - Set the correct day of year value when the system's localtime(_r)
2133 or gmtime(_r) functions fail to set struct tm. Not externally
2134 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
2135 - Avoid unlikely signed integer overflow in tor_timegm on systems
2136 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
2138 o Minor bugfixes (client):
2139 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
2140 BadExit flag are not considered worthy candidates. Fixes bug
2141 13066; bugfix on 0.1.2.3-alpha.
2142 - Use the consensus schedule for downloading consensuses, and not
2143 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
2144 - Handle unsupported or malformed SOCKS5 requests properly by
2145 responding with the appropriate error message before closing the
2146 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
2148 o Minor bugfixes (client, torrc):
2149 - Stop modifying the value of our DirReqStatistics torrc option just
2150 because we're not a bridge or relay. This bug was causing Tor
2151 Browser users to write "DirReqStatistics 0" in their torrc files
2152 as if they had chosen to change the config. Fixes bug 4244; bugfix
2154 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
2155 that our options have changed every time we SIGHUP. Fixes bug
2156 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
2158 o Minor bugfixes (controller):
2159 - Return an error when the second or later arguments of the
2160 "setevents" controller command are invalid events. Previously we
2161 would return success while silently skipping invalid events. Fixes
2162 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
2164 o Minor bugfixes (directory system):
2165 - Always believe that v3 directory authorities serve extra-info
2166 documents, whether they advertise "caches-extra-info" or not.
2167 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
2168 - When running as a v3 directory authority, advertise that you serve
2169 extra-info documents so that clients who want them can find them
2170 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
2171 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
2172 Previously, directories offering BRIDGE_DIRINFO and some other
2173 flag (i.e. microdescriptors or extrainfo) would be ignored when
2174 looking for bridges. Partially fixes bug 13163; bugfix
2177 o Minor bugfixes (networking):
2178 - Check for orconns and use connection_or_close_for_error() rather
2179 than connection_mark_for_close() directly in the getsockopt()
2180 failure case of connection_handle_write_impl(). Fixes bug 11302;
2181 bugfix on 0.2.4.4-alpha.
2183 o Minor bugfixes (relay):
2184 - When generating our family list, remove spaces from around the
2185 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
2186 - If our previous bandwidth estimate was 0 bytes, allow publishing a
2187 new relay descriptor immediately. Fixes bug 13000; bugfix
2190 o Minor bugfixes (testing networks):
2191 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
2192 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
2193 - Stop using the default authorities in networks which provide both
2194 AlternateDirAuthority and AlternateBridgeAuthority. Partially
2195 fixes bug 13163; bugfix on 0.2.0.13-alpha.
2197 o Minor bugfixes (testing):
2198 - Stop spawn test failures due to a race condition between the
2199 SIGCHLD handler updating the process status, and the test reading
2200 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
2202 o Minor bugfixes (testing, Windows):
2203 - Avoid passing an extra backslash when creating a temporary
2204 directory for running the unit tests on Windows. Fixes bug 12392;
2205 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
2207 o Minor bugfixes (windows):
2208 - Remove code to special-case handling of NTE_BAD_KEYSET when
2209 acquiring windows CryptoAPI context. This error can't actually
2210 occur for the parameters we're providing. Fixes bug 10816; bugfix
2213 o Minor bugfixes (zlib):
2214 - Avoid truncating a zlib stream when trying to finalize it with an
2215 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
2218 - Allow our configure script to build correctly with autoconf 2.62
2219 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
2220 - Improve the error message from ./configure to make it clear that
2221 when asciidoc has not been found, the user will have to either add
2222 --disable-asciidoc argument or install asciidoc. Resolves
2225 o Code simplification and refactoring:
2226 - Change the entry_is_live() function to take named bitfield
2227 elements instead of an unnamed list of booleans. Closes
2229 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
2230 Resolves ticket 12205.
2231 - Use calloc and reallocarray functions instead of multiply-
2232 then-malloc. This makes it less likely for us to fall victim to an
2233 integer overflow attack when allocating. Resolves ticket 12855.
2234 - Use the standard macro name SIZE_MAX, instead of our
2236 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
2237 functions which take them as arguments. Replace 0 with NO_DIRINFO
2238 in a function call for clarity. Seeks to prevent future issues
2240 - Avoid 4 null pointer errors under clang static analysis by using
2241 tor_assert() to prove that the pointers aren't null. Fixes
2243 - Rework the API of policies_parse_exit_policy() to use a bitmask to
2244 represent parsing options, instead of a confusing mess of
2245 booleans. Resolves ticket 8197.
2246 - Introduce a helper function to parse ExitPolicy in
2247 or_options_t structure.
2250 - Add a doc/TUNING document with tips for handling large numbers of
2251 TCP connections when running busy Tor relay. Update the warning
2252 message to point to this file when running out of sockets
2253 operating system is allowing to use simultaneously. Resolves
2257 - We no longer remind the user about configuration options that have
2258 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
2259 - Remove our old, non-weighted bandwidth-based node selection code.
2260 Previously, we used it as a fallback when we couldn't perform
2261 weighted bandwidth-based node selection. But that would only
2262 happen in the cases where we had no consensus, or when we had a
2263 consensus generated by buggy or ancient directory authorities. In
2264 either case, it's better to use the more modern, better maintained
2265 algorithm, with reasonable defaults for the weights. Closes
2267 - Remove the --disable-curve25519 configure option. Relays and
2268 clients now are required to support curve25519 and the
2270 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
2271 used to be deprecated synonyms for "StrictNodes", are now marked
2272 obsolete. Resolves ticket 12226.
2273 - Clients don't understand the BadDirectory flag in the consensus
2274 anymore, and ignore it.
2277 - Refactor the function that chooses guard nodes so that it can more
2278 easily be tested; write some tests for it.
2279 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
2280 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
2281 - Create unit tests for format_time_interval(). With bug 13393.
2282 - Add unit tests for tor_timegm signed overflow, tor_timegm and
2283 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
2284 tests (visible) fixes in bug 13476.
2285 - Add a "coverage-html" make target to generate HTML-visualized
2286 coverage results when building with --enable-coverage. (Requires
2287 lcov.) Patch from Kevin Murray.
2288 - Enable the backtrace handler (where supported) when running the
2290 - Revise all unit tests that used the legacy test_* macros to
2291 instead use the recommended tt_* macros. This patch was generated
2292 with coccinelle, to avoid manual errors. Closes ticket 13119.
2294 o Distribution (systemd):
2295 - systemd unit file: only allow tor to write to /var/lib/tor and
2296 /var/log/tor. The rest of the filesystem is accessible for reading
2297 only. Patch by intrigeri; resolves ticket 12751.
2298 - systemd unit file: ensure that the process and all its children
2299 can never gain new privileges. Patch by intrigeri; resolves
2301 - systemd unit file: set up /var/run/tor as writable for the Tor
2302 service. Patch by intrigeri; resolves ticket 13196.
2304 o Removed features (directory authorities):
2305 - Remove code that prevented authorities from listing Tor relays
2306 affected by CVE-2011-2769 as guards. These relays are already
2307 rejected altogether due to the minimum version requirement of
2308 0.2.3.16-alpha. Closes ticket 13152.
2309 - The "AuthDirRejectUnlisted" option no longer has any effect, as
2310 the fingerprints file (approved-routers) has been deprecated.
2311 - Directory authorities do not support being Naming dirauths anymore.
2312 The "NamingAuthoritativeDir" config option is now obsolete.
2313 - Directory authorities do not support giving out the BadDirectory
2315 - Directory authorities no longer advertise or support consensus
2316 methods 1 through 12 inclusive. These consensus methods were
2317 obsolete and/or insecure: maintaining the ability to support them
2318 served no good purpose. Implements part of proposal 215; closes
2321 o Testing (test-network.sh):
2322 - Stop using "echo -n", as some shells' built-in echo doesn't
2323 support "-n". Instead, use "/bin/echo -n". Partially fixes
2325 - Stop an apparent test-network hang when used with make -j2. Fixes
2327 - Add a --delay option to test-network.sh, which configures the
2328 delay before the chutney network tests for data transmission.
2329 Partially implements ticket 13161.
2332 Changes in version 0.2.5.10 - 2014-10-24
2333 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
2335 It adds several new security features, including improved
2336 denial-of-service resistance for relays, new compiler hardening
2337 options, and a system-call sandbox for hardened installations on Linux
2338 (requires seccomp2). The controller protocol has several new features,
2339 resolving IPv6 addresses should work better than before, and relays
2340 should be a little more CPU-efficient. We've added support for more
2341 OpenBSD and FreeBSD transparent proxy types. We've improved the build
2342 system and testing infrastructure to allow unit testing of more parts
2343 of the Tor codebase. Finally, we've addressed several nagging pluggable
2344 transport usability issues, and included numerous other small bugfixes
2345 and features mentioned below.
2347 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
2348 have accumulated many known flaws; everyone should upgrade.
2350 o Deprecated versions:
2351 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
2352 attention for some while.
2355 Changes in version 0.2.5.9-rc - 2014-10-20
2356 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
2357 series. It disables SSL3 in response to the recent "POODLE" attack
2358 (even though POODLE does not affect Tor). It also works around a crash
2359 bug caused by some operating systems' response to the "POODLE" attack
2360 (which does affect Tor). It also contains a few miscellaneous fixes.
2362 o Major security fixes:
2363 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
2364 today support TLS 1.0 or later, so we can safely turn off support
2365 for this old (and insecure) protocol. Fixes bug 13426.
2367 o Major bugfixes (openssl bug workaround):
2368 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
2369 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
2370 13471. This is a workaround for an OpenSSL bug.
2373 - Disable the sandbox name resolver cache when running tor-resolve:
2374 tor-resolve doesn't use the sandbox code, and turning it on was
2375 breaking attempts to do tor-resolve on a non-default server on
2376 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
2378 o Compilation fixes:
2379 - Build and run correctly on systems like OpenBSD-current that have
2380 patched OpenSSL to remove get_cipher_by_char and/or its
2381 implementations. Fixes issue 13325.
2383 o Downgraded warnings:
2384 - Downgrade the severity of the 'unexpected sendme cell from client'
2385 from 'warn' to 'protocol warning'. Closes ticket 8093.
2388 Changes in version 0.2.4.25 - 2014-10-20
2389 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
2390 (even though POODLE does not affect Tor). It also works around a crash
2391 bug caused by some operating systems' response to the "POODLE" attack
2392 (which does affect Tor).
2394 o Major security fixes (also in 0.2.5.9-rc):
2395 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
2396 today support TLS 1.0 or later, so we can safely turn off support
2397 for this old (and insecure) protocol. Fixes bug 13426.
2399 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
2400 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
2401 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
2402 13471. This is a workaround for an OpenSSL bug.
2405 Changes in version 0.2.5.8-rc - 2014-09-22
2406 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
2407 series. It fixes a bug that affects consistency and speed when
2408 connecting to hidden services, and it updates the location of one of
2409 the directory authorities.
2412 - Clients now send the correct address for their chosen rendezvous
2413 point when trying to access a hidden service. They used to send
2414 the wrong address, which would still work some of the time because
2415 they also sent the identity digest of the rendezvous point, and if
2416 the hidden service happened to try connecting to the rendezvous
2417 point from a relay that already had a connection open to it,
2418 the relay would reuse that connection. Now connections to hidden
2419 services should be more robust and faster. Also, this bug meant
2420 that clients were leaking to the hidden service whether they were
2421 on a little-endian (common) or big-endian (rare) system, which for
2422 some users might have reduced their anonymity. Fixes bug 13151;
2423 bugfix on 0.2.1.5-alpha.
2425 o Directory authority changes:
2426 - Change IP address for gabelmoo (v3 directory authority).
2429 Changes in version 0.2.4.24 - 2014-09-22
2430 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
2431 connecting to hidden services, and it updates the location of one of
2432 the directory authorities.
2435 - Clients now send the correct address for their chosen rendezvous
2436 point when trying to access a hidden service. They used to send
2437 the wrong address, which would still work some of the time because
2438 they also sent the identity digest of the rendezvous point, and if
2439 the hidden service happened to try connecting to the rendezvous
2440 point from a relay that already had a connection open to it,
2441 the relay would reuse that connection. Now connections to hidden
2442 services should be more robust and faster. Also, this bug meant
2443 that clients were leaking to the hidden service whether they were
2444 on a little-endian (common) or big-endian (rare) system, which for
2445 some users might have reduced their anonymity. Fixes bug 13151;
2446 bugfix on 0.2.1.5-alpha.
2448 o Directory authority changes:
2449 - Change IP address for gabelmoo (v3 directory authority).
2451 o Minor features (geoip):
2452 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
2456 Changes in version 0.2.5.7-rc - 2014-09-11
2457 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
2458 release series, and some long-standing bugs related to ORPort reachability
2459 testing and failure to send CREATE cells. It is the first release
2460 candidate for the Tor 0.2.5.x series.
2462 o Major bugfixes (client, startup):
2463 - Start making circuits as soon as DisabledNetwork is turned off.
2464 When Tor started with DisabledNetwork set, it would correctly
2465 conclude that it shouldn't build circuits, but it would mistakenly
2466 cache this conclusion, and continue believing it even when
2467 DisableNetwork is set to 0. Fixes the bug introduced by the fix
2468 for bug 11200; bugfix on 0.2.5.4-alpha.
2469 - Resume expanding abbreviations for command-line options. The fix
2470 for bug 4647 accidentally removed our hack from bug 586 that
2471 rewrote HashedControlPassword to __HashedControlSessionPassword
2472 when it appears on the commandline (which allowed the user to set
2473 her own HashedControlPassword in the torrc file while the
2474 controller generates a fresh session password for each run). Fixes
2475 bug 12948; bugfix on 0.2.5.1-alpha.
2476 - Warn about attempts to run hidden services and relays in the same
2477 process: that's probably not a good idea. Closes ticket 12908.
2479 o Major bugfixes (relay):
2480 - Avoid queuing or sending destroy cells for circuit ID zero when we
2481 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
2482 Found and fixed by "cypherpunks".
2483 - Fix ORPort reachability detection on relays running behind a
2484 proxy, by correctly updating the "local" mark on the controlling
2485 channel when changing the address of an or_connection_t after the
2486 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
2488 o Minor features (bridge):
2489 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
2490 cookie file for the ExtORPort g+r by default.
2492 o Minor features (geoip):
2493 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
2496 o Minor bugfixes (logging):
2497 - Reduce the log severity of the "Pluggable transport proxy does not
2498 provide any needed transports and will not be launched." message,
2499 since Tor Browser includes several ClientTransportPlugin lines in
2500 its torrc-defaults file, leading every Tor Browser user who looks
2501 at her logs to see these notices and wonder if they're dangerous.
2502 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
2503 - Downgrade "Unexpected onionskin length after decryption" warning
2504 to a protocol-warn, since there's nothing relay operators can do
2505 about a client that sends them a malformed create cell. Resolves
2506 bug 12996; bugfix on 0.0.6rc1.
2507 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
2508 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
2509 - When logging information about an EXTEND2 or EXTENDED2 cell, log
2510 their names correctly. Fixes part of bug 12700; bugfix
2512 - When logging information about a relay cell whose command we don't
2513 recognize, log its command as an integer. Fixes part of bug 12700;
2514 bugfix on 0.2.1.10-alpha.
2515 - Escape all strings from the directory connection before logging
2516 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
2518 o Minor bugfixes (controller):
2519 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
2520 bug 12864; bugfix on 0.2.5.1-alpha.
2521 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
2522 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
2525 o Minor bugfixes (compilation):
2526 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
2527 bugfix on 0.2.5.5-alpha.
2528 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
2529 0.2.5.1-alpha. Patch from "NewEraCracker".
2530 - In routerlist_assert_ok(), don't take the address of a
2531 routerinfo's cache_info member unless that routerinfo is non-NULL.
2532 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
2533 - Fix a large number of false positive warnings from the clang
2534 analyzer static analysis tool. This should make real warnings
2535 easier for clang analyzer to find. Patch from "teor". Closes
2538 o Distribution (systemd):
2539 - Verify configuration file via ExecStartPre in the systemd unit
2540 file. Patch from intrigeri; resolves ticket 12730.
2541 - Explicitly disable RunAsDaemon in the systemd unit file. Our
2542 current systemd unit uses "Type = simple", so systemd does not
2543 expect tor to fork. If the user has "RunAsDaemon 1" in their
2544 torrc, then things won't work as expected. This is e.g. the case
2545 on Debian (and derivatives), since there we pass "--defaults-torrc
2546 /usr/share/tor/tor-service-defaults-torrc" (that contains
2547 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
2551 - Adjust the URLs in the README to refer to the new locations of
2552 several documents on the website. Fixes bug 12830. Patch from
2554 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
2558 Changes in version 0.2.5.6-alpha - 2014-07-28
2559 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
2560 risk from guard rotation, and fixes a variety of other issues to get
2561 us closer to a release candidate.
2563 o Major features (also in 0.2.4.23):
2564 - Make the number of entry guards configurable via a new
2565 NumEntryGuards consensus parameter, and the number of directory
2566 guards configurable via a new NumDirectoryGuards consensus
2567 parameter. Implements ticket 12688.
2569 o Major bugfixes (also in 0.2.4.23):
2570 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
2571 implementation that caused incorrect results on 32-bit
2572 implementations when certain malformed inputs were used along with
2573 a small class of private ntor keys. This bug does not currently
2574 appear to allow an attacker to learn private keys or impersonate a
2575 Tor server, but it could provide a means to distinguish 32-bit Tor
2576 implementations from 64-bit Tor implementations. Fixes bug 12694;
2577 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
2581 - Perform circuit cleanup operations even when circuit
2582 construction operations are disabled (because the network is
2583 disabled, or because there isn't enough directory information).
2584 Previously, when we were not building predictive circuits, we
2585 were not closing expired circuits either. Fixes bug 8387; bugfix on
2586 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
2587 became more strict about when we have "enough directory information
2591 - Authorities now assign the Guard flag to the fastest 25% of the
2592 network (it used to be the fastest 50%). Also raise the consensus
2593 weight that guarantees the Guard flag from 250 to 2000. For the
2594 current network, this results in about 1100 guards, down from 2500.
2595 This step paves the way for moving the number of entry guards
2596 down to 1 (proposal 236) while still providing reasonable expected
2597 performance for most users. Implements ticket 12690.
2598 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
2600 - Slightly enhance the diagnostic message for bug 12184.
2602 o Minor bugfixes (also in 0.2.4.23):
2603 - Warn and drop the circuit if we receive an inbound 'relay early'
2604 cell. Those used to be normal to receive on hidden service circuits
2605 due to bug 1038, but the buggy Tor versions are long gone from
2606 the network so we can afford to resume watching for them. Resolves
2607 the rest of bug 1038; bugfix on 0.2.1.19.
2608 - Correct a confusing error message when trying to extend a circuit
2609 via the control protocol but we don't know a descriptor or
2610 microdescriptor for one of the specified relays. Fixes bug 12718;
2611 bugfix on 0.2.3.1-alpha.
2614 - Fix compilation when building with bufferevents enabled. (This
2615 configuration is still not expected to work, however.)
2616 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
2617 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
2619 - Compile correctly with builds and forks of OpenSSL (such as
2620 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
2621 0.2.1.1-alpha. Patch from "dhill".
2624 Changes in version 0.2.4.23 - 2014-07-28
2625 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
2626 guard rotation, and also backports several important fixes from the
2627 Tor 0.2.5 alpha release series.
2630 - Clients now look at the "usecreatefast" consensus parameter to
2631 decide whether to use CREATE_FAST or CREATE cells for the first hop
2632 of their circuit. This approach can improve security on connections
2633 where Tor's circuit handshake is stronger than the available TLS
2634 connection security levels, but the tradeoff is more computational
2635 load on guard relays. Implements proposal 221. Resolves ticket 9386.
2636 - Make the number of entry guards configurable via a new
2637 NumEntryGuards consensus parameter, and the number of directory
2638 guards configurable via a new NumDirectoryGuards consensus
2639 parameter. Implements ticket 12688.
2642 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
2643 implementation that caused incorrect results on 32-bit
2644 implementations when certain malformed inputs were used along with
2645 a small class of private ntor keys. This bug does not currently
2646 appear to allow an attacker to learn private keys or impersonate a
2647 Tor server, but it could provide a means to distinguish 32-bit Tor
2648 implementations from 64-bit Tor implementations. Fixes bug 12694;
2649 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
2653 - Warn and drop the circuit if we receive an inbound 'relay early'
2654 cell. Those used to be normal to receive on hidden service circuits
2655 due to bug 1038, but the buggy Tor versions are long gone from
2656 the network so we can afford to resume watching for them. Resolves
2657 the rest of bug 1038; bugfix on 0.2.1.19.
2658 - Correct a confusing error message when trying to extend a circuit
2659 via the control protocol but we don't know a descriptor or
2660 microdescriptor for one of the specified relays. Fixes bug 12718;
2661 bugfix on 0.2.3.1-alpha.
2662 - Avoid an illegal read from stack when initializing the TLS
2663 module using a version of OpenSSL without all of the ciphers
2664 used by the v2 link handshake. Fixes bug 12227; bugfix on
2665 0.2.4.8-alpha. Found by "starlight".
2668 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
2672 Changes in version 0.2.5.5-alpha - 2014-06-18
2673 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
2674 0.2.5.x release series, including a couple of DoS issues, some
2675 performance regressions, a large number of bugs affecting the Linux
2676 seccomp2 sandbox code, and various other bugfixes. It also adds
2677 diagnostic bugfixes for a few tricky issues that we're trying to
2680 o Major features (security, traffic analysis resistance):
2681 - Several major improvements to the algorithm used to decide when to
2682 close TLS connections. Previous versions of Tor closed connections
2683 at a fixed interval after the last time a non-padding cell was
2684 sent over the connection, regardless of the target of the
2685 connection. Now, we randomize the intervals by adding up to 50% of
2686 their base value, we measure the length of time since connection
2687 last had at least one circuit, and we allow connections to known
2688 ORs to remain open a little longer (15 minutes instead of 3
2689 minutes minimum). These changes should improve Tor's resistance
2690 against some kinds of traffic analysis, and lower some overhead
2691 from needlessly closed connections. Fixes ticket 6799.
2692 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
2694 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
2695 - Fix a memory leak that could occur if a microdescriptor parse
2696 fails during the tokenizing step. This bug could enable a memory
2697 exhaustion attack by directory servers. Fixes bug 11649; bugfix
2700 o Major bugfixes (security, directory authorities):
2701 - Directory authorities now include a digest of each relay's
2702 identity key as a part of its microdescriptor.
2704 This is a workaround for bug 11743 (reported by "cypherpunks"),
2705 where Tor clients do not support receiving multiple
2706 microdescriptors with the same SHA256 digest in the same
2707 consensus. When clients receive a consensus like this, they only
2708 use one of the relays. Without this fix, a hostile relay could
2709 selectively disable some client use of target relays by
2710 constructing a router descriptor with a different identity and the
2711 same microdescriptor parameters and getting the authorities to
2712 list it in a microdescriptor consensus. This fix prevents an
2713 attacker from causing a microdescriptor collision, because the
2714 router's identity is not forgeable.
2716 o Major bugfixes (relay):
2717 - Use a direct dirport connection when uploading non-anonymous
2718 descriptors to the directory authorities. Previously, relays would
2719 incorrectly use tunnel connections under a fairly wide variety of
2720 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
2721 - When a circuit accidentally has the same circuit ID for its
2722 forward and reverse direction, correctly detect the direction of
2723 cells using that circuit. Previously, this bug made roughly one
2724 circuit in a million non-functional. Fixes bug 12195; this is a
2725 bugfix on every version of Tor.
2727 o Major bugfixes (client, pluggable transports):
2728 - When managing pluggable transports, use OS notification facilities
2729 to learn if they have crashed, and don't attempt to kill any
2730 process that has already exited. Fixes bug 8746; bugfix
2733 o Minor features (diagnostic):
2734 - When logging a warning because of bug 7164, additionally check the
2735 hash table for consistency (as proposed on ticket 11737). This may
2736 help diagnose bug 7164.
2737 - When we log a heartbeat, log how many one-hop circuits we have
2738 that are at least 30 minutes old, and log status information about
2739 a few of them. This is an attempt to track down bug 8387.
2740 - When encountering an unexpected CR while writing text to a file on
2741 Windows, log the name of the file. Should help diagnosing
2743 - Give more specific warnings when a client notices that an onion
2744 handshake has failed. Fixes ticket 9635.
2745 - Add significant new logging code to attempt to diagnose bug 12184,
2746 where relays seem to run out of available circuit IDs.
2747 - Improve the diagnostic log message for bug 8387 even further to
2748 try to improve our odds of figuring out why one-hop directory
2749 circuits sometimes do not get closed.
2751 o Minor features (security, memory management):
2752 - Memory allocation tricks (mempools and buffer freelists) are now
2753 disabled by default. You can turn them back on with
2754 --enable-mempools and --enable-buf-freelists respectively. We're
2755 disabling these features because malloc performance is good enough
2756 on most platforms, and a similar feature in OpenSSL exacerbated
2757 exploitation of the Heartbleed attack. Resolves ticket 11476.
2759 o Minor features (security):
2760 - Apply the secure SipHash-2-4 function to the hash table mapping
2761 circuit IDs and channels to circuits. We missed this one when we
2762 were converting all the other hash functions to use SipHash back
2763 in 0.2.5.3-alpha. Resolves ticket 11750.
2765 o Minor features (build):
2766 - The configure script has a --disable-seccomp option to turn off
2767 support for libseccomp on systems that have it, in case it (or
2768 Tor's use of it) is broken. Resolves ticket 11628.
2770 o Minor features (other):
2771 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
2774 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
2775 - When running a hidden service, do not allow TunneledDirConns 0;
2776 this will keep the hidden service from running, and also
2777 make it publish its descriptors directly over HTTP. Fixes bug 10849;
2778 bugfix on 0.2.1.1-alpha.
2780 o Minor bugfixes (performance):
2781 - Avoid a bug where every successful connection made us recompute
2782 the flag telling us whether we have sufficient information to
2783 build circuits. Previously, we would forget our cached value
2784 whenever we successfully opened a channel (or marked a router as
2785 running or not running for any other reason), regardless of
2786 whether we had previously believed the router to be running. This
2787 forced us to run an expensive update operation far too often.
2788 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
2789 - Avoid using tor_memeq() for checking relay cell integrity. This
2790 removes a possible performance bottleneck. Fixes part of bug
2791 12169; bugfix on 0.2.1.31.
2793 o Minor bugfixes (compilation):
2794 - Fix compilation of test_status.c when building with MVSC. Bugfix
2795 on 0.2.5.4-alpha. Patch from Gisle Vanem.
2796 - Resolve GCC complaints on OpenBSD about discarding constness in
2797 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
2798 on 0.1.1.23. Patch from Dana Koch.
2799 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
2800 treatment of long and time_t as comparable types. Fixes part of
2801 bug 11633. Patch from Dana Koch.
2802 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
2803 11623; bugfix on 0.2.5.3-alpha.
2804 - When deciding whether to build the 64-bit curve25519
2805 implementation, detect platforms where we can compile 128-bit
2806 arithmetic but cannot link it. Fixes bug 11729; bugfix on
2807 0.2.4.8-alpha. Patch from "conradev".
2808 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
2809 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
2810 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
2813 o Minor bugfixes (Directory server):
2814 - When sending a compressed set of descriptors or microdescriptors,
2815 make sure to finalize the zlib stream. Previously, we would write
2816 all the compressed data, but if the last descriptor we wanted to
2817 send was missing or too old, we would not mark the stream as
2818 finished. This caused problems for decompression tools. Fixes bug
2819 11648; bugfix on 0.1.1.23.
2821 o Minor bugfixes (Linux seccomp sandbox):
2822 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
2823 11622; bugfix on 0.2.5.1-alpha.
2824 - Avoid crashing when re-opening listener ports with the seccomp
2825 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
2826 - Avoid crashing with the seccomp sandbox enabled along with
2827 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
2828 - When we receive a SIGHUP with the sandbox enabled, correctly
2829 support rotating our log files. Fixes bug 12032; bugfix
2831 - Avoid crash when running with sandboxing enabled and
2832 DirReqStatistics not disabled. Fixes bug 12035; bugfix
2834 - Fix a "BUG" warning when trying to write bridge-stats files with
2835 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
2837 - Prevent the sandbox from crashing on startup when run with the
2838 --enable-expensive-hardening configuration option. Fixes bug
2839 11477; bugfix on 0.2.5.4-alpha.
2840 - When running with DirPortFrontPage and sandboxing both enabled,
2841 reload the DirPortFrontPage correctly when restarting. Fixes bug
2842 12028; bugfix on 0.2.5.1-alpha.
2843 - Don't try to enable the sandbox when using the Tor binary to check
2844 its configuration, hash a passphrase, or so on. Doing so was
2845 crashing on startup for some users. Fixes bug 11609; bugfix
2847 - Avoid warnings when running with sandboxing and node statistics
2848 enabled at the same time. Fixes part of 12064; bugfix on
2849 0.2.5.1-alpha. Patch from Michael Wolf.
2850 - Avoid warnings when running with sandboxing enabled at the same
2851 time as cookie authentication, hidden services, or directory
2852 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
2853 - Do not allow options that require calls to exec to be enabled
2854 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
2855 bug 12043; bugfix on 0.2.5.1-alpha.
2856 - Handle failures in getpwnam()/getpwuid() when running with the
2857 User option set and the Linux syscall sandbox enabled. Fixes bug
2858 11946; bugfix on 0.2.5.1-alpha.
2859 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
2860 to avoid calling getaddrinfo() after installing the sandbox
2861 filters. Previously, it preloaded a cache with the IPv4 address
2862 for our hostname, and nothing else. Now, it loads the cache with
2863 every address that it used to initialize the Tor process. Fixes
2864 bug 11970; bugfix on 0.2.5.1-alpha.
2866 o Minor bugfixes (pluggable transports):
2867 - Enable the ExtORPortCookieAuthFile option, to allow changing the
2868 default location of the authentication token for the extended OR
2869 Port as used by sever-side pluggable transports. We had
2870 implemented this option before, but the code to make it settable
2871 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
2872 - Avoid another 60-second delay when starting Tor in a pluggable-
2873 transport-using configuration when we already have cached
2874 descriptors for our bridges. Fixes bug 11965; bugfix
2877 o Minor bugfixes (client):
2878 - Avoid "Tried to open a socket with DisableNetwork set" warnings
2879 when starting a client with bridges configured and DisableNetwork
2880 set. (Tor launcher starts Tor with DisableNetwork set the first
2881 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
2883 o Minor bugfixes (testing):
2884 - The Python parts of the test scripts now work on Python 3 as well
2885 as Python 2, so systems where '/usr/bin/python' is Python 3 will
2886 no longer have the tests break. Fixes bug 11608; bugfix
2888 - When looking for versions of python that we could run the tests
2889 with, check for "python2.7" and "python3.3"; previously we were
2890 only looking for "python", "python2", and "python3". Patch from
2891 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
2892 - Fix all valgrind warnings produced by the unit tests. There were
2893 over a thousand memory leak warnings previously, mostly produced
2894 by forgetting to free things in the unit test code. Fixes bug
2895 11618, bugfixes on many versions of Tor.
2897 o Minor bugfixes (tor-fw-helper):
2898 - Give a correct log message when tor-fw-helper fails to launch.
2899 (Previously, we would say something like "tor-fw-helper sent us a
2900 string we could not parse".) Fixes bug 9781; bugfix
2903 o Minor bugfixes (relay, threading):
2904 - Check return code on spawn_func() in cpuworker code, so that we
2905 don't think we've spawned a nonworking cpuworker and write junk to
2906 it forever. Fix related to bug 4345; bugfix on all released Tor
2907 versions. Found by "skruffy".
2908 - Use a pthread_attr to make sure that spawn_func() cannot return an
2909 error while at the same time launching a thread. Fix related to
2910 bug 4345; bugfix on all released Tor versions. Reported
2913 o Minor bugfixes (relay, oom prevention):
2914 - Correctly detect the total available system memory. We tried to do
2915 this in 0.2.5.4-alpha, but the code was set up to always return an
2916 error value, even on success. Fixes bug 11805; bugfix
2919 o Minor bugfixes (relay, other):
2920 - We now drop CREATE cells for already-existent circuit IDs and for
2921 zero-valued circuit IDs, regardless of other factors that might
2922 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
2924 - Avoid an illegal read from stack when initializing the TLS module
2925 using a version of OpenSSL without all of the ciphers used by the
2926 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
2928 - When rejecting DATA cells for stream_id zero, still count them
2929 against the circuit's deliver window so that we don't fail to send
2930 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
2932 o Minor bugfixes (logging):
2933 - Fix a misformatted log message about delayed directory fetches.
2934 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
2935 - Squelch a spurious LD_BUG message "No origin circuit for
2936 successful SOCKS stream" in certain hidden service failure cases;
2940 - Include a tor.service file in contrib/dist for use with systemd.
2941 Some distributions will be able to use this file unmodified;
2942 others will need to tweak it, or write their own. Patch from Jamie
2943 Nguyen; resolves ticket 8368.
2946 - Clean up several option names in the manpage to match their real
2947 names, add the missing documentation for a couple of testing and
2948 directory authority options, remove the documentation for a
2949 V2-directory fetching option that no longer exists. Resolves
2951 - Correct the documenation so that it lists the correct directory
2952 for the stats files. (They are in a subdirectory called "stats",
2954 - In the manpage, move more authority-only options into the
2955 directory authority section so that operators of regular directory
2956 caches don't get confused.
2959 - The contrib directory has been sorted and tidied. Before, it was
2960 an unsorted dumping ground for useful and not-so-useful things.
2961 Now, it is divided based on functionality, and the items which
2962 seemed to be nonfunctional or useless have been removed. Resolves
2963 ticket 8966; based on patches from "rl1987".
2966 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
2967 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
2968 - The TunnelDirConns and PreferTunnelledDirConns options no longer
2969 exist; tunneled directory connections have been available since
2970 0.1.2.5-alpha, and turning them off is not a good idea. This is a
2971 brute-force fix for 10849, where "TunnelDirConns 0" would break
2975 Changes in version 0.2.4.22 - 2014-05-16
2976 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
2977 alpha release series. These include blocking all authority signing
2978 keys that may have been affected by the OpenSSL "heartbleed" bug,
2979 choosing a far more secure set of TLS ciphersuites by default, closing
2980 a couple of memory leaks that could be used to run a target relay out
2981 of RAM, and several others.
2983 o Major features (security, backport from 0.2.5.4-alpha):
2984 - Block authority signing keys that were used on authorities
2985 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
2986 don't have any evidence that these keys _were_ compromised; we're
2987 doing this to be prudent.) Resolves ticket 11464.
2989 o Major bugfixes (security, OOM):
2990 - Fix a memory leak that could occur if a microdescriptor parse
2991 fails during the tokenizing step. This bug could enable a memory
2992 exhaustion attack by directory servers. Fixes bug 11649; bugfix
2995 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
2996 - The relay ciphersuite list is now generated automatically based on
2997 uniform criteria, and includes all OpenSSL ciphersuites with
2998 acceptable strength and forward secrecy. Previously, we had left
2999 some perfectly fine ciphersuites unsupported due to omission or
3000 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
3001 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
3002 - Relays now trust themselves to have a better view than clients of
3003 which TLS ciphersuites are better than others. (Thanks to bug
3004 11513, the relay list is now well-considered, whereas the client
3005 list has been chosen mainly for anti-fingerprinting purposes.)
3006 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
3007 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
3008 AES128. Resolves ticket 11528.
3009 - Clients now try to advertise the same list of ciphersuites as
3010 Firefox 28. This change enables selection of (fast) GCM
3011 ciphersuites, disables some strange old ciphers, and stops
3012 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
3013 Resolves ticket 11438.
3015 o Minor bugfixes (configuration, security):
3016 - When running a hidden service, do not allow TunneledDirConns 0:
3017 trying to set that option together with a hidden service would
3018 otherwise prevent the hidden service from running, and also make
3019 it publish its descriptors directly over HTTP. Fixes bug 10849;
3020 bugfix on 0.2.1.1-alpha.
3022 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
3023 - Avoid sending a garbage value to the controller when a circuit is
3024 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
3026 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
3027 - Stop leaking memory when we successfully resolve a PTR record.
3028 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
3030 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
3031 - Avoid 60-second delays in the bootstrapping process when Tor is
3032 launching for a second time while using bridges. Fixes bug 9229;
3033 bugfix on 0.2.0.3-alpha.
3035 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
3036 - Give the correct URL in the warning message when trying to run a
3037 relay on an ancient version of Windows. Fixes bug 9393.
3039 o Minor bugfixes (compilation):
3040 - Fix a compilation error when compiling with --disable-curve25519.
3041 Fixes bug 9700; bugfix on 0.2.4.17-rc.
3044 - Downgrade the warning severity for the the "md was still
3045 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
3046 for trying to diagnose this bug, and the current warning in
3047 earlier versions of tor achieves nothing useful. Addresses warning
3050 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
3051 - When we run out of usable circuit IDs on a channel, log only one
3052 warning for the whole channel, and describe how many circuits
3053 there were on the channel. Fixes part of ticket 11553.
3055 o Minor features (security, backport from 0.2.5.4-alpha):
3056 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
3057 leave the default at 8GBytes), to better support Raspberry Pi
3058 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
3060 o Documentation (backport from 0.2.5.4-alpha):
3061 - Correctly document that we search for a system torrc file before
3062 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
3066 Changes in version 0.2.5.4-alpha - 2014-04-25
3067 Tor 0.2.5.4-alpha includes several security and performance
3068 improvements for clients and relays, including blacklisting authority
3069 signing keys that were used while susceptible to the OpenSSL
3070 "heartbleed" bug, fixing two expensive functions on busy relays,
3071 improved TLS ciphersuite preference lists, support for run-time
3072 hardening on compilers that support AddressSanitizer, and more work on
3073 the Linux sandbox code.
3075 There are also several usability fixes for clients (especially clients
3076 that use bridges), two new TransPort protocols supported (one on
3077 OpenBSD, one on FreeBSD), and various other bugfixes.
3079 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
3080 have accumulated many known flaws; everyone should upgrade.
3082 o Major features (security):
3083 - If you don't specify MaxMemInQueues yourself, Tor now tries to
3084 pick a good value based on your total system memory. Previously,
3085 the default was always 8 GB. You can still override the default by
3086 setting MaxMemInQueues yourself. Resolves ticket 11396.
3087 - Block authority signing keys that were used on authorities
3088 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
3089 don't have any evidence that these keys _were_ compromised; we're
3090 doing this to be prudent.) Resolves ticket 11464.
3092 o Major features (relay performance):
3093 - Speed up server-side lookups of rendezvous and introduction point
3094 circuits by using hashtables instead of linear searches. These
3095 functions previously accounted between 3 and 7% of CPU usage on
3096 some busy relays. Resolves ticket 9841.
3097 - Avoid wasting CPU when extending a circuit over a channel that is
3098 nearly out of circuit IDs. Previously, we would do a linear scan
3099 over possible circuit IDs before finding one or deciding that we
3100 had exhausted our possibilities. Now, we try at most 64 random
3101 circuit IDs before deciding that we probably won't succeed. Fixes
3102 a possible root cause of ticket 11553.
3104 o Major features (seccomp2 sandbox, Linux only):
3105 - The seccomp2 sandbox can now run a test network for multiple hours
3106 without crashing. The sandbox is still experimental, and more bugs
3107 will probably turn up. To try it, enable "Sandbox 1" on a Linux
3108 host. Resolves ticket 11351.
3109 - Strengthen sandbox code: the sandbox can now test the arguments
3110 for rename(), and blocks _sysctl() entirely. Resolves another part
3112 - When the sandbox blocks a system call, it now tries to log a stack
3113 trace before exiting. Resolves ticket 11465.
3115 o Major bugfixes (TLS cipher selection):
3116 - The relay ciphersuite list is now generated automatically based on
3117 uniform criteria, and includes all OpenSSL ciphersuites with
3118 acceptable strength and forward secrecy. Previously, we had left
3119 some perfectly fine ciphersuites unsupported due to omission or
3120 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
3121 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
3122 - Relays now trust themselves to have a better view than clients of
3123 which TLS ciphersuites are better than others. (Thanks to bug
3124 11513, the relay list is now well-considered, whereas the client
3125 list has been chosen mainly for anti-fingerprinting purposes.)
3126 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
3127 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
3128 AES128. Resolves ticket 11528.
3129 - Clients now try to advertise the same list of ciphersuites as
3130 Firefox 28. This change enables selection of (fast) GCM
3131 ciphersuites, disables some strange old ciphers, and stops
3132 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
3133 Resolves ticket 11438.
3135 o Major bugfixes (bridge client):
3136 - Avoid 60-second delays in the bootstrapping process when Tor is
3137 launching for a second time while using bridges. Fixes bug 9229;
3138 bugfix on 0.2.0.3-alpha.
3140 o Minor features (transparent proxy, *BSD):
3141 - Support FreeBSD's ipfw firewall interface for TransPort ports on
3142 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
3143 10267; patch from "yurivict".
3144 - Support OpenBSD's divert-to rules with the pf firewall for
3145 transparent proxy ports. To enable it, set "TransProxyType
3146 pf-divert". This allows Tor to run a TransPort transparent proxy
3147 port on OpenBSD 4.4 or later without root privileges. See the
3148 pf.conf(5) manual page for information on configuring pf to use
3149 divert-to rules. Closes ticket 10896; patch from Dana Koch.
3151 o Minor features (security):
3152 - New --enable-expensive-hardening option to enable security
3153 hardening options that consume nontrivial amounts of CPU and
3154 memory. Right now, this includes AddressSanitizer and UbSan, which
3155 are supported in newer versions of GCC and Clang. Closes ticket
3158 o Minor features (log verbosity):
3159 - Demote the message that we give when a flushing connection times
3160 out for too long from NOTICE to INFO. It was usually meaningless.
3161 Resolves ticket 5286.
3162 - Don't log so many notice-level bootstrapping messages at startup
3163 about downloading descriptors. Previously, we'd log a notice
3164 whenever we learned about more routers. Now, we only log a notice
3165 at every 5% of progress. Fixes bug 9963.
3166 - Warn less verbosely when receiving a malformed
3167 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
3168 - When we run out of usable circuit IDs on a channel, log only one
3169 warning for the whole channel, and describe how many circuits
3170 there were on the channel. Fixes part of ticket 11553.
3172 o Minor features (relay):
3173 - If a circuit timed out for at least 3 minutes, check if we have a
3174 new external IP address, and publish a new descriptor with the new
3175 IP address if it changed. Resolves ticket 2454.
3177 o Minor features (controller):
3178 - Make the entire exit policy available from the control port via
3179 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
3181 - Because of the fix for ticket 11396, the real limit for memory
3182 usage may no longer match the configured MaxMemInQueues value. The
3183 real limit is now exposed via GETINFO limits/max-mem-in-queues.
3185 o Minor features (bridge client):
3186 - Report a more useful failure message when we can't connect to a
3187 bridge because we don't have the right pluggable transport
3188 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
3190 o Minor features (diagnostic):
3191 - Add more log messages to diagnose bug 7164, which causes
3192 intermittent "microdesc_free() called but md was still referenced"
3193 warnings. We now include more information, to figure out why we
3194 might be cleaning a microdescriptor for being too old if it's
3195 still referenced by a live node_t object.
3197 o Minor bugfixes (client, DNSPort):
3198 - When using DNSPort, try to respond to AAAA requests with AAAA
3199 answers. Previously, we hadn't looked at the request type when
3200 deciding which answer type to prefer. Fixes bug 10468; bugfix on
3202 - When receiving a DNS query for an unsupported record type, reply
3203 with no answer rather than with a NOTIMPL error. This behavior
3204 isn't correct either, but it will break fewer client programs, we
3205 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
3208 o Minor bugfixes (exit relay):
3209 - Stop leaking memory when we successfully resolve a PTR record.
3210 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
3212 o Minor bugfixes (bridge client):
3213 - Stop accepting bridge lines containing hostnames. Doing so would
3214 cause clients to perform DNS requests on the hostnames, which was
3215 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
3216 - Avoid a 60-second delay in the bootstrapping process when a Tor
3217 client with pluggable transports re-reads its configuration at
3218 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
3220 o Minor bugfixes (client, logging during bootstrap):
3221 - Warn only once if we start logging in an unsafe way. Previously,
3222 we complain as many times as we had problems. Fixes bug 9870;
3223 bugfix on 0.2.5.1-alpha.
3224 - Only report the first fatal bootstrap error on a given OR
3225 connection. This stops us from telling the controller bogus error
3226 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
3227 - Be more helpful when trying to run sandboxed on Linux without
3228 libseccomp. Instead of saying "Sandbox is not implemented on this
3229 platform", we now explain that we need to be built with
3230 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
3231 - Avoid generating spurious warnings when starting with
3232 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
3235 o Minor bugfixes (closing OR connections):
3236 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
3237 check if it's an or_connection_t and correctly call
3238 connection_or_close_for_error() rather than
3239 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
3241 - When closing all connections on setting DisableNetwork to 1, use
3242 connection_or_close_normally() rather than closing OR connections
3243 out from under the channel layer. Fixes bug 11306; bugfix on
3246 o Minor bugfixes (controller):
3247 - Avoid sending a garbage value to the controller when a circuit is
3248 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
3250 o Minor bugfixes (tor-fw-helper):
3251 - Allow tor-fw-helper to build again by adding src/ext to its
3252 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
3254 o Minor bugfixes (bridges):
3255 - Avoid potential crashes or bad behavior when launching a
3256 server-side managed proxy with ORPort or ExtORPort temporarily
3257 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
3259 o Minor bugfixes (platform-specific):
3260 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
3261 bug 11426; bugfix on 0.2.5.3-alpha.
3262 - When dumping a malformed directory object to disk, save it in
3263 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
3265 - Don't report failures from make_socket_reuseable() on incoming
3266 sockets on OSX: this can happen when incoming connections close
3267 early. Fixes bug 10081.
3269 o Minor bugfixes (trivial memory leaks):
3270 - Fix a small memory leak when signing a directory object. Fixes bug
3271 11275; bugfix on 0.2.4.13-alpha.
3272 - Free placeholder entries in our circuit table at exit; fixes a
3273 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
3274 - Don't re-initialize a second set of OpenSSL mutexes when starting
3275 up. Previously, we'd make one set of mutexes, and then immediately
3276 replace them with another. Fixes bug 11726; bugfix on
3278 - Resolve some memory leaks found by coverity in the unit tests, on
3279 exit in tor-gencert, and on a failure to compute digests for our
3280 own keys when generating a v3 networkstatus vote. These leaks
3281 should never have affected anyone in practice.
3283 o Minor bugfixes (hidden service):
3284 - Only retry attempts to connect to a chosen rendezvous point 8
3285 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
3287 o Minor bugfixes (misc code correctness):
3288 - Fix various instances of undefined behavior in channeltls.c,
3289 tor_memmem(), and eventdns.c that would cause us to construct
3290 pointers to memory outside an allocated object. (These invalid
3291 pointers were not accessed, but C does not even allow them to
3292 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
3293 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
3294 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
3295 fix some miscellaneous errors in our tests and codebase. Fixes bug
3296 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
3297 - Always check return values for unlink, munmap, UnmapViewOfFile;
3298 check strftime return values more often. In some cases all we can
3299 do is report a warning, but this may help prevent deeper bugs from
3300 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
3302 - Fix numerous warnings from the clang "scan-build" static analyzer.
3303 Some of these are programming style issues; some of them are false
3304 positives that indicated awkward code; some are undefined behavior
3305 cases related to constructing (but not using) invalid pointers;
3306 some are assumptions about API behavior; some are (harmlessly)
3307 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
3308 correct; and one or two are genuine bugs that weren't reachable
3309 from the rest of the program. Fixes bug 8793; bugfixes on many,
3313 - Build the torify.1 manpage again. Previously, we were only trying
3314 to build it when also building tor-fw-helper. That's why we didn't
3315 notice that we'd broken the ability to build it. Fixes bug 11321;
3316 bugfix on 0.2.5.1-alpha.
3317 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
3318 11061; bugfix on 0.2.4.7-alpha.
3319 - Correctly document that we search for a system torrc file before
3320 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
3322 - Resolve warnings from Doxygen.
3324 o Code simplifications and refactoring:
3325 - Remove is_internal_IP() function. Resolves ticket 4645.
3326 - Remove unused function circuit_dump_by_chan from circuitlist.c.
3327 Closes issue 9107; patch from "marek".
3328 - Change our use of the ENUM_BF macro to avoid declarations that
3331 o Deprecated versions:
3332 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
3333 attention for some while. Directory authorities no longer accept
3334 descriptors from relays running any version of Tor prior to Tor
3335 0.2.3.16-alpha. Resolves ticket 11149.
3338 - New macros in test.h to simplify writing mock-functions for unit
3339 tests. Part of ticket 11507. Patch from Dana Koch.
3340 - Complete tests for the status.c module. Resolves ticket 11507.
3341 Patch from Dana Koch.
3344 - Remove all code for the long unused v1 directory protocol.
3345 Resolves ticket 11070.
3348 Changes in version 0.2.5.3-alpha - 2014-03-22
3349 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
3350 two new anti-DoS features for Tor relays, resolves a bug that kept
3351 SOCKS5 support for IPv6 from working, fixes several annoying usability
3352 issues for bridge users, and removes more old code for unused
3355 The Tor 0.2.5.x release series is now in patch-freeze: no feature
3356 patches not already written will be considered for inclusion in 0.2.5.x.
3358 o Major features (relay security, DoS-resistance):
3359 - When deciding whether we have run out of memory and we need to
3360 close circuits, also consider memory allocated in buffers for
3361 streams attached to each circuit.
3363 This change, which extends an anti-DoS feature introduced in
3364 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
3365 better resist more memory-based DoS attacks than before. Since the
3366 MaxMemInCellQueues option now applies to all queues, it is renamed
3367 to MaxMemInQueues. This feature fixes bug 10169.
3368 - Avoid hash-flooding denial-of-service attacks by using the secure
3369 SipHash-2-4 hash function for our hashtables. Without this
3370 feature, an attacker could degrade performance of a targeted
3371 client or server by flooding their data structures with a large
3372 number of entries to be stored at the same hash table position,
3373 thereby slowing down the Tor instance. With this feature, hash
3374 table positions are derived from a randomized cryptographic key,
3375 and an attacker cannot predict which entries will collide. Closes
3377 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
3378 the default at 8GBytes), to better support Raspberry Pi users. Fixes
3379 bug 9686; bugfix on 0.2.4.14-alpha.
3381 o Minor features (bridges, pluggable transports):
3382 - Bridges now write the SHA1 digest of their identity key
3383 fingerprint (that is, a hash of a hash of their public key) to
3384 notice-level logs, and to a new hashed-fingerprint file. This
3385 information will help bridge operators look up their bridge in
3386 Globe and similar tools. Resolves ticket 10884.
3387 - Improve the message that Tor displays when running as a bridge
3388 using pluggable transports without an Extended ORPort listener.
3389 Also, log the message in the log file too. Resolves ticket 11043.
3391 o Minor features (other):
3392 - Add a new option, PredictedPortsRelevanceTime, to control how long
3393 after having received a request to connect to a given port Tor
3394 will try to keep circuits ready in anticipation of future requests
3395 for that port. Patch from "unixninja92"; implements ticket 9176.
3396 - Generate a warning if any ports are listed in the SocksPolicy,
3397 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
3398 AuthDirBadExit options. (These options only support address
3399 ranges.) Fixes part of ticket 11108.
3400 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
3403 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
3404 - Build without warnings under clang 3.4. (We have some macros that
3405 define static functions only some of which will get used later in
3406 the module. Starting with clang 3.4, these give a warning unless the
3407 unused attribute is set on them.) Resolves ticket 10904.
3408 - Fix build warnings about missing "a2x" comment when building the
3409 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
3410 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
3412 o Minor bugfixes (client):
3413 - Improve the log message when we can't connect to a hidden service
3414 because all of the hidden service directory nodes hosting its
3415 descriptor are excluded. Improves on our fix for bug 10722, which
3416 was a bugfix on 0.2.0.10-alpha.
3417 - Raise a control port warning when we fail to connect to all of
3418 our bridges. Previously, we didn't inform the controller, and
3419 the bootstrap process would stall. Fixes bug 11069; bugfix on
3421 - Exit immediately when a process-owning controller exits.
3422 Previously, tor relays would wait for a little while after their
3423 controller exited, as if they had gotten an INT signal -- but this
3424 was problematic, since there was no feedback for the user. To do a
3425 clean shutdown, controllers should send an INT signal and give Tor
3426 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
3427 - Stop attempting to connect to bridges before our pluggable
3428 transports are configured (harmless but resulted in some erroneous
3429 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
3430 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
3431 generating incorrect SOCKS5 responses, and confusing client
3432 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
3434 o Minor bugfixes (relays and bridges):
3435 - Avoid crashing on a malformed resolv.conf file when running a
3436 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
3437 - Non-exit relays no longer launch mock DNS requests to check for
3438 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
3439 non-exit relays stopped servicing DNS requests. Fixes bug 965;
3440 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
3441 - Bridges now report complete directory request statistics. Related
3442 to bug 5824; bugfix on 0.2.2.1-alpha.
3443 - Bridges now never collect statistics that were designed for
3444 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
3445 - Stop giving annoying warning messages when we decide not to launch
3446 a pluggable transport proxy that we don't need (because there are
3447 no bridges configured to use it). Resolves ticket 5018; bugfix
3449 - Give the correct URL in the warning message when trying to run a
3450 relay on an ancient version of Windows. Fixes bug 9393.
3452 o Minor bugfixes (backtrace support):
3453 - Support automatic backtraces on more platforms by using the
3454 "-fasynchronous-unwind-tables" compiler option. This option is
3455 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
3456 is on by default and table generation is not. This doesn't yet
3457 add Windows support; only Linux, OSX, and some BSDs are affected.
3458 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
3459 - Avoid strange behavior if two threads hit failed assertions at the
3460 same time and both try to log backtraces at once. (Previously, if
3461 this had happened, both threads would have stored their intermediate
3462 results in the same buffer, and generated junk outputs.) Reported by
3463 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
3464 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
3465 0.2.5.2-alpha; patch from Nick Hopper.
3467 o Minor bugfixes (unit tests):
3468 - Fix a small bug in the unit tests that might have made the tests
3469 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
3470 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
3473 - Remove all remaining code related to version-0 hidden service
3474 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
3475 the rest of bug 10841.
3478 - Document in the manpage that "KBytes" may also be written as
3479 "kilobytes" or "KB", that "Kbits" may also be written as
3480 "kilobits", and so forth. Closes ticket 9222.
3481 - Document that the ClientOnly config option overrides ORPort.
3482 Our old explanation made ClientOnly sound as though it did
3483 nothing at all. Resolves bug 9059.
3484 - Explain that SocksPolicy, DirPolicy, and similar options don't
3485 take port arguments. Fixes the other part of ticket 11108.
3486 - Fix a comment about the rend_server_descriptor_t.protocols field
3487 to more accurately describe its range. Also, make that field
3488 unsigned, to more accurately reflect its usage. Fixes bug 9099;
3489 bugfix on 0.2.1.5-alpha.
3490 - Fix the manpage's description of HiddenServiceAuthorizeClient:
3491 the maximum client name length is 16, not 19. Fixes bug 11118;
3492 bugfix on 0.2.1.6-alpha.
3494 o Code simplifications and refactoring:
3495 - Get rid of router->address, since in all cases it was just the
3496 string representation of router->addr. Resolves ticket 5528.
3498 o Test infrastructure:
3499 - Update to the latest version of tinytest.
3500 - Improve the tinytest implementation of string operation tests so
3501 that comparisons with NULL strings no longer crash the tests; they
3502 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
3505 Changes in version 0.2.4.21 - 2014-02-28
3506 Tor 0.2.4.21 further improves security against potential adversaries who
3507 find breaking 1024-bit crypto doable, and backports several stability
3508 and robustness patches from the 0.2.5 branch.
3510 o Major features (client security):
3511 - When we choose a path for a 3-hop circuit, make sure it contains
3512 at least one relay that supports the NTor circuit extension
3513 handshake. Otherwise, there is a chance that we're building
3514 a circuit that's worth attacking by an adversary who finds
3515 breaking 1024-bit crypto doable, and that chance changes the game
3516 theory. Implements ticket 9777.
3519 - Do not treat streams that fail with reason
3520 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
3521 since it could also indicate an ENETUNREACH connection error. Fixes
3522 part of bug 10777; bugfix on 0.2.4.8-alpha.
3524 o Code simplification and refactoring:
3525 - Remove data structures which were introduced to implement the
3526 CellStatistics option: they are now redundant with the new timestamp
3527 field in the regular packed_cell_t data structure, which we did
3528 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
3531 - Always clear OpenSSL bignums before freeing them -- even bignums
3532 that don't contain secrets. Resolves ticket 10793. Patch by
3534 - Build without warnings under clang 3.4. (We have some macros that
3535 define static functions only some of which will get used later in
3536 the module. Starting with clang 3.4, these give a warning unless the
3537 unused attribute is set on them.) Resolves ticket 10904.
3538 - Update geoip and geoip6 files to the February 7 2014 Maxmind
3539 GeoLite2 Country database.
3542 - Set the listen() backlog limit to the largest actually supported
3543 on the system, not to the value in a header file. Fixes bug 9716;
3544 bugfix on every released Tor.
3545 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
3546 exit node as a NOROUTE error, not an INTERNAL error, since they
3547 can apparently happen when trying to connect to the wrong sort
3548 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
3549 - Fix build warnings about missing "a2x" comment when building the
3550 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
3551 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
3552 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
3553 not entirely remove it from the connection lists. Fixes bug 9602;
3554 bugfix on 0.2.4.4-alpha.
3555 - Fix a segmentation fault in our benchmark code when running with
3556 Fedora's OpenSSL package, or any other OpenSSL that provides
3557 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
3558 - Turn "circuit handshake stats since last time" log messages into a
3559 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
3561 o Documentation fixes:
3562 - Document that all but one DirPort entry must have the NoAdvertise
3563 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
3566 Changes in version 0.2.5.2-alpha - 2014-02-13
3567 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
3568 like the "poor random number generation" fix and the "building too many
3569 circuits" fix. It also further improves security against potential
3570 adversaries who find breaking 1024-bit crypto doable, and launches
3571 pluggable transports on demand (which gets us closer to integrating
3572 pluggable transport support by default -- not to be confused with Tor
3573 bundles enabling pluggable transports and bridges by default).
3575 o Major features (client security):
3576 - When we choose a path for a 3-hop circuit, make sure it contains
3577 at least one relay that supports the NTor circuit extension
3578 handshake. Otherwise, there is a chance that we're building
3579 a circuit that's worth attacking by an adversary who finds
3580 breaking 1024-bit crypto doable, and that chance changes the game
3581 theory. Implements ticket 9777.
3582 - Clients now look at the "usecreatefast" consensus parameter to
3583 decide whether to use CREATE_FAST or CREATE cells for the first hop
3584 of their circuit. This approach can improve security on connections
3585 where Tor's circuit handshake is stronger than the available TLS
3586 connection security levels, but the tradeoff is more computational
3587 load on guard relays. Implements proposal 221. Resolves ticket 9386.
3589 o Major features (bridges):
3590 - Don't launch pluggable transport proxies if we don't have any
3591 bridges configured that would use them. Now we can list many
3592 pluggable transports, and Tor will dynamically start one when it
3593 hears a bridge address that needs it. Resolves ticket 5018.
3594 - The bridge directory authority now assigns status flags (Stable,
3595 Guard, etc) to bridges based on thresholds calculated over all
3596 Running bridges. Now bridgedb can finally make use of its features
3597 to e.g. include at least one Stable bridge in its answers. Fixes
3600 o Major features (other):
3601 - Extend ORCONN controller event to include an "ID" parameter,
3602 and add four new controller event types CONN_BW, CIRC_BW,
3603 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
3604 The new events are emitted in private Tor networks only, with the
3605 goal of being able to better track performance and load during
3606 full-network simulations. Implements proposal 218 and ticket 7359.
3607 - On some platforms (currently: recent OSX versions, glibc-based
3608 platforms that support the ELF format, and a few other
3609 Unix-like operating systems), Tor can now dump stack traces
3610 when a crash occurs or an assertion fails. By default, traces
3611 are dumped to stderr (if possible) and to any logs that are
3612 reporting errors. Implements ticket 9299.
3615 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
3616 not entirely remove it from the connection lists. Fixes bug 9602;
3617 bugfix on 0.2.4.4-alpha.
3618 - Do not treat streams that fail with reason
3619 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
3620 since it could also indicate an ENETUNREACH connection error. Fixes
3621 part of bug 10777; bugfix on 0.2.4.8-alpha.
3623 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
3624 - Do not allow OpenSSL engines to replace the PRNG, even when
3625 HardwareAccel is set. The only default builtin PRNG engine uses
3626 the Intel RDRAND instruction to replace the entire PRNG, and
3627 ignores all attempts to seed it with more entropy. That's
3628 cryptographically stupid: the right response to a new alleged
3629 entropy source is never to discard all previously used entropy
3630 sources. Fixes bug 10402; works around behavior introduced in
3631 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
3633 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
3634 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
3635 - Avoid launching spurious extra circuits when a stream is pending.
3636 This fixes a bug where any circuit that _wasn't_ unusable for new
3637 streams would be treated as if it were, causing extra circuits to
3638 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
3640 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3641 - No longer stop reading or writing on cpuworker connections when
3642 our rate limiting buckets go empty. Now we should handle circuit
3643 handshake requests more promptly. Resolves bug 9731.
3644 - Stop trying to bootstrap all our directory information from
3645 only our first guard. Discovered while fixing bug 9946; bugfix
3648 o Minor features (bridges, pluggable transports):
3649 - Add threshold cutoffs to the networkstatus document created by
3650 the Bridge Authority. Fixes bug 1117.
3651 - On Windows, spawn background processes using the CREATE_NO_WINDOW
3652 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
3653 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
3654 Vidalia set this option for us.) Implements ticket 10297.
3656 o Minor features (security):
3657 - Always clear OpenSSL bignums before freeing them -- even bignums
3658 that don't contain secrets. Resolves ticket 10793. Patch by
3661 o Minor features (config options and command line):
3662 - Add an --allow-missing-torrc commandline option that tells Tor to
3663 run even if the configuration file specified by -f is not available.
3664 Implements ticket 10060.
3665 - Add support for the TPROXY transparent proxying facility on Linux.
3666 See documentation for the new TransProxyType option for more
3667 details. Implementation by "thomo". Closes ticket 10582.
3669 o Minor features (controller):
3670 - Add a new "HS_DESC" controller event that reports activities
3671 related to hidden service descriptors. Resolves ticket 8510.
3672 - New "DROPGUARDS" controller command to forget all current entry
3673 guards. Not recommended for ordinary use, since replacing guards
3674 too frequently makes several attacks easier. Resolves ticket 9934;
3677 o Minor features (build):
3678 - Assume that a user using ./configure --host wants to cross-compile,
3679 and give an error if we cannot find a properly named
3680 tool-chain. Add a --disable-tool-name-check option to proceed
3681 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
3682 - If we run ./configure and the compiler recognizes -fstack-protector
3683 but the linker rejects it, warn the user about a potentially missing
3684 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
3686 o Minor features (testing):
3687 - If Python is installed, "make check" now runs extra tests beyond
3688 the unit test scripts.
3689 - When bootstrapping a test network, sometimes very few relays get
3690 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
3691 specify a set of relays which should be voted Guard regardless of
3692 their uptime or bandwidth. Addresses ticket 9206.
3694 o Minor features (log messages):
3695 - When ServerTransportPlugin is set on a bridge, Tor can write more
3696 useful statistics about bridge use in its extrainfo descriptors,
3697 but only if the Extended ORPort ("ExtORPort") is set too. Add a
3698 log message to inform the user in this case. Resolves ticket 9651.
3699 - When receiving a new controller connection, log the origin address.
3700 Resolves ticket 9698; patch from "sigpipe".
3701 - When logging OpenSSL engine status at startup, log the status of
3702 more engines. Fixes ticket 10043; patch from Joshua Datko.
3703 - Turn "circuit handshake stats since last time" log messages into a
3704 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
3706 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3707 - Improve the circuit queue out-of-memory handler. Previously, when
3708 we ran low on memory, we'd close whichever circuits had the most
3709 queued cells. Now, we close those that have the *oldest* queued
3710 cells, on the theory that those are most responsible for us
3711 running low on memory. Based on analysis from a forthcoming paper
3712 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
3713 - Generate bootstrapping status update events correctly when fetching
3714 microdescriptors. Fixes bug 9927.
3715 - Update to the October 2 2013 Maxmind GeoLite Country database.
3717 o Minor bugfixes (clients):
3718 - When closing a channel that has already been open, do not close
3719 pending circuits that were waiting to connect to the same relay.
3720 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
3723 o Minor bugfixes (relays):
3724 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
3725 exit node as a NOROUTE error, not an INTERNAL error, since they
3726 can apparently happen when trying to connect to the wrong sort
3727 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
3729 o Minor bugfixes (bridges):
3730 - Fix a bug where the first connection works to a bridge that uses a
3731 pluggable transport with client-side parameters, but we don't send
3732 the client-side parameters on subsequent connections. (We don't
3733 use any pluggable transports with client-side parameters yet,
3734 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
3735 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
3737 o Minor bugfixes (node selection):
3738 - If ExcludeNodes is set, consider non-excluded hidden service
3739 directory servers before excluded ones. Do not consider excluded
3740 hidden service directory servers at all if StrictNodes is
3741 set. (Previously, we would sometimes decide to connect to those
3742 servers, and then realize before we initiated a connection that
3743 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
3745 - If we set the ExitNodes option but it doesn't include any nodes
3746 that have the Exit flag, we would choose not to bootstrap. Now we
3747 bootstrap so long as ExitNodes includes nodes which can exit to
3748 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
3750 o Minor bugfixes (controller and command-line):
3751 - If changing a config option via "setconf" fails in a recoverable
3752 way, we used to nonetheless write our new control ports to the
3753 file described by the "ControlPortWriteToFile" option. Now we only
3754 write out that file if we successfully switch to the new config
3755 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
3756 - When a command-line option such as --version or --help that
3757 ordinarily implies --hush appears on the command line along with
3758 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
3759 only if it appeared later on the command line. Fixes bug 9578;
3760 bugfix on 0.2.5.1-alpha.
3762 o Minor bugfixes (code correctness):
3763 - Previously we used two temporary files when writing descriptors to
3764 disk; now we only use one. Fixes bug 1376.
3765 - Remove an erroneous (but impossible and thus harmless) pointer
3766 comparison that would have allowed compilers to skip a bounds
3767 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
3768 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
3769 - Fix an always-true assertion in pluggable transports code so it
3770 actually checks what it was trying to check. Fixes bug 10046;
3771 bugfix on 0.2.3.9-alpha. Found by "dcb".
3773 o Minor bugfixes (protocol correctness):
3774 - When receiving a VERSIONS cell with an odd number of bytes, close
3775 the connection immediately since the cell is malformed. Fixes bug
3776 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
3779 o Minor bugfixes (build):
3780 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
3781 turned off (that is, without support for v2 link handshakes). Fixes
3782 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
3783 - Fix compilation warnings and startup issues when running with
3784 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
3786 - Fix compilation on Solaris 9, which didn't like us having an
3787 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
3789 o Minor bugfixes (testing):
3790 - Fix a segmentation fault in our benchmark code when running with
3791 Fedora's OpenSSL package, or any other OpenSSL that provides
3792 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
3794 o Minor bugfixes (log messages):
3795 - Fix a bug where clients using bridges would report themselves
3796 as 50% bootstrapped even without a live consensus document.
3797 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
3798 - Suppress a warning where, if there's only one directory authority
3799 in the network, we would complain that votes and signatures cannot
3800 be uploaded to other directory authorities. Fixes bug 10842;
3801 bugfix on 0.2.2.26-beta.
3802 - Report bootstrapping progress correctly when we're downloading
3803 microdescriptors. We had updated our "do we have enough microdescs
3804 to begin building circuits?" logic most recently in 0.2.4.10-alpha
3805 (see bug 5956), but we left the bootstrap status event logic at
3806 "how far through getting 1/4 of them are we?" Fixes bug 9958;
3807 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
3809 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
3810 - Avoid a crash bug when starting with a corrupted microdescriptor
3811 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
3812 - If we fail to dump a previously cached microdescriptor to disk, avoid
3813 freeing duplicate data later on. Fixes bug 10423; bugfix on
3814 0.2.4.13-alpha. Spotted by "bobnomnom".
3816 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3817 - Correctly log long IPv6 exit policies, instead of truncating them
3818 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
3819 - Our default TLS ecdhe groups were backwards: we meant to be using
3820 P224 for relays (for performance win) and P256 for bridges (since
3821 it is more common in the wild). Instead we had it backwards. After
3822 reconsideration, we decided that the default should be P256 on all
3823 hosts, since its security is probably better, and since P224 is
3824 reportedly used quite little in the wild. Found by "skruffy" on
3825 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
3826 - Free directory authority certificate download statuses on exit
3827 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
3829 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3830 - If the guard we choose first doesn't answer, we would try the
3831 second guard, but once we connected to the second guard we would
3832 abandon it and retry the first one, slowing down bootstrapping.
3833 The fix is to treat all our initially chosen guards as acceptable
3834 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
3835 - Fix an assertion failure that would occur when disabling the
3836 ORPort setting on a running Tor process while accounting was
3837 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
3838 - When examining the list of network interfaces to find our address,
3839 do not consider non-running or disabled network interfaces. Fixes
3840 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
3841 - Avoid an off-by-one error when checking buffer boundaries when
3842 formatting the exit status of a pluggable transport helper.
3843 This is probably not an exploitable bug, but better safe than
3844 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
3847 o Removed code and features:
3848 - Clients now reject any directory authority certificates lacking
3849 a dir-key-crosscert element. These have been included since
3850 0.2.1.9-alpha, so there's no real reason for them to be optional
3851 any longer. Completes proposal 157. Resolves ticket 10162.
3852 - Remove all code that existed to support the v2 directory system,
3853 since there are no longer any v2 directory authorities. Resolves
3855 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
3856 options, which were used for designating authorities as "Hidden
3857 service authorities". There has been no use of hidden service
3858 authorities since 0.2.2.1-alpha, when we stopped uploading or
3859 downloading v0 hidden service descriptors. Fixes bug 10881; also
3860 part of a fix for bug 10841.
3862 o Code simplification and refactoring:
3863 - Remove some old fallback code designed to keep Tor clients working
3864 in a network with only two working relays. Elsewhere in the code we
3865 have long since stopped supporting such networks, so there wasn't
3866 much point in keeping it around. Addresses ticket 9926.
3867 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
3868 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
3869 - Remove data structures which were introduced to implement the
3870 CellStatistics option: they are now redundant with the addition
3871 of a timestamp to the regular packed_cell_t data structure, which
3872 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
3875 o Documentation (man page) fixes:
3876 - Update manpage to describe some of the files you can expect to
3877 find in Tor's DataDirectory. Addresses ticket 9839.
3878 - Document that all but one DirPort entry must have the NoAdvertise
3879 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
3881 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3882 - Clarify the usage and risks of setting the ContactInfo torrc line
3883 for your relay or bridge. Resolves ticket 9854.
3884 - Add anchors to the manpage so we can link to the html version of
3885 the documentation for specific options. Resolves ticket 9866.
3886 - Replace remaining references to DirServer in man page and
3887 log entries. Resolves ticket 10124.
3890 - Make the "tor-gencert" tool used by directory authority operators
3891 create 2048-bit signing keys by default (rather than 1024-bit, since
3892 1024-bit is uncomfortably small these days). Addresses ticket 10324.
3895 Changes in version 0.2.4.20 - 2013-12-22
3896 Tor 0.2.4.20 fixes potentially poor random number generation for users
3897 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
3898 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
3899 and 4) have no state file in their DataDirectory (as would happen on
3900 first start). Users who generated relay or hidden service identity
3901 keys in such a situation should discard them and generate new ones.
3903 This release also fixes a logic error that caused Tor clients to build
3904 many more preemptive circuits than they actually need.
3907 - Do not allow OpenSSL engines to replace the PRNG, even when
3908 HardwareAccel is set. The only default builtin PRNG engine uses
3909 the Intel RDRAND instruction to replace the entire PRNG, and
3910 ignores all attempts to seed it with more entropy. That's
3911 cryptographically stupid: the right response to a new alleged
3912 entropy source is never to discard all previously used entropy
3913 sources. Fixes bug 10402; works around behavior introduced in
3914 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
3916 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
3917 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
3918 - Avoid launching spurious extra circuits when a stream is pending.
3919 This fixes a bug where any circuit that _wasn't_ unusable for new
3920 streams would be treated as if it were, causing extra circuits to
3921 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
3924 - Avoid a crash bug when starting with a corrupted microdescriptor
3925 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
3926 - If we fail to dump a previously cached microdescriptor to disk, avoid
3927 freeing duplicate data later on. Fixes bug 10423; bugfix on
3928 0.2.4.13-alpha. Spotted by "bobnomnom".
3931 Changes in version 0.2.4.19 - 2013-12-11
3932 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
3933 (1986-2013). Aaron worked on diverse projects including helping to guide
3934 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
3935 transparency to the U.S government's PACER documents, and contributing
3936 design and development for Tor and Tor2Web. Aaron was one of the latest
3937 martyrs in our collective fight for civil liberties and human rights,
3938 and his death is all the more painful because he was one of us.
3940 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
3941 a new circuit handshake and link encryption that use ECC to provide
3942 better security and efficiency; makes relays better manage circuit
3943 creation requests; uses "directory guards" to reduce client enumeration
3944 risks; makes bridges collect and report statistics about the pluggable
3945 transports they support; cleans up and improves our geoip database;
3946 gets much closer to IPv6 support for clients, bridges, and relays; makes
3947 directory authorities use measured bandwidths rather than advertised
3948 ones when computing flags and thresholds; disables client-side DNS
3949 caching to reduce tracking risks; and fixes a big bug in bridge
3950 reachability testing. This release introduces two new design
3951 abstractions in the code: a new "channel" abstraction between circuits
3952 and or_connections to allow for implementing alternate relay-to-relay
3953 transports, and a new "circuitmux" abstraction storing the queue of
3954 circuits for a channel. The release also includes many stability,
3955 security, and privacy fixes.
3958 Changes in version 0.2.4.18-rc - 2013-11-16
3959 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
3960 series. It takes a variety of fixes from the 0.2.5.x branch to improve
3961 stability, performance, and better handling of edge cases.
3964 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
3965 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
3966 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
3967 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
3968 them to solve bug 6033.)
3971 - No longer stop reading or writing on cpuworker connections when
3972 our rate limiting buckets go empty. Now we should handle circuit
3973 handshake requests more promptly. Resolves bug 9731.
3974 - If we are unable to save a microdescriptor to the journal, do not
3975 drop it from memory and then reattempt downloading it. Fixes bug
3976 9645; bugfix on 0.2.2.6-alpha.
3977 - Stop trying to bootstrap all our directory information from
3978 only our first guard. Discovered while fixing bug 9946; bugfix
3980 - The new channel code sometimes lost track of in-progress circuits,
3981 causing long-running clients to stop building new circuits. The
3982 fix is to always call circuit_n_chan_done(chan, 0) from
3983 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
3985 o Minor bugfixes (on 0.2.4.x):
3986 - Correctly log long IPv6 exit policies, instead of truncating them
3987 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
3988 - Our default TLS ecdhe groups were backwards: we meant to be using
3989 P224 for relays (for performance win) and P256 for bridges (since
3990 it is more common in the wild). Instead we had it backwards. After
3991 reconsideration, we decided that the default should be P256 on all
3992 hosts, since its security is probably better, and since P224 is
3993 reportedly used quite little in the wild. Found by "skruffy" on
3994 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
3995 - Free directory authority certificate download statuses on exit
3996 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
3998 o Minor bugfixes (on 0.2.3.x and earlier):
3999 - If the guard we choose first doesn't answer, we would try the
4000 second guard, but once we connected to the second guard we would
4001 abandon it and retry the first one, slowing down bootstrapping.
4002 The fix is to treat all our initially chosen guards as acceptable
4003 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
4004 - Fix an assertion failure that would occur when disabling the
4005 ORPort setting on a running Tor process while accounting was
4006 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
4007 - When examining the list of network interfaces to find our address,
4008 do not consider non-running or disabled network interfaces. Fixes
4009 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
4010 - Avoid an off-by-one error when checking buffer boundaries when
4011 formatting the exit status of a pluggable transport helper.
4012 This is probably not an exploitable bug, but better safe than
4013 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
4016 o Minor features (protecting client timestamps):
4017 - Clients no longer send timestamps in their NETINFO cells. These were
4018 not used for anything, and they provided one small way for clients
4019 to be distinguished from each other as they moved from network to
4020 network or behind NAT. Implements part of proposal 222.
4021 - Clients now round timestamps in INTRODUCE cells down to the nearest
4022 10 minutes. If a new Support022HiddenServices option is set to 0, or
4023 if it's set to "auto" and the feature is disabled in the consensus,
4024 the timestamp is sent as 0 instead. Implements part of proposal 222.
4025 - Stop sending timestamps in AUTHENTICATE cells. This is not such
4026 a big deal from a security point of view, but it achieves no actual
4027 good purpose, and isn't needed. Implements part of proposal 222.
4028 - Reduce down accuracy of timestamps in hidden service descriptors.
4029 Implements part of proposal 222.
4031 o Minor features (other):
4032 - Improve the circuit queue out-of-memory handler. Previously, when
4033 we ran low on memory, we'd close whichever circuits had the most
4034 queued cells. Now, we close those that have the *oldest* queued
4035 cells, on the theory that those are most responsible for us
4036 running low on memory. Based on analysis from a forthcoming paper
4037 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
4038 - Generate bootstrapping status update events correctly when fetching
4039 microdescriptors. Fixes bug 9927.
4040 - Update to the October 2 2013 Maxmind GeoLite Country database.
4042 o Documentation fixes:
4043 - Clarify the usage and risks of setting the ContactInfo torrc line
4044 for your relay or bridge. Resolves ticket 9854.
4045 - Add anchors to the manpage so we can link to the html version of
4046 the documentation for specific options. Resolves ticket 9866.
4047 - Replace remaining references to DirServer in man page and
4048 log entries. Resolves ticket 10124.
4051 Changes in version 0.2.5.1-alpha - 2013-10-02
4052 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
4053 on Linux, allows bridges that offer pluggable transports to report usage
4054 statistics, fixes many issues to make testing easier, and provides
4055 a pile of minor features and bugfixes that have been waiting for a
4056 release of the new branch.
4058 This is the first alpha release in a new series, so expect there to
4059 be bugs. Users who would rather test out a more stable branch should
4060 stay with 0.2.4.x for now.
4062 o Major features (security):
4063 - Use the seccomp2 syscall filtering facility on Linux to limit
4064 which system calls Tor can invoke. This is an experimental,
4065 Linux-only feature to provide defense-in-depth against unknown
4066 attacks. To try turning it on, set "Sandbox 1" in your torrc
4067 file. Please be ready to report bugs. We hope to add support
4068 for better sandboxing in the future, including more fine-grained
4069 filters, better division of responsibility, and support for more
4070 platforms. This work has been done by Cristian-Matei Toader for
4071 Google Summer of Code.
4072 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
4073 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
4074 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
4075 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
4076 them to solve bug 6033.)
4078 o Major features (other):
4079 - Add support for passing arguments to managed pluggable transport
4080 proxies. Implements ticket 3594.
4081 - Bridges now track GeoIP information and the number of their users
4082 even when pluggable transports are in use, and report usage
4083 statistics in their extra-info descriptors. Resolves tickets 4773
4085 - Make testing Tor networks bootstrap better: lower directory fetch
4086 retry schedules and maximum interval without directory requests,
4087 and raise maximum download tries. Implements ticket 6752.
4088 - Add make target 'test-network' to run tests on a Chutney network.
4089 Implements ticket 8530.
4090 - The ntor handshake is now on-by-default, no matter what the
4091 directory authorities recommend. Implements ticket 8561.
4094 - Instead of writing destroy cells directly to outgoing connection
4095 buffers, queue them and intersperse them with other outgoing cells.
4096 This can prevent a set of resource starvation conditions where too
4097 many pending destroy cells prevent data cells from actually getting
4098 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
4099 bugfix on 0.2.0.1-alpha.
4100 - If we are unable to save a microdescriptor to the journal, do not
4101 drop it from memory and then reattempt downloading it. Fixes bug
4102 9645; bugfix on 0.2.2.6-alpha.
4103 - The new channel code sometimes lost track of in-progress circuits,
4104 causing long-running clients to stop building new circuits. The
4105 fix is to always call circuit_n_chan_done(chan, 0) from
4106 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
4109 - Tor now builds each source file in two modes: a mode that avoids
4110 exposing identifiers needlessly, and another mode that exposes
4111 more identifiers for testing. This lets the compiler do better at
4112 optimizing the production code, while enabling us to take more
4113 radical measures to let the unit tests test things.
4114 - The production builds no longer include functions used only in
4115 the unit tests; all functions exposed from a module only for
4116 unit-testing are now static in production builds.
4117 - Add an --enable-coverage configuration option to make the unit
4118 tests (and a new src/or/tor-cov target) to build with gcov test
4122 - We now have rudimentary function mocking support that our unit
4123 tests can use to test functions in isolation. Function mocking
4124 lets the tests temporarily replace a function's dependencies with
4125 stub functions, so that the tests can check the function without
4126 invoking the other functions it calls.
4127 - Add more unit tests for the <circid,channel>->circuit map, and
4128 the destroy-cell-tracking code to fix bug 7912.
4129 - Unit tests for failing cases of the TAP onion handshake.
4130 - More unit tests for address-manipulation functions.
4132 o Minor features (protecting client timestamps):
4133 - Clients no longer send timestamps in their NETINFO cells. These were
4134 not used for anything, and they provided one small way for clients
4135 to be distinguished from each other as they moved from network to
4136 network or behind NAT. Implements part of proposal 222.
4137 - Clients now round timestamps in INTRODUCE cells down to the nearest
4138 10 minutes. If a new Support022HiddenServices option is set to 0, or
4139 if it's set to "auto" and the feature is disabled in the consensus,
4140 the timestamp is sent as 0 instead. Implements part of proposal 222.
4141 - Stop sending timestamps in AUTHENTICATE cells. This is not such
4142 a big deal from a security point of view, but it achieves no actual
4143 good purpose, and isn't needed. Implements part of proposal 222.
4144 - Reduce down accuracy of timestamps in hidden service descriptors.
4145 Implements part of proposal 222.
4147 o Minor features (config options):
4148 - Config (torrc) lines now handle fingerprints which are missing
4149 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
4150 - Support a --dump-config option to print some or all of the
4151 configured options. Mainly useful for debugging the command-line
4152 option parsing code. Helps resolve ticket 4647.
4153 - Raise awareness of safer logging: notify user of potentially
4154 unsafe config options, like logging more verbosely than severity
4155 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
4156 - Add a new configuration option TestingV3AuthVotingStartOffset
4157 that bootstraps a network faster by changing the timing for
4158 consensus votes. Addresses ticket 8532.
4159 - Add a new torrc option "ServerTransportOptions" that allows
4160 bridge operators to pass configuration parameters to their
4161 pluggable transports. Resolves ticket 8929.
4162 - The config (torrc) file now accepts bandwidth and space limits in
4163 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
4164 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
4167 o Minor features (build):
4168 - Add support for `--library-versions` flag. Implements ticket 6384.
4169 - Return the "unexpected sendme" warnings to a warn severity, but make
4170 them rate limited, to help diagnose ticket 8093.
4171 - Detect a missing asciidoc, and warn the user about it, during
4172 configure rather than at build time. Fixes issue 6506. Patch from
4175 o Minor features (other):
4176 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
4177 sockets in a single system call. Implements ticket 5129.
4178 - Log current accounting state (bytes sent and received + remaining
4179 time for the current accounting period) in the relay's heartbeat
4180 message. Implements ticket 5526; patch from Peter Retzlaff.
4181 - Implement the TRANSPORT_LAUNCHED control port event that
4182 notifies controllers about new launched pluggable
4183 transports. Resolves ticket 5609.
4184 - If we're using the pure-C 32-bit curve25519_donna implementation
4185 of curve25519, build it with the -fomit-frame-pointer option to
4186 make it go faster on register-starved hosts. This improves our
4187 handshake performance by about 6% on i386 hosts without nacl.
4189 - Update to the September 4 2013 Maxmind GeoLite Country database.
4192 - Set the listen() backlog limit to the largest actually supported
4193 on the system, not to the value in a header file. Fixes bug 9716;
4194 bugfix on every released Tor.
4195 - No longer accept malformed http headers when parsing urls from
4196 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
4197 bugfix on 0.0.6pre1.
4198 - In munge_extrainfo_into_routerinfo(), check the return value of
4199 memchr(). This would have been a serious issue if we ever passed
4200 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
4202 - On the chance that somebody manages to build Tor on a
4203 platform where time_t is unsigned, correct the way that
4204 microdesc_add_to_cache() handles negative time arguments.
4205 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
4206 - Reject relative control socket paths and emit a warning. Previously,
4207 single-component control socket paths would be rejected, but Tor
4208 would not log why it could not validate the config. Fixes bug 9258;
4209 bugfix on 0.2.3.16-alpha.
4211 o Minor bugfixes (command line):
4212 - Use a single command-line parser for parsing torrc options on the
4213 command line and for finding special command-line options to avoid
4214 inconsistent behavior for torrc option arguments that have the same
4215 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
4217 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
4218 9573; bugfix on 0.0.9pre5.
4220 o Minor fixes (build, auxiliary programs):
4221 - Stop preprocessing the "torify" script with autoconf, since
4222 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
4224 - The tor-fw-helper program now follows the standard convention and
4225 exits with status code "0" on success. Fixes bug 9030; bugfix on
4226 0.2.3.1-alpha. Patch by Arlo Breault.
4227 - Corrected ./configure advice for what openssl dev package you should
4228 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
4230 o Minor code improvements:
4231 - Remove constants and tests for PKCS1 padding; it's insecure and
4232 shouldn't be used for anything new. Fixes bug 8792; patch
4234 - Remove instances of strcpy() from the unit tests. They weren't
4235 hurting anything, since they were only in the unit tests, but it's
4236 embarassing to have strcpy() in the code at all, and some analysis
4237 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
4238 0.2.3.8-alpha. Patch from Arlo Breault.
4241 - Remove migration code from when we renamed the "cached-routers"
4242 file to "cached-descriptors" back in 0.2.0.8-alpha. This
4243 incidentally resolves ticket 6502 by cleaning up the related code
4244 a bit. Patch from Akshay Hebbar.
4246 o Code simplification and refactoring:
4247 - Extract the common duplicated code for creating a subdirectory
4248 of the data directory and writing to a file in it. Fixes ticket
4249 4282; patch from Peter Retzlaff.
4250 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
4251 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
4252 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
4253 - Add a set of accessor functions for the circuit timeout data
4254 structure. Fixes ticket 6153; patch from "piet".
4255 - Clean up exit paths from connection_listener_new(). Closes ticket
4256 8789. Patch from Arlo Breault.
4257 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
4258 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
4259 - Use a doubly-linked list to implement the global circuit list.
4260 Resolves ticket 9108. Patch from Marek Majkowski.
4261 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
4264 Changes in version 0.2.4.17-rc - 2013-09-05
4265 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
4266 series. It adds an emergency step to help us tolerate the massive
4267 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
4268 circuit-level handshakes now effectively jump the queue compared to
4269 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
4270 big bug hindering bridge reachability tests.
4273 - Relays now process the new "NTor" circuit-level handshake requests
4274 with higher priority than the old "TAP" circuit-level handshake
4275 requests. We still process some TAP requests to not totally starve
4276 0.2.3 clients when NTor becomes popular. A new consensus parameter
4277 "NumNTorsPerTAP" lets us tune the balance later if we need to.
4278 Implements ticket 9574.
4281 - If the circuit build timeout logic is disabled (via the consensus,
4282 or because we are an authority), then don't build testing circuits.
4283 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
4284 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
4285 previously they did not, which prevented them from receiving
4286 successful connections from relays for self-test or bandwidth
4287 testing. Also, when a relay is extending a circuit to a bridge,
4288 it needs to send a NETINFO cell, even when the bridge hasn't sent
4289 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
4290 - If the time to download the next old-style networkstatus is in
4291 the future, do not decline to consider whether to download the
4292 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
4296 - Avoid double-closing the listener socket in our socketpair()
4297 replacement (used on Windows) in the case where the addresses on
4298 our opened sockets don't match what we expected. Fixes bug 9400;
4299 bugfix on 0.0.2pre7. Found by Coverity.
4301 o Minor fixes (config options):
4302 - Avoid overflows when the user sets MaxCircuitDirtiness to a
4303 ridiculously high value, by imposing a (ridiculously high) 30-day
4304 maximum on MaxCircuitDirtiness.
4305 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
4306 message is logged at notice, not at info.
4307 - Warn and fail if a server is configured not to advertise any
4308 ORPorts at all. (We need *something* to put in our descriptor,
4309 or we just won't work.)
4312 - Track how many "TAP" and "NTor" circuit handshake requests we get,
4313 and how many we complete, and log it every hour to help relay
4314 operators follow trends in network load. Addresses ticket 9658.
4315 - Update to the August 7 2013 Maxmind GeoLite Country database.
4318 Changes in version 0.2.4.16-rc - 2013-08-10
4319 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
4320 series. It fixes several crash bugs in the 0.2.4 branch.
4323 - Fix a bug in the voting algorithm that could yield incorrect results
4324 when a non-naming authority declared too many flags. Fixes bug 9200;
4325 bugfix on 0.2.0.3-alpha.
4326 - Fix an uninitialized read that could in some cases lead to a remote
4327 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
4328 Anybody running a hidden service on the experimental 0.2.4.x
4329 branch should upgrade. (This is, so far as we know, unrelated to
4331 - Avoid an assertion failure when processing DNS replies without the
4332 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
4333 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
4334 0.2.4.15-rc. Found by stem integration tests.
4337 - Fix an invalid memory read that occured when a pluggable
4338 transport proxy failed its configuration protocol.
4339 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
4340 - When evaluating whether to use a connection that we haven't
4341 decided is canonical using a recent link protocol version,
4342 decide that it's canonical only if it used address _does_
4343 match the desired address. Fixes bug 9309; bugfix on
4344 0.2.4.4-alpha. Reported by skruffy.
4345 - Make the default behavior of NumDirectoryGuards be to track
4346 NumEntryGuards. Now a user who changes only NumEntryGuards will get
4347 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
4348 - Fix a spurious compilation warning with some older versions of
4349 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
4352 - Update to the July 3 2013 Maxmind GeoLite Country database.
4355 Changes in version 0.2.4.15-rc - 2013-07-01
4356 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
4357 series. It fixes a few smaller bugs, but generally appears stable.
4358 Please test it and let us know whether it is!
4361 - When receiving a new configuration file via the control port's
4362 LOADCONF command, do not treat the defaults file as absent.
4363 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
4366 - Issue a warning when running with the bufferevents backend enabled.
4367 It's still not stable, and people should know that they're likely
4368 to hit unexpected problems. Closes ticket 9147.
4371 Changes in version 0.2.4.14-alpha - 2013-06-18
4372 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
4373 present in 0.2.4.13-alpha.
4376 - When we have too much memory queued in circuits (according to a new
4377 MaxMemInCellQueues option), close the circuits consuming the most
4378 memory. This prevents us from running out of memory as a relay if
4379 circuits fill up faster than they can be drained. Fixes bug 9063;
4380 bugfix on the 54th commit of Tor. This bug is a further fix beyond
4381 bug 6252, whose fix was merged into 0.2.3.21-rc.
4383 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
4384 where we tried to solve this issue simply by imposing an upper limit
4385 on the number of queued cells for a single circuit. That approach
4386 proved to be problematic, since there are ways to provoke clients to
4387 send a number of cells in excess of any such reasonable limit. Fixes
4388 bug 9072; bugfix on 0.2.4.13-alpha.
4390 - Limit hidden service descriptors to at most ten introduction
4391 points, to slow one kind of guard enumeration. Fixes bug 9002;
4392 bugfix on 0.1.1.11-alpha.
4395 Changes in version 0.2.4.13-alpha - 2013-06-14
4396 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
4397 vulnerabilities, makes socks5 username/password circuit isolation
4398 actually actually work (this time for sure!), and cleans up a bunch
4399 of other issues in preparation for a release candidate.
4401 o Major bugfixes (robustness):
4402 - Close any circuit that has too many cells queued on it. Fixes
4403 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
4404 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
4405 - Prevent the get_freelists() function from running off the end of
4406 the list of freelists if it somehow gets an unrecognized
4407 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
4409 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
4410 when an exit connection with optimistic data succeeds immediately
4411 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
4413 - Fix a directory authority crash bug when building a consensus
4414 using an older consensus as its basis. Fixes bug 8833. Bugfix
4418 - Avoid a memory leak where we would leak a consensus body when we
4419 find that a consensus which we couldn't previously verify due to
4420 missing certificates is now verifiable. Fixes bug 8719; bugfix
4422 - We used to always request authority certificates by identity digest,
4423 meaning we'd get the newest one even when we wanted one with a
4424 different signing key. Then we would complain about being given
4425 a certificate we already had, and never get the one we really
4426 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
4427 resource to request the one we want. Fixes bug 5595; bugfix on
4429 - Follow the socks5 protocol when offering username/password
4430 authentication. The fix for bug 8117 exposed this bug, and it
4431 turns out real-world applications like Pidgin do care. Bugfix on
4432 0.2.3.2-alpha; fixes bug 8879.
4433 - Prevent failures on Windows Vista and later when rebuilding the
4434 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
4435 bugfix on 0.2.4.12-alpha.
4438 - Fix an impossible buffer overrun in the AES unit tests. Fixes
4439 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
4440 - If for some reason we fail to write a microdescriptor while
4441 rebuilding the cache, do not let the annotations from that
4442 microdescriptor linger in the cache file, and do not let the
4443 microdescriptor stay recorded as present in its old location.
4444 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
4445 - Fix a memory leak that would occur whenever a configuration
4446 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
4447 - Paste the description for PathBias parameters from the man
4448 page into or.h, so the code documents them too. Fixes bug 7982;
4449 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
4450 - Relays now treat a changed IPv6 ORPort as sufficient reason to
4451 publish an updated descriptor. Fixes bug 6026; bugfix on
4453 - When launching a resolve request on behalf of an AF_UNIX control
4454 socket, omit the address field of the new entry connection, used in
4455 subsequent controller events, rather than letting tor_dup_addr()
4456 set it to "<unknown address type>". Fixes bug 8639; bugfix on
4459 o Minor bugfixes (log messages):
4460 - Fix a scaling issue in the path bias accounting code that
4461 resulted in "Bug:" log messages from either
4462 pathbias_scale_close_rates() or pathbias_count_build_success().
4463 This represents a bugfix on a previous bugfix: the original fix
4464 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
4466 - Give a less useless error message when the user asks for an IPv4
4467 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
4471 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
4472 to tolerate bug 8093 for now.
4473 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
4474 in directory authority votes to describe whether they have enough
4475 measured bandwidths to ignore advertised (relay descriptor)
4476 bandwidth claims. Resolves ticket 8711.
4477 - Update to the June 5 2013 Maxmind GeoLite Country database.
4479 o Removed documentation:
4480 - Remove some of the older contents of doc/ as obsolete; move others
4481 to torspec.git. Fixes bug 8965.
4483 o Code simplification and refactoring:
4484 - Avoid using character buffers when constructing most directory
4485 objects: this approach was unwieldy and error-prone. Instead,
4486 build smartlists of strings, and concatenate them when done.
4489 Changes in version 0.2.4.12-alpha - 2013-04-18
4490 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
4491 process for lengthening the guard rotation period, makes directory
4492 authority opinions in the consensus a bit less gameable, makes socks5
4493 username/password circuit isolation actually work, and fixes a wide
4494 variety of other issues.
4497 - Raise the default time that a client keeps an entry guard from
4498 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
4499 2012 paper. (We would make it even longer, but we need better client
4500 load balancing first.) Also, make the guard lifetime controllable
4501 via a new GuardLifetime torrc option and a GuardLifetime consensus
4502 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
4503 - Directory authorities now prefer using measured bandwidths to
4504 advertised ones when computing flags and thresholds. Resolves
4506 - Directory authorities that have more than a threshold number
4507 of relays with measured bandwidths now treat relays with unmeasured
4508 bandwidths as having bandwidth 0. Resolves ticket 8435.
4510 o Major bugfixes (assert / resource use):
4511 - Avoid a bug where our response to TLS renegotiation under certain
4512 network conditions could lead to a busy-loop, with 100% CPU
4513 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
4514 - Avoid an assertion when we discover that we'd like to write a cell
4515 onto a closing connection: just discard the cell. Fixes another
4516 case of bug 7350; bugfix on 0.2.4.4-alpha.
4518 o Major bugfixes (client-side privacy):
4519 - When we mark a circuit as unusable for new circuits, have it
4520 continue to be unusable for new circuits even if MaxCircuitDirtiness
4521 is increased too much at the wrong time, or the system clock jumps
4522 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
4523 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
4524 which have resolved to internal addresses") is set, apply that
4525 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
4526 - When an exit relay rejects a stream with reason "exit policy", but
4527 we only know an exit policy summary (e.g. from the microdesc
4528 consensus) for it, do not mark the relay as useless for all exiting.
4529 Instead, mark just the circuit as unsuitable for that particular
4530 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
4531 - Allow applications to get proper stream isolation with
4532 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
4533 username/password authentication also offer "no authentication". Tor
4534 had previously preferred "no authentication", so the applications
4535 never actually sent Tor their auth details. Now Tor selects
4536 username/password authentication if it's offered. You can disable
4537 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
4538 bug 8117; bugfix on 0.2.3.3-alpha.
4540 o Major bugfixes (other):
4541 - When unable to find any working directory nodes to use as a
4542 directory guard, give up rather than adding the same non-working
4543 nodes to the directory guard list over and over. Fixes bug 8231;
4544 bugfix on 0.2.4.8-alpha.
4547 - Reject as invalid most directory objects containing a NUL.
4548 Belt-and-suspender fix for bug 8037.
4549 - In our testsuite, create temporary directories with a bit more
4550 entropy in their name to make name collisions less likely. Fixes
4552 - Add CACHED keyword to ADDRMAP events in the control protocol
4553 to indicate whether a DNS result will be cached or not. Resolves
4555 - Update to the April 3 2013 Maxmind GeoLite Country database.
4557 o Minor features (build):
4558 - Detect and reject attempts to build Tor with threading support
4559 when OpenSSL has been compiled without threading support.
4561 - Clarify that when autoconf is checking for nacl, it is checking
4562 specifically for nacl with a fast curve25519 implementation.
4564 - Warn if building on a platform with an unsigned time_t: there
4565 are too many places where Tor currently assumes that time_t can
4566 hold negative values. We'd like to fix them all, but probably
4569 o Minor bugfixes (build):
4570 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
4571 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
4572 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
4573 - Add the old src/or/micro-revision.i filename to CLEANFILES.
4574 On the off chance that somebody has one, it will go away as soon
4575 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
4576 - Build Tor correctly on 32-bit platforms where the compiler can build
4577 but not run code using the "uint128_t" construction. Fixes bug 8587;
4578 bugfix on 0.2.4.8-alpha.
4579 - Fix compilation warning with some versions of clang that would
4580 prefer the -Wswitch-enum compiler flag to warn about switch
4581 statements with missing enum values, even if those switch
4582 statements have a "default:" statement. Fixes bug 8598; bugfix
4585 o Minor bugfixes (protocol):
4586 - Fix the handling of a TRUNCATE cell when it arrives while the
4587 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
4588 - Fix a misframing issue when reading the version numbers in a
4589 VERSIONS cell. Previously we would recognize [00 01 00 02] as
4590 'version 1, version 2, and version 0x100', when it should have
4591 only included versions 1 and 2. Fixes bug 8059; bugfix on
4592 0.2.0.10-alpha. Reported pseudonymously.
4593 - Make the format and order of STREAM events for DNS lookups
4594 consistent among the various ways to launch DNS lookups. Fixes
4595 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
4596 - Correct our check for which versions of Tor support the EXTEND2
4597 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
4598 later, when support was really added in version 0.2.4.8-alpha.
4599 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
4601 o Minor bugfixes (other):
4602 - Correctly store microdescriptors and extrainfo descriptors with
4603 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
4604 Bug reported by "cypherpunks".
4605 - Increase the width of the field used to remember a connection's
4606 link protocol version to two bytes. Harmless for now, since the
4607 only currently recognized versions are one byte long. Reported
4608 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
4609 - If the state file's path bias counts are invalid (presumably from a
4610 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
4611 additional checks and log messages to the scaling of Path Bias
4612 counts, in case there still are remaining issues with scaling.
4613 Should help resolve bug 8235.
4614 - Eliminate several instances where we use "Nickname=ID" to refer to
4615 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
4616 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
4617 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
4619 o Minor bugfixes (syscalls):
4620 - Always check the return values of functions fcntl() and
4621 setsockopt(). We don't believe these are ever actually failing in
4622 practice, but better safe than sorry. Also, checking these return
4623 values should please analysis tools like Coverity. Patch from
4624 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
4625 - Use direct writes rather than stdio when building microdescriptor
4626 caches, in an attempt to mitigate bug 8031, or at least make it
4629 o Minor bugfixes (config):
4630 - When rejecting a configuration because we were unable to parse a
4631 quoted string, log an actual error message. Fixes bug 7950; bugfix
4633 - Behave correctly when the user disables LearnCircuitBuildTimeout
4634 but doesn't tell us what they would like the timeout to be. Fixes
4635 bug 6304; bugfix on 0.2.2.14-alpha.
4636 - When autodetecting the number of CPUs, use the number of available
4637 CPUs in preference to the number of configured CPUs. Inform the
4638 user if this reduces the number of available CPUs. Fixes bug 8002;
4639 bugfix on 0.2.3.1-alpha.
4640 - Make it an error when you set EntryNodes but disable UseGuardNodes,
4641 since it will (surprisingly to some users) ignore EntryNodes. Fixes
4642 bug 8180; bugfix on 0.2.3.11-alpha.
4643 - Allow TestingTorNetworks to override the 4096-byte minimum for
4644 the Fast threshold. Otherwise they can't bootstrap until they've
4645 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
4646 - Fix some logic errors when the user manually overrides the
4647 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
4650 o Minor bugfixes (log messages to help diagnose bugs):
4651 - If we fail to free a microdescriptor because of bug 7164, log
4652 the filename and line number from which we tried to free it.
4653 - Add another diagnostic to the heartbeat message: track and log
4654 overhead that TLS is adding to the data we write. If this is
4655 high, we are sending too little data to SSL_write at a time.
4656 Diagnostic for bug 7707.
4657 - Add more detail to a log message about relaxed timeouts, to help
4659 - Warn more aggressively when flushing microdescriptors to a
4660 microdescriptor cache fails, in an attempt to mitigate bug 8031,
4661 or at least make it more diagnosable.
4662 - Improve debugging output to help track down bug 8185 ("Bug:
4663 outgoing relay cell has n_chan==NULL. Dropping.")
4664 - Log the purpose of a path-bias testing circuit correctly.
4665 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
4667 o Minor bugfixes (0.2.4.x log messages that were too noisy):
4668 - Don't attempt to relax the timeout of already opened 1-hop circuits.
4669 They might never timeout. This should eliminate some/all cases of
4670 the relaxed timeout log message.
4671 - Use circuit creation time for network liveness evaluation. This
4672 should eliminate warning log messages about liveness caused
4673 by changes in timeout evaluation. Fixes bug 6572; bugfix on
4675 - Reduce a path bias length check from notice to info. The message
4676 is triggered when creating controller circuits. Fixes bug 8196;
4677 bugfix on 0.2.4.8-alpha.
4678 - Fix a path state issue that triggered a notice during relay startup.
4679 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
4680 - Reduce occurrences of warns about circuit purpose in
4681 connection_ap_expire_building(). Fixes bug 8477; bugfix on
4684 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
4685 - If we encounter a write failure on a SOCKS connection before we
4686 finish our SOCKS handshake, don't warn that we closed the
4687 connection before we could send a SOCKS reply. Fixes bug 8427;
4688 bugfix on 0.1.0.1-rc.
4689 - Correctly recognize that [::1] is a loopback address. Fixes
4690 bug 8377; bugfix on 0.2.1.3-alpha.
4691 - Fix a directory authority warn caused when we have a large amount
4692 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
4693 - Don't log inappropriate heartbeat messages when hibernating: a
4694 hibernating node is _expected_ to drop out of the consensus,
4695 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
4696 bugfix on 0.2.3.1-alpha.
4697 - Don't complain about bootstrapping problems while hibernating.
4698 These complaints reflect a general code problem, but not one
4699 with any problematic effects (no connections are actually
4700 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
4702 o Documentation fixes:
4703 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
4704 names match. Fixes bug 7768.
4705 - Make the torify manpage no longer refer to tsocks; torify hasn't
4706 supported tsocks since 0.2.3.14-alpha.
4707 - Make the tor manpage no longer reference tsocks.
4708 - Fix the GeoIPExcludeUnknown documentation to refer to
4709 ExcludeExitNodes rather than the currently nonexistent
4710 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
4713 - The tor-tsocks.conf is no longer distributed or installed. We
4714 recommend that tsocks users use torsocks instead. Resolves
4718 Changes in version 0.2.4.11-alpha - 2013-03-11
4719 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
4720 more robust, makes hidden service authentication work again, and
4721 resolves a DPI fingerprint for Tor's SSL transport.
4723 o Major features (directory authorities):
4724 - Directory authorities now support a new consensus method (17)
4725 where they cap the published bandwidth of servers for which
4726 insufficient bandwidth measurements exist. Fixes part of bug 2286.
4727 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
4728 serve any v2 directory information. Now we can test disabling the
4729 old deprecated v2 directory format, and see whether doing so has
4730 any effect on network load. Begins to fix bug 6783.
4731 - Directory authorities now include inside each vote a statement of
4732 the performance thresholds they used when assigning flags.
4733 Implements ticket 8151.
4735 o Major bugfixes (directory authorities):
4736 - Stop marking every relay as having been down for one hour every
4737 time we restart a directory authority. These artificial downtimes
4738 were messing with our Stable and Guard flag calculations. Fixes
4739 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
4741 o Major bugfixes (hidden services):
4742 - Allow hidden service authentication to succeed again. When we
4743 refactored the hidden service introduction code back
4744 in 0.2.4.1-alpha, we didn't update the code that checks
4745 whether authentication information is present, causing all
4746 authentication checks to return "false". Fix for bug 8207; bugfix
4747 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
4749 o Minor features (relays, bridges):
4750 - Make bridge relays check once a minute for whether their IP
4751 address has changed, rather than only every 15 minutes. Resolves
4753 - Refactor resolve_my_address() so it returns the method by which we
4754 decided our public IP address (explicitly configured, resolved from
4755 explicit hostname, guessed from interfaces, learned by gethostname).
4756 Now we can provide more helpful log messages when a relay guesses
4757 its IP address incorrectly (e.g. due to unexpected lines in
4758 /etc/hosts). Resolves ticket 2267.
4759 - Teach bridge-using clients to avoid 0.2.2 bridges when making
4760 microdescriptor-related dir requests, and only fall back to normal
4761 descriptors if none of their bridges can handle microdescriptors
4762 (as opposed to the fix in ticket 4013, which caused them to fall
4763 back to normal descriptors if *any* of their bridges preferred
4764 them). Resolves ticket 4994.
4765 - Randomize the lifetime of our SSL link certificate, so censors can't
4766 use the static value for filtering Tor flows. Resolves ticket 8443;
4767 related to ticket 4014 which was included in 0.2.2.33.
4768 - Support a new version of the link protocol that allows 4-byte circuit
4769 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
4770 a possible resource exhaustion issue. Closes ticket 7351; implements
4773 o Minor features (portability):
4774 - Tweak the curve25519-donna*.c implementations to tolerate systems
4775 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
4776 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
4777 the signs of types during autoconf. This is better than our old
4778 approach, which didn't work when cross-compiling.
4779 - Detect the sign of enum values, rather than assuming that MSC is the
4780 only compiler where enum types are all signed. Fixes bug 7727;
4781 bugfix on 0.2.4.10-alpha.
4783 o Minor features (other):
4784 - Say "KBytes" rather than "KB" in the man page (for various values
4785 of K), to further reduce confusion about whether Tor counts in
4786 units of memory or fractions of units of memory. Resolves ticket 7054.
4787 - Clear the high bit on curve25519 public keys before passing them to
4788 our backend, in case we ever wind up using a backend that doesn't do
4789 so itself. If we used such a backend, and *didn't* clear the high bit,
4790 we could wind up in a situation where users with such backends would
4791 be distinguishable from users without. Fixes bug 8121; bugfix on
4793 - Update to the March 6 2013 Maxmind GeoLite Country database.
4795 o Minor bugfixes (clients):
4796 - When we receive a RELAY_END cell with the reason DONE, or with no
4797 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
4798 status as "connection refused". Previously we reported these cases
4799 as success but then immediately closed the connection. Fixes bug
4800 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
4801 - Downgrade an assertion in connection_ap_expire_beginning to an
4802 LD_BUG message. The fix for bug 8024 should prevent this message
4803 from displaying, but just in case, a warn that we can diagnose
4804 is better than more assert crashes. Fixes bug 8065; bugfix on
4806 - Lower path use bias thresholds to .80 for notice and .60 for warn.
4807 Also make the rate limiting flags for the path use bias log messages
4808 independent from the original path bias flags. Fixes bug 8161;
4809 bugfix on 0.2.4.10-alpha.
4811 o Minor bugfixes (relays):
4812 - Stop trying to resolve our hostname so often (e.g. every time we
4813 think about doing a directory fetch). Now we reuse the cached
4814 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
4815 and 2410 (bugfix on 0.1.2.2-alpha).
4816 - Stop sending a stray "(null)" in some cases for the server status
4817 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
4819 - When choosing which stream on a formerly stalled circuit to wake
4820 first, make better use of the platform's weak RNG. Previously,
4821 we had been using the % ("modulo") operator to try to generate a
4822 1/N chance of picking each stream, but this behaves badly with
4823 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
4825 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
4826 Irix's random() only return 15 bits; Solaris's random() returns more
4827 bits but its RAND_MAX says it only returns 15, and so on. Motivated
4828 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
4830 o Minor bugfixes (directory authorities):
4831 - Directory authorities now use less space when formatting identical
4832 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
4835 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
4836 - Avoid leaking memory if we fail to compute a consensus signature
4837 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
4838 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
4840 - Fix a memory leak during safe-cookie controller authentication.
4841 Bugfix on 0.2.3.13-alpha.
4842 - Avoid memory leak of IPv6 policy content if we fail to format it into
4843 a router descriptor. Bugfix on 0.2.4.7-alpha.
4845 o Minor bugfixes (other code correctness issues):
4846 - Avoid a crash if we fail to generate an extrainfo descriptor.
4847 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
4849 - When detecting the largest possible file descriptor (in order to
4850 close all file descriptors when launching a new program), actually
4851 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
4852 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
4854 - Fix a copy-and-paste error when adding a missing A1 to a routerset
4855 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
4856 Bugfix on 0.2.4.10-alpha.
4857 - Fix an impossible-to-trigger integer overflow when estimating how
4858 long our onionskin queue would take. (This overflow would require us
4859 to accept 4 million onionskins before processing 100 of them.) Fixes
4860 bug 8210; bugfix on 0.2.4.10-alpha.
4862 o Code simplification and refactoring:
4863 - Add a wrapper function for the common "log a message with a
4867 Changes in version 0.2.4.10-alpha - 2013-02-04
4868 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
4869 certain attacks that flood the network with relays; changes the queue
4870 for circuit create requests from a sized-based limit to a time-based
4871 limit; resumes building with MSVC on Windows; and fixes a wide variety
4874 o Major bugfixes (directory authority):
4875 - When computing directory thresholds, ignore any rejected-as-sybil
4876 nodes during the computation so that they can't influence Fast,
4877 Guard, etc. (We should have done this for proposal 109.) Fixes
4879 - When marking a node as a likely sybil, reset its uptime metrics
4880 to zero, so that it cannot time towards getting marked as Guard,
4881 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
4885 - When a TLS write is partially successful but incomplete, remember
4886 that the flushed part has been flushed, and notice that bytes were
4887 actually written. Reported and fixed pseudonymously. Fixes bug
4888 7708; bugfix on Tor 0.1.0.5-rc.
4889 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
4890 ID: these could be used to create unexpected streams and circuits
4891 which would count as "present" to some parts of Tor but "absent"
4892 to others, leading to zombie circuits and streams or to a bandwidth
4893 denial-of-service. Fixes bug 7889; bugfix on every released version
4894 of Tor. Reported by "oftc_must_be_destroyed".
4895 - Rename all macros in our local copy of queue.h to begin with "TOR_".
4896 This change seems the only good way to permanently prevent conflicts
4897 with queue.h on various operating systems. Fixes bug 8107; bugfix
4900 o Major features (relay):
4901 - Instead of limiting the number of queued onionskins (aka circuit
4902 create requests) to a fixed, hard-to-configure number, we limit
4903 the size of the queue based on how many we expect to be able to
4904 process in a given amount of time. We estimate the time it will
4905 take to process an onionskin based on average processing time
4906 of previous onionskins. Closes ticket 7291. You'll never have to
4907 configure MaxOnionsPending again.
4909 o Major features (portability):
4910 - Resume building correctly with MSVC and Makefile.nmake. This patch
4911 resolves numerous bugs and fixes reported by ultramage, including
4912 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
4913 - Make the ntor and curve25519 code build correctly with MSVC.
4914 Fix on 0.2.4.8-alpha.
4917 - When directory authorities are computing thresholds for flags,
4918 never let the threshold for the Fast flag fall below 4096
4919 bytes. Also, do not consider nodes with extremely low bandwidths
4920 when deciding thresholds for various directory flags. This change
4921 should raise our threshold for Fast relays, possibly in turn
4922 improving overall network performance; see ticket 1854. Resolves
4924 - The Tor client now ignores sub-domain components of a .onion
4925 address. This change makes HTTP "virtual" hosting
4926 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
4927 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
4928 hosted on the same hidden service. Implements proposal 204.
4929 - We compute the overhead from passing onionskins back and forth to
4930 cpuworkers, and report it when dumping statistics in response to
4931 SIGUSR1. Supports ticket 7291.
4933 o Minor features (path selection):
4934 - When deciding whether we have enough descriptors to build circuits,
4935 instead of looking at raw relay counts, look at which fraction
4936 of (bandwidth-weighted) paths we're able to build. This approach
4937 keeps clients from building circuits if their paths are likely to
4938 stand out statistically. The default fraction of paths needed is
4939 taken from the consensus directory; you can override it with the
4940 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
4941 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
4942 and we have GeoIP information, also exclude all nodes with unknown
4943 countries "??" and "A1". This behavior is controlled by the
4944 new GeoIPExcludeUnknown option: you can make such nodes always
4945 excluded with "GeoIPExcludeUnknown 1", and disable the feature
4946 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
4947 gets you the default behavior. Implements feature 7706.
4948 - Path Use Bias: Perform separate accounting for successful circuit
4949 use. Keep separate statistics on stream attempt rates versus stream
4950 success rates for each guard. Provide configurable thresholds to
4951 determine when to emit log messages or disable use of guards that
4952 fail too many stream attempts. Resolves ticket 7802.
4954 o Minor features (log messages):
4955 - When learning a fingerprint for a bridge, log its corresponding
4956 transport type. Implements ticket 7896.
4957 - Improve the log message when "Bug/attack: unexpected sendme cell
4958 from client" occurs, to help us track bug 8093.
4961 - Remove a couple of extraneous semicolons that were upsetting the
4962 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
4963 bugfix on 0.2.2.1-alpha.
4964 - Remove a source of rounding error during path bias count scaling;
4965 don't count cannibalized circuits as used for path bias until we
4966 actually try to use them; and fix a circuit_package_relay_cell()
4967 warning message about n_chan==NULL. Fixes bug 7802.
4968 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
4969 actually link against nacl when we're configured to use it. Fixes
4970 bug 7972; bugfix on 0.2.4.8-alpha.
4971 - Compile correctly with the --disable-curve25519 option. Fixes
4972 bug 8153; bugfix on 0.2.4.8-alpha.
4974 o Build improvements:
4975 - Do not report status verbosely from autogen.sh unless the -v flag
4976 is specified. Fixes issue 4664. Patch from Onizuka.
4977 - Replace all calls to snprintf() outside of src/ext with
4978 tor_snprintf(). Also remove the #define to replace snprintf with
4979 _snprintf on Windows; they have different semantics, and all of
4980 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
4981 - Try to detect if we are ever building on a platform where
4982 memset(...,0,...) does not set the value of a double to 0.0. Such
4983 platforms are permitted by the C standard, though in practice
4984 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
4985 currently support them, but it's better to detect them and fail
4986 than to perform erroneously.
4989 - Stop exporting estimates of v2 and v3 directory traffic shares
4990 in extrainfo documents. They were unneeded and sometimes inaccurate.
4991 Also stop exporting any v2 directory request statistics. Resolves
4993 - Drop support for detecting and warning about versions of Libevent
4994 before 1.3e. Nothing reasonable ships with them any longer;
4995 warning the user about them shouldn't be needed. Resolves ticket
4998 o Code simplifications and refactoring:
4999 - Rename "isin" functions to "contains", for grammar. Resolves
5001 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
5002 with the natural logarithm function from the system libm. Resolves
5006 Changes in version 0.2.4.9-alpha - 2013-01-15
5007 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
5011 - Fix backward compatibility logic when receiving an embedded ntor
5012 handshake tunneled in a CREATE cell. This clears up the "Bug:
5013 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
5017 Changes in version 0.2.4.8-alpha - 2013-01-14
5018 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
5019 risks, adds a new stronger and faster circuit handshake, and offers
5020 stronger and faster link encryption when both sides support it.
5023 - Preliminary support for directory guards (proposal 207): when
5024 possible, clients now use their entry guards for non-anonymous
5025 directory requests. This can help prevent client enumeration. Note
5026 that this behavior only works when we have a usable consensus
5027 directory, and when options about what to download are more or less
5028 standard. In the future we should re-bootstrap from our guards,
5029 rather than re-bootstrapping from the preconfigured list of
5030 directory sources that ships with Tor. Resolves ticket 6526.
5031 - Tor relays and clients now support a better CREATE/EXTEND cell
5032 format, allowing the sender to specify multiple address, identity,
5033 and handshake types. Implements Robert Ransom's proposal 200;
5036 o Major features (new circuit handshake):
5037 - Tor now supports a new circuit extension handshake designed by Ian
5038 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
5039 circuit extension handshake, later called "TAP", was a bit slow
5040 (especially on the relay side), had a fragile security proof, and
5041 used weaker keys than we'd now prefer. The new circuit handshake
5042 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
5043 function, making it significantly more secure than the older
5044 handshake, and significantly faster. Tor can use one of two built-in
5045 pure-C curve25519-donna implementations by Adam Langley, or it
5046 can link against the "nacl" library for a tuned version if present.
5048 The built-in version is very fast for 64-bit systems when building
5049 with GCC. The built-in 32-bit version is still faster than the
5050 old TAP protocol, but using libnacl is better on most such hosts.
5052 Clients don't currently use this protocol by default, since
5053 comparatively few clients support it so far. To try it, set
5054 UseNTorHandshake to 1.
5056 Implements proposal 216; closes ticket 7202.
5058 o Major features (better link encryption):
5059 - Relays can now enable the ECDHE TLS ciphersuites when available
5060 and appropriate. These ciphersuites let us negotiate forward-secure
5061 TLS secret keys more safely and more efficiently than with our
5062 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
5063 public relays prefer the (faster) P224 group, and bridges prefer
5064 the (more common) P256 group; you can override this with the
5067 Enabling these ciphers was a little tricky, since for a long time,
5068 clients had been claiming to support them without actually doing
5069 so, in order to foil fingerprinting. But with the client-side
5070 implementation of proposal 198 in 0.2.3.17-beta, clients can now
5071 match the ciphers from recent Firefox versions *and* list the
5072 ciphers they actually mean, so relays can believe such clients
5073 when they advertise ECDHE support in their TLS ClientHello messages.
5075 This feature requires clients running 0.2.3.17-beta or later,
5076 and requires both sides to be running OpenSSL 1.0.0 or later
5077 with ECC support. OpenSSL 1.0.1, with the compile-time option
5078 "enable-ec_nistp_64_gcc_128", is highly recommended.
5080 Implements the relay side of proposal 198; closes ticket 7200.
5083 - Avoid crashing when, as a relay without IPv6-exit support, a
5084 client insists on getting an IPv6 address or nothing. Fixes bug
5085 7814; bugfix on 0.2.4.7-alpha.
5088 - Improve circuit build timeout handling for hidden services.
5089 In particular: adjust build timeouts more accurately depending
5090 upon the number of hop-RTTs that a particular circuit type
5091 undergoes. Additionally, launch intro circuits in parallel
5092 if they timeout, and take the first one to reply as valid.
5093 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
5094 separate error codes; or at least, don't break for that reason.
5095 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
5096 - Update to the January 2 2013 Maxmind GeoLite Country database.
5098 o Minor features (testing):
5099 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
5100 (P-256) Diffie-Hellman handshakes to src/or/bench.
5101 - Add benchmark functions to test onion handshake performance.
5103 o Minor features (path bias detection):
5104 - Alter the Path Bias log messages to be more descriptive in terms
5105 of reporting timeouts and other statistics.
5106 - Create three levels of Path Bias log messages, as opposed to just
5107 two. These are configurable via consensus as well as via the torrc
5108 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
5109 The default values are 0.70, 0.50, and 0.30 respectively.
5110 - Separate the log message levels from the decision to drop guards,
5111 which also is available via torrc option PathBiasDropGuards.
5112 PathBiasDropGuards still defaults to 0 (off).
5113 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
5114 in combination with PathBiasExtremeRate.
5115 - Increase the default values for PathBiasScaleThreshold and
5116 PathBiasCircThreshold from (200, 20) to (300, 150).
5117 - Add in circuit usage accounting to path bias. If we try to use a
5118 built circuit but fail for any reason, it counts as path bias.
5119 Certain classes of circuits where the adversary gets to pick your
5120 destination node are exempt from this accounting. Usage accounting
5121 can be specifically disabled via consensus parameter or torrc.
5122 - Convert all internal path bias state to double-precision floating
5123 point, to avoid roundoff error and other issues.
5124 - Only record path bias information for circuits that have completed
5125 *two* hops. Assuming end-to-end tagging is the attack vector, this
5126 makes us more resilient to ambient circuit failure without any
5127 detection capability loss.
5129 o Minor bugfixes (log messages):
5130 - Rate-limit the "No circuits are opened. Relaxed timeout for a
5131 circuit with channel state open..." message to once per hour to
5132 keep it from filling the notice logs. Mitigates bug 7799 but does
5133 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
5134 - Avoid spurious warnings when configuring multiple client ports of
5135 which only some are nonlocal. Previously, we had claimed that some
5136 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
5139 o Code simplifications and refactoring:
5140 - Get rid of a couple of harmless clang warnings, where we compared
5141 enums to ints. These warnings are newly introduced in clang 3.2.
5142 - Split the onion.c file into separate modules for the onion queue
5143 and the different handshakes it supports.
5144 - Remove the marshalling/unmarshalling code for sending requests to
5145 cpuworkers over a socket, and instead just send structs. The
5146 recipient will always be the same Tor binary as the sender, so
5147 any encoding is overkill.
5150 Changes in version 0.2.4.7-alpha - 2012-12-24
5151 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
5152 directory mirrors for more robust bootstrapping; fixes more issues where
5153 clients with changing network conditions refuse to make any circuits;
5154 adds initial support for exiting to IPv6 addresses; resumes being able
5155 to update our GeoIP database, and includes the geoip6 file this time;
5156 turns off the client-side DNS cache by default due to privacy risks;
5157 and fixes a variety of other issues.
5159 o Major features (client resilience):
5160 - Add a new "FallbackDir" torrc option to use when we can't use
5161 a directory mirror from the consensus (either because we lack a
5162 consensus, or because they're all down). Currently, all authorities
5163 are fallbacks by default, and there are no other default fallbacks,
5164 but that will change. This option will allow us to give clients a
5165 longer list of servers to try to get a consensus from when first
5166 connecting to the Tor network, and thereby reduce load on the
5167 directory authorities. Implements proposal 206, "Preconfigured
5168 directory sources for bootstrapping". We also removed the old
5169 "FallbackNetworkstatus" option, since we never got it working well
5170 enough to use it. Closes bug 572.
5171 - If we have no circuits open, use a relaxed timeout (the
5172 95-percentile cutoff) until a circuit succeeds. This heuristic
5173 should allow Tor to succeed at building circuits even when the
5174 network connection drastically changes. Should help with bug 3443.
5176 o Major features (IPv6):
5177 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
5178 connectivity, then set the IPv6Exit flag to 1. Also make sure your
5179 exit policy reads as you would like: the address * applies to all
5180 address families, whereas *4 is IPv4 address only, and *6 is IPv6
5181 addresses only. On the client side, you'll need to wait until the
5182 authorities have upgraded, wait for enough exits to support IPv6,
5183 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
5184 ticket 5547, implements proposal 117 as revised in proposal 208.
5186 We DO NOT recommend that clients with actual anonymity needs start
5187 using IPv6 over Tor yet, since not enough exits support it yet.
5189 o Major features (geoip database):
5190 - Maxmind began labelling Tor relays as being in country "A1",
5191 which breaks by-country node selection inside Tor. Now we use a
5192 script to replace "A1" ("Anonymous Proxy") entries in our geoip
5193 file with real country codes. This script fixes about 90% of "A1"
5194 entries automatically and uses manual country code assignments to
5195 fix the remaining 10%. See src/config/README.geoip for details.
5196 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
5197 Country database, as modified above.
5199 o Major bugfixes (client-side DNS):
5200 - Turn off the client-side DNS cache by default. Updating and using
5201 the DNS cache is now configurable on a per-client-port
5202 level. SOCKSPort, DNSPort, etc lines may now contain
5203 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
5204 cache these types of DNS answers when we receive them from an
5205 exit node in response to an application request on this port, and
5206 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
5207 cached DNS answers of these types, we shouldn't use them. It's
5208 potentially risky to use cached DNS answers at the client, since
5209 doing so can indicate to one exit what answers we've gotten
5210 for DNS lookups in the past. With IPv6, this becomes especially
5211 problematic. Using cached DNS answers for requests on the same
5212 circuit would present less linkability risk, since all traffic
5213 on a circuit is already linkable, but it would also provide
5214 little performance benefit: the exit node caches DNS replies
5215 too. Implements a simplified version of Proposal 205. Implements
5218 o Major bugfixes (other):
5219 - Alter circuit build timeout measurement to start at the point
5220 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
5221 initialization). This should make our timeout measurements more
5222 uniform. Previously, we were sometimes including ORconn setup time
5223 in our circuit build time measurements. Should resolve bug 3443.
5224 - Fix an assertion that could trigger in hibernate_go_dormant() when
5225 closing an or_connection_t: call channel_mark_for_close() rather
5226 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
5228 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
5229 7655; bugfix on 0.2.4.6-alpha.
5232 - Add a new torrc option "ServerTransportListenAddr" to let bridge
5233 operators select the address where their pluggable transports will
5234 listen for connections. Resolves ticket 7013.
5235 - Allow an optional $ before the node identity digest in the
5236 controller command GETINFO ns/id/<identity>, for consistency with
5237 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
5238 - Log packaged cell fullness as part of the heartbeat message.
5239 Diagnosis to try to determine the extent of bug 7743.
5241 o Minor features (IPv6):
5242 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
5243 prefer to hand out virtual IPv6 addresses, since there are more of
5244 them and we can't run out. To override this behavior and make IPv4
5245 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
5246 or DNSPort you're using for resolving. Implements ticket 7571.
5247 - AutomapHostsOnResolve responses are now randomized, to avoid
5248 annoying situations where Tor is restarted and applications
5249 connect to the wrong addresses.
5250 - Never try more than 1000 times to pick a new virtual address when
5251 AutomapHostsOnResolve is set. That's good enough so long as we
5252 aren't close to handing out our entire virtual address space;
5253 if you're getting there, it's best to switch to IPv6 virtual
5257 - The ADDRMAP command can no longer generate an ill-formed error
5258 code on a failed MAPADDRESS. It now says "internal" rather than
5259 an English sentence fragment with spaces in the middle. Bugfix on
5261 - Fix log messages and comments to avoid saying "GMT" when we mean
5262 "UTC". Fixes bug 6113.
5263 - Compile on win64 using mingw64. Fixes bug 7260; patches from
5265 - Fix a crash when debugging unit tests on Windows: deallocate a
5266 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
5267 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
5270 - The DirServer option is now DirAuthority, for consistency with
5271 current naming patterns. You can still use the old DirServer form.
5273 o Code simplification and refactoring:
5274 - Move the client-side address-map/virtual-address/DNS-cache code
5275 out of connection_edge.c into a new addressmap.c module.
5276 - Remove unused code for parsing v1 directories and "running routers"
5277 documents. Fixes bug 6887.
5280 Changes in version 0.2.3.25 - 2012-11-19
5281 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
5282 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
5283 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
5284 programmer, and friend. Unstinting in his dedication to the cause of
5285 freedom, he inspired and helped many of us as we began our work on
5286 anonymity, and inspires us still. Please honor his memory by writing
5287 software to protect people's freedoms, and by helping others to do so.
5289 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
5290 significantly reduced directory overhead (via microdescriptors),
5291 enormous crypto performance improvements for fast relays on new
5292 enough hardware, a new v3 TLS handshake protocol that can better
5293 resist fingerprinting, support for protocol obfuscation plugins (aka
5294 pluggable transports), better scalability for hidden services, IPv6
5295 support for bridges, performance improvements like allowing clients
5296 to skip the first round-trip on the circuit ("optimistic data") and
5297 refilling token buckets more often, a new "stream isolation" design
5298 to isolate different applications on different circuits, and many
5299 stability, security, and privacy fixes.
5302 - Tor tries to wipe potentially sensitive data after using it, so
5303 that if some subsequent security failure exposes Tor's memory,
5304 the damage will be limited. But we had a bug where the compiler
5305 was eliminating these wipe operations when it decided that the
5306 memory was no longer visible to a (correctly running) program,
5307 hence defeating our attempt at defense in depth. We fix that
5308 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
5309 is unlikely to optimize away. Future versions of Tor may use
5310 a less ridiculously heavy approach for this. Fixes bug 7352.
5311 Reported in an article by Andrey Karpov.
5314 - Fix a harmless bug when opting against publishing a relay descriptor
5315 because DisableNetwork is set. Fixes bug 7464; bugfix on
5319 Changes in version 0.2.4.6-alpha - 2012-11-13
5320 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
5321 makes our defense-in-depth memory wiping more reliable, and begins to
5322 count IPv6 addresses in bridge statistics,
5325 - Fix an assertion failure that could occur when closing a connection
5326 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
5328 - Tor tries to wipe potentially sensitive data after using it, so
5329 that if some subsequent security failure exposes Tor's memory,
5330 the damage will be limited. But we had a bug where the compiler
5331 was eliminating these wipe operations when it decided that the
5332 memory was no longer visible to a (correctly running) program,
5333 hence defeating our attempt at defense in depth. We fix that
5334 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
5335 is unlikely to optimize away. Future versions of Tor may use
5336 a less ridiculously heavy approach for this. Fixes bug 7352.
5337 Reported in an article by Andrey Karpov.
5340 - Add GeoIP database for IPv6 addresses. The new config option
5342 - Bridge statistics now count bridge clients connecting over IPv6:
5343 bridge statistics files now list "bridge-ip-versions" and
5344 extra-info documents list "geoip6-db-digest". The control protocol
5345 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
5346 implementation by "shkoo", addressing ticket 5055.
5349 - Warn when we are binding low ports when hibernation is enabled;
5350 previously we had warned when we were _advertising_ low ports with
5351 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
5352 - Fix a harmless bug when opting against publishing a relay descriptor
5353 because DisableNetwork is set. Fixes bug 7464; bugfix on
5355 - Add warning message when a managed proxy dies during configuration.
5356 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
5357 - Fix a linking error when building tor-fw-helper without miniupnp.
5358 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
5359 - Check for closing an or_connection_t without going through correct
5360 channel functions; emit a warning and then call
5361 connection_or_close_for_error() so we don't assert as in bugs 7212
5363 - Compile correctly on compilers without C99 designated initializer
5364 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
5365 - Avoid a possible assert that can occur when channel_send_destroy() is
5366 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
5367 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
5368 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
5369 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
5370 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
5372 o Code simplification and refactoring:
5373 - Start using OpenBSD's implementation of queue.h, so that we don't
5374 need to hand-roll our own pointer and list structures whenever we
5375 need them. (We can't rely on a sys/queue.h, since some operating
5376 systems don't have them, and the ones that do have them don't all
5377 present the same extensions.)
5380 Changes in version 0.2.4.5-alpha - 2012-10-25
5381 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
5382 two important security vulnerabilities that could lead to remotely
5383 triggerable relay crashes, fix a major bug that was preventing clients
5384 from choosing suitable exit nodes, and refactor some of our code.
5386 o Major bugfixes (security, also in 0.2.3.24-rc):
5387 - Fix a group of remotely triggerable assertion failures related to
5388 incorrect link protocol negotiation. Found, diagnosed, and fixed
5389 by "some guy from France". Fix for CVE-2012-2250; bugfix on
5391 - Fix a denial of service attack by which any directory authority
5392 could crash all the others, or by which a single v2 directory
5393 authority could crash everybody downloading v2 directory
5394 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
5396 o Major bugfixes (also in 0.2.3.24-rc):
5397 - When parsing exit policy summaries from microdescriptors, we had
5398 previously been ignoring the last character in each one, so that
5399 "accept 80,443,8080" would be treated by clients as indicating
5400 a node that allows access to ports 80, 443, and 808. That would
5401 lead to clients attempting connections that could never work,
5402 and ignoring exit nodes that would support their connections. Now
5403 clients parse these exit policy summaries correctly. Fixes bug 7192;
5404 bugfix on 0.2.3.1-alpha.
5406 o Minor bugfixes (also in 0.2.3.24-rc):
5407 - Clients now consider the ClientRejectInternalAddresses config option
5408 when using a microdescriptor consensus stanza to decide whether
5409 an exit relay would allow exiting to an internal address. Fixes
5410 bug 7190; bugfix on 0.2.3.1-alpha.
5413 - Only disable TLS session ticket support when running as a TLS
5414 server. Now clients will blend better with regular Firefox
5415 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
5417 o Code simplification and refactoring:
5418 - Start using OpenBSD's implementation of queue.h (originally by
5420 - Move the entry node code from circuitbuild.c to its own file.
5421 - Move the circuit build timeout tracking code from circuitbuild.c
5425 Changes in version 0.2.3.24-rc - 2012-10-25
5426 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
5427 could lead to remotely triggerable relay crashes, and fixes
5428 a major bug that was preventing clients from choosing suitable exit
5431 o Major bugfixes (security):
5432 - Fix a group of remotely triggerable assertion failures related to
5433 incorrect link protocol negotiation. Found, diagnosed, and fixed
5434 by "some guy from France". Fix for CVE-2012-2250; bugfix on
5436 - Fix a denial of service attack by which any directory authority
5437 could crash all the others, or by which a single v2 directory
5438 authority could crash everybody downloading v2 directory
5439 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
5442 - When parsing exit policy summaries from microdescriptors, we had
5443 previously been ignoring the last character in each one, so that
5444 "accept 80,443,8080" would be treated by clients as indicating
5445 a node that allows access to ports 80, 443, and 808. That would
5446 lead to clients attempting connections that could never work,
5447 and ignoring exit nodes that would support their connections. Now
5448 clients parse these exit policy summaries correctly. Fixes bug 7192;
5449 bugfix on 0.2.3.1-alpha.
5452 - Clients now consider the ClientRejectInternalAddresses config option
5453 when using a microdescriptor consensus stanza to decide whether
5454 an exit relay would allow exiting to an internal address. Fixes
5455 bug 7190; bugfix on 0.2.3.1-alpha.
5458 Changes in version 0.2.4.4-alpha - 2012-10-20
5459 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
5460 vulnerability introduced by a change in OpenSSL, fixes a remotely
5461 triggerable assert, and adds new channel_t and circuitmux_t abstractions
5462 that will make it easier to test new connection transport and cell
5463 scheduling algorithms.
5465 o New directory authorities (also in 0.2.3.23-rc):
5466 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
5467 authority. Closes ticket 5749.
5469 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
5470 - Disable TLS session tickets. OpenSSL's implementation was giving
5471 our TLS session keys the lifetime of our TLS context objects, when
5472 perfect forward secrecy would want us to discard anything that
5473 could decrypt a link connection as soon as the link connection
5474 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
5475 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
5476 - Discard extraneous renegotiation attempts once the V3 link
5477 protocol has been initiated. Failure to do so left us open to
5478 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
5479 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
5481 o Internal abstraction features:
5482 - Introduce new channel_t abstraction between circuits and
5483 or_connection_t to allow for implementing alternate OR-to-OR
5484 transports. A channel_t is an abstract object which can either be a
5485 cell-bearing channel, which is responsible for authenticating and
5486 handshaking with the remote OR and transmitting cells to and from
5487 it, or a listening channel, which spawns new cell-bearing channels
5488 at the request of remote ORs. Implements part of ticket 6465.
5489 - Also new is the channel_tls_t subclass of channel_t, adapting it
5490 to the existing or_connection_t code. The V2/V3 protocol handshaking
5491 code which formerly resided in command.c has been moved below the
5492 channel_t abstraction layer and may be found in channeltls.c now.
5493 Implements the rest of ticket 6465.
5494 - Introduce new circuitmux_t storing the queue of circuits for
5495 a channel; this encapsulates and abstracts the queue logic and
5496 circuit selection policy, and allows the latter to be overridden
5497 easily by switching out a policy object. The existing EWMA behavior
5498 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
5500 o Required libraries:
5501 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
5502 strongly recommended.
5505 - Warn users who run hidden services on a Tor client with
5506 UseEntryGuards disabled that their hidden services will be
5507 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
5508 attack which motivated Tor to support entry guards in the first
5509 place). Resolves ticket 6889.
5510 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
5511 dhill. Resolves ticket 6982.
5512 - Option OutboundBindAddress can be specified multiple times and
5513 accepts IPv6 addresses. Resolves ticket 6876.
5515 o Minor bugfixes (also in 0.2.3.23-rc):
5516 - Don't serve or accept v2 hidden service descriptors over a
5517 relay's DirPort. It's never correct to do so, and disabling it
5518 might make it more annoying to exploit any bugs that turn up in the
5519 descriptor-parsing code. Fixes bug 7149.
5520 - Fix two cases in src/or/transports.c where we were calling
5521 fmt_addr() twice in a parameter list. Bug found by David
5522 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
5523 - Fix memory leaks whenever we logged any message about the "path
5524 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
5525 - When relays refuse a "create" cell because their queue of pending
5526 create cells is too big (typically because their cpu can't keep up
5527 with the arrival rate), send back reason "resource limit" rather
5528 than reason "internal", so network measurement scripts can get a
5529 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
5532 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
5533 - Free some more still-in-use memory at exit, to make hunting for
5534 memory leaks easier. Resolves bug 7029.
5535 - When a Tor client gets a "truncated" relay cell, the first byte of
5536 its payload specifies why the circuit was truncated. We were
5537 ignoring this 'reason' byte when tearing down the circuit, resulting
5538 in the controller not being told why the circuit closed. Now we
5539 pass the reason from the truncated cell to the controller. Bugfix
5540 on 0.1.2.3-alpha; fixes bug 7039.
5541 - Downgrade "Failed to hand off onionskin" messages to "debug"
5542 severity, since they're typically redundant with the "Your computer
5543 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
5544 - Make clients running with IPv6 bridges connect over IPv6 again,
5545 even without setting new config options ClientUseIPv6 and
5546 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
5547 - Use square brackets around IPv6 addresses in numerous places
5548 that needed them, including log messages, HTTPS CONNECT proxy
5549 requests, TransportProxy statefile entries, and pluggable transport
5550 extra-info lines. Fixes bug 7011; patch by David Fifield.
5552 o Code refactoring and cleanup:
5553 - Source files taken from other packages now reside in src/ext;
5554 previously they were scattered around the rest of Tor.
5555 - Avoid use of reserved identifiers in our C code. The C standard
5556 doesn't like us declaring anything that starts with an
5557 underscore, so let's knock it off before we get in trouble. Fix
5558 for bug 1031; bugfix on the first Tor commit.
5561 Changes in version 0.2.3.23-rc - 2012-10-20
5562 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
5563 vulnerability introduced by a change in OpenSSL, and fixes a variety
5564 of smaller bugs in preparation for the release.
5566 o New directory authorities:
5567 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
5568 authority. Closes ticket 5749.
5570 o Major bugfixes (security/privacy):
5571 - Disable TLS session tickets. OpenSSL's implementation was giving
5572 our TLS session keys the lifetime of our TLS context objects, when
5573 perfect forward secrecy would want us to discard anything that
5574 could decrypt a link connection as soon as the link connection
5575 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
5576 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
5577 - Discard extraneous renegotiation attempts once the V3 link
5578 protocol has been initiated. Failure to do so left us open to
5579 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
5580 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
5583 - Fix a possible crash bug when checking for deactivated circuits
5584 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
5585 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
5587 o Minor bugfixes (on 0.2.3.x):
5588 - Fix two cases in src/or/transports.c where we were calling
5589 fmt_addr() twice in a parameter list. Bug found by David
5590 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
5591 - Convert an assert in the pathbias code to a log message. The assert
5592 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
5593 bugfix on 0.2.3.17-beta.
5594 - Fix memory leaks whenever we logged any message about the "path
5595 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
5597 o Minor bugfixes (on 0.2.2.x and earlier):
5598 - Don't serve or accept v2 hidden service descriptors over a relay's
5599 DirPort. It's never correct to do so, and disabling it might
5600 make it more annoying to exploit any bugs that turn up in the
5601 descriptor-parsing code. Fixes bug 7149.
5602 - When relays refuse a "create" cell because their queue of pending
5603 create cells is too big (typically because their cpu can't keep up
5604 with the arrival rate), send back reason "resource limit" rather
5605 than reason "internal", so network measurement scripts can get a
5606 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
5607 - Correct file sizes when reading binary files on Cygwin, to avoid
5608 a bug where Tor would fail to read its state file. Fixes bug 6844;
5609 bugfix on 0.1.2.7-alpha.
5610 - Avoid undefined behavior when parsing the list of supported
5611 rendezvous/introduction protocols in a hidden service descriptor.
5612 Previously, Tor would have confused (as-yet-unused) protocol version
5613 numbers greater than 32 with lower ones on many platforms. Fixes
5614 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
5616 o Documentation fixes:
5617 - Clarify that hidden services are TCP only. Fixes bug 6024.
5620 Changes in version 0.2.4.3-alpha - 2012-09-22
5621 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
5622 assertion, resumes letting relays test reachability of their DirPort,
5623 and cleans up a bunch of smaller bugs.
5626 - Fix an assertion failure in tor_timegm() that could be triggered
5627 by a badly formatted directory object. Bug found by fuzzing with
5628 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5631 - Fix a possible crash bug when checking for deactivated circuits
5632 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
5633 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
5634 - Allow routers to detect that their own DirPorts are running. When
5635 we removed support for versions_supports_begindir, we also
5636 accidentally removed the mechanism we used to self-test our
5637 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
5638 bugfix on 0.2.4.2-alpha.
5640 o Security features:
5641 - Switch to a completely time-invariant approach for picking nodes
5642 weighted by bandwidth. Our old approach would run through the
5643 part of the loop after it had made its choice slightly slower
5644 than it ran through the part of the loop before it had made its
5645 choice. Addresses ticket 6538.
5646 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
5647 by tor2web clients allows hidden services to identify tor2web
5648 clients through their repeated selection of the same rendezvous
5649 and introduction point circuit endpoints (their guards). Resolves
5653 - Enable Tor to read configuration, state, and key information from
5654 a FIFO. Previously Tor would only read from files with a positive
5655 stat.st_size. Code from meejah; fixes bug 6044.
5658 - Correct file sizes when reading binary files on Cygwin, to avoid
5659 a bug where Tor would fail to read its state file. Fixes bug 6844;
5660 bugfix on 0.1.2.7-alpha.
5661 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
5662 bugfix on 0.2.0.3-alpha.
5663 - When complaining about a client port on a public address, log
5664 which address we're complaining about. Fixes bug 4020; bugfix on
5665 0.2.3.3-alpha. Patch by Tom Fitzhenry.
5666 - Convert an assert in the pathbias code to a log message. The assert
5667 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
5668 bugfix on 0.2.3.17-beta.
5669 - Our new buildsystem was overzealous about rebuilding manpages: it
5670 would rebuild them all whenever any one of them changed. Now our
5671 dependency checking should be correct. Fixes bug 6843; bugfix on
5673 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
5674 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
5675 - Correct log printout about which address family is preferred
5676 when connecting to a bridge with both an IPv4 and IPv6 OR port.
5677 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
5679 o Minor bugfixes (code cleanliness):
5680 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
5681 with large values. This situation was untriggered, but nevertheless
5682 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
5683 - Reject consensus votes with more than 64 known-flags. We aren't even
5684 close to that limit yet, and our code doesn't handle it correctly.
5685 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
5686 - Avoid undefined behavior when parsing the list of supported
5687 rendezvous/introduction protocols in a hidden service descriptor.
5688 Previously, Tor would have confused (as-yet-unused) protocol version
5689 numbers greater than 32 with lower ones on many platforms. Fixes
5690 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
5691 - Fix handling of rendezvous client authorization types over 8.
5692 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
5693 - Fix building with older versions of GCC (2.95, for one) that don't
5694 like preprocessor directives inside macro arguments. Found by
5695 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
5696 - Switch weighted node selection rule from using a list of doubles
5697 to using a list of int64_t. This change should make the process
5698 slightly easier to debug and maintain. Needed to finish ticket 6538.
5700 o Code simplification and refactoring:
5701 - Move the generic "config" code into a new file, and have "config.c"
5702 hold only torrc- and state-related code. Resolves ticket 6823.
5703 - Move the core of our "choose a weighted element at random" logic
5704 into its own function, and give it unit tests. Now the logic is
5705 testable, and a little less fragile too.
5706 - Removed the testing_since field of node_t, which hasn't been used
5707 for anything since 0.2.0.9-alpha.
5709 o Documentation fixes:
5710 - Clarify that hidden services are TCP only. Fixes bug 6024.
5711 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
5715 Changes in version 0.2.3.22-rc - 2012-09-11
5716 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
5720 - Fix an assertion failure in tor_timegm() that could be triggered
5721 by a badly formatted directory object. Bug found by fuzzing with
5722 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5725 - Avoid segfault when starting up having run with an extremely old
5726 version of Tor and parsing its state file. Fixes bug 6801; bugfix
5730 Changes in version 0.2.2.39 - 2012-09-11
5731 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
5735 - Fix an assertion failure in tor_timegm() that could be triggered
5736 by a badly formatted directory object. Bug found by fuzzing with
5737 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5738 - Do not crash when comparing an address with port value 0 to an
5739 address policy. This bug could have been used to cause a remote
5740 assertion failure by or against directory authorities, or to
5741 allow some applications to crash clients. Fixes bug 6690; bugfix
5745 Changes in version 0.2.4.2-alpha - 2012-09-10
5746 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
5747 raises the default rate limiting even more, and makes the bootstrapping
5748 log messages less noisy.
5751 - Automatically forward the TCP ports of pluggable transport
5752 proxies using tor-fw-helper if PortForwarding is enabled. Implements
5756 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
5757 to 1GB/1GB. The previous defaults were intended to be "basically
5758 infinite", but it turns out they're now limiting our 100mbit+
5759 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
5760 last time we raised it).
5763 - Detect when we're running with a version of OpenSSL other than the
5764 one we compiled with. This has occasionally given people hard-to-
5766 - Log fewer lines at level "notice" about our OpenSSL and Libevent
5767 versions and capabilities when everything is going right. Resolves
5768 part of ticket 6736.
5769 - Directory authorities no long accept descriptors for any version of
5770 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
5771 These versions are insecure, unsupported, or both. Implements
5775 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
5776 to start with a triple-underscore so the controller won't touch it.
5777 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
5778 - Avoid segfault when starting up having run with an extremely old
5779 version of Tor and parsing its state file. Fixes bug 6801; bugfix
5781 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
5782 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
5783 - Don't follow the NULL pointer if microdescriptor generation fails.
5784 (This does not appear to be triggerable, but it's best to be safe.)
5785 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
5786 - Fix mis-declared dependencies on src/common/crypto.c and
5787 src/or/tor_main.c that could break out-of-tree builds under some
5788 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
5789 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
5790 6778; bugfix on 0.2.4.1-alpha.
5791 - Fix a harmless (in this case) build warning for implicitly
5792 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
5795 - Now that all versions before 0.2.2.x are disallowed, we no longer
5796 need to work around their missing features. Thus we can remove a
5797 bunch of compatibility code.
5800 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
5801 TCP ports to forward. In the past it only accepted two ports:
5802 the ORPort and the DirPort.
5805 Changes in version 0.2.4.1-alpha - 2012-09-05
5806 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
5807 bridgedb; lets relays use IPv6 addresses and directory authorities
5808 advertise them; and switches to a cleaner build interface.
5810 This is the first alpha release in a new series, so expect there to
5811 be bugs. Users who would rather test out a more stable branch should
5812 stay with 0.2.3.x for now.
5814 o Major features (bridges):
5815 - Bridges now report the pluggable transports they support to the
5816 bridge authority, so it can pass the supported transports on to
5817 bridgedb and/or eventually do reachability testing. Implements
5820 o Major features (IPv6):
5821 - Bridge authorities now accept IPv6 bridge addresses and include
5822 them in network status documents. Implements ticket 5534.
5823 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
5824 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
5825 to happen. Implements ticket 5535.
5826 - All kind of relays, not just bridges, can now advertise an IPv6
5827 OR port. Implements ticket 6362.
5828 - Directory authorities vote on IPv6 OR ports using the new consensus
5829 method 14. Implements ticket 6363.
5831 o Major features (build):
5832 - Switch to a nonrecursive Makefile structure. Now instead of each
5833 Makefile.am invoking other Makefile.am's, there is a master
5834 Makefile.am that includes the others. This change makes our build
5835 process slightly more maintainable, and improves parallelism for
5836 building with make -j. Original patch by Stewart Smith; various
5837 fixes by Jim Meyering.
5838 - Where available, we now use automake's "silent" make rules by
5839 default, so that warnings are easier to spot. You can get the old
5840 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
5842 o Minor features (code security and spec conformance):
5843 - Clear keys and key-derived material left on the stack in
5844 rendservice.c and rendclient.c. Check return value of
5845 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
5846 These fixes should make us more forward-secure against cold-boot
5847 attacks and the like. Fixes bug 2385.
5848 - Reject EXTEND cells sent to nonexistent streams. According to the
5849 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
5850 we were only checking for stream IDs that were currently in use.
5851 Found while hunting for more instances of bug 6271. Bugfix on
5852 0.0.2pre8, which introduced incremental circuit construction.
5854 o Minor features (streamlining);
5855 - No longer include the "opt" prefix when generating routerinfos
5856 or v2 directories: it has been needless since Tor 0.1.2. Closes
5858 - Remove some now-needless code that tried to aggressively flush
5859 OR connections as data was added to them. Since 0.2.0.1-alpha, our
5860 cell queue logic has saved us from the failure mode that this code
5861 was supposed to prevent. Removing this code will limit the number
5862 of baroque control flow paths through Tor's network logic. Reported
5863 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
5865 o Minor features (controller):
5866 - Add a "GETINFO signal/names" control port command. Implements
5868 - Provide default values for all options via "GETINFO config/defaults".
5869 Implements ticket 4971.
5871 o Minor features (IPv6):
5872 - New config option "AuthDirHasIPv6Connectivity 1" that directory
5873 authorities should set if they have IPv6 connectivity and want to
5874 do reachability tests for IPv6 relays. Implements feature 5974.
5875 - A relay with an IPv6 OR port now sends that address in NETINFO
5876 cells (in addition to its other address). Implements ticket 6364.
5878 o Minor features (log messages):
5879 - Omit the first heartbeat log message, because it never has anything
5880 useful to say, and it clutters up the bootstrapping messages.
5881 Resolves ticket 6758.
5882 - Don't log about reloading the microdescriptor cache at startup. Our
5883 bootstrap warnings are supposed to tell the user when there's a
5884 problem, and our bootstrap notices say when there isn't. Resolves
5885 ticket 6759; bugfix on 0.2.2.6-alpha.
5886 - Don't log "I learned some more directory information" when we're
5887 reading cached directory information. Reserve it for when new
5888 directory information arrives in response to a fetch. Resolves
5890 - Prevent rounding error in path bias counts when scaling
5891 them down, and use the correct scale factor default. Also demote
5892 some path bias related log messages down a level and make others
5893 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
5894 - We no longer warn so much when generating manpages from their
5897 o Code simplifications and refactoring:
5898 - Enhance our internal sscanf replacement so that we can eliminate
5899 the last remaining uses of the system sscanf. (Though those uses
5900 of sscanf were safe, sscanf itself is generally error prone, so
5901 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
5903 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
5904 - Move last_reachable and testing_since from routerinfo_t to node_t.
5905 Implements ticket 5529.
5906 - Add replaycache_t structure, functions and unit tests, then refactor
5907 rend_service_introduce() to be more clear to read, improve, debug,
5908 and test. Resolves bug 6177.
5909 - Finally remove support for malloc_good_size and malloc_usable_size.
5910 We had hoped that these functions would let us eke a little more
5911 memory out of our malloc implementation. Unfortunately, the only
5912 implementations that provided these functions are also ones that
5913 are already efficient about not overallocation: they never got us
5914 more than 7 or so bytes per allocation. Removing them saves us a
5915 little code complexity and a nontrivial amount of build complexity.
5918 - Tor maintainers now require Automake version 1.9 or later to build
5919 Tor from the Git repository. (Automake is not required when building
5920 from a source distribution.)
5923 Changes in version 0.2.3.21-rc - 2012-09-05
5924 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
5925 series. It fixes a trio of potential security bugs, fixes a bug where
5926 we were leaving some of the fast relays out of the microdescriptor
5927 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
5928 and cleans up other smaller issues.
5930 o Major bugfixes (security):
5931 - Tear down the circuit if we get an unexpected SENDME cell. Clients
5932 could use this trick to make their circuits receive cells faster
5933 than our flow control would have allowed, or to gum up the network,
5934 or possibly to do targeted memory denial-of-service attacks on
5935 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
5936 from July 2002, before the release of Tor 0.0.0. We had committed
5937 this patch previously, but we had to revert it because of bug 6271.
5938 Now that 6271 is fixed, this patch appears to work.
5939 - Reject any attempt to extend to an internal address. Without
5940 this fix, a router could be used to probe addresses on an internal
5941 network to see whether they were accepting connections. Fixes bug
5942 6710; bugfix on 0.0.8pre1.
5943 - Do not crash when comparing an address with port value 0 to an
5944 address policy. This bug could have been used to cause a remote
5945 assertion failure by or against directory authorities, or to
5946 allow some applications to crash clients. Fixes bug 6690; bugfix
5950 - Remove the upper bound on microdescriptor length. We were hitting
5951 the limit for routers with complex exit policies or family
5952 declarations, causing clients to not use them. Fixes the first
5953 piece of bug 6404; fix on 0.2.2.6-alpha.
5954 - Detect "ORPort 0" as meaning, uniformly, that we're not running
5955 as a relay. Previously, some of our code would treat the presence
5956 of any ORPort line as meaning that we should act like a relay,
5957 even though our new listener code would correctly not open any
5958 ORPorts for ORPort 0. Similar bugs in other Port options are also
5959 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
5962 - Avoid a pair of double-free and use-after-mark bugs that can
5963 occur with certain timings in canceled and re-received DNS
5964 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
5965 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
5966 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
5967 - Allow one-hop directory fetching circuits the full "circuit build
5968 timeout" period, rather than just half of it, before failing them
5969 and marking the relay down. This fix should help reduce cases where
5970 clients declare relays (or worse, bridges) unreachable because
5971 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
5972 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
5974 - Authorities no longer include any router in their microdescriptor
5975 consensuses for which they couldn't generate or agree on a
5976 microdescriptor. Fixes the second piece of bug 6404; fix on
5978 - Detect and reject attempts to specify both "FooPort" and
5979 "FooPort 0" in the same configuration domain. (It's still okay
5980 to have a FooPort in your configuration file, and use "FooPort 0"
5981 on the command line to disable it.) Fixes the second half of bug
5982 6507; bugfix on 0.2.3.3-alpha.
5983 - Make wildcarded addresses (that is, ones beginning with "*.") work
5984 when provided via the controller's MapAddress command. Previously,
5985 they were accepted, but we never actually noticed that they were
5986 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
5987 - Avoid crashing on a malformed state file where EntryGuardPathBias
5988 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
5989 - Add a (probably redundant) memory clear between iterations of
5990 the router status voting loop, to prevent future coding errors
5991 where data might leak between iterations of the loop. Resolves
5994 o Minor bugfixes (log messages):
5995 - Downgrade "set buildtimeout to low value" messages to "info"
5996 severity; they were never an actual problem, there was never
5997 anything reasonable to do about them, and they tended to spam logs
5998 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
5999 - Downgrade path-bias warning messages to "info". We'll try to get
6000 them working better in 0.2.4. Add internal circuit construction
6001 state to protect against the noisy warn message "Unexpectedly high
6002 circuit_successes". Also add some additional rate-limited notice
6003 messages to help determine the root cause of the warn. Fixes bug
6004 6475. Bugfix against 0.2.3.17-beta.
6005 - Move log message when unable to find a microdesc in a routerstatus
6006 entry to parse time. Previously we'd spam this warning every time
6007 we tried to figure out which microdescriptors to download. Fixes
6008 the third piece of bug 6404; fix on 0.2.3.18-rc.
6011 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
6012 change when the authority is deciding whether to accept a newly
6013 uploaded descriptor. Implements ticket 6423.
6014 - Add missing documentation for consensus and microdesc files.
6015 Resolves ticket 6732.
6018 Changes in version 0.2.2.38 - 2012-08-12
6019 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
6020 attack that could in theory leak path information.
6023 - Avoid an uninitialized memory read when reading a vote or consensus
6024 document that has an unrecognized flavor name. This read could
6025 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
6026 - Try to leak less information about what relays a client is
6027 choosing to a side-channel attacker. Previously, a Tor client would
6028 stop iterating through the list of available relays as soon as it
6029 had chosen one, thus finishing a little earlier when it picked
6030 a router earlier in the list. If an attacker can recover this
6031 timing information (nontrivial but not proven to be impossible),
6032 they could learn some coarse-grained information about which relays
6033 a client was picking (middle nodes in particular are likelier to
6034 be affected than exits). The timing attack might be mitigated by
6035 other factors (see bug 6537 for some discussion), but it's best
6036 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
6039 Changes in version 0.2.3.20-rc - 2012-08-05
6040 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
6041 series. It fixes a pair of code security bugs and a potential anonymity
6042 issue, updates our RPM spec files, and cleans up other smaller issues.
6045 - Avoid read-from-freed-memory and double-free bugs that could occur
6046 when a DNS request fails while launching it. Fixes bug 6480;
6047 bugfix on 0.2.0.1-alpha.
6048 - Avoid an uninitialized memory read when reading a vote or consensus
6049 document that has an unrecognized flavor name. This read could
6050 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
6051 - Try to leak less information about what relays a client is
6052 choosing to a side-channel attacker. Previously, a Tor client would
6053 stop iterating through the list of available relays as soon as it
6054 had chosen one, thus finishing a little earlier when it picked
6055 a router earlier in the list. If an attacker can recover this
6056 timing information (nontrivial but not proven to be impossible),
6057 they could learn some coarse-grained information about which relays
6058 a client was picking (middle nodes in particular are likelier to
6059 be affected than exits). The timing attack might be mitigated by
6060 other factors (see bug 6537 for some discussion), but it's best
6061 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
6064 - Try to make the warning when giving an obsolete SOCKSListenAddress
6065 a little more useful.
6066 - Terminate active server managed proxies if Tor stops being a
6067 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
6068 - Provide a better error message about possible OSX Asciidoc failure
6069 reasons. Fixes bug 6436.
6070 - Warn when Tor is configured to use accounting in a way that can
6071 link a hidden service to some other hidden service or public
6072 address. Resolves ticket 6490.
6075 - Check return value of fputs() when writing authority certificate
6076 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
6077 - Ignore ServerTransportPlugin lines when Tor is not configured as
6078 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
6079 - When disabling guards for having too high a proportion of failed
6080 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
6084 - Update our default RPM spec files to work with mock and rpmbuild
6085 on RHEL/Fedora. They have an updated set of dependencies and
6086 conflicts, a fix for an ancient typo when creating the "_tor"
6087 user, and better instructions. Thanks to Ondrej Mikle for the
6088 patch series. Fixes bug 6043.
6091 - Make it possible to set the TestingTorNetwork configuration
6092 option using AlternateDirAuthority and AlternateBridgeAuthority
6093 as an alternative to setting DirServer. Addresses ticket 6377.
6096 - Clarify the documentation for the Alternate*Authority options.
6098 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
6100 o Code simplification and refactoring:
6101 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
6102 10 lines. Also, don't nest them. Doing so in the past has
6103 led to hard-to-debug code. The new style is to use the
6104 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
6107 Changes in version 0.2.3.19-rc - 2012-07-06
6108 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
6109 series. It fixes the compile on Windows, reverts to a GeoIP database
6110 that isn't as broken, and fixes a flow control bug that has been around
6111 since the beginning of Tor.
6114 - Fix a bug handling SENDME cells on nonexistent streams that could
6115 result in bizarre window values. Report and patch contributed
6116 pseudonymously. Fixes part of bug 6271. This bug was introduced
6117 before the first Tor release, in svn commit r152.
6118 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
6119 June 2012 database, Maxmind marked many Tor relays as country "A1",
6120 which will cause risky behavior for clients that set EntryNodes
6121 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
6122 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
6123 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
6126 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
6127 bugfix on 0.2.1.10-alpha.
6130 Changes in version 0.2.3.18-rc - 2012-06-28
6131 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
6132 series. It fixes a few smaller bugs, but generally appears stable.
6133 Please test it and let us know whether it is!
6136 - Allow wildcarded mapaddress targets to be specified on the
6137 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
6138 - Make our linker option detection code more robust against linkers
6139 such as on FreeBSD 8, where a bad combination of options completes
6140 successfully but makes an unrunnable binary. Fixes bug 6173;
6141 bugfix on 0.2.3.17-beta.
6143 o Minor bugfixes (on 0.2.2.x and earlier):
6144 - Avoid a false positive in the util/threads unit test by increasing
6145 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
6146 - Replace "Sending publish request" log messages with "Launching
6147 upload", so that they no longer confusingly imply that we're
6148 sending something to a directory we might not even be connected
6149 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
6150 - Make sure to set *socket_error in all error cases in
6151 connection_connect(), so it can't produce a warning about
6152 errno being zero from errno_to_orconn_end_reason(). Bugfix on
6153 0.2.1.1-alpha; resolves ticket 6028.
6154 - Downgrade "Got a certificate, but we already have it" log messages
6155 from warning to info, except when we're a dirauth. Fixes bug 5238;
6156 bugfix on 0.2.1.7-alpha.
6157 - When checking for requested signatures on the latest consensus
6158 before serving it to a client, make sure to check the right
6159 consensus flavor. Bugfix on 0.2.2.6-alpha.
6160 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
6161 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
6163 o Minor bugfixes (on 0.2.3.x):
6164 - Make format_helper_exit_status() avoid unnecessary space padding
6165 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
6167 - Downgrade a message about cleaning the microdescriptor cache to
6168 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
6169 - Log a BUG message at severity INFO if we have a networkstatus with
6170 a missing entry for some microdescriptor. Continues on a patch
6172 - Improve the log message when a managed proxy fails to launch. Fixes
6173 bug 5099; bugfix on 0.2.3.6-alpha.
6174 - Don't do DNS lookups when parsing corrupted managed proxy protocol
6175 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
6176 - When formatting wildcarded address mappings for the controller,
6177 be sure to include "*." as appropriate. Partially fixes bug 6244;
6178 bugfix on 0.2.3.9-alpha.
6179 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
6180 Bugfix on 0.2.3.13-alpha.
6181 - Stop logging messages about running with circuit timeout learning
6182 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
6183 - Disable a spurious warning about reading on a marked and flushing
6184 connection. We shouldn't be doing that, but apparently we
6185 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
6186 - Fix a bug that stopped AllowDotExit from working on addresses
6187 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
6190 o Code simplification, refactoring, unit tests:
6191 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
6192 Libevent's notion of cached time when possible.
6193 - Remove duplicate code for invoking getrlimit() from control.c.
6194 - Add a unit test for the environment_variable_names_equal function.
6197 - Document the --defaults-torrc option, and the new (in 0.2.3)
6198 semantics for overriding, extending, and clearing lists of
6199 options. Closes bug 4748.
6202 Changes in version 0.2.3.17-beta - 2012-06-15
6203 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
6204 gets our TLS handshake back on track for being able to blend in with
6205 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
6206 with Vidalia, and otherwise continues to get us closer to a release
6210 - Enable gcc and ld hardening by default. Resolves ticket 5210.
6211 - Update TLS cipher list to match Firefox 8 and later. Resolves
6213 - Implement the client side of proposal 198: remove support for
6214 clients falsely claiming to support standard ciphersuites that
6215 they can actually provide. As of modern OpenSSL versions, it's not
6216 necessary to fake any standard ciphersuite, and doing so prevents
6217 us from using better ciphersuites in the future, since servers
6218 can't know whether an advertised ciphersuite is really supported or
6219 not. Some hosts -- notably, ones with very old versions of OpenSSL
6220 or where OpenSSL has been built with ECC disabled -- will stand
6221 out because of this change; TBB users should not be affected.
6224 - Change the default value for DynamicDHGroups (introduced in
6225 0.2.3.9-alpha) to 0. This feature can make Tor relays less
6226 identifiable by their use of the mod_ssl DH group, but at
6227 the cost of some usability (#4721) and bridge tracing (#6087)
6228 regressions. Resolves ticket 5598.
6229 - Send a CRLF at the end of each STATUS_* control protocol event. This
6230 bug tickled a bug in Vidalia which would make it freeze. Fixes
6231 bug 6094; bugfix on 0.2.3.16-alpha.
6234 - Disable writing on marked-for-close connections when they are
6235 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
6236 bug 5263; bugfix on 0.0.2pre13, where we first added a special
6237 case for flushing marked connections.
6238 - Detect SSL handshake even when the initial attempt to write the
6239 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
6240 - Change the AllowDotExit rules so they should actually work.
6241 We now enforce AllowDotExit only immediately after receiving an
6242 address via SOCKS or DNSPort: other sources are free to provide
6243 .exit addresses after the resolution occurs. Fixes bug 3940;
6244 bugfix on 0.2.2.1-alpha.
6245 - Fix a (harmless) integer overflow in cell statistics reported by
6246 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
6247 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
6248 right places and never depends on the consensus parameters or
6249 computes adaptive timeouts when it is disabled. Fixes bug 5049;
6250 bugfix on 0.2.2.14-alpha.
6251 - When building Tor on Windows with -DUNICODE (not default), ensure
6252 that error messages, filenames, and DNS server names are always
6253 NUL-terminated when we convert them to a single-byte encoding.
6254 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
6255 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
6256 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
6257 - Fix an edge case where TestingTorNetwork is set but the authorities
6258 and relays all have an uptime of zero, where the private Tor network
6259 could briefly lack support for hidden services. Fixes bug 3886;
6260 bugfix on 0.2.2.18-alpha.
6261 - Correct the manpage's descriptions for the default values of
6262 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
6264 - Fix the documentation for the --hush and --quiet command line
6265 options, which changed their behavior back in 0.2.3.3-alpha.
6266 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
6270 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
6271 more information to it, so that we can track it down in case it
6272 returns again. Mitigates bug 5235.
6273 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
6274 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
6275 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
6276 - Warn the user when HTTPProxy, but no other proxy type, is
6277 configured. This can cause surprising behavior: it doesn't send
6278 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
6279 directory traffic only. Resolves ticket 4663.
6280 - Issue a notice if a guard completes less than 40% of your circuits.
6281 Threshold is configurable by torrc option PathBiasNoticeRate and
6282 consensus parameter pb_noticepct. There is additional, off-by-
6283 default code to disable guards which fail too many circuits.
6284 Addresses ticket 5458.
6285 - Update to the June 6 2012 Maxmind GeoLite Country database.
6287 o Code simplifications and refactoring:
6288 - Remove validate_pluggable_transports_config(): its warning
6289 message is now handled by connection_or_connect().
6292 Changes in version 0.2.2.37 - 2012-06-06
6293 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
6294 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
6298 - Work around a bug in OpenSSL that broke renegotiation with TLS
6299 1.1 and TLS 1.2. Without this workaround, all attempts to speak
6300 the v2 Tor connection protocol when both sides were using OpenSSL
6301 1.0.1 would fail. Resolves ticket 6033.
6302 - When waiting for a client to renegotiate, don't allow it to add
6303 any bytes to the input buffer. This fixes a potential DoS issue.
6304 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
6305 - Fix an edge case where if we fetch or publish a hidden service
6306 descriptor, we might build a 4-hop circuit and then use that circuit
6307 for exiting afterwards -- even if the new last hop doesn't obey our
6308 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
6311 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
6312 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
6315 - Tell GCC and Clang to check for any errors in format strings passed
6316 to the tor_v*(print|scan)f functions.
6319 Changes in version 0.2.3.16-alpha - 2012-06-05
6320 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
6321 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
6322 currently). It also fixes a variety of smaller bugs and other cleanups
6323 that get us closer to a release candidate.
6325 o Major bugfixes (general):
6326 - Work around a bug in OpenSSL that broke renegotiation with TLS
6327 1.1 and TLS 1.2. Without this workaround, all attempts to speak
6328 the v2 Tor connection protocol when both sides were using OpenSSL
6329 1.0.1 would fail. Resolves ticket 6033.
6330 - When waiting for a client to renegotiate, don't allow it to add
6331 any bytes to the input buffer. This fixes a potential DoS issue.
6332 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
6333 - Pass correct OR address to managed proxies (like obfsproxy),
6334 even when ORListenAddress is used. Fixes bug 4865; bugfix on
6336 - The advertised platform of a router now includes only its operating
6337 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
6338 service pack level (for Windows) or its CPU architecture (for Unix).
6339 We also no longer include the "git-XYZ" tag in the version. Resolves
6342 o Major bugfixes (clients):
6343 - If we are unable to find any exit that supports our predicted ports,
6344 stop calling them predicted, so that we don't loop and build
6345 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
6346 which introduced predicted ports.
6347 - Fix an edge case where if we fetch or publish a hidden service
6348 descriptor, we might build a 4-hop circuit and then use that circuit
6349 for exiting afterwards -- even if the new last hop doesn't obey our
6350 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
6351 - Check at each new consensus whether our entry guards were picked
6352 long enough ago that we should rotate them. Previously, we only
6353 did this check at startup, which could lead to us holding a guard
6354 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
6355 - When fetching a bridge descriptor from a bridge authority,
6356 always do so anonymously, whether we have been able to open
6357 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
6358 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
6359 but we'll need to wait for bug 6010 before it's actually usable.
6361 o Major bugfixes (directory authorities):
6362 - When computing weight parameters, behave more robustly in the
6363 presence of a bad bwweightscale value. Previously, the authorities
6364 would crash if they agreed on a sufficiently broken weight_scale
6365 value: now, they use a reasonable default and carry on. Partial
6366 fix for 5786; bugfix on 0.2.2.17-alpha.
6367 - Check more thoroughly to prevent a rogue authority from
6368 double-voting on any consensus directory parameter. Previously,
6369 authorities would crash in this case if the total number of
6370 votes for any parameter exceeded the number of active voters,
6371 but would let it pass otherwise. Partial fix for bug 5786; bugfix
6375 - Rate-limit log messages when asked to connect anonymously to
6376 a private address. When these hit, they tended to hit fast and
6377 often. Also, don't bother trying to connect to addresses that we
6378 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
6379 reply makes us think we have been lied to, even when the address the
6380 client tried to connect to was "localhost." Resolves ticket 2822.
6381 - Allow packagers to insert an extra string in server descriptor
6382 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
6383 Resolves the rest of ticket 2988.
6384 - Raise the threshold of server descriptors needed (75%) and exit
6385 server descriptors needed (50%) before we will declare ourselves
6386 bootstrapped. This will make clients start building circuits a
6387 little later, but makes the initially constructed circuits less
6388 skewed and less in conflict with further directory fetches. Fixes
6390 - Close any connection that sends unrecognized junk before the
6391 handshake. Solves an issue noted in bug 4369.
6392 - Improve log messages about managed transports. Resolves ticket 5070.
6393 - Tag a bridge's descriptor as "never to be sent unencrypted".
6394 This shouldn't matter, since bridges don't open non-anonymous
6395 connections to the bridge authority and don't allow unencrypted
6396 directory connections from clients, but we might as well make
6397 sure. Closes bug 5139.
6398 - Expose our view of whether we have gone dormant to the controller,
6399 via a new "GETINFO dormant" value. Torbutton and other controllers
6400 can use this to avoid doing periodic requests through Tor while
6401 it's dormant (bug 4718). Fixes bug 5954.
6402 - Tell GCC and Clang to check for any errors in format strings passed
6403 to the tor_v*(print|scan)f functions.
6404 - Update to the May 1 2012 Maxmind GeoLite Country database.
6406 o Minor bugfixes (already included in 0.2.2.36):
6407 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
6408 Fixes bug 5346; bugfix on 0.0.8pre3.
6409 - Correct parsing of certain date types in parse_http_time().
6410 Without this patch, If-Modified-Since would behave
6411 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
6412 Esteban Manchado Velázques.
6413 - Make our number-parsing functions always treat too-large values
6414 as an error, even when those values exceed the width of the
6415 underlying type. Previously, if the caller provided these
6416 functions with minima or maxima set to the extreme values of the
6417 underlying integer type, these functions would return those
6418 values on overflow rather than treating overflow as an error.
6419 Fixes part of bug 5786; bugfix on 0.0.9.
6420 - If we hit the error case where routerlist_insert() replaces an
6421 existing (old) server descriptor, make sure to remove that
6422 server descriptor from the old_routers list. Fix related to bug
6423 1776. Bugfix on 0.2.2.18-alpha.
6424 - Clarify the behavior of MaxCircuitDirtiness with hidden service
6425 circuits. Fixes issue 5259.
6427 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
6428 - Prevent a null-pointer dereference when receiving a data cell
6429 for a nonexistent stream when the circuit in question has an
6430 empty deliver window. We don't believe this is triggerable,
6431 since we don't currently allow deliver windows to become empty,
6432 but the logic is tricky enough that it's better to make the code
6433 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
6434 - Fix a memory leak when trying to launch a DNS request when the
6435 network is disabled or the nameservers are unconfigurable. Fixes
6436 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
6437 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
6438 - Don't hold a Windows file handle open for every file mapping;
6439 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
6441 - Avoid O(n^2) performance characteristics when parsing a large
6442 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
6443 - Format more doubles with %f, not %lf. Patch from grarpamp to make
6444 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
6446 - Make our replacement implementation of strtok_r() compatible with
6447 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
6448 bugfix on 0.2.2.1-alpha.
6449 - Fix a NULL-pointer dereference on a badly formed
6450 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
6451 bugfix on 0.2.2.9-alpha.
6452 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
6453 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
6454 - Defensively refactor rend_mid_rendezvous() so that protocol
6455 violations and length checks happen in the beginning. Fixes
6457 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
6458 that IPv6 stuff will compile on MSVC, and compilation issues
6459 will be easier to track down. Fixes bug 5861.
6461 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
6462 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
6463 resource exhaustion, so that clients can adjust their load to
6464 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
6465 started using END_STREAM_REASON_RESOURCELIMIT.
6466 - Don't check for whether the address we're using for outbound
6467 connections has changed until after the outbound connection has
6468 completed. On Windows, getsockname() doesn't succeed until the
6469 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
6470 - If the configuration tries to set MyFamily on a bridge, refuse to
6471 do so, and warn about the security implications. Fixes bug 4657;
6472 bugfix on 0.2.0.3-alpha.
6473 - If the client fails to set a reasonable set of ciphersuites
6474 during its v2 handshake renegotiation, allow the renegotiation to
6475 continue nevertheless (i.e. send all the required certificates).
6476 Fixes bug 4591; bugfix on 0.2.0.20-rc.
6477 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
6478 option is set to 0 (which Vidalia version 0.2.16 now does when
6479 a SAVECONF attempt fails), perform other actions that SIGHUP
6480 usually causes (like reopening the logs). Fixes bug 5095; bugfix
6482 - If we fail to write a microdescriptor to the disk cache, do not
6483 continue replacing the old microdescriptor file. Fixes bug 2954;
6484 bugfix on 0.2.2.6-alpha.
6485 - Exit nodes don't need to fetch certificates for authorities that
6486 they don't recognize; only directory authorities, bridges,
6487 and caches need to do that. Fixes part of bug 2297; bugfix on
6489 - Correctly handle checking the permissions on the parent
6490 directory of a control socket in the root directory. Bug found
6491 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
6493 - When told to add a bridge with the same digest as a preexisting
6494 bridge but a different addr:port, change the addr:port as
6495 requested. Previously we would not notice the change. Fixes half
6496 of bug 5603; fix on 0.2.2.26-beta.
6497 - End AUTHCHALLENGE error messages (in the control protocol) with
6498 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
6500 o Minor bugfixes (on 0.2.3.x):
6501 - Turn an assertion (that the number of handshakes received as a
6502 server is not < 1) into a warning. Fixes bug 4873; bugfix on
6504 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
6505 we had reversed them when the answer was cached.) Fixes bug
6506 5723; bugfix on 0.2.3.1-alpha.
6507 - Work correctly on Linux systems with accept4 support advertised in
6508 their headers, but without accept4 support in the kernel. Fix
6509 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
6510 - When told to add a bridge with the same addr:port as a preexisting
6511 bridge but a different transport, change the transport as
6512 requested. Previously we would not notice the change. Fixes half
6513 of bug 5603; fix on 0.2.3.2-alpha.
6514 - Avoid a "double-reply" warning when replying to a SOCKS request
6515 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
6516 bugfix on 0.2.3.4-alpha.
6517 - Fix a bug where a bridge authority crashes if it has seen no
6518 directory requests when it's time to write statistics to disk.
6519 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
6521 - Don't try to open non-control listeners when DisableNetwork is set.
6522 Previously, we'd open all listeners, then immediately close them.
6523 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
6524 - Don't abort the managed proxy protocol if the managed proxy
6525 sends us an unrecognized line; ignore it instead. Fixes bug
6526 5910; bugfix on 0.2.3.9-alpha.
6527 - Fix a compile warning in crypto.c when compiling with clang 3.1.
6528 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
6529 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
6530 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
6531 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
6532 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
6533 - Resolve numerous small warnings and build issues with MSVC. Resolves
6536 o Documentation fixes:
6537 - Improve the manual's documentation for the NT Service command-line
6538 options. Addresses ticket 3964.
6539 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
6540 - Document the changes to the ORPort and DirPort options, and the
6541 fact that {OR/Dir}ListenAddress is now unnecessary (and
6542 therefore deprecated). Resolves ticket 5597.
6545 - Remove the torrc.bridge file: we don't use it for anything, and
6546 it had become badly desynchronized from torrc.sample. Resolves
6550 Changes in version 0.2.2.36 - 2012-05-24
6551 Tor 0.2.2.36 updates the addresses for two of the eight directory
6552 authorities, fixes some potential anonymity and security issues,
6553 and fixes several crash bugs.
6555 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
6556 known flaws, and nobody should be using them. You should upgrade. If
6557 you're using a Linux or BSD and its packages are obsolete, stop using
6558 those packages and upgrade anyway.
6560 o Directory authority changes:
6561 - Change IP address for maatuska (v3 directory authority).
6562 - Change IP address for ides (v3 directory authority), and rename
6566 - When building or running with any version of OpenSSL earlier
6567 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
6568 versions have a bug (CVE-2011-4576) in which their block cipher
6569 padding includes uninitialized data, potentially leaking sensitive
6570 information to any peer with whom they make a SSLv3 connection. Tor
6571 does not use SSL v3 by default, but a hostile client or server
6572 could force an SSLv3 connection in order to gain information that
6573 they shouldn't have been able to get. The best solution here is to
6574 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
6575 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
6576 to make sure that the bug can't happen.
6577 - Never use a bridge or a controller-supplied node as an exit, even
6578 if its exit policy allows it. Found by wanoskarnet. Fixes bug
6579 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
6580 and 0.2.0.3-alpha (for bridge-purpose descriptors).
6581 - Only build circuits if we have a sufficient threshold of the total
6582 descriptors that are marked in the consensus with the "Exit"
6583 flag. This mitigates an attack proposed by wanoskarnet, in which
6584 all of a client's bridges collude to restrict the exit nodes that
6585 the client knows about. Fixes bug 5343.
6586 - Provide controllers with a safer way to implement the cookie
6587 authentication mechanism. With the old method, if another locally
6588 running program could convince a controller that it was the Tor
6589 process, then that program could trick the controller into telling
6590 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
6591 authentication method uses a challenge-response approach to prevent
6592 this attack. Fixes bug 5185; implements proposal 193.
6595 - Avoid logging uninitialized data when unable to decode a hidden
6596 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
6597 - Avoid a client-side assertion failure when receiving an INTRODUCE2
6598 cell on a general purpose circuit. Fixes bug 5644; bugfix on
6600 - Fix builds when the path to sed, openssl, or sha1sum contains
6601 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
6603 - Correct our replacements for the timeradd() and timersub() functions
6604 on platforms that lack them (for example, Windows). The timersub()
6605 function is used when expiring circuits, while timeradd() is
6606 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
6607 bugfix on 0.2.2.24-alpha.
6608 - Fix the SOCKET_OK test that we use to tell when socket
6609 creation fails so that it works on Win64. Fixes part of bug 4533;
6610 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
6613 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
6614 Fixes bug 5346; bugfix on 0.0.8pre3.
6615 - Make our number-parsing functions always treat too-large values
6616 as an error, even when those values exceed the width of the
6617 underlying type. Previously, if the caller provided these
6618 functions with minima or maxima set to the extreme values of the
6619 underlying integer type, these functions would return those
6620 values on overflow rather than treating overflow as an error.
6621 Fixes part of bug 5786; bugfix on 0.0.9.
6622 - Older Linux kernels erroneously respond to strange nmap behavior
6623 by having accept() return successfully with a zero-length
6624 socket. When this happens, just close the connection. Previously,
6625 we would try harder to learn the remote address: but there was
6626 no such remote address to learn, and our method for trying to
6627 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
6628 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
6629 - Correct parsing of certain date types in parse_http_time().
6630 Without this patch, If-Modified-Since would behave
6631 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
6632 Esteban Manchado Velázques.
6633 - Change the BridgePassword feature (part of the "bridge community"
6634 design, which is not yet implemented) to use a time-independent
6635 comparison. The old behavior might have allowed an adversary
6636 to use timing to guess the BridgePassword value. Fixes bug 5543;
6637 bugfix on 0.2.0.14-alpha.
6638 - Detect and reject certain misformed escape sequences in
6639 configuration values. Previously, these values would cause us
6640 to crash if received in a torrc file or over an authenticated
6641 control port. Bug found by Esteban Manchado Velázquez, and
6642 independently by Robert Connolly from Matta Consulting who further
6643 noted that it allows a post-authentication heap overflow. Patch
6644 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
6645 bugfix on 0.2.0.16-alpha.
6646 - Fix a compile warning when using the --enable-openbsd-malloc
6647 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
6648 - During configure, detect when we're building with clang version
6649 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
6650 CFLAGS. clang doesn't support them yet.
6651 - When sending an HTTP/1.1 proxy request, include a Host header.
6652 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
6653 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
6654 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
6655 - If we hit the error case where routerlist_insert() replaces an
6656 existing (old) server descriptor, make sure to remove that
6657 server descriptor from the old_routers list. Fix related to bug
6658 1776. Bugfix on 0.2.2.18-alpha.
6660 o Minor bugfixes (documentation and log messages):
6661 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
6662 Fixes bug 4856; bugfix on Tor 0.0.6.
6663 - Update "ClientOnly" man page entry to explain that there isn't
6664 really any point to messing with it. Resolves ticket 5005.
6665 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
6666 directory authority option (introduced in Tor 0.2.2.34).
6667 - Downgrade the "We're missing a certificate" message from notice
6668 to info: people kept mistaking it for a real problem, whereas it
6669 is seldom the problem even when we are failing to bootstrap. Fixes
6670 bug 5067; bugfix on 0.2.0.10-alpha.
6671 - Correctly spell "connect" in a log message on failure to create a
6672 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
6673 - Clarify the behavior of MaxCircuitDirtiness with hidden service
6674 circuits. Fixes issue 5259.
6677 - Directory authorities now reject versions of Tor older than
6678 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
6679 inclusive. These versions accounted for only a small fraction of
6680 the Tor network, and have numerous known security issues. Resolves
6682 - Update to the May 1 2012 Maxmind GeoLite Country database.
6685 - When sending or relaying a RELAY_EARLY cell, we used to convert
6686 it to a RELAY cell if the connection was using the v1 link
6687 protocol. This was a workaround for older versions of Tor, which
6688 didn't handle RELAY_EARLY cells properly. Now that all supported
6689 versions can handle RELAY_EARLY cells, and now that we're enforcing
6690 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
6691 remove this workaround. Addresses bug 4786.
6694 Changes in version 0.2.3.15-alpha - 2012-04-30
6695 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
6696 the development branch build on Windows again.
6698 o Minor bugfixes (on 0.2.2.x and earlier):
6699 - Make sure that there are no unhandled pending TLS errors before
6700 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
6701 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
6702 Bugfix on 0.1.0.5-rc; fixes bug 4528.
6703 - Fix an assert that directory authorities could trigger on sighup
6704 during some configuration state transitions. We now don't treat
6705 it as a fatal error when the new descriptor we just generated in
6706 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
6707 - After we pick a directory mirror, we would refuse to use it if
6708 it's in our ExcludeExitNodes list, resulting in mysterious failures
6709 to bootstrap for people who just wanted to avoid exiting from
6710 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
6711 - When building with --enable-static-tor on OpenBSD, do not
6712 erroneously attempt to link -lrt. Fixes bug 5103.
6714 o Minor bugfixes (on 0.2.3.x):
6715 - When Tor is built with kernel headers from a recent (last few
6716 years) Linux kernel, do not fail to run on older (pre-2.6.28
6717 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
6718 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
6720 - Fix compilation with miniupnpc version 1.6; patch from
6721 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
6722 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
6723 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
6724 - Fix compilation on platforms without unistd.h, or where environ
6725 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
6728 - Directory authorities are now a little more lenient at accepting
6729 older router descriptors, or newer router descriptors that don't
6730 make big changes. This should help ameliorate past and future
6731 issues where routers think they have uploaded valid descriptors,
6732 but the authorities don't think so. Fix for ticket 2479.
6733 - Make the code that clients use to detect an address change be
6734 IPv6-aware, so that it won't fill clients' logs with error
6735 messages when trying to get the IPv4 address of an IPv6
6736 connection. Implements ticket 5537.
6739 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
6740 authorities needed to use it for a while to keep the network working
6741 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
6742 that was six months ago. As of now, it should no longer be needed
6746 Changes in version 0.2.3.14-alpha - 2012-04-23
6747 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
6748 candidate. It also dramatically speeds up AES: fast relays should
6749 consider switching to the newer OpenSSL library.
6751 o Directory authority changes:
6752 - Change IP address for ides (v3 directory authority), and rename
6756 - Avoid logging uninitialized data when unable to decode a hidden
6757 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
6758 - Avoid a client-side assertion failure when receiving an INTRODUCE2
6759 cell on a general purpose circuit. Fixes bug 5644; bugfix on
6761 - If authorities are unable to get a v2 consensus document from other
6762 directory authorities, they no longer fall back to fetching
6763 them from regular directory caches. Fixes bug 5635; bugfix on
6764 0.2.2.26-beta, where routers stopped downloading v2 consensus
6766 - When we start a Tor client with a normal consensus already cached,
6767 be willing to download a microdescriptor consensus. Fixes bug 4011;
6768 fix on 0.2.3.1-alpha.
6770 o Major features (performance):
6771 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
6772 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
6773 vectorized AES implementations as appropriate. These can be much,
6774 much faster than other AES implementations.
6776 o Minor bugfixes (0.2.2.x and earlier):
6777 - Don't launch more than 10 service-side introduction-point circuits
6778 for a hidden service in five minutes. Previously, we would consider
6779 launching more introduction-point circuits if at least one second
6780 had passed without any introduction-point circuits failing. Fixes
6781 bug 4607; bugfix on 0.0.7pre1.
6782 - Change the BridgePassword feature (part of the "bridge community"
6783 design, which is not yet implemented) to use a time-independent
6784 comparison. The old behavior might have allowed an adversary
6785 to use timing to guess the BridgePassword value. Fixes bug 5543;
6786 bugfix on 0.2.0.14-alpha.
6787 - Enforce correct return behavior of tor_vsscanf() when the '%%'
6788 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
6789 - When sending an HTTP/1.1 proxy request, include a Host header.
6790 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
6791 - Don't log that we have "decided to publish new relay descriptor"
6792 unless we are actually publishing a descriptor. Fixes bug 3942;
6793 bugfix on 0.2.2.28-beta.
6795 o Minor bugfixes (0.2.3.x):
6796 - Fix a bug where a bridge authority crashes (on a failed assert)
6797 if it has seen no directory requests when it's time to write
6798 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
6799 - Fix bug stomping on ORPort option NoListen and ignoring option
6800 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
6801 - In the testsuite, provide a large enough buffer in the tor_sscanf
6802 unit test. Otherwise we'd overrun that buffer and crash during
6803 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
6805 - Make sure we create the keys directory if it doesn't exist and we're
6806 about to store the dynamic Diffie-Hellman parameters. Fixes bug
6807 5572; bugfix on 0.2.3.13-alpha.
6808 - Fix a small memory leak when trying to decode incorrect base16
6809 authenticator during SAFECOOKIE authentication. Found by
6810 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
6813 - Add more information to a log statement that might help track down
6814 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
6815 non-IP address" messages (or any Bug messages, for that matter!),
6816 please let us know about it.
6817 - Relays now understand an IPv6 address when they get one from a
6818 directory server. Resolves ticket 4875.
6819 - Resolve IPv6 addresses in bridge and entry statistics to country
6820 code "??" which means we at least count them. Resolves ticket 5053;
6821 improves on 0.2.3.9-alpha.
6822 - Update to the April 3 2012 Maxmind GeoLite Country database.
6823 - Begin a doc/state-contents.txt file to explain the contents of
6824 the Tor state file. Fixes bug 2987.
6826 o Default torrc changes:
6827 - Stop listing "socksport 9050" in torrc.sample. We open a socks
6828 port on 9050 by default anyway, so this should not change anything
6830 - Stop mentioning the deprecated *ListenAddress options in
6831 torrc.sample. Fixes bug 5438.
6832 - Document unit of bandwidth related options in sample torrc.
6836 - The "torify" script no longer supports the "tsocks" socksifier
6837 tool, since tsocks doesn't support DNS and UDP right for Tor.
6838 Everyone should be using torsocks instead. Fixes bugs 3530 and
6839 5180. Based on a patch by "ugh".
6842 - Change the symmetric cipher interface so that creating and
6843 initializing a stream cipher are no longer separate functions.
6844 - Remove all internal support for unpadded RSA. We never used it, and
6845 it would be a bad idea to start.
6848 Changes in version 0.2.3.13-alpha - 2012-03-26
6849 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
6850 in managed pluggable transports, as well as providing other cleanups
6851 that get us closer to a release candidate.
6853 o Directory authority changes:
6854 - Change IP address for maatuska (v3 directory authority).
6857 - Provide controllers with a safer way to implement the cookie
6858 authentication mechanism. With the old method, if another locally
6859 running program could convince a controller that it was the Tor
6860 process, then that program could trick the controller into telling
6861 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
6862 authentication method uses a challenge-response approach to prevent
6863 this attack. Fixes bug 5185, implements proposal 193.
6864 - Never use a bridge or a controller-supplied node as an exit, even
6865 if its exit policy allows it. Found by wanoskarnet. Fixes bug
6866 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
6867 and 0.2.0.3-alpha (for bridge-purpose descriptors).
6868 - Only build circuits if we have a sufficient threshold of the total
6869 descriptors that are marked in the consensus with the "Exit"
6870 flag. This mitigates an attack proposed by wanoskarnet, in which
6871 all of a client's bridges collude to restrict the exit nodes that
6872 the client knows about. Fixes bug 5343.
6874 o Major bugfixes (on Tor 0.2.3.x):
6875 - Avoid an assert when managed proxies like obfsproxy are configured,
6876 and we receive HUP signals or setconf attempts too rapidly. This
6877 situation happens most commonly when Vidalia tries to attach to
6878 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
6879 bugfix on 0.2.3.6-alpha.
6880 - Fix a relay-side pluggable transports bug where managed proxies were
6881 unreachable from the Internet, because Tor asked them to bind on
6882 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
6883 - Stop discarding command-line arguments when TestingTorNetwork
6884 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
6885 0.2.3.9-alpha, where task 4552 added support for two layers of
6887 - Resume allowing the unit tests to run in gdb. This was accidentally
6888 made impossible when the DisableDebuggerAttachment option was
6889 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
6890 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
6891 0.2.3.11-alpha. Reported by Anthony G. Basile.
6893 o Minor bugfixes (on 0.2.2.x and earlier):
6894 - Ensure we don't cannibalize circuits that are longer than three hops
6895 already, so we don't end up making circuits with 5 or more
6896 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
6897 0.1.0.1-rc which introduced cannibalization.
6898 - Detect and reject certain misformed escape sequences in
6899 configuration values. Previously, these values would cause us
6900 to crash if received in a torrc file or over an authenticated
6901 control port. Bug found by Esteban Manchado Velázquez, and
6902 independently by Robert Connolly from Matta Consulting who further
6903 noted that it allows a post-authentication heap overflow. Patch
6904 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
6905 bugfix on 0.2.0.16-alpha.
6906 - Fix a compile warning when using the --enable-openbsd-malloc
6907 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
6908 - Directory caches no longer refuse to clean out descriptors because
6909 of missing v2 networkstatus documents, unless they're configured
6910 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
6911 0.2.2.26-beta. Patch by Daniel Bryg.
6912 - Update to the latest version of the tinytest unit testing framework.
6913 This includes a couple of bugfixes that can be relevant for
6914 running forked unit tests on Windows, and removes all reserved
6917 o Minor bugfixes (on 0.2.3.x):
6918 - On a failed pipe() call, don't leak file descriptors. Fixes bug
6919 4296; bugfix on 0.2.3.1-alpha.
6920 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
6921 until after we have received a CERTS cell. Fixes bug 4361; bugfix
6922 on 0.2.3.6-alpha. Patch by "frosty".
6923 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
6924 option, so that the IP stack doesn't decide to use it for IPv4
6925 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
6926 - Ensure that variables set in Tor's environment cannot override
6927 environment variables that Tor passes to a managed
6928 pluggable-transport proxy. Previously, Tor would pass every
6929 variable in its environment to managed proxies along with the new
6930 ones, in such a way that on many operating systems, the inherited
6931 environment variables would override those which Tor tried to
6932 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
6933 bugfix on 0.2.3.9-alpha for Windows.
6936 - A wide variety of new unit tests by Esteban Manchado Velázquez.
6937 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
6938 - Update to the March 6 2012 Maxmind GeoLite Country database.
6941 Changes in version 0.2.3.12-alpha - 2012-02-13
6942 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
6943 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
6944 when Tor is configured to use a pluggable transport like obfsproxy.
6947 - Fix builds when the path to sed, openssl, or sha1sum contains
6948 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
6950 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
6951 connections. This change should allow busy exit relays to stop
6952 running out of available sockets as quickly. Fixes bug 4950;
6953 bugfix on 0.2.2.26-beta.
6954 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
6955 would ask the bridge for microdescriptors, which are only supported
6956 in 0.2.3.x, and then fail to bootstrap when it didn't get the
6957 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
6958 - Properly set up obfsproxy's environment when in managed mode. The
6959 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
6960 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
6961 5076 and 5082; bugfix on 0.2.3.6-alpha.
6964 - Use the dead_strip option when building Tor on OS X. This reduces
6965 binary size by almost 19% when linking openssl and libevent
6966 statically, which we do for Tor Browser Bundle.
6967 - Fix broken URLs in the sample torrc file, and tell readers about
6968 the OutboundBindAddress, ExitPolicyRejectPrivate, and
6969 PublishServerDescriptor options. Addresses bug 4652.
6970 - Update to the February 7 2012 Maxmind GeoLite Country database.
6973 - Downgrade the "We're missing a certificate" message from notice
6974 to info: people kept mistaking it for a real problem, whereas it
6975 is seldom the problem even when we are failing to bootstrap. Fixes
6976 bug 5067; bugfix on 0.2.0.10-alpha.
6977 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
6978 managed pluggable transport server proxy's environment.
6979 Previously, we would put it there, even though Tor doesn't
6980 implement an 'extended server port' yet, and even though Tor
6981 almost certainly isn't listening at that address. For now, we set
6982 it to an empty string to avoid crashing older obfsproxies. Bugfix
6984 - Log the heartbeat message every HeartbeatPeriod seconds, not every
6985 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
6986 0.2.3.1-alpha. Bug reported by Scott Bennett.
6987 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
6988 bugfix on 0.2.3.11-alpha.
6989 - Update "ClientOnly" man page entry to explain that there isn't
6990 really any point to messing with it. Resolves ticket 5005.
6991 - Use the correct CVE number for CVE-2011-4576 in our comments and
6992 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
6995 o Code simplifications and refactoring:
6996 - Use the _WIN32 macro throughout our code to detect Windows.
6997 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
7001 Changes in version 0.2.3.11-alpha - 2012-01-22
7002 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
7003 the last step of the plan to limit maximum circuit length, includes
7004 a wide variety of hidden service performance and correctness fixes,
7005 works around an OpenSSL security flaw if your distro is too stubborn
7006 to upgrade, and fixes a bunch of smaller issues.
7009 - Now that Tor 0.2.0.x is completely deprecated, enable the final
7010 part of "Proposal 110: Avoiding infinite length circuits" by
7011 refusing all circuit-extend requests that do not use a relay_early
7012 cell. This change helps Tor resist a class of denial-of-service
7013 attacks by limiting the maximum circuit length.
7014 - Adjust the number of introduction points that a hidden service
7015 will try to maintain based on how long its introduction points
7016 remain in use and how many introductions they handle. Fixes
7018 - Try to use system facilities for enumerating local interface
7019 addresses, before falling back to our old approach (which was
7020 binding a UDP socket, and calling getsockname() on it). That
7021 approach was scaring OS X users whose draconian firewall
7022 software warned about binding to UDP sockets, regardless of
7023 whether packets were sent. Now we try to use getifaddrs(),
7024 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
7025 system supports. Resolves ticket 1827.
7027 o Major security workaround:
7028 - When building or running with any version of OpenSSL earlier
7029 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
7030 versions have a bug (CVE-2011-4576) in which their block cipher
7031 padding includes uninitialized data, potentially leaking sensitive
7032 information to any peer with whom they make a SSLv3 connection. Tor
7033 does not use SSL v3 by default, but a hostile client or server
7034 could force an SSLv3 connection in order to gain information that
7035 they shouldn't have been able to get. The best solution here is to
7036 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
7037 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
7038 to make sure that the bug can't happen.
7041 - Fix the SOCKET_OK test that we use to tell when socket
7042 creation fails so that it works on Win64. Fixes part of bug 4533;
7043 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
7044 - Correct our replacements for the timeradd() and timersub() functions
7045 on platforms that lack them (for example, Windows). The timersub()
7046 function is used when expiring circuits, while timeradd() is
7047 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
7048 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
7049 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
7050 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
7051 bug at runtime, not compile time, because some distributions hack
7052 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
7053 on 0.2.3.9-alpha. Found by Pascal.
7055 o Minor features (controller):
7056 - Use absolute path names when reporting the torrc filename in the
7057 control protocol, so a controller can more easily find the torrc
7058 file. Resolves bug 1101.
7059 - Extend the control protocol to report flags that control a circuit's
7060 path selection in CIRC events and in replies to 'GETINFO
7061 circuit-status'. Implements part of ticket 2411.
7062 - Extend the control protocol to report the hidden service address
7063 and current state of a hidden-service-related circuit in CIRC
7064 events and in replies to 'GETINFO circuit-status'. Implements part
7066 - When reporting the path to the cookie file to the controller,
7067 give an absolute path. Resolves ticket 4881.
7068 - Allow controllers to request an event notification whenever a
7069 circuit is cannibalized or its purpose is changed. Implements
7070 part of ticket 3457.
7071 - Include the creation time of a circuit in CIRC and CIRC2
7072 control-port events and the list produced by the 'GETINFO
7073 circuit-status' control-port command.
7075 o Minor features (directory authorities):
7076 - Directory authorities now reject versions of Tor older than
7077 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
7078 inclusive. These versions accounted for only a small fraction of
7079 the Tor network, and have numerous known security issues. Resolves
7081 - Authority operators can now vote for all relays in a given
7082 set of countries to be BadDir/BadExit/Invalid/Rejected.
7083 - Provide two consensus parameters (FastFlagMinThreshold and
7084 FastFlagMaxThreshold) to control the range of allowable bandwidths
7085 for the Fast directory flag. These allow authorities to run
7086 experiments on appropriate requirements for being a "Fast" node.
7087 The AuthDirFastGuarantee config value still applies. Implements
7089 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
7090 directory authority option (introduced in Tor 0.2.2.34).
7092 o Minor features (other):
7093 - Don't disable the DirPort when we cannot exceed our AccountingMax
7094 limit during this interval because the effective bandwidthrate is
7095 low enough. This is useful in a situation where AccountMax is only
7096 used as an additional safeguard or to provide statistics.
7097 - Prepend an informative header to generated dynamic_dh_params files.
7098 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
7099 EntryNodes will have no effect. Resolves issue 2571.
7100 - Log more useful messages when we fail to disable debugger
7102 - Log which authority we're missing votes from when we go to fetch
7103 them from the other auths.
7104 - Log (at debug level) whenever a circuit's purpose is changed.
7105 - Add missing documentation for the MaxClientCircuitsPending,
7106 UseMicrodescriptors, UserspaceIOCPBuffers, and
7107 _UseFilteringSSLBufferevents options, all introduced during
7109 - Update to the January 3 2012 Maxmind GeoLite Country database.
7111 o Minor bugfixes (hidden services):
7112 - Don't close hidden service client circuits which have almost
7113 finished connecting to their destination when they reach
7114 the normal circuit-build timeout. Previously, we would close
7115 introduction circuits which are waiting for an acknowledgement
7116 from the introduction point, and rendezvous circuits which have
7117 been specified in an INTRODUCE1 cell sent to a hidden service,
7118 after the normal CBT. Now, we mark them as 'timed out', and launch
7119 another rendezvous attempt in parallel. This behavior change can
7120 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
7121 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
7122 - Don't close hidden-service-side rendezvous circuits when they
7123 reach the normal circuit-build timeout. This behavior change can
7124 be disabled using the new
7125 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
7126 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
7127 - Make sure we never mark the wrong rendezvous circuit as having
7128 had its introduction cell acknowleged by the introduction-point
7129 relay. Previously, when we received an INTRODUCE_ACK cell on a
7130 client-side hidden-service introduction circuit, we might have
7131 marked a rendezvous circuit other than the one we specified in
7132 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
7133 a warning message and interfered with the hidden service
7134 connection-establishment process. Fixes bug 4759; bugfix on
7135 0.2.3.3-alpha, when we added the stream-isolation feature which
7136 might cause Tor to open multiple rendezvous circuits for the same
7138 - Don't trigger an assertion failure when we mark a new client-side
7139 hidden-service introduction circuit for close during the process
7140 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
7143 o Minor bugfixes (log messages):
7144 - Correctly spell "connect" in a log message on failure to create a
7145 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
7147 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
7148 Fixes bug 4856; bugfix on Tor 0.0.6.
7149 - Fix the log message describing how we work around discovering
7150 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
7151 4837; bugfix on 0.2.2.9-alpha.
7152 - When logging about a disallowed .exit name, do not also call it
7153 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
7155 o Minor bugfixes (build fixes):
7156 - During configure, detect when we're building with clang version
7157 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
7158 CFLAGS. clang doesn't support them yet.
7159 - During configure, search for library containing cos function as
7160 libm lives in libcore on some platforms (BeOS/Haiku). Linking
7161 against libm was hard-coded before. Fixes the first part of bug
7162 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
7164 - Detect attempts to build Tor on (as yet hypothetical) versions
7165 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
7166 fix for bug 4533. Bugfix on 0.2.2.28-beta.
7167 - Preprocessor directives should not be put inside the arguments
7168 of a macro. This would break compilation with GCC releases prior
7169 to version 3.3. We would never recommend such an old GCC version,
7170 but it is apparently required for binary compatibility on some
7171 platforms (namely, certain builds of Haiku). Fixes the other part
7172 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
7175 o Minor bugfixes (other):
7176 - Older Linux kernels erroneously respond to strange nmap behavior
7177 by having accept() return successfully with a zero-length
7178 socket. When this happens, just close the connection. Previously,
7179 we would try harder to learn the remote address: but there was
7180 no such remote address to learn, and our method for trying to
7181 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
7182 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
7183 - Fix null-pointer access that could occur if TLS allocation failed.
7184 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
7185 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
7186 accidentally been reverted.
7187 - Fix our implementation of crypto_random_hostname() so it can't
7188 overflow on ridiculously large inputs. (No Tor version has ever
7189 provided this kind of bad inputs, but let's be correct in depth.)
7190 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
7191 - Find more places in the code that should have been testing for
7192 invalid sockets using the SOCKET_OK macro. Required for a fix
7193 for bug 4533. Bugfix on 0.2.2.28-beta.
7194 - Fix an assertion failure when, while running with bufferevents, a
7195 connection finishes connecting after it is marked for close, but
7196 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
7197 - test_util_spawn_background_ok() hardcoded the expected value
7198 for ENOENT to 2. This isn't portable as error numbers are
7199 platform specific, and particularly the hurd has ENOENT at
7200 0x40000002. Construct expected string at runtime, using the correct
7201 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
7202 - Reject attempts to disable DisableDebuggerAttachment while Tor is
7203 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
7204 - Use an appropriate-width type for sockets in tor-fw-helper on
7205 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
7208 - When sending or relaying a RELAY_EARLY cell, we used to convert
7209 it to a RELAY cell if the connection was using the v1 link
7210 protocol. This was a workaround for older versions of Tor, which
7211 didn't handle RELAY_EARLY cells properly. Now that all supported
7212 versions can handle RELAY_EARLY cells, and now that we're enforcing
7213 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
7214 remove this workaround. Addresses bug 4786.
7216 o Code simplifications and refactoring:
7217 - Use OpenSSL's built-in SSL_state_string_long() instead of our
7218 own homebrewed ssl_state_to_string() replacement. Patch from
7219 Emile Snyder. Fixes bug 4653.
7220 - Use macros to indicate OpenSSL versions, so we don't need to worry
7221 about accidental hexadecimal bit shifts.
7222 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
7224 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
7225 - Use the smartlist_add_asprintf() alias more consistently.
7226 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
7227 invalid value, rather than just -1.
7228 - Rename a handful of old identifiers, mostly related to crypto
7229 structures and crypto functions. By convention, our "create an
7230 object" functions are called "type_new()", our "free an object"
7231 functions are called "type_free()", and our types indicate that
7232 they are types only with a final "_t". But a handful of older
7233 types and functions broke these rules, with function names like
7234 "type_create" or "subsystem_op_type", or with type names like
7238 Changes in version 0.2.3.10-alpha - 2011-12-16
7239 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
7240 Tor's buffers code. Absolutely everybody should upgrade.
7242 The bug relied on an incorrect calculation when making data continuous
7243 in one of our IO buffers, if the first chunk of the buffer was
7244 misaligned by just the wrong amount. The miscalculation would allow an
7245 attacker to overflow a piece of heap-allocated memory. To mount this
7246 attack, the attacker would need to either open a SOCKS connection to
7247 Tor's SocksPort (usually restricted to localhost), or target a Tor
7248 instance configured to make its connections through a SOCKS proxy
7249 (which Tor does not do by default).
7251 Good security practice requires that all heap-overflow bugs should be
7252 presumed to be exploitable until proven otherwise, so we are treating
7253 this as a potential code execution attack. Please upgrade immediately!
7254 This bug does not affect bufferevents-based builds of Tor. Special
7255 thanks to "Vektor" for reporting this issue to us!
7257 This release also contains a few minor bugfixes for issues discovered
7261 - Fix a heap overflow bug that could occur when trying to pull
7262 data into the first chunk of a buffer, when that chunk had
7263 already had some data drained from it. Fixes CVE-2011-2778;
7264 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7267 - If we can't attach streams to a rendezvous circuit when we
7268 finish connecting to a hidden service, clear the rendezvous
7269 circuit's stream-isolation state and try to attach streams
7270 again. Previously, we cleared rendezvous circuits' isolation
7271 state either too early (if they were freshly built) or not at all
7272 (if they had been built earlier and were cannibalized). Bugfix on
7273 0.2.3.3-alpha; fixes bug 4655.
7274 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
7275 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
7276 - Fix an assertion failure when a relay with accounting enabled
7277 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
7280 - Update to the December 6 2011 Maxmind GeoLite Country database.
7283 Changes in version 0.2.2.35 - 2011-12-16
7284 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
7285 buffers code. Absolutely everybody should upgrade.
7287 The bug relied on an incorrect calculation when making data continuous
7288 in one of our IO buffers, if the first chunk of the buffer was
7289 misaligned by just the wrong amount. The miscalculation would allow an
7290 attacker to overflow a piece of heap-allocated memory. To mount this
7291 attack, the attacker would need to either open a SOCKS connection to
7292 Tor's SocksPort (usually restricted to localhost), or target a Tor
7293 instance configured to make its connections through a SOCKS proxy
7294 (which Tor does not do by default).
7296 Good security practice requires that all heap-overflow bugs should be
7297 presumed to be exploitable until proven otherwise, so we are treating
7298 this as a potential code execution attack. Please upgrade immediately!
7299 This bug does not affect bufferevents-based builds of Tor. Special
7300 thanks to "Vektor" for reporting this issue to us!
7302 Tor 0.2.2.35 also fixes several bugs in previous versions, including
7303 crash bugs for unusual configurations, and a long-term bug that
7304 would prevent Tor from starting on Windows machines with draconian
7307 With this release, we remind everyone that 0.2.0.x has reached its
7308 formal end-of-life. Those Tor versions have many known flaws, and
7309 nobody should be using them. You should upgrade -- ideally to the
7310 0.2.2.x series. If you're using a Linux or BSD and its packages are
7311 obsolete, stop using those packages and upgrade anyway.
7313 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
7314 longer receive support after some time in early 2012.
7317 - Fix a heap overflow bug that could occur when trying to pull
7318 data into the first chunk of a buffer, when that chunk had
7319 already had some data drained from it. Fixes CVE-2011-2778;
7320 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7321 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
7322 that it doesn't attempt to allocate a socketpair. This could cause
7323 some problems on Windows systems with overzealous firewalls. Fix for
7324 bug 4457; workaround for Libevent versions 2.0.1-alpha through
7326 - If we mark an OR connection for close based on a cell we process,
7327 don't process any further cells on it. We already avoid further
7328 reads on marked-for-close connections, but now we also discard the
7329 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
7330 which was the first version where we might mark a connection for
7331 close based on processing a cell on it.
7332 - Correctly sanity-check that we don't underflow on a memory
7333 allocation (and then assert) for hidden service introduction
7334 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7335 bugfix on 0.2.1.5-alpha.
7336 - Fix a memory leak when we check whether a hidden service
7337 descriptor has any usable introduction points left. Fixes bug
7338 4424. Bugfix on 0.2.2.25-alpha.
7339 - Don't crash when we're running as a relay and don't have a GeoIP
7340 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
7341 we've had in the 0.2.3.x branch already.
7342 - When running as a client, do not print a misleading (and plain
7343 wrong) log message that we're collecting "directory request"
7344 statistics: clients don't collect statistics. Also don't create a
7345 useless (because empty) stats file in the stats/ directory. Fixes
7346 bug 4353; bugfix on 0.2.2.34.
7349 - Detect failure to initialize Libevent. This fix provides better
7350 detection for future instances of bug 4457.
7351 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
7352 function. This was eating up hideously large amounts of time on some
7353 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
7354 - Resolve an integer overflow bug in smartlist_ensure_capacity().
7355 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
7357 - Don't warn about unused log_mutex in log.c when building with
7358 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
7359 0.1.0.6-rc which introduced --disable-threads.
7360 - When configuring, starting, or stopping an NT service, stop
7361 immediately after the service configuration attempt has succeeded
7362 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
7363 - When sending a NETINFO cell, include the original address
7364 received for the other side, not its canonical address. Found
7365 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
7366 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
7367 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
7368 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
7369 occurred when a client tried to fetch a descriptor for a bridge
7370 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
7371 - Backport fixes for a pair of compilation warnings on Windows.
7372 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
7373 - If we had ever tried to call tor_addr_to_str on an address of
7374 unknown type, we would have done a strdup on an uninitialized
7375 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
7376 Reported by "troll_un".
7377 - Correctly detect and handle transient lookup failures from
7378 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
7379 Reported by "troll_un".
7380 - Fix null-pointer access that could occur if TLS allocation failed.
7381 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
7382 - Use tor_socket_t type for listener argument to accept(). Fixes bug
7383 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
7386 - Add two new config options for directory authorities:
7387 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
7388 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
7389 that is always sufficient to satisfy the bandwidth requirement for
7390 the Guard flag. Now it will be easier for researchers to simulate
7391 Tor networks with different values. Resolves ticket 4484.
7392 - When Tor ignores a hidden service specified in its configuration,
7393 include the hidden service's directory in the warning message.
7394 Previously, we would only tell the user that some hidden service
7395 was ignored. Bugfix on 0.0.6; fixes bug 4426.
7396 - Update to the December 6 2011 Maxmind GeoLite Country database.
7398 o Packaging changes:
7399 - Make it easier to automate expert package builds on Windows,
7400 by removing an absolute path from makensis.exe command.
7403 Changes in version 0.2.1.32 - 2011-12-16
7404 Tor 0.2.1.32 backports important security and privacy fixes for
7405 oldstable. This release is intended only for package maintainers and
7406 others who cannot use the 0.2.2 stable series. All others should be
7407 using Tor 0.2.2.x or newer.
7409 The Tor 0.2.1.x series will reach formal end-of-life some time in
7410 early 2012; we will stop releasing patches for it then.
7412 o Major bugfixes (also included in 0.2.2.x):
7413 - Correctly sanity-check that we don't underflow on a memory
7414 allocation (and then assert) for hidden service introduction
7415 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7416 bugfix on 0.2.1.5-alpha.
7417 - Fix a heap overflow bug that could occur when trying to pull
7418 data into the first chunk of a buffer, when that chunk had
7419 already had some data drained from it. Fixes CVE-2011-2778;
7420 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7423 - Update to the December 6 2011 Maxmind GeoLite Country database.
7426 Changes in version 0.2.3.9-alpha - 2011-12-08
7427 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
7428 a "DisableNetwork" security feature that bundles can use to avoid
7429 touching the network until bridges are configured, moves forward on
7430 the pluggable transport design, fixes a flaw in the hidden service
7431 design that unnecessarily prevented clients with wrong clocks from
7432 reaching hidden services, and fixes a wide variety of other issues.
7435 - Clients can now connect to private bridges over IPv6. Bridges
7436 still need at least one IPv4 address in order to connect to
7437 other relays. Note that we don't yet handle the case where the
7438 user has two bridge lines for the same bridge (one IPv4, one
7439 IPv6). Implements parts of proposal 186.
7440 - New "DisableNetwork" config option to prevent Tor from launching any
7441 connections or accepting any connections except on a control port.
7442 Bundles and controllers can set this option before letting Tor talk
7443 to the rest of the network, for example to prevent any connections
7444 to a non-bridge address. Packages like Orbot can also use this
7445 option to instruct Tor to save power when the network is off.
7446 - Clients and bridges can now be configured to use a separate
7447 "transport" proxy. This approach makes the censorship arms race
7448 easier by allowing bridges to use protocol obfuscation plugins. It
7449 implements the "managed proxy" part of proposal 180 (ticket 3472).
7450 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
7451 implementation. It makes AES_CTR about 7% faster than our old one
7452 (which was about 10% faster than the one OpenSSL used to provide).
7453 Resolves ticket 4526.
7454 - Add a "tor2web mode" for clients that want to connect to hidden
7455 services non-anonymously (and possibly more quickly). As a safety
7456 measure to try to keep users from turning this on without knowing
7457 what they are doing, tor2web mode must be explicitly enabled at
7458 compile time, and a copy of Tor compiled to run in tor2web mode
7459 cannot be used as a normal Tor client. Implements feature 2553.
7460 - Add experimental support for running on Windows with IOCP and no
7461 kernel-space socket buffers. This feature is controlled by a new
7462 "UserspaceIOCPBuffers" config option (off by default), which has
7463 no effect unless Tor has been built with support for bufferevents,
7464 is running on Windows, and has enabled IOCP. This may, in the long
7465 run, help solve or mitigate bug 98.
7466 - Use a more secure consensus parameter voting algorithm. Now at
7467 least three directory authorities or a majority of them must
7468 vote on a given parameter before it will be included in the
7469 consensus. Implements proposal 178.
7472 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
7473 They used to check that the timestamp was within 30 minutes
7474 of their system clock, so they could cap the size of their
7475 replay-detection cache, but that approach unnecessarily refused
7476 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
7477 the v3 intro-point protocol (the first one which sent a timestamp
7478 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
7479 - Only use the EVP interface when AES acceleration is enabled,
7480 to avoid a 5-7% performance regression. Resolves issue 4525;
7481 bugfix on 0.2.3.8-alpha.
7483 o Privacy/anonymity features (bridge detection):
7484 - Make bridge SSL certificates a bit more stealthy by using random
7485 serial numbers, in the same fashion as OpenSSL when generating
7486 self-signed certificates. Implements ticket 4584.
7487 - Introduce a new config option "DynamicDHGroups", enabled by
7488 default, which provides each bridge with a unique prime DH modulus
7489 to be used during SSL handshakes. This option attempts to help
7490 against censors who might use the Apache DH modulus as a static
7491 identifier for bridges. Addresses ticket 4548.
7493 o Minor features (new/different config options):
7494 - New configuration option "DisableDebuggerAttachment" (on by default)
7495 to prevent basic debugging attachment attempts by other processes.
7496 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
7497 - Allow MapAddress directives to specify matches against super-domains,
7498 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
7499 Implements issue 933.
7500 - Slightly change behavior of "list" options (that is, config
7501 options that can appear more than once) when they appear both in
7502 torrc and on the command line. Previously, the command-line options
7503 would be appended to the ones from torrc. Now, the command-line
7504 options override the torrc options entirely. This new behavior
7505 allows the user to override list options (like exit policies and
7506 ports to listen on) from the command line, rather than simply
7507 appending to the list.
7508 - You can get the old (appending) command-line behavior for "list"
7509 options by prefixing the option name with a "+".
7510 - You can remove all the values for a "list" option from the command
7511 line without adding any new ones by prefixing the option name
7513 - Add experimental support for a "defaults" torrc file to be parsed
7514 before the regular torrc. Torrc options override the defaults file's
7515 options in the same way that the command line overrides the torrc.
7516 The SAVECONF controller command saves only those options which
7517 differ between the current configuration and the defaults file. HUP
7518 reloads both files. (Note: This is an experimental feature; its
7519 behavior will probably be refined in future 0.2.3.x-alpha versions
7520 to better meet packagers' needs.) Implements task 4552.
7523 - Try to make the introductory warning message that Tor prints on
7524 startup more useful for actually finding help and information.
7525 Resolves ticket 2474.
7526 - Running "make version" now displays the version of Tor that
7527 we're about to build. Idea from katmagic; resolves issue 4400.
7528 - Expire old or over-used hidden service introduction points.
7529 Required by fix for bug 3460.
7530 - Move the replay-detection cache for the RSA-encrypted parts of
7531 INTRODUCE2 cells to the introduction point data structures.
7532 Previously, we would use one replay-detection cache per hidden
7533 service. Required by fix for bug 3460.
7534 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
7535 public key replay-detection cache from 60 minutes to 5 minutes. This
7536 replay-detection cache is now used only to detect multiple
7537 INTRODUCE2 cells specifying the same rendezvous point, so we can
7538 avoid launching multiple simultaneous attempts to connect to it.
7540 o Minor bugfixes (on Tor 0.2.2.x and earlier):
7541 - Resolve an integer overflow bug in smartlist_ensure_capacity().
7542 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
7544 - Fix a minor formatting issue in one of tor-gencert's error messages.
7546 - Prevent a false positive from the check-spaces script, by disabling
7547 the "whitespace between function name and (" check for functions
7549 - Fix a log message suggesting that people contact a non-existent
7550 email address. Fixes bug 3448.
7551 - Fix null-pointer access that could occur if TLS allocation failed.
7552 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
7553 - Report a real bootstrap problem to the controller on router
7554 identity mismatch. Previously we just said "foo", which probably
7555 made a lot of sense at the time. Fixes bug 4169; bugfix on
7557 - If we had ever tried to call tor_addr_to_str() on an address of
7558 unknown type, we would have done a strdup() on an uninitialized
7559 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
7560 Reported by "troll_un".
7561 - Correctly detect and handle transient lookup failures from
7562 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
7563 Reported by "troll_un".
7564 - Use tor_socket_t type for listener argument to accept(). Fixes bug
7565 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
7566 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
7567 bug 4532; found by "troll_un".
7569 o Minor bugfixes (on Tor 0.2.3.x):
7570 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
7572 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
7573 circuit for use as a hidden service client's rendezvous point.
7574 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
7575 with help from wanoskarnet.
7576 - Restore behavior of overriding SocksPort, ORPort, and similar
7577 options from the command line. Bugfix on 0.2.3.3-alpha.
7580 - Properly handle the case where the build-tree is not the same
7581 as the source tree when generating src/common/common_sha1.i,
7582 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
7583 bugfix on 0.2.0.1-alpha.
7585 o Code simplifications, cleanups, and refactorings:
7586 - Remove the pure attribute from all functions that used it
7587 previously. In many cases we assigned it incorrectly, because the
7588 functions might assert or call impure functions, and we don't have
7589 evidence that keeping the pure attribute is worthwhile. Implements
7590 changes suggested in ticket 4421.
7591 - Remove some dead code spotted by coverity. Fixes cid 432.
7592 Bugfix on 0.2.3.1-alpha, closes bug 4637.
7595 Changes in version 0.2.3.8-alpha - 2011-11-22
7596 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
7597 socketpair-related bug that has been bothering Windows users. It adds
7598 support to serve microdescriptors to controllers, so Vidalia's network
7599 map can resume listing relays (once Vidalia implements its side),
7600 and adds better support for hardware AES acceleration. Finally, it
7601 starts the process of adjusting the bandwidth cutoff for getting the
7602 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
7603 that tiny relays harm performance more than they help network capacity.
7606 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
7607 that it doesn't attempt to allocate a socketpair. This could cause
7608 some problems on Windows systems with overzealous firewalls. Fix for
7609 bug 4457; workaround for Libevent versions 2.0.1-alpha through
7611 - Correctly sanity-check that we don't underflow on a memory
7612 allocation (and then assert) for hidden service introduction
7613 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7614 bugfix on 0.2.1.5-alpha.
7615 - Remove the artificially low cutoff of 20KB to guarantee the Fast
7616 flag. In the past few years the average relay speed has picked
7617 up, and while the "top 7/8 of the network get the Fast flag" and
7618 "all relays with 20KB or more of capacity get the Fast flag" rules
7619 used to have the same result, now the top 7/8 of the network has
7620 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
7621 - Fix a rare assertion failure when checking whether a v0 hidden
7622 service descriptor has any usable introduction points left, and
7623 we don't have enough information to build a circuit to the first
7624 intro point named in the descriptor. The HS client code in
7625 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
7626 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
7627 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
7628 - Make bridge authorities not crash when they are asked for their own
7629 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
7630 - When running as a client, do not print a misleading (and plain
7631 wrong) log message that we're collecting "directory request"
7632 statistics: clients don't collect statistics. Also don't create a
7633 useless (because empty) stats file in the stats/ directory. Fixes
7634 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
7637 - Allow Tor controllers like Vidalia to obtain the microdescriptor
7638 for a relay by identity digest or nickname. Previously,
7639 microdescriptors were only available by their own digests, so a
7640 controller would have to ask for and parse the whole microdescriptor
7641 consensus in order to look up a single relay's microdesc. Fixes
7642 bug 3832; bugfix on 0.2.3.1-alpha.
7643 - Use OpenSSL's EVP interface for AES encryption, so that all AES
7644 operations can use hardware acceleration (if present). Resolves
7647 o Minor bugfixes (on 0.2.2.x and earlier):
7648 - Detect failure to initialize Libevent. This fix provides better
7649 detection for future instances of bug 4457.
7650 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
7651 function. This was eating up hideously large amounts of time on some
7652 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
7653 - Don't warn about unused log_mutex in log.c when building with
7654 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
7655 0.1.0.6-rc which introduced --disable-threads.
7656 - Allow manual 'authenticate' commands to the controller interface
7657 from netcat (nc) as well as telnet. We were rejecting them because
7658 they didn't come with the expected whitespace at the end of the
7659 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
7660 - Fix some (not actually triggerable) buffer size checks in usage of
7661 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
7663 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
7664 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
7665 - When configuring, starting, or stopping an NT service, stop
7666 immediately after the service configuration attempt has succeeded
7667 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
7668 - When sending a NETINFO cell, include the original address
7669 received for the other side, not its canonical address. Found
7670 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
7671 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
7672 can pick them up when the tests aren't disabled. Bugfix on
7673 0.2.2.4-alpha which introduced tinytest.
7674 - Fix a memory leak when we check whether a hidden service
7675 descriptor has any usable introduction points left. Fixes bug
7676 4424. Bugfix on 0.2.2.25-alpha.
7677 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
7678 occurred when a client tried to fetch a descriptor for a bridge
7679 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
7681 o Minor bugfixes (on 0.2.3.x):
7682 - Make util unit tests build correctly with MSVC. Bugfix on
7683 0.2.3.3-alpha. Patch by Gisle Vanem.
7684 - Successfully detect AUTH_CHALLENGE cells with no recognized
7685 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
7687 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
7688 it should still send a NETINFO cell to allow the connection to
7689 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
7691 - Log less loudly when we get an invalid authentication certificate
7692 from a source other than a directory authority: it's not unusual
7693 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
7695 - Tolerate servers with more clock skew in their authentication
7696 certificates than previously. Fixes bug 4371; bugfix on
7698 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
7699 on 0.2.3.4-alpha and 0.2.3.6-alpha.
7702 - Add two new config options for directory authorities:
7703 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
7704 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
7705 that is always sufficient to satisfy the bandwidth requirement for
7706 the Guard flag. Now it will be easier for researchers to simulate
7707 Tor networks with different values. Resolves ticket 4484.
7708 - When Tor ignores a hidden service specified in its configuration,
7709 include the hidden service's directory in the warning message.
7710 Previously, we would only tell the user that some hidden service
7711 was ignored. Bugfix on 0.0.6; fixes bug 4426.
7712 - When we fail to initialize Libevent, retry with IOCP disabled so we
7713 don't need to turn on multi-threading support in Libevent, which in
7714 turn requires a working socketpair(). This is a workaround for bug
7715 4457, which affects Libevent versions from 2.0.1-alpha through
7717 - Detect when we try to build on a platform that doesn't define
7718 AF_UNSPEC to 0. We don't work there, so refuse to compile.
7719 - Update to the November 1 2011 Maxmind GeoLite Country database.
7721 o Packaging changes:
7722 - Make it easier to automate expert package builds on Windows,
7723 by removing an absolute path from makensis.exe command.
7725 o Code simplifications and refactoring:
7726 - Remove some redundant #include directives throughout the code.
7727 Patch from Andrea Gelmini.
7728 - Unconditionally use OpenSSL's AES implementation instead of our
7729 old built-in one. OpenSSL's AES has been better for a while, and
7730 relatively few servers should still be on any version of OpenSSL
7731 that doesn't have good optimized assembly AES.
7732 - Use the name "CERTS" consistently to refer to the new cell type;
7733 we were calling it CERT in some places and CERTS in others.
7736 - Numerous new unit tests for functions in util.c and address.c by
7738 - The long-disabled benchmark tests are now split into their own
7739 ./src/test/bench binary.
7740 - The benchmark tests can now use more accurate timers than
7741 gettimeofday() when such timers are available.
7744 Changes in version 0.2.3.7-alpha - 2011-10-30
7745 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
7746 the new v3 handshake. It also resolves yet another bridge address
7750 - If we mark an OR connection for close based on a cell we process,
7751 don't process any further cells on it. We already avoid further
7752 reads on marked-for-close connections, but now we also discard the
7753 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
7754 which was the first version where we might mark a connection for
7755 close based on processing a cell on it.
7756 - Fix a double-free bug that would occur when we received an invalid
7757 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
7758 bugfix on 0.2.3.6-alpha.
7759 - Bridges no longer include their address in NETINFO cells on outgoing
7760 OR connections, to allow them to blend in better with clients.
7761 Removes another avenue for enumerating bridges. Reported by
7762 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
7763 cells were introduced.
7766 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
7767 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
7770 Changes in version 0.2.3.6-alpha - 2011-10-26
7771 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
7772 anonymity vulnerability where an attacker can deanonymize Tor
7773 users. Everybody should upgrade.
7775 This release also features support for a new v3 connection handshake
7776 protocol, and fixes to make hidden service connections more robust.
7779 - Implement a new handshake protocol (v3) for authenticating Tors to
7780 each other over TLS. It should be more resistant to fingerprinting
7781 than previous protocols, and should require less TLS hacking for
7782 future Tor implementations. Implements proposal 176.
7783 - Allow variable-length padding cells to disguise the length of
7784 Tor's TLS records. Implements part of proposal 184.
7786 o Privacy/anonymity fixes (clients):
7787 - Clients and bridges no longer send TLS certificate chains on
7788 outgoing OR connections. Previously, each client or bridge would
7789 use the same cert chain for all outgoing OR connections until
7790 its IP address changes, which allowed any relay that the client
7791 or bridge contacted to determine which entry guards it is using.
7792 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7793 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7794 no longer considers that connection as suitable for satisfying a
7795 circuit EXTEND request. Now relays can protect clients from the
7796 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7797 - Directory authorities no longer assign the Guard flag to relays
7798 that haven't upgraded to the above "refuse EXTEND requests
7799 to client connections" fix. Now directory authorities can
7800 protect clients from the CVE-2011-2768 issue even if neither
7801 the clients nor the relays have upgraded yet. There's a new
7802 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
7803 to let us transition smoothly, else tomorrow there would be no
7806 o Major bugfixes (hidden services):
7807 - Improve hidden service robustness: when an attempt to connect to
7808 a hidden service ends, be willing to refetch its hidden service
7809 descriptors from each of the HSDir relays responsible for them
7810 immediately. Previously, we would not consider refetching the
7811 service's descriptors from each HSDir for 15 minutes after the last
7812 fetch, which was inconvenient if the hidden service was not running
7813 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
7814 - When one of a hidden service's introduction points appears to be
7815 unreachable, stop trying it. Previously, we would keep trying
7816 to build circuits to the introduction point until we lost the
7817 descriptor, usually because the user gave up and restarted Tor.
7818 Partly fixes bug 3825.
7819 - Don't launch a useless circuit after failing to use one of a
7820 hidden service's introduction points. Previously, we would
7821 launch a new introduction circuit, but not set the hidden service
7822 which that circuit was intended to connect to, so it would never
7823 actually be used. A different piece of code would then create a
7824 new introduction circuit correctly. Bug reported by katmagic and
7825 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
7827 o Major bugfixes (other):
7828 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7829 that they initiated. Relays could distinguish incoming bridge
7830 connections from client connections, creating another avenue for
7831 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7832 Found by "frosty_un".
7833 - Don't update the AccountingSoftLimitHitAt state file entry whenever
7834 tor gets started. This prevents a wrong average bandwidth
7835 estimate, which would cause relays to always start a new accounting
7836 interval at the earliest possible moment. Fixes bug 2003; bugfix
7837 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
7838 immensely in tracking this bug down.
7839 - Fix a crash bug when changing node restrictions while a DNS lookup
7840 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
7843 o Minor bugfixes (on 0.2.2.x and earlier):
7844 - When a hidden service turns an extra service-side introduction
7845 circuit into a general-purpose circuit, free the rend_data and
7846 intro_key fields first, so we won't leak memory if the circuit
7847 is cannibalized for use as another service-side introduction
7848 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
7849 - Rephrase the log message emitted if the TestSocks check is
7850 successful. Patch from Fabian Keil; fixes bug 4094.
7851 - Bridges now skip DNS self-tests, to act a little more stealthily.
7852 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
7853 bridges. Patch by "warms0x".
7854 - Remove a confusing dollar sign from the example fingerprint in the
7855 man page, and also make the example fingerprint a valid one. Fixes
7856 bug 4309; bugfix on 0.2.1.3-alpha.
7857 - Fix internal bug-checking logic that was supposed to catch
7858 failures in digest generation so that it will fail more robustly
7859 if we ask for a nonexistent algorithm. Found by Coverity Scan.
7860 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
7861 - Report any failure in init_keys() calls launched because our
7862 IP address has changed. Spotted by Coverity Scan. Bugfix on
7863 0.1.1.4-alpha; fixes CID 484.
7865 o Minor bugfixes (on 0.2.3.x):
7866 - Fix a bug in configure.in that kept it from building a configure
7867 script with autoconf versions earlier than 2.61. Fixes bug 2430;
7868 bugfix on 0.2.3.1-alpha.
7869 - Don't warn users that they are exposing a client port to the
7870 Internet if they have specified an RFC1918 address. Previously,
7871 we would warn if the user had specified any non-loopback
7872 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
7873 - Fix memory leaks in the failing cases of the new SocksPort and
7874 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
7875 fixes coverity CIDs 485, 486, and 487.
7878 - When a hidden service's introduction point times out, consider
7879 trying it again during the next attempt to connect to the
7880 HS. Previously, we would not try it again unless a newly fetched
7881 descriptor contained it. Required by fixes for bugs 1297 and 3825.
7882 - The next version of Windows will be called Windows 8, and it has
7883 a major version of 6, minor version of 2. Correctly identify that
7884 version instead of calling it "Very recent version". Resolves
7885 ticket 4153; reported by funkstar.
7886 - The Bridge Authority now writes statistics on how many bridge
7887 descriptors it gave out in total, and how many unique descriptors
7888 it gave out. It also lists how often the most and least commonly
7889 fetched descriptors were given out, as well as the median and
7890 25th/75th percentile. Implements tickets 4200 and 4294.
7891 - Update to the October 4 2011 Maxmind GeoLite Country database.
7893 o Code simplifications and refactoring:
7894 - Remove some old code to remember statistics about which descriptors
7895 we've served as a directory mirror. The feature wasn't used and
7896 is outdated now that microdescriptors are around.
7897 - Rename Tor functions that turn strings into addresses, so that
7898 "parse" indicates that no hostname resolution occurs, and
7899 "lookup" indicates that hostname resolution may occur. This
7900 should help prevent mistakes in the future. Fixes bug 3512.
7903 Changes in version 0.2.2.34 - 2011-10-26
7904 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
7905 can deanonymize Tor users. Everybody should upgrade.
7907 The attack relies on four components: 1) Clients reuse their TLS cert
7908 when talking to different relays, so relays can recognize a user by
7909 the identity key in her cert. 2) An attacker who knows the client's
7910 identity key can probe each guard relay to see if that identity key
7911 is connected to that guard relay right now. 3) A variety of active
7912 attacks in the literature (starting from "Low-Cost Traffic Analysis
7913 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
7914 discover the guard relays that a Tor user visiting the website is using.
7915 4) Clients typically pick three guards at random, so the set of guards
7916 for a given user could well be a unique fingerprint for her. This
7917 release fixes components #1 and #2, which is enough to block the attack;
7918 the other two remain as open research problems. Special thanks to
7919 "frosty_un" for reporting the issue to us!
7921 Clients should upgrade so they are no longer recognizable by the TLS
7922 certs they present. Relays should upgrade so they no longer allow a
7923 remote attacker to probe them to test whether unpatched clients are
7924 currently connected to them.
7926 This release also fixes several vulnerabilities that allow an attacker
7927 to enumerate bridge relays. Some bridge enumeration attacks still
7928 remain; see for example proposal 188.
7930 o Privacy/anonymity fixes (clients):
7931 - Clients and bridges no longer send TLS certificate chains on
7932 outgoing OR connections. Previously, each client or bridge would
7933 use the same cert chain for all outgoing OR connections until
7934 its IP address changes, which allowed any relay that the client
7935 or bridge contacted to determine which entry guards it is using.
7936 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7937 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7938 no longer considers that connection as suitable for satisfying a
7939 circuit EXTEND request. Now relays can protect clients from the
7940 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7941 - Directory authorities no longer assign the Guard flag to relays
7942 that haven't upgraded to the above "refuse EXTEND requests
7943 to client connections" fix. Now directory authorities can
7944 protect clients from the CVE-2011-2768 issue even if neither
7945 the clients nor the relays have upgraded yet. There's a new
7946 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
7947 to let us transition smoothly, else tomorrow there would be no
7950 o Privacy/anonymity fixes (bridge enumeration):
7951 - Bridge relays now do their directory fetches inside Tor TLS
7952 connections, like all the other clients do, rather than connecting
7953 directly to the DirPort like public relays do. Removes another
7954 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
7955 - Bridges relays now build circuits for themselves in a more similar
7956 way to how clients build them. Removes another avenue for
7957 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
7958 when bridges were introduced.
7959 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7960 that they initiated. Relays could distinguish incoming bridge
7961 connections from client connections, creating another avenue for
7962 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7963 Found by "frosty_un".
7966 - Fix a crash bug when changing node restrictions while a DNS lookup
7967 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
7969 - Don't launch a useless circuit after failing to use one of a
7970 hidden service's introduction points. Previously, we would
7971 launch a new introduction circuit, but not set the hidden service
7972 which that circuit was intended to connect to, so it would never
7973 actually be used. A different piece of code would then create a
7974 new introduction circuit correctly. Bug reported by katmagic and
7975 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
7978 - Change an integer overflow check in the OpenBSD_Malloc code so
7979 that GCC is less likely to eliminate it as impossible. Patch
7980 from Mansour Moufid. Fixes bug 4059.
7981 - When a hidden service turns an extra service-side introduction
7982 circuit into a general-purpose circuit, free the rend_data and
7983 intro_key fields first, so we won't leak memory if the circuit
7984 is cannibalized for use as another service-side introduction
7985 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
7986 - Bridges now skip DNS self-tests, to act a little more stealthily.
7987 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
7988 bridges. Patch by "warms0x".
7989 - Fix internal bug-checking logic that was supposed to catch
7990 failures in digest generation so that it will fail more robustly
7991 if we ask for a nonexistent algorithm. Found by Coverity Scan.
7992 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
7993 - Report any failure in init_keys() calls launched because our
7994 IP address has changed. Spotted by Coverity Scan. Bugfix on
7995 0.1.1.4-alpha; fixes CID 484.
7997 o Minor bugfixes (log messages and documentation):
7998 - Remove a confusing dollar sign from the example fingerprint in the
7999 man page, and also make the example fingerprint a valid one. Fixes
8000 bug 4309; bugfix on 0.2.1.3-alpha.
8001 - The next version of Windows will be called Windows 8, and it has
8002 a major version of 6, minor version of 2. Correctly identify that
8003 version instead of calling it "Very recent version". Resolves
8004 ticket 4153; reported by funkstar.
8005 - Downgrade log messages about circuit timeout calibration from
8006 "notice" to "info": they don't require or suggest any human
8007 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
8008 bugfix on 0.2.2.14-alpha.
8011 - Turn on directory request statistics by default and include them in
8012 extra-info descriptors. Don't break if we have no GeoIP database.
8013 Backported from 0.2.3.1-alpha; implements ticket 3951.
8014 - Update to the October 4 2011 Maxmind GeoLite Country database.
8017 Changes in version 0.2.1.31 - 2011-10-26
8018 Tor 0.2.1.31 backports important security and privacy fixes for
8019 oldstable. This release is intended only for package maintainers and
8020 others who cannot use the 0.2.2 stable series. All others should be
8021 using Tor 0.2.2.x or newer.
8023 o Security fixes (also included in 0.2.2.x):
8024 - Replace all potentially sensitive memory comparison operations
8025 with versions whose runtime does not depend on the data being
8026 compared. This will help resist a class of attacks where an
8027 adversary can use variations in timing information to learn
8028 sensitive data. Fix for one case of bug 3122. (Safe memcmp
8029 implementation by Robert Ransom based partially on code by DJB.)
8030 - Fix an assert in parsing router descriptors containing IPv6
8031 addresses. This one took down the directory authorities when
8032 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
8034 o Privacy/anonymity fixes (also included in 0.2.2.x):
8035 - Clients and bridges no longer send TLS certificate chains on
8036 outgoing OR connections. Previously, each client or bridge would
8037 use the same cert chain for all outgoing OR connections until
8038 its IP address changes, which allowed any relay that the client
8039 or bridge contacted to determine which entry guards it is using.
8040 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8041 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8042 no longer considers that connection as suitable for satisfying a
8043 circuit EXTEND request. Now relays can protect clients from the
8044 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8045 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8046 that they initiated. Relays could distinguish incoming bridge
8047 connections from client connections, creating another avenue for
8048 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8049 Found by "frosty_un".
8050 - When receiving a hidden service descriptor, check that it is for
8051 the hidden service we wanted. Previously, Tor would store any
8052 hidden service descriptors that a directory gave it, whether it
8053 wanted them or not. This wouldn't have let an attacker impersonate
8054 a hidden service, but it did let directories pre-seed a client
8055 with descriptors that it didn't want. Bugfix on 0.0.6.
8056 - Avoid linkability based on cached hidden service descriptors: forget
8057 all hidden service descriptors cached as a client when processing a
8058 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
8059 - Make the bridge directory authority refuse to answer directory
8060 requests for "all" descriptors. It used to include bridge
8061 descriptors in its answer, which was a major information leak.
8062 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
8063 - Don't attach new streams to old rendezvous circuits after SIGNAL
8064 NEWNYM. Previously, we would keep using an existing rendezvous
8065 circuit if it remained open (i.e. if it were kept open by a
8066 long-lived stream, or if a new stream were attached to it before
8067 Tor could notice that it was old and no longer in use). Bugfix on
8068 0.1.1.15-rc; fixes bug 3375.
8070 o Minor bugfixes (also included in 0.2.2.x):
8071 - When we restart our relay, we might get a successful connection
8072 from the outside before we've started our reachability tests,
8073 triggering a warning: "ORPort found reachable, but I have no
8074 routerinfo yet. Failing to inform controller of success." This
8075 bug was harmless unless Tor is running under a controller
8076 like Vidalia, in which case the controller would never get a
8077 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
8079 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
8080 enabled. Fixes bug 1526.
8081 - Remove undocumented option "-F" from tor-resolve: it hasn't done
8082 anything since 0.2.1.16-rc.
8083 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
8084 None of the cases where we did this before were wrong, but by making
8085 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
8086 - Fix a rare crash bug that could occur when a client was configured
8087 with a large number of bridges. Fixes bug 2629; bugfix on
8088 0.2.1.2-alpha. Bugfix by trac user "shitlei".
8089 - Correct the warning displayed when a rendezvous descriptor exceeds
8090 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
8092 - Fix an uncommon assertion failure when running with DNSPort under
8093 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
8094 - When warning about missing zlib development packages during compile,
8095 give the correct package names. Bugfix on 0.2.0.1-alpha.
8096 - Require that introduction point keys and onion keys have public
8097 exponent 65537. Bugfix on 0.2.0.10-alpha.
8098 - Do not crash when our configuration file becomes unreadable, for
8099 example due to a permissions change, between when we start up
8100 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
8102 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
8104 - Always NUL-terminate the sun_path field of a sockaddr_un before
8105 passing it to the kernel. (Not a security issue: kernels are
8106 smart enough to reject bad sockaddr_uns.) Found by Coverity;
8107 CID #428. Bugfix on Tor 0.2.0.3-alpha.
8108 - Don't stack-allocate the list of supplementary GIDs when we're
8109 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
8110 could take up to 256K, which is way too much stack. Found by
8111 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
8113 o Minor bugfixes (only in 0.2.1.x):
8114 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
8115 rely on them. Bugfix on 0.2.1.30.
8116 - Use git revisions instead of svn revisions when generating our
8117 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
8119 o Minor features (also included in 0.2.2.x):
8120 - Adjust the expiration time on our SSL session certificates to
8121 better match SSL certs seen in the wild. Resolves ticket 4014.
8122 - Allow nameservers with IPv6 address. Resolves bug 2574.
8123 - Update to the October 4 2011 Maxmind GeoLite Country database.
8126 Changes in version 0.2.3.5-alpha - 2011-09-28
8127 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
8128 bridge relays; fixes an assertion error that many users started hitting
8129 today; and adds the ability to refill token buckets more often than
8130 once per second, allowing significant performance improvements.
8133 - Bridge relays now do their directory fetches inside Tor TLS
8134 connections, like all the other clients do, rather than connecting
8135 directly to the DirPort like public relays do. Removes another
8136 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
8137 - Bridges relays now build circuits for themselves in a more similar
8138 way to how clients build them. Removes another avenue for
8139 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
8140 when bridges were introduced.
8143 - Fix an "Assertion md->held_by_node == 1 failed" error that could
8144 occur when the same microdescriptor was referenced by two node_t
8145 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
8147 o Major features (networking):
8148 - Add a new TokenBucketRefillInterval option to refill token buckets
8149 more frequently than once per second. This should improve network
8150 performance, alleviate queueing problems, and make traffic less
8151 bursty. Implements proposal 183; closes ticket 3630. Design by
8152 Florian Tschorsch and Björn Scheuermann; implementation by
8156 - Change an integer overflow check in the OpenBSD_Malloc code so
8157 that GCC is less likely to eliminate it as impossible. Patch
8158 from Mansour Moufid. Fixes bug 4059.
8160 o Minor bugfixes (usability):
8161 - Downgrade log messages about circuit timeout calibration from
8162 "notice" to "info": they don't require or suggest any human
8163 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
8164 bugfix on 0.2.2.14-alpha.
8166 o Minor features (diagnostics):
8167 - When the system call to create a listener socket fails, log the
8168 error message explaining why. This may help diagnose bug 4027.
8171 Changes in version 0.2.3.4-alpha - 2011-09-13
8172 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
8173 tweak to Tor's TLS handshake that makes relays and bridges that run
8174 this new version reachable from Iran again. It also fixes a few new
8175 bugs in 0.2.3.x, and teaches relays to recognize when they're not
8176 listed in the network consensus and republish.
8178 o Major bugfixes (also part of 0.2.2.33):
8179 - Avoid an assertion failure when reloading a configuration with
8180 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
8181 3923; bugfix on 0.2.2.25-alpha.
8183 o Minor features (security, also part of 0.2.2.33):
8184 - Check for replays of the public-key encrypted portion of an
8185 INTRODUCE1 cell, in addition to the current check for replays of
8186 the g^x value. This prevents a possible class of active attacks
8187 by an attacker who controls both an introduction point and a
8188 rendezvous point, and who uses the malleability of AES-CTR to
8189 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
8190 that these attacks are infeasible (requiring the attacker to send
8191 on the order of zettabytes of altered cells in a short interval),
8192 but we'd rather block them off in case there are any classes of
8193 this attack that we missed. Reported by Willem Pinckaers.
8195 o Minor features (also part of 0.2.2.33):
8196 - Adjust the expiration time on our SSL session certificates to
8197 better match SSL certs seen in the wild. Resolves ticket 4014.
8198 - Change the default required uptime for a relay to be accepted as
8199 a HSDir (hidden service directory) from 24 hours to 25 hours.
8200 Improves on 0.2.0.10-alpha; resolves ticket 2649.
8201 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
8202 authorities to abstain from voting on assignment of the HSDir
8203 consensus flag. Related to bug 2649.
8204 - Update to the September 6 2011 Maxmind GeoLite Country database.
8206 o Minor bugfixes (also part of 0.2.2.33):
8207 - Demote the 'replay detected' log message emitted when a hidden
8208 service receives the same Diffie-Hellman public key in two different
8209 INTRODUCE2 cells to info level. A normal Tor client can cause that
8210 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
8211 fixes part of bug 2442.
8212 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
8213 level. There is nothing that a hidden service's operator can do
8214 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
8216 - Clarify a log message specifying the characters permitted in
8217 HiddenServiceAuthorizeClient client names. Previously, the log
8218 message said that "[A-Za-z0-9+-_]" were permitted; that could have
8219 given the impression that every ASCII character between "+" and "_"
8220 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
8222 o Build fixes (also part of 0.2.2.33):
8223 - Clean up some code issues that prevented Tor from building on older
8224 BSDs. Fixes bug 3894; reported by "grarpamp".
8225 - Search for a platform-specific version of "ar" when cross-compiling.
8226 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
8229 - Fix a bug where the SocksPort option (for example) would get
8230 ignored and replaced by the default if a SocksListenAddress
8231 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
8235 - Relays now try regenerating and uploading their descriptor more
8236 frequently if they are not listed in the consensus, or if the
8237 version of their descriptor listed in the consensus is too
8238 old. This fix should prevent situations where a server declines
8239 to re-publish itself because it has done so too recently, even
8240 though the authorities decided not to list its recent-enough
8241 descriptor. Fix for bug 3327.
8244 - Relays now include a reason for regenerating their descriptors
8245 in an HTTP header when uploading to the authorities. This will
8246 make it easier to debug descriptor-upload issues in the future.
8247 - When starting as root and then changing our UID via the User
8248 control option, and we have a ControlSocket configured, make sure
8249 that the ControlSocket is owned by the same account that Tor will
8250 run under. Implements ticket 3421; fix by Jérémy Bobbio.
8253 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
8254 utility function used in the control-port code). This shouldn't
8255 ever happen unless Tor is completely out of memory, but if it did
8256 happen and Tor somehow recovered from it, Tor could have sent a log
8257 message to a control port in the middle of a reply to a controller
8258 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
8259 - Make 'FetchUselessDescriptors' cause all descriptor types and
8260 all consensus types (including microdescriptors) to get fetched.
8261 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
8264 - Make a new "entry connection" struct as an internal subtype of "edge
8265 connection", to simplify the code and make exit connections smaller.
8268 Changes in version 0.2.2.33 - 2011-09-13
8269 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
8270 TLS handshake that makes relays and bridges that run this new version
8271 reachable from Iran again.
8274 - Avoid an assertion failure when reloading a configuration with
8275 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
8276 3923; bugfix on 0.2.2.25-alpha.
8278 o Minor features (security):
8279 - Check for replays of the public-key encrypted portion of an
8280 INTRODUCE1 cell, in addition to the current check for replays of
8281 the g^x value. This prevents a possible class of active attacks
8282 by an attacker who controls both an introduction point and a
8283 rendezvous point, and who uses the malleability of AES-CTR to
8284 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
8285 that these attacks are infeasible (requiring the attacker to send
8286 on the order of zettabytes of altered cells in a short interval),
8287 but we'd rather block them off in case there are any classes of
8288 this attack that we missed. Reported by Willem Pinckaers.
8291 - Adjust the expiration time on our SSL session certificates to
8292 better match SSL certs seen in the wild. Resolves ticket 4014.
8293 - Change the default required uptime for a relay to be accepted as
8294 a HSDir (hidden service directory) from 24 hours to 25 hours.
8295 Improves on 0.2.0.10-alpha; resolves ticket 2649.
8296 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
8297 authorities to abstain from voting on assignment of the HSDir
8298 consensus flag. Related to bug 2649.
8299 - Update to the September 6 2011 Maxmind GeoLite Country database.
8301 o Minor bugfixes (documentation and log messages):
8302 - Correct the man page to explain that HashedControlPassword and
8303 CookieAuthentication can both be set, in which case either method
8304 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
8305 when we decided to allow these config options to both be set. Issue
8307 - Demote the 'replay detected' log message emitted when a hidden
8308 service receives the same Diffie-Hellman public key in two different
8309 INTRODUCE2 cells to info level. A normal Tor client can cause that
8310 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
8311 fixes part of bug 2442.
8312 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
8313 level. There is nothing that a hidden service's operator can do
8314 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
8316 - Clarify a log message specifying the characters permitted in
8317 HiddenServiceAuthorizeClient client names. Previously, the log
8318 message said that "[A-Za-z0-9+-_]" were permitted; that could have
8319 given the impression that every ASCII character between "+" and "_"
8320 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
8323 - Provide a substitute implementation of lround() for MSVC, which
8324 apparently lacks it. Patch from Gisle Vanem.
8325 - Clean up some code issues that prevented Tor from building on older
8326 BSDs. Fixes bug 3894; reported by "grarpamp".
8327 - Search for a platform-specific version of "ar" when cross-compiling.
8328 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
8331 Changes in version 0.2.3.3-alpha - 2011-09-01
8332 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
8333 security, and provides client-side support for the microdescriptor
8334 and optimistic data features introduced earlier in the 0.2.3.x
8335 series. It also includes numerous critical bugfixes in the (optional)
8336 bufferevent-based networking backend.
8338 o Major features (stream isolation):
8339 - You can now configure Tor so that streams from different
8340 applications are isolated on different circuits, to prevent an
8341 attacker who sees your streams as they leave an exit node from
8342 linking your sessions to one another. To do this, choose some way
8343 to distinguish the applications: have them connect to different
8344 SocksPorts, or have one of them use SOCKS4 while the other uses
8345 SOCKS5, or have them pass different authentication strings to the
8346 SOCKS proxy. Then, use the new SocksPort syntax to configure the
8347 degree of isolation you need. This implements Proposal 171.
8348 - There's a new syntax for specifying multiple client ports (such as
8349 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
8350 multiple *Port entries with full addr:port syntax on each.
8351 The old *ListenAddress format is still supported, but you can't
8352 mix it with the new *Port syntax.
8354 o Major features (other):
8355 - Enable microdescriptor fetching by default for clients. This allows
8356 clients to download a much smaller amount of directory information.
8357 To disable it (and go back to the old-style consensus and
8358 descriptors), set "UseMicrodescriptors 0" in your torrc file.
8359 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
8360 "PortForwarding" config option), now supports Windows.
8361 - When using an exit relay running 0.2.3.x, clients can now
8362 "optimistically" send data before the exit relay reports that
8363 the stream has opened. This saves a round trip when starting
8364 connections where the client speaks first (such as web browsing).
8365 This behavior is controlled by a consensus parameter (currently
8366 disabled). To turn it on or off manually, use the "OptimisticData"
8367 torrc option. Implements proposal 181; code by Ian Goldberg.
8369 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
8370 - When using IOCP on Windows, we need to enable Libevent windows
8372 - The IOCP backend now works even when the user has not specified
8373 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
8374 Fixes part of bug 3752.
8375 - Correctly record the bytes we've read and written when using
8376 bufferevents, so that we can include them in our bandwidth history
8377 and advertised bandwidth. Fixes bug 3803.
8378 - Apply rate-limiting only at the bottom of a chain of filtering
8379 bufferevents. This prevents us from filling up internal read
8380 buffers and violating rate-limits when filtering bufferevents
8381 are enabled. Fixes part of bug 3804.
8382 - Add high-watermarks to the output buffers for filtered
8383 bufferevents. This prevents us from filling up internal write
8384 buffers and wasting CPU cycles when filtering bufferevents are
8385 enabled. Fixes part of bug 3804.
8386 - Correctly notice when data has been written from a bufferevent
8387 without flushing it completely. Fixes bug 3805.
8388 - Fix a bug where server-side tunneled bufferevent-based directory
8389 streams would get closed prematurely. Fixes bug 3814.
8390 - Fix a use-after-free error with per-connection rate-limiting
8391 buckets. Fixes bug 3888.
8393 o Major bugfixes (also part of 0.2.2.31-rc):
8394 - If we're configured to write our ControlPorts to disk, only write
8395 them after switching UID and creating the data directory. This way,
8396 we don't fail when starting up with a nonexistent DataDirectory
8397 and a ControlPortWriteToFile setting based on that directory. Fixes
8398 bug 3747; bugfix on Tor 0.2.2.26-beta.
8401 - Added a new CONF_CHANGED event so that controllers can be notified
8402 of any configuration changes made by other controllers, or by the
8403 user. Implements ticket 1692.
8404 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
8405 leak when using bufferevents, and lets Libevent worry about how to
8406 best copy data out of a buffer.
8407 - Replace files in stats/ rather than appending to them. Now that we
8408 include statistics in extra-info descriptors, it makes no sense to
8409 keep old statistics forever. Implements ticket 2930.
8411 o Minor features (build compatibility):
8412 - Limited, experimental support for building with nmake and MSVC.
8413 - Provide a substitute implementation of lround() for MSVC, which
8414 apparently lacks it. Patch from Gisle Vanem.
8416 o Minor features (also part of 0.2.2.31-rc):
8417 - Update to the August 2 2011 Maxmind GeoLite Country database.
8419 o Minor bugfixes (on 0.2.3.x-alpha):
8420 - Fix a spurious warning when parsing SOCKS requests with
8421 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
8422 - Get rid of a harmless warning that could happen on relays running
8423 with bufferevents. The warning was caused by someone doing an http
8424 request to a relay's orport. Also don't warn for a few related
8425 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
8427 o Minor bugfixes (on 2.2.x and earlier):
8428 - Correct the man page to explain that HashedControlPassword and
8429 CookieAuthentication can both be set, in which case either method
8430 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
8431 when we decided to allow these config options to both be set. Issue
8433 - The "--quiet" and "--hush" options now apply not only to Tor's
8434 behavior before logs are configured, but also to Tor's behavior in
8435 the absense of configured logs. Fixes bug 3550; bugfix on
8438 o Minor bugfixes (also part of 0.2.2.31-rc):
8439 - Write several files in text mode, on OSes that distinguish text
8440 mode from binary mode (namely, Windows). These files are:
8441 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
8442 that collect those statistics; 'client_keys' and 'hostname' for
8443 hidden services that use authentication; and (in the tor-gencert
8444 utility) newly generated identity and signing keys. Previously,
8445 we wouldn't specify text mode or binary mode, leading to an
8446 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
8447 the DirRecordUsageByCountry option which would have triggered
8448 the assertion failure was added), although this assertion failure
8449 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
8450 - Selectively disable deprecation warnings on OS X because Lion
8451 started deprecating the shipped copy of openssl. Fixes bug 3643.
8452 - Remove an extra pair of quotation marks around the error
8453 message in control-port STATUS_GENERAL BUG events. Bugfix on
8454 0.1.2.6-alpha; fixes bug 3732.
8455 - When unable to format an address as a string, report its value
8456 as "???" rather than reusing the last formatted address. Bugfix
8459 o Code simplifications and refactoring:
8460 - Rewrite the listener-selection logic so that parsing which ports
8461 we want to listen on is now separate from binding to the ports
8465 - Building Tor with bufferevent support now requires Libevent
8466 2.0.13-stable or later. Previous versions of Libevent had bugs in
8467 SSL-related bufferevents and related issues that would make Tor
8468 work badly with bufferevents. Requiring 2.0.13-stable also allows
8469 Tor with bufferevents to take advantage of Libevent APIs
8470 introduced after 2.0.8-rc.
8473 Changes in version 0.2.2.32 - 2011-08-27
8474 The Tor 0.2.2 release series is dedicated to the memory of Andreas
8475 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
8476 a founder of the PETS community, a leader in our field, a mentor,
8477 and a friend. He left us with these words: "I had the possibility
8478 to contribute to this world that is not as it should be. I hope I
8479 could help in some areas to make the world a better place, and that
8480 I could also encourage other people to be engaged in improving the
8481 world. Please, stay engaged. This world needs you, your love, your
8482 initiative -- now I cannot be part of that anymore."
8484 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
8485 ready. More than two years in the making, this release features improved
8486 client performance and hidden service reliability, better compatibility
8487 for Android, correct behavior for bridges that listen on more than
8488 one address, more extensible and flexible directory object handling,
8489 better reporting of network statistics, improved code security, and
8490 many many other features and bugfixes.
8493 Changes in version 0.2.2.31-rc - 2011-08-17
8494 Tor 0.2.2.31-rc is the second and hopefully final release candidate
8495 for the Tor 0.2.2.x series.
8498 - Remove an extra pair of quotation marks around the error
8499 message in control-port STATUS_GENERAL BUG events. Bugfix on
8500 0.1.2.6-alpha; fixes bug 3732.
8501 - If we're configured to write our ControlPorts to disk, only write
8502 them after switching UID and creating the data directory. This way,
8503 we don't fail when starting up with a nonexistent DataDirectory
8504 and a ControlPortWriteToFile setting based on that directory. Fixes
8505 bug 3747; bugfix on Tor 0.2.2.26-beta.
8508 - Update to the August 2 2011 Maxmind GeoLite Country database.
8511 - Allow GETINFO fingerprint to return a fingerprint even when
8512 we have not yet built a router descriptor. Fixes bug 3577;
8513 bugfix on 0.2.0.1-alpha.
8514 - Write several files in text mode, on OSes that distinguish text
8515 mode from binary mode (namely, Windows). These files are:
8516 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
8517 that collect those statistics; 'client_keys' and 'hostname' for
8518 hidden services that use authentication; and (in the tor-gencert
8519 utility) newly generated identity and signing keys. Previously,
8520 we wouldn't specify text mode or binary mode, leading to an
8521 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
8522 the DirRecordUsageByCountry option which would have triggered
8523 the assertion failure was added), although this assertion failure
8524 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
8525 - Selectively disable deprecation warnings on OS X because Lion
8526 started deprecating the shipped copy of openssl. Fixes bug 3643.
8527 - When unable to format an address as a string, report its value
8528 as "???" rather than reusing the last formatted address. Bugfix
8532 Changes in version 0.2.3.2-alpha - 2011-07-18
8533 Tor 0.2.3.2-alpha introduces two new experimental features:
8534 microdescriptors and pluggable transports. It also continues cleaning
8535 up a variety of recently introduced features.
8538 - Clients can now use microdescriptors instead of regular descriptors
8539 to build circuits. Microdescriptors are authority-generated
8540 summaries of regular descriptors' contents, designed to change
8541 very rarely (see proposal 158 for details). This feature is
8542 designed to save bandwidth, especially for clients on slow internet
8543 connections. It's off by default for now, since nearly no caches
8544 support it, but it will be on-by-default for clients in a future
8545 version. You can use the UseMicrodescriptors option to turn it on.
8546 - Tor clients using bridges can now be configured to use a separate
8547 'transport' proxy for each bridge. This approach helps to resist
8548 censorship by allowing bridges to use protocol obfuscation
8549 plugins. It implements part of proposal 180. Implements ticket 2841.
8550 - While we're trying to bootstrap, record how many TLS connections
8551 fail in each state, and report which states saw the most failures
8552 in response to any bootstrap failures. This feature may speed up
8553 diagnosis of censorship events. Implements ticket 3116.
8555 o Major bugfixes (on 0.2.3.1-alpha):
8556 - When configuring a large set of nodes in EntryNodes (as with
8557 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
8558 random subset to be guards, and choose them in random
8559 order. Fixes bug 2798.
8560 - Tor could crash when remembering a consensus in a non-used consensus
8561 flavor without having a current consensus set. Fixes bug 3361.
8562 - Comparing an unknown address to a microdescriptor's shortened exit
8563 policy would always give a "rejected" result. Fixes bug 3599.
8564 - Using microdescriptors as a client no longer prevents Tor from
8565 uploading and downloading hidden service descriptors. Fixes
8569 - Allow nameservers with IPv6 address. Resolves bug 2574.
8570 - Accept attempts to include a password authenticator in the
8571 handshake, as supported by SOCKS5. This handles SOCKS clients that
8572 don't know how to omit a password when authenticating. Resolves
8574 - When configuring a large set of nodes in EntryNodes, and there are
8575 enough of them listed as Guard so that we don't need to consider
8576 the non-guard entries, prefer the ones listed with the Guard flag.
8577 - Check for and recover from inconsistency in the microdescriptor
8578 cache. This will make it harder for us to accidentally free a
8579 microdescriptor without removing it from the appropriate data
8580 structures. Fixes issue 3135; issue noted by "wanoskarnet".
8581 - Log SSL state transitions at log level DEBUG, log domain
8582 HANDSHAKE. This can be useful for debugging censorship events.
8583 Implements ticket 3264.
8584 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
8585 implements ticket 3439.
8587 o Minor bugfixes (on 0.2.3.1-alpha):
8588 - Do not free all general-purpose regular descriptors just
8589 because microdescriptor use is enabled. Fixes bug 3113.
8590 - Correctly link libevent_openssl when --enable-static-libevent
8591 is passed to configure. Fixes bug 3118.
8592 - Bridges should not complain during their heartbeat log messages that
8593 they are unlisted in the consensus: that's more or less the point
8594 of being a bridge. Fixes bug 3183.
8595 - Report a SIGNAL event to controllers when acting on a delayed
8596 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
8597 event to the controller if we acted on a SIGNAL NEWNYM command
8598 immediately, and otherwise not report a SIGNAL event for the
8599 command at all. Fixes bug 3349.
8600 - Fix a crash when handling the SIGNAL controller command or
8601 reporting ERR-level status events with bufferevents enabled. Found
8602 by Robert Ransom. Fixes bug 3367.
8603 - Always ship the tor-fw-helper manpage in our release tarballs.
8604 Fixes bug 3389. Reported by Stephen Walker.
8605 - Fix a class of double-mark-for-close bugs when bufferevents
8606 are enabled. Fixes bug 3403.
8607 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
8608 - Add SIGNAL to the list returned by the 'GETINFO events/names'
8609 control-port command. Fixes part of bug 3465.
8610 - Prevent using negative indices during unit test runs when read_all()
8611 fails. Spotted by coverity.
8612 - Fix a rare memory leak when checking the nodelist without it being
8613 present. Found by coverity.
8614 - Only try to download a microdescriptor-flavored consensus from
8615 a directory cache that provides them.
8617 o Minor bugfixes (on 0.2.2.x and earlier):
8618 - Assert that hidden-service-related operations are not performed
8619 using single-hop circuits. Previously, Tor would assert that
8620 client-side streams are not attached to single-hop circuits,
8621 but not that other sensitive operations on the client and service
8622 side are not performed using single-hop circuits. Fixes bug 3332;
8624 - Don't publish a new relay descriptor when we reload our onion key,
8625 unless the onion key has actually changed. Fixes bug 3263 and
8626 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
8627 - Allow GETINFO fingerprint to return a fingerprint even when
8628 we have not yet built a router descriptor. Fixes bug 3577;
8629 bugfix on 0.2.0.1-alpha.
8630 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
8631 on 0.2.2.4-alpha; fixes bug 3427.
8633 o Code simplification and refactoring:
8634 - Use tor_sscanf() in place of scanf() in more places through the
8635 code. This makes us a little more locale-independent, and
8636 should help shut up code-analysis tools that can't tell
8637 a safe sscanf string from a dangerous one.
8638 - Use tt_assert(), not tor_assert(), for checking for test failures.
8639 This makes the unit tests more able to go on in the event that
8641 - Split connection_about_to_close() into separate functions for each
8645 - On Windows, we now define the _WIN32_WINNT macros only if they
8646 are not already defined. This lets the person building Tor decide,
8647 if they want, to require a later version of Windows.
8650 Changes in version 0.2.2.30-rc - 2011-07-07
8651 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
8652 series. It fixes a few smaller bugs, but generally appears stable.
8653 Please test it and let us know whether it is!
8656 - Send a SUCCEEDED stream event to the controller when a reverse
8657 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
8658 discovered by katmagic.
8659 - Always NUL-terminate the sun_path field of a sockaddr_un before
8660 passing it to the kernel. (Not a security issue: kernels are
8661 smart enough to reject bad sockaddr_uns.) Found by Coverity;
8662 CID #428. Bugfix on Tor 0.2.0.3-alpha.
8663 - Don't stack-allocate the list of supplementary GIDs when we're
8664 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
8665 could take up to 256K, which is way too much stack. Found by
8666 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
8667 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
8668 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
8669 fixes part of bug 3465.
8670 - Fix a memory leak when receiving a descriptor for a hidden
8671 service we didn't ask for. Found by Coverity; CID #30. Bugfix
8675 - Update to the July 1 2011 Maxmind GeoLite Country database.
8678 Changes in version 0.2.2.29-beta - 2011-06-20
8679 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
8680 have bridge lines in their torrc but don't want to use them; gets
8681 us closer to having the control socket feature working on Debian;
8682 and fixes a variety of smaller bugs.
8685 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
8686 When we changed the default behavior to "use bridges if any
8687 are listed in the torrc", we surprised users who had bridges
8688 in their torrc files but who didn't actually want to use them.
8689 Partial resolution for bug 3354.
8692 - Don't attach new streams to old rendezvous circuits after SIGNAL
8693 NEWNYM. Previously, we would keep using an existing rendezvous
8694 circuit if it remained open (i.e. if it were kept open by a
8695 long-lived stream, or if a new stream were attached to it before
8696 Tor could notice that it was old and no longer in use). Bugfix on
8697 0.1.1.15-rc; fixes bug 3375.
8700 - Fix a bug when using ControlSocketsGroupWritable with User. The
8701 directory's group would be checked against the current group, not
8702 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
8703 bugfix on 0.2.2.26-beta.
8704 - Make connection_printf_to_buf()'s behavior sane. Its callers
8705 expect it to emit a CRLF iff the format string ends with CRLF;
8706 it actually emitted a CRLF iff (a) the format string ended with
8707 CRLF or (b) the resulting string was over 1023 characters long or
8708 (c) the format string did not end with CRLF *and* the resulting
8709 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
8710 fixes part of bug 3407.
8711 - Make send_control_event_impl()'s behavior sane. Its callers
8712 expect it to always emit a CRLF at the end of the string; it
8713 might have emitted extra control characters as well. Bugfix on
8714 0.1.1.9-alpha; fixes another part of bug 3407.
8715 - Make crypto_rand_int() check the value of its input correctly.
8716 Previously, it accepted values up to UINT_MAX, but could return a
8717 negative number if given a value above INT_MAX+1. Found by George
8718 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
8719 - Avoid a segfault when reading a malformed circuit build state
8720 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
8722 - When asked about a DNS record type we don't support via a
8723 client DNSPort, reply with NOTIMPL rather than an empty
8724 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
8725 - Fix a rare memory leak during stats writing. Found by coverity.
8728 - Update to the June 1 2011 Maxmind GeoLite Country database.
8730 o Code simplifications and refactoring:
8731 - Remove some dead code as indicated by coverity.
8732 - Remove a few dead assignments during router parsing. Found by
8734 - Add some forgotten return value checks during unit tests. Found
8736 - Don't use 1-bit wide signed bit fields. Found by coverity.
8739 Changes in version 0.2.2.28-beta - 2011-06-04
8740 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
8741 fixed a big bug in whether relays stay in the consensus consistently,
8742 we moved closer to handling bridges and hidden services correctly,
8743 and we started the process of better handling the dreaded "my Vidalia
8744 died, and now my Tor demands a password when I try to reconnect to it"
8748 - Don't decide to make a new descriptor when receiving a HUP signal.
8749 This bug has caused a lot of 0.2.2.x relays to disappear from the
8750 consensus periodically. Fixes the most common case of triggering
8751 bug 1810; bugfix on 0.2.2.7-alpha.
8752 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
8753 - Don't try to build descriptors if "ORPort auto" is set and we
8754 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
8756 - Resolve a crash that occurred when setting BridgeRelay to 1 with
8757 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
8758 - Apply circuit timeouts to opened hidden-service-related circuits
8759 based on the correct start time. Previously, we would apply the
8760 circuit build timeout based on time since the circuit's creation;
8761 it was supposed to be applied based on time since the circuit
8762 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
8763 - Use the same circuit timeout for client-side introduction
8764 circuits as for other four-hop circuits, rather than the timeout
8765 for single-hop directory-fetch circuits; the shorter timeout may
8766 have been appropriate with the static circuit build timeout in
8767 0.2.1.x and earlier, but caused many hidden service access attempts
8768 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
8769 on 0.2.2.2-alpha; fixes another part of bug 1297.
8770 - In ticket 2511 we fixed a case where you could use an unconfigured
8771 bridge if you had configured it as a bridge the last time you ran
8772 Tor. Now fix another edge case: if you had configured it as a bridge
8773 but then switched to a different bridge via the controller, you
8774 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
8778 - Add an __OwningControllerProcess configuration option and a
8779 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
8780 that when it exits, Tor will shut down. Implements feature 3049.
8781 - If "UseBridges 1" is set and no bridges are configured, Tor will
8782 now refuse to build any circuits until some bridges are set.
8783 If "UseBridges auto" is set, Tor will use bridges if they are
8784 configured and we are not running as a server, but otherwise will
8785 make circuits as usual. The new default is "auto". Patch by anonym,
8786 so the Tails LiveCD can stop automatically revealing you as a Tor
8790 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
8791 - Remove a trailing asterisk from "exit-policy/default" in the
8792 output of the control port command "GETINFO info/names". Bugfix
8794 - Use a wide type to hold sockets when built for 64-bit Windows builds.
8796 - Warn when the user configures two HiddenServiceDir lines that point
8797 to the same directory. Bugfix on 0.0.6 (the version introducing
8798 HiddenServiceDir); fixes bug 3289.
8799 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
8800 part of bug 2748; bugfix on 0.2.0.10-alpha.
8801 - Log malformed requests for rendezvous descriptors as protocol
8802 warnings, not warnings. Also, use a more informative log message
8803 in case someone sees it at log level warning without prior
8804 info-level messages. Fixes the other part of bug 2748; bugfix
8806 - Clear the table recording the time of the last request for each
8807 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
8808 Previously, we would clear our HS descriptor cache on SIGNAL
8809 NEWNYM, but if we had previously retrieved a descriptor (or tried
8810 to) from every directory responsible for it, we would refuse to
8811 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
8813 - Fix a log message that said "bits" while displaying a value in
8814 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
8816 - When checking for 1024-bit keys, check for 1024 bits, not 128
8817 bytes. This allows Tor to correctly discard keys of length 1017
8818 through 1023. Bugfix on 0.0.9pre5.
8821 - Relays now log the reason for publishing a new relay descriptor,
8822 so we have a better chance of hunting down instances of bug 1810.
8823 Resolves ticket 3252.
8824 - Revise most log messages that refer to nodes by nickname to
8825 instead use the "$key=nickname at address" format. This should be
8826 more useful, especially since nicknames are less and less likely
8827 to be unique. Resolves ticket 3045.
8828 - Log (at info level) when purging pieces of hidden-service-client
8829 state because of SIGNAL NEWNYM.
8832 - Remove undocumented option "-F" from tor-resolve: it hasn't done
8833 anything since 0.2.1.16-rc.
8836 Changes in version 0.2.2.27-beta - 2011-05-18
8837 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
8838 release, and also adds a few more general bugfixes.
8841 - Fix a crash bug when changing bridges in a running Tor process.
8842 Fixes bug 3213; bugfix on 0.2.2.26-beta.
8843 - When the controller configures a new bridge, don't wait 10 to 60
8844 seconds before trying to fetch its descriptor. Bugfix on
8845 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
8848 - Require that onion keys have exponent 65537 in microdescriptors too.
8849 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
8850 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
8851 Changed the limit to 512 characters by removing base64 newlines.
8852 Fixes bug 2752. Fix by Michael Yakubovich.
8853 - When a client starts or stops using bridges, never use a circuit
8854 that was built before the configuration change. This behavior could
8855 put at risk a user who uses bridges to ensure that her traffic
8856 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
8860 Changes in version 0.2.2.26-beta - 2011-05-17
8861 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
8862 also introduces a new "socksport auto" approach that should make it
8863 easier to run multiple Tors on the same system, and does a lot of
8864 cleanup to get us closer to a release candidate.
8866 o Security/privacy fixes:
8867 - Replace all potentially sensitive memory comparison operations
8868 with versions whose runtime does not depend on the data being
8869 compared. This will help resist a class of attacks where an
8870 adversary can use variations in timing information to learn
8871 sensitive data. Fix for one case of bug 3122. (Safe memcmp
8872 implementation by Robert Ransom based partially on code by DJB.)
8873 - When receiving a hidden service descriptor, check that it is for
8874 the hidden service we wanted. Previously, Tor would store any
8875 hidden service descriptors that a directory gave it, whether it
8876 wanted them or not. This wouldn't have let an attacker impersonate
8877 a hidden service, but it did let directories pre-seed a client
8878 with descriptors that it didn't want. Bugfix on 0.0.6.
8879 - On SIGHUP, do not clear out all TrackHostExits mappings, client
8880 DNS cache entries, and virtual address mappings: that's what
8881 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
8884 - The options SocksPort, ControlPort, and so on now all accept a
8885 value "auto" that opens a socket on an OS-selected port. A
8886 new ControlPortWriteToFile option tells Tor to write its
8887 actual control port or ports to a chosen file. If the option
8888 ControlPortFileGroupReadable is set, the file is created as
8889 group-readable. Now users can run two Tor clients on the same
8890 system without needing to manually mess with parameters. Resolves
8891 part of ticket 3076.
8892 - Set SO_REUSEADDR on all sockets, not just listeners. This should
8893 help busy exit nodes avoid running out of useable ports just
8894 because all the ports have been used in the near past. Resolves
8898 - New "GETINFO net/listeners/(type)" controller command to return
8899 a list of addresses and ports that are bound for listeners for a
8900 given connection type. This is useful when the user has configured
8901 "SocksPort auto" and the controller needs to know which port got
8902 chosen. Resolves another part of ticket 3076.
8903 - Add a new ControlSocketsGroupWritable configuration option: when
8904 it is turned on, ControlSockets are group-writeable by the default
8905 group of the current user. Patch by Jérémy Bobbio; implements
8907 - Tor now refuses to create a ControlSocket in a directory that is
8908 world-readable (or group-readable if ControlSocketsGroupWritable
8909 is 0). This is necessary because some operating systems do not
8910 enforce permissions on an AF_UNIX sockets. Permissions on the
8911 directory holding the socket, however, seems to work everywhere.
8912 - Rate-limit a warning about failures to download v2 networkstatus
8913 documents. Resolves part of bug 1352.
8914 - Backport code from 0.2.3.x that allows directory authorities to
8915 clean their microdescriptor caches. Needed to resolve bug 2230.
8916 - When an HTTPS proxy reports "403 Forbidden", we now explain
8917 what it means rather than calling it an unexpected status code.
8918 Closes bug 2503. Patch from Michael Yakubovich.
8919 - Update to the May 1 2011 Maxmind GeoLite Country database.
8922 - Authorities now clean their microdesc cache periodically and when
8923 reading from disk initially, not only when adding new descriptors.
8924 This prevents a bug where we could lose microdescriptors. Bugfix
8925 on 0.2.2.6-alpha. Fixes bug 2230.
8926 - Do not crash when our configuration file becomes unreadable, for
8927 example due to a permissions change, between when we start up
8928 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
8930 - Avoid a bug that would keep us from replacing a microdescriptor
8931 cache on Windows. (We would try to replace the file while still
8932 holding it open. That's fine on Unix, but Windows doesn't let us
8933 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
8934 - Add missing explanations for the authority-related torrc options
8935 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
8936 man page. Resolves issue 2379.
8937 - As an authority, do not upload our own vote or signature set to
8938 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
8939 it would get flagged as a duplicate. Resolves bug 3026.
8940 - Accept hidden service descriptors if we think we might be a hidden
8941 service directory, regardless of what our consensus says. This
8942 helps robustness, since clients and hidden services can sometimes
8943 have a more up-to-date view of the network consensus than we do,
8944 and if they think that the directory authorities list us a HSDir,
8945 we might actually be one. Related to bug 2732; bugfix on
8947 - When a controller changes TrackHostExits, remove mappings for
8948 hosts that should no longer have their exits tracked. Bugfix on
8950 - When a controller changes VirtualAddrNetwork, remove any mappings
8951 for hosts that were automapped to the old network. Bugfix on
8953 - When a controller changes one of the AutomapHosts* options, remove
8954 any mappings for hosts that should no longer be automapped. Bugfix
8956 - Do not reset the bridge descriptor download status every time we
8957 re-parse our configuration or get a configuration change. Fixes
8958 bug 3019; bugfix on 0.2.0.3-alpha.
8960 o Minor bugfixes (code cleanup):
8961 - When loading the microdesc journal, remember its current size.
8962 In 0.2.2, this helps prevent the microdesc journal from growing
8963 without limit on authorities (who are the only ones to use it in
8964 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
8965 Fix posted by "cypherpunks."
8966 - The microdesc journal is supposed to get rebuilt only if it is
8967 at least _half_ the length of the store, not _twice_ the length
8968 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
8969 - Fix a potential null-pointer dereference while computing a
8970 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
8972 - Avoid a possible null-pointer dereference when rebuilding the mdesc
8973 cache without actually having any descriptors to cache. Bugfix on
8974 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
8975 - If we fail to compute the identity digest of a v3 legacy keypair,
8976 warn, and don't use a buffer-full of junk instead. Bugfix on
8977 0.2.1.1-alpha; fixes bug 3106.
8978 - Resolve an untriggerable issue in smartlist_string_num_isin(),
8979 where if the function had ever in the future been used to check
8980 for the presence of a too-large number, it would have given an
8981 incorrect result. (Fortunately, we only used it for 16-bit
8982 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
8983 - Require that introduction point keys and onion handshake keys
8984 have a public exponent of 65537. Starts to fix bug 3207; bugfix
8988 - Caches no longer download and serve v2 networkstatus documents
8989 unless FetchV2Networkstatus flag is set: these documents haven't
8990 haven't been used by clients or relays since 0.2.0.x. Resolves
8994 Changes in version 0.2.3.1-alpha - 2011-05-05
8995 Tor 0.2.3.1-alpha adds some new experimental features, including support
8996 for an improved network IO backend, IOCP networking on Windows,
8997 microdescriptor caching, "fast-start" support for streams, and automatic
8998 home router configuration. There are also numerous internal improvements
8999 to try to make the code easier for developers to work with.
9001 This is the first alpha release in a new series, so expect there to be
9002 bugs. Users who would rather test out a more stable branch should
9003 stay with 0.2.2.x for now.
9006 - Tor can now optionally build with the "bufferevents" buffered IO
9007 backend provided by Libevent 2. To use this feature, make sure you
9008 have the latest possible version of Libevent, and pass the
9009 --enable-bufferevents flag to configure when building Tor from
9010 source. This feature will make our networking code more flexible,
9011 let us stack layers on each other, and let us use more efficient
9012 zero-copy transports where available.
9013 - As an experimental feature, Tor can use IOCP for networking on Windows.
9014 Once this code is tuned and optimized, it promises much better
9015 performance than the select-based backend we've used in the past. To
9016 try this feature, you must build Tor with Libevent 2, configure Tor
9017 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
9018 your torrc. There are known bugs here: only try this if you can help
9019 debug it as it breaks.
9020 - The EntryNodes option can now include country codes like {de} or IP
9021 addresses or network masks. Previously we had disallowed these options
9022 because we didn't have an efficient way to keep the list up to
9023 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
9024 - Exit nodes now accept and queue data on not-yet-connected streams.
9025 Previously, the client wasn't allowed to send data until the stream was
9026 connected, which slowed down all connections. This change will enable
9027 clients to perform a "fast-start" on streams and send data without
9028 having to wait for a confirmation that the stream has opened. (Patch
9029 from Ian Goldberg; implements the server side of Proposal 174.)
9030 - Tor now has initial support for automatic port mapping on the many
9031 home routers that support NAT-PMP or UPnP. (Not yet supported on
9032 Windows). To build the support code, you'll need to have libnatpnp
9033 library and/or the libminiupnpc library, and you'll need to enable the
9034 feature specifically by passing "--enable-upnp" and/or
9035 "--enable-natpnp" to configure. To turn it on, use the new
9036 PortForwarding option.
9037 - Caches now download, cache, and serve multiple "flavors" of the
9038 consensus, including a flavor that describes microdescriptors.
9039 - Caches now download, cache, and serve microdescriptors -- small
9040 summaries of router descriptors that are authenticated by all of the
9041 directory authorities. Once enough caches are running this code,
9042 clients will be able to save significant amounts of directory bandwidth
9043 by downloading microdescriptors instead of router descriptors.
9046 - Make logging resolution configurable with a new LogTimeGranularity
9047 option, and change the default from 1 millisecond to 1 second.
9048 Implements enhancement 1668.
9049 - We log which torrc file we're using on startup. Implements ticket
9051 - Ordinarily, Tor does not count traffic from private addresses (like
9052 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
9053 There is now a new option, CountPrivateBandwidth, to disable this
9054 behavior. Patch from Daniel Cagara.
9055 - New --enable-static-tor configure option for building Tor as
9056 statically as possible. Idea, general hackery and thoughts from
9057 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
9059 - If you set the NumCPUs option to 0, Tor will now try to detect how
9060 many CPUs you have. This is the new default behavior.
9061 - Turn on directory request statistics by default and include them in
9062 extra-info descriptors. Don't break if we have no GeoIP database.
9063 - Relays that set "ConnDirectionStatistics 1" write statistics on the
9064 bidirectional use of connections to disk every 24 hours.
9065 - Add a GeoIP file digest to the extra-info descriptor. Implements
9067 - The NodeFamily option -- which let you declare that you want to
9068 consider nodes to be part of a family whether they list themselves
9069 that way or not -- now allows IP address ranges and country codes.
9070 - Add a new 'Heartbeat' log message type to periodically log a message
9071 describing Tor's status at level Notice. This feature is meant for
9072 operators who log at notice, and want to make sure that their Tor
9073 server is still working. Implementation by George Kadianakis.
9075 o Minor bugfixes (on 0.2.2.25-alpha):
9076 - When loading the microdesc journal, remember its current size.
9077 In 0.2.2, this helps prevent the microdesc journal from growing
9078 without limit on authorities (who are the only ones to use it in
9079 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
9080 Fix posted by "cypherpunks."
9081 - The microdesc journal is supposed to get rebuilt only if it is
9082 at least _half_ the length of the store, not _twice_ the length
9083 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
9084 - If as an authority we fail to compute the identity digest of a v3
9085 legacy keypair, warn, and don't use a buffer-full of junk instead.
9086 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
9087 - Authorities now clean their microdesc cache periodically and when
9088 reading from disk initially, not only when adding new descriptors.
9089 This prevents a bug where we could lose microdescriptors. Bugfix
9092 o Minor features (controller):
9093 - Add a new SIGNAL event to the controller interface so that
9094 controllers can be notified when Tor handles a signal. Resolves
9095 issue 1955. Patch by John Brooks.
9096 - Add a new GETINFO option to get total bytes read and written. Patch
9097 from pipe, revised by atagar. Resolves ticket 2345.
9098 - Implement some GETINFO controller fields to provide information about
9099 the Tor process's pid, euid, username, and resource limits.
9102 - Our build system requires automake 1.6 or later to create the
9103 Makefile.in files. Previously, you could have used 1.4.
9104 This only affects developers and people building Tor from git;
9105 people who build Tor from the source distribution without changing
9106 the Makefile.am files should be fine.
9107 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
9108 so on. This is more robust against some of the failure modes
9109 associated with running the autotools pieces on their own.
9111 o Minor packaging issues:
9112 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
9113 already created. Patch from Andreas Stieger. Fixes bug 2573.
9115 o Code simplifications and refactoring:
9116 - A major revision to our internal node-selecting and listing logic.
9117 Tor already had at least two major ways to look at the question of
9118 "which Tor servers do we know about": a list of router descriptors,
9119 and a list of entries in the current consensus. With
9120 microdescriptors, we're adding a third. Having so many systems
9121 without an abstraction layer over them was hurting the codebase.
9122 Now, we have a new "node_t" abstraction that presents a consistent
9123 interface to a client's view of a Tor node, and holds (nearly) all
9124 of the mutable state formerly in routerinfo_t and routerstatus_t.
9125 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
9126 no longer link against Libevent: they never used it, but
9127 our library structure used to force them to link it.
9130 - Remove some old code to work around even older versions of Tor that
9131 used forked processes to handle DNS requests. Such versions of Tor
9132 are no longer in use as servers.
9134 o Documentation fixes:
9135 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
9136 - Add missing documentation for the authority-related torrc options
9137 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
9141 Changes in version 0.2.2.25-alpha - 2011-04-29
9142 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
9143 robust, routers no longer overreport their bandwidth, Win7 should crash
9144 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
9145 now prevents hidden service-related activity from being linkable. It
9146 provides more information to Vidalia so you can see if your bridge is
9147 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
9148 StrictNodes configuration options to make them more reliable, more
9149 understandable, and more regularly applied. If you use those options,
9150 please see the revised documentation for them in the manual page.
9153 - Relays were publishing grossly inflated bandwidth values because
9154 they were writing their state files wrong--now they write the
9155 correct value. Also, resume reading bandwidth history from the
9156 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
9157 - Improve hidden service robustness: When we find that we have
9158 extended a hidden service's introduction circuit to a relay not
9159 listed as an introduction point in the HS descriptor we currently
9160 have, retry with an introduction point from the current
9161 descriptor. Previously we would just give up. Fixes bugs 1024 and
9162 1930; bugfix on 0.2.0.10-alpha.
9163 - Clients now stop trying to use an exit node associated with a given
9164 destination by TrackHostExits if they fail to reach that exit node.
9165 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
9166 - Fix crash bug on platforms where gmtime and localtime can return
9167 NULL. Windows 7 users were running into this one. Fixes part of bug
9168 2077. Bugfix on all versions of Tor. Found by boboper.
9170 o Security and stability fixes:
9171 - Don't double-free a parsable, but invalid, microdescriptor, even if
9172 it is followed in the blob we're parsing by an unparsable
9173 microdescriptor. Fixes an issue reported in a comment on bug 2954.
9174 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
9175 - If the Nickname configuration option isn't given, Tor would pick a
9176 nickname based on the local hostname as the nickname for a relay.
9177 Because nicknames are not very important in today's Tor and the
9178 "Unnamed" nickname has been implemented, this is now problematic
9179 behavior: It leaks information about the hostname without being
9180 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
9181 introduced the Unnamed nickname. Reported by tagnaq.
9182 - Fix an uncommon assertion failure when running with DNSPort under
9183 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
9184 - Avoid linkability based on cached hidden service descriptors: forget
9185 all hidden service descriptors cached as a client when processing a
9186 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
9189 - Export GeoIP information on bridge usage to controllers even if we
9190 have not yet been running for 24 hours. Now Vidalia bridge operators
9191 can get more accurate and immediate feedback about their
9192 contributions to the network.
9194 o Major features and bugfixes (node selection):
9195 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
9196 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
9197 options. Previously, we had been ambiguous in describing what
9198 counted as an "exit" node, and what operations exactly "StrictNodes
9199 0" would permit. This created confusion when people saw nodes built
9200 through unexpected circuits, and made it hard to tell real bugs from
9201 surprises. Now the intended behavior is:
9202 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
9203 a node that delivers user traffic outside the Tor network.
9204 . "Entry", in the context of EntryNodes, means a node used as the
9205 first hop of a multihop circuit. It doesn't include direct
9206 connections to directory servers.
9207 . "ExcludeNodes" applies to all nodes.
9208 . "StrictNodes" changes the behavior of ExcludeNodes only. When
9209 StrictNodes is set, Tor should avoid all nodes listed in
9210 ExcludeNodes, even when it will make user requests fail. When
9211 StrictNodes is *not* set, then Tor should follow ExcludeNodes
9212 whenever it can, except when it must use an excluded node to
9213 perform self-tests, connect to a hidden service, provide a
9214 hidden service, fulfill a .exit request, upload directory
9215 information, or fetch directory information.
9216 Collectively, the changes to implement the behavior fix bug 1090.
9217 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
9218 a node is listed in both, it's treated as excluded.
9219 - ExcludeNodes now applies to directory nodes -- as a preference if
9220 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
9221 Don't exclude all the directory authorities and set StrictNodes to 1
9222 unless you really want your Tor to break.
9223 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
9224 - ExcludeExitNodes now overrides .exit requests.
9225 - We don't use bridges listed in ExcludeNodes.
9226 - When StrictNodes is 1:
9227 . We now apply ExcludeNodes to hidden service introduction points
9228 and to rendezvous points selected by hidden service users. This
9229 can make your hidden service less reliable: use it with caution!
9230 . If we have used ExcludeNodes on ourself, do not try relay
9231 reachability self-tests.
9232 . If we have excluded all the directory authorities, we will not
9233 even try to upload our descriptor if we're a relay.
9234 . Do not honor .exit requests to an excluded node.
9235 - Remove a misfeature that caused us to ignore the Fast/Stable flags
9236 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
9237 - When the set of permitted nodes changes, we now remove any mappings
9238 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
9240 - We never cannibalize a circuit that had excluded nodes on it, even
9241 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
9242 - Revert a change where we would be laxer about attaching streams to
9243 circuits than when building the circuits. This was meant to prevent
9244 a set of bugs where streams were never attachable, but our improved
9245 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
9246 - Keep track of how many times we launch a new circuit to handle a
9247 given stream. Too many launches could indicate an inconsistency
9248 between our "launch a circuit to handle this stream" logic and our
9249 "attach this stream to one of the available circuits" logic.
9250 - Improve log messages related to excluded nodes.
9253 - Fix a spurious warning when moving from a short month to a long
9254 month on relays with month-based BandwidthAccounting. Bugfix on
9255 0.2.2.17-alpha; fixes bug 3020.
9256 - When a client finds that an origin circuit has run out of 16-bit
9257 stream IDs, we now mark it as unusable for new streams. Previously,
9258 we would try to close the entire circuit. Bugfix on 0.0.6.
9259 - Add a forgotten cast that caused a compile warning on OS X 10.6.
9260 Bugfix on 0.2.2.24-alpha.
9261 - Be more careful about reporting the correct error from a failed
9262 connect() system call. Under some circumstances, it was possible to
9263 look at an incorrect value for errno when sending the end reason.
9264 Bugfix on 0.1.0.1-rc.
9265 - Correctly handle an "impossible" overflow cases in connection byte
9266 counting, where we write or read more than 4GB on an edge connection
9267 in a single second. Bugfix on 0.1.2.8-beta.
9268 - Correct the warning displayed when a rendezvous descriptor exceeds
9269 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
9271 - Clients and hidden services now use HSDir-flagged relays for hidden
9272 service descriptor downloads and uploads even if the relays have no
9273 DirPort set and the client has disabled TunnelDirConns. This will
9274 eventually allow us to give the HSDir flag to relays with no
9275 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
9276 - Downgrade "no current certificates known for authority" message from
9277 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
9278 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
9279 2917. Bugfix on 0.1.1.1-alpha.
9280 - Only limit the lengths of single HS descriptors, even when multiple
9281 HS descriptors are published to an HSDir relay in a single POST
9282 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
9283 - Write the current time into the LastWritten line in our state file,
9284 rather than the time from the previous write attempt. Also, stop
9285 trying to use a time of -1 in our log statements. Fixes bug 3039;
9286 bugfix on 0.2.2.14-alpha.
9287 - Be more consistent in our treatment of file system paths. "~" should
9288 get expanded to the user's home directory in the Log config option.
9289 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
9290 feature for the -f and --DataDirectory options.
9293 - Make sure every relay writes a state file at least every 12 hours.
9294 Previously, a relay could go for weeks without writing its state
9295 file, and on a crash could lose its bandwidth history, capacity
9296 estimates, client country statistics, and so on. Addresses bug 3012.
9297 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
9298 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
9299 clients are already deprecated because of security bugs.
9300 - Don't allow v0 hidden service authorities to act as clients.
9301 Required by fix for bug 3000.
9302 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
9303 by fix for bug 3000.
9304 - Ensure that no empty [dirreq-](read|write)-history lines are added
9305 to an extrainfo document. Implements ticket 2497.
9307 o Code simplification and refactoring:
9308 - Remove workaround code to handle directory responses from servers
9309 that had bug 539 (they would send HTTP status 503 responses _and_
9310 send a body too). Since only server versions before
9311 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
9312 keep the workaround in place.
9313 - Remove the old 'fuzzy time' logic. It was supposed to be used for
9314 handling calculations where we have a known amount of clock skew and
9315 an allowed amount of unknown skew. But we only used it in three
9316 places, and we never adjusted the known/unknown skew values. This is
9317 still something we might want to do someday, but if we do, we'll
9318 want to do it differently.
9319 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
9320 None of the cases where we did this before were wrong, but by making
9321 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
9322 - Use GetTempDir to find the proper temporary directory location on
9323 Windows when generating temporary files for the unit tests. Patch by
9327 Changes in version 0.2.2.24-alpha - 2011-04-08
9328 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
9329 prevented Tor clients from effectively using "multihomed" bridges,
9330 that is, bridges that listen on multiple ports or IP addresses so users
9331 can continue to use some of their addresses even if others get blocked.
9334 - Fix a bug where bridge users who configure the non-canonical
9335 address of a bridge automatically switch to its canonical
9336 address. If a bridge listens at more than one address, it should be
9337 able to advertise those addresses independently and any non-blocked
9338 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
9340 - If you configured Tor to use bridge A, and then quit and
9341 configured Tor to use bridge B instead, it would happily continue
9342 to use bridge A if it's still reachable. While this behavior is
9343 a feature if your goal is connectivity, in some scenarios it's a
9344 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
9345 - Directory authorities now use data collected from their own
9346 uptime observations when choosing whether to assign the HSDir flag
9347 to relays, instead of trusting the uptime value the relay reports in
9348 its descriptor. This change helps prevent an attack where a small
9349 set of nodes with frequently-changing identity keys can blackhole
9350 a hidden service. (Only authorities need upgrade; others will be
9351 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
9354 - When we restart our relay, we might get a successful connection
9355 from the outside before we've started our reachability tests,
9356 triggering a warning: "ORPort found reachable, but I have no
9357 routerinfo yet. Failing to inform controller of success." This
9358 bug was harmless unless Tor is running under a controller
9359 like Vidalia, in which case the controller would never get a
9360 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
9362 - Make directory authorities more accurate at recording when
9363 relays that have failed several reachability tests became
9364 unreachable, so we can provide more accuracy at assigning Stable,
9365 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
9366 - Fix an issue that prevented static linking of libevent on
9367 some platforms (notably Linux). Fixes bug 2698; bugfix on
9368 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
9369 the --with-static-libevent configure option).
9370 - We now ask the other side of a stream (the client or the exit)
9371 for more data on that stream when the amount of queued data on
9372 that stream dips low enough. Previously, we wouldn't ask the
9373 other side for more data until either it sent us more data (which
9374 it wasn't supposed to do if it had exhausted its window!) or we
9375 had completely flushed all our queued data. This flow control fix
9376 should improve throughput. Fixes bug 2756; bugfix on the earliest
9377 released versions of Tor (svn commit r152).
9378 - Avoid a double-mark-for-free warning when failing to attach a
9379 transparent proxy connection. (We thought we had fixed this in
9380 0.2.2.23-alpha, but it turns out our fix was checking the wrong
9381 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
9382 bug) and 0.2.2.23-alpha (the incorrect fix).
9383 - When warning about missing zlib development packages during compile,
9384 give the correct package names. Bugfix on 0.2.0.1-alpha.
9387 - Directory authorities now log the source of a rejected POSTed v3
9389 - Make compilation with clang possible when using
9390 --enable-gcc-warnings by removing two warning options that clang
9391 hasn't implemented yet and by fixing a few warnings. Implements
9393 - When expiring circuits, use microsecond timers rather than
9394 one-second timers. This can avoid an unpleasant situation where a
9395 circuit is launched near the end of one second and expired right
9396 near the beginning of the next, and prevent fluctuations in circuit
9398 - Use computed circuit-build timeouts to decide when to launch
9399 parallel introduction circuits for hidden services. (Previously,
9400 we would retry after 15 seconds.)
9401 - Update to the April 1 2011 Maxmind GeoLite Country database.
9404 - Create the /var/run/tor directory on startup on OpenSUSE if it is
9405 not already created. Patch from Andreas Stieger. Fixes bug 2573.
9407 o Documentation changes:
9408 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
9409 - Resolve all doxygen warnings except those for missing documentation.
9411 - Add doxygen documentation for more functions, fields, and types.
9414 Changes in version 0.2.2.23-alpha - 2011-03-08
9415 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
9416 they restart they don't lose their bandwidth capacity estimate. This
9417 release also fixes a diverse set of user-facing bugs, ranging from
9418 relays overrunning their rate limiting to clients falsely warning about
9419 clock skew to bridge descriptor leaks by our bridge directory authority.
9422 - Stop sending a CLOCK_SKEW controller status event whenever
9423 we fetch directory information from a relay that has a wrong clock.
9424 Instead, only inform the controller when it's a trusted authority
9425 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
9426 the rest of bug 1074.
9427 - Fix an assert in parsing router descriptors containing IPv6
9428 addresses. This one took down the directory authorities when
9429 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
9430 - Make the bridge directory authority refuse to answer directory
9431 requests for "all" descriptors. It used to include bridge
9432 descriptors in its answer, which was a major information leak.
9433 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
9434 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
9435 Tor would ignore their RelayBandwidthBurst setting,
9436 potentially using more bandwidth than expected. Bugfix on
9437 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
9438 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
9439 hidserv" in her torrc. The 'hidserv' argument never controlled
9440 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
9443 - Relays now save observed peak bandwidth throughput rates to their
9444 state file (along with total usage, which was already saved)
9445 so that they can determine their correct estimated bandwidth on
9446 restart. Resolves bug 1863, where Tor relays would reset their
9447 estimated bandwidth to 0 after restarting.
9448 - Directory authorities now take changes in router IP address and
9449 ORPort into account when determining router stability. Previously,
9450 if a router changed its IP or ORPort, the authorities would not
9451 treat it as having any downtime for the purposes of stability
9452 calculation, whereas clients would experience downtime since the
9453 change could take a while to propagate to them. Resolves issue 1035.
9454 - Enable Address Space Layout Randomization (ASLR) and Data Execution
9455 Prevention (DEP) by default on Windows to make it harder for
9456 attackers to exploit vulnerabilities. Patch from John Brooks.
9458 o Minor bugfixes (on 0.2.1.x and earlier):
9459 - Fix a rare crash bug that could occur when a client was configured
9460 with a large number of bridges. Fixes bug 2629; bugfix on
9461 0.2.1.2-alpha. Bugfix by trac user "shitlei".
9462 - Avoid a double mark-for-free warning when failing to attach a
9463 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
9465 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
9466 found by "cypherpunks". This bug was introduced before the first
9467 Tor release, in svn commit r110.
9468 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
9469 don't mention them in the manpage. Fixes bug 2450; issue
9470 spotted by keb and G-Lo.
9471 - Fix a bug in bandwidth history state parsing that could have been
9472 triggered if a future version of Tor ever changed the timing
9473 granularity at which bandwidth history is measured. Bugfix on
9475 - When a relay decides that its DNS is too broken for it to serve
9476 as an exit server, it advertised itself as a non-exit, but
9477 continued to act as an exit. This could create accidental
9478 partitioning opportunities for users. Instead, if a relay is
9479 going to advertise reject *:* as its exit policy, it should
9480 really act with exit policy "reject *:*". Fixes bug 2366.
9481 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
9482 - In the special case where you configure a public exit relay as your
9483 bridge, Tor would be willing to use that exit relay as the last
9484 hop in your circuit as well. Now we fail that circuit instead.
9485 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
9486 - Fix a bug with our locking implementation on Windows that couldn't
9487 correctly detect when a file was already locked. Fixes bug 2504,
9488 bugfix on 0.2.1.6-alpha.
9489 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
9490 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
9492 - Set target port in get_interface_address6() correctly. Bugfix
9493 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
9494 - Directory authorities are now more robust to hops back in time
9495 when calculating router stability. Previously, if a run of uptime
9496 or downtime appeared to be negative, the calculation could give
9497 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
9499 - Fix an assert that got triggered when using the TestingTorNetwork
9500 configuration option and then issuing a GETINFO config-text control
9501 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
9503 o Minor bugfixes (on 0.2.2.x):
9504 - Clients should not weight BadExit nodes as Exits in their node
9505 selection. Similarly, directory authorities should not count BadExit
9506 bandwidth as Exit bandwidth when computing bandwidth-weights.
9507 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
9508 - Correctly clear our dir_read/dir_write history when there is an
9509 error parsing any bw history value from the state file. Bugfix on
9511 - Resolve a bug in verifying signatures of directory objects
9512 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
9513 Fixes bug 2409. Found by "piebeer".
9514 - Bridge authorities no longer crash on SIGHUP when they try to
9515 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
9519 - Log less aggressively about circuit timeout changes, and improve
9520 some other circuit timeout messages. Resolves bug 2004.
9521 - Log a little more clearly about the times at which we're no longer
9522 accepting new connections. Resolves bug 2181.
9523 - Reject attempts at the client side to open connections to private
9524 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
9525 a randomly chosen exit node. Attempts to do so are always
9526 ill-defined, generally prevented by exit policies, and usually
9527 in error. This will also help to detect loops in transparent
9528 proxy configurations. You can disable this feature by setting
9529 "ClientRejectInternalAddresses 0" in your torrc.
9530 - Always treat failure to allocate an RSA key as an unrecoverable
9532 - Update to the March 1 2011 Maxmind GeoLite Country database.
9534 o Minor features (log subsystem):
9535 - Add documentation for configuring logging at different severities in
9536 different log domains. We've had this feature since 0.2.1.1-alpha,
9537 but for some reason it never made it into the manpage. Fixes
9539 - Make it simpler to specify "All log domains except for A and B".
9540 Previously you needed to say "[*,~A,~B]". Now you can just say
9542 - Add a "LogMessageDomains 1" option to include the domains of log
9543 messages along with the messages. Without this, there's no way
9544 to use log domains without reading the source or doing a lot
9547 o Packaging changes:
9548 - Stop shipping the Tor specs files and development proposal documents
9549 in the tarball. They are now in a separate git repository at
9550 git://git.torproject.org/torspec.git
9553 Changes in version 0.2.1.30 - 2011-02-23
9554 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
9555 change is a slight tweak to Tor's TLS handshake that makes relays
9556 and bridges that run this new version reachable from Iran again.
9557 We don't expect this tweak will win the arms race long-term, but it
9558 buys us time until we roll out a better solution.
9561 - Stop sending a CLOCK_SKEW controller status event whenever
9562 we fetch directory information from a relay that has a wrong clock.
9563 Instead, only inform the controller when it's a trusted authority
9564 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
9565 the rest of bug 1074.
9566 - Fix a bounds-checking error that could allow an attacker to
9567 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
9569 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
9570 Tor would ignore their RelayBandwidthBurst setting,
9571 potentially using more bandwidth than expected. Bugfix on
9572 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
9573 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
9574 hidserv" in her torrc. The 'hidserv' argument never controlled
9575 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
9578 - Adjust our TLS Diffie-Hellman parameters to match those used by
9580 - Update to the February 1 2011 Maxmind GeoLite Country database.
9583 - Check for and reject overly long directory certificates and
9584 directory tokens before they have a chance to hit any assertions.
9585 Bugfix on 0.2.1.28. Found by "doorss".
9586 - Bring the logic that gathers routerinfos and assesses the
9587 acceptability of circuits into line. This prevents a Tor OP from
9588 getting locked in a cycle of choosing its local OR as an exit for a
9589 path (due to a .exit request) and then rejecting the circuit because
9590 its OR is not listed yet. It also prevents Tor clients from using an
9591 OR running in the same instance as an exit (due to a .exit request)
9592 if the OR does not meet the same requirements expected of an OR
9593 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
9595 o Packaging changes:
9596 - Stop shipping the Tor specs files and development proposal documents
9597 in the tarball. They are now in a separate git repository at
9598 git://git.torproject.org/torspec.git
9599 - Do not include Git version tags as though they are SVN tags when
9600 generating a tarball from inside a repository that has switched
9601 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
9604 Changes in version 0.2.2.22-alpha - 2011-01-25
9605 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
9606 main other change is a slight tweak to Tor's TLS handshake that makes
9607 relays and bridges that run this new version reachable from Iran again.
9608 We don't expect this tweak will win the arms race long-term, but it
9609 will buy us a bit more time until we roll out a better solution.
9612 - Fix a bounds-checking error that could allow an attacker to
9613 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
9615 - Don't assert when changing from bridge to relay or vice versa
9616 via the controller. The assert happened because we didn't properly
9617 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
9618 bug 2433. Reported by bastik.
9621 - Adjust our TLS Diffie-Hellman parameters to match those used by
9623 - Provide a log message stating which geoip file we're parsing
9624 instead of just stating that we're parsing the geoip file.
9625 Implements ticket 2432.
9628 - Check for and reject overly long directory certificates and
9629 directory tokens before they have a chance to hit any assertions.
9630 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
9633 Changes in version 0.2.2.21-alpha - 2011-01-15
9634 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
9635 continues our recent code security audit work. The main fix resolves
9636 a remote heap overflow vulnerability that can allow remote code
9637 execution (CVE-2011-0427). Other fixes address a variety of assert
9638 and crash bugs, most of which we think are hard to exploit remotely.
9640 o Major bugfixes (security), also included in 0.2.1.29:
9641 - Fix a heap overflow bug where an adversary could cause heap
9642 corruption. This bug probably allows remote code execution
9643 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
9645 - Prevent a denial-of-service attack by disallowing any
9646 zlib-compressed data whose compression factor is implausibly
9647 high. Fixes part of bug 2324; reported by "doorss".
9648 - Zero out a few more keys in memory before freeing them. Fixes
9649 bug 2384 and part of bug 2385. These key instances found by
9650 "cypherpunks", based on Andrew Case's report about being able
9651 to find sensitive data in Tor's memory space if you have enough
9652 permissions. Bugfix on 0.0.2pre9.
9654 o Major bugfixes (crashes), also included in 0.2.1.29:
9655 - Prevent calls to Libevent from inside Libevent log handlers.
9656 This had potential to cause a nasty set of crashes, especially
9657 if running Libevent with debug logging enabled, and running
9658 Tor with a controller watching for low-severity log messages.
9659 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
9660 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
9661 underflow errors there too. Fixes the other part of bug 2324.
9662 - Fix a bug where we would assert if we ever had a
9663 cached-descriptors.new file (or another file read directly into
9664 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
9665 on 0.2.1.25. Found by doorss.
9666 - Fix some potential asserts and parsing issues with grossly
9667 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
9670 o Minor bugfixes (other), also included in 0.2.1.29:
9671 - Fix a bug with handling misformed replies to reverse DNS lookup
9672 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
9673 bug reported by doorss.
9674 - Fix compilation on mingw when a pthreads compatibility library
9675 has been installed. (We don't want to use it, so we shouldn't
9676 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
9677 - Fix a bug where we would declare that we had run out of virtual
9678 addresses when the address space was only half-exhausted. Bugfix
9680 - Correctly handle the case where AutomapHostsOnResolve is set but
9681 no virtual addresses are available. Fixes bug 2328; bugfix on
9682 0.1.2.1-alpha. Bug found by doorss.
9683 - Correctly handle wrapping around when we run out of virtual
9684 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
9686 o Minor features, also included in 0.2.1.29:
9687 - Update to the January 1 2011 Maxmind GeoLite Country database.
9688 - Introduce output size checks on all of our decryption functions.
9690 o Build changes, also included in 0.2.1.29:
9691 - Tor does not build packages correctly with Automake 1.6 and earlier;
9692 added a check to Makefile.am to make sure that we're building with
9693 Automake 1.7 or later.
9694 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
9695 because we built it with a too-old version of automake. Thus that
9696 release broke ./configure --enable-openbsd-malloc, which is popular
9697 among really fast exit relays on Linux.
9699 o Major bugfixes, new in 0.2.2.21-alpha:
9700 - Prevent crash/heap corruption when the cbtnummodes consensus
9701 parameter is set to 0 or large values. Fixes bug 2317; bugfix
9704 o Major features, new in 0.2.2.21-alpha:
9705 - Introduce minimum/maximum values that clients will believe
9706 from the consensus. Now we'll have a better chance to avoid crashes
9707 or worse when a consensus param has a weird value.
9709 o Minor features, new in 0.2.2.21-alpha:
9710 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
9711 used on bridges, and it makes bridge scanning somewhat easier.
9712 - If writing the state file to disk fails, wait up to an hour before
9713 retrying again, rather than trying again each second. Fixes bug
9714 2346; bugfix on Tor 0.1.1.3-alpha.
9715 - Make Libevent log messages get delivered to controllers later,
9716 and not from inside the Libevent log handler. This prevents unsafe
9717 reentrant Libevent calls while still letting the log messages
9719 - Detect platforms that brokenly use a signed size_t, and refuse to
9720 build there. Found and analyzed by doorss and rransom.
9721 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
9724 o Minor bugfixes, new in 0.2.2.21-alpha:
9725 - Handle SOCKS messages longer than 128 bytes long correctly, rather
9726 than waiting forever for them to finish. Fixes bug 2330; bugfix
9727 on 0.2.0.16-alpha. Found by doorss.
9728 - Add assertions to check for overflow in arguments to
9729 base32_encode() and base32_decode(); fix a signed-unsigned
9730 comparison there too. These bugs are not actually reachable in Tor,
9731 but it's good to prevent future errors too. Found by doorss.
9732 - Correctly detect failures to create DNS requests when using Libevent
9733 versions before v2. (Before Libevent 2, we used our own evdns
9734 implementation. Its return values for Libevent's evdns_resolve_*()
9735 functions are not consistent with those from Libevent.) Fixes bug
9736 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
9738 o Documentation, new in 0.2.2.21-alpha:
9739 - Document the default socks host and port (127.0.0.1:9050) for
9743 Changes in version 0.2.1.29 - 2011-01-15
9744 Tor 0.2.1.29 continues our recent code security audit work. The main
9745 fix resolves a remote heap overflow vulnerability that can allow remote
9746 code execution. Other fixes address a variety of assert and crash bugs,
9747 most of which we think are hard to exploit remotely.
9749 o Major bugfixes (security):
9750 - Fix a heap overflow bug where an adversary could cause heap
9751 corruption. This bug probably allows remote code execution
9752 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
9754 - Prevent a denial-of-service attack by disallowing any
9755 zlib-compressed data whose compression factor is implausibly
9756 high. Fixes part of bug 2324; reported by "doorss".
9757 - Zero out a few more keys in memory before freeing them. Fixes
9758 bug 2384 and part of bug 2385. These key instances found by
9759 "cypherpunks", based on Andrew Case's report about being able
9760 to find sensitive data in Tor's memory space if you have enough
9761 permissions. Bugfix on 0.0.2pre9.
9763 o Major bugfixes (crashes):
9764 - Prevent calls to Libevent from inside Libevent log handlers.
9765 This had potential to cause a nasty set of crashes, especially
9766 if running Libevent with debug logging enabled, and running
9767 Tor with a controller watching for low-severity log messages.
9768 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
9769 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
9770 underflow errors there too. Fixes the other part of bug 2324.
9771 - Fix a bug where we would assert if we ever had a
9772 cached-descriptors.new file (or another file read directly into
9773 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
9774 on 0.2.1.25. Found by doorss.
9775 - Fix some potential asserts and parsing issues with grossly
9776 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
9779 o Minor bugfixes (other):
9780 - Fix a bug with handling misformed replies to reverse DNS lookup
9781 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
9782 bug reported by doorss.
9783 - Fix compilation on mingw when a pthreads compatibility library
9784 has been installed. (We don't want to use it, so we shouldn't
9785 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
9786 - Fix a bug where we would declare that we had run out of virtual
9787 addresses when the address space was only half-exhausted. Bugfix
9789 - Correctly handle the case where AutomapHostsOnResolve is set but
9790 no virtual addresses are available. Fixes bug 2328; bugfix on
9791 0.1.2.1-alpha. Bug found by doorss.
9792 - Correctly handle wrapping around to when we run out of virtual
9793 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
9794 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
9795 because we built it with a too-old version of automake. Thus that
9796 release broke ./configure --enable-openbsd-malloc, which is popular
9797 among really fast exit relays on Linux.
9800 - Update to the January 1 2011 Maxmind GeoLite Country database.
9801 - Introduce output size checks on all of our decryption functions.
9804 - Tor does not build packages correctly with Automake 1.6 and earlier;
9805 added a check to Makefile.am to make sure that we're building with
9806 Automake 1.7 or later.
9809 Changes in version 0.2.2.20-alpha - 2010-12-17
9810 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
9811 exploitable bugs. We also fix a variety of other significant bugs,
9812 change the IP address for one of our directory authorities, and update
9813 the minimum version that Tor relays must run to join the network.
9816 - Fix a remotely exploitable bug that could be used to crash instances
9817 of Tor remotely by overflowing on the heap. Remote-code execution
9818 hasn't been confirmed, but can't be ruled out. Everyone should
9819 upgrade. Bugfix on the 0.1.1 series and later.
9820 - Fix a bug that could break accounting on 64-bit systems with large
9821 time_t values, making them hibernate for impossibly long intervals.
9822 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
9823 - Fix a logic error in directory_fetches_from_authorities() that
9824 would cause all _non_-exits refusing single-hop-like circuits
9825 to fetch from authorities, when we wanted to have _exits_ fetch
9826 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
9828 - Fix a stream fairness bug that would cause newer streams on a given
9829 circuit to get preference when reading bytes from the origin or
9830 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
9831 introduced before the first Tor release, in svn revision r152.
9833 o Directory authority changes:
9834 - Change IP address and ports for gabelmoo (v3 directory authority).
9837 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
9838 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
9839 - Fix an off-by-one error in calculating some controller command
9840 argument lengths. Fortunately, this mistake is harmless since
9841 the controller code does redundant NUL termination too. Found by
9842 boboper. Bugfix on 0.1.1.1-alpha.
9843 - Do not dereference NULL if a bridge fails to build its
9844 extra-info descriptor. Found by an anonymous commenter on
9845 Trac. Bugfix on 0.2.2.19-alpha.
9848 - Update to the December 1 2010 Maxmind GeoLite Country database.
9849 - Directory authorities now reject relays running any versions of
9850 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
9851 known bugs that keep RELAY_EARLY cells from working on rendezvous
9852 circuits. Followup to fix for bug 2081.
9853 - Directory authorities now reject relays running any version of Tor
9854 older than 0.2.0.26-rc. That version is the earliest that fetches
9855 current directory information correctly. Fixes bug 2156.
9856 - Report only the top 10 ports in exit-port stats in order not to
9857 exceed the maximum extra-info descriptor length of 50 KB. Implements
9861 Changes in version 0.2.1.28 - 2010-12-17
9862 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
9863 exploitable bugs. We also took this opportunity to change the IP address
9864 for one of our directory authorities, and to update the geoip database
9868 - Fix a remotely exploitable bug that could be used to crash instances
9869 of Tor remotely by overflowing on the heap. Remote-code execution
9870 hasn't been confirmed, but can't be ruled out. Everyone should
9871 upgrade. Bugfix on the 0.1.1 series and later.
9873 o Directory authority changes:
9874 - Change IP address and ports for gabelmoo (v3 directory authority).
9877 - Update to the December 1 2010 Maxmind GeoLite Country database.
9880 Changes in version 0.2.1.27 - 2010-11-23
9881 Yet another OpenSSL security patch broke its compatibility with Tor:
9882 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
9883 also took this opportunity to fix several crash bugs, integrate a new
9884 directory authority, and update the bundled GeoIP database.
9887 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
9888 No longer set the tlsext_host_name extension on server SSL objects;
9889 but continue to set it on client SSL objects. Our goal in setting
9890 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
9891 bugfix on 0.2.1.1-alpha.
9892 - Do not log messages to the controller while shrinking buffer
9893 freelists. Doing so would sometimes make the controller connection
9894 try to allocate a buffer chunk, which would mess up the internals
9895 of the freelist and cause an assertion failure. Fixes bug 1125;
9896 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
9897 - Learn our external IP address when we're a relay or bridge, even if
9898 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
9899 where we introduced bridge relays that don't need to publish to
9900 be useful. Fixes bug 2050.
9901 - Do even more to reject (and not just ignore) annotations on
9902 router descriptors received anywhere but from the cache. Previously
9903 we would ignore such annotations at first, but cache them to disk
9904 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
9905 - When you're using bridges and your network goes away and your
9906 bridges get marked as down, recover when you attempt a new socks
9907 connection (if the network is back), rather than waiting up to an
9908 hour to try fetching new descriptors for your bridges. Bugfix on
9909 0.2.0.3-alpha; fixes bug 1981.
9912 - Move to the November 2010 Maxmind GeoLite country db (rather
9913 than the June 2009 ip-to-country GeoIP db) for our statistics that
9914 count how many users relays are seeing from each country. Now we'll
9915 have more accurate data, especially for many African countries.
9917 o New directory authorities:
9918 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
9922 - Fix an assertion failure that could occur in directory caches or
9923 bridge users when using a very short voting interval on a testing
9924 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
9926 - Enforce multiplicity rules when parsing annotations. Bugfix on
9927 0.2.0.8-alpha. Found by piebeer.
9928 - Allow handshaking OR connections to take a full KeepalivePeriod
9929 seconds to handshake. Previously, we would close them after
9930 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
9931 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
9933 - When building with --enable-gcc-warnings on OpenBSD, disable
9934 warnings in system headers. This makes --enable-gcc-warnings
9935 pass on OpenBSD 4.8.
9938 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
9939 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
9940 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
9941 Servers can start sending this code when enough clients recognize
9942 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
9943 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
9944 Patch from mingw-san.
9947 - Remove the old debian/ directory from the main Tor distribution.
9948 The official Tor-for-debian git repository lives at the URL
9949 https://git.torproject.org/debian/tor.git
9950 - Stop shipping the old doc/website/ directory in the tarball. We
9951 changed the website format in late 2010, and what we shipped in
9952 0.2.1.26 really wasn't that useful anyway.
9955 Changes in version 0.2.2.19-alpha - 2010-11-22
9956 Yet another OpenSSL security patch broke its compatibility with Tor:
9957 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
9960 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
9961 No longer set the tlsext_host_name extension on server SSL objects;
9962 but continue to set it on client SSL objects. Our goal in setting
9963 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
9964 bugfix on 0.2.1.1-alpha.
9967 - Try harder not to exceed the maximum length of 50 KB when writing
9968 statistics to extra-info descriptors. This bug was triggered by very
9969 fast relays reporting exit-port, entry, and dirreq statistics.
9970 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
9971 - Publish a router descriptor even if generating an extra-info
9972 descriptor fails. Previously we would not publish a router
9973 descriptor without an extra-info descriptor; this can cause fast
9974 exit relays collecting exit-port statistics to drop from the
9975 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
9978 Changes in version 0.2.2.18-alpha - 2010-11-16
9979 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
9980 us lately, makes unpublished bridge relays able to detect their IP
9981 address, and fixes a wide variety of other bugs to get us much closer
9982 to a stable release.
9985 - Do even more to reject (and not just ignore) annotations on
9986 router descriptors received anywhere but from the cache. Previously
9987 we would ignore such annotations at first, but cache them to disk
9988 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
9989 - Do not log messages to the controller while shrinking buffer
9990 freelists. Doing so would sometimes make the controller connection
9991 try to allocate a buffer chunk, which would mess up the internals
9992 of the freelist and cause an assertion failure. Fixes bug 1125;
9993 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
9994 - Learn our external IP address when we're a relay or bridge, even if
9995 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
9996 where we introduced bridge relays that don't need to publish to
9997 be useful. Fixes bug 2050.
9998 - Maintain separate TLS contexts and certificates for incoming and
9999 outgoing connections in bridge relays. Previously we would use the
10000 same TLS contexts and certs for incoming and outgoing connections.
10001 Bugfix on 0.2.0.3-alpha; addresses bug 988.
10002 - Maintain separate identity keys for incoming and outgoing TLS
10003 contexts in bridge relays. Previously we would use the same
10004 identity keys for incoming and outgoing TLS contexts. Bugfix on
10005 0.2.0.3-alpha; addresses the other half of bug 988.
10006 - Avoid an assertion failure when we as an authority receive a
10007 duplicate upload of a router descriptor that we already have,
10008 but which we previously considered an obsolete descriptor.
10009 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
10010 - Avoid a crash bug triggered by looking at a dangling pointer while
10011 setting the network status consensus. Found by Robert Ransom.
10012 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
10013 - Fix a logic error where servers that _didn't_ act as exits would
10014 try to keep their server lists more aggressively up to date than
10015 exits, when it was supposed to be the other way around. Bugfix
10018 o Minor bugfixes (on Tor 0.2.1.x and earlier):
10019 - When we're trying to guess whether we know our IP address as
10020 a relay, we would log various ways that we failed to guess
10021 our address, but never log that we ended up guessing it
10022 successfully. Now add a log line to help confused and anxious
10023 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
10024 - Bring the logic that gathers routerinfos and assesses the
10025 acceptability of circuits into line. This prevents a Tor OP from
10026 getting locked in a cycle of choosing its local OR as an exit for a
10027 path (due to a .exit request) and then rejecting the circuit because
10028 its OR is not listed yet. It also prevents Tor clients from using an
10029 OR running in the same instance as an exit (due to a .exit request)
10030 if the OR does not meet the same requirements expected of an OR
10031 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
10032 - Correctly describe errors that occur when generating a TLS object.
10033 Previously we would attribute them to a failure while generating a
10034 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
10036 - Enforce multiplicity rules when parsing annotations. Bugfix on
10037 0.2.0.8-alpha. Found by piebeer.
10038 - Fix warnings that newer versions of autoconf produced during
10039 ./autogen.sh. These warnings appear to be harmless in our case,
10040 but they were extremely verbose. Fixes bug 2020.
10042 o Minor bugfixes (on Tor 0.2.2.x):
10043 - Enable protection of small arrays whenever we build with gcc
10044 hardening features, not only when also building with warnings
10045 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
10048 - Make hidden services work better in private Tor networks by not
10049 requiring any uptime to join the hidden service descriptor
10050 DHT. Implements ticket 2088.
10051 - Rate-limit the "your application is giving Tor only an IP address"
10052 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
10053 - When AllowSingleHopExits is set, print a warning to explain to the
10054 relay operator why most clients are avoiding her relay.
10055 - Update to the November 1 2010 Maxmind GeoLite Country database.
10057 o Code simplifications and refactoring:
10058 - When we fixed bug 1038 we had to put in a restriction not to send
10059 RELAY_EARLY cells on rend circuits. This was necessary as long
10060 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
10061 active. Now remove this obsolete check. Resolves bug 2081.
10062 - Some options used different conventions for uppercasing of acronyms
10063 when comparing manpage and source. Fix those in favor of the
10064 manpage, as it makes sense to capitalize acronyms.
10065 - Remove the torrc.complete file. It hasn't been kept up to date
10066 and users will have better luck checking out the manpage.
10067 - Remove the obsolete "NoPublish" option; it has been flagged
10068 as obsolete and has produced a warning since 0.1.1.18-rc.
10069 - Remove everything related to building the expert bundle for OS X.
10070 It has confused many users, doesn't work right on OS X 10.6,
10071 and is hard to get rid of once installed. Resolves bug 1274.
10074 Changes in version 0.2.2.17-alpha - 2010-09-30
10075 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
10076 to use one-hop circuits (which can put the exit relays at higher risk,
10077 plus unbalance the network); fixes a big bug in bandwidth accounting
10078 for relays that want to limit their monthly bandwidth use; fixes a
10079 big pile of bugs in how clients tolerate temporary network failure;
10080 and makes our adaptive circuit build timeout feature (which improves
10081 client performance if your network is fast while not breaking things
10082 if your network is slow) better handle bad networks.
10085 - Exit relays now try harder to block exit attempts from unknown
10086 relays, to make it harder for people to use them as one-hop proxies
10087 a la tortunnel. Controlled by the refuseunknownexits consensus
10088 parameter (currently enabled), or you can override it on your
10089 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
10091 o Major bugfixes (0.2.1.x and earlier):
10092 - Fix a bug in bandwidth accounting that could make us use twice
10093 the intended bandwidth when our interval start changes due to
10094 daylight saving time. Now we tolerate skew in stored vs computed
10095 interval starts: if the start of the period changes by no more than
10096 50% of the period's duration, we remember bytes that we transferred
10097 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
10098 - Always search the Windows system directory for system DLLs, and
10099 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
10100 - When you're using bridges and your network goes away and your
10101 bridges get marked as down, recover when you attempt a new socks
10102 connection (if the network is back), rather than waiting up to an
10103 hour to try fetching new descriptors for your bridges. Bugfix on
10104 0.2.0.3-alpha; fixes bug 1981.
10106 o Major bugfixes (on 0.2.2.x):
10107 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
10109 - Fix a segfault that could happen when operating a bridge relay with
10110 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
10111 - The consensus bandwidth-weights (used by clients to choose fast
10112 relays) entered an unexpected edge case in September where
10113 Exits were much scarcer than Guards, resulting in bad weight
10114 recommendations. Now we compute them using new constraints that
10115 should succeed in all cases. Also alter directory authorities to
10116 not include the bandwidth-weights line if they fail to produce
10117 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
10118 - When weighting bridges during path selection, we used to trust
10119 the bandwidths they provided in their descriptor, only capping them
10120 at 10MB/s. This turned out to be problematic for two reasons:
10121 Bridges could claim to handle a lot more traffic then they
10122 actually would, thus making more clients pick them and have a
10123 pretty effective DoS attack. The other issue is that new bridges
10124 that might not have a good estimate for their bw capacity yet
10125 would not get used at all unless no other bridges are available
10126 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
10128 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
10129 - Ignore cannibalized circuits when recording circuit build times.
10130 This should provide for a minor performance improvement for hidden
10131 service users using 0.2.2.14-alpha, and should remove two spurious
10132 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
10133 - Simplify the logic that causes us to decide if the network is
10134 unavailable for purposes of recording circuit build times. If we
10135 receive no cells whatsoever for the entire duration of a circuit's
10136 full measured lifetime, the network is probably down. Also ignore
10137 one-hop directory fetching circuit timeouts when calculating our
10138 circuit build times. These changes should hopefully reduce the
10139 cases where we see ridiculous circuit build timeouts for people
10140 with spotty wireless connections. Fixes part of bug 1772; bugfix
10142 - Prevent the circuit build timeout from becoming larger than
10143 the maximum build time we have ever seen. Also, prevent the time
10144 period for measurement circuits from becoming larger than twice that
10145 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
10148 - When we run out of directory information such that we can't build
10149 circuits, but then get enough that we can build circuits, log when
10150 we actually construct a circuit, so the user has a better chance of
10151 knowing what's going on. Fixes bug 1362.
10152 - Be more generous with how much bandwidth we'd use up (with
10153 accounting enabled) before entering "soft hibernation". Previously,
10154 we'd refuse new connections and circuits once we'd used up 95% of
10155 our allotment. Now, we use up 95% of our allotment, AND make sure
10156 that we have no more than 500MB (or 3 hours of expected traffic,
10157 whichever is lower) remaining before we enter soft hibernation.
10158 - If we've configured EntryNodes and our network goes away and/or all
10159 our entrynodes get marked down, optimistically retry them all when
10160 a new socks application request appears. Fixes bug 1882.
10161 - Add some more defensive programming for architectures that can't
10162 handle unaligned integer accesses. We don't know of any actual bugs
10163 right now, but that's the best time to fix them. Fixes bug 1943.
10164 - Support line continuations in the torrc config file. If a line
10165 ends with a single backslash character, the newline is ignored, and
10166 the configuration value is treated as continuing on the next line.
10169 o Minor bugfixes (on 0.2.1.x and earlier):
10170 - For bandwidth accounting, calculate our expected bandwidth rate
10171 based on the time during which we were active and not in
10172 soft-hibernation during the last interval. Previously, we were
10173 also considering the time spent in soft-hibernation. If this
10174 was a long time, we would wind up underestimating our bandwidth
10175 by a lot, and skewing our wakeup time towards the start of the
10176 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
10178 o Minor bugfixes (on 0.2.2.x):
10179 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
10180 which were disabled by the circuit build timeout changes in
10181 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
10182 - Make sure we don't warn about missing bandwidth weights when
10183 choosing bridges or other relays not in the consensus. Bugfix on
10184 0.2.2.10-alpha; fixes bug 1805.
10185 - In our logs, do not double-report signatures from unrecognized
10186 authorities both as "from unknown authority" and "not
10187 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
10190 Changes in version 0.2.2.16-alpha - 2010-09-17
10191 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
10192 evident at exit relays), and also continues to resolve all the little
10193 bugs that have been filling up trac lately.
10195 o Major bugfixes (stream-level fairness):
10196 - When receiving a circuit-level SENDME for a blocked circuit, try
10197 to package cells fairly from all the streams that had previously
10198 been blocked on that circuit. Previously, we had started with the
10199 oldest stream, and allowed each stream to potentially exhaust
10200 the circuit's package window. This gave older streams on any
10201 given circuit priority over newer ones. Fixes bug 1937. Detected
10202 originally by Camilo Viecco. This bug was introduced before the
10203 first Tor release, in svn commit r152: it is the new winner of
10204 the longest-lived bug prize.
10205 - When the exit relay got a circuit-level sendme cell, it started
10206 reading on the exit streams, even if had 500 cells queued in the
10207 circuit queue already, so the circuit queue just grew and grew in
10208 some cases. We fix this by not re-enabling reading on receipt of a
10209 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
10210 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
10212 - Newly created streams were allowed to read cells onto circuits,
10213 even if the circuit's cell queue was blocked and waiting to drain.
10214 This created potential unfairness, as older streams would be
10215 blocked, but newer streams would gladly fill the queue completely.
10216 We add code to detect this situation and prevent any stream from
10217 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
10221 - Update to the September 1 2010 Maxmind GeoLite Country database.
10222 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
10223 not. This would lead to a cookie that is still not group readable.
10224 Closes bug 1843. Suggested by katmagic.
10225 - When logging a rate-limited warning, we now mention how many messages
10226 got suppressed since the last warning.
10227 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
10228 do individual connection-level rate limiting of clients. The torrc
10229 config options with the same names trump the consensus params, if
10230 both are present. Replaces the old "bwconnrate" and "bwconnburst"
10231 consensus params which were broken from 0.2.2.7-alpha through
10232 0.2.2.14-alpha. Closes bug 1947.
10233 - When a router changes IP address or port, authorities now launch
10234 a new reachability test for it. Implements ticket 1899.
10235 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
10236 2 no signature, 4 required" messages about consensus signatures
10237 easier to read, and make sure they get logged at the same severity
10238 as the messages explaining which keys are which. Fixes bug 1290.
10239 - Don't warn when we have a consensus that we can't verify because
10240 of missing certificates, unless those certificates are ones
10241 that we have been trying and failing to download. Fixes bug 1145.
10242 - If you configure your bridge with a known identity fingerprint,
10243 and the bridge authority is unreachable (as it is in at least
10244 one country now), fall back to directly requesting the descriptor
10245 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
10247 - When building with --enable-gcc-warnings on OpenBSD, disable
10248 warnings in system headers. This makes --enable-gcc-warnings
10249 pass on OpenBSD 4.8.
10251 o Minor bugfixes (on 0.2.1.x and earlier):
10252 - Authorities will now attempt to download consensuses if their
10253 own efforts to make a live consensus have failed. This change
10254 means authorities that restart will fetch a valid consensus, and
10255 it means authorities that didn't agree with the current consensus
10256 will still fetch and serve it if it has enough signatures. Bugfix
10257 on 0.2.0.9-alpha; fixes bug 1300.
10258 - Ensure DNS requests launched by "RESOLVE" commands from the
10259 controller respect the __LeaveStreamsUnattached setconf options. The
10260 same goes for requests launched via DNSPort or transparent
10261 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
10262 - Allow handshaking OR connections to take a full KeepalivePeriod
10263 seconds to handshake. Previously, we would close them after
10264 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
10265 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
10267 - Rate-limit "Failed to hand off onionskin" warnings.
10268 - Never relay a cell for a circuit we have already destroyed.
10269 Between marking a circuit as closeable and finally closing it,
10270 it may have been possible for a few queued cells to get relayed,
10271 even though they would have been immediately dropped by the next
10272 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
10273 - Never queue a cell for a circuit that's already been marked
10275 - Never vote for a server as "Running" if we have a descriptor for
10276 it claiming to be hibernating, and that descriptor was published
10277 more recently than our last contact with the server. Bugfix on
10278 0.2.0.3-alpha; fixes bug 911.
10279 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
10282 o Minor bugfixes (on 0.2.2.x):
10283 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
10284 down if a directory fetch fails and you've configured either
10285 bridges or EntryNodes. The intent was to mark the relay as down
10286 _unless_ you're using bridges or EntryNodes, since if you are
10287 then you could quickly run out of entry points.
10288 - Fix the Windows directory-listing code. A bug introduced in
10289 0.2.2.14-alpha could make Windows directory servers forget to load
10290 some of their cached v2 networkstatus files.
10291 - Really allow clients to use relays as bridges. Fixes bug 1776;
10292 bugfix on 0.2.2.15-alpha.
10293 - Demote a warn to info that happens when the CellStatistics option
10294 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
10295 Reported by Moritz Bartl.
10296 - On Windows, build correctly either with or without Unicode support.
10297 This is necessary so that Tor can support fringe platforms like
10298 Windows 98 (which has no Unicode), or Windows CE (which has no
10299 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
10302 - Add a unit test for cross-platform directory-listing code.
10305 Changes in version 0.2.2.15-alpha - 2010-08-18
10306 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
10307 fixes a variety of other bugs that were preventing performance
10308 experiments from moving forward, fixes several bothersome memory leaks,
10309 and generally closes a lot of smaller bugs that have been filling up
10313 - Stop assigning the HSDir flag to relays that disable their
10314 DirPort (and thus will refuse to answer directory requests). This
10315 fix should dramatically improve the reachability of hidden services:
10316 hidden services and hidden service clients pick six HSDir relays
10317 to store and retrieve the hidden service descriptor, and currently
10318 about half of the HSDir relays will refuse to work. Bugfix on
10319 0.2.0.10-alpha; fixes part of bug 1693.
10320 - The PerConnBWRate and Burst config options, along with the
10321 bwconnrate and bwconnburst consensus params, initialized each conn's
10322 token bucket values only when the connection is established. Now we
10323 update them if the config options change, and update them every time
10324 we get a new consensus. Otherwise we can encounter an ugly edge
10325 case where we initialize an OR conn to client-level bandwidth,
10326 but then later the relay joins the consensus and we leave it
10327 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
10328 - Fix a regression that caused Tor to rebind its ports if it receives
10329 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
10332 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
10333 should give us approximately 40-50% more Guard-flagged nodes,
10334 improving the anonymity the Tor network can provide and also
10335 decreasing the dropoff in throughput that relays experience when
10336 they first get the Guard flag.
10337 - Allow enabling or disabling the *Statistics config options while
10341 - Update to the August 1 2010 Maxmind GeoLite Country database.
10342 - Have the controller interface give a more useful message than
10343 "Internal Error" in response to failed GETINFO requests.
10344 - Warn when the same option is provided more than once in a torrc
10345 file, on the command line, or in a single SETCONF statement, and
10346 the option is one that only accepts a single line. Closes bug 1384.
10347 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
10348 Patch from mingw-san.
10349 - Add support for the country code "{??}" in torrc options like
10350 ExcludeNodes, to indicate all routers of unknown country. Closes
10352 - Relays report the number of bytes spent on answering directory
10353 requests in extra-info descriptors similar to {read,write}-history.
10354 Implements enhancement 1790.
10356 o Minor bugfixes (on 0.2.1.x and earlier):
10357 - Complain if PublishServerDescriptor is given multiple arguments that
10358 include 0 or 1. This configuration will be rejected in the future.
10359 Bugfix on 0.2.0.1-alpha; closes bug 1107.
10360 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
10361 Bugfix on 0.2.0.13-alpha; closes bug 928.
10362 - Change "Application request when we're believed to be offline."
10363 notice to "Application request when we haven't used client
10364 functionality lately.", to clarify that it's not an error. Bugfix
10365 on 0.0.9.3; fixes bug 1222.
10366 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
10367 would return "551 Internal error" rather than "552 Unrecognized key
10368 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
10369 - Users can't configure a regular relay to be their bridge. It didn't
10370 work because when Tor fetched the bridge descriptor, it found
10371 that it already had it, and didn't realize that the purpose of the
10372 descriptor had changed. Now we replace routers with a purpose other
10373 than bridge with bridge descriptors when fetching them. Bugfix on
10374 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
10375 refetch the descriptor with router purpose 'general', disabling
10377 - Fix a rare bug in rend_fn unit tests: we would fail a test when
10378 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
10379 on 0.2.0.10-alpha; fixes bug 1808.
10380 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
10381 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
10382 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
10383 Servers can start sending this code when enough clients recognize
10384 it. Also update the spec to reflect this new reason. Bugfix on
10385 0.1.0.1-rc; fixes part of bug 1793.
10386 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
10387 when we switch from being a public relay to a bridge. Otherwise
10388 there will still be clients that see the relay in their consensus,
10389 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
10391 - Instead of giving an assertion failure on an internal mismatch
10392 on estimated freelist size, just log a BUG warning and try later.
10393 Mitigates but does not fix bug 1125.
10394 - Fix an assertion failure that could occur in caches or bridge users
10395 when using a very short voting interval on a testing network.
10396 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
10398 o Minor bugfixes (on 0.2.2.x):
10399 - Alter directory authorities to always consider Exit-flagged nodes
10400 as potential Guard nodes in their votes. The actual decision to
10401 use Exits as Guards is done in the consensus bandwidth weights.
10402 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
10403 - When the controller is reporting the purpose of circuits that
10404 didn't finish building before the circuit build timeout, it was
10405 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
10406 - Our libevent version parsing code couldn't handle versions like
10407 1.4.14b-stable and incorrectly warned the user about using an
10408 old and broken version of libevent. Treat 1.4.14b-stable like
10409 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
10411 - Don't use substitution references like $(VAR:MOD) when
10412 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
10413 '$(:x)' to 'x' rather than the empty string. This bites us in
10414 doc/ when configured with --disable-asciidoc. Bugfix on
10415 0.2.2.9-alpha; fixes bug 1773.
10416 - Remove a spurious hidden service server-side log notice about
10417 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
10419 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
10421 - Correctly report written bytes on linked connections. Found while
10422 implementing 1790. Bugfix on 0.2.2.4-alpha.
10423 - Fix three memory leaks: one in circuit_build_times_parse_state(),
10424 one in dirvote_add_signatures_to_pending_consensus(), and one every
10425 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
10426 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
10428 o Code simplifications and refactoring:
10429 - Take a first step towards making or.h smaller by splitting out
10430 function definitions for all source files in src/or/. Leave
10431 structures and defines in or.h for now.
10432 - Remove a bunch of unused function declarations as well as a block of
10433 #if 0'd code from the unit tests. Closes bug 1824.
10434 - New unit tests for exit-port history statistics; refactored exit
10435 statistics code to be more easily tested.
10436 - Remove the old debian/ directory from the main Tor distribution.
10437 The official Tor-for-debian git repository lives at the URL
10438 https://git.torproject.org/debian/tor.git
10441 Changes in version 0.2.2.14-alpha - 2010-07-12
10442 Tor 0.2.2.14-alpha greatly improves client-side handling of
10443 circuit build timeouts, which are used to estimate speed and improve
10444 performance. We also move to a much better GeoIP database, port Tor to
10445 Windows CE, introduce new compile flags that improve code security,
10446 add an eighth v3 directory authority, and address a lot of more
10450 - Tor directory authorities no longer crash when started with a
10451 cached-microdesc-consensus file in their data directory. Bugfix
10452 on 0.2.2.6-alpha; fixes bug 1532.
10453 - Treat an unset $HOME like an empty $HOME rather than triggering an
10454 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
10455 - Ignore negative and large circuit build timeout values that can
10456 happen during a suspend or hibernate. These values caused various
10457 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
10458 - Alter calculation of Pareto distribution parameter 'Xm' for
10459 Circuit Build Timeout learning to use the weighted average of the
10460 top N=3 modes (because we have three entry guards). Considering
10461 multiple modes should improve the timeout calculation in some cases,
10462 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
10464 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
10465 right censored distribution model. This approach improves over the
10466 synthetic timeout generation approach that was producing insanely
10467 high timeout values. Now we calculate build timeouts using truncated
10468 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
10469 - Do not close circuits that are under construction when they reach
10470 the circuit build timeout. Instead, leave them building (but do not
10471 use them) for up until the time corresponding to the 95th percentile
10472 on the Pareto CDF or 60 seconds, whichever is greater. This is done
10473 to provide better data for the new Pareto model. This percentile
10474 can be controlled by the consensus.
10477 - Move to the June 2010 Maxmind GeoLite country db (rather than the
10478 June 2009 ip-to-country GeoIP db) for our statistics that count
10479 how many users relays are seeing from each country. Now we have
10480 more accurate data for many African countries.
10481 - Port Tor to build and run correctly on Windows CE systems, using
10482 the wcecompat library. Contributed by Valerio Lupi.
10483 - New "--enable-gcc-hardening" ./configure flag (off by default)
10484 to turn on gcc compile time hardening options. It ensures
10485 that signed ints have defined behavior (-fwrapv), enables
10486 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
10487 with canaries (-fstack-protector-all), turns on ASLR protection if
10488 supported by the kernel (-fPIE, -pie), and adds additional security
10489 related warnings. Verified to work on Mac OS X and Debian Lenny.
10490 - New "--enable-linker-hardening" ./configure flag (off by default)
10491 to turn on ELF specific hardening features (relro, now). This does
10492 not work with Mac OS X or any other non-ELF binary format.
10494 o New directory authorities:
10495 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
10499 - New config option "WarnUnsafeSocks 0" disables the warning that
10500 occurs whenever Tor receives a socks handshake using a version of
10501 the socks protocol that can only provide an IP address (rather
10502 than a hostname). Setups that do DNS locally over Tor are fine,
10503 and we shouldn't spam the logs in that case.
10504 - Convert the HACKING file to asciidoc, and add a few new sections
10505 to it, explaining how we use Git, how we make changelogs, and
10506 what should go in a patch.
10507 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
10508 event, to give information on the current rate of circuit timeouts
10509 over our stored history.
10510 - Add ability to disable circuit build time learning via consensus
10511 parameter and via a LearnCircuitBuildTimeout config option. Also
10512 automatically disable circuit build time calculation if we are
10513 either a AuthoritativeDirectory, or if we fail to write our state
10514 file. Fixes bug 1296.
10515 - More gracefully handle corrupt state files, removing asserts
10516 in favor of saving a backup and resetting state.
10517 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
10521 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
10523 - When a2x fails, mention that the user could disable manpages instead
10524 of trying to fix their asciidoc installation.
10525 - Where available, use Libevent 2.0's periodic timers so that our
10526 once-per-second cleanup code gets called even more closely to
10527 once per second than it would otherwise. Fixes bug 943.
10528 - If you run a bridge that listens on multiple IP addresses, and
10529 some user configures a bridge address that uses a different IP
10530 address than your bridge writes in its router descriptor, and the
10531 user doesn't specify an identity key, their Tor would discard the
10532 descriptor because "it isn't one of our configured bridges", and
10533 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
10534 Bugfix on 0.2.0.3-alpha.
10535 - If OpenSSL fails to make a duplicate of a private or public key, log
10536 an error message and try to exit cleanly. May help with debugging
10537 if bug 1209 ever remanifests.
10538 - Save a couple bytes in memory allocation every time we escape
10539 certain characters in a string. Patch from Florian Zumbiehl.
10540 - Make it explicit that we don't cannibalize one-hop circuits. This
10541 happens in the wild, but doesn't turn out to be a problem because
10542 we fortunately don't use those circuits. Many thanks to outofwords
10543 for the initial analysis and to swissknife who confirmed that
10544 two-hop circuits are actually created.
10545 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
10546 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
10547 - Eliminate a case where a circuit build time warning was displayed
10548 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
10551 Changes in version 0.2.1.26 - 2010-05-02
10552 Tor 0.2.1.26 addresses the recent connection and memory overload
10553 problems we've been seeing on relays, especially relays with their
10554 DirPort open. If your relay has been crashing, or you turned it off
10555 because it used too many resources, give this release a try.
10557 This release also fixes yet another instance of broken OpenSSL libraries
10558 that was causing some relays to drop out of the consensus.
10561 - Teach relays to defend themselves from connection overload. Relays
10562 now close idle circuits early if it looks like they were intended
10563 for directory fetches. Relays are also more aggressive about closing
10564 TLS connections that have no circuits on them. Such circuits are
10565 unlikely to be re-used, and tens of thousands of them were piling
10566 up at the fast relays, causing the relays to run out of sockets
10567 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
10568 their directory fetches over TLS).
10569 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
10570 that claim to be earlier than 0.9.8m, but which have in reality
10571 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
10572 behavior. Possible fix for some cases of bug 1346.
10573 - Directory mirrors were fetching relay descriptors only from v2
10574 directory authorities, rather than v3 authorities like they should.
10575 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
10576 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
10579 - Finally get rid of the deprecated and now harmful notion of "clique
10580 mode", where directory authorities maintain TLS connections to
10584 - In the util/threads test, no longer free the test_mutex before all
10585 worker threads have finished. Bugfix on 0.2.1.6-alpha.
10586 - The master thread could starve the worker threads quite badly on
10587 certain systems, causing them to run only partially in the allowed
10588 window. This resulted in test failures. Now the master thread sleeps
10589 occasionally for a few microseconds while the two worker-threads
10590 compete for the mutex. Bugfix on 0.2.0.1-alpha.
10593 Changes in version 0.2.2.13-alpha - 2010-04-24
10594 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
10595 problems we've been seeing on relays, especially relays with their
10596 DirPort open. If your relay has been crashing, or you turned it off
10597 because it used too many resources, give this release a try.
10600 - Teach relays to defend themselves from connection overload. Relays
10601 now close idle circuits early if it looks like they were intended
10602 for directory fetches. Relays are also more aggressive about closing
10603 TLS connections that have no circuits on them. Such circuits are
10604 unlikely to be re-used, and tens of thousands of them were piling
10605 up at the fast relays, causing the relays to run out of sockets
10606 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
10607 their directory fetches over TLS).
10610 - Finally get rid of the deprecated and now harmful notion of "clique
10611 mode", where directory authorities maintain TLS connections to
10613 - Directory authorities now do an immediate reachability check as soon
10614 as they hear about a new relay. This change should slightly reduce
10615 the time between setting up a relay and getting listed as running
10616 in the consensus. It should also improve the time between setting
10617 up a bridge and seeing use by bridge users.
10618 - Directory authorities no longer launch a TLS connection to every
10619 relay as they startup. Now that we have 2k+ descriptors cached,
10620 the resulting network hiccup is becoming a burden. Besides,
10621 authorities already avoid voting about Running for the first half
10622 hour of their uptime.
10625 Changes in version 0.2.2.12-alpha - 2010-04-20
10626 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
10627 handle and vote on descriptors. It was causing relays to drop out of
10631 - Many relays have been falling out of the consensus lately because
10632 not enough authorities know about their descriptor for them to get
10633 a majority of votes. When we deprecated the v2 directory protocol,
10634 we got rid of the only way that v3 authorities can hear from each
10635 other about other descriptors. Now authorities examine every v3
10636 vote for new descriptors, and fetch them from that authority. Bugfix
10638 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
10639 and a warning in or.h related to bandwidth_weight_rule_t that
10640 prevented clean compile on OS X. Fixes bug 1363; bugfix on
10642 - Fix a segfault on relays when DirReqStatistics is enabled
10643 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
10647 - Demote a confusing TLS warning that relay operators might get when
10648 someone tries to talk to their OrPort. It is neither the operator's
10649 fault nor can they do anything about it. Fixes bug 1364; bugfix
10653 Changes in version 0.2.2.11-alpha - 2010-04-15
10654 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
10655 libraries that was causing some relays to drop out of the consensus.
10658 - Directory mirrors were fetching relay descriptors only from v2
10659 directory authorities, rather than v3 authorities like they should.
10660 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
10661 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
10662 - Fix a parsing error that made every possible value of
10663 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
10664 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
10665 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
10666 about the option without breaking older ones.
10667 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
10668 that claim to be earlier than 0.9.8m, but which have in reality
10669 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
10670 behavior. Possible fix for some cases of bug 1346.
10673 - Experiment with a more aggressive approach to preventing clients
10674 from making one-hop exit streams. Exit relays who want to try it
10675 out can set "RefuseUnknownExits 1" in their torrc, and then look
10676 for "Attempt by %s to open a stream" log messages. Let us know
10678 - Add support for statically linking zlib by specifying
10679 --enable-static-zlib, to go with our support for statically linking
10680 openssl and libevent. Resolves bug 1358.
10683 - Fix a segfault that happens whenever a Tor client that is using
10684 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
10686 - When we cleaned up the contrib/tor-exit-notice.html file, we left
10687 out the first line. Fixes bug 1295.
10688 - When building the manpage from a tarball, we required asciidoc, but
10689 the asciidoc -> roff/html conversion was already done for the
10690 tarball. Make 'make' complain only when we need asciidoc (either
10691 because we're compiling directly from git, or because we altered
10692 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
10693 - When none of the directory authorities vote on any params, Tor
10694 segfaulted when trying to make the consensus from the votes. We
10695 didn't trigger the bug in practice, because authorities do include
10696 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
10699 - In the util/threads test, no longer free the test_mutex before all
10700 worker threads have finished. Bugfix on 0.2.1.6-alpha.
10701 - The master thread could starve the worker threads quite badly on
10702 certain systems, causing them to run only partially in the allowed
10703 window. This resulted in test failures. Now the master thread sleeps
10704 occasionally for a few microseconds while the two worker-threads
10705 compete for the mutex. Bugfix on 0.2.0.1-alpha.
10708 Changes in version 0.2.2.10-alpha - 2010-03-07
10709 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
10710 could prevent relays from guessing their IP address correctly. It also
10711 starts the groundwork for another client-side performance boost, since
10712 currently we're not making efficient use of relays that have both the
10713 Guard flag and the Exit flag.
10716 - Fix a regression from our patch for bug 1244 that caused relays
10717 to guess their IP address incorrectly if they didn't set Address
10718 in their torrc and/or their address fails to resolve. Bugfix on
10719 0.2.2.9-alpha; fixes bug 1269.
10721 o Major features (performance):
10722 - Directory authorities now compute consensus weightings that instruct
10723 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
10724 and no flag. Clients that use these weightings will distribute
10725 network load more evenly across these different relay types. The
10726 weightings are in the consensus so we can change them globally in
10727 the future. Extra thanks to "outofwords" for finding some nasty
10728 security bugs in the first implementation of this feature.
10730 o Minor features (performance):
10731 - Always perform router selections using weighted relay bandwidth,
10732 even if we don't need a high capacity circuit at the time. Non-fast
10733 circuits now only differ from fast ones in that they can use relays
10734 not marked with the Fast flag. This "feature" could turn out to
10735 be a horrible bug; we should investigate more before it goes into
10739 - Allow disabling building of the manpages. Skipping the manpage
10740 speeds up the build considerably.
10742 o Minor bugfixes (on 0.2.2.x):
10743 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
10744 Bugfix on 0.2.2.9-alpha.
10745 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
10746 config option. Bugfix on 0.2.2.7-alpha.
10747 - Ship the asciidoc-helper file in the tarball, so that people can
10748 build from source if they want to, and touching the .1.txt files
10749 doesn't break the build. Bugfix on 0.2.2.9-alpha.
10751 o Minor bugfixes (on 0.2.1.x or earlier):
10752 - Fix a dereference-then-NULL-check sequence when publishing
10753 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
10755 - Fix another dereference-then-NULL-check sequence. Bugfix on
10756 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
10757 - Make sure we treat potentially not NUL-terminated strings correctly.
10758 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
10760 o Code simplifications and refactoring:
10761 - Fix some urls in the exit notice file and make it XHTML1.1 strict
10762 compliant. Based on a patch from Christian Kujau.
10763 - Don't use sed in asciidoc-helper anymore.
10764 - Make the build process fail if asciidoc cannot be found and
10765 building with asciidoc isn't disabled.
10768 Changes in version 0.2.2.9-alpha - 2010-02-22
10769 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
10770 location of a directory authority, and cleans up a bunch of small bugs.
10772 o Directory authority changes:
10773 - Change IP address for dannenberg (v3 directory authority), and
10774 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
10775 service directory authority) from the list.
10778 - Make Tor work again on the latest OS X: when deciding whether to
10779 use strange flags to turn TLS renegotiation on, detect the OpenSSL
10780 version at run-time, not compile time. We need to do this because
10781 Apple doesn't update its dev-tools headers when it updates its
10782 libraries in a security patch.
10783 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
10784 that could happen on 32-bit platforms with 64-bit time_t. Also fix
10785 a memory leak when requesting a hidden service descriptor we've
10786 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
10788 - Authorities could be tricked into giving out the Exit flag to relays
10789 that didn't allow exiting to any ports. This bug could screw
10790 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
10791 1238. Bug discovered by Martin Kowalczyk.
10792 - When freeing a session key, zero it out completely. We only zeroed
10793 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
10794 patched by ekir. Fixes bug 1254.
10797 - Fix static compilation by listing the openssl libraries in the right
10798 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
10799 - Resume handling .exit hostnames in a special way: originally we
10800 stripped the .exit part and used the requested exit relay. In
10801 0.2.2.1-alpha we stopped treating them in any special way, meaning
10802 if you use a .exit address then Tor will pass it on to the exit
10803 relay. Now we reject the .exit stream outright, since that behavior
10804 might be more expected by the user. Found and diagnosed by Scott
10805 Bennett and Downie on or-talk.
10806 - Don't spam the controller with events when we have no file
10807 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
10808 for log messages was already solved from bug 748.)
10809 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
10811 - Make the DNSPort option work with libevent 2.x. Don't alter the
10812 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
10813 - Emit a GUARD DROPPED controller event for a case we missed.
10814 - Make more fields in the controller protocol case-insensitive, since
10815 control-spec.txt said they were.
10816 - Refactor resolve_my_address() to not use gethostbyname() anymore.
10817 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
10818 - Fix a spec conformance issue: the network-status-version token
10819 must be the first token in a v3 consensus or vote. Discovered by
10820 parakeep. Bugfix on 0.2.0.3-alpha.
10822 o Code simplifications and refactoring:
10823 - Generate our manpage and HTML documentation using Asciidoc. This
10824 change should make it easier to maintain the documentation, and
10825 produce nicer HTML.
10826 - Remove the --enable-iphone option. According to reports from Marco
10827 Bonetti, Tor builds fine without any special tweaking on recent
10828 iPhone SDK versions.
10829 - Removed some unnecessary files from the source distribution. The
10830 AUTHORS file has now been merged into the people page on the
10831 website. The roadmaps and design doc can now be found in the
10832 projects directory in svn.
10833 - Enabled various circuit build timeout constants to be controlled
10834 by consensus parameters. Also set better defaults for these
10835 parameters based on experimentation on broadband and simulated
10836 high latency links.
10839 - The 'EXTENDCIRCUIT' control port command can now be used with
10840 a circ id of 0 and no path. This feature will cause Tor to build
10841 a new 'fast' general purpose circuit using its own path selection
10843 - Added a BUILDTIMEOUT_SET controller event to describe changes
10844 to the circuit build timeout.
10845 - Future-proof the controller protocol a bit by ignoring keyword
10846 arguments we do not recognize.
10847 - Expand homedirs passed to tor-checkkey. This should silence a
10848 coverity complaint about passing a user-supplied string into
10849 open() without checking it.
10852 Changes in version 0.2.1.25 - 2010-03-16
10853 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
10854 prevent relays from guessing their IP address correctly. It also fixes
10855 several minor potential security bugs.
10858 - Fix a regression from our patch for bug 1244 that caused relays
10859 to guess their IP address incorrectly if they didn't set Address
10860 in their torrc and/or their address fails to resolve. Bugfix on
10861 0.2.1.23; fixes bug 1269.
10862 - When freeing a session key, zero it out completely. We only zeroed
10863 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
10864 patched by ekir. Fixes bug 1254.
10867 - Fix a dereference-then-NULL-check sequence when publishing
10868 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
10870 - Fix another dereference-then-NULL-check sequence. Bugfix on
10871 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
10872 - Make sure we treat potentially not NUL-terminated strings correctly.
10873 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
10877 Changes in version 0.2.1.24 - 2010-02-21
10878 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
10882 - Work correctly out-of-the-box with even more vendor-patched versions
10883 of OpenSSL. In particular, make it so Debian and OS X don't need
10884 customized patches to run/build.
10887 Changes in version 0.2.1.23 - 2010-02-13
10888 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
10889 again on the latest OS X, and updates the location of a directory
10892 o Major bugfixes (performance):
10893 - We were selecting our guards uniformly at random, and then weighting
10894 which of our guards we'd use uniformly at random. This imbalance
10895 meant that Tor clients were severely limited on throughput (and
10896 probably latency too) by the first hop in their circuit. Now we
10897 select guards weighted by currently advertised bandwidth. We also
10898 automatically discard guards picked using the old algorithm. Fixes
10899 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
10902 - Make Tor work again on the latest OS X: when deciding whether to
10903 use strange flags to turn TLS renegotiation on, detect the OpenSSL
10904 version at run-time, not compile time. We need to do this because
10905 Apple doesn't update its dev-tools headers when it updates its
10906 libraries in a security patch.
10907 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
10908 that could happen on 32-bit platforms with 64-bit time_t. Also fix
10909 a memory leak when requesting a hidden service descriptor we've
10910 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
10913 o Directory authority changes:
10914 - Change IP address for dannenberg (v3 directory authority), and
10915 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
10916 service directory authority) from the list.
10919 - Refactor resolve_my_address() to not use gethostbyname() anymore.
10920 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
10923 - Avoid a mad rush at the beginning of each month when each client
10924 rotates half of its guards. Instead we spread the rotation out
10925 throughout the month, but we still avoid leaving a precise timestamp
10926 in the state file about when we first picked the guard. Improves
10927 over the behavior introduced in 0.1.2.17.
10930 Changes in version 0.2.2.8-alpha - 2010-01-26
10931 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
10932 causing bridge relays to disappear. If you're running a bridge,
10936 - Fix a memory corruption bug on bridges that occured during the
10937 inclusion of stats data in extra-info descriptors. Also fix the
10938 interface for geoip_get_bridge_stats* to prevent similar bugs in
10939 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
10940 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
10943 - Ignore OutboundBindAddress when connecting to localhost.
10944 Connections to localhost need to come _from_ localhost, or else
10945 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
10949 Changes in version 0.2.2.7-alpha - 2010-01-19
10950 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
10951 as laying the groundwork for further relay-side performance fixes. It
10952 also starts cleaning up client behavior with respect to the EntryNodes,
10953 ExitNodes, and StrictNodes config options.
10955 This release also rotates two directory authority keys, due to a
10956 security breach of some of the Torproject servers.
10958 o Directory authority changes:
10959 - Rotate keys (both v3 identity and relay identity) for moria1
10962 o Major features (performance):
10963 - We were selecting our guards uniformly at random, and then weighting
10964 which of our guards we'd use uniformly at random. This imbalance
10965 meant that Tor clients were severely limited on throughput (and
10966 probably latency too) by the first hop in their circuit. Now we
10967 select guards weighted by currently advertised bandwidth. We also
10968 automatically discard guards picked using the old algorithm. Fixes
10969 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
10970 - When choosing which cells to relay first, relays can now favor
10971 circuits that have been quiet recently, to provide lower latency
10972 for low-volume circuits. By default, relays enable or disable this
10973 feature based on a setting in the consensus. You can override
10974 this default by using the new "CircuitPriorityHalflife" config
10975 option. Design and code by Ian Goldberg, Can Tang, and Chris
10977 - Add separate per-conn write limiting to go with the per-conn read
10978 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
10979 but never per-conn write limits.
10980 - New consensus params "bwconnrate" and "bwconnburst" to let us
10981 rate-limit client connections as they enter the network. It's
10982 controlled in the consensus so we can turn it on and off for
10983 experiments. It's starting out off. Based on proposal 163.
10985 o Major features (relay selection options):
10986 - Switch to a StrictNodes config option, rather than the previous
10987 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
10988 "StrictExcludeNodes" option.
10989 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
10990 change during a config reload, mark and discard all our origin
10991 circuits. This fix should address edge cases where we change the
10992 config options and but then choose a circuit that we created before
10994 - If EntryNodes or ExitNodes are set, be more willing to use an
10995 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
10997 - Make EntryNodes config option much more aggressive even when
10998 StrictNodes is not set. Before it would prepend your requested
10999 entrynodes to your list of guard nodes, but feel free to use others
11000 after that. Now it chooses only from your EntryNodes if any of
11001 those are available, and only falls back to others if a) they're
11002 all down and b) StrictNodes is not set.
11003 - Now we refresh your entry guards from EntryNodes at each consensus
11004 fetch -- rather than just at startup and then they slowly rot as
11005 the network changes.
11008 - Stop bridge directory authorities from answering dbg-stability.txt
11009 directory queries, which would let people fetch a list of all
11010 bridge identities they track. Bugfix on 0.2.1.6-alpha.
11013 - Log a notice when we get a new control connection. Now it's easier
11014 for security-conscious users to recognize when a local application
11015 is knocking on their controller door. Suggested by bug 1196.
11016 - New config option "CircuitStreamTimeout" to override our internal
11017 timeout schedule for how many seconds until we detach a stream from
11018 a circuit and try a new circuit. If your network is particularly
11019 slow, you might want to set this to a number like 60.
11020 - New controller command "getinfo config-text". It returns the
11021 contents that Tor would write if you send it a SAVECONF command,
11022 so the controller can write the file to disk itself.
11023 - New options for SafeLogging to allow scrubbing only log messages
11024 generated while acting as a relay.
11025 - Ship the bridges spec file in the tarball too.
11026 - Avoid a mad rush at the beginning of each month when each client
11027 rotates half of its guards. Instead we spread the rotation out
11028 throughout the month, but we still avoid leaving a precise timestamp
11029 in the state file about when we first picked the guard. Improves
11030 over the behavior introduced in 0.1.2.17.
11032 o Minor bugfixes (compiling):
11033 - Fix compilation on OS X 10.3, which has a stub mlockall() but
11034 hides it. Bugfix on 0.2.2.6-alpha.
11035 - Fix compilation on Solaris by removing support for the
11036 DisableAllSwap config option. Solaris doesn't have an rlimit for
11037 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
11040 o Minor bugfixes (crashes):
11041 - Do not segfault when writing buffer stats when we haven't observed
11042 a single circuit to report about. Found by Fabian Lanze. Bugfix on
11044 - If we're in the pathological case where there's no exit bandwidth
11045 but there is non-exit bandwidth, or no guard bandwidth but there
11046 is non-guard bandwidth, don't crash during path selection. Bugfix
11048 - Fix an impossible-to-actually-trigger buffer overflow in relay
11049 descriptor generation. Bugfix on 0.1.0.15.
11051 o Minor bugfixes (privacy):
11052 - Fix an instance where a Tor directory mirror might accidentally
11053 log the IP address of a misbehaving Tor client. Bugfix on
11055 - Don't list Windows capabilities in relay descriptors. We never made
11056 use of them, and maybe it's a bad idea to publish them. Bugfix
11059 o Minor bugfixes (other):
11060 - Resolve an edge case in path weighting that could make us misweight
11061 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
11062 - Fix statistics on client numbers by country as seen by bridges that
11063 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
11064 intervals instead of variable 12-to-48-hour intervals.
11065 - After we free an internal connection structure, overwrite it
11066 with a different memory value than we use for overwriting a freed
11067 internal circuit structure. Should help with debugging. Suggested
11069 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
11072 o Removed features:
11073 - Remove the HSAuthorityRecordStats option that version 0 hidden
11074 service authorities could have used to track statistics of overall
11075 hidden service usage.
11078 Changes in version 0.2.1.22 - 2010-01-19
11079 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
11080 authorities -- it would tell you its whole history of bridge descriptors
11081 if you make the right directory request. This stable update also
11082 rotates two of the seven v3 directory authority keys and locations.
11084 o Directory authority changes:
11085 - Rotate keys (both v3 identity and relay identity) for moria1
11089 - Stop bridge directory authorities from answering dbg-stability.txt
11090 directory queries, which would let people fetch a list of all
11091 bridge identities they track. Bugfix on 0.2.1.6-alpha.
11094 Changes in version 0.2.1.21 - 2009-12-21
11095 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
11096 library. If you use Tor on Linux / Unix and you're getting SSL
11097 renegotiation errors, upgrading should help. We also recommend an
11098 upgrade if you're an exit relay.
11101 - Work around a security feature in OpenSSL 0.9.8l that prevents our
11102 handshake from working unless we explicitly tell OpenSSL that we
11103 are using SSL renegotiation safely. We are, of course, but OpenSSL
11104 0.9.8l won't work unless we say we are.
11105 - Avoid crashing if the client is trying to upload many bytes and the
11106 circuit gets torn down at the same time, or if the flip side
11107 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
11110 - Do not refuse to learn about authority certs and v2 networkstatus
11111 documents that are older than the latest consensus. This bug might
11112 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
11113 Spotted and fixed by xmux.
11114 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
11115 trigger platform-specific option misparsing case found by Coverity
11117 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
11118 trigger assert. Fixes bug 1173.
11121 Changes in version 0.2.2.6-alpha - 2009-11-19
11122 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
11123 support for the new lower-footprint "microdescriptor" directory design,
11124 future-proofing our consensus format against new hash functions or
11125 other changes, and an Android port. It also makes Tor compatible with
11126 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
11129 - Directory authorities can now create, vote on, and serve multiple
11130 parallel formats of directory data as part of their voting process.
11131 Partially implements Proposal 162: "Publish the consensus in
11133 - Directory authorities can now agree on and publish small summaries
11134 of router information that clients can use in place of regular
11135 server descriptors. This transition will eventually allow clients
11136 to use far less bandwidth for downloading information about the
11137 network. Begins the implementation of Proposal 158: "Clients
11138 download consensus + microdescriptors".
11139 - The directory voting system is now extensible to use multiple hash
11140 algorithms for signatures and resource selection. Newer formats
11141 are signed with SHA256, with a possibility for moving to a better
11142 hash algorithm in the future.
11143 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
11144 current and future memory pages via mlockall(). On supported
11145 platforms (modern Linux and probably BSD but not Windows or OS X),
11146 this should effectively disable any and all attempts to page out
11147 memory. This option requires that you start your Tor as root --
11148 if you use DisableAllSwap, please consider using the User option
11149 to properly reduce the privileges of your Tor.
11150 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
11151 to help Tor build correctly for Android phones.
11154 - Work around a security feature in OpenSSL 0.9.8l that prevents our
11155 handshake from working unless we explicitly tell OpenSSL that we
11156 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
11157 won't work unless we say we are.
11160 - Fix a crash bug when trying to initialize the evdns module in
11161 Libevent 2. Bugfix on 0.2.1.16-rc.
11162 - Stop logging at severity 'warn' when some other Tor client tries
11163 to establish a circuit with us using weak DH keys. It's a protocol
11164 violation, but that doesn't mean ordinary users need to hear about
11165 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
11166 - Do not refuse to learn about authority certs and v2 networkstatus
11167 documents that are older than the latest consensus. This bug might
11168 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
11169 Spotted and fixed by xmux.
11170 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
11171 - If all authorities restart at once right before a consensus vote,
11172 nobody will vote about "Running", and clients will get a consensus
11173 with no usable relays. Instead, authorities refuse to build a
11174 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
11175 - If your relay can't keep up with the number of incoming create
11176 cells, it would log one warning per failure into your logs. Limit
11177 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
11178 - Bridges now use "reject *:*" as their default exit policy. Bugfix
11179 on 0.2.0.3-alpha; fixes bug 1113.
11180 - Fix a memory leak on directory authorities during voting that was
11181 introduced in 0.2.2.1-alpha. Found via valgrind.
11184 Changes in version 0.2.1.20 - 2009-10-15
11185 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
11186 services at once, prepares for more performance improvements, and
11187 fixes a bunch of smaller bugs.
11189 The Windows and OS X bundles also include a more recent Vidalia,
11190 and switch from Privoxy to Polipo.
11192 The OS X installers are now drag and drop. It's best to un-install
11193 Tor/Vidalia and then install this new bundle, rather than upgrade. If
11194 you want to upgrade, you'll need to update the paths for Tor and Polipo
11195 in the Vidalia Settings window.
11198 - Send circuit or stream sendme cells when our window has decreased
11199 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
11200 by Karsten when testing the "reduce circuit window" performance
11201 patch. Bugfix on the 54th commit on Tor -- from July 2002,
11202 before the release of Tor 0.0.0. This is the new winner of the
11204 - Fix a remotely triggerable memory leak when a consensus document
11205 contains more than one signature from the same voter. Bugfix on
11207 - Avoid segfault in rare cases when finishing an introduction circuit
11208 as a client and finding out that we don't have an introduction key
11209 for it. Fixes bug 1073. Reported by Aaron Swartz.
11212 - Tor now reads the "circwindow" parameter out of the consensus,
11213 and uses that value for its circuit package window rather than the
11214 default of 1000 cells. Begins the implementation of proposal 168.
11216 o New directory authorities:
11217 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
11219 - Move moria1 and tonga to alternate IP addresses.
11222 - Fix a signed/unsigned compile warning in 0.2.1.19.
11223 - Fix possible segmentation fault on directory authorities. Bugfix on
11225 - Fix an extremely rare infinite recursion bug that could occur if
11226 we tried to log a message after shutting down the log subsystem.
11227 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
11228 - Fix an obscure bug where hidden services on 64-bit big-endian
11229 systems might mis-read the timestamp in v3 introduce cells, and
11230 refuse to connect back to the client. Discovered by "rotor".
11231 Bugfix on 0.2.1.6-alpha.
11232 - We were triggering a CLOCK_SKEW controller status event whenever
11233 we connect via the v2 connection protocol to any relay that has
11234 a wrong clock. Instead, we should only inform the controller when
11235 it's a trusted authority that claims our clock is wrong. Bugfix
11236 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
11237 - We were telling the controller about CHECKING_REACHABILITY and
11238 REACHABILITY_FAILED status events whenever we launch a testing
11239 circuit or notice that one has failed. Instead, only tell the
11240 controller when we want to inform the user of overall success or
11241 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
11243 - Don't warn when we're using a circuit that ends with a node
11244 excluded in ExcludeExitNodes, but the circuit is not used to access
11245 the outside world. This should help fix bug 1090. Bugfix on
11247 - Work around a small memory leak in some versions of OpenSSL that
11248 stopped the memory used by the hostname TLS extension from being
11252 - Add a "getinfo status/accepted-server-descriptor" controller
11253 command, which is the recommended way for controllers to learn
11254 whether our server descriptor has been successfully received by at
11255 least on directory authority. Un-recommend good-server-descriptor
11256 getinfo and status events until we have a better design for them.
11259 Changes in version 0.2.2.5-alpha - 2009-10-11
11260 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
11263 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
11265 o Directory authorities:
11266 - Temporarily (just for this release) move dizum to an alternate
11270 Changes in version 0.2.2.4-alpha - 2009-10-10
11271 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
11272 introduces a new unit test framework, shifts directry authority
11273 addresses around to reduce the impact from recent blocking events,
11274 and fixes a few smaller bugs.
11277 - Fix several more asserts in the circuit_build_times code, for
11278 example one that causes Tor to fail to start once we have
11279 accumulated 5000 build times in the state file. Bugfixes on
11280 0.2.2.2-alpha; fixes bug 1108.
11282 o New directory authorities:
11283 - Move moria1 and Tonga to alternate IP addresses.
11286 - Log SSL state transitions at debug level during handshake, and
11287 include SSL states in error messages. This may help debug future
11288 SSL handshake issues.
11289 - Add a new "Handshake" log domain for activities that happen
11290 during the TLS handshake.
11291 - Revert to the "June 3 2009" ip-to-country file. The September one
11292 seems to have removed most US IP addresses.
11293 - Directory authorities now reject Tor relays with versions less than
11294 0.1.2.14. This step cuts out four relays from the current network,
11295 none of which are very big.
11298 - Fix a couple of smaller issues with gathering statistics. Bugfixes
11300 - Fix two memory leaks in the error case of
11301 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
11302 - Don't count one-hop circuits when we're estimating how long it
11303 takes circuits to build on average. Otherwise we'll set our circuit
11304 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
11305 - Directory authorities no longer change their opinion of, or vote on,
11306 whether a router is Running, unless they have themselves been
11307 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
11310 o Code simplifications and refactoring:
11311 - Revise our unit tests to use the "tinytest" framework, so we
11312 can run tests in their own processes, have smarter setup/teardown
11313 code, and so on. The unit test code has moved to its own
11314 subdirectory, and has been split into multiple modules.
11317 Changes in version 0.2.2.3-alpha - 2009-09-23
11318 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
11321 - Fix an overzealous assert in our new circuit build timeout code.
11322 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
11325 - If the networkstatus consensus tells us that we should use a
11326 negative circuit package window, ignore it. Otherwise we'll
11327 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
11330 Changes in version 0.2.2.2-alpha - 2009-09-21
11331 Tor 0.2.2.2-alpha introduces our latest performance improvement for
11332 clients: Tor tracks the average time it takes to build a circuit, and
11333 avoids using circuits that take too long to build. For fast connections,
11334 this feature can cut your expected latency in half. For slow or flaky
11335 connections, it could ruin your Tor experience. Let us know if it does!
11338 - Tor now tracks how long it takes to build client-side circuits
11339 over time, and adapts its timeout to local network performance.
11340 Since a circuit that takes a long time to build will also provide
11341 bad performance, we get significant latency improvements by
11342 discarding the slowest 20% of circuits. Specifically, Tor creates
11343 circuits more aggressively than usual until it has enough data
11344 points for a good timeout estimate. Implements proposal 151.
11345 We are especially looking for reports (good and bad) from users with
11346 both EDGE and broadband connections that can move from broadband
11347 to EDGE and find out if the build-time data in the .tor/state gets
11348 reset without loss of Tor usability. You should also see a notice
11349 log message telling you that Tor has reset its timeout.
11350 - Directory authorities can now vote on arbitary integer values as
11351 part of the consensus process. This is designed to help set
11352 network-wide parameters. Implements proposal 167.
11353 - Tor now reads the "circwindow" parameter out of the consensus,
11354 and uses that value for its circuit package window rather than the
11355 default of 1000 cells. Begins the implementation of proposal 168.
11358 - Fix a remotely triggerable memory leak when a consensus document
11359 contains more than one signature from the same voter. Bugfix on
11363 - Fix an extremely rare infinite recursion bug that could occur if
11364 we tried to log a message after shutting down the log subsystem.
11365 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
11366 - Fix parsing for memory or time units given without a space between
11367 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
11368 - A networkstatus vote must contain exactly one signature. Spec
11369 conformance issue. Bugfix on 0.2.0.3-alpha.
11370 - Fix an obscure bug where hidden services on 64-bit big-endian
11371 systems might mis-read the timestamp in v3 introduce cells, and
11372 refuse to connect back to the client. Discovered by "rotor".
11373 Bugfix on 0.2.1.6-alpha.
11374 - We were triggering a CLOCK_SKEW controller status event whenever
11375 we connect via the v2 connection protocol to any relay that has
11376 a wrong clock. Instead, we should only inform the controller when
11377 it's a trusted authority that claims our clock is wrong. Bugfix
11378 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
11379 - We were telling the controller about CHECKING_REACHABILITY and
11380 REACHABILITY_FAILED status events whenever we launch a testing
11381 circuit or notice that one has failed. Instead, only tell the
11382 controller when we want to inform the user of overall success or
11383 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
11385 - Don't warn when we're using a circuit that ends with a node
11386 excluded in ExcludeExitNodes, but the circuit is not used to access
11387 the outside world. This should help fix bug 1090, but more problems
11388 remain. Bugfix on 0.2.1.6-alpha.
11389 - Work around a small memory leak in some versions of OpenSSL that
11390 stopped the memory used by the hostname TLS extension from being
11392 - Make our 'torify' script more portable; if we have only one of
11393 'torsocks' or 'tsocks' installed, don't complain to the user;
11394 and explain our warning about tsocks better.
11397 - Add a "getinfo status/accepted-server-descriptor" controller
11398 command, which is the recommended way for controllers to learn
11399 whether our server descriptor has been successfully received by at
11400 least on directory authority. Un-recommend good-server-descriptor
11401 getinfo and status events until we have a better design for them.
11402 - Update to the "September 4 2009" ip-to-country file.
11405 Changes in version 0.2.2.1-alpha - 2009-08-26
11406 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
11407 Tor clients to bootstrap on networks where only port 80 is reachable,
11408 makes it more straightforward to support hardware crypto accelerators,
11409 and starts the groundwork for gathering stats safely at relays.
11412 - Start the process of disabling ".exit" address notation, since it
11413 can be used for a variety of esoteric application-level attacks
11414 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
11417 o New directory authorities:
11418 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
11422 - New AccelName and AccelDir options add support for dynamic OpenSSL
11423 hardware crypto acceleration engines.
11424 - Tor now supports tunneling all of its outgoing connections over
11425 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
11426 configuration options. Code by Christopher Davis.
11429 - Send circuit or stream sendme cells when our window has decreased
11430 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
11431 by Karsten when testing the "reduce circuit window" performance
11432 patch. Bugfix on the 54th commit on Tor -- from July 2002,
11433 before the release of Tor 0.0.0. This is the new winner of the
11436 o New options for gathering stats safely:
11437 - Directory mirrors that set "DirReqStatistics 1" write statistics
11438 about directory requests to disk every 24 hours. As compared to the
11439 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
11440 1) stats are written to disk exactly every 24 hours; 2) estimated
11441 shares of v2 and v3 requests are determined as mean values, not at
11442 the end of a measurement period; 3) unresolved requests are listed
11443 with country code '??'; 4) directories also measure download times.
11444 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
11445 number of exit streams and transferred bytes per port to disk every
11447 - Relays that set "CellStatistics 1" write statistics on how long
11448 cells spend in their circuit queues to disk every 24 hours.
11449 - Entry nodes that set "EntryStatistics 1" write statistics on the
11450 rough number and origins of connecting clients to disk every 24
11452 - Relays that write any of the above statistics to disk and set
11453 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
11454 their extra-info documents.
11457 - New --digests command-line switch to output the digests of the
11458 source files Tor was built with.
11459 - The "torify" script now uses torsocks where available.
11460 - The memarea code now uses a sentinel value at the end of each area
11461 to make sure nothing writes beyond the end of an area. This might
11462 help debug some conceivable causes of bug 930.
11463 - Time and memory units in the configuration file can now be set to
11464 fractional units. For example, "2.5 GB" is now a valid value for
11466 - Certain Tor clients (such as those behind check.torproject.org) may
11467 want to fetch the consensus in an extra early manner. To enable this
11468 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
11469 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
11470 as only certain clients who must have this information sooner should
11472 - Instead of adding the svn revision to the Tor version string, report
11473 the git commit (when we're building from a git checkout).
11476 - If any of the v3 certs we download are unparseable, we should
11477 actually notice the failure so we don't retry indefinitely. Bugfix
11478 on 0.2.0.x; reported by "rotator".
11479 - If the cached cert file is unparseable, warn but don't exit.
11480 - Fix possible segmentation fault on directory authorities. Bugfix on
11482 - When Tor fails to parse a descriptor of any kind, dump it to disk.
11483 Might help diagnosing bug 1051.
11485 o Deprecated and removed features:
11486 - The controller no longer accepts the old obsolete "addr-mappings/"
11487 or "unregistered-servers-" GETINFO values.
11488 - Hidden services no longer publish version 0 descriptors, and clients
11489 do not request or use version 0 descriptors. However, the old hidden
11490 service authorities still accept and serve version 0 descriptors
11491 when contacted by older hidden services/clients.
11492 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
11493 always on; using them is necessary for correct forward-compatible
11495 - Remove support for .noconnect style addresses. Nobody was using
11496 them, and they provided another avenue for detecting Tor users
11497 via application-level web tricks.
11499 o Packaging changes:
11500 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
11501 installer bundles. See
11502 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
11503 for details of what's new in Vidalia 0.2.3.
11504 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
11505 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
11506 configuration file, rather than the old Privoxy.
11507 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
11508 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
11509 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
11510 better compatibility with OS X 10.6, aka Snow Leopard.
11511 - OS X Vidalia Bundle: The multi-package installer is now replaced
11512 by a simple drag and drop to the /Applications folder. This change
11513 occurred with the upgrade to Vidalia 0.2.3.
11516 Changes in version 0.2.1.19 - 2009-07-28
11517 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
11518 services on Tor 0.2.1.3-alpha through 0.2.1.18.
11521 - Make accessing hidden services on 0.2.1.x work right again.
11522 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
11523 part of patch provided by "optimist".
11526 - When a relay/bridge is writing out its identity key fingerprint to
11527 the "fingerprint" file and to its logs, write it without spaces. Now
11528 it will look like the fingerprints in our bridges documentation,
11529 and confuse fewer users.
11532 - Relays no longer publish a new server descriptor if they change
11533 their MaxAdvertisedBandwidth config option but it doesn't end up
11534 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
11535 fixes bug 1026. Patch from Sebastian.
11536 - Avoid leaking memory every time we get a create cell but we have
11537 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
11538 fixes bug 1034. Reported by BarkerJr.
11541 Changes in version 0.2.1.18 - 2009-07-24
11542 Tor 0.2.1.18 lays the foundations for performance improvements,
11543 adds status events to help users diagnose bootstrap problems, adds
11544 optional authentication/authorization for hidden services, fixes a
11545 variety of potential anonymity problems, and includes a huge pile of
11546 other features and bug fixes.
11549 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
11552 Changes in version 0.2.1.17-rc - 2009-07-07
11553 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
11554 candidate for the 0.2.1.x series. It lays the groundwork for further
11555 client performance improvements, and also fixes a big bug with directory
11556 authorities that were causing them to assign Guard and Stable flags
11559 The Windows bundles also finally include the geoip database that we
11560 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
11561 should actually install Torbutton rather than giving you a cryptic
11562 failure message (oops).
11565 - Clients now use the bandwidth values in the consensus, rather than
11566 the bandwidth values in each relay descriptor. This approach opens
11567 the door to more accurate bandwidth estimates once the directory
11568 authorities start doing active measurements. Implements more of
11572 - When Tor clients restart after 1-5 days, they discard all their
11573 cached descriptors as too old, but they still use the cached
11574 consensus document. This approach is good for robustness, but
11575 bad for performance: since they don't know any bandwidths, they
11576 end up choosing at random rather than weighting their choice by
11577 speed. Fixed by the above feature of putting bandwidths in the
11578 consensus. Bugfix on 0.2.0.x.
11579 - Directory authorities were neglecting to mark relays down in their
11580 internal histories if the relays fall off the routerlist without
11581 ever being found unreachable. So there were relays in the histories
11582 that haven't been seen for eight months, and are listed as being
11583 up for eight months. This wreaked havoc on the "median wfu"
11584 and "median mtbf" calculations, in turn making Guard and Stable
11585 flags very wrong, hurting network performance. Fixes bugs 696 and
11586 969. Bugfix on 0.2.0.6-alpha.
11589 - Serve the DirPortFrontPage page even when we have been approaching
11590 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
11591 - The control port would close the connection before flushing long
11592 replies, such as the network consensus, if a QUIT command was issued
11593 before the reply had completed. Now, the control port flushes all
11594 pending replies before closing the connection. Also fixed a spurious
11595 warning when a QUIT command is issued after a malformed or rejected
11596 AUTHENTICATE command, but before the connection was closed. Patch
11597 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
11598 - When we can't find an intro key for a v2 hidden service descriptor,
11599 fall back to the v0 hidden service descriptor and log a bug message.
11600 Workaround for bug 1024.
11601 - Fix a log message that did not respect the SafeLogging option.
11605 - If we're a relay and we change our IP address, be more verbose
11606 about the reason that made us change. Should help track down
11607 further bugs for relays on dynamic IP addresses.
11610 Changes in version 0.2.0.35 - 2009-06-24
11612 - Avoid crashing in the presence of certain malformed descriptors.
11613 Found by lark, and by automated fuzzing.
11614 - Fix an edge case where a malicious exit relay could convince a
11615 controller that the client's DNS question resolves to an internal IP
11616 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
11619 - Finally fix the bug where dynamic-IP relays disappear when their
11620 IP address changes: directory mirrors were mistakenly telling
11621 them their old address if they asked via begin_dir, so they
11622 never got an accurate answer about their new address, so they
11623 just vanished after a day. For belt-and-suspenders, relays that
11624 don't set Address in their config now avoid using begin_dir for
11625 all direct connections. Should fix bugs 827, 883, and 900.
11626 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
11627 that would occur on some exit nodes when DNS failures and timeouts
11628 occurred in certain patterns. Fix for bug 957.
11631 - When starting with a cache over a few days old, do not leak
11632 memory for the obsolete router descriptors in it. Bugfix on
11633 0.2.0.33; fixes bug 672.
11634 - Hidden service clients didn't use a cached service descriptor that
11635 was older than 15 minutes, but wouldn't fetch a new one either,
11636 because there was already one in the cache. Now, fetch a v2
11637 descriptor unless the same descriptor was added to the cache within
11638 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
11641 Changes in version 0.2.1.16-rc - 2009-06-20
11642 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
11643 a bunch of minor bugs.
11646 - Fix an edge case where a malicious exit relay could convince a
11647 controller that the client's DNS question resolves to an internal IP
11648 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
11650 o Major performance improvements (on 0.2.0.x):
11651 - Disable and refactor some debugging checks that forced a linear scan
11652 over the whole server-side DNS cache. These accounted for over 50%
11653 of CPU time on a relatively busy exit node's gprof profile. Found
11655 - Disable some debugging checks that appeared in exit node profile
11659 - Update to the "June 3 2009" ip-to-country file.
11660 - Do not have tor-resolve automatically refuse all .onion addresses;
11661 if AutomapHostsOnResolve is set in your torrc, this will work fine.
11663 o Minor bugfixes (on 0.2.0.x):
11664 - Log correct error messages for DNS-related network errors on
11666 - Fix a race condition that could cause crashes or memory corruption
11667 when running as a server with a controller listening for log
11669 - Avoid crashing when we have a policy specified in a DirPolicy or
11670 SocksPolicy or ReachableAddresses option with ports set on it,
11671 and we re-load the policy. May fix bug 996.
11672 - Hidden service clients didn't use a cached service descriptor that
11673 was older than 15 minutes, but wouldn't fetch a new one either,
11674 because there was already one in the cache. Now, fetch a v2
11675 descriptor unless the same descriptor was added to the cache within
11676 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
11678 o Minor bugfixes (on 0.2.1.x):
11679 - Don't warn users about low port and hibernation mix when they
11680 provide a *ListenAddress directive to fix that. Bugfix on
11682 - When switching back and forth between bridge mode, do not start
11683 gathering GeoIP data until two hours have passed.
11684 - Do not complain that the user has requested an excluded node as
11685 an exit when the node is not really an exit. This could happen
11686 because the circuit was for testing, or an introduction point.
11690 Changes in version 0.2.1.15-rc - 2009-05-25
11691 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
11692 series. It fixes a major bug on fast exit relays, as well as a variety
11693 of more minor bugs.
11695 o Major bugfixes (on 0.2.0.x):
11696 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
11697 that would occur on some exit nodes when DNS failures and timeouts
11698 occurred in certain patterns. Fix for bug 957.
11700 o Minor bugfixes (on 0.2.0.x):
11701 - Actually return -1 in the error case for read_bandwidth_usage().
11702 Harmless bug, since we currently don't care about the return value
11703 anywhere. Bugfix on 0.2.0.9-alpha.
11704 - Provide a more useful log message if bug 977 (related to buffer
11705 freelists) ever reappears, and do not crash right away.
11706 - Fix an assertion failure on 64-bit platforms when we allocated
11707 memory right up to the end of a memarea, then realigned the memory
11708 one step beyond the end. Fixes a possible cause of bug 930.
11709 - Protect the count of open sockets with a mutex, so we can't
11710 corrupt it when two threads are closing or opening sockets at once.
11711 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
11712 - Don't allow a bridge to publish its router descriptor to a
11713 non-bridge directory authority. Fixes part of bug 932.
11714 - When we change to or from being a bridge, reset our counts of
11715 client usage by country. Fixes bug 932.
11716 - Fix a bug that made stream bandwidth get misreported to the
11718 - Stop using malloc_usable_size() to use more area than we had
11719 actually allocated: it was safe, but made valgrind really unhappy.
11720 - Fix a memory leak when v3 directory authorities load their keys
11721 and cert from disk. Bugfix on 0.2.0.1-alpha.
11723 o Minor bugfixes (on 0.2.1.x):
11724 - Fix use of freed memory when deciding to mark a non-addable
11725 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
11728 Changes in version 0.2.1.14-rc - 2009-04-12
11729 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
11730 series. It begins fixing some major performance problems, and also
11731 finally addresses the bug that was causing relays on dynamic IP
11732 addresses to fall out of the directory.
11735 - Clients replace entry guards that were chosen more than a few months
11736 ago. This change should significantly improve client performance,
11737 especially once more people upgrade, since relays that have been
11738 a guard for a long time are currently overloaded.
11740 o Major bugfixes (on 0.2.0):
11741 - Finally fix the bug where dynamic-IP relays disappear when their
11742 IP address changes: directory mirrors were mistakenly telling
11743 them their old address if they asked via begin_dir, so they
11744 never got an accurate answer about their new address, so they
11745 just vanished after a day. For belt-and-suspenders, relays that
11746 don't set Address in their config now avoid using begin_dir for
11747 all direct connections. Should fix bugs 827, 883, and 900.
11748 - Relays were falling out of the networkstatus consensus for
11749 part of a day if they changed their local config but the
11750 authorities discarded their new descriptor as "not sufficiently
11751 different". Now directory authorities accept a descriptor as changed
11752 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
11753 patch by Sebastian.
11754 - Avoid crashing in the presence of certain malformed descriptors.
11755 Found by lark, and by automated fuzzing.
11758 - When generating circuit events with verbose nicknames for
11759 controllers, try harder to look up nicknames for routers on a
11760 circuit. (Previously, we would look in the router descriptors we had
11761 for nicknames, but not in the consensus.) Partial fix for bug 941.
11762 - If the bridge config line doesn't specify a port, assume 443.
11763 This makes bridge lines a bit smaller and easier for users to
11765 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
11766 bytes (aka 20KB/s), to match our documentation. Also update
11767 directory authorities so they always assign the Fast flag to relays
11768 with 20KB/s of capacity. Now people running relays won't suddenly
11769 find themselves not seeing any use, if the network gets faster
11771 - Update to the "April 3 2009" ip-to-country file.
11774 - Avoid trying to print raw memory to the logs when we decide to
11775 give up on downloading a given relay descriptor. Bugfix on
11777 - In tor-resolve, when the Tor client to use is specified by
11778 <hostname>:<port>, actually use the specified port rather than
11779 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
11780 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
11781 - When starting with a cache over a few days old, do not leak
11782 memory for the obsolete router descriptors in it. Bugfix on
11784 - Avoid double-free on list of successfully uploaded hidden
11785 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
11786 - Change memarea_strndup() implementation to work even when
11787 duplicating a string at the end of a page. This bug was
11788 harmless for now, but could have meant crashes later. Fix by
11789 lark. Bugfix on 0.2.1.1-alpha.
11790 - Limit uploaded directory documents to be 16M rather than 500K.
11791 The directory authorities were refusing v3 consensus votes from
11792 other authorities, since the votes are now 504K. Fixes bug 959;
11793 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
11794 - Directory authorities should never send a 503 "busy" response to
11795 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
11799 Changes in version 0.2.1.13-alpha - 2009-03-09
11800 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
11801 cleanups. We're finally getting close to a release candidate.
11804 - Correctly update the list of which countries we exclude as
11805 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
11806 lark. Bugfix on 0.2.1.6-alpha.
11808 o Minor bugfixes (on 0.2.0.x and earlier):
11809 - Automatically detect MacOSX versions earlier than 10.4.0, and
11810 disable kqueue from inside Tor when running with these versions.
11811 We previously did this from the startup script, but that was no
11812 help to people who didn't use the startup script. Resolves bug 863.
11813 - When we had picked an exit node for a connection, but marked it as
11814 "optional", and it turned out we had no onion key for the exit,
11815 stop wanting that exit and try again. This situation may not
11816 be possible now, but will probably become feasible with proposal
11817 158. Spotted by rovv. Fixes another case of bug 752.
11818 - Clients no longer cache certificates for authorities they do not
11819 recognize. Bugfix on 0.2.0.9-alpha.
11820 - When we can't transmit a DNS request due to a network error, retry
11821 it after a while, and eventually transmit a failing response to
11822 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
11823 - If the controller claimed responsibility for a stream, but that
11824 stream never finished making its connection, it would live
11825 forever in circuit_wait state. Now we close it after SocksTimeout
11826 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
11827 - Drop begin cells to a hidden service if they come from the middle
11828 of a circuit. Patch from lark.
11829 - When we erroneously receive two EXTEND cells for the same circuit
11830 ID on the same connection, drop the second. Patch from lark.
11831 - Fix a crash that occurs on exit nodes when a nameserver request
11832 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
11833 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
11835 - Do not assume that a stack-allocated character array will be
11836 64-bit aligned on platforms that demand that uint64_t access is
11837 aligned. Possible fix for bug 604.
11838 - Parse dates and IPv4 addresses in a locale- and libc-independent
11839 manner, to avoid platform-dependent behavior on malformed input.
11840 - Build correctly when configured to build outside the main source
11841 path. Patch from Michael Gold.
11842 - We were already rejecting relay begin cells with destination port
11843 of 0. Now also reject extend cells with destination port or address
11844 of 0. Suggested by lark.
11846 o Minor bugfixes (on 0.2.1.x):
11847 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
11848 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
11849 - If we're an exit node, scrub the IP address to which we are exiting
11850 in the logs. Bugfix on 0.2.1.8-alpha.
11853 - On Linux, use the prctl call to re-enable core dumps when the user
11855 - New controller event NEWCONSENSUS that lists the networkstatus
11856 lines for every recommended relay. Now controllers like Torflow
11857 can keep up-to-date on which relays they should be using.
11858 - Update to the "February 26 2009" ip-to-country file.
11861 Changes in version 0.2.0.34 - 2009-02-08
11862 Tor 0.2.0.34 features several more security-related fixes. You should
11863 upgrade, especially if you run an exit relay (remote crash) or a
11864 directory authority (remote infinite loop), or you're on an older
11865 (pre-XP) or not-recently-patched Windows (remote exploit).
11867 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
11868 have many known flaws, and nobody should be using them. You should
11869 upgrade. If you're using a Linux or BSD and its packages are obsolete,
11870 stop using those packages and upgrade anyway.
11873 - Fix an infinite-loop bug on handling corrupt votes under certain
11874 circumstances. Bugfix on 0.2.0.8-alpha.
11875 - Fix a temporary DoS vulnerability that could be performed by
11876 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
11877 - Avoid a potential crash on exit nodes when processing malformed
11878 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
11879 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
11880 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
11883 - Fix compilation on systems where time_t is a 64-bit integer.
11884 Patch from Matthias Drochner.
11885 - Don't consider expiring already-closed client connections. Fixes
11886 bug 893. Bugfix on 0.0.2pre20.
11889 Changes in version 0.2.1.12-alpha - 2009-02-08
11890 Tor 0.2.1.12-alpha features several more security-related fixes. You
11891 should upgrade, especially if you run an exit relay (remote crash) or
11892 a directory authority (remote infinite loop), or you're on an older
11893 (pre-XP) or not-recently-patched Windows (remote exploit). It also
11894 includes a big pile of minor bugfixes and cleanups.
11897 - Fix an infinite-loop bug on handling corrupt votes under certain
11898 circumstances. Bugfix on 0.2.0.8-alpha.
11899 - Fix a temporary DoS vulnerability that could be performed by
11900 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
11901 - Avoid a potential crash on exit nodes when processing malformed
11902 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
11905 - Let controllers actually ask for the "clients_seen" event for
11906 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
11907 reported by Matt Edman.
11908 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
11910 - Fix a bug in address parsing that was preventing bridges or hidden
11911 service targets from being at IPv6 addresses.
11912 - Solve a bug that kept hardware crypto acceleration from getting
11913 enabled when accounting was turned on. Fixes bug 907. Bugfix on
11915 - Remove a bash-ism from configure.in to build properly on non-Linux
11916 platforms. Bugfix on 0.2.1.1-alpha.
11917 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
11918 headers. Bugfix on 0.2.0.10-alpha.
11919 - Don't consider expiring already-closed client connections. Fixes
11920 bug 893. Bugfix on 0.0.2pre20.
11921 - Fix another interesting corner-case of bug 891 spotted by rovv:
11922 Previously, if two hosts had different amounts of clock drift, and
11923 one of them created a new connection with just the wrong timing,
11924 the other might decide to deprecate the new connection erroneously.
11925 Bugfix on 0.1.1.13-alpha.
11926 - Resolve a very rare crash bug that could occur when the user forced
11927 a nameserver reconfiguration during the middle of a nameserver
11928 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
11929 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
11930 Bugfix on 0.2.1.7-alpha.
11931 - If we're using bridges and our network goes away, be more willing
11932 to forgive our bridges and try again when we get an application
11933 request. Bugfix on 0.2.0.x.
11936 - Support platforms where time_t is 64 bits long. (Congratulations,
11937 NetBSD!) Patch from Matthias Drochner.
11938 - Add a 'getinfo status/clients-seen' controller command, in case
11939 controllers want to hear clients_seen events but connect late.
11942 - Disable GCC's strict alias optimization by default, to avoid the
11943 likelihood of its introducing subtle bugs whenever our code violates
11944 the letter of C99's alias rules.
11947 Changes in version 0.2.0.33 - 2009-01-21
11948 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
11949 useful to users. It also finally fixes a bug where a relay or client
11950 that's been off for many days would take a long time to bootstrap.
11952 This update also fixes an important security-related bug reported by
11953 Ilja van Sprundel. You should upgrade. (We'll send out more details
11954 about the bug once people have had some time to upgrade.)
11957 - Fix a heap-corruption bug that may be remotely triggerable on
11958 some platforms. Reported by Ilja van Sprundel.
11961 - When a stream at an exit relay is in state "resolving" or
11962 "connecting" and it receives an "end" relay cell, the exit relay
11963 would silently ignore the end cell and not close the stream. If
11964 the client never closes the circuit, then the exit relay never
11965 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
11966 reported by "wood".
11967 - When sending CREATED cells back for a given circuit, use a 64-bit
11968 connection ID to find the right connection, rather than an addr:port
11969 combination. Now that we can have multiple OR connections between
11970 the same ORs, it is no longer possible to use addr:port to uniquely
11971 identify a connection.
11972 - Bridge relays that had DirPort set to 0 would stop fetching
11973 descriptors shortly after startup, and then briefly resume
11974 after a new bandwidth test and/or after publishing a new bridge
11975 descriptor. Bridge users that try to bootstrap from them would
11976 get a recent networkstatus but would get descriptors from up to
11977 18 hours earlier, meaning most of the descriptors were obsolete
11978 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
11979 - Prevent bridge relays from serving their 'extrainfo' document
11980 to anybody who asks, now that extrainfo docs include potentially
11981 sensitive aggregated client geoip summaries. Bugfix on
11983 - If the cached networkstatus consensus is more than five days old,
11984 discard it rather than trying to use it. In theory it could be
11985 useful because it lists alternate directory mirrors, but in practice
11986 it just means we spend many minutes trying directory mirrors that
11987 are long gone from the network. Also discard router descriptors as
11988 we load them if they are more than five days old, since the onion
11989 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
11992 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
11993 could make gcc generate non-functional binary search code. Bugfix
11995 - Build correctly on platforms without socklen_t.
11996 - Compile without warnings on solaris.
11997 - Avoid potential crash on internal error during signature collection.
11998 Fixes bug 864. Patch from rovv.
11999 - Correct handling of possible malformed authority signing key
12000 certificates with internal signature types. Fixes bug 880.
12001 Bugfix on 0.2.0.3-alpha.
12002 - Fix a hard-to-trigger resource leak when logging credential status.
12004 - When we can't initialize DNS because the network is down, do not
12005 automatically stop Tor from starting. Instead, we retry failed
12006 dns_init() every 10 minutes, and change the exit policy to reject
12007 *:* until one succeeds. Fixes bug 691.
12008 - Use 64 bits instead of 32 bits for connection identifiers used with
12009 the controller protocol, to greatly reduce risk of identifier reuse.
12010 - When we're choosing an exit node for a circuit, and we have
12011 no pending streams, choose a good general exit rather than one that
12012 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
12013 - Fix another case of assuming, when a specific exit is requested,
12014 that we know more than the user about what hosts it allows.
12015 Fixes one case of bug 752. Patch from rovv.
12016 - Clip the MaxCircuitDirtiness config option to a minimum of 10
12017 seconds. Warn the user if lower values are given in the
12018 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
12019 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
12020 user if lower values are given in the configuration. Bugfix on
12021 0.1.1.17-rc. Patch by Sebastian.
12022 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
12023 the cache because we already had a v0 descriptor with the same ID.
12024 Bugfix on 0.2.0.18-alpha.
12025 - Fix a race condition when freeing keys shared between main thread
12026 and CPU workers that could result in a memory leak. Bugfix on
12027 0.1.0.1-rc. Fixes bug 889.
12028 - Send a valid END cell back when a client tries to connect to a
12029 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
12030 840. Patch from rovv.
12031 - Check which hops rendezvous stream cells are associated with to
12032 prevent possible guess-the-streamid injection attacks from
12033 intermediate hops. Fixes another case of bug 446. Based on patch
12035 - If a broken client asks a non-exit router to connect somewhere,
12036 do not even do the DNS lookup before rejecting the connection.
12037 Fixes another case of bug 619. Patch from rovv.
12038 - When a relay gets a create cell it can't decrypt (e.g. because it's
12039 using the wrong onion key), we were dropping it and letting the
12040 client time out. Now actually answer with a destroy cell. Fixes
12041 bug 904. Bugfix on 0.0.2pre8.
12043 o Minor bugfixes (hidden services):
12044 - Do not throw away existing introduction points on SIGHUP. Bugfix on
12045 0.0.6pre1. Patch by Karsten. Fixes bug 874.
12048 - Report the case where all signatures in a detached set are rejected
12049 differently than the case where there is an error handling the
12051 - When we realize that another process has modified our cached
12052 descriptors, print out a more useful error message rather than
12053 triggering an assertion. Fixes bug 885. Patch from Karsten.
12054 - Implement the 0x20 hack to better resist DNS poisoning: set the
12055 case on outgoing DNS requests randomly, and reject responses that do
12056 not match the case correctly. This logic can be disabled with the
12057 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
12058 of servers that do not reliably preserve case in replies. See
12059 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
12061 - Check DNS replies for more matching fields to better resist DNS
12063 - Never use OpenSSL compression: it wastes RAM and CPU trying to
12064 compress cells, which are basically all encrypted, compressed, or
12068 Changes in version 0.2.1.11-alpha - 2009-01-20
12069 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
12070 week it will take a long time to bootstrap again" bug. It also fixes
12071 an important security-related bug reported by Ilja van Sprundel. You
12072 should upgrade. (We'll send out more details about the bug once people
12073 have had some time to upgrade.)
12076 - Fix a heap-corruption bug that may be remotely triggerable on
12077 some platforms. Reported by Ilja van Sprundel.
12080 - Discard router descriptors as we load them if they are more than
12081 five days old. Otherwise if Tor is off for a long time and then
12082 starts with cached descriptors, it will try to use the onion
12083 keys in those obsolete descriptors when building circuits. Bugfix
12084 on 0.2.0.x. Fixes bug 887.
12087 - Try to make sure that the version of Libevent we're running with
12088 is binary-compatible with the one we built with. May address bug
12090 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
12091 for bug 905. Bugfix on 0.2.1.7-alpha.
12092 - Add a new --enable-local-appdata configuration switch to change
12093 the default location of the datadir on win32 from APPDATA to
12094 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
12095 entirely. Patch from coderman.
12098 - Make outbound DNS packets respect the OutboundBindAddress setting.
12099 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
12100 - When our circuit fails at the first hop (e.g. we get a destroy
12101 cell back), avoid using that OR connection anymore, and also
12102 tell all the one-hop directory requests waiting for it that they
12103 should fail. Bugfix on 0.2.1.3-alpha.
12104 - In the torify(1) manpage, mention that tsocks will leak your
12108 Changes in version 0.2.1.10-alpha - 2009-01-06
12109 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
12110 would make the bridge relay not so useful if it had DirPort set to 0,
12111 and one that could let an attacker learn a little bit of information
12112 about the bridge's users), and a bug that would cause your Tor relay
12113 to ignore a circuit create request it can't decrypt (rather than reply
12114 with an error). It also fixes a wide variety of other bugs.
12117 - If the cached networkstatus consensus is more than five days old,
12118 discard it rather than trying to use it. In theory it could
12119 be useful because it lists alternate directory mirrors, but in
12120 practice it just means we spend many minutes trying directory
12121 mirrors that are long gone from the network. Helps bug 887 a bit;
12123 - Bridge relays that had DirPort set to 0 would stop fetching
12124 descriptors shortly after startup, and then briefly resume
12125 after a new bandwidth test and/or after publishing a new bridge
12126 descriptor. Bridge users that try to bootstrap from them would
12127 get a recent networkstatus but would get descriptors from up to
12128 18 hours earlier, meaning most of the descriptors were obsolete
12129 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
12130 - Prevent bridge relays from serving their 'extrainfo' document
12131 to anybody who asks, now that extrainfo docs include potentially
12132 sensitive aggregated client geoip summaries. Bugfix on
12136 - New controller event "clients_seen" to report a geoip-based summary
12137 of which countries we've seen clients from recently. Now controllers
12138 like Vidalia can show bridge operators that they're actually making
12140 - Build correctly against versions of OpenSSL 0.9.8 or later built
12141 without support for deprecated functions.
12142 - Update to the "December 19 2008" ip-to-country file.
12144 o Minor bugfixes (on 0.2.0.x):
12145 - Authorities now vote for the Stable flag for any router whose
12146 weighted MTBF is at least 5 days, regardless of the mean MTBF.
12147 - Do not remove routers as too old if we do not have any consensus
12148 document. Bugfix on 0.2.0.7-alpha.
12149 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
12150 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
12151 - When an exit relay resolves a stream address to a local IP address,
12152 do not just keep retrying that same exit relay over and
12153 over. Instead, just close the stream. Addresses bug 872. Bugfix
12154 on 0.2.0.32. Patch from rovv.
12155 - If a hidden service sends us an END cell, do not consider
12156 retrying the connection; just close it. Patch from rovv.
12157 - When we made bridge authorities stop serving bridge descriptors over
12158 unencrypted links, we also broke DirPort reachability testing for
12159 bridges. So bridges with a non-zero DirPort were printing spurious
12160 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
12161 - When a relay gets a create cell it can't decrypt (e.g. because it's
12162 using the wrong onion key), we were dropping it and letting the
12163 client time out. Now actually answer with a destroy cell. Fixes
12164 bug 904. Bugfix on 0.0.2pre8.
12165 - Squeeze 2-5% out of client performance (according to oprofile) by
12166 improving the implementation of some policy-manipulation functions.
12168 o Minor bugfixes (on 0.2.1.x):
12169 - Make get_interface_address() function work properly again; stop
12170 guessing the wrong parts of our address as our address.
12171 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
12172 send on that circuit. Otherwise we might violate the proposal-110
12173 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
12175 - When we're sending non-EXTEND cells to the first hop in a circuit,
12176 for example to use an encrypted directory connection, we don't need
12177 to use RELAY_EARLY cells: the first hop knows what kind of cell
12178 it is, and nobody else can even see the cell type. Conserving
12179 RELAY_EARLY cells makes it easier to cannibalize circuits like
12181 - Stop logging nameserver addresses in reverse order.
12182 - If we are retrying a directory download slowly over and over, do
12183 not automatically give up after the 254th failure. Bugfix on
12185 - Resume reporting accurate "stream end" reasons to the local control
12186 port. They were lost in the changes for Proposal 148. Bugfix on
12189 o Deprecated and removed features:
12190 - The old "tor --version --version" command, which would print out
12191 the subversion "Id" of most of the source files, is now removed. It
12192 turned out to be less useful than we'd expected, and harder to
12195 o Code simplifications and refactoring:
12196 - Change our header file guard macros to be less likely to conflict
12197 with system headers. Adam Langley noticed that we were conflicting
12198 with log.h on Android.
12199 - Tool-assisted documentation cleanup. Nearly every function or
12200 static variable in Tor should have its own documentation now.
12203 Changes in version 0.2.1.9-alpha - 2008-12-25
12204 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
12206 o New directory authorities:
12207 - gabelmoo (the authority run by Karsten Loesing) now has a new
12211 - Never use a connection with a mismatched address to extend a
12212 circuit, unless that connection is canonical. A canonical
12213 connection is one whose address is authenticated by the router's
12214 identity key, either in a NETINFO cell or in a router descriptor.
12215 - Avoid a possible memory corruption bug when receiving hidden service
12216 descriptors. Bugfix on 0.2.1.6-alpha.
12219 - Fix a logic error that would automatically reject all but the first
12220 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
12221 part of bug 813/868. Bug spotted by coderman.
12222 - When a stream at an exit relay is in state "resolving" or
12223 "connecting" and it receives an "end" relay cell, the exit relay
12224 would silently ignore the end cell and not close the stream. If
12225 the client never closes the circuit, then the exit relay never
12226 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
12227 reported by "wood".
12228 - When we can't initialize DNS because the network is down, do not
12229 automatically stop Tor from starting. Instead, retry failed
12230 dns_init() every 10 minutes, and change the exit policy to reject
12231 *:* until one succeeds. Fixes bug 691.
12234 - Give a better error message when an overzealous init script says
12235 "sudo -u username tor --user username". Makes Bug 882 easier for
12237 - When a directory authority gives us a new guess for our IP address,
12238 log which authority we used. Hopefully this will help us debug
12239 the recent complaints about bad IP address guesses.
12240 - Detect svn revision properly when we're using git-svn.
12241 - Try not to open more than one descriptor-downloading connection
12242 to an authority at once. This should reduce load on directory
12243 authorities. Fixes bug 366.
12244 - Add cross-certification to newly generated certificates, so that
12245 a signing key is enough information to look up a certificate.
12246 Partial implementation of proposal 157.
12247 - Start serving certificates by <identity digest, signing key digest>
12248 pairs. Partial implementation of proposal 157.
12249 - Clients now never report any stream end reason except 'MISC'.
12250 Implements proposal 148.
12251 - On platforms with a maximum syslog string length, truncate syslog
12252 messages to that length ourselves, rather than relying on the
12253 system to do it for us.
12254 - Optimize out calls to time(NULL) that occur for every IO operation,
12255 or for every cell. On systems where time() is a slow syscall,
12256 this fix will be slightly helpful.
12257 - Exit servers can now answer resolve requests for ip6.arpa addresses.
12258 - When we download a descriptor that we then immediately (as
12259 a directory authority) reject, do not retry downloading it right
12260 away. Should save some bandwidth on authorities. Fix for bug
12261 888. Patch by Sebastian Hahn.
12262 - When a download gets us zero good descriptors, do not notify
12263 Tor that new directory information has arrived.
12264 - Avoid some nasty corner cases in the logic for marking connections
12265 as too old or obsolete or noncanonical for circuits. Partial
12268 o Minor features (controller):
12269 - New CONSENSUS_ARRIVED event to note when a new consensus has
12270 been fetched and validated.
12271 - When we realize that another process has modified our cached
12272 descriptors file, print out a more useful error message rather
12273 than triggering an assertion. Fixes bug 885. Patch from Karsten.
12274 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
12275 controllers to prevent SIGHUP from reloading the
12276 configuration. Fixes bug 856.
12279 - Resume using the correct "REASON=" stream when telling the
12280 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
12281 - When a canonical connection appears later in our internal list
12282 than a noncanonical one for a given OR ID, always use the
12283 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
12285 - Clip the MaxCircuitDirtiness config option to a minimum of 10
12286 seconds. Warn the user if lower values are given in the
12287 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
12288 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
12289 user if lower values are given in the configuration. Bugfix on
12290 0.1.1.17-rc. Patch by Sebastian.
12291 - Fix a race condition when freeing keys shared between main thread
12292 and CPU workers that could result in a memory leak. Bugfix on
12293 0.1.0.1-rc. Fixes bug 889.
12295 o Minor bugfixes (hidden services):
12296 - Do not throw away existing introduction points on SIGHUP (bugfix on
12297 0.0.6pre1); also, do not stall hidden services because we're
12298 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
12299 by John Brooks. Patch by Karsten. Fixes bug 874.
12300 - Fix a memory leak when we decline to add a v2 rendezvous
12301 descriptor to the cache because we already had a v0 descriptor
12302 with the same ID. Bugfix on 0.2.0.18-alpha.
12304 o Deprecated and removed features:
12305 - RedirectExits has been removed. It was deprecated since
12307 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
12308 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
12309 - Cell pools are now always enabled; --disable-cell-pools is ignored.
12311 o Code simplifications and refactoring:
12312 - Rename the confusing or_is_obsolete field to the more appropriate
12313 is_bad_for_new_circs, and move it to or_connection_t where it
12315 - Move edge-only flags from connection_t to edge_connection_t: not
12316 only is this better coding, but on machines of plausible alignment,
12317 it should save 4-8 bytes per connection_t. "Every little bit helps."
12318 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
12319 for consistency; keep old option working for backward compatibility.
12320 - Simplify the code for finding connections to use for a circuit.
12323 Changes in version 0.2.1.8-alpha - 2008-12-08
12324 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
12325 builds better on unusual platforms like Solaris and old OS X, and
12326 fixes a variety of other issues.
12329 - New DirPortFrontPage option that takes an html file and publishes
12330 it as "/" on the DirPort. Now relay operators can provide a
12331 disclaimer without needing to set up a separate webserver. There's
12332 a sample disclaimer in contrib/tor-exit-notice.html.
12335 - When the client is choosing entry guards, now it selects at most
12336 one guard from a given relay family. Otherwise we could end up with
12337 all of our entry points into the network run by the same operator.
12338 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
12341 - Fix a DOS opportunity during the voting signature collection process
12342 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
12343 - Fix a possible segfault when establishing an exit connection. Bugfix
12347 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
12349 - Made Tor a little less aggressive about deleting expired
12350 certificates. Partial fix for bug 854.
12351 - Stop doing unaligned memory access that generated bus errors on
12352 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
12353 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
12354 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
12355 - Make USR2 log-level switch take effect immediately. Bugfix on
12357 - If one win32 nameserver fails to get added, continue adding the
12358 rest, and don't automatically fail.
12359 - Use fcntl() for locking when flock() is not available. Should fix
12360 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
12361 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
12362 could make gcc generate non-functional binary search code. Bugfix
12364 - Build correctly on platforms without socklen_t.
12365 - Avoid potential crash on internal error during signature collection.
12366 Fixes bug 864. Patch from rovv.
12367 - Do not use C's stdio library for writing to log files. This will
12368 improve logging performance by a minute amount, and will stop
12369 leaking fds when our disk is full. Fixes bug 861.
12370 - Stop erroneous use of O_APPEND in cases where we did not in fact
12371 want to re-seek to the end of a file before every last write().
12372 - Correct handling of possible malformed authority signing key
12373 certificates with internal signature types. Fixes bug 880. Bugfix
12375 - Fix a hard-to-trigger resource leak when logging credential status.
12379 - Directory mirrors no longer fetch the v1 directory or
12380 running-routers files. They are obsolete, and nobody asks for them
12381 anymore. This is the first step to making v1 authorities obsolete.
12383 o Minor features (controller):
12384 - Return circuit purposes in response to GETINFO circuit-status. Fixes
12388 Changes in version 0.2.0.32 - 2008-11-20
12389 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
12390 packages (and maybe other packages) noticed by Theo de Raadt, fixes
12391 a smaller security flaw that might allow an attacker to access local
12392 services, further improves hidden service performance, and fixes a
12393 variety of other issues.
12396 - The "User" and "Group" config options did not clear the
12397 supplementary group entries for the Tor process. The "User" option
12398 is now more robust, and we now set the groups to the specified
12399 user's primary group. The "Group" option is now ignored. For more
12400 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
12401 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
12402 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
12403 - The "ClientDNSRejectInternalAddresses" config option wasn't being
12404 consistently obeyed: if an exit relay refuses a stream because its
12405 exit policy doesn't allow it, we would remember what IP address
12406 the relay said the destination address resolves to, even if it's
12407 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
12410 - Fix a DOS opportunity during the voting signature collection process
12411 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
12413 o Major bugfixes (hidden services):
12414 - When fetching v0 and v2 rendezvous service descriptors in parallel,
12415 we were failing the whole hidden service request when the v0
12416 descriptor fetch fails, even if the v2 fetch is still pending and
12417 might succeed. Similarly, if the last v2 fetch fails, we were
12418 failing the whole hidden service request even if a v0 fetch is
12419 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
12420 - When extending a circuit to a hidden service directory to upload a
12421 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
12422 requests failed, because the router descriptor has not been
12423 downloaded yet. In these cases, do not attempt to upload the
12424 rendezvous descriptor, but wait until the router descriptor is
12425 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
12426 descriptor from a hidden service directory for which the router
12427 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
12431 - Fix several infrequent memory leaks spotted by Coverity.
12432 - When testing for libevent functions, set the LDFLAGS variable
12433 correctly. Found by Riastradh.
12434 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
12435 bootstrapping with tunneled directory connections. Bugfix on
12436 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
12437 - When asked to connect to A.B.exit:80, if we don't know the IP for A
12438 and we know that server B rejects most-but-not all connections to
12439 port 80, we would previously reject the connection. Now, we assume
12440 the user knows what they were asking for. Fixes bug 752. Bugfix
12441 on 0.0.9rc5. Diagnosed by BarkerJr.
12442 - If we overrun our per-second write limits a little, count this as
12443 having used up our write allocation for the second, and choke
12444 outgoing directory writes. Previously, we had only counted this when
12445 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
12446 Bugfix on 0.2.0.x (??).
12447 - Remove the old v2 directory authority 'lefkada' from the default
12448 list. It has been gone for many months.
12449 - Stop doing unaligned memory access that generated bus errors on
12450 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
12451 - Make USR2 log-level switch take effect immediately. Bugfix on
12454 o Minor bugfixes (controller):
12455 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
12456 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
12459 Changes in version 0.2.1.7-alpha - 2008-11-08
12460 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
12461 packages (and maybe other packages) noticed by Theo de Raadt, fixes
12462 a smaller security flaw that might allow an attacker to access local
12463 services, adds better defense against DNS poisoning attacks on exit
12464 relays, further improves hidden service performance, and fixes a
12465 variety of other issues.
12468 - The "ClientDNSRejectInternalAddresses" config option wasn't being
12469 consistently obeyed: if an exit relay refuses a stream because its
12470 exit policy doesn't allow it, we would remember what IP address
12471 the relay said the destination address resolves to, even if it's
12472 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
12473 - The "User" and "Group" config options did not clear the
12474 supplementary group entries for the Tor process. The "User" option
12475 is now more robust, and we now set the groups to the specified
12476 user's primary group. The "Group" option is now ignored. For more
12477 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
12478 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
12479 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
12480 - Do not use or believe expired v3 authority certificates. Patch
12481 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
12484 - Now NodeFamily and MyFamily config options allow spaces in
12485 identity fingerprints, so it's easier to paste them in.
12486 Suggested by Lucky Green.
12487 - Implement the 0x20 hack to better resist DNS poisoning: set the
12488 case on outgoing DNS requests randomly, and reject responses that do
12489 not match the case correctly. This logic can be disabled with the
12490 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
12491 of servers that do not reliably preserve case in replies. See
12492 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
12494 - Preserve case in replies to DNSPort requests in order to support
12495 the 0x20 hack for resisting DNS poisoning attacks.
12497 o Hidden service performance improvements:
12498 - When the client launches an introduction circuit, retry with a
12499 new circuit after 30 seconds rather than 60 seconds.
12500 - Launch a second client-side introduction circuit in parallel
12501 after a delay of 15 seconds (based on work by Christian Wilms).
12502 - Hidden services start out building five intro circuits rather
12503 than three, and when the first three finish they publish a service
12504 descriptor using those. Now we publish our service descriptor much
12505 faster after restart.
12508 - Minor fix in the warning messages when you're having problems
12509 bootstrapping; also, be more forgiving of bootstrap problems when
12510 we're still making incremental progress on a given bootstrap phase.
12511 - When we're choosing an exit node for a circuit, and we have
12512 no pending streams, choose a good general exit rather than one that
12513 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
12514 - Send a valid END cell back when a client tries to connect to a
12515 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
12516 840. Patch from rovv.
12517 - If a broken client asks a non-exit router to connect somewhere,
12518 do not even do the DNS lookup before rejecting the connection.
12519 Fixes another case of bug 619. Patch from rovv.
12520 - Fix another case of assuming, when a specific exit is requested,
12521 that we know more than the user about what hosts it allows.
12522 Fixes another case of bug 752. Patch from rovv.
12523 - Check which hops rendezvous stream cells are associated with to
12524 prevent possible guess-the-streamid injection attacks from
12525 intermediate hops. Fixes another case of bug 446. Based on patch
12527 - Avoid using a negative right-shift when comparing 32-bit
12528 addresses. Possible fix for bug 845 and bug 811.
12529 - Make the assert_circuit_ok() function work correctly on circuits that
12530 have already been marked for close.
12531 - Fix read-off-the-end-of-string error in unit tests when decoding
12532 introduction points.
12533 - Fix uninitialized size field for memory area allocation: may improve
12534 memory performance during directory parsing.
12535 - Treat duplicate certificate fetches as failures, so that we do
12536 not try to re-fetch an expired certificate over and over and over.
12537 - Do not say we're fetching a certificate when we'll in fact skip it
12538 because of a pending download.
12541 Changes in version 0.2.1.6-alpha - 2008-09-30
12542 Tor 0.2.1.6-alpha further improves performance and robustness of
12543 hidden services, starts work on supporting per-country relay selection,
12544 and fixes a variety of smaller issues.
12547 - Implement proposal 121: make it possible to build hidden services
12548 that only certain clients are allowed to connect to. This is
12549 enforced at several points, so that unauthorized clients are unable
12550 to send INTRODUCE cells to the service, or even (depending on the
12551 type of authentication) to learn introduction points. This feature
12552 raises the bar for certain kinds of active attacks against hidden
12553 services. Code by Karsten Loesing.
12554 - Relays now store and serve v2 hidden service descriptors by default,
12555 i.e., the new default value for HidServDirectoryV2 is 1. This is
12556 the last step in proposal 114, which aims to make hidden service
12557 lookups more reliable.
12558 - Start work to allow node restrictions to include country codes. The
12559 syntax to exclude nodes in a country with country code XX is
12560 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
12561 refinement to decide what config options should take priority if
12562 you ask to both use a particular node and exclude it.
12563 - Allow ExitNodes list to include IP ranges and country codes, just
12564 like the Exclude*Nodes lists. Patch from Robert Hogan.
12567 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
12568 Tor to fail to start if you had it configured to use a bridge
12569 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
12570 - When extending a circuit to a hidden service directory to upload a
12571 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
12572 requests failed, because the router descriptor had not been
12573 downloaded yet. In these cases, we now wait until the router
12574 descriptor is downloaded, and then retry. Likewise, clients
12575 now skip over a hidden service directory if they don't yet have
12576 its router descriptor, rather than futilely requesting it and
12577 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
12579 - When fetching v0 and v2 rendezvous service descriptors in parallel,
12580 we were failing the whole hidden service request when the v0
12581 descriptor fetch fails, even if the v2 fetch is still pending and
12582 might succeed. Similarly, if the last v2 fetch fails, we were
12583 failing the whole hidden service request even if a v0 fetch is
12584 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
12585 - DNS replies need to have names matching their requests, but
12586 these names should be in the questions section, not necessarily
12587 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
12590 - Update to the "September 1 2008" ip-to-country file.
12591 - Allow ports 465 and 587 in the default exit policy again. We had
12592 rejected them in 0.1.0.15, because back in 2005 they were commonly
12593 misconfigured and ended up as spam targets. We hear they are better
12594 locked down these days.
12595 - Use a lockfile to make sure that two Tor processes are not
12596 simultaneously running with the same datadir.
12597 - Serve the latest v3 networkstatus consensus via the control
12598 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
12599 - Better logging about stability/reliability calculations on directory
12601 - Drop the requirement to have an open dir port for storing and
12602 serving v2 hidden service descriptors.
12603 - Directory authorities now serve a /tor/dbg-stability.txt URL to
12604 help debug WFU and MTBF calculations.
12605 - Implement most of Proposal 152: allow specialized servers to permit
12606 single-hop circuits, and clients to use those servers to build
12607 single-hop circuits when using a specialized controller. Patch
12608 from Josh Albrecht. Resolves feature request 768.
12609 - Add a -p option to tor-resolve for specifying the SOCKS port: some
12610 people find host:port too confusing.
12611 - Make TrackHostExit mappings expire a while after their last use, not
12612 after their creation. Patch from Robert Hogan.
12613 - Provide circuit purposes along with circuit events to the controller.
12616 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
12618 - Fixed some memory leaks -- some quite frequent, some almost
12619 impossible to trigger -- based on results from Coverity.
12620 - When testing for libevent functions, set the LDFLAGS variable
12621 correctly. Found by Riastradh.
12622 - Fix an assertion bug in parsing policy-related options; possible fix
12624 - Catch and report a few more bootstrapping failure cases when Tor
12625 fails to establish a TCP connection. Cleanup on 0.2.1.x.
12626 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
12627 bootstrapping with tunneled directory connections. Bugfix on
12628 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
12629 - When asked to connect to A.B.exit:80, if we don't know the IP for A
12630 and we know that server B rejects most-but-not all connections to
12631 port 80, we would previously reject the connection. Now, we assume
12632 the user knows what they were asking for. Fixes bug 752. Bugfix
12633 on 0.0.9rc5. Diagnosed by BarkerJr.
12634 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
12635 service directories if they have no advertised dir port. Bugfix
12637 - If we overrun our per-second write limits a little, count this as
12638 having used up our write allocation for the second, and choke
12639 outgoing directory writes. Previously, we had only counted this when
12640 we had met our limits precisely. Fixes bug 824. Patch by rovv.
12641 Bugfix on 0.2.0.x (??).
12642 - Avoid a "0 divided by 0" calculation when calculating router uptime
12643 at directory authorities. Bugfix on 0.2.0.8-alpha.
12644 - Make DNS resolved controller events into "CLOSED", not
12645 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
12647 - Fix a bug where an unreachable relay would establish enough
12648 reachability testing circuits to do a bandwidth test -- if
12649 we already have a connection to the middle hop of the testing
12650 circuit, then it could establish the last hop by using the existing
12651 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
12652 circuits no longer use entry guards in 0.2.1.3-alpha.
12653 - If we have correct permissions on $datadir, we complain to stdout
12654 and fail to start. But dangerous permissions on
12655 $datadir/cached-status/ would cause us to open a log and complain
12656 there. Now complain to stdout and fail to start in both cases. Fixes
12657 bug 820, reported by seeess.
12658 - Remove the old v2 directory authority 'lefkada' from the default
12659 list. It has been gone for many months.
12661 o Code simplifications and refactoring:
12662 - Revise the connection_new functions so that a more typesafe variant
12663 exists. This will work better with Coverity, and let us find any
12664 actual mistakes we're making here.
12665 - Refactor unit testing logic so that dmalloc can be used sensibly
12666 with unit tests to check for memory leaks.
12667 - Move all hidden-service related fields from connection and circuit
12668 structure to substructures: this way they won't eat so much memory.
12671 Changes in version 0.2.0.31 - 2008-09-03
12672 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
12673 a big bug we're seeing where in rare cases traffic from one Tor stream
12674 gets mixed into another stream, and fixes a variety of smaller issues.
12677 - Make sure that two circuits can never exist on the same connection
12678 with the same circuit ID, even if one is marked for close. This
12679 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
12680 - Relays now reject risky extend cells: if the extend cell includes
12681 a digest of all zeroes, or asks to extend back to the relay that
12682 sent the extend cell, tear down the circuit. Ideas suggested
12684 - If not enough of our entry guards are available so we add a new
12685 one, we might use the new one even if it overlapped with the
12686 current circuit's exit relay (or its family). Anonymity bugfix
12687 pointed out by rovv.
12690 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
12691 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
12692 - Correctly detect the presence of the linux/netfilter_ipv4.h header
12693 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
12694 - Pick size of default geoip filename string correctly on windows.
12695 Fixes bug 806. Bugfix on 0.2.0.30.
12696 - Make the autoconf script accept the obsolete --with-ssl-dir
12697 option as an alias for the actually-working --with-openssl-dir
12698 option. Fix the help documentation to recommend --with-openssl-dir.
12699 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
12700 - When using the TransPort option on OpenBSD, and using the User
12701 option to change UID and drop privileges, make sure to open
12702 /dev/pf before dropping privileges. Fixes bug 782. Patch from
12703 Christopher Davis. Bugfix on 0.1.2.1-alpha.
12704 - Try to attach connections immediately upon receiving a RENDEZVOUS2
12705 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
12706 on the client side when connecting to a hidden service. Bugfix
12707 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
12708 - When closing an application-side connection because its circuit is
12709 getting torn down, generate the stream event correctly. Bugfix on
12710 0.1.2.x. Anonymous patch.
12713 Changes in version 0.2.1.5-alpha - 2008-08-31
12714 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
12715 in a lot of the infrastructure for adding authorization to hidden
12716 services, lays the groundwork for having clients read their load
12717 balancing information out of the networkstatus consensus rather than
12718 the individual router descriptors, addresses two potential anonymity
12719 issues, and fixes a variety of smaller issues.
12722 - Convert many internal address representations to optionally hold
12724 - Generate and accept IPv6 addresses in many protocol elements.
12725 - Make resolver code handle nameservers located at ipv6 addresses.
12726 - Begin implementation of proposal 121 ("Client authorization for
12727 hidden services"): configure hidden services with client
12728 authorization, publish descriptors for them, and configure
12729 authorization data for hidden services at clients. The next
12730 step is to actually access hidden services that perform client
12732 - More progress toward proposal 141: Network status consensus
12733 documents and votes now contain bandwidth information for each
12734 router and a summary of that router's exit policy. Eventually this
12735 will be used by clients so that they do not have to download every
12736 known descriptor before building circuits.
12738 o Major bugfixes (on 0.2.0.x and before):
12739 - When sending CREATED cells back for a given circuit, use a 64-bit
12740 connection ID to find the right connection, rather than an addr:port
12741 combination. Now that we can have multiple OR connections between
12742 the same ORs, it is no longer possible to use addr:port to uniquely
12743 identify a connection.
12744 - Relays now reject risky extend cells: if the extend cell includes
12745 a digest of all zeroes, or asks to extend back to the relay that
12746 sent the extend cell, tear down the circuit. Ideas suggested
12748 - If not enough of our entry guards are available so we add a new
12749 one, we might use the new one even if it overlapped with the
12750 current circuit's exit relay (or its family). Anonymity bugfix
12751 pointed out by rovv.
12754 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
12755 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
12756 - When using the TransPort option on OpenBSD, and using the User
12757 option to change UID and drop privileges, make sure to open /dev/pf
12758 before dropping privileges. Fixes bug 782. Patch from Christopher
12759 Davis. Bugfix on 0.1.2.1-alpha.
12760 - Correctly detect the presence of the linux/netfilter_ipv4.h header
12761 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
12762 - Add a missing safe_str() call for a debug log message.
12763 - Use 64 bits instead of 32 bits for connection identifiers used with
12764 the controller protocol, to greatly reduce risk of identifier reuse.
12765 - Make the autoconf script accept the obsolete --with-ssl-dir
12766 option as an alias for the actually-working --with-openssl-dir
12767 option. Fix the help documentation to recommend --with-openssl-dir.
12768 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
12771 - Rate-limit too-many-sockets messages: when they happen, they happen
12772 a lot. Resolves bug 748.
12773 - Resist DNS poisoning a little better by making sure that names in
12774 answer sections match.
12775 - Print the SOCKS5 error message string as well as the error code
12776 when a tor-resolve request fails. Patch from Jacob.
12779 Changes in version 0.2.1.4-alpha - 2008-08-04
12780 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
12783 - The address part of exit policies was not correctly written
12784 to router descriptors. This generated router descriptors that failed
12785 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
12787 - Tor triggered a false assert when extending a circuit to a relay
12788 but we already have a connection open to that relay. Noticed by
12789 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
12792 - Fix a hidden service logging bug: in some edge cases, the router
12793 descriptor of a previously picked introduction point becomes
12794 obsolete and we need to give up on it rather than continually
12795 complaining that it has become obsolete. Observed by xiando. Bugfix
12798 o Removed features:
12799 - Take out the TestVia config option, since it was a workaround for
12800 a bug that was fixed in Tor 0.1.1.21.
12803 Changes in version 0.2.1.3-alpha - 2008-08-03
12804 Tor 0.2.1.3-alpha implements most of the pieces to prevent
12805 infinite-length circuit attacks (see proposal 110); fixes a bug that
12806 might cause exit relays to corrupt streams they send back; allows
12807 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
12808 ExcludeExitNodes config options; and fixes a big pile of bugs.
12810 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
12811 - Send a bootstrap problem "warn" event on the first problem if the
12812 reason is NO_ROUTE (that is, our network is down).
12815 - Implement most of proposal 110: The first K cells to be sent
12816 along a circuit are marked as special "early" cells; only K "early"
12817 cells will be allowed. Once this code is universal, we can block
12818 certain kinds of DOS attack by requiring that EXTEND commands must
12819 be sent using an "early" cell.
12822 - Try to attach connections immediately upon receiving a RENDEZVOUS2
12823 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
12824 on the client side when connecting to a hidden service. Bugfix
12825 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
12826 - Ensure that two circuits can never exist on the same connection
12827 with the same circuit ID, even if one is marked for close. This
12828 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
12831 - When relays do their initial bandwidth measurement, don't limit
12832 to just our entry guards for the test circuits. Otherwise we tend
12833 to have multiple test circuits going through a single entry guard,
12834 which makes our bandwidth test less accurate. Fixes part of bug 654;
12835 patch contributed by Josh Albrecht.
12836 - Add an ExcludeExitNodes option so users can list a set of nodes
12837 that should be be excluded from the exit node position, but
12838 allowed elsewhere. Implements proposal 151.
12839 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
12840 ExcludeNodes and ExcludeExitNodes lists.
12841 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
12842 be more efficient. Formerly it was quadratic in the number of
12843 servers; now it should be linear. Fixes bug 509.
12844 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
12845 and n_conn_id_digest fields into a separate structure that's
12846 only needed when the circuit has not yet attached to an n_conn.
12849 - Change the contrib/tor.logrotate script so it makes the new
12850 logs as "_tor:_tor" rather than the default, which is generally
12851 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
12852 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
12853 warnings (occasionally), but it can also cause the compiler to
12854 eliminate error-checking code. Suggested by Peter Gutmann.
12855 - When a hidden service is giving up on an introduction point candidate
12856 that was not included in the last published rendezvous descriptor,
12857 don't reschedule publication of the next descriptor. Fixes bug 763.
12859 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
12860 HiddenServiceExcludeNodes as obsolete: they never worked properly,
12861 and nobody claims to be using them. Fixes bug 754. Bugfix on
12862 0.1.0.1-rc. Patch from Christian Wilms.
12863 - Fix a small alignment and memory-wasting bug on buffer chunks.
12866 o Minor bugfixes (controller):
12867 - When closing an application-side connection because its circuit
12868 is getting torn down, generate the stream event correctly.
12869 Bugfix on 0.1.2.x. Anonymous patch.
12871 o Removed features:
12872 - Remove all backward-compatibility code to support relays running
12873 versions of Tor so old that they no longer work at all on the
12877 Changes in version 0.2.0.30 - 2008-07-15
12879 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
12880 warnings (occasionally), but it can also cause the compiler to
12881 eliminate error-checking code. Suggested by Peter Gutmann.
12884 Changes in version 0.2.0.29-rc - 2008-07-08
12885 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
12886 hidden-service performance bugs, and fixes a bunch of smaller bugs.
12889 - If you have more than one bridge but don't know their keys,
12890 you would only launch a request for the descriptor of the first one
12891 on your list. (Tor considered launching requests for the others, but
12892 found that it already had a connection on the way for $0000...0000
12893 so it didn't open another.) Bugfix on 0.2.0.x.
12894 - If you have more than one bridge but don't know their keys, and the
12895 connection to one of the bridges failed, you would cancel all
12896 pending bridge connections. (After all, they all have the same
12897 digest.) Bugfix on 0.2.0.x.
12898 - When a hidden service was trying to establish an introduction point,
12899 and Tor had built circuits preemptively for such purposes, we
12900 were ignoring all the preemptive circuits and launching a new one
12901 instead. Bugfix on 0.2.0.14-alpha.
12902 - When a hidden service was trying to establish an introduction point,
12903 and Tor *did* manage to reuse one of the preemptively built
12904 circuits, it didn't correctly remember which one it used,
12905 so it asked for another one soon after, until there were no
12906 more preemptive circuits, at which point it launched one from
12907 scratch. Bugfix on 0.0.9.x.
12908 - Make directory servers include the X-Your-Address-Is: http header in
12909 their responses even for begin_dir conns. Now clients who only
12910 ever use begin_dir connections still have a way to learn their IP
12911 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
12914 - Fix a macro/CPP interaction that was confusing some compilers:
12915 some GCCs don't like #if/#endif pairs inside macro arguments.
12917 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
12918 Fixes bug 704; fix from Steven Murdoch.
12919 - When opening /dev/null in finish_daemonize(), do not pass the
12920 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
12921 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
12922 - Correctly detect transparent proxy support on Linux hosts that
12923 require in.h to be included before netfilter_ipv4.h. Patch
12925 - Disallow session resumption attempts during the renegotiation
12926 stage of the v2 handshake protocol. Clients should never be trying
12927 session resumption at this point, but apparently some did, in
12928 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
12929 found by Geoff Goodell.
12932 Changes in version 0.2.1.2-alpha - 2008-06-20
12933 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
12934 make it easier to set up your own private Tor network; fixes several
12935 big bugs with using more than one bridge relay; fixes a big bug with
12936 offering hidden services quickly after Tor starts; and uses a better
12937 API for reporting potential bootstrapping problems to the controller.
12940 - New TestingTorNetwork config option to allow adjustment of
12941 previously constant values that, while reasonable, could slow
12942 bootstrapping. Implements proposal 135. Patch from Karsten.
12945 - If you have more than one bridge but don't know their digests,
12946 you would only learn a request for the descriptor of the first one
12947 on your list. (Tor considered launching requests for the others, but
12948 found that it already had a connection on the way for $0000...0000
12949 so it didn't open another.) Bugfix on 0.2.0.x.
12950 - If you have more than one bridge but don't know their digests,
12951 and the connection to one of the bridges failed, you would cancel
12952 all pending bridge connections. (After all, they all have the
12953 same digest.) Bugfix on 0.2.0.x.
12954 - When establishing a hidden service, introduction points that
12955 originate from cannibalized circuits are completely ignored and not
12956 included in rendezvous service descriptors. This might be another
12957 reason for delay in making a hidden service available. Bugfix
12958 from long ago (0.0.9.x?)
12961 - Allow OpenSSL to use dynamic locks if it wants.
12962 - When building a consensus, do not include routers that are down.
12963 This will cut down 30% to 40% on consensus size. Implements
12965 - In directory authorities' approved-routers files, allow
12966 fingerprints with or without space.
12967 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
12968 controller can query our current bootstrap state in case it attaches
12969 partway through and wants to catch up.
12970 - Send an initial "Starting" bootstrap status event, so we have a
12971 state to start out in.
12974 - Asking for a conditional consensus at .../consensus/<fingerprints>
12975 would crash a dirserver if it did not already have a
12976 consensus. Bugfix on 0.2.1.1-alpha.
12977 - Clean up some macro/CPP interactions: some GCC versions don't like
12978 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
12981 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
12982 - Directory authorities shouldn't complain about bootstrapping
12983 problems just because they do a lot of reachability testing and
12984 some of the connection attempts fail.
12985 - Start sending "count" and "recommendation" key/value pairs in
12986 bootstrap problem status events, so the controller can hear about
12987 problems even before Tor decides they're worth reporting for sure.
12988 - If you're using bridges, generate "bootstrap problem" warnings
12989 as soon as you run out of working bridges, rather than waiting
12990 for ten failures -- which will never happen if you have less than
12992 - If we close our OR connection because there's been a circuit
12993 pending on it for too long, we were telling our bootstrap status
12994 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
12997 Changes in version 0.2.1.1-alpha - 2008-06-13
12998 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
12999 were making the Tor process bloat especially on Linux; makes our TLS
13000 handshake blend in better; sends "bootstrap phase" status events to
13001 the controller, so it can keep the user informed of progress (and
13002 problems) fetching directory information and establishing circuits;
13003 and adds a variety of smaller features.
13006 - More work on making our TLS handshake blend in: modify the list
13007 of ciphers advertised by OpenSSL in client mode to even more
13008 closely resemble a common web browser. We cheat a little so that
13009 we can advertise ciphers that the locally installed OpenSSL doesn't
13011 - Start sending "bootstrap phase" status events to the controller,
13012 so it can keep the user informed of progress fetching directory
13013 information and establishing circuits. Also inform the controller
13014 if we think we're stuck at a particular bootstrap phase. Implements
13016 - Resume using OpenSSL's RAND_poll() for better (and more portable)
13017 cross-platform entropy collection again. We used to use it, then
13018 stopped using it because of a bug that could crash systems that
13019 called RAND_poll when they had a lot of fds open. It looks like the
13020 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
13021 at startup, and to call RAND_poll() when we reseed later only if
13022 we have a non-buggy OpenSSL version.
13025 - When we choose to abandon a new entry guard because we think our
13026 older ones might be better, close any circuits pending on that
13027 new entry guard connection. This fix should make us recover much
13028 faster when our network is down and then comes back. Bugfix on
13029 0.1.2.8-beta; found by lodger.
13031 o Memory fixes and improvements:
13032 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
13033 to avoid unused RAM in buffer chunks and memory pools.
13034 - Speed up parsing and cut down on memory fragmentation by using
13035 stack-style allocations for parsing directory objects. Previously,
13036 this accounted for over 40% of allocations from within Tor's code
13037 on a typical directory cache.
13038 - Use a Bloom filter rather than a digest-based set to track which
13039 descriptors we need to keep around when we're cleaning out old
13040 router descriptors. This speeds up the computation significantly,
13041 and may reduce fragmentation.
13042 - Reduce the default smartlist size from 32 to 16; it turns out that
13043 most smartlists hold around 8-12 elements tops.
13044 - Make dumpstats() log the fullness and size of openssl-internal
13046 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
13047 patch to their OpenSSL, turn it on to save memory on servers. This
13048 patch will (with any luck) get included in a mainline distribution
13050 - Never use OpenSSL compression: it wastes RAM and CPU trying to
13051 compress cells, which are basically all encrypted, compressed,
13055 - Stop reloading the router list from disk for no reason when we
13056 run out of reachable directory mirrors. Once upon a time reloading
13057 it would set the 'is_running' flag back to 1 for them. It hasn't
13058 done that for a long time.
13059 - In very rare situations new hidden service descriptors were
13060 published earlier than 30 seconds after the last change to the
13061 service. (We currently think that a hidden service descriptor
13062 that's been stable for 30 seconds is worth publishing.)
13065 - Allow separate log levels to be configured for different logging
13066 domains. For example, this allows one to log all notices, warnings,
13067 or errors, plus all memory management messages of level debug or
13068 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
13069 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
13070 and stop using a warning that had become unfixably verbose under
13072 - New --hush command-line option similar to --quiet. While --quiet
13073 disables all logging to the console on startup, --hush limits the
13074 output to messages of warning and error severity.
13075 - Servers support a new URL scheme for consensus downloads that
13076 allows the client to specify which authorities are trusted.
13077 The server then only sends the consensus if the client will trust
13078 it. Otherwise a 404 error is sent back. Clients use this
13079 new scheme when the server supports it (meaning it's running
13080 0.2.1.1-alpha or later). Implements proposal 134.
13081 - New configure/torrc options (--enable-geoip-stats,
13082 DirRecordUsageByCountry) to record how many IPs we've served
13083 directory info to in each country code, how many status documents
13084 total we've sent to each country code, and what share of the total
13085 directory requests we should expect to see.
13086 - Use the TLS1 hostname extension to more closely resemble browser
13088 - Lots of new unit tests.
13089 - Add a macro to implement the common pattern of iterating through
13090 two parallel lists in lockstep.
13093 Changes in version 0.2.0.28-rc - 2008-06-13
13094 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
13095 performance bug, and fixes a bunch of smaller bugs.
13098 - Fix a bug where, when we were choosing the 'end stream reason' to
13099 put in our relay end cell that we send to the exit relay, Tor
13100 clients on Windows were sometimes sending the wrong 'reason'. The
13101 anonymity problem is that exit relays may be able to guess whether
13102 the client is running Windows, thus helping partition the anonymity
13103 set. Down the road we should stop sending reasons to exit relays,
13104 or otherwise prevent future versions of this bug.
13107 - While setting up a hidden service, some valid introduction circuits
13108 were overlooked and abandoned. This might be the reason for
13109 the long delay in making a hidden service available. Bugfix on
13113 - Update to the "June 9 2008" ip-to-country file.
13114 - Run 'make test' as part of 'make dist', so we stop releasing so
13115 many development snapshots that fail their unit tests.
13118 - When we're checking if we have enough dir info for each relay
13119 to begin establishing circuits, make sure that we actually have
13120 the descriptor listed in the consensus, not just any descriptor.
13122 - Bridge relays no longer print "xx=0" in their extrainfo document
13123 for every single country code in the geoip db. Bugfix on
13125 - Only warn when we fail to load the geoip file if we were planning to
13126 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
13127 - If we change our MaxAdvertisedBandwidth and then reload torrc,
13128 Tor won't realize it should publish a new relay descriptor. Fixes
13129 bug 688, reported by mfr. Bugfix on 0.1.2.x.
13130 - When we haven't had any application requests lately, don't bother
13131 logging that we have expired a bunch of descriptors. Bugfix
13133 - Make relay cells written on a connection count as non-padding when
13134 tracking how long a connection has been in use. Bugfix on
13135 0.2.0.1-alpha. Spotted by lodger.
13136 - Fix unit tests in 0.2.0.27-rc.
13137 - Fix compile on Windows.
13140 Changes in version 0.2.0.27-rc - 2008-06-03
13141 Tor 0.2.0.27-rc adds a few features we left out of the earlier
13142 release candidates. In particular, we now include an IP-to-country
13143 GeoIP database, so controllers can easily look up what country a
13144 given relay is in, and so bridge relays can give us some sanitized
13145 summaries about which countries are making use of bridges. (See proposal
13146 126-geoip-fetching.txt for details.)
13149 - Include an IP-to-country GeoIP file in the tarball, so bridge
13150 relays can report sanitized summaries of the usage they're seeing.
13153 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
13154 Robert Hogan. Fixes the first part of bug 681.
13155 - Make bridge authorities never serve extrainfo docs.
13156 - Add support to detect Libevent versions in the 1.4.x series
13158 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
13159 - Include a new contrib/tor-exit-notice.html file that exit relay
13160 operators can put on their website to help reduce abuse queries.
13163 - When tunneling an encrypted directory connection, and its first
13164 circuit fails, do not leave it unattached and ask the controller
13165 to deal. Fixes the second part of bug 681.
13166 - Make bridge authorities correctly expire old extrainfo documents
13170 Changes in version 0.2.0.26-rc - 2008-05-13
13171 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
13172 in Debian's OpenSSL packages. All users running any 0.2.0.x version
13173 should upgrade, whether they're running Debian or not.
13175 o Major security fixes:
13176 - Use new V3 directory authority keys on the tor26, gabelmoo, and
13177 moria1 V3 directory authorities. The old keys were generated with
13178 a vulnerable version of Debian's OpenSSL package, and must be
13179 considered compromised. Other authorities' keys were not generated
13180 with an affected version of OpenSSL.
13183 - List authority signatures as "unrecognized" based on DirServer
13184 lines, not on cert cache. Bugfix on 0.2.0.x.
13187 - Add a new V3AuthUseLegacyKey option to make it easier for
13188 authorities to change their identity keys if they have to.
13191 Changes in version 0.2.0.25-rc - 2008-04-23
13192 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
13195 - Remember to initialize threading before initializing logging.
13196 Otherwise, many BSD-family implementations will crash hard on
13197 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
13200 - Authorities correctly free policies on bad servers on
13201 exit. Fixes bug 672. Bugfix on 0.2.0.x.
13204 Changes in version 0.2.0.24-rc - 2008-04-22
13205 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
13206 v3 directory authority, makes relays with dynamic IP addresses and no
13207 DirPort notice more quickly when their IP address changes, fixes a few
13208 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
13210 o New directory authorities:
13211 - Take lefkada out of the list of v3 directory authorities, since
13212 it has been down for months.
13213 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
13217 - Detect address changes more quickly on non-directory mirror
13218 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
13220 o Minor features (security):
13221 - Reject requests for reverse-dns lookup of names that are in
13222 a private address space. Patch from lodger.
13223 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
13226 o Minor bugfixes (crashes):
13227 - Avoid a rare assert that can trigger when Tor doesn't have much
13228 directory information yet and it tries to fetch a v2 hidden
13229 service descriptor. Fixes bug 651, reported by nwf.
13230 - Initialize log mutex before initializing dmalloc. Otherwise,
13231 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
13232 - Use recursive pthread mutexes in order to avoid deadlock when
13233 logging debug-level messages to a controller. Bug spotted by nwf,
13234 bugfix on 0.2.0.16-alpha.
13236 o Minor bugfixes (resource management):
13237 - Keep address policies from leaking memory: start their refcount
13238 at 1, not 2. Bugfix on 0.2.0.16-alpha.
13239 - Free authority certificates on exit, so they don't look like memory
13240 leaks. Bugfix on 0.2.0.19-alpha.
13241 - Free static hashtables for policy maps and for TLS connections on
13242 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
13243 - Avoid allocating extra space when computing consensuses on 64-bit
13244 platforms. Bug spotted by aakova.
13246 o Minor bugfixes (misc):
13247 - Do not read the configuration file when we've only been told to
13248 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
13249 based on patch from Sebastian Hahn.
13250 - Exit relays that are used as a client can now reach themselves
13251 using the .exit notation, rather than just launching an infinite
13252 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
13253 - When attempting to open a logfile fails, tell us why.
13254 - Fix a dumb bug that was preventing us from knowing that we should
13255 preemptively build circuits to handle expected directory requests.
13256 Fixes bug 660. Bugfix on 0.1.2.x.
13257 - Warn less verbosely about clock skew from netinfo cells from
13258 untrusted sources. Fixes bug 663.
13259 - Make controller stream events for DNS requests more consistent,
13260 by adding "new stream" events for DNS requests, and removing
13261 spurious "stream closed" events" for cached reverse resolves.
13262 Patch from mwenge. Fixes bug 646.
13263 - Correctly notify one-hop connections when a circuit build has
13264 failed. Possible fix for bug 669. Found by lodger.
13267 Changes in version 0.2.0.23-rc - 2008-03-24
13268 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
13269 makes bootstrapping faster if the first directory mirror you contact
13270 is down. The bundles also include the new Vidalia 0.1.2 release.
13273 - When a tunneled directory request is made to a directory server
13274 that's down, notice after 30 seconds rather than 120 seconds. Also,
13275 fail any begindir streams that are pending on it, so they can
13276 retry elsewhere. This was causing multi-minute delays on bootstrap.
13279 Changes in version 0.2.0.22-rc - 2008-03-18
13280 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
13281 enables encrypted directory connections by default for non-relays, fixes
13282 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
13283 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
13286 - Enable encrypted directory connections by default for non-relays,
13287 so censor tools that block Tor directory connections based on their
13288 plaintext patterns will no longer work. This means Tor works in
13289 certain censored countries by default again.
13292 - Make sure servers always request certificates from clients during
13293 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
13294 - Do not enter a CPU-eating loop when a connection is closed in
13295 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
13296 diagnosed by lodger; bugfix on 0.2.0.20-rc.
13297 - Fix assertion failure that could occur when a blocked circuit
13298 became unblocked, and it had pending client DNS requests. Bugfix
13299 on 0.2.0.1-alpha. Fixes bug 632.
13301 o Minor bugfixes (on 0.1.2.x):
13302 - Generate "STATUS_SERVER" events rather than misspelled
13303 "STATUS_SEVER" events. Caught by mwenge.
13304 - When counting the number of bytes written on a TLS connection,
13305 look at the BIO actually used for writing to the network, not
13306 at the BIO used (sometimes) to buffer data for the network.
13307 Looking at different BIOs could result in write counts on the
13308 order of ULONG_MAX. Fixes bug 614.
13309 - On Windows, correctly detect errors when listing the contents of
13310 a directory. Fix from lodger.
13312 o Minor bugfixes (on 0.2.0.x):
13313 - Downgrade "sslv3 alert handshake failure" message to INFO.
13314 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
13315 left BandwidthRate and BandwidthBurst at the default, we would be
13316 silently limited by those defaults. Now raise them to match the
13317 RelayBandwidth* values.
13318 - Fix the SVK version detection logic to work correctly on a branch.
13319 - Make --enable-openbsd-malloc work correctly on Linux with alpha
13320 CPUs. Fixes bug 625.
13321 - Logging functions now check that the passed severity is sane.
13322 - Use proper log levels in the testsuite call of
13323 get_interface_address6().
13324 - When using a nonstandard malloc, do not use the platform values for
13325 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
13326 - Make the openbsd malloc code use 8k pages on alpha CPUs and
13328 - Detect mismatched page sizes when using --enable-openbsd-malloc.
13329 - Avoid double-marked-for-close warning when certain kinds of invalid
13330 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
13331 for bug 617. Bugfix on 0.2.0.1-alpha.
13332 - Make sure that the "NULL-means-reject *:*" convention is followed by
13333 all the policy manipulation functions, avoiding some possible crash
13334 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
13335 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
13336 actually works, and doesn't warn about every single reverse lookup.
13337 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
13340 - Only log guard node status when guard node status has changed.
13341 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
13342 make "INFO" 75% less verbose.
13345 Changes in version 0.2.0.21-rc - 2008-03-02
13346 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
13347 makes Tor work well with Vidalia again, fixes a rare assert bug,
13348 and fixes a pair of more minor bugs. The bundles also include Vidalia
13349 0.1.0 and Torbutton 1.1.16.
13352 - The control port should declare that it requires password auth
13353 when HashedControlSessionPassword is set too. Patch from Matt Edman;
13354 bugfix on 0.2.0.20-rc. Fixes bug 615.
13355 - Downgrade assert in connection_buckets_decrement() to a log message.
13356 This may help us solve bug 614, and in any case will make its
13357 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
13358 - We were sometimes miscounting the number of bytes read from the
13359 network, causing our rate limiting to not be followed exactly.
13360 Bugfix on 0.2.0.16-alpha. Reported by lodger.
13363 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
13364 OpenSSL versions should have been working fine. Diagnosis and patch
13365 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
13366 Bugfix on 0.2.0.20-rc.
13369 Changes in version 0.2.0.20-rc - 2008-02-24
13370 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
13371 makes more progress towards normalizing Tor's TLS handshake, makes
13372 hidden services work better again, helps relays bootstrap if they don't
13373 know their IP address, adds optional support for linking in openbsd's
13374 allocator or tcmalloc, allows really fast relays to scale past 15000
13375 sockets, and fixes a bunch of minor bugs reported by Veracode.
13378 - Enable the revised TLS handshake based on the one designed by
13379 Steven Murdoch in proposal 124, as revised in proposal 130. It
13380 includes version negotiation for OR connections as described in
13381 proposal 105. The new handshake is meant to be harder for censors
13382 to fingerprint, and it adds the ability to detect certain kinds of
13383 man-in-the-middle traffic analysis attacks. The version negotiation
13384 feature will allow us to improve Tor's link protocol more safely
13386 - Choose which bridge to use proportional to its advertised bandwidth,
13387 rather than uniformly at random. This should speed up Tor for
13388 bridge users. Also do this for people who set StrictEntryNodes.
13389 - When a TrackHostExits-chosen exit fails too many times in a row,
13390 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
13393 - Resolved problems with (re-)fetching hidden service descriptors.
13394 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
13395 and 0.2.0.19-alpha.
13396 - If we only ever used Tor for hidden service lookups or posts, we
13397 would stop building circuits and start refusing connections after
13398 24 hours, since we falsely believed that Tor was dormant. Reported
13399 by nwf; bugfix on 0.1.2.x.
13400 - Servers that don't know their own IP address should go to the
13401 authorities for their first directory fetch, even if their DirPort
13402 is off or if they don't know they're reachable yet. This will help
13403 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
13404 - When counting the number of open sockets, count not only the number
13405 of sockets we have received from the socket() call, but also
13406 the number we've gotten from accept() and socketpair(). This bug
13407 made us fail to count all sockets that we were using for incoming
13408 connections. Bugfix on 0.2.0.x.
13409 - Fix code used to find strings within buffers, when those strings
13410 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
13411 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
13412 - Add a new __HashedControlSessionPassword option for controllers
13413 to use for one-off session password hashes that shouldn't get
13414 saved to disk by SAVECONF --- Vidalia users were accumulating a
13415 pile of HashedControlPassword lines in their torrc files, one for
13416 each time they had restarted Tor and then clicked Save. Make Tor
13417 automatically convert "HashedControlPassword" to this new option but
13418 only when it's given on the command line. Partial fix for bug 586.
13420 o Minor features (performance):
13421 - Tune parameters for cell pool allocation to minimize amount of
13423 - Add OpenBSD malloc code from phk as an optional malloc
13424 replacement on Linux: some glibc libraries do very poorly
13425 with Tor's memory allocation patterns. Pass
13426 --enable-openbsd-malloc to get the replacement malloc code.
13427 - Add a --with-tcmalloc option to the configure script to link
13428 against tcmalloc (if present). Does not yet search for
13429 non-system include paths.
13430 - Stop imposing an arbitrary maximum on the number of file descriptors
13431 used for busy servers. Bug reported by Olaf Selke; patch from
13434 o Minor features (other):
13435 - When SafeLogging is disabled, log addresses along with all TLS
13437 - When building with --enable-gcc-warnings, check for whether Apple's
13438 warning "-Wshorten-64-to-32" is available.
13439 - Add a --passphrase-fd argument to the tor-gencert command for
13442 o Minor bugfixes (memory leaks and code problems):
13443 - We were leaking a file descriptor if Tor started with a zero-length
13444 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
13445 - Detect size overflow in zlib code. Reported by Justin Ferguson and
13447 - We were comparing the raw BridgePassword entry with a base64'ed
13448 version of it, when handling a "/tor/networkstatus-bridges"
13449 directory request. Now compare correctly. Noticed by Veracode.
13450 - Recover from bad tracked-since value in MTBF-history file.
13451 Should fix bug 537.
13452 - Alter the code that tries to recover from unhandled write
13453 errors, to not try to flush onto a socket that's given us
13454 unhandled errors. Bugfix on 0.1.2.x.
13455 - Make Unix controlsockets work correctly on OpenBSD. Patch from
13456 tup. Bugfix on 0.2.0.3-alpha.
13458 o Minor bugfixes (other):
13459 - If we have an extra-info document for our server, always make
13460 it available on the control port, even if we haven't gotten
13461 a copy of it from an authority yet. Patch from mwenge.
13462 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
13463 - Directory mirrors no longer include a guess at the client's IP
13464 address if the connection appears to be coming from the same /24
13465 network; it was producing too many wrong guesses.
13466 - Make the new hidden service code respect the SafeLogging setting.
13467 Bugfix on 0.2.0.x. Patch from Karsten.
13468 - When starting as an authority, do not overwrite all certificates
13469 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
13470 - If we're trying to flush the last bytes on a connection (for
13471 example, when answering a directory request), reset the
13472 time-to-give-up timeout every time we manage to write something
13473 on the socket. Bugfix on 0.1.2.x.
13474 - Change the behavior of "getinfo status/good-server-descriptor"
13475 so it doesn't return failure when any authority disappears.
13476 - Even though the man page said that "TrackHostExits ." should
13477 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
13478 - Report TLS "zero return" case as a "clean close" and "IO error"
13479 as a "close". Stop calling closes "unexpected closes": existing
13480 Tors don't use SSL_close(), so having a connection close without
13481 the TLS shutdown handshake is hardly unexpected.
13482 - Send NAMESERVER_STATUS messages for a single failed nameserver
13485 o Code simplifications and refactoring:
13486 - Remove the tor_strpartition function: its logic was confused,
13487 and it was only used for one thing that could be implemented far
13491 Changes in version 0.2.0.19-alpha - 2008-02-09
13492 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
13493 handshake, makes path selection for relays more secure and IP address
13494 guessing more robust, and generally fixes a lot of bugs in preparation
13495 for calling the 0.2.0 branch stable.
13498 - Do not include recognizeable strings in the commonname part of
13499 Tor's x509 certificates.
13502 - If we're a relay, avoid picking ourselves as an introduction point,
13503 a rendezvous point, or as the final hop for internal circuits. Bug
13504 reported by taranis and lodger. Bugfix on 0.1.2.x.
13505 - Patch from "Andrew S. Lists" to catch when we contact a directory
13506 mirror at IP address X and he says we look like we're coming from
13507 IP address X. Bugfix on 0.1.2.x.
13509 o Minor features (security):
13510 - Be more paranoid about overwriting sensitive memory on free(),
13511 as a defensive programming tactic to ensure forward secrecy.
13513 o Minor features (directory authority):
13514 - Actually validate the options passed to AuthDirReject,
13515 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
13516 - Reject router descriptors with out-of-range bandwidthcapacity or
13517 bandwidthburst values.
13519 o Minor features (controller):
13520 - Reject controller commands over 1MB in length. This keeps rogue
13521 processes from running us out of memory.
13523 o Minor features (misc):
13524 - Give more descriptive well-formedness errors for out-of-range
13525 hidden service descriptor/protocol versions.
13526 - Make memory debugging information describe more about history
13527 of cell allocation, so we can help reduce our memory use.
13529 o Deprecated features (controller):
13530 - The status/version/num-versioning and status/version/num-concurring
13531 GETINFO options are no longer useful in the v3 directory protocol:
13532 treat them as deprecated, and warn when they're used.
13535 - When our consensus networkstatus has been expired for a while, stop
13536 being willing to build circuits using it. Fixes bug 401. Bugfix
13538 - Directory caches now fetch certificates from all authorities
13539 listed in a networkstatus consensus, even when they do not
13540 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
13541 - When connecting to a bridge without specifying its key, insert
13542 the connection into the identity-to-connection map as soon as
13543 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
13544 - Detect versions of OS X where malloc_good_size() is present in the
13545 library but never actually declared. Resolves bug 587. Bugfix
13547 - Stop incorrectly truncating zlib responses to directory authority
13548 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
13549 - Stop recommending that every server operator send mail to tor-ops.
13550 Resolves bug 597. Bugfix on 0.1.2.x.
13551 - Don't trigger an assert if we start a directory authority with a
13552 private IP address (like 127.0.0.1).
13553 - Avoid possible failures when generating a directory with routers
13554 with over-long versions strings, or too many flags set. Bugfix
13556 - If an attempt to launch a DNS resolve request over the control
13557 port fails because we have overrun the limit on the number of
13558 connections, tell the controller that the request has failed.
13559 - Avoid using too little bandwidth when our clock skips a few
13560 seconds. Bugfix on 0.1.2.x.
13561 - Fix shell error when warning about missing packages in configure
13562 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
13563 - Do not become confused when receiving a spurious VERSIONS-like
13564 cell from a confused v1 client. Bugfix on 0.2.0.x.
13565 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
13566 introduction points for a hidden service have failed. Patch from
13567 Karsten Loesing. Bugfix on 0.2.0.x.
13569 o Code simplifications and refactoring:
13570 - Remove some needless generality from cpuworker code, for improved
13572 - Stop overloading the circuit_t.onionskin field for both "onionskin
13573 from a CREATE cell that we are waiting for a cpuworker to be
13574 assigned" and "onionskin from an EXTEND cell that we are going to
13575 send to an OR as soon as we are connected". Might help with bug 600.
13576 - Add an in-place version of aes_crypt() so that we can avoid doing a
13577 needless memcpy() call on each cell payload.
13580 Changes in version 0.2.0.18-alpha - 2008-01-25
13581 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
13582 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
13583 that can warn or reject connections to ports generally associated with
13584 vulnerable-plaintext protocols.
13586 o New directory authorities:
13587 - Set up dannenberg (run by CCC) as the sixth v3 directory
13591 - Fix a major memory leak when attempting to use the v2 TLS
13592 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
13593 - We accidentally enabled the under-development v2 TLS handshake
13594 code, which was causing log entries like "TLS error while
13595 renegotiating handshake". Disable it again. Resolves bug 590.
13596 - We were computing the wrong Content-Length: header for directory
13597 responses that need to be compressed on the fly, causing clients
13598 asking for those items to always fail. Bugfix on 0.2.0.x; partially
13602 - Avoid going directly to the directory authorities even if you're a
13603 relay, if you haven't found yourself reachable yet or if you've
13604 decided not to advertise your dirport yet. Addresses bug 556.
13605 - If we've gone 12 hours since our last bandwidth check, and we
13606 estimate we have less than 50KB bandwidth capacity but we could
13607 handle more, do another bandwidth test.
13608 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
13609 Tor can warn and/or refuse connections to ports commonly used with
13610 vulnerable-plaintext protocols. Currently we warn on ports 23,
13611 109, 110, and 143, but we don't reject any.
13614 - When we setconf ClientOnly to 1, close any current OR and Dir
13615 listeners. Reported by mwenge.
13616 - When we get a consensus that's been signed by more people than
13617 we expect, don't log about it; it's not a big deal. Reported
13621 - Don't answer "/tor/networkstatus-bridges" directory requests if
13622 the request isn't encrypted.
13623 - Make "ClientOnly 1" config option disable directory ports too.
13624 - Patches from Karsten Loesing to make v2 hidden services more
13625 robust: work even when there aren't enough HSDir relays available;
13626 retry when a v2 rend desc fetch fails; but don't retry if we
13627 already have a usable v0 rend desc.
13630 Changes in version 0.2.0.17-alpha - 2008-01-17
13631 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
13634 - Make the tor-gencert man page get included correctly in the tarball.
13637 Changes in version 0.2.0.16-alpha - 2008-01-17
13638 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
13639 Loesing, and generally cleans up a lot of features and minor bugs.
13641 o New directory authorities:
13642 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
13645 o Major performance improvements:
13646 - Switch our old ring buffer implementation for one more like that
13647 used by free Unix kernels. The wasted space in a buffer with 1mb
13648 of data will now be more like 8k than 1mb. The new implementation
13649 also avoids realloc();realloc(); patterns that can contribute to
13650 memory fragmentation.
13653 - Configuration files now accept C-style strings as values. This
13654 helps encode characters not allowed in the current configuration
13655 file format, such as newline or #. Addresses bug 557.
13656 - Although we fixed bug 539 (where servers would send HTTP status 503
13657 responses _and_ send a body too), there are still servers out
13658 there that haven't upgraded. Therefore, make clients parse such
13659 bodies when they receive them.
13660 - When we're not serving v2 directory information, there is no reason
13661 to actually keep any around. Remove the obsolete files and directory
13662 on startup if they are very old and we aren't going to serve them.
13664 o Minor performance improvements:
13665 - Reference-count and share copies of address policy entries; only 5%
13666 of them were actually distinct.
13667 - Never walk through the list of logs if we know that no log is
13668 interested in a given message.
13671 - When an authority has not signed a consensus, do not try to
13672 download a nonexistent "certificate with key 00000000". Bugfix
13673 on 0.2.0.x. Fixes bug 569.
13674 - Fix a rare assert error when we're closing one of our threads:
13675 use a mutex to protect the list of logs, so we never write to the
13676 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
13677 bug 575, which is kind of the revenge of bug 222.
13678 - Patch from Karsten Loesing to complain less at both the client
13679 and the relay when a relay used to have the HSDir flag but doesn't
13680 anymore, and we try to upload a hidden service descriptor.
13681 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
13683 - Do not try to download missing certificates until we have tried
13684 to check our fallback consensus. Fixes bug 583.
13685 - Make bridges round reported GeoIP stats info up to the nearest
13686 estimate, not down. Now we can distinguish between "0 people from
13687 this country" and "1 person from this country".
13688 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
13689 - Avoid possible segfault if key generation fails in
13690 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
13691 - Avoid segfault in the case where a badly behaved v2 versioning
13692 directory sends a signed networkstatus with missing client-versions.
13694 - Avoid segfaults on certain complex invocations of
13695 router_get_by_hexdigest(). Bugfix on 0.1.2.
13696 - Correct bad index on array access in parse_http_time(). Bugfix
13698 - Fix possible bug in vote generation when server versions are present
13699 but client versions are not.
13700 - Fix rare bug on REDIRECTSTREAM control command when called with no
13701 port set: it could erroneously report an error when none had
13703 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
13704 compressing large objects and find ourselves with more than 4k
13705 left over. Bugfix on 0.2.0.
13706 - Fix a small memory leak when setting up a hidden service.
13707 - Fix a few memory leaks that could in theory happen under bizarre
13709 - Fix an assert if we post a general-purpose descriptor via the
13710 control port but that descriptor isn't mentioned in our current
13711 network consensus. Bug reported by Jon McLachlan; bugfix on
13714 o Minor features (controller):
13715 - Get NS events working again. Patch from tup.
13716 - The GETCONF command now escapes and quotes configuration values
13717 that don't otherwise fit into the torrc file.
13718 - The SETCONF command now handles quoted values correctly.
13720 o Minor features (directory authorities):
13721 - New configuration options to override default maximum number of
13722 servers allowed on a single IP address. This is important for
13723 running a test network on a single host.
13724 - Actually implement the -s option to tor-gencert.
13725 - Add a manual page for tor-gencert.
13727 o Minor features (bridges):
13728 - Bridge authorities no longer serve bridge descriptors over
13729 unencrypted connections.
13731 o Minor features (other):
13732 - Add hidden services and DNSPorts to the list of things that make
13733 Tor accept that it has running ports. Change starting Tor with no
13734 ports from a fatal error to a warning; we might change it back if
13735 this turns out to confuse anybody. Fixes bug 579.
13738 Changes in version 0.1.2.19 - 2008-01-17
13739 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
13740 exit policy a little bit more conservative so it's safer to run an
13741 exit relay on a home system, and fixes a variety of smaller issues.
13744 - Exit policies now reject connections that are addressed to a
13745 relay's public (external) IP address too, unless
13746 ExitPolicyRejectPrivate is turned off. We do this because too
13747 many relays are running nearby to services that trust them based
13748 on network address.
13751 - When the clock jumps forward a lot, do not allow the bandwidth
13752 buckets to become negative. Fixes bug 544.
13753 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
13754 on every successful resolve. Reported by Mike Perry.
13755 - Purge old entries from the "rephist" database and the hidden
13756 service descriptor database even when DirPort is zero.
13757 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
13758 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
13759 crashing or mis-answering these requests.
13760 - When we decide to send a 503 response to a request for servers, do
13761 not then also send the server descriptors: this defeats the whole
13762 purpose. Fixes bug 539.
13765 - Changing the ExitPolicyRejectPrivate setting should cause us to
13766 rebuild our server descriptor.
13767 - Fix handling of hex nicknames when answering controller requests for
13768 networkstatus by name, or when deciding whether to warn about
13769 unknown routers in a config option. (Patch from mwenge.)
13770 - Fix a couple of hard-to-trigger autoconf problems that could result
13771 in really weird results on platforms whose sys/types.h files define
13772 nonstandard integer types.
13773 - Don't try to create the datadir when running --verify-config or
13774 --hash-password. Resolves bug 540.
13775 - If we were having problems getting a particular descriptor from the
13776 directory caches, and then we learned about a new descriptor for
13777 that router, we weren't resetting our failure count. Reported
13779 - Although we fixed bug 539 (where servers would send HTTP status 503
13780 responses _and_ send a body too), there are still servers out there
13781 that haven't upgraded. Therefore, make clients parse such bodies
13782 when they receive them.
13783 - Run correctly on systems where rlim_t is larger than unsigned long.
13784 This includes some 64-bit systems.
13785 - Run correctly on platforms (like some versions of OS X 10.5) where
13786 the real limit for number of open files is OPEN_FILES, not rlim_max
13787 from getrlimit(RLIMIT_NOFILES).
13788 - Avoid a spurious free on base64 failure.
13789 - Avoid segfaults on certain complex invocations of
13790 router_get_by_hexdigest().
13791 - Fix rare bug on REDIRECTSTREAM control command when called with no
13792 port set: it could erroneously report an error when none had
13796 Changes in version 0.2.0.15-alpha - 2007-12-25
13797 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
13798 features added in 0.2.0.13-alpha.
13801 - Fix several remotely triggerable asserts based on DirPort requests
13802 for a v2 or v3 networkstatus object before we were prepared. This
13803 was particularly bad for 0.2.0.13 and later bridge relays, who
13804 would never have a v2 networkstatus and would thus always crash
13805 when used. Bugfixes on 0.2.0.x.
13806 - Estimate the v3 networkstatus size more accurately, rather than
13807 estimating it at zero bytes and giving it artificially high priority
13808 compared to other directory requests. Bugfix on 0.2.0.x.
13811 - Fix configure.in logic for cross-compilation.
13812 - When we load a bridge descriptor from the cache, and it was
13813 previously unreachable, mark it as retriable so we won't just
13814 ignore it. Also, try fetching a new copy immediately. Bugfixes
13816 - The bridge GeoIP stats were counting other relays, for example
13817 self-reachability and authority-reachability tests.
13820 - Support compilation to target iPhone; patch from cjacker huang.
13821 To build for iPhone, pass the --enable-iphone option to configure.
13824 Changes in version 0.2.0.14-alpha - 2007-12-23
13826 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
13827 without a datadirectory from a previous Tor install. Reported
13829 - Fix a crash when we fetch a descriptor that turns out to be
13830 unexpected (it used to be in our networkstatus when we started
13831 fetching it, but it isn't in our current networkstatus), and we
13832 aren't using bridges. Bugfix on 0.2.0.x.
13833 - Fix a crash when accessing hidden services: it would work the first
13834 time you use a given introduction point for your service, but
13835 on subsequent requests we'd be using garbage memory. Fixed by
13836 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
13837 - Fix a crash when we load a bridge descriptor from disk but we don't
13838 currently have a Bridge line for it in our torrc. Bugfix on
13842 - If bridge authorities set BridgePassword, they will serve a
13843 snapshot of known bridge routerstatuses from their DirPort to
13844 anybody who knows that password. Unset by default.
13847 - Make the unit tests build again.
13848 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
13849 - Make PublishServerDescriptor default to 1, so the default doesn't
13850 have to change as we invent new directory protocol versions.
13851 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
13852 be included unless sys/time.h is already included. Fixes
13853 bug 553. Bugfix on 0.2.0.x.
13854 - If we receive a general-purpose descriptor and then receive an
13855 identical bridge-purpose descriptor soon after, don't discard
13856 the next one as a duplicate.
13859 - If BridgeRelay is set to 1, then the default for
13860 PublishServerDescriptor is now "bridge" rather than "v2,v3".
13861 - If the user sets RelayBandwidthRate but doesn't set
13862 RelayBandwidthBurst, then make them equal rather than erroring out.
13865 Changes in version 0.2.0.13-alpha - 2007-12-21
13866 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
13867 Goodell, fixes many more bugs, and adds a lot of infrastructure for
13870 o New directory authorities:
13871 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
13875 - Only update guard status (usable / not usable) once we have
13876 enough directory information. This was causing us to always pick
13877 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
13878 causing us to discard all our guards on startup if we hadn't been
13879 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
13880 - Purge old entries from the "rephist" database and the hidden
13881 service descriptor databases even when DirPort is zero. Bugfix
13883 - We were ignoring our RelayBandwidthRate for the first 30 seconds
13884 after opening a circuit -- even a relayed circuit. Bugfix on
13886 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
13887 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
13888 crashing or mis-answering these types of requests.
13889 - Relays were publishing their server descriptor to v1 and v2
13890 directory authorities, but they didn't try publishing to v3-only
13891 authorities. Fix this; and also stop publishing to v1 authorities.
13893 - When we were reading router descriptors from cache, we were ignoring
13894 the annotations -- so for example we were reading in bridge-purpose
13895 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
13896 - When we decided to send a 503 response to a request for servers, we
13897 were then also sending the server descriptors: this defeats the
13898 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
13901 - Bridge relays now behave like clients with respect to time
13902 intervals for downloading new consensus documents -- otherwise they
13903 stand out. Bridge users now wait until the end of the interval,
13904 so their bridge relay will be sure to have a new consensus document.
13905 - Three new config options (AlternateDirAuthority,
13906 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
13907 user selectively replace the default directory authorities by type,
13908 rather than the all-or-nothing replacement that DirServer offers.
13909 - Tor can now be configured to read a GeoIP file from disk in one
13910 of two formats. This can be used by controllers to map IP addresses
13911 to countries. Eventually, it may support exit-by-country.
13912 - When possible, bridge relays remember which countries users
13913 are coming from, and report aggregate information in their
13914 extra-info documents, so that the bridge authorities can learn
13915 where Tor is blocked.
13916 - Bridge directory authorities now do reachability testing on the
13917 bridges they know. They provide router status summaries to the
13918 controller via "getinfo ns/purpose/bridge", and also dump summaries
13919 to a file periodically.
13920 - Stop fetching directory info so aggressively if your DirPort is
13921 on but your ORPort is off; stop fetching v2 dir info entirely.
13922 You can override these choices with the new FetchDirInfoEarly
13926 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
13927 consensus documents when there are too many relays at a single
13928 IP address. Now clear it in v2 network status documents too, and
13929 also clear it in routerinfo_t when the relay is no longer listed
13930 in the relevant networkstatus document.
13931 - Don't crash if we get an unexpected value for the
13932 PublishServerDescriptor config option. Reported by Matt Edman;
13933 bugfix on 0.2.0.9-alpha.
13934 - Our new v2 hidden service descriptor format allows descriptors
13935 that have no introduction points. But Tor crashed when we tried
13936 to build a descriptor with no intro points (and it would have
13937 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
13938 by Karsten Loesing.
13939 - Fix building with dmalloc 5.5.2 with glibc.
13940 - Reject uploaded descriptors and extrainfo documents if they're
13941 huge. Otherwise we'll cache them all over the network and it'll
13942 clog everything up. Reported by Aljosha Judmayer.
13943 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
13944 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
13945 - When the DANGEROUS_VERSION controller status event told us we're
13946 running an obsolete version, it used the string "OLD" to describe
13947 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
13948 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
13949 - If we can't expand our list of entry guards (e.g. because we're
13950 using bridges or we have StrictEntryNodes set), don't mark relays
13951 down when they fail a directory request. Otherwise we're too quick
13952 to mark all our entry points down. Bugfix on 0.1.2.x.
13953 - Fix handling of hex nicknames when answering controller requests for
13954 networkstatus by name, or when deciding whether to warn about unknown
13955 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
13956 - Fix a couple of hard-to-trigger autoconf problems that could result
13957 in really weird results on platforms whose sys/types.h files define
13958 nonstandard integer types. Bugfix on 0.1.2.x.
13959 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
13960 - Don't crash on name lookup when we have no current consensus. Fixes
13961 bug 538; bugfix on 0.2.0.x.
13962 - Only Tors that want to mirror the v2 directory info should
13963 create the "cached-status" directory in their datadir. (All Tors
13964 used to create it.) Bugfix on 0.2.0.9-alpha.
13965 - Directory authorities should only automatically download Extra Info
13966 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
13969 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
13970 consumers. (We already do this on HUP.)
13971 - Authorities and caches fetch the v2 networkstatus documents
13972 less often, now that v3 is encouraged.
13973 - Add a new config option BridgeRelay that specifies you want to
13974 be a bridge relay. Right now the only difference is that it makes
13975 you answer begin_dir requests, and it makes you cache dir info,
13976 even if your DirPort isn't on.
13977 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
13978 ask about source, timestamp of arrival, purpose, etc. We need
13979 something like this to help Vidalia not do GeoIP lookups on bridge
13981 - Allow multiple HashedControlPassword config lines, to support
13982 multiple controller passwords.
13983 - Authorities now decide whether they're authoritative for a given
13984 router based on the router's purpose.
13985 - New config options AuthDirBadDir and AuthDirListBadDirs for
13986 authorities to mark certain relays as "bad directories" in the
13987 networkstatus documents. Also supports the "!baddir" directive in
13988 the approved-routers file.
13991 Changes in version 0.2.0.12-alpha - 2007-11-16
13992 This twelfth development snapshot fixes some more build problems as
13993 well as a few minor bugs.
13996 - Make it build on OpenBSD again. Patch from tup.
13997 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
13998 package-building for Red Hat, OS X, etc.
14000 o Minor bugfixes (on 0.1.2.x):
14001 - Changing the ExitPolicyRejectPrivate setting should cause us to
14002 rebuild our server descriptor.
14004 o Minor bugfixes (on 0.2.0.x):
14005 - When we're lacking a consensus, don't try to perform rendezvous
14006 operations. Reported by Karsten Loesing.
14007 - Fix a small memory leak whenever we decide against using a
14008 newly picked entry guard. Reported by Mike Perry.
14009 - When authorities detected more than two relays running on the same
14010 IP address, they were clearing all the status flags but forgetting
14011 to clear the "hsdir" flag. So clients were being told that a
14012 given relay was the right choice for a v2 hsdir lookup, yet they
14013 never had its descriptor because it was marked as 'not running'
14015 - If we're trying to fetch a bridge descriptor and there's no way
14016 the bridge authority could help us (for example, we don't know
14017 a digest, or there is no bridge authority), don't be so eager to
14018 fall back to asking the bridge authority.
14019 - If we're using bridges or have strictentrynodes set, and our
14020 chosen exit is in the same family as all our bridges/entry guards,
14021 then be flexible about families.
14024 - When we negotiate a v2 link-layer connection (not yet implemented),
14025 accept RELAY_EARLY cells and turn them into RELAY cells if we've
14026 negotiated a v1 connection for their next step. Initial code for
14030 Changes in version 0.2.0.11-alpha - 2007-11-12
14031 This eleventh development snapshot fixes some build problems with
14032 the previous snapshot. It also includes a more secure-by-default exit
14033 policy for relays, fixes an enormous memory leak for exit relays, and
14034 fixes another bug where servers were falling out of the directory list.
14037 - Exit policies now reject connections that are addressed to a
14038 relay's public (external) IP address too, unless
14039 ExitPolicyRejectPrivate is turned off. We do this because too
14040 many relays are running nearby to services that trust them based
14041 on network address. Bugfix on 0.1.2.x.
14044 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
14045 on every successful resolve. Reported by Mike Perry; bugfix
14047 - On authorities, never downgrade to old router descriptors simply
14048 because they're listed in the consensus. This created a catch-22
14049 where we wouldn't list a new descriptor because there was an
14050 old one in the consensus, and we couldn't get the new one in the
14051 consensus because we wouldn't list it. Possible fix for bug 548.
14052 Also, this might cause bug 543 to appear on authorities; if so,
14053 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
14055 o Packaging fixes on 0.2.0.10-alpha:
14056 - We were including instructions about what to do with the
14057 src/config/fallback-consensus file, but we weren't actually
14058 including it in the tarball. Disable all of that for now.
14061 - Allow people to say PreferTunnelledDirConns rather than
14062 PreferTunneledDirConns, for those alternate-spellers out there.
14065 - Don't reevaluate all the information from our consensus document
14066 just because we've downloaded a v2 networkstatus that we intend
14067 to cache. Fixes bug 545; bugfix on 0.2.0.x.
14070 Changes in version 0.2.0.10-alpha - 2007-11-10
14071 This tenth development snapshot adds a third v3 directory authority
14072 run by Mike Perry, adds most of Karsten Loesing's new hidden service
14073 descriptor format, fixes a bad crash bug and new bridge bugs introduced
14074 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
14075 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
14076 addresses many more minor issues.
14078 o New directory authorities:
14079 - Set up ides (run by Mike Perry) as the third v3 directory authority.
14082 - Allow tunnelled directory connections to ask for an encrypted
14083 "begin_dir" connection or an anonymized "uses a full Tor circuit"
14084 connection independently. Now we can make anonymized begin_dir
14085 connections for (e.g.) more secure hidden service posting and
14087 - More progress on proposal 114: code from Karsten Loesing to
14088 implement new hidden service descriptor format.
14089 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
14090 accommodate the growing number of servers that use the default
14091 and are reaching it.
14092 - Directory authorities use a new formula for selecting which nodes
14093 to advertise as Guards: they must be in the top 7/8 in terms of
14094 how long we have known about them, and above the median of those
14095 nodes in terms of weighted fractional uptime.
14096 - Make "not enough dir info yet" warnings describe *why* Tor feels
14097 it doesn't have enough directory info yet.
14100 - Stop servers from crashing if they set a Family option (or
14101 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
14103 - Make bridge users work again -- the move to v3 directories in
14104 0.2.0.9-alpha had introduced a number of bugs that made bridges
14105 no longer work for clients.
14106 - When the clock jumps forward a lot, do not allow the bandwidth
14107 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
14109 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
14110 - When the consensus lists a router descriptor that we previously were
14111 mirroring, but that we considered non-canonical, reload the
14112 descriptor as canonical. This fixes bug 543 where Tor servers
14113 would start complaining after a few days that they don't have
14114 enough directory information to build a circuit.
14115 - Consider replacing the current consensus when certificates arrive
14116 that make the pending consensus valid. Previously, we were only
14117 considering replacement when the new certs _didn't_ help.
14118 - Fix an assert error on startup if we didn't already have the
14119 consensus and certs cached in our datadirectory: we were caching
14120 the consensus in consensus_waiting_for_certs but then free'ing it
14122 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
14123 Request) if we need more v3 certs but we've already got pending
14124 requests for all of them.
14125 - Correctly back off from failing certificate downloads. Fixes
14127 - Authorities don't vote on the Running flag if they have been running
14128 for less than 30 minutes themselves. Fixes bug 547, where a newly
14129 started authority would vote that everyone was down.
14131 o New requirements:
14132 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
14133 it, it had no AES, and it hasn't seen any security patches since
14137 - Clients now hold circuitless TLS connections open for 1.5 times
14138 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
14139 rebuild a new circuit over them within that timeframe. Previously,
14140 they held them open only for KeepalivePeriod (5 minutes).
14141 - Use "If-Modified-Since" to avoid retrieving consensus
14142 networkstatuses that we already have.
14143 - When we have no consensus, check FallbackNetworkstatusFile (defaults
14144 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
14145 we start knowing some directory caches.
14146 - When we receive a consensus from the future, warn about skew.
14147 - Improve skew reporting: try to give the user a better log message
14148 about how skewed they are, and how much this matters.
14149 - When we have a certificate for an authority, believe that
14150 certificate's claims about the authority's IP address.
14151 - New --quiet command-line option to suppress the default console log.
14152 Good in combination with --hash-password.
14153 - Authorities send back an X-Descriptor-Not-New header in response to
14154 an accepted-but-discarded descriptor upload. Partially implements
14156 - Make the log message for "tls error. breaking." more useful.
14157 - Better log messages about certificate downloads, to attempt to
14158 track down the second incarnation of bug 546.
14160 o Minor features (bridges):
14161 - If bridge users set UpdateBridgesFromAuthority, but the digest
14162 they ask for is a 404 from the bridge authority, they now fall
14163 back to trying the bridge directly.
14164 - Bridges now use begin_dir to publish their server descriptor to
14165 the bridge authority, even when they haven't set TunnelDirConns.
14167 o Minor features (controller):
14168 - When reporting clock skew, and we know that the clock is _at least
14169 as skewed_ as some value, but we don't know the actual value,
14170 report the value as a "minimum skew."
14173 - Update linux-tor-prio.sh script to allow QoS based on the uid of
14174 the Tor process. Patch from Marco Bonetti with tweaks from Mike
14178 - Refuse to start if both ORPort and UseBridges are set. Bugfix
14179 on 0.2.0.x, suggested by Matt Edman.
14180 - Don't stop fetching descriptors when FetchUselessDescriptors is
14181 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
14182 reported by tup and ioerror.
14183 - Better log message on vote from unknown authority.
14184 - Don't log "Launching 0 request for 0 router" message.
14186 o Minor bugfixes (memory leaks):
14187 - Stop leaking memory every time we parse a v3 certificate. Bugfix
14189 - Stop leaking memory every time we load a v3 certificate. Bugfix
14190 on 0.2.0.1-alpha. Fixes bug 536.
14191 - Stop leaking a cached networkstatus on exit. Bugfix on
14193 - Stop leaking voter information every time we free a consensus.
14194 Bugfix on 0.2.0.3-alpha.
14195 - Stop leaking signed data every time we check a voter signature.
14196 Bugfix on 0.2.0.3-alpha.
14197 - Stop leaking a signature every time we fail to parse a consensus or
14198 a vote. Bugfix on 0.2.0.3-alpha.
14199 - Stop leaking v2_download_status_map on shutdown. Bugfix on
14201 - Stop leaking conn->nickname every time we make a connection to a
14202 Tor relay without knowing its expected identity digest (e.g. when
14203 using bridges). Bugfix on 0.2.0.3-alpha.
14205 - Minor bugfixes (portability):
14206 - Run correctly on platforms where rlim_t is larger than unsigned
14207 long, and/or where the real limit for number of open files is
14208 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
14209 particular, these may be needed for OS X 10.5.
14212 Changes in version 0.1.2.18 - 2007-10-28
14213 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
14214 hidden service introduction that were causing huge delays, and a big
14215 bug that was causing some servers to disappear from the network status
14216 lists for a few hours each day.
14218 o Major bugfixes (crashes):
14219 - If a connection is shut down abruptly because of something that
14220 happened inside connection_flushed_some(), do not call
14221 connection_finished_flushing(). Should fix bug 451:
14222 "connection_stop_writing: Assertion conn->write_event failed"
14223 Bugfix on 0.1.2.7-alpha.
14224 - Fix possible segfaults in functions called from
14225 rend_process_relay_cell().
14227 o Major bugfixes (hidden services):
14228 - Hidden services were choosing introduction points uniquely by
14229 hexdigest, but when constructing the hidden service descriptor
14230 they merely wrote the (potentially ambiguous) nickname.
14231 - Clients now use the v2 intro format for hidden service
14232 connections: they specify their chosen rendezvous point by identity
14233 digest rather than by (potentially ambiguous) nickname. These
14234 changes could speed up hidden service connections dramatically.
14236 o Major bugfixes (other):
14237 - Stop publishing a new server descriptor just because we get a
14238 HUP signal. This led (in a roundabout way) to some servers getting
14239 dropped from the networkstatus lists for a few hours each day.
14240 - When looking for a circuit to cannibalize, consider family as well
14241 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
14242 circuit cannibalization).
14243 - When a router wasn't listed in a new networkstatus, we were leaving
14244 the flags for that router alone -- meaning it remained Named,
14245 Running, etc -- even though absence from the networkstatus means
14246 that it shouldn't be considered to exist at all anymore. Now we
14247 clear all the flags for routers that fall out of the networkstatus
14248 consensus. Fixes bug 529.
14251 - Don't try to access (or alter) the state file when running
14252 --list-fingerprint or --verify-config or --hash-password. Resolves
14254 - When generating information telling us how to extend to a given
14255 router, do not try to include the nickname if it is
14256 absent. Resolves bug 467.
14257 - Fix a user-triggerable segfault in expand_filename(). (There isn't
14258 a way to trigger this remotely.)
14259 - When sending a status event to the controller telling it that an
14260 OR address is reachable, set the port correctly. (Previously we
14261 were reporting the dir port.)
14262 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
14263 command. Bugfix on 0.1.2.17.
14264 - When loading bandwidth history, do not believe any information in
14265 the future. Fixes bug 434.
14266 - When loading entry guard information, do not believe any information
14268 - When we have our clock set far in the future and generate an
14269 onion key, then re-set our clock to be correct, we should not stop
14270 the onion key from getting rotated.
14271 - On some platforms, accept() can return a broken address. Detect
14272 this more quietly, and deal accordingly. Fixes bug 483.
14273 - It's not actually an error to find a non-pending entry in the DNS
14274 cache when canceling a pending resolve. Don't log unless stuff
14275 is fishy. Resolves bug 463.
14276 - Don't reset trusted dir server list when we set a configuration
14277 option. Patch from Robert Hogan.
14278 - Don't try to create the datadir when running --verify-config or
14279 --hash-password. Resolves bug 540.
14282 Changes in version 0.2.0.9-alpha - 2007-10-24
14283 This ninth development snapshot switches clients to the new v3 directory
14284 system; allows servers to be listed in the network status even when they
14285 have the same nickname as a registered server; and fixes many other
14286 bugs including a big one that was causing some servers to disappear
14287 from the network status lists for a few hours each day.
14289 o Major features (directory system):
14290 - Clients now download v3 consensus networkstatus documents instead
14291 of v2 networkstatus documents. Clients and caches now base their
14292 opinions about routers on these consensus documents. Clients only
14293 download router descriptors listed in the consensus.
14294 - Authorities now list servers who have the same nickname as
14295 a different named server, but list them with a new flag,
14296 "Unnamed". Now we can list servers that happen to pick the same
14297 nickname as a server that registered two years ago and then
14298 disappeared. Partially implements proposal 122.
14299 - If the consensus lists a router as "Unnamed", the name is assigned
14300 to a different router: do not identify the router by that name.
14301 Partially implements proposal 122.
14302 - Authorities can now come to a consensus on which method to use to
14303 compute the consensus. This gives us forward compatibility.
14306 - Stop publishing a new server descriptor just because we HUP or
14307 when we find our DirPort to be reachable but won't actually publish
14308 it. New descriptors without any real changes are dropped by the
14309 authorities, and can screw up our "publish every 18 hours" schedule.
14311 - When a router wasn't listed in a new networkstatus, we were leaving
14312 the flags for that router alone -- meaning it remained Named,
14313 Running, etc -- even though absence from the networkstatus means
14314 that it shouldn't be considered to exist at all anymore. Now we
14315 clear all the flags for routers that fall out of the networkstatus
14316 consensus. Fixes bug 529; bugfix on 0.1.2.x.
14317 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
14318 extrainfo documents and then discard them immediately for not
14319 matching the latest router. Bugfix on 0.2.0.1-alpha.
14321 o Minor features (v3 directory protocol):
14322 - Allow tor-gencert to generate a new certificate without replacing
14324 - Allow certificates to include an address.
14325 - When we change our directory-cache settings, reschedule all voting
14326 and download operations.
14327 - Reattempt certificate downloads immediately on failure, as long as
14328 we haven't failed a threshold number of times yet.
14329 - Delay retrying consensus downloads while we're downloading
14330 certificates to verify the one we just got. Also, count getting a
14331 consensus that we already have (or one that isn't valid) as a failure,
14332 and count failing to get the certificates after 20 minutes as a
14334 - Build circuits and download descriptors even if our consensus is a
14335 little expired. (This feature will go away once authorities are
14338 o Minor features (router descriptor cache):
14339 - If we find a cached-routers file that's been sitting around for more
14340 than 28 days unmodified, then most likely it's a leftover from
14341 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
14343 - When we (as a cache) download a descriptor because it was listed
14344 in a consensus, remember when the consensus was supposed to expire,
14345 and don't expire the descriptor until then.
14347 o Minor features (performance):
14348 - Call routerlist_remove_old_routers() much less often. This should
14349 speed startup, especially on directory caches.
14350 - Don't try to launch new descriptor downloads quite so often when we
14351 already have enough directory information to build circuits.
14352 - Base64 decoding was actually showing up on our profile when parsing
14353 the initial descriptor file; switch to an in-process all-at-once
14354 implementation that's about 3.5x times faster than calling out to
14357 o Minor features (compilation):
14358 - Detect non-ASCII platforms (if any still exist) and refuse to
14359 build there: some of our code assumes that 'A' is 65 and so on.
14361 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
14362 - Make the "next period" votes into "current period" votes immediately
14363 after publishing the consensus; avoid a heisenbug that made them
14364 stick around indefinitely.
14365 - When we discard a vote as a duplicate, do not report this as
14367 - Treat missing v3 keys or certificates as an error when running as a
14368 v3 directory authority.
14369 - When we're configured to be a v3 authority, but we're only listed
14370 as a non-v3 authority in our DirServer line for ourself, correct
14372 - If an authority doesn't have a qualified hostname, just put
14373 its address in the vote. This fixes the problem where we referred to
14374 "moria on moria:9031."
14375 - Distinguish between detached signatures for the wrong period, and
14376 detached signatures for a divergent vote.
14377 - Fix a small memory leak when computing a consensus.
14378 - When there's no concensus, we were forming a vote every 30
14379 minutes, but writing the "valid-after" line in our vote based
14380 on our configured V3AuthVotingInterval: so unless the intervals
14381 matched up, we immediately rejected our own vote because it didn't
14382 start at the voting interval that caused us to construct a vote.
14384 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
14385 - Delete unverified-consensus when the real consensus is set.
14386 - Consider retrying a consensus networkstatus fetch immediately
14387 after one fails: don't wait 60 seconds to notice.
14388 - When fetching a consensus as a cache, wait until a newer consensus
14389 should exist before trying to replace the current one.
14390 - Use a more forgiving schedule for retrying failed consensus
14391 downloads than for other types.
14393 o Minor bugfixes (other directory issues):
14394 - Correct the implementation of "download votes by digest." Bugfix on
14396 - Authorities no longer send back "400 you're unreachable please fix
14397 it" errors to Tor servers that aren't online all the time. We're
14398 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
14400 o Minor bugfixes (controller):
14401 - Don't reset trusted dir server list when we set a configuration
14402 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
14403 - Respond to INT and TERM SIGNAL commands before we execute the
14404 signal, in case the signal shuts us down. We had a patch in
14405 0.1.2.1-alpha that tried to do this by queueing the response on
14406 the connection's buffer before shutting down, but that really
14407 isn't the same thing at all. Bug located by Matt Edman.
14409 o Minor bugfixes (misc):
14410 - Correctly check for bad options to the "PublishServerDescriptor"
14411 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
14412 - Stop leaking memory on failing case of base32_decode, and make
14413 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
14414 - Don't try to download extrainfo documents when we're trying to
14415 fetch enough directory info to build a circuit: having enough
14416 info should get priority. Bugfix on 0.2.0.x.
14417 - Don't complain that "your server has not managed to confirm that its
14418 ports are reachable" if we haven't been able to build any circuits
14419 yet. Bug found by spending four hours without a v3 consensus. Bugfix
14421 - Detect the reason for failing to mmap a descriptor file we just
14422 wrote, and give a more useful log message. Fixes bug 533. Bugfix
14425 o Code simplifications and refactoring:
14426 - Remove support for the old bw_accounting file: we've been storing
14427 bandwidth accounting information in the state file since
14428 0.1.2.5-alpha. This may result in bandwidth accounting errors
14429 if you try to upgrade from 0.1.1.x or earlier, or if you try to
14430 downgrade to 0.1.1.x or earlier.
14431 - New convenience code to locate a file within the DataDirectory.
14432 - Move non-authority functionality out of dirvote.c.
14433 - Refactor the arguments for router_pick_{directory_|trusteddir}server
14434 so that they all take the same named flags.
14437 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
14438 Unix users an easy way to script their Tor process (e.g. by
14439 adjusting bandwidth based on the time of the day).
14442 Changes in version 0.2.0.8-alpha - 2007-10-12
14443 This eighth development snapshot fixes a crash bug that's been bothering
14444 us since February 2007, lets bridge authorities store a list of bridge
14445 descriptors they've seen, gets v3 directory voting closer to working,
14446 starts caching v3 directory consensus documents on directory mirrors,
14447 and fixes a variety of smaller issues including some minor memory leaks.
14449 o Major features (router descriptor cache):
14450 - Store routers in a file called cached-descriptors instead of in
14451 cached-routers. Initialize cached-descriptors from cached-routers
14452 if the old format is around. The new format allows us to store
14453 annotations along with descriptors.
14454 - Use annotations to record the time we received each descriptor, its
14455 source, and its purpose.
14456 - Disable the SETROUTERPURPOSE controller command: it is now
14458 - Controllers should now specify cache=no or cache=yes when using
14459 the +POSTDESCRIPTOR command.
14460 - Bridge authorities now write bridge descriptors to disk, meaning
14461 we can export them to other programs and begin distributing them
14464 o Major features (directory authorities):
14465 - When a v3 authority is missing votes or signatures, it now tries
14467 - Directory authorities track weighted fractional uptime as well as
14468 weighted mean-time-between failures. WFU is suitable for deciding
14469 whether a node is "usually up", while MTBF is suitable for deciding
14470 whether a node is "likely to stay up." We need both, because
14471 "usually up" is a good requirement for guards, while "likely to
14472 stay up" is a good requirement for long-lived connections.
14474 o Major features (v3 directory system):
14475 - Caches now download v3 network status documents as needed,
14476 and download the descriptors listed in them.
14477 - All hosts now attempt to download and keep fresh v3 authority
14478 certificates, and re-attempt after failures.
14479 - More internal-consistency checks for vote parsing.
14481 o Major bugfixes (crashes):
14482 - If a connection is shut down abruptly because of something that
14483 happened inside connection_flushed_some(), do not call
14484 connection_finished_flushing(). Should fix bug 451. Bugfix on
14487 o Major bugfixes (performance):
14488 - Fix really bad O(n^2) performance when parsing a long list of
14489 routers: Instead of searching the entire list for an "extra-info "
14490 string which usually wasn't there, once for every routerinfo
14491 we read, just scan lines forward until we find one we like.
14493 - When we add data to a write buffer in response to the data on that
14494 write buffer getting low because of a flush, do not consider the
14495 newly added data as a candidate for immediate flushing, but rather
14496 make it wait until the next round of writing. Otherwise, we flush
14497 and refill recursively, and a single greedy TLS connection can
14498 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
14500 o Minor features (v3 authority system):
14501 - Add more ways for tools to download the votes that lead to the
14503 - Send a 503 when low on bandwidth and a vote, consensus, or
14504 certificate is requested.
14505 - If-modified-since is now implemented properly for all kinds of
14506 certificate requests.
14508 o Minor bugfixes (network statuses):
14509 - Tweak the implementation of proposal 109 slightly: allow at most
14510 two Tor servers on the same IP address, except if it's the location
14511 of a directory authority, in which case allow five. Bugfix on
14514 o Minor bugfixes (controller):
14515 - When sending a status event to the controller telling it that an
14516 OR address is reachable, set the port correctly. (Previously we
14517 were reporting the dir port.) Bugfix on 0.1.2.x.
14519 o Minor bugfixes (v3 directory system):
14520 - Fix logic to look up a cert by its signing key digest. Bugfix on
14522 - Only change the reply to a vote to "OK" if it's not already
14523 set. This gets rid of annoying "400 OK" log messages, which may
14524 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
14525 - When we get a valid consensus, recompute the voting schedule.
14526 - Base the valid-after time of a vote on the consensus voting
14527 schedule, not on our preferred schedule.
14528 - Make the return values and messages from signature uploads and
14529 downloads more sensible.
14530 - Fix a memory leak when serving votes and consensus documents, and
14531 another when serving certificates.
14533 o Minor bugfixes (performance):
14534 - Use a slightly simpler string hashing algorithm (copying Python's
14535 instead of Java's) and optimize our digest hashing algorithm to take
14536 advantage of 64-bit platforms and to remove some possibly-costly
14538 - Fix a minor memory leak whenever we parse guards from our state
14539 file. Bugfix on 0.2.0.7-alpha.
14540 - Fix a minor memory leak whenever we write out a file. Bugfix on
14542 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
14543 command. Bugfix on 0.2.0.5-alpha.
14545 o Minor bugfixes (portability):
14546 - On some platforms, accept() can return a broken address. Detect
14547 this more quietly, and deal accordingly. Fixes bug 483.
14548 - Stop calling tor_strlower() on uninitialized memory in some cases.
14549 Bugfix in 0.2.0.7-alpha.
14551 o Minor bugfixes (usability):
14552 - Treat some 403 responses from directory servers as INFO rather than
14553 WARN-severity events.
14554 - It's not actually an error to find a non-pending entry in the DNS
14555 cache when canceling a pending resolve. Don't log unless stuff is
14556 fishy. Resolves bug 463.
14558 o Minor bugfixes (anonymity):
14559 - Never report that we've used more bandwidth than we're willing to
14560 relay: it leaks how much non-relay traffic we're using. Resolves
14562 - When looking for a circuit to cannibalize, consider family as well
14563 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
14564 circuit cannibalization).
14566 o Code simplifications and refactoring:
14567 - Make a bunch of functions static. Remove some dead code.
14568 - Pull out about a third of the really big routerlist.c; put it in a
14569 new module, networkstatus.c.
14570 - Merge the extra fields in local_routerstatus_t back into
14571 routerstatus_t: we used to need one routerstatus_t for each
14572 authority's opinion, plus a local_routerstatus_t for the locally
14573 computed consensus opinion. To save space, we put the locally
14574 modified fields into local_routerstatus_t, and only the common
14575 stuff into routerstatus_t. But once v3 directories are in use,
14576 clients and caches will no longer need to hold authority opinions;
14577 thus, the rationale for keeping the types separate is now gone.
14578 - Make the code used to reschedule and reattempt downloads more
14580 - Turn all 'Are we a directory server/mirror?' logic into a call to
14582 - Remove the code to generate the oldest (v1) directory format.
14583 The code has been disabled since 0.2.0.5-alpha.
14586 Changes in version 0.2.0.7-alpha - 2007-09-21
14587 This seventh development snapshot makes bridges work again, makes bridge
14588 authorities work for the first time, fixes two huge performance flaws
14589 in hidden services, and fixes a variety of minor issues.
14591 o New directory authorities:
14592 - Set up moria1 and tor26 as the first v3 directory authorities. See
14593 doc/spec/dir-spec.txt for details on the new directory design.
14595 o Major bugfixes (crashes):
14596 - Fix possible segfaults in functions called from
14597 rend_process_relay_cell(). Bugfix on 0.1.2.x.
14599 o Major bugfixes (bridges):
14600 - Fix a bug that made servers send a "404 Not found" in response to
14601 attempts to fetch their server descriptor. This caused Tor servers
14602 to take many minutes to establish reachability for their DirPort,
14603 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
14604 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
14605 users configure that and specify a bridge with an identity
14606 fingerprint, now they will lookup the bridge descriptor at the
14607 default bridge authority via a one-hop tunnel, but once circuits
14608 are established they will switch to a three-hop tunnel for later
14609 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
14611 o Major bugfixes (hidden services):
14612 - Hidden services were choosing introduction points uniquely by
14613 hexdigest, but when constructing the hidden service descriptor
14614 they merely wrote the (potentially ambiguous) nickname.
14615 - Clients now use the v2 intro format for hidden service
14616 connections: they specify their chosen rendezvous point by identity
14617 digest rather than by (potentially ambiguous) nickname. Both
14618 are bugfixes on 0.1.2.x, and they could speed up hidden service
14619 connections dramatically. Thanks to Karsten Loesing.
14621 o Minor features (security):
14622 - As a client, do not believe any server that tells us that an
14623 address maps to an internal address space.
14624 - Make it possible to enable HashedControlPassword and
14625 CookieAuthentication at the same time.
14627 o Minor features (guard nodes):
14628 - Tag every guard node in our state file with the version that
14629 we believe added it, or with our own version if we add it. This way,
14630 if a user temporarily runs an old version of Tor and then switches
14631 back to a new one, she doesn't automatically lose her guards.
14633 o Minor features (speed):
14634 - When implementing AES counter mode, update only the portions of the
14635 counter buffer that need to change, and don't keep separate
14636 network-order and host-order counters when they are the same (i.e.,
14637 on big-endian hosts.)
14639 o Minor features (controller):
14640 - Accept LF instead of CRLF on controller, since some software has a
14641 hard time generating real Internet newlines.
14642 - Add GETINFO values for the server status events
14643 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
14646 o Removed features:
14647 - Routers no longer include bandwidth-history lines in their
14648 descriptors; this information is already available in extra-info
14649 documents, and including it in router descriptors took up 60%
14650 (!) of compressed router descriptor downloads. Completes
14651 implementation of proposal 104.
14652 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
14653 and TorControl.py, as they use the old v0 controller protocol,
14654 and are obsoleted by TorFlow anyway.
14655 - Drop support for v1 rendezvous descriptors, since we never used
14656 them anyway, and the code has probably rotted by now. Based on
14657 patch from Karsten Loesing.
14658 - On OSX, stop warning the user that kqueue support in libevent is
14659 "experimental", since it seems to have worked fine for ages.
14662 - When generating information telling us how to extend to a given
14663 router, do not try to include the nickname if it is absent. Fixes
14664 bug 467. Bugfix on 0.2.0.3-alpha.
14665 - Fix a user-triggerable (but not remotely-triggerable) segfault
14666 in expand_filename(). Bugfix on 0.1.2.x.
14667 - Fix a memory leak when freeing incomplete requests from DNSPort.
14668 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
14669 - Don't try to access (or alter) the state file when running
14670 --list-fingerprint or --verify-config or --hash-password. (Resolves
14671 bug 499.) Bugfix on 0.1.2.x.
14672 - Servers used to decline to publish their DirPort if their
14673 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
14674 were below a threshold. Now they only look at BandwidthRate and
14675 RelayBandwidthRate. Bugfix on 0.1.2.x.
14676 - Remove an optimization in the AES counter-mode code that assumed
14677 that the counter never exceeded 2^68. When the counter can be set
14678 arbitrarily as an IV (as it is by Karsten's new hidden services
14679 code), this assumption no longer holds. Bugfix on 0.1.2.x.
14680 - Resume listing "AUTHORITY" flag for authorities in network status.
14681 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
14683 o Code simplifications and refactoring:
14684 - Revamp file-writing logic so we don't need to have the entire
14685 contents of a file in memory at once before we write to disk. Tor,
14687 - Turn "descriptor store" into a full-fledged type.
14688 - Move all NT services code into a separate source file.
14689 - Unify all code that computes medians, percentile elements, etc.
14690 - Get rid of a needless malloc when parsing address policies.
14693 Changes in version 0.1.2.17 - 2007-08-30
14694 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
14695 X bundles. Vidalia 0.0.14 makes authentication required for the
14696 ControlPort in the default configuration, which addresses important
14697 security risks. Everybody who uses Vidalia (or another controller)
14700 In addition, this Tor update fixes major load balancing problems with
14701 path selection, which should speed things up a lot once many people
14704 o Major bugfixes (security):
14705 - We removed support for the old (v0) control protocol. It has been
14706 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
14707 become more of a headache than it's worth.
14709 o Major bugfixes (load balancing):
14710 - When choosing nodes for non-guard positions, weight guards
14711 proportionally less, since they already have enough load. Patch
14713 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
14714 will allow fast Tor servers to get more attention.
14715 - When we're upgrading from an old Tor version, forget our current
14716 guards and pick new ones according to the new weightings. These
14717 three load balancing patches could raise effective network capacity
14718 by a factor of four. Thanks to Mike Perry for measurements.
14720 o Major bugfixes (stream expiration):
14721 - Expire not-yet-successful application streams in all cases if
14722 they've been around longer than SocksTimeout. Right now there are
14723 some cases where the stream will live forever, demanding a new
14724 circuit every 15 seconds. Fixes bug 454; reported by lodger.
14726 o Minor features (controller):
14727 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
14728 is valid before any authentication has been received. It tells
14729 a controller what kind of authentication is expected, and what
14730 protocol is spoken. Implements proposal 119.
14732 o Minor bugfixes (performance):
14733 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
14734 greatly speeding up loading cached-routers from disk on startup.
14735 - Disable sentinel-based debugging for buffer code: we squashed all
14736 the bugs that this was supposed to detect a long time ago, and now
14737 its only effect is to change our buffer sizes from nice powers of
14738 two (which platform mallocs tend to like) to values slightly over
14739 powers of two (which make some platform mallocs sad).
14741 o Minor bugfixes (misc):
14742 - If exit bandwidth ever exceeds one third of total bandwidth, then
14743 use the correct formula to weight exit nodes when choosing paths.
14744 Based on patch from Mike Perry.
14745 - Choose perfectly fairly among routers when choosing by bandwidth and
14746 weighting by fraction of bandwidth provided by exits. Previously, we
14747 would choose with only approximate fairness, and correct ourselves
14748 if we ran off the end of the list.
14749 - If we require CookieAuthentication but we fail to write the
14750 cookie file, we would warn but not exit, and end up in a state
14751 where no controller could authenticate. Now we exit.
14752 - If we require CookieAuthentication, stop generating a new cookie
14753 every time we change any piece of our config.
14754 - Refuse to start with certain directory authority keys, and
14755 encourage people using them to stop.
14756 - Terminate multi-line control events properly. Original patch
14758 - Fix a minor memory leak when we fail to find enough suitable
14759 servers to choose a circuit.
14760 - Stop leaking part of the descriptor when we run into a particularly
14761 unparseable piece of it.
14764 Changes in version 0.2.0.6-alpha - 2007-08-26
14765 This sixth development snapshot features a new Vidalia version in the
14766 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
14767 the ControlPort in the default configuration, which addresses important
14770 In addition, this snapshot fixes major load balancing problems
14771 with path selection, which should speed things up a lot once many
14772 people have upgraded. The directory authorities also use a new
14773 mean-time-between-failure approach to tracking which servers are stable,
14774 rather than just looking at the most recent uptime.
14776 o New directory authorities:
14777 - Set up Tonga as the default bridge directory authority.
14780 - Directory authorities now track servers by weighted
14781 mean-times-between-failures. When we have 4 or more days of data,
14782 use measured MTBF rather than declared uptime to decide whether
14783 to call a router Stable. Implements proposal 108.
14785 o Major bugfixes (load balancing):
14786 - When choosing nodes for non-guard positions, weight guards
14787 proportionally less, since they already have enough load. Patch
14789 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
14790 will allow fast Tor servers to get more attention.
14791 - When we're upgrading from an old Tor version, forget our current
14792 guards and pick new ones according to the new weightings. These
14793 three load balancing patches could raise effective network capacity
14794 by a factor of four. Thanks to Mike Perry for measurements.
14796 o Major bugfixes (descriptor parsing):
14797 - Handle unexpected whitespace better in malformed descriptors. Bug
14798 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
14801 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
14802 GETINFO for Torstat to use until it can switch to using extrainfos.
14803 - Optionally (if built with -DEXPORTMALLINFO) export the output
14804 of mallinfo via http, as tor/mallinfo.txt. Only accessible
14808 - Do not intermix bridge routers with controller-added
14809 routers. (Bugfix on 0.2.0.x)
14810 - Do not fail with an assert when accept() returns an unexpected
14811 address family. Addresses but does not wholly fix bug 483. (Bugfix
14813 - Let directory authorities startup even when they can't generate
14814 a descriptor immediately, e.g. because they don't know their
14816 - Stop putting the authentication cookie in a file called "0"
14817 in your working directory if you don't specify anything for the
14818 new CookieAuthFile option. Reported by Matt Edman.
14819 - Make it possible to read the PROTOCOLINFO response in a way that
14820 conforms to our control-spec. Reported by Matt Edman.
14821 - Fix a minor memory leak when we fail to find enough suitable
14822 servers to choose a circuit. Bugfix on 0.1.2.x.
14823 - Stop leaking part of the descriptor when we run into a particularly
14824 unparseable piece of it. Bugfix on 0.1.2.x.
14825 - Unmap the extrainfo cache file on exit.
14828 Changes in version 0.2.0.5-alpha - 2007-08-19
14829 This fifth development snapshot fixes compilation on Windows again;
14830 fixes an obnoxious client-side bug that slowed things down and put
14831 extra load on the network; gets us closer to using the v3 directory
14832 voting scheme; makes it easier for Tor controllers to use cookie-based
14833 authentication; and fixes a variety of other bugs.
14835 o Removed features:
14836 - Version 1 directories are no longer generated in full. Instead,
14837 authorities generate and serve "stub" v1 directories that list
14838 no servers. This will stop Tor versions 0.1.0.x and earlier from
14839 working, but (for security reasons) nobody should be running those
14842 o Major bugfixes (compilation, 0.2.0.x):
14843 - Try to fix Win32 compilation again: improve checking for IPv6 types.
14844 - Try to fix MSVC compilation: build correctly on platforms that do
14845 not define s6_addr16 or s6_addr32.
14846 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
14849 o Major bugfixes (stream expiration):
14850 - Expire not-yet-successful application streams in all cases if
14851 they've been around longer than SocksTimeout. Right now there are
14852 some cases where the stream will live forever, demanding a new
14853 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
14854 reported by lodger.
14856 o Minor features (directory servers):
14857 - When somebody requests a list of statuses or servers, and we have
14858 none of those, return a 404 rather than an empty 200.
14860 o Minor features (directory voting):
14861 - Store v3 consensus status consensuses on disk, and reload them
14864 o Minor features (security):
14865 - Warn about unsafe ControlPort configurations.
14866 - Refuse to start with certain directory authority keys, and
14867 encourage people using them to stop.
14869 o Minor features (controller):
14870 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
14871 is valid before any authentication has been received. It tells
14872 a controller what kind of authentication is expected, and what
14873 protocol is spoken. Implements proposal 119.
14874 - New config option CookieAuthFile to choose a new location for the
14875 cookie authentication file, and config option
14876 CookieAuthFileGroupReadable to make it group-readable.
14878 o Minor features (unit testing):
14879 - Add command-line arguments to unit-test executable so that we can
14880 invoke any chosen test from the command line rather than having
14881 to run the whole test suite at once; and so that we can turn on
14882 logging for the unit tests.
14884 o Minor bugfixes (on 0.1.2.x):
14885 - If we require CookieAuthentication but we fail to write the
14886 cookie file, we would warn but not exit, and end up in a state
14887 where no controller could authenticate. Now we exit.
14888 - If we require CookieAuthentication, stop generating a new cookie
14889 every time we change any piece of our config.
14890 - When loading bandwidth history, do not believe any information in
14891 the future. Fixes bug 434.
14892 - When loading entry guard information, do not believe any information
14894 - When we have our clock set far in the future and generate an
14895 onion key, then re-set our clock to be correct, we should not stop
14896 the onion key from getting rotated.
14897 - Clean up torrc sample config file.
14898 - Do not automatically run configure from autogen.sh. This
14899 non-standard behavior tended to annoy people who have built other
14902 o Minor bugfixes (on 0.2.0.x):
14903 - Fix a bug with AutomapHostsOnResolve that would always cause
14904 the second request to fail. Bug reported by Kate. Bugfix on
14906 - Fix a bug in ADDRMAP controller replies that would sometimes
14907 try to print a NULL. Patch from tup.
14908 - Read v3 directory authority keys from the right location.
14909 - Numerous bugfixes to directory voting code.
14912 Changes in version 0.1.2.16 - 2007-08-01
14913 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
14914 remote attacker in certain situations to rewrite the user's torrc
14915 configuration file. This can completely compromise anonymity of users
14916 in most configurations, including those running the Vidalia bundles,
14917 TorK, etc. Or worse.
14919 o Major security fixes:
14920 - Close immediately after missing authentication on control port;
14921 do not allow multiple authentication attempts.
14924 Changes in version 0.2.0.4-alpha - 2007-08-01
14925 This fourth development snapshot fixes a critical security vulnerability
14926 for most users, specifically those running Vidalia, TorK, etc. Everybody
14927 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
14929 o Major security fixes:
14930 - Close immediately after missing authentication on control port;
14931 do not allow multiple authentication attempts.
14933 o Major bugfixes (compilation):
14934 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
14937 o Minor features (performance):
14938 - Be even more aggressive about releasing RAM from small
14939 empty buffers. Thanks to our free-list code, this shouldn't be too
14940 performance-intensive.
14941 - Disable sentinel-based debugging for buffer code: we squashed all
14942 the bugs that this was supposed to detect a long time ago, and
14943 now its only effect is to change our buffer sizes from nice
14944 powers of two (which platform mallocs tend to like) to values
14945 slightly over powers of two (which make some platform mallocs sad).
14946 - Log malloc statistics from mallinfo() on platforms where it
14950 Changes in version 0.2.0.3-alpha - 2007-07-29
14951 This third development snapshot introduces new experimental
14952 blocking-resistance features and a preliminary version of the v3
14953 directory voting design, and includes many other smaller features
14957 - The first pieces of our "bridge" design for blocking-resistance
14958 are implemented. People can run bridge directory authorities;
14959 people can run bridges; and people can configure their Tor clients
14960 with a set of bridges to use as the first hop into the Tor network.
14961 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
14963 - Create listener connections before we setuid to the configured
14964 User and Group. Now non-Windows users can choose port values
14965 under 1024, start Tor as root, and have Tor bind those ports
14966 before it changes to another UID. (Windows users could already
14968 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
14969 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
14970 on "vserver" accounts. (Patch from coderman.)
14971 - Be even more aggressive about separating local traffic from relayed
14972 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
14974 o Major features (experimental):
14975 - First cut of code for "v3 dir voting": directory authorities will
14976 vote on a common network status document rather than each publishing
14977 their own opinion. This code needs more testing and more corner-case
14978 handling before it's ready for use.
14981 - Directory authorities now call routers Fast if their bandwidth is
14982 at least 100KB/s, and consider their bandwidth adequate to be a
14983 Guard if it is at least 250KB/s, no matter the medians. This fix
14984 complements proposal 107. [Bugfix on 0.1.2.x]
14985 - Directory authorities now never mark more than 3 servers per IP as
14986 Valid and Running. (Implements proposal 109, by Kevin Bauer and
14988 - Minor change to organizationName and commonName generation
14989 procedures in TLS certificates during Tor handshakes, to invalidate
14990 some earlier censorware approaches. This is not a long-term
14991 solution, but applying it will give us a bit of time to look into
14992 the epidemiology of countermeasures as they spread.
14994 o Major bugfixes (directory):
14995 - Rewrite directory tokenization code to never run off the end of
14996 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
14998 o Minor features (controller):
14999 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
15000 match requests to applications. (Patch from Robert Hogan.)
15001 - Report address and port correctly on connections to DNSPort. (Patch
15002 from Robert Hogan.)
15003 - Add a RESOLVE command to launch hostname lookups. (Original patch
15004 from Robert Hogan.)
15005 - Add GETINFO status/enough-dir-info to let controllers tell whether
15006 Tor has downloaded sufficient directory information. (Patch
15008 - You can now use the ControlSocket option to tell Tor to listen for
15009 controller connections on Unix domain sockets on systems that
15010 support them. (Patch from Peter Palfrader.)
15011 - STREAM NEW events are generated for DNSPort requests and for
15012 tunneled directory connections. (Patch from Robert Hogan.)
15013 - New "GETINFO address-mappings/*" command to get address mappings
15014 with expiry information. "addr-mappings/*" is now deprecated.
15017 o Minor features (misc):
15018 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
15020 - The tor-gencert tool for v3 directory authorities now creates all
15021 files as readable to the file creator only, and write-protects
15022 the authority identity key.
15023 - When dumping memory usage, list bytes used in buffer memory
15025 - When running with dmalloc, dump more stats on hup and on exit.
15026 - Directory authorities now fail quickly and (relatively) harmlessly
15027 if they generate a network status document that is somehow
15030 o Traffic load balancing improvements:
15031 - If exit bandwidth ever exceeds one third of total bandwidth, then
15032 use the correct formula to weight exit nodes when choosing paths.
15033 (Based on patch from Mike Perry.)
15034 - Choose perfectly fairly among routers when choosing by bandwidth and
15035 weighting by fraction of bandwidth provided by exits. Previously, we
15036 would choose with only approximate fairness, and correct ourselves
15037 if we ran off the end of the list. [Bugfix on 0.1.2.x]
15039 o Performance improvements:
15040 - Be more aggressive with freeing buffer RAM or putting it on the
15042 - Use Critical Sections rather than Mutexes for synchronizing threads
15043 on win32; Mutexes are heavier-weight, and designed for synchronizing
15046 o Deprecated and removed features:
15047 - RedirectExits is now deprecated.
15048 - Stop allowing address masks that do not correspond to bit prefixes.
15049 We have warned about these for a really long time; now it's time
15050 to reject them. (Patch from croup.)
15052 o Minor bugfixes (directory):
15053 - Fix another crash bug related to extra-info caching. (Bug found by
15054 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
15055 - Directories no longer return a "304 not modified" when they don't
15056 have the networkstatus the client asked for. Also fix a memory
15057 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
15058 - We had accidentally labelled 0.1.2.x directory servers as not
15059 suitable for begin_dir requests, and had labelled no directory
15060 servers as suitable for uploading extra-info documents. [Bugfix
15063 o Minor bugfixes (dns):
15064 - Fix a crash when DNSPort is set more than once. (Patch from Robert
15065 Hogan.) [Bugfix on 0.2.0.2-alpha]
15066 - Add DNSPort connections to the global connection list, so that we
15067 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
15069 - Fix a dangling reference that could lead to a crash when DNSPort is
15070 changed or closed (Patch from Robert Hogan.) [Bugfix on
15073 o Minor bugfixes (controller):
15074 - Provide DNS expiry times in GMT, not in local time. For backward
15075 compatibility, ADDRMAP events only provide GMT expiry in an extended
15076 field. "GETINFO address-mappings" always does the right thing.
15077 - Use CRLF line endings properly in NS events.
15078 - Terminate multi-line control events properly. (Original patch
15079 from tup.) [Bugfix on 0.1.2.x-alpha]
15080 - Do not include spaces in SOURCE_ADDR fields in STREAM
15081 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
15084 Changes in version 0.1.2.15 - 2007-07-17
15085 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
15086 problems, fixes compilation on BSD, and fixes a variety of other
15087 bugs. Everybody should upgrade.
15089 o Major bugfixes (compilation):
15090 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
15092 o Major bugfixes (crashes):
15093 - Try even harder not to dereference the first character after
15094 an mmap(). Reported by lodger.
15095 - Fix a crash bug in directory authorities when we re-number the
15096 routerlist while inserting a new router.
15097 - When the cached-routers file is an even multiple of the page size,
15098 don't run off the end and crash. (Fixes bug 455; based on idea
15100 - Fix eventdns.c behavior on Solaris: It is critical to include
15101 orconfig.h _before_ sys/types.h, so that we can get the expected
15102 definition of _FILE_OFFSET_BITS.
15104 o Major bugfixes (security):
15105 - Fix a possible buffer overrun when using BSD natd support. Bug
15107 - When sending destroy cells from a circuit's origin, don't include
15108 the reason for tearing down the circuit. The spec says we didn't,
15109 and now we actually don't. Reported by lodger.
15110 - Keep streamids from different exits on a circuit separate. This
15111 bug may have allowed other routers on a given circuit to inject
15112 cells into streams. Reported by lodger; fixes bug 446.
15113 - If there's a never-before-connected-to guard node in our list,
15114 never choose any guards past it. This way we don't expand our
15115 guard list unless we need to.
15117 o Minor bugfixes (guard nodes):
15118 - Weight guard selection by bandwidth, so that low-bandwidth nodes
15119 don't get overused as guards.
15121 o Minor bugfixes (directory):
15122 - Correctly count the number of authorities that recommend each
15123 version. Previously, we were under-counting by 1.
15124 - Fix a potential crash bug when we load many server descriptors at
15125 once and some of them make others of them obsolete. Fixes bug 458.
15127 o Minor bugfixes (hidden services):
15128 - Stop tearing down the whole circuit when the user asks for a
15129 connection to a port that the hidden service didn't configure.
15132 o Minor bugfixes (misc):
15133 - On Windows, we were preventing other processes from reading
15134 cached-routers while Tor was running. Reported by janbar.
15135 - Fix a possible (but very unlikely) bug in picking routers by
15136 bandwidth. Add a log message to confirm that it is in fact
15137 unlikely. Patch from lodger.
15138 - Backport a couple of memory leak fixes.
15139 - Backport miscellaneous cosmetic bugfixes.
15142 Changes in version 0.2.0.2-alpha - 2007-06-02
15143 o Major bugfixes on 0.2.0.1-alpha:
15144 - Fix an assertion failure related to servers without extra-info digests.
15145 Resolves bugs 441 and 442.
15147 o Minor features (directory):
15148 - Support "If-Modified-Since" when answering HTTP requests for
15149 directories, running-routers documents, and network-status documents.
15150 (There's no need to support it for router descriptors, since those
15151 are downloaded by descriptor digest.)
15153 o Minor build issues:
15154 - Clear up some MIPSPro compiler warnings.
15155 - When building from a tarball on a machine that happens to have SVK
15156 installed, report the micro-revision as whatever version existed
15157 in the tarball, not as "x".
15160 Changes in version 0.2.0.1-alpha - 2007-06-01
15161 This early development snapshot provides new features for people running
15162 Tor as both a client and a server (check out the new RelayBandwidth
15163 config options); lets Tor run as a DNS proxy; and generally moves us
15164 forward on a lot of fronts.
15166 o Major features, server usability:
15167 - New config options RelayBandwidthRate and RelayBandwidthBurst:
15168 a separate set of token buckets for relayed traffic. Right now
15169 relayed traffic is defined as answers to directory requests, and
15170 OR connections that don't have any local circuits on them.
15172 o Major features, client usability:
15173 - A client-side DNS proxy feature to replace the need for
15174 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
15175 for DNS requests on port 9999, use the Tor network to resolve them
15176 anonymously, and send the reply back like a regular DNS server.
15177 The code still only implements a subset of DNS.
15178 - Make PreferTunneledDirConns and TunnelDirConns work even when
15179 we have no cached directory info. This means Tor clients can now
15180 do all of their connections protected by TLS.
15182 o Major features, performance and efficiency:
15183 - Directory authorities accept and serve "extra info" documents for
15184 routers. These documents contain fields from router descriptors
15185 that aren't usually needed, and that use a lot of excess
15186 bandwidth. Once these fields are removed from router descriptors,
15187 the bandwidth savings should be about 60%. [Partially implements
15189 - Servers upload extra-info documents to any authority that accepts
15190 them. Authorities (and caches that have been configured to download
15191 extra-info documents) download them as needed. [Partially implements
15193 - Change the way that Tor buffers data that it is waiting to write.
15194 Instead of queueing data cells in an enormous ring buffer for each
15195 client->OR or OR->OR connection, we now queue cells on a separate
15196 queue for each circuit. This lets us use less slack memory, and
15197 will eventually let us be smarter about prioritizing different kinds
15199 - Use memory pools to allocate cells with better speed and memory
15200 efficiency, especially on platforms where malloc() is inefficient.
15201 - Stop reading on edge connections when their corresponding circuit
15202 buffers are full; start again as the circuits empty out.
15204 o Major features, other:
15205 - Add an HSAuthorityRecordStats option that hidden service authorities
15206 can use to track statistics of overall hidden service usage without
15207 logging information that would be very useful to an attacker.
15208 - Start work implementing multi-level keys for directory authorities:
15209 Add a standalone tool to generate key certificates. (Proposal 103.)
15212 - Directory authorities now call routers Stable if they have an
15213 uptime of at least 30 days, even if that's not the median uptime
15214 in the network. Implements proposal 107, suggested by Kevin Bauer
15217 o Minor fixes (resource management):
15218 - Count the number of open sockets separately from the number
15219 of active connection_t objects. This will let us avoid underusing
15220 our allocated connection limit.
15221 - We no longer use socket pairs to link an edge connection to an
15222 anonymous directory connection or a DirPort test connection.
15223 Instead, we track the link internally and transfer the data
15224 in-process. This saves two sockets per "linked" connection (at the
15225 client and at the server), and avoids the nasty Windows socketpair()
15227 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
15228 for every single inactive connection_t. Free items from the
15229 4k/16k-buffer free lists when they haven't been used for a while.
15231 o Minor features (build):
15232 - Make autoconf search for libevent, openssl, and zlib consistently.
15233 - Update deprecated macros in configure.in.
15234 - When warning about missing headers, tell the user to let us
15235 know if the compile succeeds anyway, so we can downgrade the
15237 - Include the current subversion revision as part of the version
15238 string: either fetch it directly if we're in an SVN checkout, do
15239 some magic to guess it if we're in an SVK checkout, or use
15240 the last-detected version if we're building from a .tar.gz.
15241 Use this version consistently in log messages.
15243 o Minor features (logging):
15244 - Always prepend "Bug: " to any log message about a bug.
15245 - Put a platform string (e.g. "Linux i686") in the startup log
15246 message, so when people paste just their logs, we know if it's
15247 OpenBSD or Windows or what.
15248 - When logging memory usage, break down memory used in buffers by
15251 o Minor features (directory system):
15252 - New config option V2AuthoritativeDirectory that all directory
15253 authorities should set. This will let future authorities choose
15254 not to serve V2 directory information.
15255 - Directory authorities allow multiple router descriptors and/or extra
15256 info documents to be uploaded in a single go. This will make
15257 implementing proposal 104 simpler.
15259 o Minor features (controller):
15260 - Add a new config option __DisablePredictedCircuits designed for
15261 use by the controller, when we don't want Tor to build any circuits
15263 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
15264 so we can exit from the middle of the circuit.
15265 - Implement "getinfo status/circuit-established".
15266 - Implement "getinfo status/version/..." so a controller can tell
15267 whether the current version is recommended, and whether any versions
15268 are good, and how many authorities agree. (Patch from shibz.)
15270 o Minor features (hidden services):
15271 - Allow multiple HiddenServicePort directives with the same virtual
15272 port; when they occur, the user is sent round-robin to one
15273 of the target ports chosen at random. Partially fixes bug 393 by
15274 adding limited ad-hoc round-robining.
15276 o Minor features (other):
15278 - Add a new AutomapHostsOnResolve option: when it is enabled, any
15279 resolve request for hosts matching a given pattern causes Tor to
15280 generate an internal virtual address mapping for that host. This
15281 allows DNSPort to work sensibly with hidden service users. By
15282 default, .exit and .onion addresses are remapped; the list of
15283 patterns can be reconfigured with AutomapHostsSuffixes.
15284 - Add an "-F" option to tor-resolve to force a resolve for a .onion
15285 address. Thanks to the AutomapHostsOnResolve option, this is no
15286 longer a completely silly thing to do.
15287 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
15288 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
15289 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
15290 minus 1 byte: the actual maximum declared bandwidth.
15292 o Removed features:
15293 - Removed support for the old binary "version 0" controller protocol.
15294 This has been deprecated since 0.1.1, and warnings have been issued
15295 since 0.1.2. When we encounter a v0 control message, we now send
15296 back an error and close the connection.
15297 - Remove the old "dns worker" server DNS code: it hasn't been default
15298 since 0.1.2.2-alpha, and all the servers seem to be using the new
15301 o Minor bugfixes (portability):
15302 - Even though Windows is equally happy with / and \ as path separators,
15303 try to use \ consistently on Windows and / consistently on Unix: it
15304 makes the log messages nicer.
15305 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
15306 - Read resolv.conf files correctly on platforms where read() returns
15307 partial results on small file reads.
15309 o Minor bugfixes (directory):
15310 - Correctly enforce that elements of directory objects do not appear
15311 more often than they are allowed to appear.
15312 - When we are reporting the DirServer line we just parsed, we were
15313 logging the second stanza of the key fingerprint, not the first.
15315 o Minor bugfixes (logging):
15316 - When we hit an EOF on a log (probably because we're shutting down),
15317 don't try to remove the log from the list: just mark it as
15318 unusable. (Bulletproofs against bug 222.)
15320 o Minor bugfixes (other):
15321 - In the exitlist script, only consider the most recently published
15322 server descriptor for each server. Also, when the user requests
15323 a list of servers that _reject_ connections to a given address,
15324 explicitly exclude the IPs that also have servers that accept
15325 connections to that address. (Resolves bug 405.)
15326 - Stop allowing hibernating servers to be "stable" or "fast".
15327 - On Windows, we were preventing other processes from reading
15328 cached-routers while Tor was running. (Reported by janbar)
15329 - Make the NodeFamilies config option work. (Reported by
15330 lodger -- it has never actually worked, even though we added it
15332 - Check return values from pthread_mutex functions.
15333 - Don't save non-general-purpose router descriptors to the disk cache,
15334 because we have no way of remembering what their purpose was when
15336 - Add even more asserts to hunt down bug 417.
15337 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
15338 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
15339 Add a log message to confirm that it is in fact unlikely.
15341 o Minor bugfixes (controller):
15342 - Make 'getinfo fingerprint' return a 551 error if we're not a
15343 server, so we match what the control spec claims we do. Reported
15345 - Fix a typo in an error message when extendcircuit fails that
15346 caused us to not follow the \r\n-based delimiter protocol. Reported
15349 o Code simplifications and refactoring:
15350 - Stop passing around circuit_t and crypt_path_t pointers that are
15351 implicit in other procedure arguments.
15352 - Drop the old code to choke directory connections when the
15353 corresponding OR connections got full: thanks to the cell queue
15354 feature, OR conns don't get full any more.
15355 - Make dns_resolve() handle attaching connections to circuits
15356 properly, so the caller doesn't have to.
15357 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
15358 - Keep the connection array as a dynamic smartlist_t, rather than as
15359 a fixed-sized array. This is important, as the number of connections
15360 is becoming increasingly decoupled from the number of sockets.
15363 Changes in version 0.1.2.14 - 2007-05-25
15364 Tor 0.1.2.14 changes the addresses of two directory authorities (this
15365 change especially affects those who serve or use hidden services),
15366 and fixes several other crash- and security-related bugs.
15368 o Directory authority changes:
15369 - Two directory authorities (moria1 and moria2) just moved to new
15370 IP addresses. This change will particularly affect those who serve
15371 or use hidden services.
15373 o Major bugfixes (crashes):
15374 - If a directory server runs out of space in the connection table
15375 as it's processing a begin_dir request, it will free the exit stream
15376 but leave it attached to the circuit, leading to unpredictable
15377 behavior. (Reported by seeess, fixes bug 425.)
15378 - Fix a bug in dirserv_remove_invalid() that would cause authorities
15379 to corrupt memory under some really unlikely scenarios.
15380 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
15381 - Avoid segfaults when reading from mmaped descriptor file. (Reported
15384 o Major bugfixes (security):
15385 - When choosing an entry guard for a circuit, avoid using guards
15386 that are in the same family as the chosen exit -- not just guards
15387 that are exactly the chosen exit. (Reported by lodger.)
15389 o Major bugfixes (resource management):
15390 - If a directory authority is down, skip it when deciding where to get
15391 networkstatus objects or descriptors. Otherwise we keep asking
15392 every 10 seconds forever. Fixes bug 384.
15393 - Count it as a failure if we fetch a valid network-status but we
15394 don't want to keep it. Otherwise we'll keep fetching it and keep
15395 not wanting to keep it. Fixes part of bug 422.
15396 - If all of our dirservers have given us bad or no networkstatuses
15397 lately, then stop hammering them once per minute even when we
15398 think they're failed. Fixes another part of bug 422.
15401 - Actually set the purpose correctly for descriptors inserted with
15402 purpose=controller.
15403 - When we have k non-v2 authorities in our DirServer config,
15404 we ignored the last k authorities in the list when updating our
15406 - Correctly back-off from requesting router descriptors that we are
15407 having a hard time downloading.
15408 - Read resolv.conf files correctly on platforms where read() returns
15409 partial results on small file reads.
15410 - Don't rebuild the entire router store every time we get 32K of
15411 routers: rebuild it when the journal gets very large, or when
15412 the gaps in the store get very large.
15415 - When routers publish SVN revisions in their router descriptors,
15416 authorities now include those versions correctly in networkstatus
15418 - Warn when using a version of libevent before 1.3b to run a server on
15419 OSX or BSD: these versions interact badly with userspace threads.
15422 Changes in version 0.1.2.13 - 2007-04-24
15423 This release features some major anonymity fixes, such as safer path
15424 selection; better client performance; faster bootstrapping, better
15425 address detection, and better DNS support for servers; write limiting as
15426 well as read limiting to make servers easier to run; and a huge pile of
15427 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
15429 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
15430 of the Freenode IRC network, remembering his patience and vision for
15431 free speech on the Internet.
15434 - Fix a memory leak when we ask for "all" networkstatuses and we
15435 get one we don't recognize.
15436 - Add more asserts to hunt down bug 417.
15437 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
15440 Changes in version 0.1.2.12-rc - 2007-03-16
15442 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
15443 directory information requested inside Tor connections (i.e. via
15444 begin_dir cells). It only triggered when the same connection was
15445 serving other data at the same time. Reported by seeess.
15448 - When creating a circuit via the controller, send a 'launched'
15449 event when we're done, so we follow the spec better.
15452 Changes in version 0.1.2.11-rc - 2007-03-15
15453 o Minor bugfixes (controller), reported by daejees:
15454 - Correct the control spec to match how the code actually responds
15455 to 'getinfo addr-mappings/*'.
15456 - The control spec described a GUARDS event, but the code
15457 implemented a GUARD event. Standardize on GUARD, but let people
15458 ask for GUARDS too.
15461 Changes in version 0.1.2.10-rc - 2007-03-07
15462 o Major bugfixes (Windows):
15463 - Do not load the NT services library functions (which may not exist)
15464 just to detect if we're a service trying to shut down. Now we run
15465 on Win98 and friends again.
15467 o Minor bugfixes (other):
15468 - Clarify a couple of log messages.
15469 - Fix a misleading socks5 error number.
15472 Changes in version 0.1.2.9-rc - 2007-03-02
15473 o Major bugfixes (Windows):
15474 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
15475 of the usual GCC "%llu". This prevents a bug when saving 64-bit
15476 int configuration values: the high-order 32 bits would get
15477 truncated. In particular, we were being bitten by the default
15478 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
15479 and maybe also bug 397.)
15481 o Minor bugfixes (performance):
15482 - Use OpenSSL's AES implementation on platforms where it's faster.
15483 This could save us as much as 10% CPU usage.
15485 o Minor bugfixes (server):
15486 - Do not rotate onion key immediately after setting it for the first
15489 o Minor bugfixes (directory authorities):
15490 - Stop calling servers that have been hibernating for a long time
15491 "stable". Also, stop letting hibernating or obsolete servers affect
15492 uptime and bandwidth cutoffs.
15493 - Stop listing hibernating servers in the v1 directory.
15495 o Minor bugfixes (hidden services):
15496 - Upload hidden service descriptors slightly less often, to reduce
15497 load on authorities.
15499 o Minor bugfixes (other):
15500 - Fix an assert that could trigger if a controller quickly set then
15501 cleared EntryNodes. Bug found by Udo van den Heuvel.
15502 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
15504 - Fix a potential race condition in the rpm installer. Found by
15506 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
15507 of 2 as indicating that the server is completely bad; it sometimes
15508 means that the server is just bad for the request in question. (may fix
15509 the last of bug 326.)
15510 - Disable encrypted directory connections when we don't have a server
15511 descriptor for the destination. We'll get this working again in
15515 Changes in version 0.1.2.8-beta - 2007-02-26
15516 o Major bugfixes (crashes):
15517 - Stop crashing when the controller asks us to resetconf more than
15518 one config option at once. (Vidalia 0.0.11 does this.)
15519 - Fix a crash that happened on Win98 when we're given command-line
15520 arguments: don't try to load NT service functions from advapi32.dll
15521 except when we need them. (Bug introduced in 0.1.2.7-alpha;
15523 - Fix a longstanding obscure crash bug that could occur when
15524 we run out of DNS worker processes. (Resolves bug 390.)
15526 o Major bugfixes (hidden services):
15527 - Correctly detect whether hidden service descriptor downloads are
15528 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
15530 o Major bugfixes (accounting):
15531 - When we start during an accounting interval before it's time to wake
15532 up, remember to wake up at the correct time. (May fix bug 342.)
15534 o Minor bugfixes (controller):
15535 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
15536 clear the corresponding on_circuit variable, and remember later
15537 that we don't need to send a redundant CLOSED event. Resolves part
15539 - Report events where a resolve succeeded or where we got a socks
15540 protocol error correctly, rather than calling both of them
15542 - Change reported stream target addresses to IP consistently when
15543 we finally get the IP from an exit node.
15544 - Send log messages to the controller even if they happen to be very
15547 o Minor bugfixes (other):
15548 - Display correct results when reporting which versions are
15549 recommended, and how recommended they are. (Resolves bug 383.)
15550 - Improve our estimates for directory bandwidth to be less random:
15551 guess that an unrecognized directory will have the average bandwidth
15552 from all known directories, not that it will have the average
15553 bandwidth from those directories earlier than it on the list.
15554 - If we start a server with ClientOnly 1, then set ClientOnly to 0
15555 and hup, stop triggering an assert based on an empty onion_key.
15556 - On platforms with no working mmap() equivalent, don't warn the
15557 user when cached-routers doesn't exist.
15558 - Warn the user when mmap() [or its equivalent] fails for some reason
15559 other than file-not-found.
15560 - Don't warn the user when cached-routers.new doesn't exist: that's
15561 perfectly fine when starting up for the first time.
15562 - When EntryNodes are configured, rebuild the guard list to contain,
15563 in order: the EntryNodes that were guards before; the rest of the
15564 EntryNodes; the nodes that were guards before.
15565 - Mask out all signals in sub-threads; only the libevent signal
15566 handler should be processing them. This should prevent some crashes
15567 on some machines using pthreads. (Patch from coderman.)
15568 - Fix switched arguments on memset in the implementation of
15569 tor_munmap() for systems with no mmap() call.
15570 - When Tor receives a router descriptor that it asked for, but
15571 no longer wants (because it has received fresh networkstatuses
15572 in the meantime), do not warn the user. Cache the descriptor if
15573 we're a cache; drop it if we aren't.
15574 - Make earlier entry guards _really_ get retried when the network
15576 - On a malformed DNS reply, always give an error to the corresponding
15578 - Build with recent libevents on platforms that do not define the
15579 nonstandard types "u_int8_t" and friends.
15581 o Minor features (controller):
15582 - Warn the user when an application uses the obsolete binary v0
15583 control protocol. We're planning to remove support for it during
15584 the next development series, so it's good to give people some
15586 - Add STREAM_BW events to report per-entry-stream bandwidth
15587 use. (Patch from Robert Hogan.)
15588 - Rate-limit SIGNEWNYM signals in response to controllers that
15589 impolitely generate them for every single stream. (Patch from
15590 mwenge; closes bug 394.)
15591 - Make REMAP stream events have a SOURCE (cache or exit), and
15592 make them generated in every case where we get a successful
15593 connected or resolved cell.
15595 o Minor bugfixes (performance):
15596 - Call router_have_min_dir_info half as often. (This is showing up in
15597 some profiles, but not others.)
15598 - When using GCC, make log_debug never get called at all, and its
15599 arguments never get evaluated, when no debug logs are configured.
15600 (This is showing up in some profiles, but not others.)
15603 - Remove some never-implemented options. Mark PathlenCoinWeight as
15605 - Implement proposal 106: Stop requiring clients to have well-formed
15606 certificates; stop checking nicknames in certificates. (Clients
15607 have certificates so that they can look like Tor servers, but in
15608 the future we might want to allow them to look like regular TLS
15609 clients instead. Nicknames in certificates serve no purpose other
15610 than making our protocol easier to recognize on the wire.)
15611 - Revise messages on handshake failure again to be even more clear about
15612 which are incoming connections and which are outgoing.
15613 - Discard any v1 directory info that's over 1 month old (for
15614 directories) or over 1 week old (for running-routers lists).
15615 - Do not warn when individual nodes in the configuration's EntryNodes,
15616 ExitNodes, etc are down: warn only when all possible nodes
15617 are down. (Fixes bug 348.)
15618 - Always remove expired routers and networkstatus docs before checking
15619 whether we have enough information to build circuits. (Fixes
15621 - Put a lower-bound on MaxAdvertisedBandwidth.
15624 Changes in version 0.1.2.7-alpha - 2007-02-06
15625 o Major bugfixes (rate limiting):
15626 - Servers decline directory requests much more aggressively when
15627 they're low on bandwidth. Otherwise they end up queueing more and
15628 more directory responses, which can't be good for latency.
15629 - But never refuse directory requests from local addresses.
15630 - Fix a memory leak when sending a 503 response for a networkstatus
15632 - Be willing to read or write on local connections (e.g. controller
15633 connections) even when the global rate limiting buckets are empty.
15634 - If our system clock jumps back in time, don't publish a negative
15635 uptime in the descriptor. Also, don't let the global rate limiting
15636 buckets go absurdly negative.
15637 - Flush local controller connection buffers periodically as we're
15638 writing to them, so we avoid queueing 4+ megabytes of data before
15641 o Major bugfixes (NT services):
15642 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
15643 command-line flag so that admins can override the default by saying
15644 "tor --service install --user "SomeUser"". This will not affect
15645 existing installed services. Also, warn the user that the service
15646 will look for its configuration file in the service user's
15647 %appdata% directory. (We can't do the 'hardwire the user's appdata
15648 directory' trick any more, since we may not have read access to that
15651 o Major bugfixes (other):
15652 - Previously, we would cache up to 16 old networkstatus documents
15653 indefinitely, if they came from nontrusted authorities. Now we
15654 discard them if they are more than 10 days old.
15655 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
15657 - Detect and reject malformed DNS responses containing circular
15659 - If exits are rare enough that we're not marking exits as guards,
15660 ignore exit bandwidth when we're deciding the required bandwidth
15662 - When we're handling a directory connection tunneled over Tor,
15663 don't fill up internal memory buffers with all the data we want
15664 to tunnel; instead, only add it if the OR connection that will
15665 eventually receive it has some room for it. (This can lead to
15666 slowdowns in tunneled dir connections; a better solution will have
15667 to wait for 0.2.0.)
15669 o Minor bugfixes (dns):
15670 - Add some defensive programming to eventdns.c in an attempt to catch
15671 possible memory-stomping bugs.
15672 - Detect and reject DNS replies containing IPv4 or IPv6 records with
15673 an incorrect number of bytes. (Previously, we would ignore the
15675 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
15676 in the correct order, and doesn't crash.
15677 - Free memory held in recently-completed DNS lookup attempts on exit.
15678 This was not a memory leak, but may have been hiding memory leaks.
15679 - Handle TTL values correctly on reverse DNS lookups.
15680 - Treat failure to parse resolv.conf as an error.
15682 o Minor bugfixes (other):
15683 - Fix crash with "tor --list-fingerprint" (reported by seeess).
15684 - When computing clock skew from directory HTTP headers, consider what
15685 time it was when we finished asking for the directory, not what
15687 - Expire socks connections if they spend too long waiting for the
15688 handshake to finish. Previously we would let them sit around for
15689 days, if the connecting application didn't close them either.
15690 - And if the socks handshake hasn't started, don't send a
15691 "DNS resolve socks failed" handshake reply; just close it.
15692 - Stop using C functions that OpenBSD's linker doesn't like.
15693 - Don't launch requests for descriptors unless we have networkstatuses
15694 from at least half of the authorities. This delays the first
15695 download slightly under pathological circumstances, but can prevent
15696 us from downloading a bunch of descriptors we don't need.
15697 - Do not log IPs with TLS failures for incoming TLS
15698 connections. (Fixes bug 382.)
15699 - If the user asks to use invalid exit nodes, be willing to use
15701 - Stop using the reserved ac_cv namespace in our configure script.
15702 - Call stat() slightly less often; use fstat() when possible.
15703 - Refactor the way we handle pending circuits when an OR connection
15704 completes or fails, in an attempt to fix a rare crash bug.
15705 - Only rewrite a conn's address based on X-Forwarded-For: headers
15706 if it's a parseable public IP address; and stop adding extra quotes
15707 to the resulting address.
15710 - Weight directory requests by advertised bandwidth. Now we can
15711 let servers enable write limiting but still allow most clients to
15712 succeed at their directory requests. (We still ignore weights when
15713 choosing a directory authority; I hope this is a feature.)
15716 - Create a new file ReleaseNotes which was the old ChangeLog. The
15717 new ChangeLog file now includes the summaries for all development
15719 - Check for addresses with invalid characters at the exit as well
15720 as at the client, and warn less verbosely when they fail. You can
15721 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
15722 - Adapt a patch from goodell to let the contrib/exitlist script
15723 take arguments rather than require direct editing.
15724 - Inform the server operator when we decide not to advertise a
15725 DirPort due to AccountingMax enabled or a low BandwidthRate. It
15726 was confusing Zax, so now we're hopefully more helpful.
15727 - Bring us one step closer to being able to establish an encrypted
15728 directory tunnel without knowing a descriptor first. Still not
15729 ready yet. As part of the change, now assume we can use a
15730 create_fast cell if we don't know anything about a router.
15731 - Allow exit nodes to use nameservers running on ports other than 53.
15732 - Servers now cache reverse DNS replies.
15733 - Add an --ignore-missing-torrc command-line option so that we can
15734 get the "use sensible defaults if the configuration file doesn't
15735 exist" behavior even when specifying a torrc location on the command
15738 o Minor features (controller):
15739 - Track reasons for OR connection failure; make these reasons
15740 available via the controller interface. (Patch from Mike Perry.)
15741 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
15742 can learn when clients are sending malformed hostnames to Tor.
15743 - Clean up documentation for controller status events.
15744 - Add a REMAP status to stream events to note that a stream's
15745 address has changed because of a cached address or a MapAddress
15749 Changes in version 0.1.2.6-alpha - 2007-01-09
15751 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
15752 connection handles more than 4 gigs in either direction, we crash.
15753 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
15754 advertised exit node, somebody might try to exit from us when
15755 we're bootstrapping and before we've built our descriptor yet.
15756 Refuse the connection rather than crashing.
15759 - Warn if we (as a server) find that we've resolved an address that we
15760 weren't planning to resolve.
15761 - Warn that using select() on any libevent version before 1.1 will be
15762 unnecessarily slow (even for select()).
15763 - Flush ERR-level controller status events just like we currently
15764 flush ERR-level log events, so that a Tor shutdown doesn't prevent
15765 the controller from learning about current events.
15767 o Minor features (more controller status events):
15768 - Implement EXTERNAL_ADDRESS server status event so controllers can
15769 learn when our address changes.
15770 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
15771 can learn when directories reject our descriptor.
15772 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
15773 can learn when a client application is speaking a non-socks protocol
15775 - Implement DANGEROUS_SOCKS client status event so controllers
15776 can learn when a client application is leaking DNS addresses.
15777 - Implement BUG general status event so controllers can learn when
15778 Tor is unhappy about its internal invariants.
15779 - Implement CLOCK_SKEW general status event so controllers can learn
15780 when Tor thinks the system clock is set incorrectly.
15781 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
15782 server status events so controllers can learn when their descriptors
15783 are accepted by a directory.
15784 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
15785 server status events so controllers can learn about Tor's progress in
15786 deciding whether it's reachable from the outside.
15787 - Implement BAD_LIBEVENT general status event so controllers can learn
15788 when we have a version/method combination in libevent that needs to
15790 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
15791 and DNS_USELESS server status events so controllers can learn
15792 about changes to DNS server status.
15794 o Minor features (directory):
15795 - Authorities no longer recommend exits as guards if this would shift
15796 too much load to the exit nodes.
15799 Changes in version 0.1.2.5-alpha - 2007-01-06
15801 - Enable write limiting as well as read limiting. Now we sacrifice
15802 capacity if we're pushing out lots of directory traffic, rather
15803 than overrunning the user's intended bandwidth limits.
15804 - Include TLS overhead when counting bandwidth usage; previously, we
15805 would count only the bytes sent over TLS, but not the bytes used
15807 - Support running the Tor service with a torrc not in the same
15808 directory as tor.exe and default to using the torrc located in
15809 the %appdata%\Tor\ of the user who installed the service. Patch
15811 - Servers now check for the case when common DNS requests are going to
15812 wildcarded addresses (i.e. all getting the same answer), and change
15813 their exit policy to reject *:* if it's happening.
15814 - Implement BEGIN_DIR cells, so we can connect to the directory
15815 server via TLS to do encrypted directory requests rather than
15816 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
15817 config options if you like.
15819 o Minor features (config and docs):
15820 - Start using the state file to store bandwidth accounting data:
15821 the bw_accounting file is now obsolete. We'll keep generating it
15822 for a while for people who are still using 0.1.2.4-alpha.
15823 - Try to batch changes to the state file so that we do as few
15824 disk writes as possible while still storing important things in
15826 - The state file and the bw_accounting file get saved less often when
15827 the AvoidDiskWrites config option is set.
15828 - Make PIDFile work on Windows (untested).
15829 - Add internal descriptions for a bunch of configuration options:
15830 accessible via controller interface and in comments in saved
15832 - Reject *:563 (NNTPS) in the default exit policy. We already reject
15833 NNTP by default, so this seems like a sensible addition.
15834 - Clients now reject hostnames with invalid characters. This should
15835 avoid some inadvertent info leaks. Add an option
15836 AllowNonRFC953Hostnames to disable this behavior, in case somebody
15837 is running a private network with hosts called @, !, and #.
15838 - Add a maintainer script to tell us which options are missing
15839 documentation: "make check-docs".
15840 - Add a new address-spec.txt document to describe our special-case
15841 addresses: .exit, .onion, and .noconnnect.
15843 o Minor features (DNS):
15844 - Ongoing work on eventdns infrastructure: now it has dns server
15845 and ipv6 support. One day Tor will make use of it.
15846 - Add client-side caching for reverse DNS lookups.
15847 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
15848 - When we change nameservers or IP addresses, reset and re-launch
15849 our tests for DNS hijacking.
15851 o Minor features (directory):
15852 - Authorities now specify server versions in networkstatus. This adds
15853 about 2% to the size of compressed networkstatus docs, and allows
15854 clients to tell which servers support BEGIN_DIR and which don't.
15855 The implementation is forward-compatible with a proposed future
15856 protocol version scheme not tied to Tor versions.
15857 - DirServer configuration lines now have an orport= option so
15858 clients can open encrypted tunnels to the authorities without
15859 having downloaded their descriptors yet. Enabled for moria1,
15860 moria2, tor26, and lefkada now in the default configuration.
15861 - Directory servers are more willing to send a 503 "busy" if they
15862 are near their write limit, especially for v1 directory requests.
15863 Now they can use their limited bandwidth for actual Tor traffic.
15864 - Clients track responses with status 503 from dirservers. After a
15865 dirserver has given us a 503, we try not to use it until an hour has
15866 gone by, or until we have no dirservers that haven't given us a 503.
15867 - When we get a 503 from a directory, and we're not a server, we don't
15868 count the failure against the total number of failures allowed
15869 for the thing we're trying to download.
15870 - Report X-Your-Address-Is correctly from tunneled directory
15871 connections; don't report X-Your-Address-Is when it's an internal
15872 address; and never believe reported remote addresses when they're
15874 - Protect against an unlikely DoS attack on directory servers.
15875 - Add a BadDirectory flag to network status docs so that authorities
15876 can (eventually) tell clients about caches they believe to be
15879 o Minor features (controller):
15880 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
15881 - Reimplement GETINFO so that info/names stays in sync with the
15883 - Implement "GETINFO fingerprint".
15884 - Implement "SETEVENTS GUARD" so controllers can get updates on
15885 entry guard status as it changes.
15887 o Minor features (clean up obsolete pieces):
15888 - Remove some options that have been deprecated since at least
15889 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
15890 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
15891 to set log options.
15892 - We no longer look for identity and onion keys in "identity.key" and
15893 "onion.key" -- these were replaced by secret_id_key and
15894 secret_onion_key in 0.0.8pre1.
15895 - We no longer require unrecognized directory entries to be
15898 o Major bugfixes (security):
15899 - Stop sending the HttpProxyAuthenticator string to directory
15900 servers when directory connections are tunnelled through Tor.
15901 - Clients no longer store bandwidth history in the state file.
15902 - Do not log introduction points for hidden services if SafeLogging
15904 - When generating bandwidth history, round down to the nearest
15905 1k. When storing accounting data, round up to the nearest 1k.
15906 - When we're running as a server, remember when we last rotated onion
15907 keys, so that we will rotate keys once they're a week old even if
15908 we never stay up for a week ourselves.
15910 o Major bugfixes (other):
15911 - Fix a longstanding bug in eventdns that prevented the count of
15912 timed-out resolves from ever being reset. This bug caused us to
15913 give up on a nameserver the third time it timed out, and try it
15914 10 seconds later... and to give up on it every time it timed out
15916 - Take out the '5 second' timeout from the connection retry
15917 schedule. Now the first connect attempt will wait a full 10
15918 seconds before switching to a new circuit. Perhaps this will help
15919 a lot. Based on observations from Mike Perry.
15920 - Fix a bug on the Windows implementation of tor_mmap_file() that
15921 would prevent the cached-routers file from ever loading. Reported
15925 - Fix an assert failure when a directory authority sets
15926 AuthDirRejectUnlisted and then receives a descriptor from an
15927 unlisted router. Reported by seeess.
15928 - Avoid a double-free when parsing malformed DirServer lines.
15929 - Fix a bug when a BSD-style PF socket is first used. Patch from
15931 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
15932 to resolve an address at a given exit node even when they ask for
15934 - Servers no longer ever list themselves in their "family" line,
15935 even if configured to do so. This makes it easier to configure
15936 family lists conveniently.
15937 - When running as a server, don't fall back to 127.0.0.1 when no
15938 nameservers are configured in /etc/resolv.conf; instead, make the
15939 user fix resolv.conf or specify nameservers explicitly. (Resolves
15941 - Stop accepting certain malformed ports in configured exit policies.
15942 - Don't re-write the fingerprint file every restart, unless it has
15944 - Stop warning when a single nameserver fails: only warn when _all_ of
15945 our nameservers have failed. Also, when we only have one nameserver,
15946 raise the threshold for deciding that the nameserver is dead.
15947 - Directory authorities now only decide that routers are reachable
15948 if their identity keys are as expected.
15949 - When the user uses bad syntax in the Log config line, stop
15950 suggesting other bad syntax as a replacement.
15951 - Correctly detect ipv6 DNS capability on OpenBSD.
15953 o Minor bugfixes (controller):
15954 - Report the circuit number correctly in STREAM CLOSED events. Bug
15955 reported by Mike Perry.
15956 - Do not report bizarre values for results of accounting GETINFOs
15957 when the last second's write or read exceeds the allotted bandwidth.
15958 - Report "unrecognized key" rather than an empty string when the
15959 controller tries to fetch a networkstatus that doesn't exist.
15962 Changes in version 0.1.1.26 - 2006-12-14
15963 o Security bugfixes:
15964 - Stop sending the HttpProxyAuthenticator string to directory
15965 servers when directory connections are tunnelled through Tor.
15966 - Clients no longer store bandwidth history in the state file.
15967 - Do not log introduction points for hidden services if SafeLogging
15971 - Fix an assert failure when a directory authority sets
15972 AuthDirRejectUnlisted and then receives a descriptor from an
15973 unlisted router (reported by seeess).
15976 Changes in version 0.1.2.4-alpha - 2006-12-03
15978 - Add support for using natd; this allows FreeBSDs earlier than
15979 5.1.2 to have ipfw send connections through Tor without using
15980 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
15983 - Make all connections to addresses of the form ".noconnect"
15984 immediately get closed. This lets application/controller combos
15985 successfully test whether they're talking to the same Tor by
15986 watching for STREAM events.
15987 - Make cross.sh cross-compilation script work even when autogen.sh
15988 hasn't been run. (Patch from Michael Mohr.)
15989 - Statistics dumped by -USR2 now include a breakdown of public key
15990 operations, for profiling.
15993 - Fix a major leak when directory authorities parse their
15994 approved-routers list, a minor memory leak when we fail to pick
15995 an exit node, and a few rare leaks on errors.
15996 - Handle TransPort connections even when the server sends data before
15997 the client sends data. Previously, the connection would just hang
15998 until the client sent data. (Patch from tup based on patch from
16000 - Avoid assert failure when our cached-routers file is empty on
16004 - Don't log spurious warnings when we see a circuit close reason we
16005 don't recognize; it's probably just from a newer version of Tor.
16006 - Have directory authorities allow larger amounts of drift in uptime
16007 without replacing the server descriptor: previously, a server that
16008 restarted every 30 minutes could have 48 "interesting" descriptors
16010 - Start linking to the Tor specification and Tor reference manual
16011 correctly in the Windows installer.
16012 - Add Vidalia to the OS X uninstaller script, so when we uninstall
16013 Tor/Privoxy we also uninstall Vidalia.
16014 - Resume building on Irix64, and fix a lot of warnings from its
16015 MIPSpro C compiler.
16016 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
16017 when we're running as a client.
16020 Changes in version 0.1.1.25 - 2006-11-04
16022 - When a client asks us to resolve (rather than connect to)
16023 an address, and we have a cached answer, give them the cached
16024 answer. Previously, we would give them no answer at all.
16025 - We were building exactly the wrong circuits when we predict
16026 hidden service requirements, meaning Tor would have to build all
16027 its circuits on demand.
16028 - If none of our live entry guards have a high uptime, but we
16029 require a guard with a high uptime, try adding a new guard before
16030 we give up on the requirement. This patch should make long-lived
16031 connections more stable on average.
16032 - When testing reachability of our DirPort, don't launch new
16033 tests when there's already one in progress -- unreachable
16034 servers were stacking up dozens of testing streams.
16036 o Security bugfixes:
16037 - When the user sends a NEWNYM signal, clear the client-side DNS
16038 cache too. Otherwise we continue to act on previous information.
16041 - Avoid a memory corruption bug when creating a hash table for
16043 - Avoid possibility of controller-triggered crash when misusing
16044 certain commands from a v0 controller on platforms that do not
16045 handle printf("%s",NULL) gracefully.
16046 - Avoid infinite loop on unexpected controller input.
16047 - Don't log spurious warnings when we see a circuit close reason we
16048 don't recognize; it's probably just from a newer version of Tor.
16049 - Add Vidalia to the OS X uninstaller script, so when we uninstall
16050 Tor/Privoxy we also uninstall Vidalia.
16053 Changes in version 0.1.2.3-alpha - 2006-10-29
16055 - Prepare for servers to publish descriptors less often: never
16056 discard a descriptor simply for being too old until either it is
16057 recommended by no authorities, or until we get a better one for
16058 the same router. Make caches consider retaining old recommended
16059 routers for even longer.
16060 - If most authorities set a BadExit flag for a server, clients
16061 don't think of it as a general-purpose exit. Clients only consider
16062 authorities that advertise themselves as listing bad exits.
16063 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
16064 headers for content, so that we can work better in the presence of
16065 caching HTTP proxies.
16066 - Allow authorities to list nodes as bad exits by fingerprint or by
16069 o Minor features, controller:
16070 - Add a REASON field to CIRC events; for backward compatibility, this
16071 field is sent only to controllers that have enabled the extended
16072 event format. Also, add additional reason codes to explain why
16073 a given circuit has been destroyed or truncated. (Patches from
16075 - Add a REMOTE_REASON field to extended CIRC events to tell the
16076 controller about why a remote OR told us to close a circuit.
16077 - Stream events also now have REASON and REMOTE_REASON fields,
16078 working much like those for circuit events.
16079 - There's now a GETINFO ns/... field so that controllers can ask Tor
16080 about the current status of a router.
16081 - A new event type "NS" to inform a controller when our opinion of
16082 a router's status has changed.
16083 - Add a GETINFO events/names and GETINFO features/names so controllers
16084 can tell which events and features are supported.
16085 - A new CLEARDNSCACHE signal to allow controllers to clear the
16086 client-side DNS cache without expiring circuits.
16088 o Security bugfixes:
16089 - When the user sends a NEWNYM signal, clear the client-side DNS
16090 cache too. Otherwise we continue to act on previous information.
16093 - Avoid sending junk to controllers or segfaulting when a controller
16094 uses EVENT_NEW_DESC with verbose nicknames.
16095 - Stop triggering asserts if the controller tries to extend hidden
16096 service circuits (reported by mwenge).
16097 - Avoid infinite loop on unexpected controller input.
16098 - When the controller does a "GETINFO network-status", tell it
16099 about even those routers whose descriptors are very old, and use
16100 long nicknames where appropriate.
16101 - Change NT service functions to be loaded on demand. This lets us
16102 build with MinGW without breaking Tor for Windows 98 users.
16103 - Do DirPort reachability tests less often, since a single test
16104 chews through many circuits before giving up.
16105 - In the hidden service example in torrc.sample, stop recommending
16106 esoteric and discouraged hidden service options.
16107 - When stopping an NT service, wait up to 10 sec for it to actually
16108 stop. Patch from Matt Edman; resolves bug 295.
16109 - Fix handling of verbose nicknames with ORCONN controller events:
16110 make them show up exactly when requested, rather than exactly when
16112 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
16113 printing a duplicate "$" in the keys we send (reported by mwenge).
16114 - Correctly set maximum connection limit on Cygwin. (This time
16116 - Try to detect Windows correctly when cross-compiling.
16117 - Detect the size of the routers file correctly even if it is
16118 corrupted (on systems without mmap) or not page-aligned (on systems
16119 with mmap). This bug was harmless.
16120 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
16121 to open a stream fails; now we do in more cases. This should
16122 make clients able to find a good exit faster in some cases, since
16123 unhandleable requests will now get an error rather than timing out.
16124 - Resolve two memory leaks when rebuilding the on-disk router cache
16125 (reported by fookoowa).
16126 - Clean up minor code warnings suggested by the MIPSpro C compiler,
16127 and reported by some Centos users.
16128 - Controller signals now work on non-Unix platforms that don't define
16129 SIGUSR1 and SIGUSR2 the way we expect.
16130 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
16131 values before failing, and always enables eventdns.
16132 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
16133 Try to fix this in configure.in by checking for most functions
16134 before we check for libevent.
16137 Changes in version 0.1.2.2-alpha - 2006-10-07
16139 - Make our async eventdns library on-by-default for Tor servers,
16140 and plan to deprecate the separate dnsworker threads.
16141 - Add server-side support for "reverse" DNS lookups (using PTR
16142 records so clients can determine the canonical hostname for a given
16143 IPv4 address). Only supported by servers using eventdns; servers
16144 now announce in their descriptors whether they support eventdns.
16145 - Specify and implement client-side SOCKS5 interface for reverse DNS
16146 lookups (see doc/socks-extensions.txt).
16147 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
16148 connect to directory servers through Tor. Previously, clients needed
16149 to find Tor exits to make private connections to directory servers.
16150 - Avoid choosing Exit nodes for entry or middle hops when the
16151 total bandwidth available from non-Exit nodes is much higher than
16152 the total bandwidth available from Exit nodes.
16153 - Workaround for name servers (like Earthlink's) that hijack failing
16154 DNS requests and replace the no-such-server answer with a "helpful"
16155 redirect to an advertising-driven search portal. Also work around
16156 DNS hijackers who "helpfully" decline to hijack known-invalid
16157 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
16158 lets you turn it off.
16159 - Send out a burst of long-range padding cells once we've established
16160 that we're reachable. Spread them over 4 circuits, so hopefully
16161 a few will be fast. This exercises our bandwidth and bootstraps
16162 us into the directory more quickly.
16164 o New/improved config options:
16165 - Add new config option "ResolvConf" to let the server operator
16166 choose an alternate resolve.conf file when using eventdns.
16167 - Add an "EnforceDistinctSubnets" option to control our "exclude
16168 servers on the same /16" behavior. It's still on by default; this
16169 is mostly for people who want to operate private test networks with
16170 all the machines on the same subnet.
16171 - If one of our entry guards is on the ExcludeNodes list, or the
16172 directory authorities don't think it's a good guard, treat it as
16173 if it were unlisted: stop using it as a guard, and throw it off
16174 the guards list if it stays that way for a long time.
16175 - Allow directory authorities to be marked separately as authorities
16176 for the v1 directory protocol, the v2 directory protocol, and
16177 as hidden service directories, to make it easier to retire old
16178 authorities. V1 authorities should set "HSAuthoritativeDir 1"
16179 to continue being hidden service authorities too.
16180 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
16182 o Minor features, controller:
16183 - Fix CIRC controller events so that controllers can learn the
16184 identity digests of non-Named servers used in circuit paths.
16185 - Let controllers ask for more useful identifiers for servers. Instead
16186 of learning identity digests for un-Named servers and nicknames
16187 for Named servers, the new identifiers include digest, nickname,
16188 and indication of Named status. Off by default; see control-spec.txt
16189 for more information.
16190 - Add a "getinfo address" controller command so it can display Tor's
16191 best guess to the user.
16192 - New controller event to alert the controller when our server
16193 descriptor has changed.
16194 - Give more meaningful errors on controller authentication failure.
16196 o Minor features, other:
16197 - When asked to resolve a hostname, don't use non-exit servers unless
16198 requested to do so. This allows servers with broken DNS to be
16199 useful to the network.
16200 - Divide eventdns log messages into warn and info messages.
16201 - Reserve the nickname "Unnamed" for routers that can't pick
16202 a hostname: any router can call itself Unnamed; directory
16203 authorities will never allocate Unnamed to any particular router;
16204 clients won't believe that any router is the canonical Unnamed.
16205 - Only include function names in log messages for info/debug messages.
16206 For notice/warn/err, the content of the message should be clear on
16207 its own, and printing the function name only confuses users.
16208 - Avoid some false positives during reachability testing: don't try
16209 to test via a server that's on the same /24 as us.
16210 - If we fail to build a circuit to an intended enclave, and it's
16211 not mandatory that we use that enclave, stop wanting it.
16212 - When eventdns is enabled, allow multithreaded builds on NetBSD and
16213 OpenBSD. (We had previously disabled threads on these platforms
16214 because they didn't have working thread-safe resolver functions.)
16216 o Major bugfixes, anonymity/security:
16217 - If a client asked for a server by name, and there's a named server
16218 in our network-status but we don't have its descriptor yet, we
16219 could return an unnamed server instead.
16220 - Fix NetBSD bug that could allow someone to force uninitialized RAM
16221 to be sent to a server's DNS resolver. This only affects NetBSD
16222 and other platforms that do not bounds-check tolower().
16223 - Reject (most) attempts to use Tor circuits with length one. (If
16224 many people start using Tor as a one-hop proxy, exit nodes become
16225 a more attractive target for compromise.)
16226 - Just because your DirPort is open doesn't mean people should be
16227 able to remotely teach you about hidden service descriptors. Now
16228 only accept rendezvous posts if you've got HSAuthoritativeDir set.
16230 o Major bugfixes, other:
16231 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
16232 - When a client asks the server to resolve (not connect to)
16233 an address, and it has a cached answer, give them the cached answer.
16234 Previously, the server would give them no answer at all.
16235 - Allow really slow clients to not hang up five minutes into their
16236 directory downloads (suggested by Adam J. Richter).
16237 - We were building exactly the wrong circuits when we anticipated
16238 hidden service requirements, meaning Tor would have to build all
16239 its circuits on demand.
16240 - Avoid crashing when we mmap a router cache file of size 0.
16241 - When testing reachability of our DirPort, don't launch new
16242 tests when there's already one in progress -- unreachable
16243 servers were stacking up dozens of testing streams.
16245 o Minor bugfixes, correctness:
16246 - If we're a directory mirror and we ask for "all" network status
16247 documents, we would discard status documents from authorities
16248 we don't recognize.
16249 - Avoid a memory corruption bug when creating a hash table for
16251 - Avoid controller-triggered crash when misusing certain commands
16252 from a v0 controller on platforms that do not handle
16253 printf("%s",NULL) gracefully.
16254 - Don't crash when a controller sends a third argument to an
16255 "extendcircuit" request.
16256 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
16257 response; fix error code when "getinfo dir/status/" fails.
16258 - Avoid crash when telling controller stream-status and a stream
16260 - Patch from Adam Langley to fix assert() in eventdns.c.
16261 - Fix a debug log message in eventdns to say "X resolved to Y"
16262 instead of "X resolved to X".
16263 - Make eventdns give strings for DNS errors, not just error numbers.
16264 - Track unreachable entry guards correctly: don't conflate
16265 'unreachable by us right now' with 'listed as down by the directory
16266 authorities'. With the old code, if a guard was unreachable by
16267 us but listed as running, it would clog our guard list forever.
16268 - Behave correctly in case we ever have a network with more than
16269 2GB/s total advertised capacity.
16270 - Make TrackExitHosts case-insensitive, and fix the behavior of
16271 ".suffix" TrackExitHosts items to avoid matching in the middle of
16273 - Finally fix the openssl warnings from newer gccs that believe that
16274 ignoring a return value is okay, but casting a return value and
16275 then ignoring it is a sign of madness.
16276 - Prevent the contrib/exitlist script from printing the same
16277 result more than once.
16278 - Patch from Steve Hildrey: Generate network status correctly on
16279 non-versioning dirservers.
16280 - Don't listen to the X-Your-Address-Is hint if you did the lookup
16281 via Tor; otherwise you'll think you're the exit node's IP address.
16283 o Minor bugfixes, performance:
16284 - Two small performance improvements on parsing descriptors.
16285 - Major performance improvement on inserting descriptors: change
16286 algorithm from O(n^2) to O(n).
16287 - Make the common memory allocation path faster on machines where
16288 malloc(0) returns a pointer.
16289 - Start remembering X-Your-Address-Is directory hints even if you're
16290 a client, so you can become a server more smoothly.
16291 - Avoid duplicate entries on MyFamily line in server descriptor.
16293 o Packaging, features:
16294 - Remove architecture from OS X builds. The official builds are
16295 now universal binaries.
16296 - The Debian package now uses --verify-config when (re)starting,
16297 to distinguish configuration errors from other errors.
16298 - Update RPMs to require libevent 1.1b.
16300 o Packaging, bugfixes:
16301 - Patches so Tor builds with MinGW on Windows.
16302 - Patches so Tor might run on Cygwin again.
16303 - Resume building on non-gcc compilers and ancient gcc. Resume
16304 building with the -O0 compile flag. Resume building cleanly on
16306 - Run correctly on OS X platforms with case-sensitive filesystems.
16307 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
16308 - Add autoconf checks so Tor can build on Solaris x86 again.
16311 - Documented (and renamed) ServerDNSSearchDomains and
16312 ServerDNSResolvConfFile options.
16313 - Be clearer that the *ListenAddress directives can be repeated
16317 Changes in version 0.1.1.24 - 2006-09-29
16319 - Allow really slow clients to not hang up five minutes into their
16320 directory downloads (suggested by Adam J. Richter).
16321 - Fix major performance regression from 0.1.0.x: instead of checking
16322 whether we have enough directory information every time we want to
16323 do something, only check when the directory information has changed.
16324 This should improve client CPU usage by 25-50%.
16325 - Don't crash if, after a server has been running for a while,
16326 it can't resolve its hostname.
16329 - Allow Tor to start when RunAsDaemon is set but no logs are set.
16330 - Don't crash when the controller receives a third argument to an
16331 "extendcircuit" request.
16332 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
16333 response; fix error code when "getinfo dir/status/" fails.
16334 - Fix configure.in to not produce broken configure files with
16335 more recent versions of autoconf. Thanks to Clint for his auto*
16337 - Fix security bug on NetBSD that could allow someone to force
16338 uninitialized RAM to be sent to a server's DNS resolver. This
16339 only affects NetBSD and other platforms that do not bounds-check
16341 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
16342 methods: these are known to be buggy.
16343 - If we're a directory mirror and we ask for "all" network status
16344 documents, we would discard status documents from authorities
16345 we don't recognize.
16348 Changes in version 0.1.2.1-alpha - 2006-08-27
16350 - Add "eventdns" async dns library from Adam Langley, tweaked to
16351 build on OSX and Windows. Only enabled if you pass the
16352 --enable-eventdns argument to configure.
16353 - Allow servers with no hostname or IP address to learn their
16354 IP address by asking the directory authorities. This code only
16355 kicks in when you would normally have exited with a "no address"
16356 error. Nothing's authenticated, so use with care.
16357 - Rather than waiting a fixed amount of time between retrying
16358 application connections, we wait only 5 seconds for the first,
16359 10 seconds for the second, and 15 seconds for each retry after
16360 that. Hopefully this will improve the expected user experience.
16361 - Patch from Tup to add support for transparent AP connections:
16362 this basically bundles the functionality of trans-proxy-tor
16363 into the Tor mainline. Now hosts with compliant pf/netfilter
16364 implementations can redirect TCP connections straight to Tor
16365 without diverting through SOCKS. Needs docs.
16366 - Busy directory servers save lots of memory by spooling server
16367 descriptors, v1 directories, and v2 networkstatus docs to buffers
16368 as needed rather than en masse. Also mmap the cached-routers
16369 files, so we don't need to keep the whole thing in memory too.
16370 - Automatically avoid picking more than one node from the same
16371 /16 network when constructing a circuit.
16372 - Revise and clean up the torrc.sample that we ship with; add
16373 a section for BandwidthRate and BandwidthBurst.
16376 - Split circuit_t into origin_circuit_t and or_circuit_t, and
16377 split connection_t into edge, or, dir, control, and base structs.
16378 These will save quite a bit of memory on busy servers, and they'll
16379 also help us track down bugs in the code and bugs in the spec.
16380 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
16381 or later. Log when we are doing this, so we can diagnose it when
16382 it fails. (Also, recommend libevent 1.1b for kqueue and
16383 win32 methods; deprecate libevent 1.0b harder; make libevent
16384 recommendation system saner.)
16385 - Start being able to build universal binaries on OS X (thanks
16387 - Export the default exit policy via the control port, so controllers
16388 don't need to guess what it is / will be later.
16389 - Add a man page entry for ProtocolWarnings.
16390 - Add TestVia config option to the man page.
16391 - Remove even more protocol-related warnings from Tor server logs,
16392 such as bad TLS handshakes and malformed begin cells.
16393 - Stop fetching descriptors if you're not a dir mirror and you
16394 haven't tried to establish any circuits lately. [This currently
16395 causes some dangerous behavior, because when you start up again
16396 you'll use your ancient server descriptors.]
16397 - New DirPort behavior: if you have your dirport set, you download
16398 descriptors aggressively like a directory mirror, whether or not
16399 your ORPort is set.
16400 - Get rid of the router_retry_connections notion. Now routers
16401 no longer try to rebuild long-term connections to directory
16402 authorities, and directory authorities no longer try to rebuild
16403 long-term connections to all servers. We still don't hang up
16404 connections in these two cases though -- we need to look at it
16405 more carefully to avoid flapping, and we likely need to wait til
16406 0.1.1.x is obsolete.
16407 - Drop compatibility with obsolete Tors that permit create cells
16408 to have the wrong circ_id_type.
16409 - Re-enable per-connection rate limiting. Get rid of the "OP
16410 bandwidth" concept. Lay groundwork for "bandwidth classes" --
16411 separate global buckets that apply depending on what sort of conn
16413 - Start publishing one minute or so after we find our ORPort
16414 to be reachable. This will help reduce the number of descriptors
16415 we have for ourselves floating around, since it's quite likely
16416 other things (e.g. DirPort) will change during that minute too.
16417 - Fork the v1 directory protocol into its own spec document,
16418 and mark dir-spec.txt as the currently correct (v2) spec.
16421 - When we find our DirPort to be reachable, publish a new descriptor
16422 so we'll tell the world (reported by pnx).
16423 - Publish a new descriptor after we hup/reload. This is important
16424 if our config has changed such that we'll want to start advertising
16425 our DirPort now, etc.
16426 - Allow Tor to start when RunAsDaemon is set but no logs are set.
16427 - When we have a state file we cannot parse, tell the user and
16428 move it aside. Now we avoid situations where the user starts
16429 Tor in 1904, Tor writes a state file with that timestamp in it,
16430 the user fixes her clock, and Tor refuses to start.
16431 - Fix configure.in to not produce broken configure files with
16432 more recent versions of autoconf. Thanks to Clint for his auto*
16434 - "tor --verify-config" now exits with -1(255) or 0 depending on
16435 whether the config options are bad or good.
16436 - Resolve bug 321 when using dnsworkers: append a period to every
16437 address we resolve at the exit node, so that we do not accidentally
16438 pick up local addresses, and so that failing searches are retried
16439 in the resolver search domains. (This is already solved for
16440 eventdns.) (This breaks Blossom servers for now.)
16441 - If we are using an exit enclave and we can't connect, e.g. because
16442 its webserver is misconfigured to not listen on localhost, then
16443 back off and try connecting from somewhere else before we fail.
16446 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
16447 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
16448 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
16449 when the IP address is mapped through MapAddress to a hostname.
16450 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
16451 useless IPv6 DNS resolves.
16452 - Patch suggested by Karsten Loesing: respond to SIGNAL command
16453 before we execute the signal, in case the signal shuts us down.
16454 - Clean up AllowInvalidNodes man page entry.
16455 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
16456 - Add more asserts to track down an assert error on a windows Tor
16457 server with connection_add being called with socket == -1.
16458 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
16459 - Fix misleading log messages: an entry guard that is "unlisted",
16460 as well as not known to be "down" (because we've never heard
16461 of it), is not therefore "up".
16462 - Remove code to special-case "-cvs" ending, since it has not
16463 actually mattered since 0.0.9.
16464 - Make our socks5 handling more robust to broken socks clients:
16465 throw out everything waiting on the buffer in between socks
16466 handshake phases, since they can't possibly (so the theory
16467 goes) have predicted what we plan to respond to them.
16470 Changes in version 0.1.1.23 - 2006-07-30
16472 - Fast Tor servers, especially exit nodes, were triggering asserts
16473 due to a bug in handling the list of pending DNS resolves. Some
16474 bugs still remain here; we're hunting them.
16475 - Entry guards could crash clients by sending unexpected input.
16476 - More fixes on reachability testing: if you find yourself reachable,
16477 then don't ever make any client requests (so you stop predicting
16478 circuits), then hup or have your clock jump, then later your IP
16479 changes, you won't think circuits are working, so you won't try to
16480 test reachability, so you won't publish.
16483 - Avoid a crash if the controller does a resetconf firewallports
16484 and then a setconf fascistfirewall=1.
16485 - Avoid an integer underflow when the dir authority decides whether
16486 a router is stable: we might wrongly label it stable, and compute
16487 a slightly wrong median stability, when a descriptor is published
16489 - Fix a place where we might trigger an assert if we can't build our
16490 own server descriptor yet.
16493 Changes in version 0.1.1.22 - 2006-07-05
16495 - Fix a big bug that was causing servers to not find themselves
16496 reachable if they changed IP addresses. Since only 0.1.1.22+
16497 servers can do reachability testing correctly, now we automatically
16498 make sure to test via one of these.
16499 - Fix to allow clients and mirrors to learn directory info from
16500 descriptor downloads that get cut off partway through.
16501 - Directory authorities had a bug in deciding if a newly published
16502 descriptor was novel enough to make everybody want a copy -- a few
16503 servers seem to be publishing new descriptors many times a minute.
16505 - Fix a rare bug that was causing some servers to complain about
16506 "closing wedged cpuworkers" and skip some circuit create requests.
16507 - Make the Exit flag in directory status documents actually work.
16510 Changes in version 0.1.1.21 - 2006-06-10
16511 o Crash and assert fixes from 0.1.1.20:
16512 - Fix a rare crash on Tor servers that have enabled hibernation.
16513 - Fix a seg fault on startup for Tor networks that use only one
16514 directory authority.
16515 - Fix an assert from a race condition that occurs on Tor servers
16516 while exiting, where various threads are trying to log that they're
16517 exiting, and delete the logs, at the same time.
16518 - Make our unit tests pass again on certain obscure platforms.
16521 - Add support for building SUSE RPM packages.
16522 - Speed up initial bootstrapping for clients: if we are making our
16523 first ever connection to any entry guard, then don't mark it down
16525 - When only one Tor server in the network is labelled as a guard,
16526 and we've already picked him, we would cycle endlessly picking him
16527 again, being unhappy about it, etc. Now we specifically exclude
16528 current guards when picking a new guard.
16529 - Servers send create cells more reliably after the TLS connection
16530 is established: we were sometimes forgetting to send half of them
16531 when we had more than one pending.
16532 - If we get a create cell that asks us to extend somewhere, but the
16533 Tor server there doesn't match the expected digest, we now send
16534 a destroy cell back, rather than silently doing nothing.
16535 - Make options->RedirectExit work again.
16536 - Make cookie authentication for the controller work again.
16537 - Stop being picky about unusual characters in the arguments to
16538 mapaddress. It's none of our business.
16539 - Add a new config option "TestVia" that lets you specify preferred
16540 middle hops to use for test circuits. Perhaps this will let me
16541 debug the reachability problems better.
16543 o Log / documentation fixes:
16544 - If we're a server and some peer has a broken TLS certificate, don't
16545 log about it unless ProtocolWarnings is set, i.e., we want to hear
16546 about protocol violations by others.
16547 - Fix spelling of VirtualAddrNetwork in man page.
16548 - Add a better explanation at the top of the autogenerated torrc file
16549 about what happened to our old torrc.
16552 Changes in version 0.1.1.20 - 2006-05-23
16554 - Downgrade a log severity where servers complain that they're
16556 - Avoid a compile warning on FreeBSD.
16557 - Remove string size limit on NEWDESC messages; solve bug 291.
16558 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
16559 more thoroughly when we're running on windows.
16562 Changes in version 0.1.1.19-rc - 2006-05-03
16564 - Regenerate our local descriptor if it's dirty and we try to use
16565 it locally (e.g. if it changes during reachability detection).
16566 - If we setconf our ORPort to 0, we continued to listen on the
16567 old ORPort and receive connections.
16568 - Avoid a second warning about machine/limits.h on Debian
16570 - Be willing to add our own routerinfo into the routerlist.
16571 Now authorities will include themselves in their directories
16572 and network-statuses.
16573 - Stop trying to upload rendezvous descriptors to every
16574 directory authority: only try the v1 authorities.
16575 - Servers no longer complain when they think they're not
16576 registered with the directory authorities. There were too many
16578 - Backport dist-rpm changes so rpms can be built without errors.
16581 - Implement an option, VirtualAddrMask, to set which addresses
16582 get handed out in response to mapaddress requests. This works
16583 around a bug in tsocks where 127.0.0.0/8 is never socksified.
16586 Changes in version 0.1.1.18-rc - 2006-04-10
16588 - Work harder to download live network-statuses from all the
16589 directory authorities we know about. Improve the threshold
16590 decision logic so we're more robust to edge cases.
16591 - When fetching rendezvous descriptors, we were willing to ask
16592 v2 authorities too, which would always return 404.
16595 - Stop listing down or invalid nodes in the v1 directory. This will
16596 reduce its bulk by about 1/3, and reduce load on directory
16598 - When deciding whether a router is Fast or Guard-worthy, consider
16599 his advertised BandwidthRate and not just the BandwidthCapacity.
16600 - No longer ship INSTALL and README files -- they are useless now.
16601 - Force rpmbuild to behave and honor target_cpu.
16602 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
16603 - Start to include translated versions of the tor-doc-*.html
16604 files, along with the screenshots. Still needs more work.
16605 - Start sending back 512 and 451 errors if mapaddress fails,
16606 rather than not sending anything back at all.
16607 - When we fail to bind or listen on an incoming or outgoing
16608 socket, we should close it before failing. otherwise we just
16609 leak it. (thanks to weasel for finding.)
16610 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
16611 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
16612 - Make NoPublish (even though deprecated) work again.
16613 - Fix a minor security flaw where a versioning auth dirserver
16614 could list a recommended version many times in a row to make
16615 clients more convinced that it's recommended.
16616 - Fix crash bug if there are two unregistered servers running
16617 with the same nickname, one of them is down, and you ask for
16618 them by nickname in your EntryNodes or ExitNodes. Also, try
16619 to pick the one that's running rather than an arbitrary one.
16620 - Fix an infinite loop we could hit if we go offline for too long.
16621 - Complain when we hit WSAENOBUFS on recv() or write() too.
16622 Perhaps this will help us hunt the bug.
16623 - If you're not a versioning dirserver, don't put the string
16624 "client-versions \nserver-versions \n" in your network-status.
16625 - Lower the minimum required number of file descriptors to 1000,
16626 so we can have some overhead for Valgrind on Linux, where the
16627 default ulimit -n is 1024.
16630 - Add tor.dizum.com as the fifth authoritative directory server.
16631 - Add a new config option FetchUselessDescriptors, off by default,
16632 for when you plan to run "exitlist" on your client and you want
16633 to know about even the non-running descriptors.
16636 Changes in version 0.1.1.17-rc - 2006-03-28
16638 - Clients and servers since 0.1.1.10-alpha have been expiring
16639 connections whenever they are idle for 5 minutes and they *do*
16640 have circuits on them. Oops. With this new version, clients will
16641 discard their previous entry guard choices and avoid choosing
16642 entry guards running these flawed versions.
16643 - Fix memory leak when uncompressing concatenated zlib streams. This
16644 was causing substantial leaks over time on Tor servers.
16645 - The v1 directory was including servers as much as 48 hours old,
16646 because that's how the new routerlist->routers works. Now only
16647 include them if they're 20 hours old or less.
16650 - Resume building on irix64, netbsd 2.0, etc.
16651 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
16653 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
16654 and it is confusing some users.
16655 - Mirrors stop caching the v1 directory so often.
16656 - Make the max number of old descriptors that a cache will hold
16657 rise with the number of directory authorities, so we can scale.
16658 - Change our win32 uname() hack to be more forgiving about what
16659 win32 versions it thinks it's found.
16662 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
16664 - When the controller's *setconf commands fail, collect an error
16665 message in a string and hand it back to the controller.
16666 - Make the v2 dir's "Fast" flag based on relative capacity, just
16667 like "Stable" is based on median uptime. Name everything in the
16668 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
16669 - Log server fingerprint on startup, so new server operators don't
16670 have to go hunting around their filesystem for it.
16671 - Return a robots.txt on our dirport to discourage google indexing.
16672 - Let the controller ask for GETINFO dir/status/foo so it can ask
16673 directly rather than connecting to the dir port. Only works when
16674 dirport is set for now.
16676 o New config options rather than constants in the code:
16677 - SocksTimeout: How long do we let a socks connection wait
16678 unattached before we fail it?
16679 - CircuitBuildTimeout: Cull non-open circuits that were born
16680 at least this many seconds ago.
16681 - CircuitIdleTimeout: Cull open clean circuits that were born
16682 at least this many seconds ago.
16685 Changes in version 0.1.1.16-rc - 2006-03-18
16686 o Bugfixes on 0.1.1.15-rc:
16687 - Fix assert when the controller asks to attachstream a connect-wait
16688 or resolve-wait stream.
16689 - Now do address rewriting when the controller asks us to attach
16690 to a particular circuit too. This will let Blossom specify
16691 "moria2.exit" without having to learn what moria2's IP address is.
16692 - Make the "tor --verify-config" command-line work again, so people
16693 can automatically check if their torrc will parse.
16694 - Authoritative dirservers no longer require an open connection from
16695 a server to consider him "reachable". We need this change because
16696 when we add new auth dirservers, old servers won't know not to
16698 - Let Tor build on Sun CC again.
16699 - Fix an off-by-one buffer size in dirserv.c that magically never
16700 hit our three authorities but broke sjmurdoch's own tor network.
16701 - If we as a directory mirror don't know of any v1 directory
16702 authorities, then don't try to cache any v1 directories.
16703 - Stop warning about unknown servers in our family when they are
16704 given as hex digests.
16705 - Stop complaining as quickly to the server operator that he
16706 hasn't registered his nickname/key binding.
16707 - Various cleanups so we can add new V2 Auth Dirservers.
16708 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
16709 reflect the updated flags in our v2 dir protocol.
16710 - Resume allowing non-printable characters for exit streams (both
16711 for connecting and for resolving). Now we tolerate applications
16712 that don't follow the RFCs. But continue to block malformed names
16715 o Bugfixes on 0.1.0.x:
16716 - Fix assert bug in close_logs(): when we close and delete logs,
16717 remove them all from the global "logfiles" list.
16718 - Fix minor integer overflow in calculating when we expect to use up
16719 our bandwidth allocation before hibernating.
16720 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
16721 there are multiple SSLs installed with different versions.
16722 - When we try to be a server and Address is not explicitly set and
16723 our hostname resolves to a private IP address, try to use an
16724 interface address if it has a public address. Now Windows machines
16725 that think of themselves as localhost can work by default.
16728 - Let the controller ask for GETINFO dir/server/foo so it can ask
16729 directly rather than connecting to the dir port.
16730 - Let the controller tell us about certain router descriptors
16731 that it doesn't want Tor to use in circuits. Implement
16732 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
16733 - New config option SafeSocks to reject all application connections
16734 using unsafe socks protocols. Defaults to off.
16737 Changes in version 0.1.1.15-rc - 2006-03-11
16738 o Bugfixes and cleanups:
16739 - When we're printing strings from the network, don't try to print
16740 non-printable characters. This protects us against shell escape
16741 sequence exploits, and also against attacks to fool humans into
16742 misreading their logs.
16743 - Fix a bug where Tor would fail to establish any connections if you
16744 left it off for 24 hours and then started it: we were happy with
16745 the obsolete network statuses, but they all referred to router
16746 descriptors that were too old to fetch, so we ended up with no
16747 valid router descriptors.
16748 - Fix a seg fault in the controller's "getinfo orconn-status"
16749 command while listing status on incoming handshaking connections.
16750 Introduce a status name "NEW" for these connections.
16751 - If we get a linelist or linelist_s config option from the torrc
16752 (e.g. ExitPolicy) and it has no value, warn and skip rather than
16753 silently resetting it to its default.
16754 - Don't abandon entry guards until they've been down or gone for
16756 - Cleaner and quieter log messages.
16759 - New controller signal NEWNYM that makes new application requests
16760 use clean circuits.
16761 - Add a new circuit purpose 'controller' to let the controller ask
16762 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
16763 controller command to let you specify the purpose if you're
16764 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
16765 command to let you change a circuit's purpose after it's been
16767 - Accept "private:*" in routerdesc exit policies; not generated yet
16768 because older Tors do not understand it.
16769 - Add BSD-style contributed startup script "rc.subr" from Peter
16773 Changes in version 0.1.1.14-alpha - 2006-02-20
16774 o Bugfixes on 0.1.1.x:
16775 - Don't die if we ask for a stdout or stderr log (even implicitly)
16776 and we're set to RunAsDaemon -- just warn.
16777 - We still had a few bugs in the OR connection rotation code that
16778 caused directory servers to slowly aggregate connections to other
16779 fast Tor servers. This time for sure!
16780 - Make log entries on Win32 include the name of the function again.
16781 - We were treating a pair of exit policies if they were equal even
16782 if one said accept and the other said reject -- causing us to
16783 not always publish a new descriptor since we thought nothing
16785 - Retry pending server downloads as well as pending networkstatus
16786 downloads when we unexpectedly get a socks request.
16787 - We were ignoring the IS_FAST flag in the directory status,
16788 meaning we were willing to pick trivial-bandwidth nodes for "fast"
16790 - If the controller's SAVECONF command fails (e.g. due to file
16791 permissions), let the controller know that it failed.
16794 - If we're trying to be a Tor server and running Windows 95/98/ME
16795 as a server, explain that we'll likely crash.
16796 - When we're a server, a client asks for an old-style directory,
16797 and our write bucket is empty, don't give it to him. This way
16798 small servers can continue to serve the directory *sometimes*,
16799 without getting overloaded.
16800 - Compress exit policies even more -- look for duplicate lines
16802 - Clients now honor the "guard" flag in the router status when
16803 picking entry guards, rather than looking at is_fast or is_stable.
16804 - Retain unrecognized lines in $DATADIR/state file, so that we can
16805 be forward-compatible.
16806 - Generate 18.0.0.0/8 address policy format in descs when we can;
16807 warn when the mask is not reducible to a bit-prefix.
16808 - Let the user set ControlListenAddress in the torrc. This can be
16809 dangerous, but there are some cases (like a secured LAN) where it
16811 - Split ReachableAddresses into ReachableDirAddresses and
16812 ReachableORAddresses, so we can restrict Dir conns to port 80
16813 and OR conns to port 443.
16814 - Now we can target arch and OS in rpm builds (contributed by
16815 Phobos). Also make the resulting dist-rpm filename match the
16817 - New config options to help controllers: FetchServerDescriptors
16818 and FetchHidServDescriptors for whether to fetch server
16819 info and hidserv info or let the controller do it, and
16820 PublishServerDescriptor and PublishHidServDescriptors.
16821 - Also let the controller set the __AllDirActionsPrivate config
16822 option if you want all directory fetches/publishes to happen via
16823 Tor (it assumes your controller bootstraps your circuits).
16826 Changes in version 0.1.0.17 - 2006-02-17
16827 o Crash bugfixes on 0.1.0.x:
16828 - When servers with a non-zero DirPort came out of hibernation,
16829 sometimes they would trigger an assert.
16831 o Other important bugfixes:
16832 - On platforms that don't have getrlimit (like Windows), we were
16833 artificially constraining ourselves to a max of 1024
16834 connections. Now just assume that we can handle as many as 15000
16835 connections. Hopefully this won't cause other problems.
16837 o Backported features:
16838 - When we're a server, a client asks for an old-style directory,
16839 and our write bucket is empty, don't give it to him. This way
16840 small servers can continue to serve the directory *sometimes*,
16841 without getting overloaded.
16842 - Whenever you get a 503 in response to a directory fetch, try
16843 once more. This will become important once servers start sending
16844 503's whenever they feel busy.
16845 - Fetch a new directory every 120 minutes, not every 40 minutes.
16846 Now that we have hundreds of thousands of users running the old
16847 directory algorithm, it's starting to hurt a lot.
16848 - Bump up the period for forcing a hidden service descriptor upload
16849 from 20 minutes to 1 hour.
16852 Changes in version 0.1.1.13-alpha - 2006-02-09
16853 o Crashes in 0.1.1.x:
16854 - When you tried to setconf ORPort via the controller, Tor would
16855 crash. So people using TorCP to become a server were sad.
16856 - Solve (I hope) the stack-smashing bug that we were seeing on fast
16857 servers. The problem appears to be something do with OpenSSL's
16858 random number generation, or how we call it, or something. Let me
16859 know if the crashes continue.
16860 - Turn crypto hardware acceleration off by default, until we find
16861 somebody smart who can test it for us. (It appears to produce
16862 seg faults in at least some cases.)
16863 - Fix a rare assert error when we've tried all intro points for
16864 a hidden service and we try fetching the service descriptor again:
16865 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
16868 - Fix a major load balance bug: we were round-robining in 16 KB
16869 chunks, and servers with bandwidthrate of 20 KB, while downloading
16870 a 600 KB directory, would starve their other connections. Now we
16871 try to be a bit more fair.
16872 - Dir authorities and mirrors were never expiring the newest
16873 descriptor for each server, causing memory and directory bloat.
16874 - Fix memory-bloating and connection-bloating bug on servers: We
16875 were never closing any connection that had ever had a circuit on
16876 it, because we were checking conn->n_circuits == 0, yet we had a
16877 bug that let it go negative.
16878 - Make Tor work using squid as your http proxy again -- squid
16879 returns an error if you ask for a URL that's too long, and it uses
16880 a really generic error message. Plus, many people are behind a
16881 transparent squid so they don't even realize it.
16882 - On platforms that don't have getrlimit (like Windows), we were
16883 artificially constraining ourselves to a max of 1024
16884 connections. Now just assume that we can handle as many as 15000
16885 connections. Hopefully this won't cause other problems.
16886 - Add a new config option ExitPolicyRejectPrivate which defaults to
16887 1. This means all exit policies will begin with rejecting private
16888 addresses, unless the server operator explicitly turns it off.
16891 - Clients no longer download descriptors for non-running
16893 - Before we add new directory authorities, we should make it
16894 clear that only v1 authorities should receive/publish hidden
16895 service descriptors.
16898 - As soon as we've fetched some more directory info, immediately
16899 try to download more server descriptors. This way we don't have
16900 a 10 second pause during initial bootstrapping.
16901 - Remove even more loud log messages that the server operator can't
16903 - When we're running an obsolete or un-recommended version, make
16904 the log message more clear about what the problem is and what
16905 versions *are* still recommended.
16906 - Provide a more useful warn message when our onion queue gets full:
16907 the CPU is too slow or the exit policy is too liberal.
16908 - Don't warn when we receive a 503 from a dirserver/cache -- this
16909 will pave the way for them being able to refuse if they're busy.
16910 - When we fail to bind a listener, try to provide a more useful
16911 log message: e.g., "Is Tor already running?"
16912 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
16913 Goldberg can prove things about our handshake protocol more
16915 - MaxConn has been obsolete for a while now. Document the ConnLimit
16916 config option, which is a *minimum* number of file descriptors
16917 that must be available else Tor refuses to start.
16918 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
16919 if you log to syslog and want something other than LOG_DAEMON.
16920 - Make dirservers generate a separate "guard" flag to mean,
16921 "would make a good entry guard". Make clients parse it and vote
16922 on it. Not used by clients yet.
16923 - Implement --with-libevent-dir option to ./configure. Also, improve
16924 search techniques to find libevent, and use those for openssl too.
16925 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
16926 - Only start testing reachability once we've established a
16927 circuit. This will make startup on dirservers less noisy.
16928 - Don't try to upload hidden service descriptors until we have
16929 established a circuit.
16930 - Fix the controller's "attachstream 0" command to treat conn like
16931 it just connected, doing address remapping, handling .exit and
16932 .onion idioms, and so on. Now we're more uniform in making sure
16933 that the controller hears about new and closing connections.
16936 Changes in version 0.1.1.12-alpha - 2006-01-11
16937 o Bugfixes on 0.1.1.x:
16938 - The fix to close duplicate server connections was closing all
16939 Tor client connections if they didn't establish a circuit
16940 quickly enough. Oops.
16941 - Fix minor memory issue (double-free) that happened on exit.
16943 o Bugfixes on 0.1.0.x:
16944 - Tor didn't warn when it failed to open a log file.
16947 Changes in version 0.1.1.11-alpha - 2006-01-10
16948 o Crashes in 0.1.1.x:
16949 - Include all the assert/crash fixes from 0.1.0.16.
16950 - If you start Tor and then quit very quickly, there were some
16951 races that tried to free things that weren't allocated yet.
16952 - Fix a rare memory stomp if you're running hidden services.
16953 - Fix segfault when specifying DirServer in config without nickname.
16954 - Fix a seg fault when you finish connecting to a server but at
16955 that moment you dump his server descriptor.
16956 - Extendcircuit and Attachstream controller commands would
16957 assert/crash if you don't give them enough arguments.
16958 - Fix an assert error when we're out of space in the connection_list
16959 and we try to post a hidden service descriptor (reported by weasel).
16960 - If you specify a relative torrc path and you set RunAsDaemon in
16961 your torrc, then it chdir()'s to the new directory. If you HUP,
16962 it tries to load the new torrc location, fails, and exits.
16963 The fix: no longer allow a relative path to torrc using -f.
16966 - Implement "entry guards": automatically choose a handful of entry
16967 nodes and stick with them for all circuits. Only pick new guards
16968 when the ones you have are unsuitable, and if the old guards
16969 become suitable again, switch back. This will increase security
16970 dramatically against certain end-point attacks. The EntryNodes
16971 config option now provides some hints about which entry guards you
16972 want to use most; and StrictEntryNodes means to only use those.
16973 - New directory logic: download by descriptor digest, not by
16974 fingerprint. Caches try to download all listed digests from
16975 authorities; clients try to download "best" digests from caches.
16976 This avoids partitioning and isolating attacks better.
16977 - Make the "stable" router flag in network-status be the median of
16978 the uptimes of running valid servers, and make clients pay
16979 attention to the network-status flags. Thus the cutoff adapts
16980 to the stability of the network as a whole, making IRC, IM, etc
16981 connections more reliable.
16984 - Tor servers with dynamic IP addresses were needing to wait 18
16985 hours before they could start doing reachability testing using
16986 the new IP address and ports. This is because they were using
16987 the internal descriptor to learn what to test, yet they were only
16988 rebuilding the descriptor once they decided they were reachable.
16989 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
16990 to download certain server descriptors, throw them away, and then
16991 fetch them again after 30 minutes. Now mirrors throw away these
16992 server descriptors so clients can't get them.
16993 - We were leaving duplicate connections to other ORs open for a week,
16994 rather than closing them once we detect a duplicate. This only
16995 really affected authdirservers, but it affected them a lot.
16996 - Spread the authdirservers' reachability testing over the entire
16997 testing interval, so we don't try to do 500 TLS's at once every
17001 - If the network is down, and we try to connect to a conn because
17002 we have a circuit in mind, and we timeout (30 seconds) because the
17003 network never answers, we were expiring the circuit, but we weren't
17004 obsoleting the connection or telling the entry_guards functions.
17005 - Some Tor servers process billions of cells per day. These statistics
17006 need to be uint64_t's.
17007 - Check for integer overflows in more places, when adding elements
17008 to smartlists. This could possibly prevent a buffer overflow
17009 on malicious huge inputs. I don't see any, but I haven't looked
17011 - ReachableAddresses kept growing new "reject *:*" lines on every
17013 - When you "setconf log" via the controller, it should remove all
17014 logs. We were automatically adding back in a "log notice stdout".
17015 - Newly bootstrapped Tor networks couldn't establish hidden service
17016 circuits until they had nodes with high uptime. Be more tolerant.
17017 - We were marking servers down when they could not answer every piece
17018 of the directory request we sent them. This was far too harsh.
17019 - Fix the torify (tsocks) config file to not use Tor for localhost
17021 - Directory authorities now go to the proper authority when asking for
17022 a networkstatus, even when they want a compressed one.
17023 - Fix a harmless bug that was causing Tor servers to log
17024 "Got an end because of misc error, but we're not an AP. Closing."
17025 - Authorities were treating their own descriptor changes as cosmetic,
17026 meaning the descriptor available in the network-status and the
17027 descriptor that clients downloaded were different.
17028 - The OS X installer was adding a symlink for tor_resolve but
17029 the binary was called tor-resolve (reported by Thomas Hardly).
17030 - Workaround a problem with some http proxies where they refuse GET
17031 requests that specify "Content-Length: 0" (reported by Adrian).
17032 - Fix wrong log message when you add a "HiddenServiceNodes" config
17033 line without any HiddenServiceDir line (reported by Chris Thomas).
17036 - Write the TorVersion into the state file so we have a prayer of
17037 keeping forward and backward compatibility.
17038 - Revive the FascistFirewall config option rather than eliminating it:
17039 now it's a synonym for ReachableAddresses *:80,*:443.
17040 - Clients choose directory servers from the network status lists,
17041 not from their internal list of router descriptors. Now they can
17042 go to caches directly rather than needing to go to authorities
17044 - Directory authorities ignore router descriptors that have only
17045 cosmetic differences: do this for 0.1.0.x servers now too.
17046 - Add a new flag to network-status indicating whether the server
17047 can answer v2 directory requests too.
17048 - Authdirs now stop whining so loudly about bad descriptors that
17049 they fetch from other dirservers. So when there's a log complaint,
17050 it's for sure from a freshly uploaded descriptor.
17051 - Reduce memory requirements in our structs by changing the order
17053 - There used to be two ways to specify your listening ports in a
17054 server descriptor: on the "router" line and with a separate "ports"
17055 line. Remove support for the "ports" line.
17056 - New config option "AuthDirRejectUnlisted" for auth dirservers as
17057 a panic button: if we get flooded with unusable servers we can
17058 revert to only listing servers in the approved-routers file.
17059 - Auth dir servers can now mark a fingerprint as "!reject" or
17060 "!invalid" in the approved-routers file (as its nickname), to
17061 refuse descriptors outright or include them but marked as invalid.
17062 - Servers store bandwidth history across restarts/crashes.
17063 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
17064 get a better idea of why their circuits failed. Not used yet.
17065 - Directory mirrors now cache up to 16 unrecognized network-status
17066 docs. Now we can add new authdirservers and they'll be cached too.
17067 - When picking a random directory, prefer non-authorities if any
17069 - New controller option "getinfo desc/all-recent" to fetch the
17070 latest server descriptor for every router that Tor knows about.
17073 Changes in version 0.1.0.16 - 2006-01-02
17074 o Crash bugfixes on 0.1.0.x:
17075 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
17076 corrupting the heap, losing FDs, or crashing when we need to resize
17077 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
17078 - It turns out sparc64 platforms crash on unaligned memory access
17079 too -- so detect and avoid this.
17080 - Handle truncated compressed data correctly (by detecting it and
17082 - Fix possible-but-unlikely free(NULL) in control.c.
17083 - When we were closing connections, there was a rare case that
17084 stomped on memory, triggering seg faults and asserts.
17085 - Avoid potential infinite recursion when building a descriptor. (We
17086 don't know that it ever happened, but better to fix it anyway.)
17087 - We were neglecting to unlink marked circuits from soon-to-close OR
17088 connections, which caused some rare scribbling on freed memory.
17089 - Fix a memory stomping race bug when closing the joining point of two
17090 rendezvous circuits.
17091 - Fix an assert in time parsing found by Steven Murdoch.
17093 o Other bugfixes on 0.1.0.x:
17094 - When we're doing reachability testing, provide more useful log
17095 messages so the operator knows what to expect.
17096 - Do not check whether DirPort is reachable when we are suppressing
17097 advertising it because of hibernation.
17098 - When building with -static or on Solaris, we sometimes needed -ldl.
17099 - When we're deciding whether a stream has enough circuits around
17100 that can handle it, count the freshly dirty ones and not the ones
17101 that are so dirty they won't be able to handle it.
17102 - When we're expiring old circuits, we had a logic error that caused
17103 us to close new rendezvous circuits rather than old ones.
17104 - Give a more helpful log message when you try to change ORPort via
17105 the controller: you should upgrade Tor if you want that to work.
17106 - We were failing to parse Tor versions that start with "Tor ".
17107 - Tolerate faulty streams better: when a stream fails for reason
17108 exitpolicy, stop assuming that the router is lying about his exit
17109 policy. When a stream fails for reason misc, allow it to retry just
17110 as if it was resolvefailed. When a stream has failed three times,
17111 reset its failure count so we can try again and get all three tries.
17114 Changes in version 0.1.1.10-alpha - 2005-12-11
17115 o Correctness bugfixes on 0.1.0.x:
17116 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
17117 corrupting the heap, losing FDs, or crashing when we need to resize
17118 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
17119 - Stop doing the complex voodoo overkill checking for insecure
17120 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
17121 - When we were closing connections, there was a rare case that
17122 stomped on memory, triggering seg faults and asserts.
17123 - We were neglecting to unlink marked circuits from soon-to-close OR
17124 connections, which caused some rare scribbling on freed memory.
17125 - When we're deciding whether a stream has enough circuits around
17126 that can handle it, count the freshly dirty ones and not the ones
17127 that are so dirty they won't be able to handle it.
17128 - Recover better from TCP connections to Tor servers that are
17129 broken but don't tell you (it happens!); and rotate TLS
17130 connections once a week.
17131 - When we're expiring old circuits, we had a logic error that caused
17132 us to close new rendezvous circuits rather than old ones.
17133 - Fix a scary-looking but apparently harmless bug where circuits
17134 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
17135 servers, and never switch to state CIRCUIT_STATE_OPEN.
17136 - When building with -static or on Solaris, we sometimes needed to
17138 - Give a useful message when people run Tor as the wrong user,
17139 rather than telling them to start chowning random directories.
17140 - We were failing to inform the controller about new .onion streams.
17142 o Security bugfixes on 0.1.0.x:
17143 - Refuse server descriptors if the fingerprint line doesn't match
17144 the included identity key. Tor doesn't care, but other apps (and
17145 humans) might actually be trusting the fingerprint line.
17146 - We used to kill the circuit when we receive a relay command we
17147 don't recognize. Now we just drop it.
17148 - Start obeying our firewall options more rigorously:
17149 . If we can't get to a dirserver directly, try going via Tor.
17150 . Don't ever try to connect (as a client) to a place our
17151 firewall options forbid.
17152 . If we specify a proxy and also firewall options, obey the
17153 firewall options even when we're using the proxy: some proxies
17154 can only proxy to certain destinations.
17155 - Fix a bug found by Lasse Overlier: when we were making internal
17156 circuits (intended to be cannibalized later for rendezvous and
17157 introduction circuits), we were picking them so that they had
17158 useful exit nodes. There was no need for this, and it actually
17159 aids some statistical attacks.
17160 - Start treating internal circuits and exit circuits separately.
17161 It's important to keep them separate because internal circuits
17162 have their last hops picked like middle hops, rather than like
17163 exit hops. So exiting on them will break the user's expectations.
17165 o Bugfixes on 0.1.1.x:
17166 - Take out the mis-feature where we tried to detect IP address
17167 flapping for people with DynDNS, and chose not to upload a new
17168 server descriptor sometimes.
17169 - Try to be compatible with OpenSSL 0.9.6 again.
17170 - Log fix: when the controller is logging about .onion addresses,
17171 sometimes it didn't include the ".onion" part of the address.
17172 - Don't try to modify options->DirServers internally -- if the
17173 user didn't specify any, just add the default ones directly to
17174 the trusted dirserver list. This fixes a bug where people running
17175 controllers would use SETCONF on some totally unrelated config
17176 option, and Tor would start yelling at them about changing their
17178 - Let the controller's redirectstream command specify a port, in
17179 case the controller wants to change that too.
17180 - When we requested a pile of server descriptors, we sometimes
17181 accidentally launched a duplicate request for the first one.
17182 - Bugfix for trackhostexits: write down the fingerprint of the
17183 chosen exit, not its nickname, because the chosen exit might not
17185 - When parsing foo.exit, if foo is unknown, and we are leaving
17186 circuits unattached, set the chosen_exit field and leave the
17187 address empty. This matters because controllers got confused
17189 - Directory authorities no longer try to download server
17190 descriptors that they know they will reject.
17192 o Features and updates:
17193 - Replace balanced trees with hash tables: this should make stuff
17194 significantly faster.
17195 - Resume using the AES counter-mode implementation that we ship,
17196 rather than OpenSSL's. Ours is significantly faster.
17197 - Many other CPU and memory improvements.
17198 - Add a new config option FastFirstHopPK (on by default) so clients
17199 do a trivial crypto handshake for their first hop, since TLS has
17200 already taken care of confidentiality and authentication.
17201 - Add a new config option TestSocks so people can see if their
17202 applications are using socks4, socks4a, socks5-with-ip, or
17203 socks5-with-hostname. This way they don't have to keep mucking
17204 with tcpdump and wondering if something got cached somewhere.
17205 - Warn when listening on a public address for socks. I suspect a
17206 lot of people are setting themselves up as open socks proxies,
17207 and they have no idea that jerks on the Internet are using them,
17208 since they simply proxy the traffic into the Tor network.
17209 - Add "private:*" as an alias in configuration for policies. Now
17210 you can simplify your exit policy rather than needing to list
17211 every single internal or nonroutable network space.
17212 - Add a new controller event type that allows controllers to get
17213 all server descriptors that were uploaded to a router in its role
17214 as authoritative dirserver.
17215 - Start shipping socks-extensions.txt, tor-doc-unix.html,
17216 tor-doc-server.html, and stylesheet.css in the tarball.
17217 - Stop shipping tor-doc.html in the tarball.
17220 Changes in version 0.1.1.9-alpha - 2005-11-15
17221 o Usability improvements:
17222 - Start calling it FooListenAddress rather than FooBindAddress,
17223 since few of our users know what it means to bind an address
17225 - Reduce clutter in server logs. We're going to try to make
17226 them actually usable now. New config option ProtocolWarnings that
17227 lets you hear about how _other Tors_ are breaking the protocol. Off
17229 - Divide log messages into logging domains. Once we put some sort
17230 of interface on this, it will let people looking at more verbose
17231 log levels specify the topics they want to hear more about.
17232 - Make directory servers return better http 404 error messages
17233 instead of a generic "Servers unavailable".
17234 - Check for even more Windows version flags when writing the platform
17235 string in server descriptors, and note any we don't recognize.
17236 - Clean up more of the OpenSSL memory when exiting, so we can detect
17237 memory leaks better.
17238 - Make directory authorities be non-versioning, non-naming by
17239 default. Now we can add new directory servers without requiring
17240 their operators to pay close attention.
17241 - When logging via syslog, include the pid whenever we provide
17242 a log entry. Suggested by Todd Fries.
17244 o Performance improvements:
17245 - Directory servers now silently throw away new descriptors that
17246 haven't changed much if the timestamps are similar. We do this to
17247 tolerate older Tor servers that upload a new descriptor every 15
17248 minutes. (It seemed like a good idea at the time.)
17249 - Inline bottleneck smartlist functions; use fast versions by default.
17250 - Add a "Map from digest to void*" abstraction digestmap_t so we
17251 can do less hex encoding/decoding. Use it in router_get_by_digest()
17252 to resolve a performance bottleneck.
17253 - Allow tor_gzip_uncompress to extract as much as possible from
17254 truncated compressed data. Try to extract as many
17255 descriptors as possible from truncated http responses (when
17256 DIR_PURPOSE_FETCH_ROUTERDESC).
17257 - Make circ->onionskin a pointer, not a static array. moria2 was using
17258 125000 circuit_t's after it had been up for a few weeks, which
17259 translates to 20+ megs of wasted space.
17260 - The private half of our EDH handshake keys are now chosen out
17261 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
17263 o Security improvements:
17264 - Start making directory caches retain old routerinfos, so soon
17265 clients can start asking by digest of descriptor rather than by
17266 fingerprint of server.
17267 - Add half our entropy from RAND_poll in OpenSSL. This knows how
17268 to use egd (if present), openbsd weirdness (if present), vms/os2
17269 weirdness (if we ever port there), and more in the future.
17271 o Bugfixes on 0.1.0.x:
17272 - Do round-robin writes of at most 16 kB per write. This might be
17273 more fair on loaded Tor servers, and it might resolve our Windows
17274 crash bug. It might also slow things down.
17275 - Our TLS handshakes were generating a single public/private
17276 keypair for the TLS context, rather than making a new one for
17277 each new connections. Oops. (But we were still rotating them
17278 periodically, so it's not so bad.)
17279 - When we were cannibalizing a circuit with a particular exit
17280 node in mind, we weren't checking to see if that exit node was
17281 already present earlier in the circuit. Oops.
17282 - When a Tor server's IP changes (e.g. from a dyndns address),
17283 upload a new descriptor so clients will learn too.
17284 - Really busy servers were keeping enough circuits open on stable
17285 connections that they were wrapping around the circuit_id
17286 space. (It's only two bytes.) This exposed a bug where we would
17287 feel free to reuse a circuit_id even if it still exists but has
17288 been marked for close. Try to fix this bug. Some bug remains.
17289 - If we would close a stream early (e.g. it asks for a .exit that
17290 we know would refuse it) but the LeaveStreamsUnattached config
17291 option is set by the controller, then don't close it.
17293 o Bugfixes on 0.1.1.8-alpha:
17294 - Fix a big pile of memory leaks, some of them serious.
17295 - Do not try to download a routerdesc if we would immediately reject
17297 - Resume inserting a newline between all router descriptors when
17298 generating (old style) signed directories, since our spec says
17300 - When providing content-type application/octet-stream for
17301 server descriptors using .z, we were leaving out the
17302 content-encoding header. Oops. (Everything tolerated this just
17303 fine, but that doesn't mean we need to be part of the problem.)
17304 - Fix a potential seg fault in getconf and getinfo using version 1
17305 of the controller protocol.
17306 - Avoid crash: do not check whether DirPort is reachable when we
17307 are suppressing it because of hibernation.
17308 - Make --hash-password not crash on exit.
17311 Changes in version 0.1.1.8-alpha - 2005-10-07
17312 o New features (major):
17313 - Clients don't download or use the directory anymore. Now they
17314 download and use network-statuses from the trusted dirservers,
17315 and fetch individual server descriptors as needed from mirrors.
17316 See dir-spec.txt for all the gory details.
17317 - Be more conservative about whether to advertise our DirPort.
17318 The main change is to not advertise if we're running at capacity
17319 and either a) we could hibernate or b) our capacity is low and
17320 we're using a default DirPort.
17321 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
17323 o New features (minor):
17324 - Try to be smart about when to retry network-status and
17325 server-descriptor fetches. Still needs some tuning.
17326 - Stop parsing, storing, or using running-routers output (but
17327 mirrors still cache and serve it).
17328 - Consider a threshold of versioning dirservers (dirservers who have
17329 an opinion about which Tor versions are still recommended) before
17330 deciding whether to warn the user that he's obsolete.
17331 - Dirservers can now reject/invalidate by key and IP, with the
17332 config options "AuthDirInvalid" and "AuthDirReject". This is
17333 useful since currently we automatically list servers as running
17334 and usable even if we know they're jerks.
17335 - Provide dire warnings to any users who set DirServer; move it out
17336 of torrc.sample and into torrc.complete.
17337 - Add MyFamily to torrc.sample in the server section.
17338 - Add nicknames to the DirServer line, so we can refer to them
17339 without requiring all our users to memorize their IP addresses.
17340 - When we get an EOF or a timeout on a directory connection, note
17341 how many bytes of serverdesc we are dropping. This will help
17342 us determine whether it is smart to parse incomplete serverdesc
17344 - Add a new function to "change pseudonyms" -- that is, to stop
17345 using any currently-dirty circuits for new streams, so we don't
17346 link new actions to old actions. Currently it's only called on
17347 HUP (or SIGNAL RELOAD).
17348 - On sighup, if UseHelperNodes changed to 1, use new circuits.
17349 - Start using RAND_bytes rather than RAND_pseudo_bytes from
17350 OpenSSL. Also, reseed our entropy every hour, not just at
17351 startup. And entropy in 512-bit chunks, not 160-bit chunks.
17353 o Fixes on 0.1.1.7-alpha:
17354 - Nobody ever implemented EVENT_ADDRMAP for control protocol
17355 version 0, so don't let version 0 controllers ask for it.
17356 - If you requested something with too many newlines via the
17357 v1 controller protocol, you could crash tor.
17358 - Fix a number of memory leaks, including some pretty serious ones.
17359 - Re-enable DirPort testing again, so Tor servers will be willing
17360 to advertise their DirPort if it's reachable.
17361 - On TLS handshake, only check the other router's nickname against
17362 its expected nickname if is_named is set.
17364 o Fixes forward-ported from 0.1.0.15:
17365 - Don't crash when we don't have any spare file descriptors and we
17366 try to spawn a dns or cpu worker.
17367 - Make the numbers in read-history and write-history into uint64s,
17368 so they don't overflow and publish negatives in the descriptor.
17370 o Fixes on 0.1.0.x:
17371 - For the OS X package's modified privoxy config file, comment
17372 out the "logfile" line so we don't log everything passed
17374 - We were whining about using socks4 or socks5-with-local-lookup
17375 even when it's an IP in the "virtual" range we designed exactly
17377 - We were leaking some memory every time the client changes IPs.
17378 - Never call free() on tor_malloc()d memory. This will help us
17379 use dmalloc to detect memory leaks.
17380 - Check for named servers when looking them up by nickname;
17381 warn when we'recalling a non-named server by its nickname;
17382 don't warn twice about the same name.
17383 - Try to list MyFamily elements by key, not by nickname, and warn
17384 if we've not heard of the server.
17385 - Make windows platform detection (uname equivalent) smarter.
17386 - It turns out sparc64 doesn't like unaligned access either.
17389 Changes in version 0.1.0.15 - 2005-09-23
17390 o Bugfixes on 0.1.0.x:
17391 - Reject ports 465 and 587 (spam targets) in default exit policy.
17392 - Don't crash when we don't have any spare file descriptors and we
17393 try to spawn a dns or cpu worker.
17394 - Get rid of IgnoreVersion undocumented config option, and make us
17395 only warn, never exit, when we're running an obsolete version.
17396 - Don't try to print a null string when your server finds itself to
17397 be unreachable and the Address config option is empty.
17398 - Make the numbers in read-history and write-history into uint64s,
17399 so they don't overflow and publish negatives in the descriptor.
17400 - Fix a minor memory leak in smartlist_string_remove().
17401 - We were only allowing ourselves to upload a server descriptor at
17402 most every 20 minutes, even if it changed earlier than that.
17403 - Clean up log entries that pointed to old URLs.
17406 Changes in version 0.1.1.7-alpha - 2005-09-14
17407 o Fixes on 0.1.1.6-alpha:
17408 - Exit servers were crashing when people asked them to make a
17409 connection to an address not in their exit policy.
17410 - Looking up a non-existent stream for a v1 control connection would
17412 - Fix a seg fault if we ask a dirserver for a descriptor by
17413 fingerprint but he doesn't know about him.
17414 - SETCONF was appending items to linelists, not clearing them.
17415 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
17416 out and refuse the setconf if it would fail.
17417 - Downgrade the dirserver log messages when whining about
17421 - Add Peter Palfrader's check-tor script to tor/contrib/
17422 It lets you easily check whether a given server (referenced by
17423 nickname) is reachable by you.
17424 - Numerous changes to move towards client-side v2 directories. Not
17427 o Fixes on 0.1.0.x:
17428 - If the user gave tor an odd number of command-line arguments,
17429 we were silently ignoring the last one. Now we complain and fail.
17430 [This wins the oldest-bug prize -- this bug has been present since
17431 November 2002, as released in Tor 0.0.0.]
17432 - Do not use unaligned memory access on alpha, mips, or mipsel.
17433 It *works*, but is very slow, so we treat them as if it doesn't.
17434 - Retry directory requests if we fail to get an answer we like
17435 from a given dirserver (we were retrying before, but only if
17436 we fail to connect).
17437 - When writing the RecommendedVersions line, sort them first.
17438 - When the client asked for a rendezvous port that the hidden
17439 service didn't want to provide, we were sending an IP address
17440 back along with the end cell. Fortunately, it was zero. But stop
17442 - Correct "your server is reachable" log entries to indicate that
17443 it was self-testing that told us so.
17446 Changes in version 0.1.1.6-alpha - 2005-09-09
17447 o Fixes on 0.1.1.5-alpha:
17448 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
17449 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
17450 - Fix bug with tor_memmem finding a match at the end of the string.
17451 - Make unit tests run without segfaulting.
17452 - Resolve some solaris x86 compile warnings.
17453 - Handle duplicate lines in approved-routers files without warning.
17454 - Fix bug where as soon as a server refused any requests due to his
17455 exit policy (e.g. when we ask for localhost and he tells us that's
17456 127.0.0.1 and he won't do it), we decided he wasn't obeying his
17457 exit policy using him for any exits.
17458 - Only do openssl hardware accelerator stuff if openssl version is
17461 o New controller features/fixes:
17462 - Add a "RESETCONF" command so you can set config options like
17463 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
17464 a config option in the torrc with no value, then it clears it
17465 entirely (rather than setting it to its default).
17466 - Add a "GETINFO config-file" to tell us where torrc is.
17467 - Avoid sending blank lines when GETINFO replies should be empty.
17468 - Add a QUIT command for the controller (for using it manually).
17469 - Fix a bug in SAVECONF that was adding default dirservers and
17470 other redundant entries to the torrc file.
17472 o Start on the new directory design:
17473 - Generate, publish, cache, serve new network-status format.
17474 - Publish individual descriptors (by fingerprint, by "all", and by
17476 - Publish client and server recommended versions separately.
17477 - Allow tor_gzip_uncompress() to handle multiple concatenated
17478 compressed strings. Serve compressed groups of router
17479 descriptors. The compression logic here could be more
17481 - Distinguish v1 authorities (all currently trusted directories)
17482 from v2 authorities (all trusted directories).
17483 - Change DirServers config line to note which dirs are v1 authorities.
17484 - Add configuration option "V1AuthoritativeDirectory 1" which
17485 moria1, moria2, and tor26 should set.
17486 - Remove option when getting directory cache to see whether they
17487 support running-routers; they all do now. Replace it with one
17488 to see whether caches support v2 stuff.
17491 - Dirservers now do their own external reachability testing of each
17492 Tor server, and only list them as running if they've been found to
17493 be reachable. We also send back warnings to the server's logs if
17494 it uploads a descriptor that we already believe is unreachable.
17495 - Implement exit enclaves: if we know an IP address for the
17496 destination, and there's a running Tor server at that address
17497 which allows exit to the destination, then extend the circuit to
17498 that exit first. This provides end-to-end encryption and end-to-end
17499 authentication. Also, if the user wants a .exit address or enclave,
17500 use 4 hops rather than 3, and cannibalize a general circ for it
17502 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
17503 controller. Also, rotate dns and cpu workers if the controller
17504 changes options that will affect them; and initialize the dns
17505 worker cache tree whether or not we start out as a server.
17506 - Only upload a new server descriptor when options change, 18
17507 hours have passed, uptime is reset, or bandwidth changes a lot.
17508 - Check [X-]Forwarded-For headers in HTTP requests when generating
17509 log messages. This lets people run dirservers (and caches) behind
17510 Apache but still know which IP addresses are causing warnings.
17512 o Config option changes:
17513 - Replace (Fascist)Firewall* config options with a new
17514 ReachableAddresses option that understands address policies.
17515 For example, "ReachableAddresses *:80,*:443"
17516 - Get rid of IgnoreVersion undocumented config option, and make us
17517 only warn, never exit, when we're running an obsolete version.
17518 - Make MonthlyAccountingStart config option truly obsolete now.
17520 o Fixes on 0.1.0.x:
17521 - Reject ports 465 and 587 in the default exit policy, since
17522 people have started using them for spam too.
17523 - It turns out we couldn't bootstrap a network since we added
17524 reachability detection in 0.1.0.1-rc. Good thing the Tor network
17525 has never gone down. Add an AssumeReachable config option to let
17526 servers and dirservers bootstrap. When we're trying to build a
17527 high-uptime or high-bandwidth circuit but there aren't enough
17528 suitable servers, try being less picky rather than simply failing.
17529 - Our logic to decide if the OR we connected to was the right guy
17530 was brittle and maybe open to a mitm for unverified routers.
17531 - We weren't cannibalizing circuits correctly for
17532 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
17533 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
17534 build those from scratch. This should make hidden services faster.
17535 - Predict required circuits better, with an eye toward making hidden
17536 services faster on the service end.
17537 - Retry streams if the exit node sends back a 'misc' failure. This
17538 should result in fewer random failures. Also, after failing
17539 from resolve failed or misc, reset the num failures, so we give
17540 it a fair shake next time we try.
17541 - Clean up the rendezvous warn log msgs, and downgrade some to info.
17542 - Reduce severity on logs about dns worker spawning and culling.
17543 - When we're shutting down and we do something like try to post a
17544 server descriptor or rendezvous descriptor, don't complain that
17545 we seem to be unreachable. Of course we are, we're shutting down.
17546 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
17547 We don't use them yet, but maybe one day our DNS resolver will be
17548 able to discover them.
17549 - Make ContactInfo mandatory for authoritative directory servers.
17550 - Require server descriptors to list IPv4 addresses -- hostnames
17551 are no longer allowed. This also fixes some potential security
17552 problems with people providing hostnames as their address and then
17553 preferentially resolving them to partition users.
17554 - Change log line for unreachability to explicitly suggest /etc/hosts
17555 as the culprit. Also make it clearer what IP address and ports we're
17556 testing for reachability.
17557 - Put quotes around user-supplied strings when logging so users are
17558 more likely to realize if they add bad characters (like quotes)
17560 - Let auth dir servers start without specifying an Address config
17562 - Make unit tests (and other invocations that aren't the real Tor)
17563 run without launching listeners, creating subdirectories, and so on.
17566 Changes in version 0.1.1.5-alpha - 2005-08-08
17567 o Bugfixes included in 0.1.0.14.
17569 o Bugfixes on 0.1.0.x:
17570 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
17571 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
17572 it would silently using ignore the 6668.
17575 Changes in version 0.1.0.14 - 2005-08-08
17576 o Bugfixes on 0.1.0.x:
17577 - Fix the other half of the bug with crypto handshakes
17579 - Fix an assert trigger if you send a 'signal term' via the
17580 controller when it's listening for 'event info' messages.
17583 Changes in version 0.1.1.4-alpha - 2005-08-04
17584 o Bugfixes included in 0.1.0.13.
17587 - Improve tor_gettimeofday() granularity on windows.
17588 - Make clients regenerate their keys when their IP address changes.
17589 - Implement some more GETINFO goodness: expose helper nodes, config
17590 options, getinfo keys.
17593 Changes in version 0.1.0.13 - 2005-08-04
17594 o Bugfixes on 0.1.0.x:
17595 - Fix a critical bug in the security of our crypto handshakes.
17596 - Fix a size_t underflow in smartlist_join_strings2() that made
17597 it do bad things when you hand it an empty smartlist.
17598 - Fix Windows installer to ship Tor license (thanks to Aphex for
17599 pointing out this oversight) and put a link to the doc directory
17601 - Explicitly set no-unaligned-access for sparc: it turns out the
17602 new gcc's let you compile broken code, but that doesn't make it
17606 Changes in version 0.1.1.3-alpha - 2005-07-23
17607 o Bugfixes on 0.1.1.2-alpha:
17608 - Fix a bug in handling the controller's "post descriptor"
17610 - Fix several bugs in handling the controller's "extend circuit"
17612 - Fix a bug in handling the controller's "stream status" event.
17613 - Fix an assert failure if we have a controller listening for
17614 circuit events and we go offline.
17615 - Re-allow hidden service descriptors to publish 0 intro points.
17616 - Fix a crash when generating your hidden service descriptor if
17617 you don't have enough intro points already.
17619 o New features on 0.1.1.2-alpha:
17620 - New controller function "getinfo accounting", to ask how
17621 many bytes we've used in this time period.
17622 - Experimental support for helper nodes: a lot of the risk from
17623 a small static adversary comes because users pick new random
17624 nodes every time they rebuild a circuit. Now users will try to
17625 stick to the same small set of entry nodes if they can. Not
17626 enabled by default yet.
17628 o Bugfixes on 0.1.0.12:
17629 - If you're an auth dir server, always publish your dirport,
17630 even if you haven't yet found yourself to be reachable.
17631 - Fix a size_t underflow in smartlist_join_strings2() that made
17632 it do bad things when you hand it an empty smartlist.
17635 Changes in version 0.1.0.12 - 2005-07-18
17636 o New directory servers:
17637 - tor26 has changed IP address.
17639 o Bugfixes on 0.1.0.x:
17640 - Fix a possible double-free in tor_gzip_uncompress().
17641 - When --disable-threads is set, do not search for or link against
17642 pthreads libraries.
17643 - Don't trigger an assert if an authoritative directory server
17644 claims its dirport is 0.
17645 - Fix bug with removing Tor as an NT service: some people were
17646 getting "The service did not return an error." Thanks to Matt
17650 Changes in version 0.1.1.2-alpha - 2005-07-15
17651 o New directory servers:
17652 - tor26 has changed IP address.
17654 o Bugfixes on 0.1.0.x, crashes/leaks:
17655 - Port the servers-not-obeying-their-exit-policies fix from
17657 - Fix an fd leak in start_daemon().
17658 - On Windows, you can't always reopen a port right after you've
17659 closed it. So change retry_listeners() to only close and re-open
17660 ports that have changed.
17661 - Fix a possible double-free in tor_gzip_uncompress().
17663 o Bugfixes on 0.1.0.x, usability:
17664 - When tor_socketpair() fails in Windows, give a reasonable
17665 Windows-style errno back.
17666 - Let people type "tor --install" as well as "tor -install" when
17668 want to make it an NT service.
17669 - NT service patch from Matt Edman to improve error messages.
17670 - When the controller asks for a config option with an abbreviated
17671 name, give the full name in our response.
17672 - Correct the man page entry on TrackHostExitsExpire.
17673 - Looks like we were never delivering deflated (i.e. compressed)
17674 running-routers lists, even when asked. Oops.
17675 - When --disable-threads is set, do not search for or link against
17676 pthreads libraries.
17678 o Bugfixes on 0.1.1.x:
17679 - Fix a seg fault with autodetecting which controller version is
17683 - New hidden service descriptor format: put a version in it, and
17684 let people specify introduction/rendezvous points that aren't
17685 in "the directory" (which is subjective anyway).
17686 - Allow the DEBUG controller event to work again. Mark certain log
17687 entries as "don't tell this to controllers", so we avoid cycles.
17690 Changes in version 0.1.0.11 - 2005-06-30
17691 o Bugfixes on 0.1.0.x:
17692 - Fix major security bug: servers were disregarding their
17693 exit policies if clients behaved unexpectedly.
17694 - Make OS X init script check for missing argument, so we don't
17695 confuse users who invoke it incorrectly.
17696 - Fix a seg fault in "tor --hash-password foo".
17697 - The MAPADDRESS control command was broken.
17700 Changes in version 0.1.1.1-alpha - 2005-06-29
17702 - Make OS X init script check for missing argument, so we don't
17703 confuse users who invoke it incorrectly.
17704 - Fix a seg fault in "tor --hash-password foo".
17705 - Fix a possible way to DoS dirservers.
17706 - When we complain that your exit policy implicitly allows local or
17707 private address spaces, name them explicitly so operators can
17709 - Make the log message less scary when all the dirservers are
17710 temporarily unreachable.
17711 - We were printing the number of idle dns workers incorrectly when
17715 - Revised controller protocol (version 1) that uses ascii rather
17716 than binary. Add supporting libraries in python and java so you
17717 can use the controller from your applications without caring how
17718 our protocol works.
17719 - Spiffy new support for crypto hardware accelerators. Can somebody
17723 Changes in version 0.0.9.10 - 2005-06-16
17724 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
17725 - Refuse relay cells that claim to have a length larger than the
17726 maximum allowed. This prevents a potential attack that could read
17727 arbitrary memory (e.g. keys) from an exit server's process
17731 Changes in version 0.1.0.10 - 2005-06-14
17732 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
17733 libevent before 1.1a.
17736 Changes in version 0.1.0.9-rc - 2005-06-09
17738 - Reset buf->highwater every time buf_shrink() is called, not just on
17739 a successful shrink. This was causing significant memory bloat.
17740 - Fix buffer overflow when checking hashed passwords.
17741 - Security fix: if seeding the RNG on Win32 fails, quit.
17742 - Allow seeding the RNG on Win32 even when you're not running as
17744 - Disable threading on Solaris too. Something is wonky with it,
17745 cpuworkers, and reentrant libs.
17746 - Reenable the part of the code that tries to flush as soon as an
17747 OR outbuf has a full TLS record available. Perhaps this will make
17748 OR outbufs not grow as huge except in rare cases, thus saving lots
17749 of CPU time plus memory.
17750 - Reject malformed .onion addresses rather then passing them on as
17751 normal web requests.
17752 - Adapt patch from Adam Langley: fix possible memory leak in
17753 tor_lookup_hostname().
17754 - Initialize libevent later in the startup process, so the logs are
17755 already established by the time we start logging libevent warns.
17756 - Use correct errno on win32 if libevent fails.
17757 - Check and warn about known-bad/slow libevent versions.
17758 - Pay more attention to the ClientOnly config option.
17759 - Have torctl.in/tor.sh.in check for location of su binary (needed
17761 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
17762 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
17763 HttpProxyAuthenticator
17764 - Stop warning about sigpipes in the logs. We're going to
17765 pretend that getting these occassionally is normal and fine.
17766 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
17768 installer screens; and don't put stuff into StartupItems unless
17769 the user asks you to.
17770 - Require servers that use the default dirservers to have public IP
17771 addresses. We have too many servers that are configured with private
17772 IPs and their admins never notice the log entries complaining that
17773 their descriptors are being rejected.
17774 - Add OSX uninstall instructions. An actual uninstall script will
17778 Changes in version 0.1.0.8-rc - 2005-05-23
17780 - It turns out that kqueue on OS X 10.3.9 was causing kernel
17781 panics. Disable kqueue on all OS X Tors.
17782 - Fix RPM: remove duplicate line accidentally added to the rpm
17784 - Disable threads on openbsd too, since its gethostaddr is not
17786 - Tolerate libevent 0.8 since it still works, even though it's
17788 - Enable building on Red Hat 9.0 again.
17789 - Allow the middle hop of the testing circuit to be running any
17790 version, now that most of them have the bugfix to let them connect
17791 to unknown servers. This will allow reachability testing to work
17792 even when 0.0.9.7-0.0.9.9 become obsolete.
17793 - Handle relay cells with rh.length too large. This prevents
17794 a potential attack that could read arbitrary memory (maybe even
17795 keys) from the exit server's process.
17796 - We screwed up the dirport reachability testing when we don't yet
17797 have a cached version of the directory. Hopefully now fixed.
17798 - Clean up router_load_single_router() (used by the controller),
17799 so it doesn't seg fault on error.
17800 - Fix a minor memory leak when somebody establishes an introduction
17801 point at your Tor server.
17802 - If a socks connection ends because read fails, don't warn that
17803 you're not sending a socks reply back.
17806 - Add HttpProxyAuthenticator config option too, that works like
17807 the HttpsProxyAuthenticator config option.
17808 - Encode hashed controller passwords in hex instead of base64,
17809 to make it easier to write controllers.
17812 Changes in version 0.1.0.7-rc - 2005-05-17
17814 - Fix a bug in the OS X package installer that prevented it from
17815 installing on Tiger.
17816 - Fix a script bug in the OS X package installer that made it
17817 complain during installation.
17818 - Find libevent even if it's hiding in /usr/local/ and your
17819 CFLAGS and LDFLAGS don't tell you to look there.
17820 - Be able to link with libevent as a shared library (the default
17821 after 1.0d), even if it's hiding in /usr/local/lib and even
17822 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
17823 assuming you're running gcc. Otherwise fail and give a useful
17825 - Fix a bug in the RPM packager: set home directory for _tor to
17826 something more reasonable when first installing.
17827 - Free a minor amount of memory that is still reachable on exit.
17830 Changes in version 0.1.0.6-rc - 2005-05-14
17832 - Implement --disable-threads configure option. Disable threads on
17833 netbsd by default, because it appears to have no reentrant resolver
17835 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
17836 release (1.1) detects and disables kqueue if it's broken.
17837 - Append default exit policy before checking for implicit internal
17838 addresses. Now we don't log a bunch of complaints on startup
17839 when using the default exit policy.
17840 - Some people were putting "Address " in their torrc, and they had
17841 a buggy resolver that resolved " " to 0.0.0.0. Oops.
17842 - If DataDir is ~/.tor, and that expands to /.tor, then default to
17843 LOCALSTATEDIR/tor instead.
17844 - Fix fragmented-message bug in TorControl.py.
17845 - Resolve a minor bug which would prevent unreachable dirports
17846 from getting suppressed in the published descriptor.
17847 - When the controller gave us a new descriptor, we weren't resolving
17848 it immediately, so Tor would think its address was 0.0.0.0 until
17849 we fetched a new directory.
17850 - Fix an uppercase/lowercase case error in suppressing a bogus
17851 libevent warning on some Linuxes.
17854 - Begin scrubbing sensitive strings from logs by default. Turn off
17855 the config option SafeLogging if you need to do debugging.
17856 - Switch to a new buffer management algorithm, which tries to avoid
17857 reallocing and copying quite as much. In first tests it looks like
17858 it uses *more* memory on average, but less cpu.
17859 - First cut at support for "create-fast" cells. Clients can use
17860 these when extending to their first hop, since the TLS already
17861 provides forward secrecy and authentication. Not enabled on
17863 - When dirservers refuse a router descriptor, we now log its
17864 contactinfo, platform, and the poster's IP address.
17865 - Call tor_free_all instead of connections_free_all after forking, to
17866 save memory on systems that need to fork.
17867 - Whine at you if you're a server and you don't set your contactinfo.
17868 - Implement --verify-config command-line option to check if your torrc
17869 is valid without actually launching Tor.
17870 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
17871 rather than just rejecting it.
17874 Changes in version 0.1.0.5-rc - 2005-04-27
17876 - Stop trying to print a null pointer if an OR conn fails because
17877 we didn't like its cert.
17879 - Switch our internal buffers implementation to use a ring buffer,
17880 to hopefully improve performance for fast servers a lot.
17881 - Add HttpsProxyAuthenticator support (basic auth only), based
17882 on patch from Adam Langley.
17883 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
17884 the fast servers that have been joining lately.
17885 - Give hidden service accesses extra time on the first attempt,
17886 since 60 seconds is often only barely enough. This might improve
17888 - Improve performance for dirservers: stop re-parsing the whole
17889 directory every time you regenerate it.
17890 - Add more debugging info to help us find the weird dns freebsd
17891 pthreads bug; cleaner debug messages to help track future issues.
17894 Changes in version 0.0.9.9 - 2005-04-23
17895 o Bugfixes on 0.0.9.x:
17896 - If unofficial Tor clients connect and send weird TLS certs, our
17897 Tor server triggers an assert. This release contains a minimal
17898 backport from the broader fix that we put into 0.1.0.4-rc.
17901 Changes in version 0.1.0.4-rc - 2005-04-23
17903 - If unofficial Tor clients connect and send weird TLS certs, our
17904 Tor server triggers an assert. Stop asserting, and start handling
17905 TLS errors better in other situations too.
17906 - When the controller asks us to tell it about all the debug-level
17907 logs, it turns out we were generating debug-level logs while
17908 telling it about them, which turns into a bad loop. Now keep
17909 track of whether you're sending a debug log to the controller,
17910 and don't log when you are.
17911 - Fix the "postdescriptor" feature of the controller interface: on
17912 non-complete success, only say "done" once.
17914 - Clients are now willing to load balance over up to 2mB, not 1mB,
17915 of advertised bandwidth capacity.
17916 - Add a NoPublish config option, so you can be a server (e.g. for
17917 testing running Tor servers in other Tor networks) without
17918 publishing your descriptor to the primary dirservers.
17921 Changes in version 0.1.0.3-rc - 2005-04-08
17922 o Improvements on 0.1.0.2-rc:
17923 - Client now retries when streams end early for 'hibernating' or
17924 'resource limit' reasons, rather than failing them.
17925 - More automated handling for dirserver operators:
17926 - Automatically approve nodes running 0.1.0.2-rc or later,
17927 now that the the reachability detection stuff is working.
17928 - Now we allow two unverified servers with the same nickname
17929 but different keys. But if a nickname is verified, only that
17930 nickname+key are allowed.
17931 - If you're an authdirserver connecting to an address:port,
17932 and it's not the OR you were expecting, forget about that
17933 descriptor. If he *was* the one you were expecting, then forget
17934 about all other descriptors for that address:port.
17935 - Allow servers to publish descriptors from 12 hours in the future.
17936 Corollary: only whine about clock skew from the dirserver if
17937 he's a trusted dirserver (since now even verified servers could
17938 have quite wrong clocks).
17939 - Adjust maximum skew and age for rendezvous descriptors: let skew
17940 be 48 hours rather than 90 minutes.
17941 - Efficiency improvements:
17942 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
17943 it much faster to look up a circuit for each relay cell.
17944 - Remove most calls to assert_all_pending_dns_resolves_ok(),
17945 since they're eating our cpu on exit nodes.
17946 - Stop wasting time doing a case insensitive comparison for every
17947 dns name every time we do any lookup. Canonicalize the names to
17948 lowercase and be done with it.
17949 - Start sending 'truncated' cells back rather than destroy cells,
17950 if the circuit closes in front of you. This means we won't have
17951 to abandon partially built circuits.
17952 - Only warn once per nickname from add_nickname_list_to_smartlist
17953 per failure, so an entrynode or exitnode choice that's down won't
17955 - Put a note in the torrc about abuse potential with the default
17957 - Revise control spec and implementation to allow all log messages to
17958 be sent to controller with their severities intact (suggested by
17959 Matt Edman). Update TorControl to handle new log event types.
17960 - Provide better explanation messages when controller's POSTDESCRIPTOR
17962 - Stop putting nodename in the Platform string in server descriptors.
17963 It doesn't actually help, and it is confusing/upsetting some people.
17965 o Bugfixes on 0.1.0.2-rc:
17966 - We were printing the host mask wrong in exit policies in server
17967 descriptors. This isn't a critical bug though, since we were still
17968 obeying the exit policy internally.
17969 - Fix Tor when compiled with libevent but without pthreads: move
17970 connection_unregister() from _connection_free() to
17972 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
17973 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
17974 when we look through the connection array, we'll find any of the
17975 cpu/dnsworkers. This is no good.
17977 o Bugfixes on 0.0.9.8:
17978 - Fix possible bug on threading platforms (e.g. win32) which was
17979 leaking a file descriptor whenever a cpuworker or dnsworker died.
17980 - When using preferred entry or exit nodes, ignore whether the
17981 circuit wants uptime or capacity. They asked for the nodes, they
17983 - chdir() to your datadirectory at the *end* of the daemonize process,
17984 not the beginning. This was a problem because the first time you
17985 run tor, if your datadir isn't there, and you have runasdaemon set
17986 to 1, it will try to chdir to it before it tries to create it. Oops.
17987 - Handle changed router status correctly when dirserver reloads
17988 fingerprint file. We used to be dropping all unverified descriptors
17989 right then. The bug was hidden because we would immediately
17990 fetch a directory from another dirserver, which would include the
17991 descriptors we just dropped.
17992 - When we're connecting to an OR and he's got a different nickname/key
17993 than we were expecting, only complain loudly if we're an OP or a
17994 dirserver. Complaining loudly to the OR admins just confuses them.
17995 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
17996 artificially capped at 500kB.
17999 Changes in version 0.0.9.8 - 2005-04-07
18000 o Bugfixes on 0.0.9.x:
18001 - We have a bug that I haven't found yet. Sometimes, very rarely,
18002 cpuworkers get stuck in the 'busy' state, even though the cpuworker
18003 thinks of itself as idle. This meant that no new circuits ever got
18004 established. Here's a workaround to kill any cpuworker that's been
18005 busy for more than 100 seconds.
18008 Changes in version 0.1.0.2-rc - 2005-04-01
18009 o Bugfixes on 0.1.0.1-rc:
18010 - Fixes on reachability detection:
18011 - Don't check for reachability while hibernating.
18012 - If ORPort is reachable but DirPort isn't, still publish the
18013 descriptor, but zero out DirPort until it's found reachable.
18014 - When building testing circs for ORPort testing, use only
18015 high-bandwidth nodes, so fewer circuits fail.
18016 - Complain about unreachable ORPort separately from unreachable
18017 DirPort, so the user knows what's going on.
18018 - Make sure we only conclude ORPort reachability if we didn't
18019 initiate the conn. Otherwise we could falsely conclude that
18020 we're reachable just because we connected to the guy earlier
18021 and he used that same pipe to extend to us.
18022 - Authdirservers shouldn't do ORPort reachability detection,
18023 since they're in clique mode, so it will be rare to find a
18024 server not already connected to them.
18025 - When building testing circuits, always pick middle hops running
18026 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
18027 bug. (This is a kludge; it will go away when 0.0.9.x becomes
18029 - When we decide we're reachable, actually publish our descriptor
18031 - Fix bug in redirectstream in the controller.
18032 - Fix the state descriptor strings so logs don't claim edge streams
18033 are in a different state than they actually are.
18034 - Use recent libevent features when possible (this only really affects
18035 win32 and osx right now, because the new libevent with these
18036 features hasn't been released yet). Add code to suppress spurious
18038 - Prevent possible segfault in connection_close_unattached_ap().
18039 - Fix newlines on torrc in win32.
18040 - Improve error msgs when tor-resolve fails.
18042 o Improvements on 0.0.9.x:
18043 - New experimental script tor/contrib/ExerciseServer.py (needs more
18044 work) that uses the controller interface to build circuits and
18045 fetch pages over them. This will help us bootstrap servers that
18046 have lots of capacity but haven't noticed it yet.
18047 - New experimental script tor/contrib/PathDemo.py (needs more work)
18048 that uses the controller interface to let you choose whole paths
18050 "<hostname>.<path,separated by dots>.<length of path>.path"
18051 - When we've connected to an OR and handshaked but didn't like
18052 the result, we were closing the conn without sending destroy
18053 cells back for pending circuits. Now send those destroys.
18056 Changes in version 0.0.9.7 - 2005-04-01
18057 o Bugfixes on 0.0.9.x:
18058 - Fix another race crash bug (thanks to Glenn Fink for reporting).
18059 - Compare identity to identity, not to nickname, when extending to
18060 a router not already in the directory. This was preventing us from
18061 extending to unknown routers. Oops.
18062 - Make sure to create OS X Tor user in <500 range, so we aren't
18063 creating actual system users.
18064 - Note where connection-that-hasn't-sent-end was marked, and fix
18065 a few really loud instances of this harmless bug (it's fixed more
18069 Changes in version 0.1.0.1-rc - 2005-03-28
18071 - Add reachability testing. Your Tor server will automatically try
18072 to see if its ORPort and DirPort are reachable from the outside,
18073 and it won't upload its descriptor until it decides they are.
18074 - Handle unavailable hidden services better. Handle slow or busy
18075 hidden services better.
18076 - Add support for CONNECTing through https proxies, with "HttpsProxy"
18078 - New exit policy: accept most low-numbered ports, rather than
18079 rejecting most low-numbered ports.
18080 - More Tor controller support (still experimental). See
18081 http://tor.eff.org/doc/control-spec.txt for all the new features,
18082 including signals to emulate unix signals from any platform;
18083 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
18084 closestream; closecircuit; etc.
18085 - Make nt services work and start on startup on win32 (based on
18086 patch by Matt Edman).
18087 - Add a new AddressMap config directive to rewrite incoming socks
18088 addresses. This lets you, for example, declare an implicit
18089 required exit node for certain sites.
18090 - Add a new TrackHostExits config directive to trigger addressmaps
18091 for certain incoming socks addresses -- for sites that break when
18092 your exit keeps changing (based on patch by Mike Perry).
18093 - Redo the client-side dns cache so it's just an addressmap too.
18094 - Notice when our IP changes, and reset stats/uptime/reachability.
18095 - When an application is using socks5, give him the whole variety of
18096 potential socks5 responses (connect refused, host unreachable, etc),
18097 rather than just "success" or "failure".
18098 - A more sane version numbering system. See
18099 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
18100 - New contributed script "exitlist": a simple python script to
18101 parse directories and find Tor nodes that exit to listed
18103 - New contributed script "privoxy-tor-toggle" to toggle whether
18104 Privoxy uses Tor. Seems to be configured for Debian by default.
18105 - Report HTTP reasons to client when getting a response from directory
18106 servers -- so you can actually know what went wrong.
18107 - New config option MaxAdvertisedBandwidth which lets you advertise
18108 a low bandwidthrate (to not attract as many circuits) while still
18109 allowing a higher bandwidthrate in reality.
18111 o Robustness/stability fixes:
18112 - Make Tor use Niels Provos's libevent instead of its current
18113 poll-but-sometimes-select mess. This will let us use faster async
18114 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
18116 - pthread support now too. This was forced because when we forked,
18117 we ended up wasting a lot of duplicate ram over time. Also switch
18118 to foo_r versions of some library calls to allow reentry and
18120 - Better handling for heterogeneous / unreliable nodes:
18121 - Annotate circuits w/ whether they aim to contain high uptime nodes
18122 and/or high capacity nodes. When building circuits, choose
18124 - This means that every single node in an intro rend circuit,
18125 not just the last one, will have a minimum uptime.
18126 - New config option LongLivedPorts to indicate application streams
18127 that will want high uptime circuits.
18128 - Servers reset uptime when a dir fetch entirely fails. This
18129 hopefully reflects stability of the server's network connectivity.
18130 - If somebody starts his tor server in Jan 2004 and then fixes his
18131 clock, don't make his published uptime be a year.
18132 - Reset published uptime when you wake up from hibernation.
18133 - Introduce a notion of 'internal' circs, which are chosen without
18134 regard to the exit policy of the last hop. Intro and rendezvous
18135 circs must be internal circs, to avoid leaking information. Resolve
18136 and connect streams can use internal circs if they want.
18137 - New circuit pooling algorithm: make sure to have enough circs around
18138 to satisfy any predicted ports, and also make sure to have 2 internal
18139 circs around if we've required internal circs lately (and with high
18140 uptime if we've seen that lately too).
18141 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
18142 which describes how often we retry making new circuits if current
18143 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
18144 how long we're willing to make use of an already-dirty circuit.
18145 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
18146 circ as necessary, if there are any completed ones lying around
18147 when we try to launch one.
18148 - Make hidden services try to establish a rendezvous for 30 seconds,
18149 rather than for n (where n=3) attempts to build a circuit.
18150 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
18151 "ShutdownWaitLength".
18152 - Try to be more zealous about calling connection_edge_end when
18153 things go bad with edge conns in connection.c.
18154 - Revise tor-spec to add more/better stream end reasons.
18155 - Revise all calls to connection_edge_end to avoid sending "misc",
18156 and to take errno into account where possible.
18159 - Fix a race condition that can trigger an assert, when we have a
18160 pending create cell and an OR connection fails right then.
18161 - Fix several double-mark-for-close bugs, e.g. where we were finding
18162 a conn for a cell even if that conn is already marked for close.
18163 - Make sequence of log messages when starting on win32 with no config
18164 file more reasonable.
18165 - When choosing an exit node for a new non-internal circ, don't take
18166 into account whether it'll be useful for any pending x.onion
18167 addresses -- it won't.
18168 - Turn addr_policy_compare from a tristate to a quadstate; this should
18169 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
18170 for google.com" problem.
18171 - Make "platform" string in descriptor more accurate for Win32 servers,
18172 so it's not just "unknown platform".
18173 - Fix an edge case in parsing config options (thanks weasel).
18174 If they say "--" on the commandline, it's not an option.
18175 - Reject odd-looking addresses at the client (e.g. addresses that
18176 contain a colon), rather than having the server drop them because
18178 - tor-resolve requests were ignoring .exit if there was a working circuit
18179 they could use instead.
18180 - REUSEADDR on normal platforms means you can rebind to the port
18181 right after somebody else has let it go. But REUSEADDR on win32
18182 means to let you bind to the port _even when somebody else
18183 already has it bound_! So, don't do that on Win32.
18184 - Change version parsing logic: a version is "obsolete" if it is not
18185 recommended and (1) there is a newer recommended version in the
18186 same series, or (2) there are no recommended versions in the same
18187 series, but there are some recommended versions in a newer series.
18188 A version is "new" if it is newer than any recommended version in
18190 - Stop most cases of hanging up on a socks connection without sending
18194 - Require BandwidthRate to be at least 20kB/s for servers.
18195 - When a dirserver causes you to give a warn, mention which dirserver
18197 - New config option DirAllowPrivateAddresses for authdirservers.
18198 Now by default they refuse router descriptors that have non-IP or
18199 private-IP addresses.
18200 - Stop publishing socksport in the directory, since it's not
18201 actually meant to be public. For compatibility, publish a 0 there
18203 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
18204 smart" value, that is low for servers and high for clients.
18205 - If our clock jumps forward by 100 seconds or more, assume something
18206 has gone wrong with our network and abandon all not-yet-used circs.
18207 - Warn when exit policy implicitly allows local addresses.
18208 - If we get an incredibly skewed timestamp from a dirserver mirror
18209 that isn't a verified OR, don't warn -- it's probably him that's
18211 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
18212 cookies to disk and doesn't log each web request to disk. (Thanks
18213 to Brett Carrington for pointing this out.)
18214 - When a client asks us for a dir mirror and we don't have one,
18215 launch an attempt to get a fresh one.
18216 - If we're hibernating and we get a SIGINT, exit immediately.
18217 - Add --with-dmalloc ./configure option, to track memory leaks.
18218 - And try to free all memory on closing, so we can detect what
18220 - Cache local dns resolves correctly even when they're .exit
18222 - Give a better warning when some other server advertises an
18223 ORPort that is actually an apache running ssl.
18224 - Add "opt hibernating 1" to server descriptor to make it clearer
18225 whether the server is hibernating.
18228 Changes in version 0.0.9.6 - 2005-03-24
18229 o Bugfixes on 0.0.9.x (crashes and asserts):
18230 - Add new end stream reasons to maintainance branch. Fix bug where
18231 reason (8) could trigger an assert. Prevent bug from recurring.
18232 - Apparently win32 stat wants paths to not end with a slash.
18233 - Fix assert triggers in assert_cpath_layer_ok(), where we were
18234 blowing away the circuit that conn->cpath_layer points to, then
18235 checking to see if the circ is well-formed. Backport check to make
18236 sure we dont use the cpath on a closed connection.
18237 - Prevent circuit_resume_edge_reading_helper() from trying to package
18238 inbufs for marked-for-close streams.
18239 - Don't crash on hup if your options->address has become unresolvable.
18240 - Some systems (like OS X) sometimes accept() a connection and tell
18241 you the remote host is 0.0.0.0:0. If this happens, due to some
18242 other mis-features, we get confused; so refuse the conn for now.
18244 o Bugfixes on 0.0.9.x (other):
18245 - Fix harmless but scary "Unrecognized content encoding" warn message.
18246 - Add new stream error reason: TORPROTOCOL reason means "you are not
18247 speaking a version of Tor I understand; say bye-bye to your stream."
18248 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
18249 into the future, now that we are more tolerant of skew. This
18250 resolves a bug where a Tor server would refuse to cache a directory
18251 because all the directories it gets are too far in the future;
18252 yet the Tor server never logs any complaints about clock skew.
18253 - Mac packaging magic: make man pages useable, and do not overwrite
18254 existing torrc files.
18255 - Make OS X log happily to /var/log/tor/tor.log
18258 Changes in version 0.0.9.5 - 2005-02-22
18259 o Bugfixes on 0.0.9.x:
18260 - Fix an assert race at exit nodes when resolve requests fail.
18261 - Stop picking unverified dir mirrors--it only leads to misery.
18262 - Patch from Matt Edman to make NT services work better. Service
18263 support is still not compiled into the executable by default.
18264 - Patch from Dmitri Bely so the Tor service runs better under
18265 the win32 SYSTEM account.
18266 - Make tor-resolve actually work (?) on Win32.
18267 - Fix a sign bug when getrlimit claims to have 4+ billion
18268 file descriptors available.
18269 - Stop refusing to start when bandwidthburst == bandwidthrate.
18270 - When create cells have been on the onion queue more than five
18271 seconds, just send back a destroy and take them off the list.
18274 Changes in version 0.0.9.4 - 2005-02-03
18275 o Bugfixes on 0.0.9:
18276 - Fix an assert bug that took down most of our servers: when
18277 a server claims to have 1 GB of bandwidthburst, don't
18279 - Don't crash as badly if we have spawned the max allowed number
18280 of dnsworkers, or we're out of file descriptors.
18281 - Block more file-sharing ports in the default exit policy.
18282 - MaxConn is now automatically set to the hard limit of max
18283 file descriptors we're allowed (ulimit -n), minus a few for
18285 - Give a clearer message when servers need to raise their
18286 ulimit -n when they start running out of file descriptors.
18287 - SGI Compatibility patches from Jan Schaumann.
18288 - Tolerate a corrupt cached directory better.
18289 - When a dirserver hasn't approved your server, list which one.
18290 - Go into soft hibernation after 95% of the bandwidth is used,
18291 not 99%. This is especially important for daily hibernators who
18292 have a small accounting max. Hopefully it will result in fewer
18293 cut connections when the hard hibernation starts.
18294 - Load-balance better when using servers that claim more than
18295 800kB/s of capacity.
18296 - Make NT services work (experimental, only used if compiled in).
18299 Changes in version 0.0.9.3 - 2005-01-21
18300 o Bugfixes on 0.0.9:
18301 - Backport the cpu use fixes from main branch, so busy servers won't
18302 need as much processor time.
18303 - Work better when we go offline and then come back, or when we
18304 run Tor at boot before the network is up. We do this by
18305 optimistically trying to fetch a new directory whenever an
18306 application request comes in and we think we're offline -- the
18307 human is hopefully a good measure of when the network is back.
18308 - Backport some minimal hidserv bugfixes: keep rend circuits open as
18309 long as you keep using them; actually publish hidserv descriptors
18310 shortly after they change, rather than waiting 20-40 minutes.
18311 - Enable Mac startup script by default.
18312 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
18313 - When you update AllowUnverifiedNodes or FirewallPorts via the
18314 controller's setconf feature, we were always appending, never
18316 - When you update HiddenServiceDir via setconf, it was screwing up
18317 the order of reading the lines, making it fail.
18318 - Do not rewrite a cached directory back to the cache; otherwise we
18319 will think it is recent and not fetch a newer one on startup.
18320 - Workaround for webservers that lie about Content-Encoding: Tor
18321 now tries to autodetect compressed directories and compression
18322 itself. This lets us Proxypass dir fetches through apache.
18325 Changes in version 0.0.9.2 - 2005-01-04
18326 o Bugfixes on 0.0.9 (crashes and asserts):
18327 - Fix an assert on startup when the disk is full and you're logging
18329 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
18330 style address, then we'd crash.
18331 - Fix an assert trigger when the running-routers string we get from
18332 a dirserver is broken.
18333 - Make worker threads start and run on win32. Now win32 servers
18335 - Bandaid (not actually fix, but now it doesn't crash) an assert
18336 where the dns worker dies mysteriously and the main Tor process
18337 doesn't remember anything about the address it was resolving.
18339 o Bugfixes on 0.0.9 (Win32):
18340 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
18341 name out of the warning/assert messages.
18342 - Fix a superficial "unhandled error on read" bug on win32.
18343 - The win32 installer no longer requires a click-through for our
18344 license, since our Free Software license grants rights but does not
18346 - Win32: When connecting to a dirserver fails, try another one
18347 immediately. (This was already working for non-win32 Tors.)
18348 - Stop trying to parse $HOME on win32 when hunting for default
18350 - Make tor-resolve.c work on win32 by calling network_init().
18352 o Bugfixes on 0.0.9 (other):
18353 - Make 0.0.9.x build on Solaris again.
18354 - Due to a fencepost error, we were blowing away the \n when reporting
18355 confvalue items in the controller. So asking for multiple config
18356 values at once couldn't work.
18357 - When listing circuits that are pending on an opening OR connection,
18358 if we're an OR we were listing circuits that *end* at us as
18359 being pending on every listener, dns/cpu worker, etc. Stop that.
18360 - Dirservers were failing to create 'running-routers' or 'directory'
18361 strings if we had more than some threshold of routers. Fix them so
18362 they can handle any number of routers.
18363 - Fix a superficial "Duplicate mark for close" bug.
18364 - Stop checking for clock skew for OR connections, even for servers.
18365 - Fix a fencepost error that was chopping off the last letter of any
18366 nickname that is the maximum allowed nickname length.
18367 - Update URLs in log messages so they point to the new website.
18368 - Fix a potential problem in mangling server private keys while
18369 writing to disk (not triggered yet, as far as we know).
18370 - Include the licenses for other free software we include in Tor,
18371 now that we're shipping binary distributions more regularly.
18374 Changes in version 0.0.9.1 - 2004-12-15
18375 o Bugfixes on 0.0.9:
18376 - Make hibernation actually work.
18377 - Make HashedControlPassword config option work.
18378 - When we're reporting event circuit status to a controller,
18379 don't use the stream status code.
18382 Changes in version 0.0.9 - 2004-12-12
18384 - Clean up manpage and torrc.sample file.
18385 - Clean up severities and text of log warnings.
18387 - Make servers trigger an assert when they enter hibernation.
18390 Changes in version 0.0.9rc7 - 2004-12-08
18391 o Bugfixes on 0.0.9rc:
18392 - Fix a stack-trashing crash when an exit node begins hibernating.
18393 - Avoid looking at unallocated memory while considering which
18394 ports we need to build circuits to cover.
18395 - Stop a sigpipe: when an 'end' cell races with eof from the app,
18396 we shouldn't hold-open-until-flush if the eof arrived first.
18397 - Fix a bug with init_cookie_authentication() in the controller.
18398 - When recommending new-format log lines, if the upper bound is
18399 LOG_ERR, leave it implicit.
18401 o Bugfixes on 0.0.8.1:
18402 - Fix a whole slew of memory leaks.
18403 - Fix isspace() and friends so they still make Solaris happy
18404 but also so they don't trigger asserts on win32.
18405 - Fix parse_iso_time on platforms without strptime (eg win32).
18406 - win32: tolerate extra "readable" events better.
18407 - win32: when being multithreaded, leave parent fdarray open.
18408 - Make unit tests work on win32.
18411 Changes in version 0.0.9rc6 - 2004-12-06
18412 o Bugfixes on 0.0.9pre:
18413 - Clean up some more integer underflow opportunities (not exploitable
18415 - While hibernating, hup should not regrow our listeners.
18416 - Send an end to the streams we close when we hibernate, rather
18417 than just chopping them off.
18418 - React to eof immediately on non-open edge connections.
18420 o Bugfixes on 0.0.8.1:
18421 - Calculate timeout for waiting for a connected cell from the time
18422 we sent the begin cell, not from the time the stream started. If
18423 it took a long time to establish the circuit, we would time out
18424 right after sending the begin cell.
18425 - Fix router_compare_addr_to_addr_policy: it was not treating a port
18426 of * as always matching, so we were picking reject *:* nodes as
18427 exit nodes too. Oops.
18430 - New circuit building strategy: keep a list of ports that we've
18431 used in the past 6 hours, and always try to have 2 circuits open
18432 or on the way that will handle each such port. Seed us with port
18433 80 so web users won't complain that Tor is "slow to start up".
18434 - Make kill -USR1 dump more useful stats about circuits.
18435 - When warning about retrying or giving up, print the address, so
18436 the user knows which one it's talking about.
18437 - If you haven't used a clean circuit in an hour, throw it away,
18438 just to be on the safe side. (This means after 6 hours a totally
18439 unused Tor client will have no circuits open.)
18442 Changes in version 0.0.9rc5 - 2004-12-01
18443 o Bugfixes on 0.0.8.1:
18444 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
18445 - Let resolve conns retry/expire also, rather than sticking around
18447 - If we are using select, make sure we stay within FD_SETSIZE.
18449 o Bugfixes on 0.0.9pre:
18450 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
18451 but doesn't seem to be currently; thanks to Ilja van Sprundel for
18453 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
18454 instead. Impose minima and maxima for all *Period options; impose
18455 even tighter maxima for fetching if we are a caching dirserver.
18456 Clip rather than rejecting.
18457 - Fetch cached running-routers from servers that serve it (that is,
18458 authdirservers and servers running 0.0.9rc5-cvs or later.)
18461 - Accept *:706 (silc) in default exit policy.
18462 - Implement new versioning format for post 0.1.
18463 - Support "foo.nickname.exit" addresses, to let Alice request the
18464 address "foo" as viewed by exit node "nickname". Based on a patch
18466 - Make tor --version --version dump the cvs Id of every file.
18469 Changes in version 0.0.9rc4 - 2004-11-28
18470 o Bugfixes on 0.0.8.1:
18471 - Make windows sockets actually non-blocking (oops), and handle
18472 win32 socket errors better.
18474 o Bugfixes on 0.0.9rc1:
18475 - Actually catch the -USR2 signal.
18478 Changes in version 0.0.9rc3 - 2004-11-25
18479 o Bugfixes on 0.0.8.1:
18480 - Flush the log file descriptor after we print "Tor opening log file",
18481 so we don't see those messages days later.
18483 o Bugfixes on 0.0.9rc1:
18484 - Make tor-resolve work again.
18485 - Avoid infinite loop in tor-resolve if tor hangs up on it.
18486 - Fix an assert trigger for clients/servers handling resolves.
18489 Changes in version 0.0.9rc2 - 2004-11-24
18490 o Bugfixes on 0.0.9rc1:
18491 - I broke socks5 support while fixing the eof bug.
18492 - Allow unitless bandwidths and intervals; they default to bytes
18494 - New servers don't start out hibernating; they are active until
18495 they run out of bytes, so they have a better estimate of how
18496 long it takes, and so their operators can know they're working.
18499 Changes in version 0.0.9rc1 - 2004-11-23
18500 o Bugfixes on 0.0.8.1:
18501 - Finally fix a bug that's been plaguing us for a year:
18502 With high load, circuit package window was reaching 0. Whenever
18503 we got a circuit-level sendme, we were reading a lot on each
18504 socket, but only writing out a bit. So we would eventually reach
18505 eof. This would be noticed and acted on even when there were still
18506 bytes sitting in the inbuf.
18507 - When poll() is interrupted, we shouldn't believe the revents values.
18509 o Bugfixes on 0.0.9pre6:
18510 - Fix hibernate bug that caused pre6 to be broken.
18511 - Don't keep rephist info for routers that haven't had activity for
18512 24 hours. (This matters now that clients have keys, since we track
18514 - Never call close_temp_logs while validating log options.
18515 - Fix backslash-escaping on tor.sh.in and torctl.in.
18518 - Implement weekly/monthly/daily accounting: now you specify your
18519 hibernation properties by
18520 AccountingMax N bytes|KB|MB|GB|TB
18521 AccountingStart day|week|month [day] HH:MM
18522 Defaults to "month 1 0:00".
18523 - Let bandwidth and interval config options be specified as 5 bytes,
18524 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
18525 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
18526 get back to normal.)
18527 - If your requested entry or exit node has advertised bandwidth 0,
18529 - Be more greedy about filling up relay cells -- we try reading again
18530 once we've processed the stuff we read, in case enough has arrived
18531 to fill the last cell completely.
18532 - Apply NT service patch from Osamu Fujino. Still needs more work.
18535 Changes in version 0.0.9pre6 - 2004-11-15
18536 o Bugfixes on 0.0.8.1:
18537 - Fix assert failure on malformed socks4a requests.
18538 - Use identity comparison, not nickname comparison, to choose which
18539 half of circuit-ID-space each side gets to use. This is needed
18540 because sometimes we think of a router as a nickname, and sometimes
18541 as a hex ID, and we can't predict what the other side will do.
18542 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
18543 write() call will fail and we handle it there.
18544 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
18545 and smartlist_len, which are two major profiling offenders.
18547 o Bugfixes on 0.0.9pre5:
18548 - Fix a bug in read_all that was corrupting config files on windows.
18549 - When we're raising the max number of open file descriptors to
18550 'unlimited', don't log that we just raised it to '-1'.
18551 - Include event code with events, as required by control-spec.txt.
18552 - Don't give a fingerprint when clients do --list-fingerprint:
18553 it's misleading, because it will never be the same again.
18554 - Stop using strlcpy in tor_strndup, since it was slowing us
18556 - Remove warn on startup about missing cached-directory file.
18557 - Make kill -USR1 work again.
18558 - Hibernate if we start tor during the "wait for wakeup-time" phase
18559 of an accounting interval. Log our hibernation plans better.
18560 - Authoritative dirservers now also cache their directory, so they
18561 have it on start-up.
18564 - Fetch running-routers; cache running-routers; compress
18565 running-routers; serve compressed running-routers.z
18566 - Add NSI installer script contributed by J Doe.
18567 - Commit VC6 and VC7 workspace/project files.
18568 - Commit a tor.spec for making RPM files, with help from jbash.
18569 - Add contrib/torctl.in contributed by Glenn Fink.
18570 - Implement the control-spec's SAVECONF command, to write your
18571 configuration to torrc.
18572 - Get cookie authentication for the controller closer to working.
18573 - Include control-spec.txt in the tarball.
18574 - When set_conf changes our server descriptor, upload a new copy.
18575 But don't upload it too often if there are frequent changes.
18576 - Document authentication config in man page, and document signals
18578 - Clean up confusing parts of man page and torrc.sample.
18579 - Make expand_filename handle ~ and ~username.
18580 - Use autoconf to enable largefile support where necessary. Use
18581 ftello where available, since ftell can fail at 2GB.
18582 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
18583 log more informatively.
18584 - Give a slightly more useful output for "tor -h".
18585 - Refuse application socks connections to port 0.
18586 - Check clock skew for verified servers, but allow unverified
18587 servers and clients to have any clock skew.
18588 - Break DirFetchPostPeriod into:
18589 - DirFetchPeriod for fetching full directory,
18590 - StatusFetchPeriod for fetching running-routers,
18591 - DirPostPeriod for posting server descriptor,
18592 - RendPostPeriod for posting hidden service descriptors.
18593 - Make sure the hidden service descriptors are at a random offset
18594 from each other, to hinder linkability.
18597 Changes in version 0.0.9pre5 - 2004-11-09
18598 o Bugfixes on 0.0.9pre4:
18599 - Fix a seg fault in unit tests (doesn't affect main program).
18600 - Fix an assert bug where a hidden service provider would fail if
18601 the first hop of his rendezvous circuit was down.
18602 - Hidden service operators now correctly handle version 1 style
18603 INTRODUCE1 cells (nobody generates them still, so not a critical
18605 - If do_hup fails, actually notice.
18606 - Handle more errnos from accept() without closing the listener.
18607 Some OpenBSD machines were closing their listeners because
18608 they ran out of file descriptors.
18609 - Send resolve cells to exit routers that are running a new
18610 enough version of the resolve code to work right.
18611 - Better handling of winsock includes on non-MSV win32 compilers.
18612 - Some people had wrapped their tor client/server in a script
18613 that would restart it whenever it died. This did not play well
18614 with our "shut down if your version is obsolete" code. Now people
18615 don't fetch a new directory if their local cached version is
18617 - Make our autogen.sh work on ksh as well as bash.
18620 - Hibernation: New config option "AccountingMaxKB" lets you
18621 set how many KBytes per month you want to allow your server to
18622 consume. Rather than spreading those bytes out evenly over the
18623 month, we instead hibernate for some of the month and pop up
18624 at a deterministic time, work until the bytes are consumed, then
18625 hibernate again. Config option "MonthlyAccountingStart" lets you
18626 specify which day of the month your billing cycle starts on.
18627 - Control interface: a separate program can now talk to your
18628 client/server over a socket, and get/set config options, receive
18629 notifications of circuits and streams starting/finishing/dying,
18630 bandwidth used, etc. The next step is to get some GUIs working.
18631 Let us know if you want to help out. See doc/control-spec.txt .
18632 - Ship a contrib/tor-control.py as an example script to interact
18633 with the control port.
18634 - "tor --hash-password zzyxz" will output a salted password for
18635 use in authenticating to the control interface.
18636 - New log format in config:
18637 "Log minsev[-maxsev] stdout|stderr|syslog" or
18638 "Log minsev[-maxsev] file /var/foo"
18641 - DirPolicy config option, to let people reject incoming addresses
18642 from their dirserver.
18643 - "tor --list-fingerprint" will list your identity key fingerprint
18645 - Add "pass" target for RedirectExit, to make it easier to break
18646 out of a sequence of RedirectExit rules.
18647 - Clients now generate a TLS cert too, in preparation for having
18648 them act more like real nodes.
18649 - Ship src/win32/ in the tarball, so people can use it to build.
18650 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
18652 - New "router-status" line in directory, to better bind each verified
18653 nickname to its identity key.
18654 - Deprecate unofficial config option abbreviations, and abbreviations
18655 not on the command line.
18656 - Add a pure-C tor-resolve implementation.
18657 - Use getrlimit and friends to ensure we can reach MaxConn (currently
18658 1024) file descriptors.
18660 o Code security improvements, inspired by Ilja:
18661 - Replace sprintf with snprintf. (I think they were all safe, but
18663 - Replace strcpy/strncpy with strlcpy in more places.
18664 - Avoid strcat; use snprintf or strlcat instead.
18665 - snprintf wrapper with consistent (though not C99) overflow behavior.
18668 Changes in version 0.0.9pre4 - 2004-10-17
18669 o Bugfixes on 0.0.9pre3:
18670 - If the server doesn't specify an exit policy, use the real default
18671 exit policy, not reject *:*.
18672 - Ignore fascistfirewall when uploading/downloading hidden service
18673 descriptors, since we go through Tor for those; and when using
18674 an HttpProxy, since we assume it can reach them all.
18675 - When looking for an authoritative dirserver, use only the ones
18676 configured at boot. Don't bother looking in the directory.
18677 - The rest of the fix for get_default_conf_file() on older win32.
18678 - Make 'Routerfile' config option obsolete.
18681 - New 'MyFamily nick1,...' config option for a server to
18682 specify other servers that shouldn't be used in the same circuit
18683 with it. Only believed if nick1 also specifies us.
18684 - New 'NodeFamily nick1,nick2,...' config option for a client to
18685 specify nodes that it doesn't want to use in the same circuit.
18686 - New 'Redirectexit pattern address:port' config option for a
18687 server to redirect exit connections, e.g. to a local squid.
18690 Changes in version 0.0.9pre3 - 2004-10-13
18691 o Bugfixes on 0.0.8.1:
18692 - Better torrc example lines for dirbindaddress and orbindaddress.
18693 - Improved bounds checking on parsed ints (e.g. config options and
18694 the ones we find in directories.)
18695 - Better handling of size_t vs int, so we're more robust on 64
18697 - Fix the rest of the bug where a newly started OR would appear
18698 as unverified even after we've added his fingerprint and hupped
18700 - Fix a bug from 0.0.7: when read() failed on a stream, we would
18701 close it without sending back an end. So 'connection refused'
18702 would simply be ignored and the user would get no response.
18704 o Bugfixes on 0.0.9pre2:
18705 - Serving the cached-on-disk directory to people is bad. We now
18706 provide no directory until we've fetched a fresh one.
18707 - Workaround for bug on windows where cached-directories get crlf
18709 - Make get_default_conf_file() work on older windows too.
18710 - If we write a *:* exit policy line in the descriptor, don't write
18711 any more exit policy lines.
18714 - Use only 0.0.9pre1 and later servers for resolve cells.
18715 - Make the dirservers file obsolete.
18716 - Include a dir-signing-key token in directories to tell the
18717 parsing entity which key is being used to sign.
18718 - Remove the built-in bulky default dirservers string.
18719 - New config option "Dirserver %s:%d [fingerprint]", which can be
18720 repeated as many times as needed. If no dirservers specified,
18721 default to moria1,moria2,tor26.
18722 - Make moria2 advertise a dirport of 80, so people behind firewalls
18723 will be able to get a directory.
18724 - Http proxy support
18725 - Dirservers translate requests for http://%s:%d/x to /x
18726 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
18727 be routed through this host.
18728 - Clients ask for /tor/x rather than /x for new enough dirservers.
18729 This way we can one day coexist peacefully with apache.
18730 - Clients specify a "Host: %s%d" http header, to be compatible
18731 with more proxies, and so running squid on an exit node can work.
18734 Changes in version 0.0.8.1 - 2004-10-13
18736 - Fix a seg fault that can be triggered remotely for Tor
18737 clients/servers with an open dirport.
18738 - Fix a rare assert trigger, where routerinfos for entries in
18739 our cpath would expire while we're building the path.
18740 - Fix a bug in OutboundBindAddress so it (hopefully) works.
18741 - Fix a rare seg fault for people running hidden services on
18742 intermittent connections.
18743 - Fix a bug in parsing opt keywords with objects.
18744 - Fix a stale pointer assert bug when a stream detaches and
18746 - Fix a string format vulnerability (probably not exploitable)
18747 in reporting stats locally.
18748 - Fix an assert trigger: sometimes launching circuits can fail
18749 immediately, e.g. because too many circuits have failed recently.
18750 - Fix a compile warning on 64 bit platforms.
18753 Changes in version 0.0.9pre2 - 2004-10-03
18755 - Make fetching a cached directory work for 64-bit platforms too.
18756 - Make zlib.h a required header, not an optional header.
18759 Changes in version 0.0.9pre1 - 2004-10-01
18761 - Stop using separate defaults for no-config-file and
18762 empty-config-file. Now you have to explicitly turn off SocksPort,
18763 if you don't want it open.
18764 - Fix a bug in OutboundBindAddress so it (hopefully) works.
18765 - Improve man page to mention more of the 0.0.8 features.
18766 - Fix a rare seg fault for people running hidden services on
18767 intermittent connections.
18768 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
18770 - Fix more dns related bugs: send back resolve_failed and end cells
18771 more reliably when the resolve fails, rather than closing the
18772 circuit and then trying to send the cell. Also attach dummy resolve
18773 connections to a circuit *before* calling dns_resolve(), to fix
18774 a bug where cached answers would never be sent in RESOLVED cells.
18775 - When we run out of disk space, or other log writing error, don't
18776 crash. Just stop logging to that log and continue.
18777 - We were starting to daemonize before we opened our logs, so if
18778 there were any problems opening logs, we would complain to stderr,
18779 which wouldn't work, and then mysteriously exit.
18780 - Fix a rare bug where sometimes a verified OR would connect to us
18781 before he'd uploaded his descriptor, which would cause us to
18782 assign conn->nickname as though he's unverified. Now we look through
18783 the fingerprint list to see if he's there.
18784 - Fix a rare assert trigger, where routerinfos for entries in
18785 our cpath would expire while we're building the path.
18788 - Clients can ask dirservers for /dir.z to get a compressed version
18789 of the directory. Only works for servers running 0.0.9, of course.
18790 - Make clients cache directories and use them to seed their router
18791 lists at startup. This means clients have a datadir again.
18792 - Configuration infrastructure support for warning on obsolete
18794 - Respond to content-encoding headers by trying to uncompress as
18796 - Reply with a deflated directory when a client asks for "dir.z".
18797 We could use allow-encodings instead, but allow-encodings isn't
18798 specified in HTTP 1.0.
18799 - Raise the max dns workers from 50 to 100.
18800 - Discourage people from setting their dirfetchpostperiod more often
18801 than once per minute.
18802 - Protect dirservers from overzealous descriptor uploading -- wait
18803 10 seconds after directory gets dirty, before regenerating.
18806 Changes in version 0.0.8 - 2004-08-25
18807 o Port it to SunOS 5.9 / Athena
18810 Changes in version 0.0.8rc2 - 2004-08-20
18811 o Make it compile on cygwin again.
18812 o When picking unverified routers, skip those with low uptime and/or
18813 low bandwidth, depending on what properties you care about.
18816 Changes in version 0.0.8rc1 - 2004-08-18
18817 o Changes from 0.0.7.3:
18819 - Fix assert triggers: if the other side returns an address 0.0.0.0,
18820 don't put it into the client dns cache.
18821 - If a begin failed due to exit policy, but we believe the IP address
18822 should have been allowed, switch that router to exitpolicy reject *:*
18823 until we get our next directory.
18825 - Clients choose nodes proportional to advertised bandwidth.
18826 - Avoid using nodes with low uptime as introduction points.
18827 - Handle servers with dynamic IP addresses: don't replace
18828 options->Address with the resolved one at startup, and
18829 detect our address right before we make a routerinfo each time.
18830 - 'FascistFirewall' option to pick dirservers and ORs on specific
18831 ports; plus 'FirewallPorts' config option to tell FascistFirewall
18832 which ports are open. (Defaults to 80,443)
18833 - Be more aggressive about trying to make circuits when the network
18834 has changed (e.g. when you unsuspend your laptop).
18835 - Check for time skew on http headers; report date in response to
18837 - If the entrynode config line has only one node, don't pick it as
18839 - Add strict{entry|exit}nodes config options. If set to 1, then
18840 we refuse to build circuits that don't include the specified entry
18842 - OutboundBindAddress config option, to bind to a specific
18843 IP address for outgoing connect()s.
18844 - End truncated log entries (e.g. directories) with "[truncated]".
18846 o Patches to 0.0.8preX:
18848 - Patches to compile and run on win32 again (maybe)?
18849 - Fix crash when looking for ~/.torrc with no $HOME set.
18850 - Fix a race bug in the unit tests.
18851 - Handle verified/unverified name collisions better when new
18852 routerinfo's arrive in a directory.
18853 - Sometimes routers were getting entered into the stats before
18854 we'd assigned their identity_digest. Oops.
18855 - Only pick and establish intro points after we've gotten a
18858 - AllowUnverifiedNodes config option to let circuits choose no-name
18859 routers in entry,middle,exit,introduction,rendezvous positions.
18860 Allow middle and rendezvous positions by default.
18861 - Add a man page for tor-resolve.
18864 Changes in version 0.0.7.3 - 2004-08-12
18865 o Stop dnsworkers from triggering an assert failure when you
18866 ask them to resolve the host "".
18869 Changes in version 0.0.8pre3 - 2004-08-09
18870 o Changes from 0.0.7.2:
18871 - Allow multiple ORs with same nickname in routerlist -- now when
18872 people give us one identity key for a nickname, then later
18873 another, we don't constantly complain until the first expires.
18874 - Remember used bandwidth (both in and out), and publish 15-minute
18875 snapshots for the past day into our descriptor.
18876 - You can now fetch $DIRURL/running-routers to get just the
18877 running-routers line, not the whole descriptor list. (But
18878 clients don't use this yet.)
18879 - When people mistakenly use Tor as an http proxy, point them
18880 at the tor-doc.html rather than the INSTALL.
18881 - Remove our mostly unused -- and broken -- hex_encode()
18882 function. Use base16_encode() instead. (Thanks to Timo Lindfors
18883 for pointing out this bug.)
18884 - Rotate onion keys every 12 hours, not every 2 hours, so we have
18885 fewer problems with people using the wrong key.
18886 - Change the default exit policy to reject the default edonkey,
18887 kazaa, gnutella ports.
18888 - Add replace_file() to util.[ch] to handle win32's rename().
18890 o Changes from 0.0.8preX:
18891 - Fix two bugs in saving onion keys to disk when rotating, so
18892 hopefully we'll get fewer people using old onion keys.
18893 - Fix an assert error that was making SocksPolicy not work.
18894 - Be willing to expire routers that have an open dirport -- it's
18895 just the authoritative dirservers we want to not forget.
18896 - Reject tor-resolve requests for .onion addresses early, so we
18897 don't build a whole rendezvous circuit and then fail.
18898 - When you're warning a server that he's unverified, don't cry
18899 wolf unpredictably.
18900 - Fix a race condition: don't try to extend onto a connection
18901 that's still handshaking.
18902 - For servers in clique mode, require the conn to be open before
18903 you'll choose it for your path.
18904 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
18905 end relay cell, etc.
18906 - Measure bandwidth capacity over the last 24 hours, not just 12
18907 - Bugfix: authoritative dirservers were making and signing a new
18908 directory for each client, rather than reusing the cached one.
18911 Changes in version 0.0.8pre2 - 2004-08-04
18912 o Changes from 0.0.7.2:
18914 - Check directory signature _before_ you decide whether you're
18915 you're running an obsolete version and should exit.
18916 - Check directory signature _before_ you parse the running-routers
18917 list to decide who's running or verified.
18918 - Bugfixes and features:
18919 - Check return value of fclose while writing to disk, so we don't
18920 end up with broken files when servers run out of disk space.
18921 - Log a warning if the user uses an unsafe socks variant, so people
18922 are more likely to learn about privoxy or socat.
18923 - Dirservers now include RFC1123-style dates in the HTTP headers,
18924 which one day we will use to better detect clock skew.
18926 o Changes from 0.0.8pre1:
18927 - Make it compile without warnings again on win32.
18928 - Log a warning if you're running an unverified server, to let you
18929 know you might want to get it verified.
18930 - Only pick a default nickname if you plan to be a server.
18933 Changes in version 0.0.8pre1 - 2004-07-23
18935 - Made our unit tests compile again on OpenBSD 3.5, and tor
18936 itself compile again on OpenBSD on a sparc64.
18937 - We were neglecting milliseconds when logging on win32, so
18938 everything appeared to happen at the beginning of each second.
18940 o Protocol changes:
18941 - 'Extend' relay cell payloads now include the digest of the
18942 intended next hop's identity key. Now we can verify that we're
18943 extending to the right router, and also extend to routers we
18944 hadn't heard of before.
18947 - Tor nodes can now act as relays (with an advertised ORPort)
18948 without being manually verified by the dirserver operators.
18949 - Uploaded descriptors of unverified routers are now accepted
18950 by the dirservers, and included in the directory.
18951 - Verified routers are listed by nickname in the running-routers
18952 list; unverified routers are listed as "$<fingerprint>".
18953 - We now use hash-of-identity-key in most places rather than
18954 nickname or addr:port, for improved security/flexibility.
18955 - To avoid Sybil attacks, paths still use only verified servers.
18956 But now we have a chance to play around with hybrid approaches.
18957 - Nodes track bandwidth usage to estimate capacity (not used yet).
18958 - ClientOnly option for nodes that never want to become servers.
18959 - Directory caching.
18960 - "AuthoritativeDir 1" option for the official dirservers.
18961 - Now other nodes (clients and servers) will cache the latest
18962 directory they've pulled down.
18963 - They can enable their DirPort to serve it to others.
18964 - Clients will pull down a directory from any node with an open
18965 DirPort, and check the signature/timestamp correctly.
18966 - Authoritative dirservers now fetch directories from other
18967 authdirservers, to stay better synced.
18968 - Running-routers list tells who's down also, along with noting
18969 if they're verified (listed by nickname) or unverified (listed
18971 - Allow dirservers to serve running-router list separately.
18972 This isn't used yet.
18973 - ORs connect-on-demand to other ORs
18974 - If you get an extend cell to an OR you're not connected to,
18975 connect, handshake, and forward the create cell.
18976 - The authoritative dirservers stay connected to everybody,
18977 and everybody stays connected to 0.0.7 servers, but otherwise
18978 clients/servers expire unused connections after 5 minutes.
18979 - When servers get a sigint, they delay 30 seconds (refusing new
18980 connections) then exit. A second sigint causes immediate exit.
18981 - File and name management:
18982 - Look for .torrc if no CONFDIR "torrc" is found.
18983 - If no datadir is defined, then choose, make, and secure ~/.tor
18985 - If torrc not found, exitpolicy reject *:*.
18986 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
18987 - If no nickname is defined, derive default from hostname.
18988 - Rename secret key files, e.g. identity.key -> secret_id_key,
18989 to discourage people from mailing their identity key to tor-ops.
18990 - Refuse to build a circuit before the directory has arrived --
18991 it won't work anyway, since you won't know the right onion keys
18993 - Try other dirservers immediately if the one you try is down. This
18994 should tolerate down dirservers better now.
18995 - Parse tor version numbers so we can do an is-newer-than check
18996 rather than an is-in-the-list check.
18997 - New socks command 'resolve', to let us shim gethostbyname()
18999 - A 'tor_resolve' script to access the socks resolve functionality.
19000 - A new socks-extensions.txt doc file to describe our
19001 interpretation and extensions to the socks protocols.
19002 - Add a ContactInfo option, which gets published in descriptor.
19003 - Publish OR uptime in descriptor (and thus in directory) too.
19004 - Write tor version at the top of each log file
19005 - New docs in the tarball:
19007 - Document that you should proxy your SSL traffic too.
19010 Changes in version 0.0.7.2 - 2004-07-07
19011 o A better fix for the 0.0.0.0 problem, that will hopefully
19012 eliminate the remaining related assertion failures.
19015 Changes in version 0.0.7.1 - 2004-07-04
19016 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
19017 since internally we use 0.0.0.0 to signify "not yet resolved".
19020 Changes in version 0.0.7 - 2004-06-07
19021 o Updated the man page to reflect the new features.
19024 Changes in version 0.0.7rc2 - 2004-06-06
19025 o Changes from 0.0.7rc1:
19026 - Make it build on Win32 again.
19027 o Changes from 0.0.6.2:
19028 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
19032 Changes in version 0.0.7rc1 - 2004-06-02
19034 - On sighup, we were adding another log without removing the first
19035 one. So log messages would get duplicated n times for n sighups.
19036 - Several cases of using a connection after we'd freed it. The
19037 problem was that connections that are pending resolve are in both
19038 the pending_resolve tree, and also the circuit's resolving_streams
19039 list. When you want to remove one, you must remove it from both.
19040 - Fix a double-mark-for-close where an end cell arrived for a
19041 resolving stream, and then the resolve failed.
19042 - Check directory signatures based on name of signer, not on whom
19043 we got the directory from. This will let us cache directories more
19046 - Crank up some of our constants to handle more users.
19049 Changes in version 0.0.7pre1 - 2004-06-02
19050 o Fixes for crashes and other obnoxious bugs:
19051 - Fix an epipe bug: sometimes when directory connections failed
19052 to connect, we would give them a chance to flush before closing
19054 - When we detached from a circuit because of resolvefailed, we
19055 would immediately try the same circuit twice more, and then
19056 give up on the resolve thinking we'd tried three different
19058 - Limit the number of intro circuits we'll attempt to build for a
19059 hidden service per 15-minute period.
19060 - Check recommended-software string *early*, before actually parsing
19061 the directory. Thus we can detect an obsolete version and exit,
19062 even if the new directory format doesn't parse.
19063 o Fixes for security bugs:
19064 - Remember which nodes are dirservers when you startup, and if a
19065 random OR enables his dirport, don't automatically assume he's
19066 a trusted dirserver.
19068 - Directory connections were asking the wrong poll socket to
19069 start writing, and not asking themselves to start writing.
19070 - When we detached from a circuit because we sent a begin but
19071 didn't get a connected, we would use it again the first time;
19072 but after that we would correctly switch to a different one.
19073 - Stop warning when the first onion decrypt attempt fails; they
19074 will sometimes legitimately fail now that we rotate keys.
19075 - Override unaligned-access-ok check when $host_cpu is ia64 or
19076 arm. Apparently they allow it but the kernel whines.
19077 - Dirservers try to reconnect periodically too, in case connections
19079 - Fix some memory leaks in directory servers.
19080 - Allow backslash in Win32 filenames.
19081 - Made Tor build complain-free on FreeBSD, hopefully without
19082 breaking other BSD builds. We'll see.
19084 - Doxygen markup on all functions and global variables.
19085 - Make directory functions update routerlist, not replace it. So
19086 now directory disagreements are not so critical a problem.
19087 - Remove the upper limit on number of descriptors in a dirserver's
19088 directory (not that we were anywhere close).
19089 - Allow multiple logfiles at different severity ranges.
19090 - Allow *BindAddress to specify ":port" rather than setting *Port
19091 separately. Allow multiple instances of each BindAddress config
19092 option, so you can bind to multiple interfaces if you want.
19093 - Allow multiple exit policy lines, which are processed in order.
19094 Now we don't need that huge line with all the commas in it.
19095 - Enable accept/reject policies on SOCKS connections, so you can bind
19096 to 0.0.0.0 but still control who can use your OP.
19099 Changes in version 0.0.6.2 - 2004-05-16
19100 o Our integrity-checking digest was checking only the most recent cell,
19101 not the previous cells like we'd thought.
19102 Thanks to Stefan Mark for finding the flaw!
19105 Changes in version 0.0.6.1 - 2004-05-06
19106 o Fix two bugs in our AES counter-mode implementation (this affected
19107 onion-level stream encryption, but not TLS-level). It turns
19108 out we were doing something much more akin to a 16-character
19109 polyalphabetic cipher. Oops.
19110 Thanks to Stefan Mark for finding the flaw!
19111 o Retire moria3 as a directory server, and add tor26 as a directory
19115 Changes in version 0.0.6 - 2004-05-02
19116 [version bump only]
19119 Changes in version 0.0.6rc4 - 2004-05-01
19120 o Update the built-in dirservers list to use the new directory format
19121 o Fix a rare seg fault: if a node offering a hidden service attempts
19122 to build a circuit to Alice's rendezvous point and fails before it
19123 reaches the last hop, it retries with a different circuit, but
19125 o Handle windows socket errors correctly.
19128 Changes in version 0.0.6rc3 - 2004-04-28
19129 o Don't expire non-general excess circuits (if we had enough
19130 circuits open, we were expiring rendezvous circuits -- even
19131 when they had a stream attached. oops.)
19132 o Fetch randomness from /dev/urandom better (not via fopen/fread)
19133 o Better debugging for tls errors
19134 o Some versions of openssl have an SSL_pending function that erroneously
19135 returns bytes when there is a non-application record pending.
19136 o Set Content-Type on the directory and hidserv descriptor.
19137 o Remove IVs from cipher code, since AES-ctr has none.
19138 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
19139 o We were using an array of length zero in a few places.
19140 o win32's gethostbyname can't resolve an IP to an IP.
19141 o win32's close can't close a socket.
19144 Changes in version 0.0.6rc2 - 2004-04-26
19145 o Fix a bug where we were closing tls connections intermittently.
19146 It turns out openssl keeps its errors around -- so if an error
19147 happens, and you don't ask about it, and then another openssl
19148 operation happens and succeeds, and you ask if there was an error,
19149 it tells you about the first error. Fun fun.
19150 o Fix a bug that's been lurking since 27 may 03 (!)
19151 When passing back a destroy cell, we would use the wrong circ id.
19152 'Mostly harmless', but still worth fixing.
19153 o Since we don't support truncateds much, don't bother sending them;
19154 just close the circ.
19155 o check for <machine/limits.h> so we build on NetBSD again (I hope).
19156 o don't crash if a conn that sent a begin has suddenly lost its circuit
19157 (this was quite rare).
19160 Changes in version 0.0.6rc1 - 2004-04-25
19161 o We now rotate link (tls context) keys and onion keys.
19162 o CREATE cells now include oaep padding, so you can tell
19163 if you decrypted them correctly.
19164 o Add bandwidthburst to server descriptor.
19165 o Directories now say which dirserver signed them.
19166 o Use a tor_assert macro that logs failed assertions too.
19169 Changes in version 0.0.6pre5 - 2004-04-18
19170 o changes from 0.0.6pre4:
19171 - make tor build on broken freebsd 5.2 installs
19172 - fix a failed assert when you try an intro point, get a nack, and try
19173 a second one and it works.
19174 - when alice uses a port that the hidden service doesn't accept,
19175 it now sends back an end cell (denied by exit policy). otherwise
19176 alice would just have to wait to time out.
19177 - fix another rare bug: when we had tried all the intro
19178 points for a hidden service, we fetched the descriptor
19179 again, but we left our introcirc thinking it had already
19180 sent an intro, so it kept waiting for a response...
19181 - bugfix: when you sleep your hidden-service laptop, as soon
19182 as it wakes up it tries to upload a service descriptor, but
19183 socketpair fails for some reason (localhost not up yet?).
19184 now we simply give up on that upload, and we'll try again later.
19185 i'd still like to find the bug though.
19186 - if an intro circ waiting for an ack dies before getting one, then
19188 - we were reusing stale service descriptors and refetching usable
19192 Changes in version 0.0.6pre4 - 2004-04-14
19193 o changes from 0.0.6pre3:
19194 - when bob fails to connect to the rendezvous point, and his
19195 circ didn't fail because of the rendezvous point itself, then
19196 he retries a couple of times
19197 - we expire introduction and rendezvous circs more thoroughly
19198 (sometimes they were hanging around forever)
19199 - we expire unattached rendezvous streams that have been around
19200 too long (they were sticking around forever).
19201 - fix a measly fencepost error that was crashing everybody with
19205 Changes in version 0.0.6pre3 - 2004-04-14
19206 o changes from 0.0.6pre2:
19207 - make hup work again
19208 - fix some memory leaks for dirservers
19209 - allow more skew in rendezvous descriptor timestamps, to help
19210 handle people like blanu who don't know what time it is
19211 - normal circs are 3 hops, but some rend/intro circs are 4, if
19212 the initiator doesn't get to choose the last hop
19213 - send acks for introductions, so alice can know whether to try
19215 - bob publishes intro points more correctly
19216 o changes from 0.0.5:
19217 - fix an assert trigger that's been plaguing us since the days
19218 of 0.0.2prexx (thanks weasel!)
19219 - retry stream correctly when we fail to connect because of
19220 exit-policy-reject (should try another) or can't-resolve-address
19221 (also should try another, because dns on random internet servers
19223 - when we hup a dirserver and we've *removed* a server from the
19224 approved-routers list, now we remove that server from the
19225 in-memory directories too
19228 Changes in version 0.0.6pre2 - 2004-04-08
19229 o We fixed our base32 implementation. Now it works on all architectures.
19232 Changes in version 0.0.6pre1 - 2004-04-08
19234 - Hidden services and rendezvous points are implemented. Go to
19235 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
19236 hidden services. (This only works via a socks4a proxy such as
19237 Privoxy, and currently it's quite slow.)
19240 Changes in version 0.0.5 - 2004-03-30
19241 [version bump only]
19244 Changes in version 0.0.5rc3 - 2004-03-29
19245 o Install torrc as torrc.sample -- we no longer clobber your
19247 o Re-enable recommendedversion checking (we broke it in rc2, oops)
19248 o Add in a 'notice' log level for things the operator should hear
19249 but that aren't warnings
19252 Changes in version 0.0.5rc2 - 2004-03-29
19253 o Hold socks connection open until reply is flushed (if possible)
19254 o Make exit nodes resolve IPs to IPs immediately, rather than asking
19255 the dns farm to do it.
19256 o Fix c99 aliasing warnings in rephist.c
19257 o Don't include server descriptors that are older than 24 hours in the
19259 o Give socks 'reject' replies their whole 15s to attempt to flush,
19260 rather than seeing the 60s timeout and assuming the flush had failed.
19261 o Clean automake droppings from the cvs repository
19264 Changes in version 0.0.5rc1 - 2004-03-28
19265 o Fix mangled-state bug in directory fetching (was causing sigpipes).
19266 o Only build circuits after we've fetched the directory: clients were
19267 using only the directory servers before they'd fetched a directory.
19268 This also means longer startup time; so it goes.
19269 o Fix an assert trigger where an OP would fail to handshake, and we'd
19270 expect it to have a nickname.
19271 o Work around a tsocks bug: do a socks reject when AP connection dies
19272 early, else tsocks goes into an infinite loop.
19275 Changes in version 0.0.4 - 2004-03-26
19276 o When connecting to a dirserver or OR and the network is down,
19280 Changes in version 0.0.3 - 2004-03-26
19281 o Warn and fail if server chose a nickname with illegal characters
19282 o Port to Solaris and Sparc:
19283 - include missing header fcntl.h
19284 - have autoconf find -lsocket -lnsl automatically
19285 - deal with hardware word alignment
19286 - make uname() work (solaris has a different return convention)
19287 - switch from using signal() to sigaction()
19288 o Preliminary work on reputation system:
19289 - Keep statistics on success/fail of connect attempts; they're published
19290 by kill -USR1 currently.
19291 - Add a RunTesting option to try to learn link state by creating test
19292 circuits, even when SocksPort is off.
19293 - Remove unused open circuits when there are too many.
19296 Changes in version 0.0.2 - 2004-03-19
19297 - Include strlcpy and strlcat for safer string ops
19298 - define INADDR_NONE so we compile (but still not run) on solaris
19301 Changes in version 0.0.2pre27 - 2004-03-14
19303 - Allow internal tor networks (we were rejecting internal IPs,
19304 now we allow them if they're set explicitly).
19305 - And fix a few endian issues.
19308 Changes in version 0.0.2pre26 - 2004-03-14
19310 - If a stream times out after 15s without a connected cell, don't
19311 try that circuit again: try a new one.
19312 - Retry streams at most 4 times. Then give up.
19313 - When a dirserver gets a descriptor from an unknown router, it
19314 logs its fingerprint (so the dirserver operator can choose to
19315 accept it even without mail from the server operator).
19316 - Inform unapproved servers when we reject their descriptors.
19317 - Make tor build on Windows again. It works as a client, who knows
19319 - Clearer instructions in the torrc for how to set up a server.
19320 - Be more efficient about reading fd's when our global token bucket
19321 (used for rate limiting) becomes empty.
19323 - Stop asserting that computers always go forward in time. It's
19325 - When we sent a cell (e.g. destroy) and then marked an OR connection
19326 expired, we might close it before finishing a flush if the other
19327 side isn't reading right then.
19328 - Don't allow dirservers to start if they haven't defined
19329 RecommendedVersions
19330 - We were caching transient dns failures. Oops.
19331 - Prevent servers from publishing an internal IP as their address.
19332 - Address a strcat vulnerability in circuit.c
19335 Changes in version 0.0.2pre25 - 2004-03-04
19337 - Put the OR's IP in its router descriptor, not its fqdn. That way
19338 we'll stop being stalled by gethostbyname for nodes with flaky dns,
19341 - If the user typed in an address that didn't resolve, the server
19345 Changes in version 0.0.2pre24 - 2004-03-03
19347 - Fix an assertion failure in dns.c, where we were trying to dequeue
19348 a pending dns resolve even if it wasn't pending
19349 - Fix a spurious socks5 warning about still trying to write after the
19350 connection is finished.
19351 - Hold certain marked_for_close connections open until they're finished
19352 flushing, rather than losing bytes by closing them too early.
19353 - Correctly report the reason for ending a stream
19354 - Remove some duplicate calls to connection_mark_for_close
19355 - Put switch_id and start_daemon earlier in the boot sequence, so it
19356 will actually try to chdir() to options.DataDirectory
19357 - Make 'make test' exit(1) if a test fails; fix some unit tests
19358 - Make tor fail when you use a config option it doesn't know about,
19359 rather than warn and continue.
19360 - Make --version work
19361 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
19364 Changes in version 0.0.2pre23 - 2004-02-29
19366 - Print a statement when the first circ is finished, so the user
19367 knows it's working.
19368 - If a relay cell is unrecognized at the end of the circuit,
19369 send back a destroy. (So attacks to mutate cells are more
19371 - New config option 'excludenodes' to avoid certain nodes for circuits.
19372 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
19373 so you can collect coredumps there.
19375 - Fix a bug in tls flushing where sometimes data got wedged and
19376 didn't flush until more data got sent. Hopefully this bug was
19377 a big factor in the random delays we were seeing.
19378 - Make 'connected' cells include the resolved IP, so the client
19379 dns cache actually gets populated.
19380 - Disallow changing from ORPort=0 to ORPort>0 on hup.
19381 - When we time-out on a stream and detach from the circuit, send an
19382 end cell down it first.
19383 - Only warn about an unknown router (in exitnodes, entrynodes,
19384 excludenodes) after we've fetched a directory.
19387 Changes in version 0.0.2pre22 - 2004-02-26
19389 - Servers publish less revealing uname information in descriptors.
19390 - More memory tracking and assertions, to crash more usefully when
19392 - If the default torrc isn't there, just use some default defaults.
19393 Plus provide an internal dirservers file if they don't have one.
19394 - When the user tries to use Tor as an http proxy, give them an http
19395 501 failure explaining that we're a socks proxy.
19396 - Dump a new router.desc on hup, to help confused people who change
19397 their exit policies and then wonder why router.desc doesn't reflect
19399 - Clean up the generic tor.sh init script that we ship with.
19401 - If the exit stream is pending on the resolve, and a destroy arrives,
19402 then the stream wasn't getting removed from the pending list. I
19403 think this was the one causing recent server crashes.
19404 - Use a more robust poll on OSX 10.3, since their poll is flaky.
19405 - When it couldn't resolve any dirservers, it was useless from then on.
19406 Now it reloads the RouterFile (or default dirservers) if it has no
19408 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
19409 many users don't even *have* a /usr/local/sbin/.
19412 Changes in version 0.0.2pre21 - 2004-02-18
19414 - There's a ChangeLog file that actually reflects the changelog.
19415 - There's a 'torify' wrapper script, with an accompanying
19416 tor-tsocks.conf, that simplifies the process of using tsocks for
19417 tor. It even has a man page.
19418 - The tor binary gets installed to sbin rather than bin now.
19419 - Retry streams where the connected cell hasn't arrived in 15 seconds
19420 - Clean up exit policy handling -- get the default out of the torrc,
19421 so we can update it without forcing each server operator to fix
19423 - Allow imaps and pop3s in default exit policy
19425 - Prevent picking middleman nodes as the last node in the circuit
19428 Changes in version 0.0.2pre20 - 2004-01-30
19430 - We now have a deb package, and it's in debian unstable. Go to
19431 it, apt-getters. :)
19432 - I've split the TotalBandwidth option into BandwidthRate (how many
19433 bytes per second you want to allow, long-term) and
19434 BandwidthBurst (how many bytes you will allow at once before the cap
19435 kicks in). This better token bucket approach lets you, say, set
19436 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
19437 performance while not exceeding your monthly bandwidth quota.
19438 - Push out a tls record's worth of data once you've got it, rather
19439 than waiting until you've read everything waiting to be read. This
19440 may improve performance by pipelining better. We'll see.
19441 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
19442 from failed circuits (if they haven't been connected yet) and attach
19444 - Expire old streams that haven't managed to connect. Some day we'll
19445 have them reattach to new circuits instead.
19448 - Fix several memory leaks that were causing servers to become bloated
19450 - Fix a few very rare assert triggers. A few more remain.
19451 - Setuid to User _before_ complaining about running as root.
19454 Changes in version 0.0.2pre19 - 2004-01-07
19456 - Fix deadlock condition in dns farm. We were telling a child to die by
19457 closing the parent's file descriptor to him. But newer children were
19458 inheriting the open file descriptor from the parent, and since they
19459 weren't closing it, the socket never closed, so the child never read
19460 eof, so he never knew to exit. Similarly, dns workers were holding
19461 open other sockets, leading to all sorts of chaos.
19462 - New cleaner daemon() code for forking and backgrounding.
19463 - If you log to a file, it now prints an entry at the top of the
19464 logfile so you know it's working.
19465 - The onionskin challenge length was 30 bytes longer than necessary.
19466 - Started to patch up the spec so it's not quite so out of date.
19469 Changes in version 0.0.2pre18 - 2004-01-02
19471 - Fix endian issues with the 'integrity' field in the relay header.
19472 - Fix a potential bug where connections in state
19473 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
19476 Changes in version 0.0.2pre17 - 2003-12-30
19478 - Made --debuglogfile (or any second log file, actually) work.
19479 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
19480 adversary could force us into an infinite loop.
19483 - Each onionskin handshake now includes a hash of the computed key,
19484 to prove the server's identity and help perfect forward secrecy.
19485 - Changed cell size from 256 to 512 bytes (working toward compatibility
19487 - Changed cell length to 2 bytes, and moved it to the relay header.
19488 - Implemented end-to-end integrity checking for the payloads of
19490 - Separated streamid from 'recognized' (otherwise circuits will get
19491 messed up when we try to have streams exit from the middle). We
19492 use the integrity-checking to confirm that a cell is addressed to
19494 - Randomize the initial circid and streamid values, so an adversary who
19495 breaks into a node can't learn how many circuits or streams have
19499 Changes in version 0.0.2pre16 - 2003-12-14
19501 - Fixed a bug that made HUP trigger an assert
19502 - Fixed a bug where a circuit that immediately failed wasn't being
19503 counted as a failed circuit in counting retries.
19506 - Now we close the circuit when we get a truncated cell: otherwise we're
19507 open to an anonymity attack where a bad node in the path truncates
19508 the circuit and then we open streams at him.
19509 - Add port ranges to exit policies
19510 - Add a conservative default exit policy
19511 - Warn if you're running tor as root
19512 - on HUP, retry OR connections and close/rebind listeners
19513 - options.EntryNodes: try these nodes first when picking the first node
19514 - options.ExitNodes: if your best choices happen to include any of
19515 your preferred exit nodes, you choose among just those preferred
19517 - options.ExcludedNodes: nodes that are never picked in path building
19520 Changes in version 0.0.2pre15 - 2003-12-03
19521 o Robustness and bugfixes:
19522 - Sometimes clients would cache incorrect DNS resolves, which would
19523 really screw things up.
19524 - An OP that goes offline would slowly leak all its sockets and stop
19526 - A wide variety of bugfixes in exit node selection, exit policy
19527 handling, and processing pending streams when a new circuit is
19529 - Pick nodes for a path only from those the directory says are up
19530 - Choose randomly from all running dirservers, not always the first one
19531 - Increase allowed http header size for directory fetch.
19532 - Stop writing to stderr (if we're daemonized it will be closed).
19533 - Enable -g always, so cores will be more useful to me.
19534 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
19537 - Wrote a man page. It lists commonly used options.
19540 - Change default loglevel to warn.
19541 - Make PidFile default to null rather than littering in your CWD.
19542 - OnionRouter config option is now obsolete. Instead it just checks
19544 - Moved to a single unified torrc file for both clients and servers.
19547 Changes in version 0.0.2pre14 - 2003-11-29
19548 o Robustness and bugfixes:
19549 - Force the admin to make the DataDirectory himself
19550 - to get ownership/permissions right
19551 - so clients no longer make a DataDirectory and then never use it
19552 - fix bug where a client who was offline for 45 minutes would never
19553 pull down a directory again
19554 - fix (or at least hide really well) the dns assert bug that was
19555 causing server crashes
19556 - warnings and improved robustness wrt clockskew for certs
19557 - use the native daemon(3) to daemonize, when available
19558 - exit if bind() fails
19559 - exit if neither socksport nor orport is defined
19560 - include our own tor_timegm (Win32 doesn't have its own)
19561 - bugfix for win32 with lots of connections
19562 - fix minor bias in PRNG
19563 - make dirserver more robust to corrupt cached directory
19566 - Wrote the design document (woo)
19568 o Circuit building and exit policies:
19569 - Circuits no longer try to use nodes that the directory has told them
19571 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
19572 bitcounts (18.0.0.0/8).
19573 - Make AP connections standby for a circuit if no suitable circuit
19574 exists, rather than failing
19575 - Circuits choose exit node based on addr/port, exit policies, and
19576 which AP connections are standing by
19577 - Bump min pathlen from 2 to 3
19578 - Relay end cells have a payload to describe why the stream ended.
19579 - If the stream failed because of exit policy, try again with a new
19581 - Clients have a dns cache to remember resolved addresses.
19582 - Notice more quickly when we have no working circuits
19585 - APPort is now called SocksPort
19586 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
19588 - RecommendedVersions is now a config variable rather than
19589 hardcoded (for dirservers)
19590 - Reloads config on HUP
19591 - Usage info on -h or --help
19592 - If you set User and Group config vars, it'll setu/gid to them.
19595 Changes in version 0.0.2pre13 - 2003-10-19
19596 o General stability:
19597 - SSL_write no longer fails when it returns WANTWRITE and the number
19598 of bytes in the buf has changed by the next SSL_write call.
19599 - Fix segfault fetching directory when network is down
19600 - Fix a variety of minor memory leaks
19601 - Dirservers reload the fingerprints file on HUP, so I don't have
19602 to take down the network when I approve a new router
19603 - Default server config file has explicit Address line to specify fqdn
19606 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
19607 - Make listener connections not ever alloc bufs
19609 o Autoconf improvements:
19610 - don't clobber an external CFLAGS in ./configure
19611 - Make install now works
19612 - create var/lib/tor on make install
19613 - autocreate a tor.sh initscript to help distribs
19614 - autocreate the torrc and sample-server-torrc with correct paths
19616 o Log files and Daemonizing now work:
19617 - If --DebugLogFile is specified, log to it at -l debug
19618 - If --LogFile is specified, use it instead of commandline
19619 - If --RunAsDaemon is set, tor forks and backgrounds on startup