1 Changes in version 0.2.7.6 - 2015-12-10
2 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
3 well as a minor bug in hidden service reliability.
5 o Major bugfixes (guard selection):
6 - Actually look at the Guard flag when selecting a new directory
7 guard. When we implemented the directory guard design, we
8 accidentally started treating all relays as if they have the Guard
9 flag during guard selection, leading to weaker anonymity and worse
10 performance. Fixes bug 17222; bugfix on 0.2.4.8-alpha. Discovered
13 o Minor features (geoip):
14 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
17 o Minor bugfixes (compilation):
18 - When checking for net/pfvar.h, include netinet/in.h if possible.
19 This fixes transparent proxy detection on OpenBSD. Fixes bug
20 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
21 - Fix a compilation warning with Clang 3.6: Do not check the
22 presence of an address which can never be NULL. Fixes bug 17781.
24 o Minor bugfixes (correctness):
25 - When displaying an IPv6 exit policy, include the mask bits
26 correctly even when the number is greater than 31. Fixes bug
27 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
28 - The wrong list was used when looking up expired intro points in a
29 rend service object, causing what we think could be reachability
30 issues for hidden services, and triggering a BUG log. Fixes bug
31 16702; bugfix on 0.2.7.2-alpha.
32 - Fix undefined behavior in the tor_cert_checksig function. Fixes
33 bug 17722; bugfix on 0.2.7.2-alpha.
36 Changes in version 0.2.7.5 - 2015-11-20
37 The Tor 0.2.7 release series is dedicated to the memory of Tor user
38 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
39 tirelessly to advocate human rights regardless of national borders,
40 and oppose the encroachments of mass surveillance. He opposed national
41 exceptionalism, he brought clarity to legal and policy debates, he
42 understood and predicted the impact of mass surveillance on the world,
43 and he laid the groundwork for resisting it. While serving on the Tor
44 Project's board of directors, he brought us his uncompromising focus
45 on technical excellence in the service of humankind. Caspar was an
46 inimitable force for good and a wonderful friend. He was kind,
47 humorous, generous, gallant, and believed we should protect one
48 another without exception. We honor him here for his ideals, his
49 efforts, and his accomplishments. Please honor his memory with works
50 that would make him proud.
52 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
54 The 0.2.7 series adds a more secure identity key type for relays,
55 improves cryptography performance, resolves several longstanding
56 hidden-service performance issues, improves controller support for
57 hidden services, and includes small bugfixes and performance
58 improvements throughout the program. This release series also includes
59 more tests than before, and significant simplifications to which parts
60 of Tor invoke which others.
62 (This release contains no code changes since 0.2.7.4-rc.)
65 Changes in version 0.2.7.4-rc - 2015-10-21
66 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
67 fixes some important memory leaks, and a scary-looking (but mostly
68 harmless in practice) invalid-read bug. It also has a few small
69 bugfixes, notably fixes for compilation and portability on different
70 platforms. If no further significant bounds are found, the next
71 release will the the official stable release.
73 o Major bugfixes (security, correctness):
74 - Fix an error that could cause us to read 4 bytes before the
75 beginning of an openssl string. This bug could be used to cause
76 Tor to crash on systems with unusual malloc implementations, or
77 systems with unusual hardening installed. Fixes bug 17404; bugfix
80 o Major bugfixes (correctness):
81 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
82 bug 17401; bugfix on 0.2.7.3-rc.
84 o Major bugfixes (memory leaks):
85 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
86 17398; bugfix on 0.2.6.1-alpha.
87 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
88 17402; bugfix on 0.2.7.3-rc.
89 - Fix a memory leak when reading an expired signing key from disk.
90 Fixes bug 17403; bugfix on 0.2.7.2-rc.
92 o Minor features (geoIP):
93 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
96 o Minor bugfixes (compilation):
97 - Repair compilation with the most recent (unreleased, alpha)
98 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
99 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
100 17251; bugfix on 0.2.7.2-alpha.
101 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
102 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
104 o Minor bugfixes (portability):
105 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes part
106 of bug 17151; bugfix on 0.2.5.2-alpha. Patch from Marcin Cieślak.
108 o Minor bugfixes (sandbox):
109 - Add the "hidserv-stats" filename to our sandbox filter for the
110 HiddenServiceStatistics option to work properly. Fixes bug 17354;
111 bugfix on tor-0.2.6.2-alpha. Patch from David Goulet.
113 o Minor bugfixes (testing):
114 - Add unit tests for get_interface_address* failure cases. Fixes bug
115 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
116 - Fix breakage when running 'make check' with BSD make. Fixes bug
117 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
118 - Make the get_ifaddrs_* unit tests more tolerant of different
119 network configurations. (Don't assume every test box has an IPv4
120 address, and don't assume every test box has a non-localhost
121 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
122 - Skip backtrace tests when backtrace support is not compiled in.
123 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
127 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
128 - Note that HiddenServicePorts can take a unix domain socket. Closes
132 Changes in version 0.2.7.3-rc - 2015-09-25
133 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
134 contains numerous usability fixes for Ed25519 keys, safeguards against
135 several misconfiguration problems, significant simplifications to
136 Tor's callgraph, and numerous bugfixes and small features.
138 This is the most tested release of Tor to date. The unit tests cover
139 39.40% of the code, and the integration tests (accessible with "make
140 test-full-online", requiring stem and chutney and a network
141 connection) raise the coverage to 64.49%.
143 o Major features (security, hidden services):
144 - Hidden services, if using the EntryNodes option, are required to
145 use more than one EntryNode, in order to avoid a guard discovery
146 attack. (This would only affect people who had configured hidden
147 services and manually specified the EntryNodes option with a
148 single entry-node. The impact was that it would be easy to
149 remotely identify the guard node used by such a hidden service.
150 See ticket for more information.) Fixes ticket 14917.
152 o Major features (Ed25519 keys, keypinning):
153 - The key-pinning option on directory authorities is now advisory-
154 only by default. In a future version, or when the AuthDirPinKeys
155 option is set, pins are enforced again. Disabling key-pinning
156 seemed like a good idea so that we can survive the fallout of any
157 usability problems associated with Ed25519 keys. Closes
160 o Major features (Ed25519 performance):
161 - Improve the speed of Ed25519 operations and Curve25519 keypair
162 generation when built targeting 32 bit x86 platforms with SSE2
163 available. Implements ticket 16535.
164 - Improve the runtime speed of Ed25519 signature verification by
165 using Ed25519-donna's batch verification support. Implements
168 o Major features (performance testing):
169 - The test-network.sh script now supports performance testing.
170 Requires corresponding chutney performance testing changes. Patch
171 by "teor". Closes ticket 14175.
173 o Major features (relay, Ed25519):
174 - Significant usability improvements for Ed25519 key management. Log
175 messages are better, and the code can recover from far more
176 failure conditions. Thanks to "s7r" for reporting and diagnosing
178 - Add a new OfflineMasterKey option to tell Tor never to try loading
179 or generating a secret Ed25519 identity key. You can use this in
180 combination with tor --keygen to manage offline and/or encrypted
181 Ed25519 keys. Implements ticket 16944.
182 - Add a --newpass option to allow changing or removing the
183 passphrase of an encrypted key with tor --keygen. Implements part
185 - On receiving a HUP signal, check to see whether the Ed25519
186 signing key has changed, and reload it if so. Closes ticket 16790.
188 o Major bugfixes (relay, Ed25519):
189 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
190 0.2.7.2-alpha. Reported by "s7r".
191 - Improve handling of expired signing keys with offline master keys.
192 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
194 o Minor features (client-side privacy):
195 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
196 lifespan when IsolateSOCKSAuth and streams with SOCKS
197 authentication are attached to the circuit. This allows
198 applications like TorBrowser to manage circuit lifetime on their
199 own. Implements feature 15482.
200 - When logging malformed hostnames from SOCKS5 requests, respect
201 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
203 o Minor features (compilation):
204 - Give a warning as early as possible when trying to build with an
205 unsupported OpenSSL version. Closes ticket 16901.
206 - Fail during configure if we're trying to build against an OpenSSL
207 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
208 which started requiring ECC.
210 o Minor features (geoip):
211 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
214 o Minor features (hidden services):
215 - Relays need to have the Fast flag to get the HSDir flag. As this
216 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
217 drop. This change should make some attacks against the hidden
218 service directory system harder. Fixes ticket 15963.
219 - Turn on hidden service statistics collection by setting the torrc
220 option HiddenServiceStatistics to "1" by default. (This keeps
221 track only of the fraction of traffic used by hidden services, and
222 the total number of hidden services in existence.) Closes
224 - Client now uses an introduction point failure cache to know when
225 to fetch or keep a descriptor in their cache. Previously, failures
226 were recorded implicitly, but not explicitly remembered. Closes
229 o Minor features (testing, authorities, documentation):
230 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
231 explicitly manage consensus flags in testing networks. Patch by
232 "robgjansen", modified by "teor". Implements part of ticket 14882.
234 o Minor bugfixes (security, exit policies):
235 - ExitPolicyRejectPrivate now also rejects the relay's published
236 IPv6 address (if any), and any publicly routable IPv4 or IPv6
237 addresses on any local interfaces. ticket 17027. Patch by "teor".
238 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
240 o Minor bug fixes (torrc exit policies):
241 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
242 produce IPv6 wildcard addresses. Previously they would produce
243 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
244 of bug 16069; bugfix on 0.2.4.7-alpha.
245 - When parsing torrc ExitPolicies, we now warn for a number of cases
246 where the user's intent is likely to differ from Tor's actual
247 behavior. These include: using an IPv4 address with an accept6 or
248 reject6 line; using "private" on an accept6 or reject6 line; and
249 including any ExitPolicy lines after accept *:* or reject *:*.
250 Related to ticket 16069.
251 - When parsing torrc ExitPolicies, we now issue an info-level
252 message when expanding an "accept/reject *" line to include both
253 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
254 - In each instance above, usage advice is provided to avoid the
255 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
256 16069; bugfix on 0.2.4.7-alpha.
258 o Minor bugfixes (authority):
259 - Don't assign "HSDir" to a router if it isn't Valid and Running.
260 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
261 - Downgrade log messages about Ed25519 key issues if they are in old
262 cached router descriptors. Fixes part of bug 16286; bugfix
264 - When we find an Ed25519 key issue in a cached descriptor, stop
265 saying the descriptor was just "uploaded". Fixes another part of
266 bug 16286; bugfix on 0.2.7.2-alpha.
268 o Minor bugfixes (control port):
269 - Repair a warning and a spurious result when getting the maximum
270 number of file descriptors from the controller. Fixes bug 16697;
271 bugfix on 0.2.7.2-alpha.
273 o Minor bugfixes (correctness):
274 - When calling channel_free_list(), avoid calling smartlist_remove()
275 while inside a FOREACH loop. This partially reverts commit
276 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
277 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
279 o Minor bugfixes (documentation):
280 - Advise users on how to configure separate IPv4 and IPv6 exit
281 policies in the manpage and sample torrcs. Related to ticket 16069.
282 - Fix the usage message of tor-resolve(1) so that it no longer lists
283 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
284 - Fix an error in the manual page and comments for
285 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
286 required "ORPort connectivity". While this is true, it is in no
287 way unique to the HSDir flag. Of all the flags, only HSDirs need a
288 DirPort configured in order for the authorities to assign that
289 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
292 o Minor bugfixes (Ed25519):
293 - Fix a memory leak when reading router descriptors with expired
294 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
296 o Minor bugfixes (linux seccomp2 sandbox):
297 - Allow bridge authorities to run correctly under the seccomp2
298 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
299 - Allow routers with ed25519 keys to run correctly under the
300 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
302 o Minor bugfixes (open file limit):
303 - Fix set_max_file_descriptors() to set by default the max open file
304 limit to the current limit when setrlimit() fails. Fixes bug
305 16274; bugfix on tor- 0.2.0.10-alpha. Patch by dgoulet.
307 o Minor bugfixes (portability):
308 - Try harder to normalize the exit status of the Tor process to the
309 standard-provided range. Fixes bug 16975; bugfix on every version
311 - Check correctly for Windows socket errors in the workqueue
312 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
313 - Fix the behavior of crypto_rand_time_range() when told to consider
314 times before 1970. (These times were possible when running in a
315 simulated network environment where time()'s output starts at
316 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
317 - Restore correct operation of TLS client-cipher detection on
318 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
320 o Minor bugfixes (relay):
321 - Ensure that worker threads actually exit when a fatal error or
322 shutdown is indicated. This fix doesn't currently affect the
323 behavior of Tor, because Tor workers never indicates fatal error
324 or shutdown except in the unit tests. Fixes bug 16868; bugfix
326 - Unblock threads before releasing the work queue mutex to ensure
327 predictable scheduling behavior. Fixes bug 16644; bugfix
330 o Code simplification and refactoring:
331 - Change the function that's called when we need to retry all
332 downloads so that it only reschedules the downloads to happen
333 immediately, rather than launching them all at once itself. This
334 further simplifies Tor's callgraph.
335 - Move some format-parsing functions out of crypto.c and
336 crypto_curve25519.c into crypto_format.c and/or util_format.c.
337 - Move the client-only parts of init_keys() into a separate
338 function. Closes ticket 16763.
339 - Simplify the microdesc_free() implementation so that it no longer
340 appears (to code analysis tools) to potentially invoke a huge
341 suite of other microdesc functions.
342 - Simply the control graph further by deferring the inner body of
343 directory_all_unreachable() into a callback. Closes ticket 16762.
344 - Treat the loss of an owning controller as equivalent to a SIGTERM
345 signal. This removes a tiny amount of duplicated code, and
346 simplifies our callgraph. Closes ticket 16788.
347 - When generating an event to send to the controller, we no longer
348 put the event over the network immediately. Instead, we queue
349 these events, and use a Libevent callback to deliver them. This
350 change simplifies Tor's callgraph by reducing the number of
351 functions from which all other Tor functions are reachable. Closes
353 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
354 that try to scan or compile every file on Unix won't decide that
356 - Remove the unused "nulterminate" argument from buf_pullup().
359 - Recommend a 40 GB example AccountingMax in torrc.sample rather
360 than a 4 GB max. Closes ticket 16742.
361 - Include the TUNING document in our source tarball. It is referred
362 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
366 - The internal pure-C tor-fw-helper tool is now removed from the Tor
367 distribution, in favor of the pure-Go clone available from
368 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
369 used by the C tor-fw-helper are not, in our opinion, very
370 confidence- inspiring in their secure-programming techniques.
372 - Remove the code that would try to aggressively flush controller
373 connections while writing to them. This code was introduced in
374 0.1.2.7-alpha, in order to keep output buffers from exceeding
375 their limits. But there is no longer a maximum output buffer size,
376 and flushing data in this way caused some undesirable recursions
377 in our call graph. Closes ticket 16480.
380 - Make "bridges+hs" the default test network. This tests almost all
381 tor functionality during make test-network, while allowing tests
382 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
383 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
384 (chutney). Patches by "teor".
385 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
386 by-side in the same parent directory. Closes ticket 16903. Patch
388 - Use environment variables rather than autoconf substitutions to
389 send variables from the build system to the test scripts. This
390 change should be easier to maintain, and cause 'make distcheck' to
391 work better than before. Fixes bug 17148.
392 - Add a new set of callgraph analysis scripts that use clang to
393 produce a list of which Tor functions are reachable from which
394 other Tor functions. We're planning to use these to help simplify
395 our code structure by identifying illogical dependencies.
396 - Add new 'test-full' and 'test-full-online' targets to run all
397 tests, including integration tests with stem and chutney.
398 - Make the test-workqueue test work on Windows by initializing the
399 network before we begin.
400 - New make target (make test-network-all) to run multiple applicable
401 chutney test cases. Patch from Teor; closes 16953.
402 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
403 functions in dns.c. Implements a portion of ticket 16831.
404 - When building Tor with testing coverage enabled, run Chutney tests
405 (if any) using the 'tor-cov' coverage binary.
406 - When running test-network or test-stem, check for the absence of
407 stem/chutney before doing any build operations.
410 Changes in version 0.2.7.2-alpha - 2015-07-27
411 This, the second alpha in the Tor 0.2.7 series, has a number of new
412 features, including a way to manually pick the number of introduction
413 points for hidden services, and the much stronger Ed25519 signing key
414 algorithm for regular Tor relays (including support for encrypted
415 offline identity keys in the new algorithm).
417 Support for Ed25519 on relays is currently limited to signing router
418 descriptors; later alphas in this series will extend Ed25519 key
419 support to more parts of the Tor protocol.
421 o Major features (Ed25519 identity keys, Proposal 220):
422 - All relays now maintain a stronger identity key, using the Ed25519
423 elliptic curve signature format. This master key is designed so
424 that it can be kept offline. Relays also generate an online
425 signing key, and a set of other Ed25519 keys and certificates.
426 These are all automatically regenerated and rotated as needed.
427 Implements part of ticket 12498.
428 - Directory authorities now vote on Ed25519 identity keys along with
429 RSA1024 keys. Implements part of ticket 12498.
430 - Directory authorities track which Ed25519 identity keys have been
431 used with which RSA1024 identity keys, and do not allow them to
432 vary freely. Implements part of ticket 12498.
433 - Microdescriptors now include Ed25519 identity keys. Implements
434 part of ticket 12498.
435 - Add support for offline encrypted Ed25519 master keys. To use this
436 feature on your tor relay, run "tor --keygen" to make a new master
437 key (or to make a new signing key if you already have a master
438 key). Closes ticket 13642.
440 o Major features (Hidden services):
441 - Add the torrc option HiddenServiceNumIntroductionPoints, to
442 specify a fixed number of introduction points. Its maximum value
443 is 10 and default is 3. Using this option can increase a hidden
444 service's reliability under load, at the cost of making it more
445 visible that the hidden service is facing extra load. Closes
447 - Remove the adaptive algorithm for choosing the number of
448 introduction points, which used to change the number of
449 introduction points (poorly) depending on the number of
450 connections the HS sees. Closes ticket 4862.
452 o Major features (onion key cross-certification):
453 - Relay descriptors now include signatures of their own identity
454 keys, made using the TAP and ntor onion keys. These signatures
455 allow relays to prove ownership of their own onion keys. Because
456 of this change, microdescriptors will no longer need to include
457 RSA identity keys. Implements proposal 228; closes ticket 12499.
459 o Major features (performance):
460 - Improve the runtime speed of Ed25519 operations by using the
461 public-domain Ed25519-donna by Andrew M. ("floodyberry").
462 Implements ticket 16467.
463 - Improve the runtime speed of the ntor handshake by using an
464 optimized curve25519 basepoint scalarmult implementation from the
465 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
466 ideas by Adam Langley. Implements ticket 9663.
468 o Major bugfixes (client-side privacy, also in 0.2.6.9):
469 - Properly separate out each SOCKSPort when applying stream
470 isolation. The error occurred because each port's session group
471 was being overwritten by a default value when the listener
472 connection was initialized. Fixes bug 16247; bugfix on
473 0.2.6.3-alpha. Patch by "jojelino".
475 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
476 - Stop refusing to store updated hidden service descriptors on a
477 client. This reverts commit 9407040c59218 (which indeed fixed bug
478 14219, but introduced a major hidden service reachability
479 regression detailed in bug 16381). This is a temporary fix since
480 we can live with the minor issue in bug 14219 (it just results in
481 some load on the network) but the regression of 16381 is too much
482 of a setback. First-round fix for bug 16381; bugfix
485 o Major bugfixes (hidden services):
486 - When cannibalizing a circuit for an introduction point, always
487 extend to the chosen exit node (creating a 4 hop circuit).
488 Previously Tor would use the current circuit exit node, which
489 changed the original choice of introduction point, and could cause
490 the hidden service to skip excluded introduction points or
491 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
494 o Major bugfixes (open file limit):
495 - The open file limit wasn't checked before calling
496 tor_accept_socket_nonblocking(), which would make Tor exceed the
497 limit. Now, before opening a new socket, Tor validates the open
498 file limit just before, and if the max has been reached, return an
499 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
501 o Major bugfixes (stability, also in 0.2.6.10):
502 - Stop crashing with an assertion failure when parsing certain kinds
503 of malformed or truncated microdescriptors. Fixes bug 16400;
504 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
505 by "cypherpunks_backup".
506 - Stop random client-side assertion failures that could occur when
507 connecting to a busy hidden service, or connecting to a hidden
508 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
511 o Minor features (directory authorities, security, also in 0.2.6.9):
512 - The HSDir flag given by authorities now requires the Stable flag.
513 For the current network, this results in going from 2887 to 2806
514 HSDirs. Also, it makes it harder for an attacker to launch a sybil
515 attack by raising the effort for a relay to become Stable to
516 require at the very least 7 days, while maintaining the 96 hours
517 uptime requirement for HSDir. Implements ticket 8243.
519 o Minor features (client):
520 - Relax the validation of hostnames in SOCKS5 requests, allowing the
521 character '_' to appear, in order to cope with domains observed in
522 the wild that are serving non-RFC compliant records. Resolves
524 - Relax the validation done to hostnames in SOCKS5 requests, and
525 allow a single trailing '.' to cope with clients that pass FQDNs
526 using that syntax to explicitly indicate that the domain name is
527 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
528 - Add GroupWritable and WorldWritable options to unix-socket based
529 SocksPort and ControlPort options. These options apply to a single
530 socket, and override {Control,Socks}SocketsGroupWritable. Closes
533 o Minor features (control protocol):
534 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
535 the control protocol. Resolves ticket 15358.
537 o Minor features (directory authorities):
538 - Directory authorities no longer vote against the "Fast", "Stable",
539 and "HSDir" flags just because they were going to vote against
540 "Running": if the consensus turns out to be that the router was
541 running, then the authority's vote should count. Patch from Peter
542 Retzlaff; closes issue 8712.
544 o Minor features (geoip, also in 0.2.6.10):
545 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
546 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
548 o Minor features (hidden services):
549 - Add the new options "HiddenServiceMaxStreams" and
550 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
551 limit the maximum number of simultaneous streams per circuit, and
552 optionally tear down the circuit when the limit is exceeded. Part
555 o Minor features (portability):
556 - Use C99 variadic macros when the compiler is not GCC. This avoids
557 failing compilations on MSVC, and fixes a log-file-based race
558 condition in our old workarounds. Original patch from Gisle Vanem.
560 o Minor bugfixes (compilation, also in 0.2.6.9):
561 - Build with --enable-systemd correctly when libsystemd is
562 installed, but systemd is not. Fixes bug 16164; bugfix on
563 0.2.6.3-alpha. Patch from Peter Palfrader.
565 o Minor bugfixes (controller):
566 - Add the descriptor ID in each HS_DESC control event. It was
567 missing, but specified in control-spec.txt. Fixes bug 15881;
568 bugfix on 0.2.5.2-alpha.
570 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
571 - Check for failures from crypto_early_init, and refuse to continue.
572 A previous typo meant that we could keep going with an
573 uninitialized crypto library, and would have OpenSSL initialize
574 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
575 when implementing ticket 4900. Patch by "teor".
577 o Minor bugfixes (hidden services):
578 - Fix a crash when reloading configuration while at least one
579 configured and one ephemeral hidden service exists. Fixes bug
580 16060; bugfix on 0.2.7.1-alpha.
581 - Avoid crashing with a double-free bug when we create an ephemeral
582 hidden service but adding it fails for some reason. Fixes bug
583 16228; bugfix on 0.2.7.1-alpha.
585 o Minor bugfixes (Linux seccomp2 sandbox):
586 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
587 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
589 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
590 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
591 these when eventfd2() support is missing. Fixes bug 16363; bugfix
592 on 0.2.6.3-alpha. Patch from "teor".
594 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
595 - Fix sandboxing to work when running as a relay, by allowing the
596 renaming of secret_id_key, and allowing the eventfd2 and futex
597 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
599 - Allow systemd connections to work with the Linux seccomp2 sandbox
600 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
603 o Minor bugfixes (relay):
604 - Fix a rarely-encountered memory leak when failing to initialize
605 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
608 o Minor bugfixes (systemd):
609 - Fix an accidental formatting error that broke the systemd
610 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
611 - Tor's systemd unit file no longer contains extraneous spaces.
612 These spaces would sometimes confuse tools like deb-systemd-
613 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
615 o Minor bugfixes (tests):
616 - Use the configured Python executable when running test-stem-full.
617 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
619 o Minor bugfixes (tests, also in 0.2.6.9):
620 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
621 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
623 o Minor bugfixes (threads, comments):
624 - Always initialize return value in compute_desc_id in rendcommon.c
625 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
626 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
627 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
628 - Remove undefined directive-in-macro in test_util_writepid clang
629 3.7 complains that using a preprocessor directive inside a macro
630 invocation in test_util_writepid in test_util.c is undefined.
631 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
633 o Code simplification and refactoring:
634 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
635 to ensure they remain consistent and visible everywhere.
636 - Remove some vestigial workarounds for the MSVC6 compiler. We
637 haven't supported that in ages.
638 - The link authentication code has been refactored for better
639 testability and reliability. It now uses code generated with the
640 "trunnel" binary encoding generator, to reduce the risk of bugs
641 due to programmer error. Done as part of ticket 12498.
644 - Include a specific and (hopefully) accurate documentation of the
645 torrc file's meta-format in doc/torrc_format.txt. This is mainly
646 of interest to people writing programs to parse or generate torrc
647 files. This document is not a commitment to long-term
648 compatibility; some aspects of the current format are a bit
649 ridiculous. Closes ticket 2325.
652 - Tor no longer supports copies of OpenSSL that are missing support
653 for Elliptic Curve Cryptography. (We began using ECC when
654 available in 0.2.4.8-alpha, for more safe and efficient key
655 negotiation.) In particular, support for at least one of P256 or
656 P224 is now required, with manual configuration needed if only
657 P224 is available. Resolves ticket 16140.
658 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
659 on an operating system that has not upgraded to OpenSSL 1.0 or
660 later, and you compile Tor from source, you will need to install a
661 more recent OpenSSL to link Tor against.) These versions of
662 OpenSSL are still supported by the OpenSSL, but the numerous
663 cryptographic improvements in later OpenSSL releases makes them a
664 clear choice. Resolves ticket 16034.
665 - Remove the HidServDirectoryV2 option. Now all relays offer to
666 store hidden service descriptors. Related to 16543.
667 - Remove the VoteOnHidServDirectoriesV2 option, since all
668 authorities have long set it to 1. Closes ticket 16543.
671 - Document use of coverity, clang static analyzer, and clang dynamic
672 undefined behavior and address sanitizers in doc/HACKING. Include
673 detailed usage instructions in the blacklist. Patch by "teor".
675 - The link authentication protocol code now has extensive tests.
676 - The relay descriptor signature testing code now has
678 - The test_workqueue program now runs faster, and is enabled by
679 default as a part of "make check".
680 - Now that OpenSSL has its own scrypt implementation, add an unit
681 test that checks for interoperability between libscrypt_scrypt()
682 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
683 and rely on EVP_PBE_scrypt() whenever possible. Resolves
687 Changes in version 0.2.6.10 - 2015-07-12
688 Tor version 0.2.6.10 fixes some significant stability and hidden
689 service client bugs, bulletproofs the cryptography init process, and
690 fixes a bug when using the sandbox code with some older versions of
691 Linux. Everyone running an older version, especially an older version
692 of 0.2.6, should upgrade.
694 o Major bugfixes (hidden service clients, stability):
695 - Stop refusing to store updated hidden service descriptors on a
696 client. This reverts commit 9407040c59218 (which indeed fixed bug
697 14219, but introduced a major hidden service reachability
698 regression detailed in bug 16381). This is a temporary fix since
699 we can live with the minor issue in bug 14219 (it just results in
700 some load on the network) but the regression of 16381 is too much
701 of a setback. First-round fix for bug 16381; bugfix
704 o Major bugfixes (stability):
705 - Stop crashing with an assertion failure when parsing certain kinds
706 of malformed or truncated microdescriptors. Fixes bug 16400;
707 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
708 by "cypherpunks_backup".
709 - Stop random client-side assertion failures that could occur when
710 connecting to a busy hidden service, or connecting to a hidden
711 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
714 o Minor features (geoip):
715 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
716 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
718 o Minor bugfixes (crypto error-handling):
719 - Check for failures from crypto_early_init, and refuse to continue.
720 A previous typo meant that we could keep going with an
721 uninitialized crypto library, and would have OpenSSL initialize
722 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
723 when implementing ticket 4900. Patch by "teor".
725 o Minor bugfixes (Linux seccomp2 sandbox):
726 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
727 these when eventfd2() support is missing. Fixes bug 16363; bugfix
728 on 0.2.6.3-alpha. Patch from "teor".
731 Changes in version 0.2.6.9 - 2015-06-11
732 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
733 requirements for receiving an HSDir flag, and addresses some other small
734 bugs in the systemd and sandbox code. Clients using circuit isolation
735 should upgrade; all directory authorities should upgrade.
737 o Major bugfixes (client-side privacy):
738 - Properly separate out each SOCKSPort when applying stream
739 isolation. The error occurred because each port's session group was
740 being overwritten by a default value when the listener connection
741 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
744 o Minor feature (directory authorities, security):
745 - The HSDir flag given by authorities now requires the Stable flag.
746 For the current network, this results in going from 2887 to 2806
747 HSDirs. Also, it makes it harder for an attacker to launch a sybil
748 attack by raising the effort for a relay to become Stable which
749 takes at the very least 7 days to do so and by keeping the 96
750 hours uptime requirement for HSDir. Implements ticket 8243.
752 o Minor bugfixes (compilation):
753 - Build with --enable-systemd correctly when libsystemd is
754 installed, but systemd is not. Fixes bug 16164; bugfix on
755 0.2.6.3-alpha. Patch from Peter Palfrader.
757 o Minor bugfixes (Linux seccomp2 sandbox):
758 - Fix sandboxing to work when running as a relaymby renaming of
759 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
760 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
761 - Allow systemd connections to work with the Linux seccomp2 sandbox
762 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
765 o Minor bugfixes (tests):
766 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
767 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
770 Changes in version 0.2.6.8 - 2015-05-21
771 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
772 fixes an authority-side bug in assigning the HSDir flag. All directory
773 authorities should upgrade.
775 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
776 - Revert commit that made directory authorities assign the HSDir
777 flag to relay without a DirPort; this was bad because such relays
778 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
779 on tor-0.2.6.3-alpha.
781 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
782 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
783 a client authorized hidden service. Fixes bug 15823; bugfix
786 o Minor features (geoip):
787 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
788 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
792 Changes in version 0.2.7.1-alpha - 2015-05-12
793 Tor 0.2.7.1-alpha is the first alpha release in its series. It
794 includes numerous small features and bugfixes against previous Tor
795 versions, and numerous small infrastructure improvements. The most
796 notable features are several new ways for controllers to interact with
797 the hidden services subsystem.
799 o New system requirements:
800 - Tor no longer includes workarounds to support Libevent versions
801 before 1.3e. Libevent 2.0 or later is recommended. Closes
804 o Major features (controller):
805 - Add the ADD_ONION and DEL_ONION commands that allow the creation
806 and management of hidden services via the controller. Closes
808 - New "GETINFO onions/current" and "GETINFO onions/detached"
809 commands to get information about hidden services created via the
810 controller. Part of ticket 6411.
811 - New HSFETCH command to launch a request for a hidden service
812 descriptor. Closes ticket 14847.
813 - New HSPOST command to upload a hidden service descriptor. Closes
814 ticket 3523. Patch by "DonnchaC".
816 o Major bugfixes (hidden services):
817 - Revert commit that made directory authorities assign the HSDir
818 flag to relay without a DirPort; this was bad because such relays
819 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
820 on tor-0.2.6.3-alpha.
822 o Minor features (clock-jump tolerance):
823 - Recover better when our clock jumps back many hours, like might
824 happen for Tails or Whonix users who start with a very wrong
825 hardware clock, use Tor to discover a more accurate time, and then
826 fix their clock. Resolves part of ticket 8766.
828 o Minor features (command-line interface):
829 - Make --hash-password imply --hush to prevent unnecessary noise.
830 Closes ticket 15542. Patch from "cypherpunks".
831 - Print a warning whenever we find a relative file path being used
832 as torrc option. Resolves issue 14018.
834 o Minor features (controller):
835 - Add DirAuthority lines for default directory authorities to the
836 output of the "GETINFO config/defaults" command if not already
837 present. Implements ticket 14840.
838 - Controllers can now use "GETINFO hs/client/desc/id/..." to
839 retrieve items from the client's hidden service descriptor cache.
841 - Implement a new controller command "GETINFO status/fresh-relay-
842 descs" to fetch a descriptor/extrainfo pair that was generated on
843 demand just for the controller's use. Implements ticket 14784.
845 o Minor features (DoS-resistance):
846 - Make it harder for attackers to overload hidden services with
847 introductions, by blocking multiple introduction requests on the
848 same circuit. Resolves ticket 15515.
850 o Minor features (geoip):
851 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
852 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
855 o Minor features (HS popularity countermeasure):
856 - To avoid leaking HS popularity, don't cycle the introduction point
857 when we've handled a fixed number of INTRODUCE2 cells but instead
858 cycle it when a random number of introductions is reached, thus
859 making it more difficult for an attacker to find out the amount of
860 clients that have used the introduction point for a specific HS.
863 o Minor features (logging):
864 - Include the Tor version in all LD_BUG log messages, since people
865 tend to cut and paste those into the bugtracker. Implements
868 o Minor features (pluggable transports):
869 - When launching managed pluggable transports on Linux systems,
870 attempt to have the kernel deliver a SIGTERM on tor exit if the
871 pluggable transport process is still running. Resolves
873 - When launching managed pluggable transports, setup a valid open
874 stdin in the child process that can be used to detect if tor has
875 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
876 can be used by implementations to detect this new behavior.
877 Resolves ticket 15435.
879 o Minor features (testing):
880 - Add a test to verify that the compiler does not eliminate our
881 memwipe() implementation. Closes ticket 15377.
882 - Add make rule `check-changes` to verify the format of changes
883 files. Closes ticket 15180.
884 - Add unit tests for control_event_is_interesting(). Add a compile-
885 time check that the number of events doesn't exceed the capacity
886 of control_event_t.event_mask. Closes ticket 15431, checks for
887 bugs similar to 13085. Patch by "teor".
888 - Command-line argument tests moved to Stem. Resolves ticket 14806.
889 - Integrate the ntor, backtrace, and zero-length keys tests into the
890 automake test suite. Closes ticket 15344.
891 - Remove assertions during builds to determine Tor's test coverage.
892 We don't want to trigger these even in assertions, so including
893 them artificially makes our branch coverage look worse than it is.
894 This patch provides the new test-stem-full and coverage-html-full
895 configure options. Implements ticket 15400.
897 o Minor bugfixes (build):
898 - Improve out-of-tree builds by making non-standard rules work and
899 clean up additional files and directories. Fixes bug 15053; bugfix
902 o Minor bugfixes (command-line interface):
903 - When "--quiet" is provided along with "--validate-config", do not
904 write anything to stdout on success. Fixes bug 14994; bugfix
906 - When complaining about bad arguments to "--dump-config", use
909 o Minor bugfixes (configuration, unit tests):
910 - Only add the default fallback directories when the DirAuthorities,
911 AlternateDirAuthority, and FallbackDir directory config options
912 are set to their defaults. The default fallback directory list is
913 currently empty, this fix will only change tor's behavior when it
914 has default fallback directories. Includes unit tests for
915 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
916 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
918 o Minor bugfixes (correctness):
919 - For correctness, avoid modifying a constant string in
920 handle_control_postdescriptor. Fixes bug 15546; bugfix
922 - Remove side-effects from tor_assert() calls. This was harmless,
923 because we never disable assertions, but it is bad style and
924 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
927 o Minor bugfixes (hidden service):
928 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
929 a client authorized hidden service. Fixes bug 15823; bugfix
931 - Remove an extraneous newline character from the end of hidden
932 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
934 o Minor bugfixes (interface):
935 - Print usage information for --dump-config when it is used without
936 an argument. Also, fix the error message to use different wording
937 and add newline at the end. Fixes bug 15541; bugfix
940 o Minor bugfixes (logs):
941 - When building Tor under Clang, do not include an extra set of
942 parentheses in log messages that include function names. Fixes bug
943 15269; bugfix on every released version of Tor when compiled with
946 o Minor bugfixes (network):
947 - When attempting to use fallback technique for network interface
948 lookup, disregard loopback and multicast addresses since they are
949 unsuitable for public communications.
951 o Minor bugfixes (statistics):
952 - Disregard the ConnDirectionStatistics torrc options when Tor is
953 not a relay since in that mode of operation no sensible data is
954 being collected and because Tor might run into measurement hiccups
955 when running as a client for some time, then becoming a relay.
956 Fixes bug 15604; bugfix on 0.2.2.35.
958 o Minor bugfixes (test networks):
959 - When self-testing reachability, use ExtendAllowPrivateAddresses to
960 determine if local/private addresses imply reachability. The
961 previous fix used TestingTorNetwork, which implies
962 ExtendAllowPrivateAddresses, but this excluded rare configurations
963 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
964 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
965 issue discovered by CJ Ess.
967 o Minor bugfixes (testing):
968 - Check for matching value in server response in ntor_ref.py. Fixes
969 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
971 - Set the severity correctly when testing
972 get_interface_addresses_ifaddrs() and
973 get_interface_addresses_win32(), so that the tests fail gracefully
974 instead of triggering an assertion. Fixes bug 15759; bugfix on
975 0.2.6.3-alpha. Reported by Nicolas Derive.
977 o Code simplification and refactoring:
978 - Move the hacky fallback code out of get_interface_address6() into
979 separate function and get it covered with unit-tests. Resolves
981 - Refactor hidden service client-side cache lookup to intelligently
982 report its various failure cases, and disentangle failure cases
983 involving a lack of introduction points. Closes ticket 14391.
984 - Use our own Base64 encoder instead of OpenSSL's, to allow more
985 control over the output. Part of ticket 15652.
988 - Improve the descriptions of statistics-related torrc options in
989 the manpage to describe rationale and possible uses cases. Fixes
991 - Improve the layout and formatting of ./configure --help messages.
992 Closes ticket 15024. Patch from "cypherpunks".
993 - Standardize on the term "server descriptor" in the manual page.
994 Previously, we had used "router descriptor", "server descriptor",
995 and "relay descriptor" interchangeably. Part of ticket 14987.
998 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
999 and always use the internal Base64 decoder. The internal decoder
1000 has been part of tor since tor-0.2.0.10-alpha, and no one should
1001 be using the OpenSSL one. Part of ticket 15652.
1002 - Remove the 'tor_strclear()' function; use memwipe() instead.
1003 Closes ticket 14922.
1006 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
1007 fingerprinting we now recommend pluggable transports; for forward-
1008 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
1009 - Remove the undocumented "--digests" command-line option. It
1010 complicated our build process, caused subtle build issues on
1011 multiple platforms, and is now redundant since we started
1012 including git version identifiers. Closes ticket 14742.
1013 - Tor no longer contains checks for ancient directory cache versions
1014 that didn't know about microdescriptors.
1015 - Tor no longer contains workarounds for stat files generated by
1016 super-old versions of Tor that didn't choose guards sensibly.
1019 Changes in version 0.2.4.27 - 2015-04-06
1020 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
1021 could be used by an attacker to crash hidden services, or crash clients
1022 visiting hidden services. Hidden services should upgrade as soon as
1023 possible; clients should upgrade whenever packages become available.
1025 This release also backports a simple improvement to make hidden
1026 services a bit less vulnerable to denial-of-service attacks.
1028 o Major bugfixes (security, hidden service):
1029 - Fix an issue that would allow a malicious client to trigger an
1030 assertion failure and halt a hidden service. Fixes bug 15600;
1031 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
1032 - Fix a bug that could cause a client to crash with an assertion
1033 failure when parsing a malformed hidden service descriptor. Fixes
1034 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1036 o Minor features (DoS-resistance, hidden service):
1037 - Introduction points no longer allow multiple INTRODUCE1 cells to
1038 arrive on the same circuit. This should make it more expensive for
1039 attackers to overwhelm hidden services with introductions.
1040 Resolves ticket 15515.
1043 Changes in version 0.2.6.7 - 2015-04-06
1044 Tor 0.2.6.7 fixes two security issues that could be used by an
1045 attacker to crash hidden services, or crash clients visiting hidden
1046 services. Hidden services should upgrade as soon as possible; clients
1047 should upgrade whenever packages become available.
1049 This release also contains two simple improvements to make hidden
1050 services a bit less vulnerable to denial-of-service attacks.
1052 o Major bugfixes (security, hidden service):
1053 - Fix an issue that would allow a malicious client to trigger an
1054 assertion failure and halt a hidden service. Fixes bug 15600;
1055 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
1056 - Fix a bug that could cause a client to crash with an assertion
1057 failure when parsing a malformed hidden service descriptor. Fixes
1058 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1060 o Minor features (DoS-resistance, hidden service):
1061 - Introduction points no longer allow multiple INTRODUCE1 cells to
1062 arrive on the same circuit. This should make it more expensive for
1063 attackers to overwhelm hidden services with introductions.
1064 Resolves ticket 15515.
1065 - Decrease the amount of reattempts that a hidden service performs
1066 when its rendezvous circuits fail. This reduces the computational
1067 cost for running a hidden service under heavy load. Resolves
1071 Changes in version 0.2.6.6 - 2015-03-24
1072 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
1074 It adds numerous safety, security, correctness, and performance
1075 improvements. Client programs can be configured to use more kinds of
1076 sockets, AutomapHosts works better, the multithreading backend is
1077 improved, cell transmission is refactored, test coverage is much
1078 higher, more denial-of-service attacks are handled, guard selection is
1079 improved to handle long-term guards better, pluggable transports
1080 should work a bit better, and some annoying hidden service performance
1081 bugs should be addressed.
1083 o Minor bugfixes (portability):
1084 - Use the correct datatype in the SipHash-2-4 function to prevent
1085 compilers from assuming any sort of alignment. Fixes bug 15436;
1086 bugfix on 0.2.5.3-alpha.
1088 Changes in version 0.2.6.5-rc - 2015-03-18
1089 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
1090 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
1092 o Major bugfixes (client):
1093 - Avoid crashing when making certain configuration option changes on
1094 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
1097 o Major bugfixes (pluggable transports):
1098 - Initialize the extended OR Port authentication cookie before
1099 launching pluggable transports. This prevents a race condition
1100 that occured when server-side pluggable transports would cache the
1101 authentication cookie before it has been (re)generated. Fixes bug
1102 15240; bugfix on 0.2.5.1-alpha.
1104 o Major bugfixes (portability):
1105 - Do not crash on startup when running on Solaris. Fixes a bug
1106 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
1109 o Minor features (heartbeat):
1110 - On relays, report how many connections we negotiated using each
1111 version of the Tor link protocols. This information will let us
1112 know if removing support for very old versions of the Tor
1113 protocols is harming the network. Closes ticket 15212.
1115 o Code simplification and refactoring:
1116 - Refactor main loop to extract the 'loop' part. This makes it
1117 easier to run Tor under Shadow. Closes ticket 15176.
1120 Changes in version 0.2.5.11 - 2015-03-17
1121 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
1123 It backports several bugfixes from the 0.2.6 branch, including a
1124 couple of medium-level security fixes for relays and exit nodes.
1125 It also updates the list of directory authorities.
1127 o Directory authority changes:
1128 - Remove turtles as a directory authority.
1129 - Add longclaw as a new (v3) directory authority. This implements
1130 ticket 13296. This keeps the directory authority count at 9.
1131 - The directory authority Faravahar has a new IP address. This
1132 closes ticket 14487.
1134 o Major bugfixes (crash, OSX, security):
1135 - Fix a remote denial-of-service opportunity caused by a bug in
1136 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
1139 o Major bugfixes (relay, stability, possible security):
1140 - Fix a bug that could lead to a relay crashing with an assertion
1141 failure if a buffer of exactly the wrong layout was passed to
1142 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1143 0.2.0.10-alpha. Patch from 'cypherpunks'.
1144 - Do not assert if the 'data' pointer on a buffer is advanced to the
1145 very end of the buffer; log a BUG message instead. Only assert if
1146 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1148 o Major bugfixes (exit node stability):
1149 - Fix an assertion failure that could occur under high DNS load.
1150 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1151 diagnosed and fixed by "cypherpunks".
1153 o Major bugfixes (Linux seccomp2 sandbox):
1154 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
1155 crash during attempts to call wait4. Fixes bug 15088; bugfix on
1156 0.2.5.1-alpha. Patch from "sanic".
1158 o Minor features (controller):
1159 - New "GETINFO bw-event-cache" to get information about recent
1160 bandwidth events. Closes ticket 14128. Useful for controllers to
1161 get recent bandwidth history after the fix for ticket 13988.
1163 o Minor features (geoip):
1164 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1165 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1168 o Minor bugfixes (client, automapping):
1169 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
1170 no value follows the option. Fixes bug 14142; bugfix on
1171 0.2.4.7-alpha. Patch by "teor".
1172 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
1173 14195; bugfix on 0.1.0.1-rc.
1175 o Minor bugfixes (compilation):
1176 - Build without warnings with the stock OpenSSL srtp.h header, which
1177 has a duplicate declaration of SSL_get_selected_srtp_profile().
1178 Fixes bug 14220; this is OpenSSL's bug, not ours.
1180 o Minor bugfixes (directory authority):
1181 - Allow directory authorities to fetch more data from one another if
1182 they find themselves missing lots of votes. Previously, they had
1183 been bumping against the 10 MB queued data limit. Fixes bug 14261;
1184 bugfix on 0.1.2.5-alpha.
1185 - Enlarge the buffer to read bwauth generated files to avoid an
1186 issue when parsing the file in dirserv_read_measured_bandwidths().
1187 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
1189 o Minor bugfixes (statistics):
1190 - Increase period over which bandwidth observations are aggregated
1191 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
1193 o Minor bugfixes (preventative security, C safety):
1194 - When reading a hexadecimal, base-32, or base-64 encoded value from
1195 a string, always overwrite the whole output buffer. This prevents
1196 some bugs where we would look at (but fortunately, not reveal)
1197 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
1201 Changes in version 0.2.4.26 - 2015-03-17
1202 Tor 0.2.4.26 includes an updated list of directory authorities. It
1203 also backports a couple of stability and security bugfixes from 0.2.5
1206 o Directory authority changes:
1207 - Remove turtles as a directory authority.
1208 - Add longclaw as a new (v3) directory authority. This implements
1209 ticket 13296. This keeps the directory authority count at 9.
1210 - The directory authority Faravahar has a new IP address. This
1211 closes ticket 14487.
1213 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
1214 - Fix an assertion failure that could occur under high DNS load.
1215 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1216 diagnosed and fixed by "cypherpunks".
1218 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
1219 - Fix a bug that could lead to a relay crashing with an assertion
1220 failure if a buffer of exactly the wrong layout was passed to
1221 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1222 0.2.0.10-alpha. Patch from 'cypherpunks'.
1223 - Do not assert if the 'data' pointer on a buffer is advanced to the
1224 very end of the buffer; log a BUG message instead. Only assert if
1225 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1227 o Minor features (geoip):
1228 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1229 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1232 Changes in version 0.2.6.4-rc - 2015-03-09
1233 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
1234 attacker might be able to use in order to crash certain Tor
1235 directories. It also resolves some minor issues left over from, or
1236 introduced in, Tor 0.2.6.3-alpha or earlier.
1238 o Major bugfixes (crash, OSX, security):
1239 - Fix a remote denial-of-service opportunity caused by a bug in
1240 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
1243 o Major bugfixes (relay, stability, possible security):
1244 - Fix a bug that could lead to a relay crashing with an assertion
1245 failure if a buffer of exactly the wrong layout is passed to
1246 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
1247 0.2.0.10-alpha. Patch from "cypherpunks".
1248 - Do not assert if the 'data' pointer on a buffer is advanced to the
1249 very end of the buffer; log a BUG message instead. Only assert if
1250 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
1252 o Major bugfixes (FreeBSD IPFW transparent proxy):
1253 - Fix address detection with FreeBSD transparent proxies, when
1254 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
1257 o Major bugfixes (Linux seccomp2 sandbox):
1258 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
1259 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
1261 - Allow AF_UNIX hidden services to be used with the seccomp2
1262 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
1263 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
1264 crash during attempts to call wait4. Fixes bug 15088; bugfix on
1265 0.2.5.1-alpha. Patch from "sanic".
1267 o Minor features (controller):
1268 - Messages about problems in the bootstrap process now include
1269 information about the server we were trying to connect to when we
1270 noticed the problem. Closes ticket 15006.
1272 o Minor features (geoip):
1273 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
1274 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
1277 o Minor features (logs):
1278 - Quiet some log messages in the heartbeat and at startup. Closes
1281 o Minor bugfixes (certificate handling):
1282 - If an authority operator accidentally makes a signing certificate
1283 with a future publication time, do not discard its real signing
1284 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
1285 - Remove any old authority certificates that have been superseded
1286 for at least two days. Previously, we would keep superseded
1287 certificates until they expired, if they were published close in
1288 time to the certificate that superseded them. Fixes bug 11454;
1289 bugfix on 0.2.1.8-alpha.
1291 o Minor bugfixes (compilation):
1292 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
1294 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
1297 o Minor bugfixes (testing):
1298 - Fix endianness issues in unit test for resolve_my_address() to
1299 have it pass on big endian systems. Fixes bug 14980; bugfix on
1301 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
1302 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
1303 - When running the new 'make test-stem' target, use the configured
1304 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
1306 - When running the zero-length-keys tests, do not use the default
1307 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
1310 o Directory authority IP change:
1311 - The directory authority Faravahar has a new IP address. This
1312 closes ticket 14487.
1315 - Remove some lingering dead code that once supported mempools.
1316 Mempools were disabled by default in 0.2.5, and removed entirely
1317 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
1321 Changes in version 0.2.6.3-alpha - 2015-02-19
1322 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
1323 the 0.2.6.x series. It introduces support for more kinds of sockets,
1324 makes it harder to accidentally run an exit, improves our
1325 multithreading backend, incorporates several fixes for the
1326 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
1328 If no major regressions or security holes are found in this version,
1329 the next version will be a release candidate.
1331 o Deprecated versions:
1332 - Tor relays older than 0.2.4.18-rc are no longer allowed to
1333 advertise themselves on the network. Closes ticket 13555.
1335 o Major features (security, unix domain sockets):
1336 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
1337 applications can reach Tor without having to create AF_INET or
1338 AF_INET6 sockets, meaning they can completely disable their
1339 ability to make non-Tor network connections. To create a socket of
1340 this type, use "SocksPort unix:/path/to/socket". Implements
1342 - Support mapping hidden service virtual ports to AF_UNIX sockets.
1343 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
1344 Implements ticket 11485.
1346 o Major features (changed defaults):
1347 - Prevent relay operators from unintentionally running exits: When a
1348 relay is configured as an exit node, we now warn the user unless
1349 the "ExitRelay" option is set to 1. We warn even more loudly if
1350 the relay is configured with the default exit policy, since this
1351 can indicate accidental misconfiguration. Setting "ExitRelay 0"
1352 stops Tor from running as an exit relay. Closes ticket 10067.
1354 o Major features (directory system):
1355 - When downloading server- or microdescriptors from a directory
1356 server, we no longer launch multiple simultaneous requests to the
1357 same server. This reduces load on the directory servers,
1358 especially when directory guards are in use. Closes ticket 9969.
1359 - When downloading server- or microdescriptors over a tunneled
1360 connection, do not limit the length of our requests to what the
1361 Squid proxy is willing to handle. Part of ticket 9969.
1362 - Authorities can now vote on the correct digests and latest
1363 versions for different software packages. This allows packages
1364 that include Tor to use the Tor authority system as a way to get
1365 notified of updates and their correct digests. Implements proposal
1366 227. Closes ticket 10395.
1368 o Major features (guards):
1369 - Introduce the Guardfraction feature to improves load balancing on
1370 guard nodes. Specifically, it aims to reduce the traffic gap that
1371 guard nodes experience when they first get the Guard flag. This is
1372 a required step if we want to increase the guard lifetime to 9
1373 months or greater. Closes ticket 9321.
1375 o Major features (performance):
1376 - Make the CPU worker implementation more efficient by avoiding the
1377 kernel and lengthening pipelines. The original implementation used
1378 sockets to transfer data from the main thread to the workers, and
1379 didn't allow any thread to be assigned more than a single piece of
1380 work at once. The new implementation avoids communications
1381 overhead by making requests in shared memory, avoiding kernel IO
1382 where possible, and keeping more requests in flight at once.
1383 Implements ticket 9682.
1385 o Major features (relay):
1386 - Raise the minimum acceptable configured bandwidth rate for bridges
1387 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
1388 20 KiB/sec.) Closes ticket 13822.
1390 o Major bugfixes (exit node stability):
1391 - Fix an assertion failure that could occur under high DNS load.
1392 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
1393 diagnosed and fixed by "cypherpunks".
1395 o Major bugfixes (mixed relay-client operation):
1396 - When running as a relay and client at the same time (not
1397 recommended), if we decide not to use a new guard because we want
1398 to retry older guards, only close the locally-originating circuits
1399 passing through that guard. Previously we would close all the
1400 circuits through that guard. Fixes bug 9819; bugfix on
1401 0.2.1.1-alpha. Reported by "skruffy".
1403 o Minor features (build):
1404 - New --disable-system-torrc compile-time option to prevent Tor from
1405 looking for the system-wide torrc or torrc-defaults files.
1406 Resolves ticket 13037.
1408 o Minor features (controller):
1409 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
1410 events so controllers can observe circuit isolation inputs. Closes
1412 - ControlPort now supports the unix:/path/to/socket syntax as an
1413 alternative to the ControlSocket option, for consistency with
1414 SocksPort and HiddenServicePort. Closes ticket 14451.
1415 - New "GETINFO bw-event-cache" to get information about recent
1416 bandwidth events. Closes ticket 14128. Useful for controllers to
1417 get recent bandwidth history after the fix for ticket 13988.
1419 o Minor features (Denial of service resistance):
1420 - Count the total number of bytes used storing hidden service
1421 descriptors against the value of MaxMemInQueues. If we're low on
1422 memory, and more than 20% of our memory is used holding hidden
1423 service descriptors, free them until no more than 10% of our
1424 memory holds hidden service descriptors. Free the least recently
1425 fetched descriptors first. Resolves ticket 13806.
1426 - When we have recently been under memory pressure (over 3/4 of
1427 MaxMemInQueues is allocated), then allocate smaller zlib objects
1428 for small requests. Closes ticket 11791.
1430 o Minor features (geoip):
1431 - Update geoip and geoip6 files to the January 7 2015 Maxmind
1432 GeoLite2 Country database.
1434 o Minor features (guard nodes):
1435 - Reduce the time delay before saving guard status to disk from 10
1436 minutes to 30 seconds (or from one hour to 10 minutes if
1437 AvoidDiskWrites is set). Closes ticket 12485.
1439 o Minor features (hidden service):
1440 - Make Sybil attacks against hidden services harder by changing the
1441 minimum time required to get the HSDir flag from 25 hours up to 96
1442 hours. Addresses ticket 14149.
1443 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
1444 services to disable the anti-scanning feature introduced in
1445 0.2.6.2-alpha. With this option not set, a connection to an
1446 unlisted port closes the circuit. With this option set, only a
1447 RELAY_DONE cell is sent. Closes ticket 14084.
1449 o Minor features (interface):
1450 - Implement "-f -" command-line option to read torrc configuration
1451 from standard input, if you don't want to store the torrc file in
1452 the file system. Implements feature 13865.
1454 o Minor features (logging):
1455 - Add a count of unique clients to the bridge heartbeat message.
1456 Resolves ticket 6852.
1457 - Suppress "router info incompatible with extra info" message when
1458 reading extrainfo documents from cache. (This message got loud
1459 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
1461 - Elevate hidden service authorized-client message from DEBUG to
1462 INFO. Closes ticket 14015.
1464 o Minor features (stability):
1465 - Add assertions in our hash-table iteration code to check for
1466 corrupted values that could cause infinite loops. Closes
1469 o Minor features (systemd):
1470 - Various improvements and modernizations in systemd hardening
1471 support. Closes ticket 13805. Patch from Craig Andrews.
1473 o Minor features (testing networks):
1474 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
1475 and the default on a testing network to 2 minutes. Drop the
1476 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
1477 keep the default on a testing network at 30 seconds. This reduces
1478 HS bootstrap time to around 25 seconds. Also, change the default
1479 time in test-network.sh to match. Closes ticket 13401. Patch
1481 - Create TestingDirAuthVoteHSDir to correspond to
1482 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
1483 HSDir flag for the listed relays regardless of uptime or ORPort
1484 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
1485 Partial implementation for ticket 14067. Patch by "teor".
1487 o Minor features (tor2web mode):
1488 - Introduce the config option Tor2webRendezvousPoints, which allows
1489 clients in Tor2webMode to select a specific Rendezvous Point to be
1490 used in HS circuits. This might allow better performance for
1491 Tor2Web nodes. Implements ticket 12844.
1493 o Minor bugfixes (client DNS):
1494 - Report the correct cached DNS expiration times on SOCKS port or in
1495 DNS replies. Previously, we would report everything as "never
1496 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
1497 - Avoid a small memory leak when we find a cached answer for a
1498 reverse DNS lookup in a client-side DNS cache. (Remember, client-
1499 side DNS caching is off by default, and is not recommended.) Fixes
1500 bug 14259; bugfix on 0.2.0.1-alpha.
1502 o Minor bugfixes (client, automapping):
1503 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
1504 no value follows the option. Fixes bug 14142; bugfix on
1505 0.2.4.7-alpha. Patch by "teor".
1506 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
1507 14195; bugfix on 0.1.0.1-rc.
1508 - Prevent changes to other options from removing the wildcard value
1509 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
1511 - Allow MapAddress and AutomapHostsOnResolve to work together when
1512 an address is mapped into another address type (like .onion) that
1513 must be automapped at resolve time. Fixes bug 7555; bugfix
1516 o Minor bugfixes (client, bridges):
1517 - When we are using bridges and we had a network connectivity
1518 problem, only retry connecting to our currently configured
1519 bridges, not all bridges we know about and remember using. Fixes
1520 bug 14216; bugfix on 0.2.2.17-alpha.
1522 o Minor bugfixes (client, IPv6):
1523 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
1524 flag is not set; and not because the NoIPv4Traffic flag was set.
1525 Previously we'd looked at the NoIPv4Traffic flag for both types of
1526 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
1528 o Minor bugfixes (compilation):
1529 - The address of an array in the middle of a structure will always
1530 be non-NULL. clang recognises this and complains. Disable the
1531 tautologous and redundant check to silence this warning. Fixes bug
1532 14001; bugfix on 0.2.1.2-alpha.
1533 - Avoid warnings when building with systemd 209 or later. Fixes bug
1534 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
1535 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
1536 Addresses ticket 14188.
1537 - Build without warnings with the stock OpenSSL srtp.h header, which
1538 has a duplicate declaration of SSL_get_selected_srtp_profile().
1539 Fixes bug 14220; this is OpenSSL's bug, not ours.
1540 - Do not compile any code related to Tor2Web mode when Tor2Web mode
1541 is not enabled at compile time. Previously, this code was included
1542 in a disabled state. See discussion on ticket 12844.
1543 - Remove the --disable-threads configure option again. It was
1544 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
1545 14819; bugfix on 0.2.6.2-alpha.
1547 o Minor bugfixes (controller):
1548 - Report "down" in response to the "GETINFO entry-guards" command
1549 when relays are down with an unreachable_since value. Previously,
1550 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
1551 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
1552 14116; bugfix on 0.2.2.9-alpha.
1553 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
1554 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
1556 o Minor bugfixes (directory authority):
1557 - Allow directory authorities to fetch more data from one another if
1558 they find themselves missing lots of votes. Previously, they had
1559 been bumping against the 10 MB queued data limit. Fixes bug 14261;
1560 bugfix on 0.1.2.5-alpha.
1561 - Do not attempt to download extrainfo documents which we will be
1562 unable to validate with a matching server descriptor. Fixes bug
1563 13762; bugfix on 0.2.0.1-alpha.
1564 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
1565 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
1566 - Enlarge the buffer to read bwauth generated files to avoid an
1567 issue when parsing the file in dirserv_read_measured_bandwidths().
1568 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
1570 o Minor bugfixes (file handling):
1571 - Stop failing when key files are zero-length. Instead, generate new
1572 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
1573 on all versions of Tor. Patch by "teor".
1574 - Stop generating a fresh .old RSA onion key file when the .old file
1575 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
1576 - Avoid overwriting .old key files with empty key files.
1577 - Skip loading zero-length extrainfo store, router store, stats,
1578 state, and key files.
1579 - Avoid crashing when trying to reload a torrc specified as a
1580 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
1583 o Minor bugfixes (hidden services):
1584 - Close the introduction circuit when we have no more usable intro
1585 points, instead of waiting for it to time out. This also ensures
1586 that no follow-up HS descriptor fetch is triggered when the
1587 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
1588 - When fetching a hidden service descriptor for a down service that
1589 was recently up, do not keep refetching until we try the same
1590 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
1591 - Successfully launch Tor with a nonexistent hidden service
1592 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
1593 14106; bugfix on 0.2.6.2-alpha.
1595 o Minor bugfixes (logging):
1596 - Avoid crashing when there are more log domains than entries in
1597 domain_list. Bugfix on 0.2.3.1-alpha.
1598 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
1600 - Don't log messages to stdout twice when starting up. Fixes bug
1601 13993; bugfix on 0.2.6.1-alpha.
1603 o Minor bugfixes (parsing):
1604 - Stop accepting milliseconds (or other junk) at the end of
1605 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
1606 - Support two-number and three-number version numbers correctly, in
1607 case we change the Tor versioning system in the future. Fixes bug
1608 13661; bugfix on 0.0.8pre1.
1610 o Minor bugfixes (path counting):
1611 - When deciding whether the consensus lists any exit nodes, count
1612 the number listed in the consensus, not the number we have
1613 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
1614 - When deciding whether we have any exit nodes, only examine
1615 ExitNodes when the ExitNodes option is actually set. Fixes part of
1616 bug 14918; bugfix on 0.2.6.2-alpha.
1617 - Get rid of redundant and possibly scary warnings that we are
1618 missing directory information while we bootstrap. Fixes part of
1619 bug 14918; bugfix on 0.2.6.2-alpha.
1621 o Minor bugfixes (portability):
1622 - Fix the ioctl()-based network interface lookup code so that it
1623 will work on systems that have variable-length struct ifreq, for
1625 - Fix scheduler compilation on targets where char is unsigned. Fixes
1626 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
1628 o Minor bugfixes (sandbox):
1629 - Allow glibc fatal errors to be sent to stderr before Tor exits.
1630 Previously, glibc would try to write them to /dev/tty, and the
1631 sandbox would trap the call and make Tor exit prematurely. Fixes
1632 bug 14759; bugfix on 0.2.5.1-alpha.
1634 o Minor bugfixes (shutdown):
1635 - When shutting down, always call event_del() on lingering read or
1636 write events before freeing them. Otherwise, we risk double-frees
1637 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
1640 o Minor bugfixes (small memory leaks):
1641 - Avoid leaking memory when using IPv6 virtual address mappings.
1642 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
1645 o Minor bugfixes (statistics):
1646 - Increase period over which bandwidth observations are aggregated
1647 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
1649 o Minor bugfixes (systemd support):
1650 - Fix detection and operation of systemd watchdog. Fixes part of bug
1651 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
1652 - Run correctly under systemd with the RunAsDaemon option set. Fixes
1653 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
1654 - Inform the systemd supervisor about more changes in the Tor
1655 process status. Implements part of ticket 14141. Patch from
1657 - Cause the "--disable-systemd" option to actually disable systemd
1658 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
1661 o Minor bugfixes (TLS):
1662 - Check more thoroughly throughout the TLS code for possible
1663 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
1665 o Minor bugfixes (transparent proxy):
1666 - Use getsockname, not getsockopt, to retrieve the address for a
1667 TPROXY-redirected connection. Fixes bug 13796; bugfix
1670 o Code simplification and refactoring:
1671 - Move fields related to isolating and configuring client ports into
1672 a shared structure. Previously, they were duplicated across
1673 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
1674 to copy them correctly had been the cause of at least one bug in
1675 the past. Closes ticket 8546.
1676 - Refactor the get_interface_addresses_raw() doom-function into
1677 multiple smaller and simpler subfunctions. Cover the resulting
1678 subfunctions with unit-tests. Fixes a significant portion of
1680 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
1681 only for version <= 0.2.2.24 which is now deprecated. Closes
1683 - Remove a test for a long-defunct broken version-one
1687 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
1688 for writing the OpenBSD-specific tips. Resolves ticket 13702.
1689 - Make the tor-resolve documentation match its help string and its
1690 options. Resolves part of ticket 14325.
1691 - Log a more useful error message from tor-resolve when failing to
1692 look up a hidden service address. Resolves part of ticket 14325.
1694 o Downgraded warnings:
1695 - Don't warn when we've attempted to contact a relay using the wrong
1696 ntor onion key. Closes ticket 9635.
1699 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
1700 longer silently accepted as an alias for "ExitNodes".
1701 - The --enable-mempool and --enable-buf-freelists options, which
1702 were originally created to work around bad malloc implementations,
1703 no longer exist. They were off-by-default in 0.2.5. Closes
1707 - Make the checkdir/perms test complete successfully even if the
1708 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
1709 - Test that tor does not fail when key files are zero-length. Check
1710 that tor generates new keys, and overwrites the empty key files.
1711 - Test that tor generates new keys when keys are missing
1712 (existing behavior).
1713 - Test that tor does not overwrite key files that already contain
1714 data (existing behavior). Tests bug 13111. Patch by "teor".
1715 - New "make test-stem" target to run stem integration tests.
1716 Requires that the "STEM_SOURCE_DIR" environment variable be set.
1717 Closes ticket 14107.
1718 - Make the test_cmdline_args.py script work correctly on Windows.
1719 Patch from Gisle Vanem.
1720 - Move the slower unit tests into a new "./src/test/test-slow"
1721 binary that can be run independently of the other tests. Closes
1723 - Avoid undefined behavior when sampling huge values from the
1724 Laplace distribution. This made unittests fail on Raspberry Pi.
1725 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
1728 Changes in version 0.2.6.2-alpha - 2014-12-31
1729 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
1730 It introduces a major new backend for deciding when to send cells on
1731 channels, which should lead down the road to big performance
1732 increases. It contains security and statistics features for better
1733 work on hidden services, and numerous bugfixes.
1735 This release contains many new unit tests, along with major
1736 performance improvements for running testing networks using Chutney.
1737 Thanks to a series of patches contributed by "teor", testing networks
1738 should now bootstrap in seconds, rather than minutes.
1740 o Major features (relay, infrastructure):
1741 - Complete revision of the code that relays use to decide which cell
1742 to send next. Formerly, we selected the best circuit to write on
1743 each channel, but we didn't select among channels in any
1744 sophisticated way. Now, we choose the best circuits globally from
1745 among those whose channels are ready to deliver traffic.
1747 This patch implements a new inter-cmux comparison API, a global
1748 high/low watermark mechanism and a global scheduler loop for
1749 transmission prioritization across all channels as well as among
1750 circuits on one channel. This schedule is currently tuned to
1751 (tolerantly) avoid making changes in network performance, but it
1752 should form the basis for major circuit performance increases in
1753 the future. Code by Andrea; tuning by Rob Jansen; implements
1756 o Major features (hidden services):
1757 - Make HS port scanning more difficult by immediately closing the
1758 circuit when a user attempts to connect to a nonexistent port.
1759 Closes ticket 13667.
1760 - Add a HiddenServiceStatistics option that allows Tor relays to
1761 gather and publish statistics about the overall size and volume of
1762 hidden service usage. Specifically, when this option is turned on,
1763 an HSDir will publish an approximate number of hidden services
1764 that have published descriptors to it the past 24 hours. Also, if
1765 a relay has acted as a hidden service rendezvous point, it will
1766 publish the approximate amount of rendezvous cells it has relayed
1767 the past 24 hours. The statistics themselves are obfuscated so
1768 that the exact values cannot be derived. For more details see
1769 proposal 238, "Better hidden service stats from Tor relays". This
1770 feature is currently disabled by default. Implements feature 13192.
1772 o Major bugfixes (client, automap):
1773 - Repair automapping with IPv6 addresses. This automapping should
1774 have worked previously, but one piece of debugging code that we
1775 inserted to detect a regression actually caused the regression to
1776 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
1777 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
1780 o Major bugfixes (hidden services):
1781 - When closing an introduction circuit that was opened in parallel
1782 with others, don't mark the introduction point as unreachable.
1783 Previously, the first successful connection to an introduction
1784 point would make the other introduction points get marked as
1785 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
1787 o Directory authority changes:
1788 - Remove turtles as a directory authority.
1789 - Add longclaw as a new (v3) directory authority. This implements
1790 ticket 13296. This keeps the directory authority count at 9.
1792 o Major removed features:
1793 - Tor clients no longer support connecting to hidden services
1794 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
1795 option has been removed. (There shouldn't be any hidden services
1796 running these versions on the network.) Closes ticket 7803.
1798 o Minor features (client):
1799 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
1800 is enabled, reject requests with IP addresses as hostnames.
1801 Resolves ticket 13315.
1803 o Minor features (controller):
1804 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
1805 write an unscheduled heartbeat message to the log. Implements
1808 o Minor features (geoip):
1809 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
1812 o Minor features (hidden services):
1813 - When re-enabling the network, don't try to build introduction
1814 circuits until we have successfully built a circuit. This makes
1815 hidden services come up faster when the network is re-enabled.
1816 Patch from "akwizgran". Closes ticket 13447.
1817 - When we fail to retrieve a hidden service descriptor, send the
1818 controller an "HS_DESC FAILED" controller event. Implements
1820 - New HiddenServiceDirGroupReadable option to cause hidden service
1821 directories and hostname files to be created group-readable. Patch
1822 from "anon", David Stainton, and "meejah". Closes ticket 11291.
1824 o Minor features (systemd):
1825 - Where supported, when running with systemd, report successful
1826 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
1827 - When running with systemd, support systemd watchdog messages. Part
1828 of ticket 11016. Patch by Michael Scherer.
1830 o Minor features (transparent proxy):
1831 - Update the transparent proxy option checks to allow for both ipfw
1832 and pf on OS X. Closes ticket 14002.
1833 - Use the correct option when using IPv6 with transparent proxy
1834 support on Linux. Resolves 13808. Patch by Francisco Blas
1837 o Minor bugfixes (preventative security, C safety):
1838 - When reading a hexadecimal, base-32, or base-64 encoded value from
1839 a string, always overwrite the whole output buffer. This prevents
1840 some bugs where we would look at (but fortunately, not reveal)
1841 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
1843 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
1844 just the part that's used. This makes it harder for data leak bugs
1845 to occur in the event of other programming failures. Resolves
1848 o Minor bugfixes (client, microdescriptors):
1849 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
1850 computing which microdescriptors to download. This keeps us from
1851 erroneous download behavior if two microdescriptor digests ever
1852 have the same first 160 bits. Fixes part of bug 13399; bugfix
1854 - Reset a router's status if its microdescriptor digest changes,
1855 even if the first 160 bits remain the same. Fixes part of bug
1856 13399; bugfix on 0.2.3.1-alpha.
1858 o Minor bugfixes (compilation):
1859 - Silence clang warnings under --enable-expensive-hardening,
1860 including implicit truncation of 64 bit values to 32 bit, const
1861 char assignment to self, tautological compare, and additional
1862 parentheses around equality tests. Fixes bug 13577; bugfix
1864 - Fix a clang warning about checking whether an address in the
1865 middle of a structure is NULL. Fixes bug 14001; bugfix
1868 o Minor bugfixes (hidden services):
1869 - Correctly send a controller event when we find that a rendezvous
1870 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
1871 - Pre-check directory permissions for new hidden-services to avoid
1872 at least one case of "Bug: Acting on config options left us in a
1873 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
1874 - When adding a new hidden service (for example, via SETCONF), Tor
1875 no longer congratulates the user for running a relay. Fixes bug
1876 13941; bugfix on 0.2.6.1-alpha.
1877 - When fetching hidden service descriptors, we now check not only
1878 for whether we got the hidden service we had in mind, but also
1879 whether we got the particular descriptors we wanted. This prevents
1880 a class of inefficient but annoying DoS attacks by hidden service
1881 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
1884 o Minor bugfixes (Linux seccomp2 sandbox):
1885 - Make transparent proxy support work along with the seccomp2
1886 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
1887 by Francisco Blas Izquierdo Riera.
1888 - Fix a memory leak in tor-resolve when running with the sandbox
1889 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
1891 o Minor bugfixes (logging):
1892 - Downgrade warnings about RSA signature failures to info log level.
1893 Emit a warning when an extra info document is found incompatible
1894 with a corresponding router descriptor. Fixes bug 9812; bugfix
1896 - Make connection_ap_handshake_attach_circuit() log the circuit ID
1897 correctly. Fixes bug 13701; bugfix on 0.0.6.
1899 o Minor bugfixes (misc):
1900 - Stop allowing invalid address patterns like "*/24" that contain
1901 both a wildcard address and a bit prefix length. This affects all
1902 our address-range parsing code. Fixes bug 7484; bugfix
1905 o Minor bugfixes (testing networks, fast startup):
1906 - Allow Tor to build circuits using a consensus with no exits. If
1907 the consensus has no exits (typical of a bootstrapping test
1908 network), allow Tor to build circuits once enough descriptors have
1909 been downloaded. This assists in bootstrapping a testing Tor
1910 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
1912 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
1913 header to directory servers. This allows us to obtain consensuses
1914 promptly when the consensus interval is very short. This assists
1915 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
1916 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
1917 - Stop assuming that private addresses are local when checking
1918 reachability in a TestingTorNetwork. Instead, when testing, assume
1919 all OR connections are remote. (This is necessary due to many test
1920 scenarios running all relays on localhost.) This assists in
1921 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
1922 0.1.0.1-rc. Patch by "teor".
1923 - Avoid building exit circuits from a consensus with no exits. Now
1924 thanks to our fix for 13718, we accept a no-exit network as not
1925 wholly lost, but we need to remember not to try to build exit
1926 circuits on it. Closes ticket 13814; patch by "teor".
1927 - Stop requiring exits to have non-zero bandwithcapacity in a
1928 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
1929 ignore exit bandwidthcapacity. This assists in bootstrapping a
1930 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
1931 on 0.2.0.3-alpha. Patch by "teor".
1932 - Add "internal" to some bootstrap statuses when no exits are
1933 available. If the consensus does not contain Exits, Tor will only
1934 build internal circuits. In this case, relevant statuses will
1935 contain the word "internal" as indicated in the Tor control-
1936 spec.txt. When bootstrap completes, Tor will be ready to build
1937 internal circuits. If a future consensus contains Exits, exit
1938 circuits may become available. Fixes part of bug 13718; bugfix on
1939 0.2.4.10-alpha. Patch by "teor".
1940 - Decrease minimum consensus interval to 10 seconds when
1941 TestingTorNetwork is set, or 5 seconds for the first consensus.
1942 Fix assumptions throughout the code that assume larger intervals.
1943 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
1945 - Avoid excluding guards from path building in minimal test
1946 networks, when we're in a test network and excluding guards would
1947 exclude all relays. This typically occurs in incredibly small tor
1948 networks, and those using "TestingAuthVoteGuard *". Fixes part of
1949 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
1951 o Code simplification and refactoring:
1952 - Stop using can_complete_circuits as a global variable; access it
1953 with a function instead.
1954 - Avoid using operators directly as macro arguments: this lets us
1955 apply coccinelle transformations to our codebase more directly.
1956 Closes ticket 13172.
1957 - Combine the functions used to parse ClientTransportPlugin and
1958 ServerTransportPlugin into a single function. Closes ticket 6456.
1959 - Add inline functions and convenience macros for inspecting channel
1960 state. Refactor the code to use convenience macros instead of
1961 checking channel state directly. Fixes issue 7356.
1962 - Document all members of was_router_added_t and rename
1963 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
1964 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
1965 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
1966 constant instead of hardcoded value. Fixes issue 13840.
1967 - Refactor our generic strmap and digestmap types into a single
1968 implementation, so that we can add a new digest256map
1972 - Document the bridge-authority-only 'networkstatus-bridges' file.
1973 Closes ticket 13713; patch from "tom".
1974 - Fix typo in PredictedPortsRelevanceTime option description in
1975 manpage. Resolves issue 13707.
1976 - Stop suggesting that users specify relays by nickname: it isn't a
1977 good idea. Also, properly cross-reference how to specify relays in
1978 all parts of manual documenting options that take a list of
1979 relays. Closes ticket 13381.
1980 - Clarify the HiddenServiceDir option description in manpage to make
1981 it clear that relative paths are taken with respect to the current
1982 working directory. Also clarify that this behavior is not
1983 guaranteed to remain indefinitely. Fixes issue 13913.
1986 - New tests for many parts of channel, relay, and circuitmux
1987 functionality. Code by Andrea; part of 9262.
1988 - New tests for parse_transport_line(). Part of ticket 6456.
1989 - In the unit tests, use chgrp() to change the group of the unit
1990 test temporary directory to the current user, so that the sticky
1991 bit doesn't interfere with tests that check directory groups.
1993 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
1997 Changes in version 0.2.6.1-alpha - 2014-10-30
1998 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
1999 includes numerous code cleanups and new tests, and fixes a large
2000 number of annoying bugs. Out-of-memory conditions are handled better
2001 than in 0.2.5, pluggable transports have improved proxy support, and
2002 clients now use optimistic data for contacting hidden services. Also,
2003 we are now more robust to changes in what we consider a parseable
2004 directory object, so that tightening restrictions does not have a risk
2005 of introducing infinite download loops.
2007 This is the first alpha release in a new series, so expect there to be
2008 bugs. Users who would rather test out a more stable branch should stay
2009 with 0.2.5.x for now.
2011 o New compiler and system requirements:
2012 - Tor 0.2.6.x requires that your compiler support more of the C99
2013 language standard than before. The 'configure' script now detects
2014 whether your compiler supports C99 mid-block declarations and
2015 designated initializers. If it does not, Tor will not compile.
2017 We may revisit this requirement if it turns out that a significant
2018 number of people need to build Tor with compilers that don't
2019 bother implementing a 15-year-old standard. Closes ticket 13233.
2020 - Tor no longer supports systems without threading support. When we
2021 began working on Tor, there were several systems that didn't have
2022 threads, or where the thread support wasn't able to run the
2023 threads of a single process on multiple CPUs. That no longer
2024 holds: every system where Tor needs to run well now has threading
2025 support. Resolves ticket 12439.
2027 o Removed platform support:
2028 - We no longer include special code to build on Windows CE; as far
2029 as we know, nobody has used Tor on Windows CE in a very long time.
2030 Closes ticket 11446.
2032 o Major features (bridges):
2033 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
2034 transports if they are configured via the "TOR_PT_PROXY"
2035 environment variable. Implements proposal 232. Resolves
2038 o Major features (client performance, hidden services):
2039 - Allow clients to use optimistic data when connecting to a hidden
2040 service, which should remove a round-trip from hidden service
2041 initialization. See proposal 181 for details. Implements
2044 o Major features (directory system):
2045 - Upon receiving an unparseable directory object, if its digest
2046 matches what we expected, then don't try to download it again.
2047 Previously, when we got a descriptor we didn't like, we would keep
2048 trying to download it over and over. Closes ticket 11243.
2050 o Major features (sample torrc):
2051 - Add a new, infrequently-changed "torrc.minimal". This file is
2052 similar to torrc.sample, but it will change as infrequently as
2053 possible, for the benefit of users whose systems prompt them for
2054 intervention whenever a default configuration file is changed.
2055 Making this change allows us to update torrc.sample to be a more
2056 generally useful "sample torrc".
2058 o Major bugfixes (directory authorities):
2059 - Do not assign the HSDir flag to relays if they are not Valid, or
2060 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
2062 o Major bugfixes (directory bandwidth performance):
2063 - Don't flush the zlib buffer aggressively when compressing
2064 directory information for clients. This should save about 7% of
2065 the bandwidth currently used for compressed descriptors and
2066 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
2068 o Minor features (security, memory wiping):
2069 - Ensure we securely wipe keys from memory after
2070 crypto_digest_get_digest and init_curve25519_keypair_from_file
2071 have finished using them. Resolves ticket 13477.
2073 o Minor features (security, out-of-memory handling):
2074 - When handling an out-of-memory condition, allocate less memory for
2075 temporary data structures. Fixes issue 10115.
2076 - When handling an out-of-memory condition, consider more types of
2077 buffers, including those on directory connections, and zlib
2078 buffers. Resolves ticket 11792.
2081 - When identity keypair is generated for first time, log a
2082 congratulatory message that links to the new relay lifecycle
2083 document. Implements feature 10427.
2085 o Minor features (client):
2086 - Clients are now willing to send optimistic data (before they
2087 receive a 'connected' cell) to relays of any version. (Relays
2088 without support for optimistic data are no longer supported on the
2089 Tor network.) Resolves ticket 13153.
2091 o Minor features (directory authorities):
2092 - Don't list relays with a bandwidth estimate of 0 in the consensus.
2093 Implements a feature proposed during discussion of bug 13000.
2094 - In tor-gencert, report an error if the user provides the same
2095 argument more than once.
2096 - If a directory authority can't find a best consensus method in the
2097 votes that it holds, it now falls back to its favorite consensus
2098 method. Previously, it fell back to method 1. Neither of these is
2099 likely to get enough signatures, but "fall back to favorite"
2100 doesn't require us to maintain support an obsolete consensus
2101 method. Implements part of proposal 215.
2103 o Minor features (logging):
2104 - On Unix-like systems, you can now use named pipes as the target of
2105 the Log option, and other options that try to append to files.
2106 Closes ticket 12061. Patch from "carlo von lynX".
2107 - When opening a log file at startup, send it every log message that
2108 we generated between startup and opening it. Previously, log
2109 messages that were generated before opening the log file were only
2110 logged to stdout. Closes ticket 6938.
2111 - Add a TruncateLogFile option to overwrite logs instead of
2112 appending to them. Closes ticket 5583.
2114 o Minor features (portability, Solaris):
2115 - Threads are no longer disabled by default on Solaris; we believe
2116 that the versions of Solaris with broken threading support are all
2117 obsolete by now. Resolves ticket 9495.
2119 o Minor features (relay):
2120 - Re-check our address after we detect a changed IP address from
2121 getsockname(). This ensures that the controller command "GETINFO
2122 address" will report the correct value. Resolves ticket 11582.
2124 - A new AccountingRule option lets Relays set whether they'd like
2125 AccountingMax to be applied separately to inbound and outbound
2126 traffic, or applied to the sum of inbound and outbound traffic.
2127 Resolves ticket 961. Patch by "chobe".
2129 o Minor features (testing networks):
2130 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
2131 the "Exit" flag regardless of their uptime, bandwidth, or exit
2132 policy. TestingTorNetwork must be set for this option to have any
2133 effect. Previously, authorities would take up to 35 minutes to
2134 give nodes the Exit flag in a test network. Partially implements
2137 o Minor features (validation):
2138 - Check all date/time values passed to tor_timegm and
2139 parse_rfc1123_time for validity, taking leap years into account.
2140 Improves HTTP header validation. Implemented with bug 13476.
2141 - In correct_tm(), limit the range of values returned by system
2142 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
2143 This means we don't have to deal with negative or too large dates,
2144 even if a clock is wrong. Otherwise we might fail to read a file
2145 written by us which includes such a date. Fixes bug 13476.
2147 o Minor bugfixes (bridge clients):
2148 - When configured to use a bridge without an identity digest (not
2149 recommended), avoid launching an extra channel to it when
2150 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
2152 o Minor bugfixes (bridges):
2153 - When DisableNetwork is set, do not launch pluggable transport
2154 plugins, and if any are running, terminate them. Fixes bug 13213;
2155 bugfix on 0.2.3.6-alpha.
2157 o Minor bugfixes (C correctness):
2158 - Fix several instances of possible integer overflow/underflow/NaN.
2159 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
2161 - In circuit_build_times_calculate_timeout() in circuitstats.c,
2162 avoid dividing by zero in the pareto calculations. This traps
2163 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
2165 - Fix an integer overflow in format_time_interval(). Fixes bug
2166 13393; bugfix on 0.2.0.10-alpha.
2167 - Set the correct day of year value when the system's localtime(_r)
2168 or gmtime(_r) functions fail to set struct tm. Not externally
2169 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
2170 - Avoid unlikely signed integer overflow in tor_timegm on systems
2171 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
2173 o Minor bugfixes (client):
2174 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
2175 BadExit flag are not considered worthy candidates. Fixes bug
2176 13066; bugfix on 0.1.2.3-alpha.
2177 - Use the consensus schedule for downloading consensuses, and not
2178 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
2179 - Handle unsupported or malformed SOCKS5 requests properly by
2180 responding with the appropriate error message before closing the
2181 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
2183 o Minor bugfixes (client, torrc):
2184 - Stop modifying the value of our DirReqStatistics torrc option just
2185 because we're not a bridge or relay. This bug was causing Tor
2186 Browser users to write "DirReqStatistics 0" in their torrc files
2187 as if they had chosen to change the config. Fixes bug 4244; bugfix
2189 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
2190 that our options have changed every time we SIGHUP. Fixes bug
2191 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
2193 o Minor bugfixes (controller):
2194 - Return an error when the second or later arguments of the
2195 "setevents" controller command are invalid events. Previously we
2196 would return success while silently skipping invalid events. Fixes
2197 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
2199 o Minor bugfixes (directory system):
2200 - Always believe that v3 directory authorities serve extra-info
2201 documents, whether they advertise "caches-extra-info" or not.
2202 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
2203 - When running as a v3 directory authority, advertise that you serve
2204 extra-info documents so that clients who want them can find them
2205 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
2206 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
2207 Previously, directories offering BRIDGE_DIRINFO and some other
2208 flag (i.e. microdescriptors or extrainfo) would be ignored when
2209 looking for bridges. Partially fixes bug 13163; bugfix
2212 o Minor bugfixes (networking):
2213 - Check for orconns and use connection_or_close_for_error() rather
2214 than connection_mark_for_close() directly in the getsockopt()
2215 failure case of connection_handle_write_impl(). Fixes bug 11302;
2216 bugfix on 0.2.4.4-alpha.
2218 o Minor bugfixes (relay):
2219 - When generating our family list, remove spaces from around the
2220 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
2221 - If our previous bandwidth estimate was 0 bytes, allow publishing a
2222 new relay descriptor immediately. Fixes bug 13000; bugfix
2225 o Minor bugfixes (testing networks):
2226 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
2227 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
2228 - Stop using the default authorities in networks which provide both
2229 AlternateDirAuthority and AlternateBridgeAuthority. Partially
2230 fixes bug 13163; bugfix on 0.2.0.13-alpha.
2232 o Minor bugfixes (testing):
2233 - Stop spawn test failures due to a race condition between the
2234 SIGCHLD handler updating the process status, and the test reading
2235 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
2237 o Minor bugfixes (testing, Windows):
2238 - Avoid passing an extra backslash when creating a temporary
2239 directory for running the unit tests on Windows. Fixes bug 12392;
2240 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
2242 o Minor bugfixes (windows):
2243 - Remove code to special-case handling of NTE_BAD_KEYSET when
2244 acquiring windows CryptoAPI context. This error can't actually
2245 occur for the parameters we're providing. Fixes bug 10816; bugfix
2248 o Minor bugfixes (zlib):
2249 - Avoid truncating a zlib stream when trying to finalize it with an
2250 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
2253 - Allow our configure script to build correctly with autoconf 2.62
2254 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
2255 - Improve the error message from ./configure to make it clear that
2256 when asciidoc has not been found, the user will have to either add
2257 --disable-asciidoc argument or install asciidoc. Resolves
2260 o Code simplification and refactoring:
2261 - Change the entry_is_live() function to take named bitfield
2262 elements instead of an unnamed list of booleans. Closes
2264 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
2265 Resolves ticket 12205.
2266 - Use calloc and reallocarray functions instead of multiply-
2267 then-malloc. This makes it less likely for us to fall victim to an
2268 integer overflow attack when allocating. Resolves ticket 12855.
2269 - Use the standard macro name SIZE_MAX, instead of our
2271 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
2272 functions which take them as arguments. Replace 0 with NO_DIRINFO
2273 in a function call for clarity. Seeks to prevent future issues
2275 - Avoid 4 null pointer errors under clang static analysis by using
2276 tor_assert() to prove that the pointers aren't null. Fixes
2278 - Rework the API of policies_parse_exit_policy() to use a bitmask to
2279 represent parsing options, instead of a confusing mess of
2280 booleans. Resolves ticket 8197.
2281 - Introduce a helper function to parse ExitPolicy in
2282 or_options_t structure.
2285 - Add a doc/TUNING document with tips for handling large numbers of
2286 TCP connections when running busy Tor relay. Update the warning
2287 message to point to this file when running out of sockets
2288 operating system is allowing to use simultaneously. Resolves
2292 - We no longer remind the user about configuration options that have
2293 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
2294 - Remove our old, non-weighted bandwidth-based node selection code.
2295 Previously, we used it as a fallback when we couldn't perform
2296 weighted bandwidth-based node selection. But that would only
2297 happen in the cases where we had no consensus, or when we had a
2298 consensus generated by buggy or ancient directory authorities. In
2299 either case, it's better to use the more modern, better maintained
2300 algorithm, with reasonable defaults for the weights. Closes
2302 - Remove the --disable-curve25519 configure option. Relays and
2303 clients now are required to support curve25519 and the
2305 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
2306 used to be deprecated synonyms for "StrictNodes", are now marked
2307 obsolete. Resolves ticket 12226.
2308 - Clients don't understand the BadDirectory flag in the consensus
2309 anymore, and ignore it.
2312 - Refactor the function that chooses guard nodes so that it can more
2313 easily be tested; write some tests for it.
2314 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
2315 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
2316 - Create unit tests for format_time_interval(). With bug 13393.
2317 - Add unit tests for tor_timegm signed overflow, tor_timegm and
2318 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
2319 tests (visible) fixes in bug 13476.
2320 - Add a "coverage-html" make target to generate HTML-visualized
2321 coverage results when building with --enable-coverage. (Requires
2322 lcov.) Patch from Kevin Murray.
2323 - Enable the backtrace handler (where supported) when running the
2325 - Revise all unit tests that used the legacy test_* macros to
2326 instead use the recommended tt_* macros. This patch was generated
2327 with coccinelle, to avoid manual errors. Closes ticket 13119.
2329 o Distribution (systemd):
2330 - systemd unit file: only allow tor to write to /var/lib/tor and
2331 /var/log/tor. The rest of the filesystem is accessible for reading
2332 only. Patch by intrigeri; resolves ticket 12751.
2333 - systemd unit file: ensure that the process and all its children
2334 can never gain new privileges. Patch by intrigeri; resolves
2336 - systemd unit file: set up /var/run/tor as writable for the Tor
2337 service. Patch by intrigeri; resolves ticket 13196.
2339 o Removed features (directory authorities):
2340 - Remove code that prevented authorities from listing Tor relays
2341 affected by CVE-2011-2769 as guards. These relays are already
2342 rejected altogether due to the minimum version requirement of
2343 0.2.3.16-alpha. Closes ticket 13152.
2344 - The "AuthDirRejectUnlisted" option no longer has any effect, as
2345 the fingerprints file (approved-routers) has been deprecated.
2346 - Directory authorities do not support being Naming dirauths anymore.
2347 The "NamingAuthoritativeDir" config option is now obsolete.
2348 - Directory authorities do not support giving out the BadDirectory
2350 - Directory authorities no longer advertise or support consensus
2351 methods 1 through 12 inclusive. These consensus methods were
2352 obsolete and/or insecure: maintaining the ability to support them
2353 served no good purpose. Implements part of proposal 215; closes
2356 o Testing (test-network.sh):
2357 - Stop using "echo -n", as some shells' built-in echo doesn't
2358 support "-n". Instead, use "/bin/echo -n". Partially fixes
2360 - Stop an apparent test-network hang when used with make -j2. Fixes
2362 - Add a --delay option to test-network.sh, which configures the
2363 delay before the chutney network tests for data transmission.
2364 Partially implements ticket 13161.
2367 Changes in version 0.2.5.10 - 2014-10-24
2368 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
2370 It adds several new security features, including improved
2371 denial-of-service resistance for relays, new compiler hardening
2372 options, and a system-call sandbox for hardened installations on Linux
2373 (requires seccomp2). The controller protocol has several new features,
2374 resolving IPv6 addresses should work better than before, and relays
2375 should be a little more CPU-efficient. We've added support for more
2376 OpenBSD and FreeBSD transparent proxy types. We've improved the build
2377 system and testing infrastructure to allow unit testing of more parts
2378 of the Tor codebase. Finally, we've addressed several nagging pluggable
2379 transport usability issues, and included numerous other small bugfixes
2380 and features mentioned below.
2382 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
2383 have accumulated many known flaws; everyone should upgrade.
2385 o Deprecated versions:
2386 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
2387 attention for some while.
2390 Changes in version 0.2.5.9-rc - 2014-10-20
2391 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
2392 series. It disables SSL3 in response to the recent "POODLE" attack
2393 (even though POODLE does not affect Tor). It also works around a crash
2394 bug caused by some operating systems' response to the "POODLE" attack
2395 (which does affect Tor). It also contains a few miscellaneous fixes.
2397 o Major security fixes:
2398 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
2399 today support TLS 1.0 or later, so we can safely turn off support
2400 for this old (and insecure) protocol. Fixes bug 13426.
2402 o Major bugfixes (openssl bug workaround):
2403 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
2404 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
2405 13471. This is a workaround for an OpenSSL bug.
2408 - Disable the sandbox name resolver cache when running tor-resolve:
2409 tor-resolve doesn't use the sandbox code, and turning it on was
2410 breaking attempts to do tor-resolve on a non-default server on
2411 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
2413 o Compilation fixes:
2414 - Build and run correctly on systems like OpenBSD-current that have
2415 patched OpenSSL to remove get_cipher_by_char and/or its
2416 implementations. Fixes issue 13325.
2418 o Downgraded warnings:
2419 - Downgrade the severity of the 'unexpected sendme cell from client'
2420 from 'warn' to 'protocol warning'. Closes ticket 8093.
2423 Changes in version 0.2.4.25 - 2014-10-20
2424 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
2425 (even though POODLE does not affect Tor). It also works around a crash
2426 bug caused by some operating systems' response to the "POODLE" attack
2427 (which does affect Tor).
2429 o Major security fixes (also in 0.2.5.9-rc):
2430 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
2431 today support TLS 1.0 or later, so we can safely turn off support
2432 for this old (and insecure) protocol. Fixes bug 13426.
2434 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
2435 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
2436 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
2437 13471. This is a workaround for an OpenSSL bug.
2440 Changes in version 0.2.5.8-rc - 2014-09-22
2441 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
2442 series. It fixes a bug that affects consistency and speed when
2443 connecting to hidden services, and it updates the location of one of
2444 the directory authorities.
2447 - Clients now send the correct address for their chosen rendezvous
2448 point when trying to access a hidden service. They used to send
2449 the wrong address, which would still work some of the time because
2450 they also sent the identity digest of the rendezvous point, and if
2451 the hidden service happened to try connecting to the rendezvous
2452 point from a relay that already had a connection open to it,
2453 the relay would reuse that connection. Now connections to hidden
2454 services should be more robust and faster. Also, this bug meant
2455 that clients were leaking to the hidden service whether they were
2456 on a little-endian (common) or big-endian (rare) system, which for
2457 some users might have reduced their anonymity. Fixes bug 13151;
2458 bugfix on 0.2.1.5-alpha.
2460 o Directory authority changes:
2461 - Change IP address for gabelmoo (v3 directory authority).
2464 Changes in version 0.2.4.24 - 2014-09-22
2465 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
2466 connecting to hidden services, and it updates the location of one of
2467 the directory authorities.
2470 - Clients now send the correct address for their chosen rendezvous
2471 point when trying to access a hidden service. They used to send
2472 the wrong address, which would still work some of the time because
2473 they also sent the identity digest of the rendezvous point, and if
2474 the hidden service happened to try connecting to the rendezvous
2475 point from a relay that already had a connection open to it,
2476 the relay would reuse that connection. Now connections to hidden
2477 services should be more robust and faster. Also, this bug meant
2478 that clients were leaking to the hidden service whether they were
2479 on a little-endian (common) or big-endian (rare) system, which for
2480 some users might have reduced their anonymity. Fixes bug 13151;
2481 bugfix on 0.2.1.5-alpha.
2483 o Directory authority changes:
2484 - Change IP address for gabelmoo (v3 directory authority).
2486 o Minor features (geoip):
2487 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
2491 Changes in version 0.2.5.7-rc - 2014-09-11
2492 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
2493 release series, and some long-standing bugs related to ORPort reachability
2494 testing and failure to send CREATE cells. It is the first release
2495 candidate for the Tor 0.2.5.x series.
2497 o Major bugfixes (client, startup):
2498 - Start making circuits as soon as DisabledNetwork is turned off.
2499 When Tor started with DisabledNetwork set, it would correctly
2500 conclude that it shouldn't build circuits, but it would mistakenly
2501 cache this conclusion, and continue believing it even when
2502 DisableNetwork is set to 0. Fixes the bug introduced by the fix
2503 for bug 11200; bugfix on 0.2.5.4-alpha.
2504 - Resume expanding abbreviations for command-line options. The fix
2505 for bug 4647 accidentally removed our hack from bug 586 that
2506 rewrote HashedControlPassword to __HashedControlSessionPassword
2507 when it appears on the commandline (which allowed the user to set
2508 her own HashedControlPassword in the torrc file while the
2509 controller generates a fresh session password for each run). Fixes
2510 bug 12948; bugfix on 0.2.5.1-alpha.
2511 - Warn about attempts to run hidden services and relays in the same
2512 process: that's probably not a good idea. Closes ticket 12908.
2514 o Major bugfixes (relay):
2515 - Avoid queuing or sending destroy cells for circuit ID zero when we
2516 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
2517 Found and fixed by "cypherpunks".
2518 - Fix ORPort reachability detection on relays running behind a
2519 proxy, by correctly updating the "local" mark on the controlling
2520 channel when changing the address of an or_connection_t after the
2521 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
2523 o Minor features (bridge):
2524 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
2525 cookie file for the ExtORPort g+r by default.
2527 o Minor features (geoip):
2528 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
2531 o Minor bugfixes (logging):
2532 - Reduce the log severity of the "Pluggable transport proxy does not
2533 provide any needed transports and will not be launched." message,
2534 since Tor Browser includes several ClientTransportPlugin lines in
2535 its torrc-defaults file, leading every Tor Browser user who looks
2536 at her logs to see these notices and wonder if they're dangerous.
2537 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
2538 - Downgrade "Unexpected onionskin length after decryption" warning
2539 to a protocol-warn, since there's nothing relay operators can do
2540 about a client that sends them a malformed create cell. Resolves
2541 bug 12996; bugfix on 0.0.6rc1.
2542 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
2543 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
2544 - When logging information about an EXTEND2 or EXTENDED2 cell, log
2545 their names correctly. Fixes part of bug 12700; bugfix
2547 - When logging information about a relay cell whose command we don't
2548 recognize, log its command as an integer. Fixes part of bug 12700;
2549 bugfix on 0.2.1.10-alpha.
2550 - Escape all strings from the directory connection before logging
2551 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
2553 o Minor bugfixes (controller):
2554 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
2555 bug 12864; bugfix on 0.2.5.1-alpha.
2556 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
2557 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
2560 o Minor bugfixes (compilation):
2561 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
2562 bugfix on 0.2.5.5-alpha.
2563 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
2564 0.2.5.1-alpha. Patch from "NewEraCracker".
2565 - In routerlist_assert_ok(), don't take the address of a
2566 routerinfo's cache_info member unless that routerinfo is non-NULL.
2567 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
2568 - Fix a large number of false positive warnings from the clang
2569 analyzer static analysis tool. This should make real warnings
2570 easier for clang analyzer to find. Patch from "teor". Closes
2573 o Distribution (systemd):
2574 - Verify configuration file via ExecStartPre in the systemd unit
2575 file. Patch from intrigeri; resolves ticket 12730.
2576 - Explicitly disable RunAsDaemon in the systemd unit file. Our
2577 current systemd unit uses "Type = simple", so systemd does not
2578 expect tor to fork. If the user has "RunAsDaemon 1" in their
2579 torrc, then things won't work as expected. This is e.g. the case
2580 on Debian (and derivatives), since there we pass "--defaults-torrc
2581 /usr/share/tor/tor-service-defaults-torrc" (that contains
2582 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
2586 - Adjust the URLs in the README to refer to the new locations of
2587 several documents on the website. Fixes bug 12830. Patch from
2589 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
2593 Changes in version 0.2.5.6-alpha - 2014-07-28
2594 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
2595 risk from guard rotation, and fixes a variety of other issues to get
2596 us closer to a release candidate.
2598 o Major features (also in 0.2.4.23):
2599 - Make the number of entry guards configurable via a new
2600 NumEntryGuards consensus parameter, and the number of directory
2601 guards configurable via a new NumDirectoryGuards consensus
2602 parameter. Implements ticket 12688.
2604 o Major bugfixes (also in 0.2.4.23):
2605 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
2606 implementation that caused incorrect results on 32-bit
2607 implementations when certain malformed inputs were used along with
2608 a small class of private ntor keys. This bug does not currently
2609 appear to allow an attacker to learn private keys or impersonate a
2610 Tor server, but it could provide a means to distinguish 32-bit Tor
2611 implementations from 64-bit Tor implementations. Fixes bug 12694;
2612 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
2616 - Perform circuit cleanup operations even when circuit
2617 construction operations are disabled (because the network is
2618 disabled, or because there isn't enough directory information).
2619 Previously, when we were not building predictive circuits, we
2620 were not closing expired circuits either. Fixes bug 8387; bugfix on
2621 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
2622 became more strict about when we have "enough directory information
2626 - Authorities now assign the Guard flag to the fastest 25% of the
2627 network (it used to be the fastest 50%). Also raise the consensus
2628 weight that guarantees the Guard flag from 250 to 2000. For the
2629 current network, this results in about 1100 guards, down from 2500.
2630 This step paves the way for moving the number of entry guards
2631 down to 1 (proposal 236) while still providing reasonable expected
2632 performance for most users. Implements ticket 12690.
2633 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
2635 - Slightly enhance the diagnostic message for bug 12184.
2637 o Minor bugfixes (also in 0.2.4.23):
2638 - Warn and drop the circuit if we receive an inbound 'relay early'
2639 cell. Those used to be normal to receive on hidden service circuits
2640 due to bug 1038, but the buggy Tor versions are long gone from
2641 the network so we can afford to resume watching for them. Resolves
2642 the rest of bug 1038; bugfix on 0.2.1.19.
2643 - Correct a confusing error message when trying to extend a circuit
2644 via the control protocol but we don't know a descriptor or
2645 microdescriptor for one of the specified relays. Fixes bug 12718;
2646 bugfix on 0.2.3.1-alpha.
2649 - Fix compilation when building with bufferevents enabled. (This
2650 configuration is still not expected to work, however.)
2651 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
2652 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
2654 - Compile correctly with builds and forks of OpenSSL (such as
2655 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
2656 0.2.1.1-alpha. Patch from "dhill".
2659 Changes in version 0.2.4.23 - 2014-07-28
2660 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
2661 guard rotation, and also backports several important fixes from the
2662 Tor 0.2.5 alpha release series.
2665 - Clients now look at the "usecreatefast" consensus parameter to
2666 decide whether to use CREATE_FAST or CREATE cells for the first hop
2667 of their circuit. This approach can improve security on connections
2668 where Tor's circuit handshake is stronger than the available TLS
2669 connection security levels, but the tradeoff is more computational
2670 load on guard relays. Implements proposal 221. Resolves ticket 9386.
2671 - Make the number of entry guards configurable via a new
2672 NumEntryGuards consensus parameter, and the number of directory
2673 guards configurable via a new NumDirectoryGuards consensus
2674 parameter. Implements ticket 12688.
2677 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
2678 implementation that caused incorrect results on 32-bit
2679 implementations when certain malformed inputs were used along with
2680 a small class of private ntor keys. This bug does not currently
2681 appear to allow an attacker to learn private keys or impersonate a
2682 Tor server, but it could provide a means to distinguish 32-bit Tor
2683 implementations from 64-bit Tor implementations. Fixes bug 12694;
2684 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
2688 - Warn and drop the circuit if we receive an inbound 'relay early'
2689 cell. Those used to be normal to receive on hidden service circuits
2690 due to bug 1038, but the buggy Tor versions are long gone from
2691 the network so we can afford to resume watching for them. Resolves
2692 the rest of bug 1038; bugfix on 0.2.1.19.
2693 - Correct a confusing error message when trying to extend a circuit
2694 via the control protocol but we don't know a descriptor or
2695 microdescriptor for one of the specified relays. Fixes bug 12718;
2696 bugfix on 0.2.3.1-alpha.
2697 - Avoid an illegal read from stack when initializing the TLS
2698 module using a version of OpenSSL without all of the ciphers
2699 used by the v2 link handshake. Fixes bug 12227; bugfix on
2700 0.2.4.8-alpha. Found by "starlight".
2703 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
2707 Changes in version 0.2.5.5-alpha - 2014-06-18
2708 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
2709 0.2.5.x release series, including a couple of DoS issues, some
2710 performance regressions, a large number of bugs affecting the Linux
2711 seccomp2 sandbox code, and various other bugfixes. It also adds
2712 diagnostic bugfixes for a few tricky issues that we're trying to
2715 o Major features (security, traffic analysis resistance):
2716 - Several major improvements to the algorithm used to decide when to
2717 close TLS connections. Previous versions of Tor closed connections
2718 at a fixed interval after the last time a non-padding cell was
2719 sent over the connection, regardless of the target of the
2720 connection. Now, we randomize the intervals by adding up to 50% of
2721 their base value, we measure the length of time since connection
2722 last had at least one circuit, and we allow connections to known
2723 ORs to remain open a little longer (15 minutes instead of 3
2724 minutes minimum). These changes should improve Tor's resistance
2725 against some kinds of traffic analysis, and lower some overhead
2726 from needlessly closed connections. Fixes ticket 6799.
2727 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
2729 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
2730 - Fix a memory leak that could occur if a microdescriptor parse
2731 fails during the tokenizing step. This bug could enable a memory
2732 exhaustion attack by directory servers. Fixes bug 11649; bugfix
2735 o Major bugfixes (security, directory authorities):
2736 - Directory authorities now include a digest of each relay's
2737 identity key as a part of its microdescriptor.
2739 This is a workaround for bug 11743 (reported by "cypherpunks"),
2740 where Tor clients do not support receiving multiple
2741 microdescriptors with the same SHA256 digest in the same
2742 consensus. When clients receive a consensus like this, they only
2743 use one of the relays. Without this fix, a hostile relay could
2744 selectively disable some client use of target relays by
2745 constructing a router descriptor with a different identity and the
2746 same microdescriptor parameters and getting the authorities to
2747 list it in a microdescriptor consensus. This fix prevents an
2748 attacker from causing a microdescriptor collision, because the
2749 router's identity is not forgeable.
2751 o Major bugfixes (relay):
2752 - Use a direct dirport connection when uploading non-anonymous
2753 descriptors to the directory authorities. Previously, relays would
2754 incorrectly use tunnel connections under a fairly wide variety of
2755 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
2756 - When a circuit accidentally has the same circuit ID for its
2757 forward and reverse direction, correctly detect the direction of
2758 cells using that circuit. Previously, this bug made roughly one
2759 circuit in a million non-functional. Fixes bug 12195; this is a
2760 bugfix on every version of Tor.
2762 o Major bugfixes (client, pluggable transports):
2763 - When managing pluggable transports, use OS notification facilities
2764 to learn if they have crashed, and don't attempt to kill any
2765 process that has already exited. Fixes bug 8746; bugfix
2768 o Minor features (diagnostic):
2769 - When logging a warning because of bug 7164, additionally check the
2770 hash table for consistency (as proposed on ticket 11737). This may
2771 help diagnose bug 7164.
2772 - When we log a heartbeat, log how many one-hop circuits we have
2773 that are at least 30 minutes old, and log status information about
2774 a few of them. This is an attempt to track down bug 8387.
2775 - When encountering an unexpected CR while writing text to a file on
2776 Windows, log the name of the file. Should help diagnosing
2778 - Give more specific warnings when a client notices that an onion
2779 handshake has failed. Fixes ticket 9635.
2780 - Add significant new logging code to attempt to diagnose bug 12184,
2781 where relays seem to run out of available circuit IDs.
2782 - Improve the diagnostic log message for bug 8387 even further to
2783 try to improve our odds of figuring out why one-hop directory
2784 circuits sometimes do not get closed.
2786 o Minor features (security, memory management):
2787 - Memory allocation tricks (mempools and buffer freelists) are now
2788 disabled by default. You can turn them back on with
2789 --enable-mempools and --enable-buf-freelists respectively. We're
2790 disabling these features because malloc performance is good enough
2791 on most platforms, and a similar feature in OpenSSL exacerbated
2792 exploitation of the Heartbleed attack. Resolves ticket 11476.
2794 o Minor features (security):
2795 - Apply the secure SipHash-2-4 function to the hash table mapping
2796 circuit IDs and channels to circuits. We missed this one when we
2797 were converting all the other hash functions to use SipHash back
2798 in 0.2.5.3-alpha. Resolves ticket 11750.
2800 o Minor features (build):
2801 - The configure script has a --disable-seccomp option to turn off
2802 support for libseccomp on systems that have it, in case it (or
2803 Tor's use of it) is broken. Resolves ticket 11628.
2805 o Minor features (other):
2806 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
2809 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
2810 - When running a hidden service, do not allow TunneledDirConns 0;
2811 this will keep the hidden service from running, and also
2812 make it publish its descriptors directly over HTTP. Fixes bug 10849;
2813 bugfix on 0.2.1.1-alpha.
2815 o Minor bugfixes (performance):
2816 - Avoid a bug where every successful connection made us recompute
2817 the flag telling us whether we have sufficient information to
2818 build circuits. Previously, we would forget our cached value
2819 whenever we successfully opened a channel (or marked a router as
2820 running or not running for any other reason), regardless of
2821 whether we had previously believed the router to be running. This
2822 forced us to run an expensive update operation far too often.
2823 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
2824 - Avoid using tor_memeq() for checking relay cell integrity. This
2825 removes a possible performance bottleneck. Fixes part of bug
2826 12169; bugfix on 0.2.1.31.
2828 o Minor bugfixes (compilation):
2829 - Fix compilation of test_status.c when building with MVSC. Bugfix
2830 on 0.2.5.4-alpha. Patch from Gisle Vanem.
2831 - Resolve GCC complaints on OpenBSD about discarding constness in
2832 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
2833 on 0.1.1.23. Patch from Dana Koch.
2834 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
2835 treatment of long and time_t as comparable types. Fixes part of
2836 bug 11633. Patch from Dana Koch.
2837 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
2838 11623; bugfix on 0.2.5.3-alpha.
2839 - When deciding whether to build the 64-bit curve25519
2840 implementation, detect platforms where we can compile 128-bit
2841 arithmetic but cannot link it. Fixes bug 11729; bugfix on
2842 0.2.4.8-alpha. Patch from "conradev".
2843 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
2844 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
2845 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
2848 o Minor bugfixes (Directory server):
2849 - When sending a compressed set of descriptors or microdescriptors,
2850 make sure to finalize the zlib stream. Previously, we would write
2851 all the compressed data, but if the last descriptor we wanted to
2852 send was missing or too old, we would not mark the stream as
2853 finished. This caused problems for decompression tools. Fixes bug
2854 11648; bugfix on 0.1.1.23.
2856 o Minor bugfixes (Linux seccomp sandbox):
2857 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
2858 11622; bugfix on 0.2.5.1-alpha.
2859 - Avoid crashing when re-opening listener ports with the seccomp
2860 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
2861 - Avoid crashing with the seccomp sandbox enabled along with
2862 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
2863 - When we receive a SIGHUP with the sandbox enabled, correctly
2864 support rotating our log files. Fixes bug 12032; bugfix
2866 - Avoid crash when running with sandboxing enabled and
2867 DirReqStatistics not disabled. Fixes bug 12035; bugfix
2869 - Fix a "BUG" warning when trying to write bridge-stats files with
2870 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
2872 - Prevent the sandbox from crashing on startup when run with the
2873 --enable-expensive-hardening configuration option. Fixes bug
2874 11477; bugfix on 0.2.5.4-alpha.
2875 - When running with DirPortFrontPage and sandboxing both enabled,
2876 reload the DirPortFrontPage correctly when restarting. Fixes bug
2877 12028; bugfix on 0.2.5.1-alpha.
2878 - Don't try to enable the sandbox when using the Tor binary to check
2879 its configuration, hash a passphrase, or so on. Doing so was
2880 crashing on startup for some users. Fixes bug 11609; bugfix
2882 - Avoid warnings when running with sandboxing and node statistics
2883 enabled at the same time. Fixes part of 12064; bugfix on
2884 0.2.5.1-alpha. Patch from Michael Wolf.
2885 - Avoid warnings when running with sandboxing enabled at the same
2886 time as cookie authentication, hidden services, or directory
2887 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
2888 - Do not allow options that require calls to exec to be enabled
2889 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
2890 bug 12043; bugfix on 0.2.5.1-alpha.
2891 - Handle failures in getpwnam()/getpwuid() when running with the
2892 User option set and the Linux syscall sandbox enabled. Fixes bug
2893 11946; bugfix on 0.2.5.1-alpha.
2894 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
2895 to avoid calling getaddrinfo() after installing the sandbox
2896 filters. Previously, it preloaded a cache with the IPv4 address
2897 for our hostname, and nothing else. Now, it loads the cache with
2898 every address that it used to initialize the Tor process. Fixes
2899 bug 11970; bugfix on 0.2.5.1-alpha.
2901 o Minor bugfixes (pluggable transports):
2902 - Enable the ExtORPortCookieAuthFile option, to allow changing the
2903 default location of the authentication token for the extended OR
2904 Port as used by sever-side pluggable transports. We had
2905 implemented this option before, but the code to make it settable
2906 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
2907 - Avoid another 60-second delay when starting Tor in a pluggable-
2908 transport-using configuration when we already have cached
2909 descriptors for our bridges. Fixes bug 11965; bugfix
2912 o Minor bugfixes (client):
2913 - Avoid "Tried to open a socket with DisableNetwork set" warnings
2914 when starting a client with bridges configured and DisableNetwork
2915 set. (Tor launcher starts Tor with DisableNetwork set the first
2916 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
2918 o Minor bugfixes (testing):
2919 - The Python parts of the test scripts now work on Python 3 as well
2920 as Python 2, so systems where '/usr/bin/python' is Python 3 will
2921 no longer have the tests break. Fixes bug 11608; bugfix
2923 - When looking for versions of python that we could run the tests
2924 with, check for "python2.7" and "python3.3"; previously we were
2925 only looking for "python", "python2", and "python3". Patch from
2926 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
2927 - Fix all valgrind warnings produced by the unit tests. There were
2928 over a thousand memory leak warnings previously, mostly produced
2929 by forgetting to free things in the unit test code. Fixes bug
2930 11618, bugfixes on many versions of Tor.
2932 o Minor bugfixes (tor-fw-helper):
2933 - Give a correct log message when tor-fw-helper fails to launch.
2934 (Previously, we would say something like "tor-fw-helper sent us a
2935 string we could not parse".) Fixes bug 9781; bugfix
2938 o Minor bugfixes (relay, threading):
2939 - Check return code on spawn_func() in cpuworker code, so that we
2940 don't think we've spawned a nonworking cpuworker and write junk to
2941 it forever. Fix related to bug 4345; bugfix on all released Tor
2942 versions. Found by "skruffy".
2943 - Use a pthread_attr to make sure that spawn_func() cannot return an
2944 error while at the same time launching a thread. Fix related to
2945 bug 4345; bugfix on all released Tor versions. Reported
2948 o Minor bugfixes (relay, oom prevention):
2949 - Correctly detect the total available system memory. We tried to do
2950 this in 0.2.5.4-alpha, but the code was set up to always return an
2951 error value, even on success. Fixes bug 11805; bugfix
2954 o Minor bugfixes (relay, other):
2955 - We now drop CREATE cells for already-existent circuit IDs and for
2956 zero-valued circuit IDs, regardless of other factors that might
2957 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
2959 - Avoid an illegal read from stack when initializing the TLS module
2960 using a version of OpenSSL without all of the ciphers used by the
2961 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
2963 - When rejecting DATA cells for stream_id zero, still count them
2964 against the circuit's deliver window so that we don't fail to send
2965 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
2967 o Minor bugfixes (logging):
2968 - Fix a misformatted log message about delayed directory fetches.
2969 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
2970 - Squelch a spurious LD_BUG message "No origin circuit for
2971 successful SOCKS stream" in certain hidden service failure cases;
2975 - Include a tor.service file in contrib/dist for use with systemd.
2976 Some distributions will be able to use this file unmodified;
2977 others will need to tweak it, or write their own. Patch from Jamie
2978 Nguyen; resolves ticket 8368.
2981 - Clean up several option names in the manpage to match their real
2982 names, add the missing documentation for a couple of testing and
2983 directory authority options, remove the documentation for a
2984 V2-directory fetching option that no longer exists. Resolves
2986 - Correct the documenation so that it lists the correct directory
2987 for the stats files. (They are in a subdirectory called "stats",
2989 - In the manpage, move more authority-only options into the
2990 directory authority section so that operators of regular directory
2991 caches don't get confused.
2994 - The contrib directory has been sorted and tidied. Before, it was
2995 an unsorted dumping ground for useful and not-so-useful things.
2996 Now, it is divided based on functionality, and the items which
2997 seemed to be nonfunctional or useless have been removed. Resolves
2998 ticket 8966; based on patches from "rl1987".
3001 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
3002 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
3003 - The TunnelDirConns and PreferTunnelledDirConns options no longer
3004 exist; tunneled directory connections have been available since
3005 0.1.2.5-alpha, and turning them off is not a good idea. This is a
3006 brute-force fix for 10849, where "TunnelDirConns 0" would break
3010 Changes in version 0.2.4.22 - 2014-05-16
3011 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
3012 alpha release series. These include blocking all authority signing
3013 keys that may have been affected by the OpenSSL "heartbleed" bug,
3014 choosing a far more secure set of TLS ciphersuites by default, closing
3015 a couple of memory leaks that could be used to run a target relay out
3016 of RAM, and several others.
3018 o Major features (security, backport from 0.2.5.4-alpha):
3019 - Block authority signing keys that were used on authorities
3020 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
3021 don't have any evidence that these keys _were_ compromised; we're
3022 doing this to be prudent.) Resolves ticket 11464.
3024 o Major bugfixes (security, OOM):
3025 - Fix a memory leak that could occur if a microdescriptor parse
3026 fails during the tokenizing step. This bug could enable a memory
3027 exhaustion attack by directory servers. Fixes bug 11649; bugfix
3030 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
3031 - The relay ciphersuite list is now generated automatically based on
3032 uniform criteria, and includes all OpenSSL ciphersuites with
3033 acceptable strength and forward secrecy. Previously, we had left
3034 some perfectly fine ciphersuites unsupported due to omission or
3035 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
3036 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
3037 - Relays now trust themselves to have a better view than clients of
3038 which TLS ciphersuites are better than others. (Thanks to bug
3039 11513, the relay list is now well-considered, whereas the client
3040 list has been chosen mainly for anti-fingerprinting purposes.)
3041 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
3042 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
3043 AES128. Resolves ticket 11528.
3044 - Clients now try to advertise the same list of ciphersuites as
3045 Firefox 28. This change enables selection of (fast) GCM
3046 ciphersuites, disables some strange old ciphers, and stops
3047 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
3048 Resolves ticket 11438.
3050 o Minor bugfixes (configuration, security):
3051 - When running a hidden service, do not allow TunneledDirConns 0:
3052 trying to set that option together with a hidden service would
3053 otherwise prevent the hidden service from running, and also make
3054 it publish its descriptors directly over HTTP. Fixes bug 10849;
3055 bugfix on 0.2.1.1-alpha.
3057 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
3058 - Avoid sending a garbage value to the controller when a circuit is
3059 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
3061 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
3062 - Stop leaking memory when we successfully resolve a PTR record.
3063 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
3065 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
3066 - Avoid 60-second delays in the bootstrapping process when Tor is
3067 launching for a second time while using bridges. Fixes bug 9229;
3068 bugfix on 0.2.0.3-alpha.
3070 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
3071 - Give the correct URL in the warning message when trying to run a
3072 relay on an ancient version of Windows. Fixes bug 9393.
3074 o Minor bugfixes (compilation):
3075 - Fix a compilation error when compiling with --disable-curve25519.
3076 Fixes bug 9700; bugfix on 0.2.4.17-rc.
3079 - Downgrade the warning severity for the the "md was still
3080 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
3081 for trying to diagnose this bug, and the current warning in
3082 earlier versions of tor achieves nothing useful. Addresses warning
3085 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
3086 - When we run out of usable circuit IDs on a channel, log only one
3087 warning for the whole channel, and describe how many circuits
3088 there were on the channel. Fixes part of ticket 11553.
3090 o Minor features (security, backport from 0.2.5.4-alpha):
3091 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
3092 leave the default at 8GBytes), to better support Raspberry Pi
3093 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
3095 o Documentation (backport from 0.2.5.4-alpha):
3096 - Correctly document that we search for a system torrc file before
3097 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
3101 Changes in version 0.2.5.4-alpha - 2014-04-25
3102 Tor 0.2.5.4-alpha includes several security and performance
3103 improvements for clients and relays, including blacklisting authority
3104 signing keys that were used while susceptible to the OpenSSL
3105 "heartbleed" bug, fixing two expensive functions on busy relays,
3106 improved TLS ciphersuite preference lists, support for run-time
3107 hardening on compilers that support AddressSanitizer, and more work on
3108 the Linux sandbox code.
3110 There are also several usability fixes for clients (especially clients
3111 that use bridges), two new TransPort protocols supported (one on
3112 OpenBSD, one on FreeBSD), and various other bugfixes.
3114 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
3115 have accumulated many known flaws; everyone should upgrade.
3117 o Major features (security):
3118 - If you don't specify MaxMemInQueues yourself, Tor now tries to
3119 pick a good value based on your total system memory. Previously,
3120 the default was always 8 GB. You can still override the default by
3121 setting MaxMemInQueues yourself. Resolves ticket 11396.
3122 - Block authority signing keys that were used on authorities
3123 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
3124 don't have any evidence that these keys _were_ compromised; we're
3125 doing this to be prudent.) Resolves ticket 11464.
3127 o Major features (relay performance):
3128 - Speed up server-side lookups of rendezvous and introduction point
3129 circuits by using hashtables instead of linear searches. These
3130 functions previously accounted between 3 and 7% of CPU usage on
3131 some busy relays. Resolves ticket 9841.
3132 - Avoid wasting CPU when extending a circuit over a channel that is
3133 nearly out of circuit IDs. Previously, we would do a linear scan
3134 over possible circuit IDs before finding one or deciding that we
3135 had exhausted our possibilities. Now, we try at most 64 random
3136 circuit IDs before deciding that we probably won't succeed. Fixes
3137 a possible root cause of ticket 11553.
3139 o Major features (seccomp2 sandbox, Linux only):
3140 - The seccomp2 sandbox can now run a test network for multiple hours
3141 without crashing. The sandbox is still experimental, and more bugs
3142 will probably turn up. To try it, enable "Sandbox 1" on a Linux
3143 host. Resolves ticket 11351.
3144 - Strengthen sandbox code: the sandbox can now test the arguments
3145 for rename(), and blocks _sysctl() entirely. Resolves another part
3147 - When the sandbox blocks a system call, it now tries to log a stack
3148 trace before exiting. Resolves ticket 11465.
3150 o Major bugfixes (TLS cipher selection):
3151 - The relay ciphersuite list is now generated automatically based on
3152 uniform criteria, and includes all OpenSSL ciphersuites with
3153 acceptable strength and forward secrecy. Previously, we had left
3154 some perfectly fine ciphersuites unsupported due to omission or
3155 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
3156 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
3157 - Relays now trust themselves to have a better view than clients of
3158 which TLS ciphersuites are better than others. (Thanks to bug
3159 11513, the relay list is now well-considered, whereas the client
3160 list has been chosen mainly for anti-fingerprinting purposes.)
3161 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
3162 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
3163 AES128. Resolves ticket 11528.
3164 - Clients now try to advertise the same list of ciphersuites as
3165 Firefox 28. This change enables selection of (fast) GCM
3166 ciphersuites, disables some strange old ciphers, and stops
3167 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
3168 Resolves ticket 11438.
3170 o Major bugfixes (bridge client):
3171 - Avoid 60-second delays in the bootstrapping process when Tor is
3172 launching for a second time while using bridges. Fixes bug 9229;
3173 bugfix on 0.2.0.3-alpha.
3175 o Minor features (transparent proxy, *BSD):
3176 - Support FreeBSD's ipfw firewall interface for TransPort ports on
3177 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
3178 10267; patch from "yurivict".
3179 - Support OpenBSD's divert-to rules with the pf firewall for
3180 transparent proxy ports. To enable it, set "TransProxyType
3181 pf-divert". This allows Tor to run a TransPort transparent proxy
3182 port on OpenBSD 4.4 or later without root privileges. See the
3183 pf.conf(5) manual page for information on configuring pf to use
3184 divert-to rules. Closes ticket 10896; patch from Dana Koch.
3186 o Minor features (security):
3187 - New --enable-expensive-hardening option to enable security
3188 hardening options that consume nontrivial amounts of CPU and
3189 memory. Right now, this includes AddressSanitizer and UbSan, which
3190 are supported in newer versions of GCC and Clang. Closes ticket
3193 o Minor features (log verbosity):
3194 - Demote the message that we give when a flushing connection times
3195 out for too long from NOTICE to INFO. It was usually meaningless.
3196 Resolves ticket 5286.
3197 - Don't log so many notice-level bootstrapping messages at startup
3198 about downloading descriptors. Previously, we'd log a notice
3199 whenever we learned about more routers. Now, we only log a notice
3200 at every 5% of progress. Fixes bug 9963.
3201 - Warn less verbosely when receiving a malformed
3202 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
3203 - When we run out of usable circuit IDs on a channel, log only one
3204 warning for the whole channel, and describe how many circuits
3205 there were on the channel. Fixes part of ticket 11553.
3207 o Minor features (relay):
3208 - If a circuit timed out for at least 3 minutes, check if we have a
3209 new external IP address, and publish a new descriptor with the new
3210 IP address if it changed. Resolves ticket 2454.
3212 o Minor features (controller):
3213 - Make the entire exit policy available from the control port via
3214 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
3216 - Because of the fix for ticket 11396, the real limit for memory
3217 usage may no longer match the configured MaxMemInQueues value. The
3218 real limit is now exposed via GETINFO limits/max-mem-in-queues.
3220 o Minor features (bridge client):
3221 - Report a more useful failure message when we can't connect to a
3222 bridge because we don't have the right pluggable transport
3223 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
3225 o Minor features (diagnostic):
3226 - Add more log messages to diagnose bug 7164, which causes
3227 intermittent "microdesc_free() called but md was still referenced"
3228 warnings. We now include more information, to figure out why we
3229 might be cleaning a microdescriptor for being too old if it's
3230 still referenced by a live node_t object.
3232 o Minor bugfixes (client, DNSPort):
3233 - When using DNSPort, try to respond to AAAA requests with AAAA
3234 answers. Previously, we hadn't looked at the request type when
3235 deciding which answer type to prefer. Fixes bug 10468; bugfix on
3237 - When receiving a DNS query for an unsupported record type, reply
3238 with no answer rather than with a NOTIMPL error. This behavior
3239 isn't correct either, but it will break fewer client programs, we
3240 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
3243 o Minor bugfixes (exit relay):
3244 - Stop leaking memory when we successfully resolve a PTR record.
3245 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
3247 o Minor bugfixes (bridge client):
3248 - Stop accepting bridge lines containing hostnames. Doing so would
3249 cause clients to perform DNS requests on the hostnames, which was
3250 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
3251 - Avoid a 60-second delay in the bootstrapping process when a Tor
3252 client with pluggable transports re-reads its configuration at
3253 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
3255 o Minor bugfixes (client, logging during bootstrap):
3256 - Warn only once if we start logging in an unsafe way. Previously,
3257 we complain as many times as we had problems. Fixes bug 9870;
3258 bugfix on 0.2.5.1-alpha.
3259 - Only report the first fatal bootstrap error on a given OR
3260 connection. This stops us from telling the controller bogus error
3261 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
3262 - Be more helpful when trying to run sandboxed on Linux without
3263 libseccomp. Instead of saying "Sandbox is not implemented on this
3264 platform", we now explain that we need to be built with
3265 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
3266 - Avoid generating spurious warnings when starting with
3267 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
3270 o Minor bugfixes (closing OR connections):
3271 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
3272 check if it's an or_connection_t and correctly call
3273 connection_or_close_for_error() rather than
3274 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
3276 - When closing all connections on setting DisableNetwork to 1, use
3277 connection_or_close_normally() rather than closing OR connections
3278 out from under the channel layer. Fixes bug 11306; bugfix on
3281 o Minor bugfixes (controller):
3282 - Avoid sending a garbage value to the controller when a circuit is
3283 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
3285 o Minor bugfixes (tor-fw-helper):
3286 - Allow tor-fw-helper to build again by adding src/ext to its
3287 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
3289 o Minor bugfixes (bridges):
3290 - Avoid potential crashes or bad behavior when launching a
3291 server-side managed proxy with ORPort or ExtORPort temporarily
3292 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
3294 o Minor bugfixes (platform-specific):
3295 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
3296 bug 11426; bugfix on 0.2.5.3-alpha.
3297 - When dumping a malformed directory object to disk, save it in
3298 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
3300 - Don't report failures from make_socket_reuseable() on incoming
3301 sockets on OSX: this can happen when incoming connections close
3302 early. Fixes bug 10081.
3304 o Minor bugfixes (trivial memory leaks):
3305 - Fix a small memory leak when signing a directory object. Fixes bug
3306 11275; bugfix on 0.2.4.13-alpha.
3307 - Free placeholder entries in our circuit table at exit; fixes a
3308 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
3309 - Don't re-initialize a second set of OpenSSL mutexes when starting
3310 up. Previously, we'd make one set of mutexes, and then immediately
3311 replace them with another. Fixes bug 11726; bugfix on
3313 - Resolve some memory leaks found by coverity in the unit tests, on
3314 exit in tor-gencert, and on a failure to compute digests for our
3315 own keys when generating a v3 networkstatus vote. These leaks
3316 should never have affected anyone in practice.
3318 o Minor bugfixes (hidden service):
3319 - Only retry attempts to connect to a chosen rendezvous point 8
3320 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
3322 o Minor bugfixes (misc code correctness):
3323 - Fix various instances of undefined behavior in channeltls.c,
3324 tor_memmem(), and eventdns.c that would cause us to construct
3325 pointers to memory outside an allocated object. (These invalid
3326 pointers were not accessed, but C does not even allow them to
3327 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
3328 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
3329 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
3330 fix some miscellaneous errors in our tests and codebase. Fixes bug
3331 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
3332 - Always check return values for unlink, munmap, UnmapViewOfFile;
3333 check strftime return values more often. In some cases all we can
3334 do is report a warning, but this may help prevent deeper bugs from
3335 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
3337 - Fix numerous warnings from the clang "scan-build" static analyzer.
3338 Some of these are programming style issues; some of them are false
3339 positives that indicated awkward code; some are undefined behavior
3340 cases related to constructing (but not using) invalid pointers;
3341 some are assumptions about API behavior; some are (harmlessly)
3342 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
3343 correct; and one or two are genuine bugs that weren't reachable
3344 from the rest of the program. Fixes bug 8793; bugfixes on many,
3348 - Build the torify.1 manpage again. Previously, we were only trying
3349 to build it when also building tor-fw-helper. That's why we didn't
3350 notice that we'd broken the ability to build it. Fixes bug 11321;
3351 bugfix on 0.2.5.1-alpha.
3352 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
3353 11061; bugfix on 0.2.4.7-alpha.
3354 - Correctly document that we search for a system torrc file before
3355 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
3357 - Resolve warnings from Doxygen.
3359 o Code simplifications and refactoring:
3360 - Remove is_internal_IP() function. Resolves ticket 4645.
3361 - Remove unused function circuit_dump_by_chan from circuitlist.c.
3362 Closes issue 9107; patch from "marek".
3363 - Change our use of the ENUM_BF macro to avoid declarations that
3366 o Deprecated versions:
3367 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
3368 attention for some while. Directory authorities no longer accept
3369 descriptors from relays running any version of Tor prior to Tor
3370 0.2.3.16-alpha. Resolves ticket 11149.
3373 - New macros in test.h to simplify writing mock-functions for unit
3374 tests. Part of ticket 11507. Patch from Dana Koch.
3375 - Complete tests for the status.c module. Resolves ticket 11507.
3376 Patch from Dana Koch.
3379 - Remove all code for the long unused v1 directory protocol.
3380 Resolves ticket 11070.
3383 Changes in version 0.2.5.3-alpha - 2014-03-22
3384 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
3385 two new anti-DoS features for Tor relays, resolves a bug that kept
3386 SOCKS5 support for IPv6 from working, fixes several annoying usability
3387 issues for bridge users, and removes more old code for unused
3390 The Tor 0.2.5.x release series is now in patch-freeze: no feature
3391 patches not already written will be considered for inclusion in 0.2.5.x.
3393 o Major features (relay security, DoS-resistance):
3394 - When deciding whether we have run out of memory and we need to
3395 close circuits, also consider memory allocated in buffers for
3396 streams attached to each circuit.
3398 This change, which extends an anti-DoS feature introduced in
3399 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
3400 better resist more memory-based DoS attacks than before. Since the
3401 MaxMemInCellQueues option now applies to all queues, it is renamed
3402 to MaxMemInQueues. This feature fixes bug 10169.
3403 - Avoid hash-flooding denial-of-service attacks by using the secure
3404 SipHash-2-4 hash function for our hashtables. Without this
3405 feature, an attacker could degrade performance of a targeted
3406 client or server by flooding their data structures with a large
3407 number of entries to be stored at the same hash table position,
3408 thereby slowing down the Tor instance. With this feature, hash
3409 table positions are derived from a randomized cryptographic key,
3410 and an attacker cannot predict which entries will collide. Closes
3412 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
3413 the default at 8GBytes), to better support Raspberry Pi users. Fixes
3414 bug 9686; bugfix on 0.2.4.14-alpha.
3416 o Minor features (bridges, pluggable transports):
3417 - Bridges now write the SHA1 digest of their identity key
3418 fingerprint (that is, a hash of a hash of their public key) to
3419 notice-level logs, and to a new hashed-fingerprint file. This
3420 information will help bridge operators look up their bridge in
3421 Globe and similar tools. Resolves ticket 10884.
3422 - Improve the message that Tor displays when running as a bridge
3423 using pluggable transports without an Extended ORPort listener.
3424 Also, log the message in the log file too. Resolves ticket 11043.
3426 o Minor features (other):
3427 - Add a new option, PredictedPortsRelevanceTime, to control how long
3428 after having received a request to connect to a given port Tor
3429 will try to keep circuits ready in anticipation of future requests
3430 for that port. Patch from "unixninja92"; implements ticket 9176.
3431 - Generate a warning if any ports are listed in the SocksPolicy,
3432 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
3433 AuthDirBadExit options. (These options only support address
3434 ranges.) Fixes part of ticket 11108.
3435 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
3438 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
3439 - Build without warnings under clang 3.4. (We have some macros that
3440 define static functions only some of which will get used later in
3441 the module. Starting with clang 3.4, these give a warning unless the
3442 unused attribute is set on them.) Resolves ticket 10904.
3443 - Fix build warnings about missing "a2x" comment when building the
3444 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
3445 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
3447 o Minor bugfixes (client):
3448 - Improve the log message when we can't connect to a hidden service
3449 because all of the hidden service directory nodes hosting its
3450 descriptor are excluded. Improves on our fix for bug 10722, which
3451 was a bugfix on 0.2.0.10-alpha.
3452 - Raise a control port warning when we fail to connect to all of
3453 our bridges. Previously, we didn't inform the controller, and
3454 the bootstrap process would stall. Fixes bug 11069; bugfix on
3456 - Exit immediately when a process-owning controller exits.
3457 Previously, tor relays would wait for a little while after their
3458 controller exited, as if they had gotten an INT signal -- but this
3459 was problematic, since there was no feedback for the user. To do a
3460 clean shutdown, controllers should send an INT signal and give Tor
3461 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
3462 - Stop attempting to connect to bridges before our pluggable
3463 transports are configured (harmless but resulted in some erroneous
3464 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
3465 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
3466 generating incorrect SOCKS5 responses, and confusing client
3467 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
3469 o Minor bugfixes (relays and bridges):
3470 - Avoid crashing on a malformed resolv.conf file when running a
3471 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
3472 - Non-exit relays no longer launch mock DNS requests to check for
3473 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
3474 non-exit relays stopped servicing DNS requests. Fixes bug 965;
3475 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
3476 - Bridges now report complete directory request statistics. Related
3477 to bug 5824; bugfix on 0.2.2.1-alpha.
3478 - Bridges now never collect statistics that were designed for
3479 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
3480 - Stop giving annoying warning messages when we decide not to launch
3481 a pluggable transport proxy that we don't need (because there are
3482 no bridges configured to use it). Resolves ticket 5018; bugfix
3484 - Give the correct URL in the warning message when trying to run a
3485 relay on an ancient version of Windows. Fixes bug 9393.
3487 o Minor bugfixes (backtrace support):
3488 - Support automatic backtraces on more platforms by using the
3489 "-fasynchronous-unwind-tables" compiler option. This option is
3490 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
3491 is on by default and table generation is not. This doesn't yet
3492 add Windows support; only Linux, OSX, and some BSDs are affected.
3493 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
3494 - Avoid strange behavior if two threads hit failed assertions at the
3495 same time and both try to log backtraces at once. (Previously, if
3496 this had happened, both threads would have stored their intermediate
3497 results in the same buffer, and generated junk outputs.) Reported by
3498 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
3499 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
3500 0.2.5.2-alpha; patch from Nick Hopper.
3502 o Minor bugfixes (unit tests):
3503 - Fix a small bug in the unit tests that might have made the tests
3504 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
3505 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
3508 - Remove all remaining code related to version-0 hidden service
3509 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
3510 the rest of bug 10841.
3513 - Document in the manpage that "KBytes" may also be written as
3514 "kilobytes" or "KB", that "Kbits" may also be written as
3515 "kilobits", and so forth. Closes ticket 9222.
3516 - Document that the ClientOnly config option overrides ORPort.
3517 Our old explanation made ClientOnly sound as though it did
3518 nothing at all. Resolves bug 9059.
3519 - Explain that SocksPolicy, DirPolicy, and similar options don't
3520 take port arguments. Fixes the other part of ticket 11108.
3521 - Fix a comment about the rend_server_descriptor_t.protocols field
3522 to more accurately describe its range. Also, make that field
3523 unsigned, to more accurately reflect its usage. Fixes bug 9099;
3524 bugfix on 0.2.1.5-alpha.
3525 - Fix the manpage's description of HiddenServiceAuthorizeClient:
3526 the maximum client name length is 16, not 19. Fixes bug 11118;
3527 bugfix on 0.2.1.6-alpha.
3529 o Code simplifications and refactoring:
3530 - Get rid of router->address, since in all cases it was just the
3531 string representation of router->addr. Resolves ticket 5528.
3533 o Test infrastructure:
3534 - Update to the latest version of tinytest.
3535 - Improve the tinytest implementation of string operation tests so
3536 that comparisons with NULL strings no longer crash the tests; they
3537 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
3540 Changes in version 0.2.4.21 - 2014-02-28
3541 Tor 0.2.4.21 further improves security against potential adversaries who
3542 find breaking 1024-bit crypto doable, and backports several stability
3543 and robustness patches from the 0.2.5 branch.
3545 o Major features (client security):
3546 - When we choose a path for a 3-hop circuit, make sure it contains
3547 at least one relay that supports the NTor circuit extension
3548 handshake. Otherwise, there is a chance that we're building
3549 a circuit that's worth attacking by an adversary who finds
3550 breaking 1024-bit crypto doable, and that chance changes the game
3551 theory. Implements ticket 9777.
3554 - Do not treat streams that fail with reason
3555 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
3556 since it could also indicate an ENETUNREACH connection error. Fixes
3557 part of bug 10777; bugfix on 0.2.4.8-alpha.
3559 o Code simplification and refactoring:
3560 - Remove data structures which were introduced to implement the
3561 CellStatistics option: they are now redundant with the new timestamp
3562 field in the regular packed_cell_t data structure, which we did
3563 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
3566 - Always clear OpenSSL bignums before freeing them -- even bignums
3567 that don't contain secrets. Resolves ticket 10793. Patch by
3569 - Build without warnings under clang 3.4. (We have some macros that
3570 define static functions only some of which will get used later in
3571 the module. Starting with clang 3.4, these give a warning unless the
3572 unused attribute is set on them.) Resolves ticket 10904.
3573 - Update geoip and geoip6 files to the February 7 2014 Maxmind
3574 GeoLite2 Country database.
3577 - Set the listen() backlog limit to the largest actually supported
3578 on the system, not to the value in a header file. Fixes bug 9716;
3579 bugfix on every released Tor.
3580 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
3581 exit node as a NOROUTE error, not an INTERNAL error, since they
3582 can apparently happen when trying to connect to the wrong sort
3583 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
3584 - Fix build warnings about missing "a2x" comment when building the
3585 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
3586 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
3587 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
3588 not entirely remove it from the connection lists. Fixes bug 9602;
3589 bugfix on 0.2.4.4-alpha.
3590 - Fix a segmentation fault in our benchmark code when running with
3591 Fedora's OpenSSL package, or any other OpenSSL that provides
3592 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
3593 - Turn "circuit handshake stats since last time" log messages into a
3594 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
3596 o Documentation fixes:
3597 - Document that all but one DirPort entry must have the NoAdvertise
3598 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
3601 Changes in version 0.2.5.2-alpha - 2014-02-13
3602 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
3603 like the "poor random number generation" fix and the "building too many
3604 circuits" fix. It also further improves security against potential
3605 adversaries who find breaking 1024-bit crypto doable, and launches
3606 pluggable transports on demand (which gets us closer to integrating
3607 pluggable transport support by default -- not to be confused with Tor
3608 bundles enabling pluggable transports and bridges by default).
3610 o Major features (client security):
3611 - When we choose a path for a 3-hop circuit, make sure it contains
3612 at least one relay that supports the NTor circuit extension
3613 handshake. Otherwise, there is a chance that we're building
3614 a circuit that's worth attacking by an adversary who finds
3615 breaking 1024-bit crypto doable, and that chance changes the game
3616 theory. Implements ticket 9777.
3617 - Clients now look at the "usecreatefast" consensus parameter to
3618 decide whether to use CREATE_FAST or CREATE cells for the first hop
3619 of their circuit. This approach can improve security on connections
3620 where Tor's circuit handshake is stronger than the available TLS
3621 connection security levels, but the tradeoff is more computational
3622 load on guard relays. Implements proposal 221. Resolves ticket 9386.
3624 o Major features (bridges):
3625 - Don't launch pluggable transport proxies if we don't have any
3626 bridges configured that would use them. Now we can list many
3627 pluggable transports, and Tor will dynamically start one when it
3628 hears a bridge address that needs it. Resolves ticket 5018.
3629 - The bridge directory authority now assigns status flags (Stable,
3630 Guard, etc) to bridges based on thresholds calculated over all
3631 Running bridges. Now bridgedb can finally make use of its features
3632 to e.g. include at least one Stable bridge in its answers. Fixes
3635 o Major features (other):
3636 - Extend ORCONN controller event to include an "ID" parameter,
3637 and add four new controller event types CONN_BW, CIRC_BW,
3638 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
3639 The new events are emitted in private Tor networks only, with the
3640 goal of being able to better track performance and load during
3641 full-network simulations. Implements proposal 218 and ticket 7359.
3642 - On some platforms (currently: recent OSX versions, glibc-based
3643 platforms that support the ELF format, and a few other
3644 Unix-like operating systems), Tor can now dump stack traces
3645 when a crash occurs or an assertion fails. By default, traces
3646 are dumped to stderr (if possible) and to any logs that are
3647 reporting errors. Implements ticket 9299.
3650 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
3651 not entirely remove it from the connection lists. Fixes bug 9602;
3652 bugfix on 0.2.4.4-alpha.
3653 - Do not treat streams that fail with reason
3654 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
3655 since it could also indicate an ENETUNREACH connection error. Fixes
3656 part of bug 10777; bugfix on 0.2.4.8-alpha.
3658 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
3659 - Do not allow OpenSSL engines to replace the PRNG, even when
3660 HardwareAccel is set. The only default builtin PRNG engine uses
3661 the Intel RDRAND instruction to replace the entire PRNG, and
3662 ignores all attempts to seed it with more entropy. That's
3663 cryptographically stupid: the right response to a new alleged
3664 entropy source is never to discard all previously used entropy
3665 sources. Fixes bug 10402; works around behavior introduced in
3666 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
3668 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
3669 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
3670 - Avoid launching spurious extra circuits when a stream is pending.
3671 This fixes a bug where any circuit that _wasn't_ unusable for new
3672 streams would be treated as if it were, causing extra circuits to
3673 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
3675 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3676 - No longer stop reading or writing on cpuworker connections when
3677 our rate limiting buckets go empty. Now we should handle circuit
3678 handshake requests more promptly. Resolves bug 9731.
3679 - Stop trying to bootstrap all our directory information from
3680 only our first guard. Discovered while fixing bug 9946; bugfix
3683 o Minor features (bridges, pluggable transports):
3684 - Add threshold cutoffs to the networkstatus document created by
3685 the Bridge Authority. Fixes bug 1117.
3686 - On Windows, spawn background processes using the CREATE_NO_WINDOW
3687 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
3688 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
3689 Vidalia set this option for us.) Implements ticket 10297.
3691 o Minor features (security):
3692 - Always clear OpenSSL bignums before freeing them -- even bignums
3693 that don't contain secrets. Resolves ticket 10793. Patch by
3696 o Minor features (config options and command line):
3697 - Add an --allow-missing-torrc commandline option that tells Tor to
3698 run even if the configuration file specified by -f is not available.
3699 Implements ticket 10060.
3700 - Add support for the TPROXY transparent proxying facility on Linux.
3701 See documentation for the new TransProxyType option for more
3702 details. Implementation by "thomo". Closes ticket 10582.
3704 o Minor features (controller):
3705 - Add a new "HS_DESC" controller event that reports activities
3706 related to hidden service descriptors. Resolves ticket 8510.
3707 - New "DROPGUARDS" controller command to forget all current entry
3708 guards. Not recommended for ordinary use, since replacing guards
3709 too frequently makes several attacks easier. Resolves ticket 9934;
3712 o Minor features (build):
3713 - Assume that a user using ./configure --host wants to cross-compile,
3714 and give an error if we cannot find a properly named
3715 tool-chain. Add a --disable-tool-name-check option to proceed
3716 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
3717 - If we run ./configure and the compiler recognizes -fstack-protector
3718 but the linker rejects it, warn the user about a potentially missing
3719 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
3721 o Minor features (testing):
3722 - If Python is installed, "make check" now runs extra tests beyond
3723 the unit test scripts.
3724 - When bootstrapping a test network, sometimes very few relays get
3725 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
3726 specify a set of relays which should be voted Guard regardless of
3727 their uptime or bandwidth. Addresses ticket 9206.
3729 o Minor features (log messages):
3730 - When ServerTransportPlugin is set on a bridge, Tor can write more
3731 useful statistics about bridge use in its extrainfo descriptors,
3732 but only if the Extended ORPort ("ExtORPort") is set too. Add a
3733 log message to inform the user in this case. Resolves ticket 9651.
3734 - When receiving a new controller connection, log the origin address.
3735 Resolves ticket 9698; patch from "sigpipe".
3736 - When logging OpenSSL engine status at startup, log the status of
3737 more engines. Fixes ticket 10043; patch from Joshua Datko.
3738 - Turn "circuit handshake stats since last time" log messages into a
3739 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
3741 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3742 - Improve the circuit queue out-of-memory handler. Previously, when
3743 we ran low on memory, we'd close whichever circuits had the most
3744 queued cells. Now, we close those that have the *oldest* queued
3745 cells, on the theory that those are most responsible for us
3746 running low on memory. Based on analysis from a forthcoming paper
3747 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
3748 - Generate bootstrapping status update events correctly when fetching
3749 microdescriptors. Fixes bug 9927.
3750 - Update to the October 2 2013 Maxmind GeoLite Country database.
3752 o Minor bugfixes (clients):
3753 - When closing a channel that has already been open, do not close
3754 pending circuits that were waiting to connect to the same relay.
3755 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
3758 o Minor bugfixes (relays):
3759 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
3760 exit node as a NOROUTE error, not an INTERNAL error, since they
3761 can apparently happen when trying to connect to the wrong sort
3762 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
3764 o Minor bugfixes (bridges):
3765 - Fix a bug where the first connection works to a bridge that uses a
3766 pluggable transport with client-side parameters, but we don't send
3767 the client-side parameters on subsequent connections. (We don't
3768 use any pluggable transports with client-side parameters yet,
3769 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
3770 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
3772 o Minor bugfixes (node selection):
3773 - If ExcludeNodes is set, consider non-excluded hidden service
3774 directory servers before excluded ones. Do not consider excluded
3775 hidden service directory servers at all if StrictNodes is
3776 set. (Previously, we would sometimes decide to connect to those
3777 servers, and then realize before we initiated a connection that
3778 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
3780 - If we set the ExitNodes option but it doesn't include any nodes
3781 that have the Exit flag, we would choose not to bootstrap. Now we
3782 bootstrap so long as ExitNodes includes nodes which can exit to
3783 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
3785 o Minor bugfixes (controller and command-line):
3786 - If changing a config option via "setconf" fails in a recoverable
3787 way, we used to nonetheless write our new control ports to the
3788 file described by the "ControlPortWriteToFile" option. Now we only
3789 write out that file if we successfully switch to the new config
3790 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
3791 - When a command-line option such as --version or --help that
3792 ordinarily implies --hush appears on the command line along with
3793 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
3794 only if it appeared later on the command line. Fixes bug 9578;
3795 bugfix on 0.2.5.1-alpha.
3797 o Minor bugfixes (code correctness):
3798 - Previously we used two temporary files when writing descriptors to
3799 disk; now we only use one. Fixes bug 1376.
3800 - Remove an erroneous (but impossible and thus harmless) pointer
3801 comparison that would have allowed compilers to skip a bounds
3802 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
3803 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
3804 - Fix an always-true assertion in pluggable transports code so it
3805 actually checks what it was trying to check. Fixes bug 10046;
3806 bugfix on 0.2.3.9-alpha. Found by "dcb".
3808 o Minor bugfixes (protocol correctness):
3809 - When receiving a VERSIONS cell with an odd number of bytes, close
3810 the connection immediately since the cell is malformed. Fixes bug
3811 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
3814 o Minor bugfixes (build):
3815 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
3816 turned off (that is, without support for v2 link handshakes). Fixes
3817 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
3818 - Fix compilation warnings and startup issues when running with
3819 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
3821 - Fix compilation on Solaris 9, which didn't like us having an
3822 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
3824 o Minor bugfixes (testing):
3825 - Fix a segmentation fault in our benchmark code when running with
3826 Fedora's OpenSSL package, or any other OpenSSL that provides
3827 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
3829 o Minor bugfixes (log messages):
3830 - Fix a bug where clients using bridges would report themselves
3831 as 50% bootstrapped even without a live consensus document.
3832 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
3833 - Suppress a warning where, if there's only one directory authority
3834 in the network, we would complain that votes and signatures cannot
3835 be uploaded to other directory authorities. Fixes bug 10842;
3836 bugfix on 0.2.2.26-beta.
3837 - Report bootstrapping progress correctly when we're downloading
3838 microdescriptors. We had updated our "do we have enough microdescs
3839 to begin building circuits?" logic most recently in 0.2.4.10-alpha
3840 (see bug 5956), but we left the bootstrap status event logic at
3841 "how far through getting 1/4 of them are we?" Fixes bug 9958;
3842 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
3844 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
3845 - Avoid a crash bug when starting with a corrupted microdescriptor
3846 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
3847 - If we fail to dump a previously cached microdescriptor to disk, avoid
3848 freeing duplicate data later on. Fixes bug 10423; bugfix on
3849 0.2.4.13-alpha. Spotted by "bobnomnom".
3851 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3852 - Correctly log long IPv6 exit policies, instead of truncating them
3853 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
3854 - Our default TLS ecdhe groups were backwards: we meant to be using
3855 P224 for relays (for performance win) and P256 for bridges (since
3856 it is more common in the wild). Instead we had it backwards. After
3857 reconsideration, we decided that the default should be P256 on all
3858 hosts, since its security is probably better, and since P224 is
3859 reportedly used quite little in the wild. Found by "skruffy" on
3860 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
3861 - Free directory authority certificate download statuses on exit
3862 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
3864 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3865 - If the guard we choose first doesn't answer, we would try the
3866 second guard, but once we connected to the second guard we would
3867 abandon it and retry the first one, slowing down bootstrapping.
3868 The fix is to treat all our initially chosen guards as acceptable
3869 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
3870 - Fix an assertion failure that would occur when disabling the
3871 ORPort setting on a running Tor process while accounting was
3872 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
3873 - When examining the list of network interfaces to find our address,
3874 do not consider non-running or disabled network interfaces. Fixes
3875 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
3876 - Avoid an off-by-one error when checking buffer boundaries when
3877 formatting the exit status of a pluggable transport helper.
3878 This is probably not an exploitable bug, but better safe than
3879 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
3882 o Removed code and features:
3883 - Clients now reject any directory authority certificates lacking
3884 a dir-key-crosscert element. These have been included since
3885 0.2.1.9-alpha, so there's no real reason for them to be optional
3886 any longer. Completes proposal 157. Resolves ticket 10162.
3887 - Remove all code that existed to support the v2 directory system,
3888 since there are no longer any v2 directory authorities. Resolves
3890 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
3891 options, which were used for designating authorities as "Hidden
3892 service authorities". There has been no use of hidden service
3893 authorities since 0.2.2.1-alpha, when we stopped uploading or
3894 downloading v0 hidden service descriptors. Fixes bug 10881; also
3895 part of a fix for bug 10841.
3897 o Code simplification and refactoring:
3898 - Remove some old fallback code designed to keep Tor clients working
3899 in a network with only two working relays. Elsewhere in the code we
3900 have long since stopped supporting such networks, so there wasn't
3901 much point in keeping it around. Addresses ticket 9926.
3902 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
3903 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
3904 - Remove data structures which were introduced to implement the
3905 CellStatistics option: they are now redundant with the addition
3906 of a timestamp to the regular packed_cell_t data structure, which
3907 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
3910 o Documentation (man page) fixes:
3911 - Update manpage to describe some of the files you can expect to
3912 find in Tor's DataDirectory. Addresses ticket 9839.
3913 - Document that all but one DirPort entry must have the NoAdvertise
3914 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
3916 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3917 - Clarify the usage and risks of setting the ContactInfo torrc line
3918 for your relay or bridge. Resolves ticket 9854.
3919 - Add anchors to the manpage so we can link to the html version of
3920 the documentation for specific options. Resolves ticket 9866.
3921 - Replace remaining references to DirServer in man page and
3922 log entries. Resolves ticket 10124.
3925 - Make the "tor-gencert" tool used by directory authority operators
3926 create 2048-bit signing keys by default (rather than 1024-bit, since
3927 1024-bit is uncomfortably small these days). Addresses ticket 10324.
3930 Changes in version 0.2.4.20 - 2013-12-22
3931 Tor 0.2.4.20 fixes potentially poor random number generation for users
3932 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
3933 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
3934 and 4) have no state file in their DataDirectory (as would happen on
3935 first start). Users who generated relay or hidden service identity
3936 keys in such a situation should discard them and generate new ones.
3938 This release also fixes a logic error that caused Tor clients to build
3939 many more preemptive circuits than they actually need.
3942 - Do not allow OpenSSL engines to replace the PRNG, even when
3943 HardwareAccel is set. The only default builtin PRNG engine uses
3944 the Intel RDRAND instruction to replace the entire PRNG, and
3945 ignores all attempts to seed it with more entropy. That's
3946 cryptographically stupid: the right response to a new alleged
3947 entropy source is never to discard all previously used entropy
3948 sources. Fixes bug 10402; works around behavior introduced in
3949 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
3951 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
3952 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
3953 - Avoid launching spurious extra circuits when a stream is pending.
3954 This fixes a bug where any circuit that _wasn't_ unusable for new
3955 streams would be treated as if it were, causing extra circuits to
3956 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
3959 - Avoid a crash bug when starting with a corrupted microdescriptor
3960 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
3961 - If we fail to dump a previously cached microdescriptor to disk, avoid
3962 freeing duplicate data later on. Fixes bug 10423; bugfix on
3963 0.2.4.13-alpha. Spotted by "bobnomnom".
3966 Changes in version 0.2.4.19 - 2013-12-11
3967 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
3968 (1986-2013). Aaron worked on diverse projects including helping to guide
3969 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
3970 transparency to the U.S government's PACER documents, and contributing
3971 design and development for Tor and Tor2Web. Aaron was one of the latest
3972 martyrs in our collective fight for civil liberties and human rights,
3973 and his death is all the more painful because he was one of us.
3975 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
3976 a new circuit handshake and link encryption that use ECC to provide
3977 better security and efficiency; makes relays better manage circuit
3978 creation requests; uses "directory guards" to reduce client enumeration
3979 risks; makes bridges collect and report statistics about the pluggable
3980 transports they support; cleans up and improves our geoip database;
3981 gets much closer to IPv6 support for clients, bridges, and relays; makes
3982 directory authorities use measured bandwidths rather than advertised
3983 ones when computing flags and thresholds; disables client-side DNS
3984 caching to reduce tracking risks; and fixes a big bug in bridge
3985 reachability testing. This release introduces two new design
3986 abstractions in the code: a new "channel" abstraction between circuits
3987 and or_connections to allow for implementing alternate relay-to-relay
3988 transports, and a new "circuitmux" abstraction storing the queue of
3989 circuits for a channel. The release also includes many stability,
3990 security, and privacy fixes.
3993 Changes in version 0.2.4.18-rc - 2013-11-16
3994 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
3995 series. It takes a variety of fixes from the 0.2.5.x branch to improve
3996 stability, performance, and better handling of edge cases.
3999 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
4000 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
4001 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
4002 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
4003 them to solve bug 6033.)
4006 - No longer stop reading or writing on cpuworker connections when
4007 our rate limiting buckets go empty. Now we should handle circuit
4008 handshake requests more promptly. Resolves bug 9731.
4009 - If we are unable to save a microdescriptor to the journal, do not
4010 drop it from memory and then reattempt downloading it. Fixes bug
4011 9645; bugfix on 0.2.2.6-alpha.
4012 - Stop trying to bootstrap all our directory information from
4013 only our first guard. Discovered while fixing bug 9946; bugfix
4015 - The new channel code sometimes lost track of in-progress circuits,
4016 causing long-running clients to stop building new circuits. The
4017 fix is to always call circuit_n_chan_done(chan, 0) from
4018 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
4020 o Minor bugfixes (on 0.2.4.x):
4021 - Correctly log long IPv6 exit policies, instead of truncating them
4022 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
4023 - Our default TLS ecdhe groups were backwards: we meant to be using
4024 P224 for relays (for performance win) and P256 for bridges (since
4025 it is more common in the wild). Instead we had it backwards. After
4026 reconsideration, we decided that the default should be P256 on all
4027 hosts, since its security is probably better, and since P224 is
4028 reportedly used quite little in the wild. Found by "skruffy" on
4029 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
4030 - Free directory authority certificate download statuses on exit
4031 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
4033 o Minor bugfixes (on 0.2.3.x and earlier):
4034 - If the guard we choose first doesn't answer, we would try the
4035 second guard, but once we connected to the second guard we would
4036 abandon it and retry the first one, slowing down bootstrapping.
4037 The fix is to treat all our initially chosen guards as acceptable
4038 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
4039 - Fix an assertion failure that would occur when disabling the
4040 ORPort setting on a running Tor process while accounting was
4041 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
4042 - When examining the list of network interfaces to find our address,
4043 do not consider non-running or disabled network interfaces. Fixes
4044 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
4045 - Avoid an off-by-one error when checking buffer boundaries when
4046 formatting the exit status of a pluggable transport helper.
4047 This is probably not an exploitable bug, but better safe than
4048 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
4051 o Minor features (protecting client timestamps):
4052 - Clients no longer send timestamps in their NETINFO cells. These were
4053 not used for anything, and they provided one small way for clients
4054 to be distinguished from each other as they moved from network to
4055 network or behind NAT. Implements part of proposal 222.
4056 - Clients now round timestamps in INTRODUCE cells down to the nearest
4057 10 minutes. If a new Support022HiddenServices option is set to 0, or
4058 if it's set to "auto" and the feature is disabled in the consensus,
4059 the timestamp is sent as 0 instead. Implements part of proposal 222.
4060 - Stop sending timestamps in AUTHENTICATE cells. This is not such
4061 a big deal from a security point of view, but it achieves no actual
4062 good purpose, and isn't needed. Implements part of proposal 222.
4063 - Reduce down accuracy of timestamps in hidden service descriptors.
4064 Implements part of proposal 222.
4066 o Minor features (other):
4067 - Improve the circuit queue out-of-memory handler. Previously, when
4068 we ran low on memory, we'd close whichever circuits had the most
4069 queued cells. Now, we close those that have the *oldest* queued
4070 cells, on the theory that those are most responsible for us
4071 running low on memory. Based on analysis from a forthcoming paper
4072 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
4073 - Generate bootstrapping status update events correctly when fetching
4074 microdescriptors. Fixes bug 9927.
4075 - Update to the October 2 2013 Maxmind GeoLite Country database.
4077 o Documentation fixes:
4078 - Clarify the usage and risks of setting the ContactInfo torrc line
4079 for your relay or bridge. Resolves ticket 9854.
4080 - Add anchors to the manpage so we can link to the html version of
4081 the documentation for specific options. Resolves ticket 9866.
4082 - Replace remaining references to DirServer in man page and
4083 log entries. Resolves ticket 10124.
4086 Changes in version 0.2.5.1-alpha - 2013-10-02
4087 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
4088 on Linux, allows bridges that offer pluggable transports to report usage
4089 statistics, fixes many issues to make testing easier, and provides
4090 a pile of minor features and bugfixes that have been waiting for a
4091 release of the new branch.
4093 This is the first alpha release in a new series, so expect there to
4094 be bugs. Users who would rather test out a more stable branch should
4095 stay with 0.2.4.x for now.
4097 o Major features (security):
4098 - Use the seccomp2 syscall filtering facility on Linux to limit
4099 which system calls Tor can invoke. This is an experimental,
4100 Linux-only feature to provide defense-in-depth against unknown
4101 attacks. To try turning it on, set "Sandbox 1" in your torrc
4102 file. Please be ready to report bugs. We hope to add support
4103 for better sandboxing in the future, including more fine-grained
4104 filters, better division of responsibility, and support for more
4105 platforms. This work has been done by Cristian-Matei Toader for
4106 Google Summer of Code.
4107 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
4108 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
4109 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
4110 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
4111 them to solve bug 6033.)
4113 o Major features (other):
4114 - Add support for passing arguments to managed pluggable transport
4115 proxies. Implements ticket 3594.
4116 - Bridges now track GeoIP information and the number of their users
4117 even when pluggable transports are in use, and report usage
4118 statistics in their extra-info descriptors. Resolves tickets 4773
4120 - Make testing Tor networks bootstrap better: lower directory fetch
4121 retry schedules and maximum interval without directory requests,
4122 and raise maximum download tries. Implements ticket 6752.
4123 - Add make target 'test-network' to run tests on a Chutney network.
4124 Implements ticket 8530.
4125 - The ntor handshake is now on-by-default, no matter what the
4126 directory authorities recommend. Implements ticket 8561.
4129 - Instead of writing destroy cells directly to outgoing connection
4130 buffers, queue them and intersperse them with other outgoing cells.
4131 This can prevent a set of resource starvation conditions where too
4132 many pending destroy cells prevent data cells from actually getting
4133 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
4134 bugfix on 0.2.0.1-alpha.
4135 - If we are unable to save a microdescriptor to the journal, do not
4136 drop it from memory and then reattempt downloading it. Fixes bug
4137 9645; bugfix on 0.2.2.6-alpha.
4138 - The new channel code sometimes lost track of in-progress circuits,
4139 causing long-running clients to stop building new circuits. The
4140 fix is to always call circuit_n_chan_done(chan, 0) from
4141 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
4144 - Tor now builds each source file in two modes: a mode that avoids
4145 exposing identifiers needlessly, and another mode that exposes
4146 more identifiers for testing. This lets the compiler do better at
4147 optimizing the production code, while enabling us to take more
4148 radical measures to let the unit tests test things.
4149 - The production builds no longer include functions used only in
4150 the unit tests; all functions exposed from a module only for
4151 unit-testing are now static in production builds.
4152 - Add an --enable-coverage configuration option to make the unit
4153 tests (and a new src/or/tor-cov target) to build with gcov test
4157 - We now have rudimentary function mocking support that our unit
4158 tests can use to test functions in isolation. Function mocking
4159 lets the tests temporarily replace a function's dependencies with
4160 stub functions, so that the tests can check the function without
4161 invoking the other functions it calls.
4162 - Add more unit tests for the <circid,channel>->circuit map, and
4163 the destroy-cell-tracking code to fix bug 7912.
4164 - Unit tests for failing cases of the TAP onion handshake.
4165 - More unit tests for address-manipulation functions.
4167 o Minor features (protecting client timestamps):
4168 - Clients no longer send timestamps in their NETINFO cells. These were
4169 not used for anything, and they provided one small way for clients
4170 to be distinguished from each other as they moved from network to
4171 network or behind NAT. Implements part of proposal 222.
4172 - Clients now round timestamps in INTRODUCE cells down to the nearest
4173 10 minutes. If a new Support022HiddenServices option is set to 0, or
4174 if it's set to "auto" and the feature is disabled in the consensus,
4175 the timestamp is sent as 0 instead. Implements part of proposal 222.
4176 - Stop sending timestamps in AUTHENTICATE cells. This is not such
4177 a big deal from a security point of view, but it achieves no actual
4178 good purpose, and isn't needed. Implements part of proposal 222.
4179 - Reduce down accuracy of timestamps in hidden service descriptors.
4180 Implements part of proposal 222.
4182 o Minor features (config options):
4183 - Config (torrc) lines now handle fingerprints which are missing
4184 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
4185 - Support a --dump-config option to print some or all of the
4186 configured options. Mainly useful for debugging the command-line
4187 option parsing code. Helps resolve ticket 4647.
4188 - Raise awareness of safer logging: notify user of potentially
4189 unsafe config options, like logging more verbosely than severity
4190 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
4191 - Add a new configuration option TestingV3AuthVotingStartOffset
4192 that bootstraps a network faster by changing the timing for
4193 consensus votes. Addresses ticket 8532.
4194 - Add a new torrc option "ServerTransportOptions" that allows
4195 bridge operators to pass configuration parameters to their
4196 pluggable transports. Resolves ticket 8929.
4197 - The config (torrc) file now accepts bandwidth and space limits in
4198 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
4199 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
4202 o Minor features (build):
4203 - Add support for `--library-versions` flag. Implements ticket 6384.
4204 - Return the "unexpected sendme" warnings to a warn severity, but make
4205 them rate limited, to help diagnose ticket 8093.
4206 - Detect a missing asciidoc, and warn the user about it, during
4207 configure rather than at build time. Fixes issue 6506. Patch from
4210 o Minor features (other):
4211 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
4212 sockets in a single system call. Implements ticket 5129.
4213 - Log current accounting state (bytes sent and received + remaining
4214 time for the current accounting period) in the relay's heartbeat
4215 message. Implements ticket 5526; patch from Peter Retzlaff.
4216 - Implement the TRANSPORT_LAUNCHED control port event that
4217 notifies controllers about new launched pluggable
4218 transports. Resolves ticket 5609.
4219 - If we're using the pure-C 32-bit curve25519_donna implementation
4220 of curve25519, build it with the -fomit-frame-pointer option to
4221 make it go faster on register-starved hosts. This improves our
4222 handshake performance by about 6% on i386 hosts without nacl.
4224 - Update to the September 4 2013 Maxmind GeoLite Country database.
4227 - Set the listen() backlog limit to the largest actually supported
4228 on the system, not to the value in a header file. Fixes bug 9716;
4229 bugfix on every released Tor.
4230 - No longer accept malformed http headers when parsing urls from
4231 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
4232 bugfix on 0.0.6pre1.
4233 - In munge_extrainfo_into_routerinfo(), check the return value of
4234 memchr(). This would have been a serious issue if we ever passed
4235 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
4237 - On the chance that somebody manages to build Tor on a
4238 platform where time_t is unsigned, correct the way that
4239 microdesc_add_to_cache() handles negative time arguments.
4240 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
4241 - Reject relative control socket paths and emit a warning. Previously,
4242 single-component control socket paths would be rejected, but Tor
4243 would not log why it could not validate the config. Fixes bug 9258;
4244 bugfix on 0.2.3.16-alpha.
4246 o Minor bugfixes (command line):
4247 - Use a single command-line parser for parsing torrc options on the
4248 command line and for finding special command-line options to avoid
4249 inconsistent behavior for torrc option arguments that have the same
4250 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
4252 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
4253 9573; bugfix on 0.0.9pre5.
4255 o Minor fixes (build, auxiliary programs):
4256 - Stop preprocessing the "torify" script with autoconf, since
4257 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
4259 - The tor-fw-helper program now follows the standard convention and
4260 exits with status code "0" on success. Fixes bug 9030; bugfix on
4261 0.2.3.1-alpha. Patch by Arlo Breault.
4262 - Corrected ./configure advice for what openssl dev package you should
4263 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
4265 o Minor code improvements:
4266 - Remove constants and tests for PKCS1 padding; it's insecure and
4267 shouldn't be used for anything new. Fixes bug 8792; patch
4269 - Remove instances of strcpy() from the unit tests. They weren't
4270 hurting anything, since they were only in the unit tests, but it's
4271 embarassing to have strcpy() in the code at all, and some analysis
4272 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
4273 0.2.3.8-alpha. Patch from Arlo Breault.
4276 - Remove migration code from when we renamed the "cached-routers"
4277 file to "cached-descriptors" back in 0.2.0.8-alpha. This
4278 incidentally resolves ticket 6502 by cleaning up the related code
4279 a bit. Patch from Akshay Hebbar.
4281 o Code simplification and refactoring:
4282 - Extract the common duplicated code for creating a subdirectory
4283 of the data directory and writing to a file in it. Fixes ticket
4284 4282; patch from Peter Retzlaff.
4285 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
4286 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
4287 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
4288 - Add a set of accessor functions for the circuit timeout data
4289 structure. Fixes ticket 6153; patch from "piet".
4290 - Clean up exit paths from connection_listener_new(). Closes ticket
4291 8789. Patch from Arlo Breault.
4292 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
4293 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
4294 - Use a doubly-linked list to implement the global circuit list.
4295 Resolves ticket 9108. Patch from Marek Majkowski.
4296 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
4299 Changes in version 0.2.4.17-rc - 2013-09-05
4300 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
4301 series. It adds an emergency step to help us tolerate the massive
4302 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
4303 circuit-level handshakes now effectively jump the queue compared to
4304 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
4305 big bug hindering bridge reachability tests.
4308 - Relays now process the new "NTor" circuit-level handshake requests
4309 with higher priority than the old "TAP" circuit-level handshake
4310 requests. We still process some TAP requests to not totally starve
4311 0.2.3 clients when NTor becomes popular. A new consensus parameter
4312 "NumNTorsPerTAP" lets us tune the balance later if we need to.
4313 Implements ticket 9574.
4316 - If the circuit build timeout logic is disabled (via the consensus,
4317 or because we are an authority), then don't build testing circuits.
4318 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
4319 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
4320 previously they did not, which prevented them from receiving
4321 successful connections from relays for self-test or bandwidth
4322 testing. Also, when a relay is extending a circuit to a bridge,
4323 it needs to send a NETINFO cell, even when the bridge hasn't sent
4324 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
4325 - If the time to download the next old-style networkstatus is in
4326 the future, do not decline to consider whether to download the
4327 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
4331 - Avoid double-closing the listener socket in our socketpair()
4332 replacement (used on Windows) in the case where the addresses on
4333 our opened sockets don't match what we expected. Fixes bug 9400;
4334 bugfix on 0.0.2pre7. Found by Coverity.
4336 o Minor fixes (config options):
4337 - Avoid overflows when the user sets MaxCircuitDirtiness to a
4338 ridiculously high value, by imposing a (ridiculously high) 30-day
4339 maximum on MaxCircuitDirtiness.
4340 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
4341 message is logged at notice, not at info.
4342 - Warn and fail if a server is configured not to advertise any
4343 ORPorts at all. (We need *something* to put in our descriptor,
4344 or we just won't work.)
4347 - Track how many "TAP" and "NTor" circuit handshake requests we get,
4348 and how many we complete, and log it every hour to help relay
4349 operators follow trends in network load. Addresses ticket 9658.
4350 - Update to the August 7 2013 Maxmind GeoLite Country database.
4353 Changes in version 0.2.4.16-rc - 2013-08-10
4354 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
4355 series. It fixes several crash bugs in the 0.2.4 branch.
4358 - Fix a bug in the voting algorithm that could yield incorrect results
4359 when a non-naming authority declared too many flags. Fixes bug 9200;
4360 bugfix on 0.2.0.3-alpha.
4361 - Fix an uninitialized read that could in some cases lead to a remote
4362 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
4363 Anybody running a hidden service on the experimental 0.2.4.x
4364 branch should upgrade. (This is, so far as we know, unrelated to
4366 - Avoid an assertion failure when processing DNS replies without the
4367 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
4368 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
4369 0.2.4.15-rc. Found by stem integration tests.
4372 - Fix an invalid memory read that occured when a pluggable
4373 transport proxy failed its configuration protocol.
4374 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
4375 - When evaluating whether to use a connection that we haven't
4376 decided is canonical using a recent link protocol version,
4377 decide that it's canonical only if it used address _does_
4378 match the desired address. Fixes bug 9309; bugfix on
4379 0.2.4.4-alpha. Reported by skruffy.
4380 - Make the default behavior of NumDirectoryGuards be to track
4381 NumEntryGuards. Now a user who changes only NumEntryGuards will get
4382 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
4383 - Fix a spurious compilation warning with some older versions of
4384 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
4387 - Update to the July 3 2013 Maxmind GeoLite Country database.
4390 Changes in version 0.2.4.15-rc - 2013-07-01
4391 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
4392 series. It fixes a few smaller bugs, but generally appears stable.
4393 Please test it and let us know whether it is!
4396 - When receiving a new configuration file via the control port's
4397 LOADCONF command, do not treat the defaults file as absent.
4398 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
4401 - Issue a warning when running with the bufferevents backend enabled.
4402 It's still not stable, and people should know that they're likely
4403 to hit unexpected problems. Closes ticket 9147.
4406 Changes in version 0.2.4.14-alpha - 2013-06-18
4407 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
4408 present in 0.2.4.13-alpha.
4411 - When we have too much memory queued in circuits (according to a new
4412 MaxMemInCellQueues option), close the circuits consuming the most
4413 memory. This prevents us from running out of memory as a relay if
4414 circuits fill up faster than they can be drained. Fixes bug 9063;
4415 bugfix on the 54th commit of Tor. This bug is a further fix beyond
4416 bug 6252, whose fix was merged into 0.2.3.21-rc.
4418 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
4419 where we tried to solve this issue simply by imposing an upper limit
4420 on the number of queued cells for a single circuit. That approach
4421 proved to be problematic, since there are ways to provoke clients to
4422 send a number of cells in excess of any such reasonable limit. Fixes
4423 bug 9072; bugfix on 0.2.4.13-alpha.
4425 - Limit hidden service descriptors to at most ten introduction
4426 points, to slow one kind of guard enumeration. Fixes bug 9002;
4427 bugfix on 0.1.1.11-alpha.
4430 Changes in version 0.2.4.13-alpha - 2013-06-14
4431 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
4432 vulnerabilities, makes socks5 username/password circuit isolation
4433 actually actually work (this time for sure!), and cleans up a bunch
4434 of other issues in preparation for a release candidate.
4436 o Major bugfixes (robustness):
4437 - Close any circuit that has too many cells queued on it. Fixes
4438 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
4439 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
4440 - Prevent the get_freelists() function from running off the end of
4441 the list of freelists if it somehow gets an unrecognized
4442 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
4444 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
4445 when an exit connection with optimistic data succeeds immediately
4446 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
4448 - Fix a directory authority crash bug when building a consensus
4449 using an older consensus as its basis. Fixes bug 8833. Bugfix
4453 - Avoid a memory leak where we would leak a consensus body when we
4454 find that a consensus which we couldn't previously verify due to
4455 missing certificates is now verifiable. Fixes bug 8719; bugfix
4457 - We used to always request authority certificates by identity digest,
4458 meaning we'd get the newest one even when we wanted one with a
4459 different signing key. Then we would complain about being given
4460 a certificate we already had, and never get the one we really
4461 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
4462 resource to request the one we want. Fixes bug 5595; bugfix on
4464 - Follow the socks5 protocol when offering username/password
4465 authentication. The fix for bug 8117 exposed this bug, and it
4466 turns out real-world applications like Pidgin do care. Bugfix on
4467 0.2.3.2-alpha; fixes bug 8879.
4468 - Prevent failures on Windows Vista and later when rebuilding the
4469 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
4470 bugfix on 0.2.4.12-alpha.
4473 - Fix an impossible buffer overrun in the AES unit tests. Fixes
4474 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
4475 - If for some reason we fail to write a microdescriptor while
4476 rebuilding the cache, do not let the annotations from that
4477 microdescriptor linger in the cache file, and do not let the
4478 microdescriptor stay recorded as present in its old location.
4479 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
4480 - Fix a memory leak that would occur whenever a configuration
4481 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
4482 - Paste the description for PathBias parameters from the man
4483 page into or.h, so the code documents them too. Fixes bug 7982;
4484 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
4485 - Relays now treat a changed IPv6 ORPort as sufficient reason to
4486 publish an updated descriptor. Fixes bug 6026; bugfix on
4488 - When launching a resolve request on behalf of an AF_UNIX control
4489 socket, omit the address field of the new entry connection, used in
4490 subsequent controller events, rather than letting tor_dup_addr()
4491 set it to "<unknown address type>". Fixes bug 8639; bugfix on
4494 o Minor bugfixes (log messages):
4495 - Fix a scaling issue in the path bias accounting code that
4496 resulted in "Bug:" log messages from either
4497 pathbias_scale_close_rates() or pathbias_count_build_success().
4498 This represents a bugfix on a previous bugfix: the original fix
4499 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
4501 - Give a less useless error message when the user asks for an IPv4
4502 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
4506 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
4507 to tolerate bug 8093 for now.
4508 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
4509 in directory authority votes to describe whether they have enough
4510 measured bandwidths to ignore advertised (relay descriptor)
4511 bandwidth claims. Resolves ticket 8711.
4512 - Update to the June 5 2013 Maxmind GeoLite Country database.
4514 o Removed documentation:
4515 - Remove some of the older contents of doc/ as obsolete; move others
4516 to torspec.git. Fixes bug 8965.
4518 o Code simplification and refactoring:
4519 - Avoid using character buffers when constructing most directory
4520 objects: this approach was unwieldy and error-prone. Instead,
4521 build smartlists of strings, and concatenate them when done.
4524 Changes in version 0.2.4.12-alpha - 2013-04-18
4525 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
4526 process for lengthening the guard rotation period, makes directory
4527 authority opinions in the consensus a bit less gameable, makes socks5
4528 username/password circuit isolation actually work, and fixes a wide
4529 variety of other issues.
4532 - Raise the default time that a client keeps an entry guard from
4533 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
4534 2012 paper. (We would make it even longer, but we need better client
4535 load balancing first.) Also, make the guard lifetime controllable
4536 via a new GuardLifetime torrc option and a GuardLifetime consensus
4537 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
4538 - Directory authorities now prefer using measured bandwidths to
4539 advertised ones when computing flags and thresholds. Resolves
4541 - Directory authorities that have more than a threshold number
4542 of relays with measured bandwidths now treat relays with unmeasured
4543 bandwidths as having bandwidth 0. Resolves ticket 8435.
4545 o Major bugfixes (assert / resource use):
4546 - Avoid a bug where our response to TLS renegotiation under certain
4547 network conditions could lead to a busy-loop, with 100% CPU
4548 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
4549 - Avoid an assertion when we discover that we'd like to write a cell
4550 onto a closing connection: just discard the cell. Fixes another
4551 case of bug 7350; bugfix on 0.2.4.4-alpha.
4553 o Major bugfixes (client-side privacy):
4554 - When we mark a circuit as unusable for new circuits, have it
4555 continue to be unusable for new circuits even if MaxCircuitDirtiness
4556 is increased too much at the wrong time, or the system clock jumps
4557 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
4558 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
4559 which have resolved to internal addresses") is set, apply that
4560 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
4561 - When an exit relay rejects a stream with reason "exit policy", but
4562 we only know an exit policy summary (e.g. from the microdesc
4563 consensus) for it, do not mark the relay as useless for all exiting.
4564 Instead, mark just the circuit as unsuitable for that particular
4565 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
4566 - Allow applications to get proper stream isolation with
4567 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
4568 username/password authentication also offer "no authentication". Tor
4569 had previously preferred "no authentication", so the applications
4570 never actually sent Tor their auth details. Now Tor selects
4571 username/password authentication if it's offered. You can disable
4572 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
4573 bug 8117; bugfix on 0.2.3.3-alpha.
4575 o Major bugfixes (other):
4576 - When unable to find any working directory nodes to use as a
4577 directory guard, give up rather than adding the same non-working
4578 nodes to the directory guard list over and over. Fixes bug 8231;
4579 bugfix on 0.2.4.8-alpha.
4582 - Reject as invalid most directory objects containing a NUL.
4583 Belt-and-suspender fix for bug 8037.
4584 - In our testsuite, create temporary directories with a bit more
4585 entropy in their name to make name collisions less likely. Fixes
4587 - Add CACHED keyword to ADDRMAP events in the control protocol
4588 to indicate whether a DNS result will be cached or not. Resolves
4590 - Update to the April 3 2013 Maxmind GeoLite Country database.
4592 o Minor features (build):
4593 - Detect and reject attempts to build Tor with threading support
4594 when OpenSSL has been compiled without threading support.
4596 - Clarify that when autoconf is checking for nacl, it is checking
4597 specifically for nacl with a fast curve25519 implementation.
4599 - Warn if building on a platform with an unsigned time_t: there
4600 are too many places where Tor currently assumes that time_t can
4601 hold negative values. We'd like to fix them all, but probably
4604 o Minor bugfixes (build):
4605 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
4606 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
4607 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
4608 - Add the old src/or/micro-revision.i filename to CLEANFILES.
4609 On the off chance that somebody has one, it will go away as soon
4610 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
4611 - Build Tor correctly on 32-bit platforms where the compiler can build
4612 but not run code using the "uint128_t" construction. Fixes bug 8587;
4613 bugfix on 0.2.4.8-alpha.
4614 - Fix compilation warning with some versions of clang that would
4615 prefer the -Wswitch-enum compiler flag to warn about switch
4616 statements with missing enum values, even if those switch
4617 statements have a "default:" statement. Fixes bug 8598; bugfix
4620 o Minor bugfixes (protocol):
4621 - Fix the handling of a TRUNCATE cell when it arrives while the
4622 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
4623 - Fix a misframing issue when reading the version numbers in a
4624 VERSIONS cell. Previously we would recognize [00 01 00 02] as
4625 'version 1, version 2, and version 0x100', when it should have
4626 only included versions 1 and 2. Fixes bug 8059; bugfix on
4627 0.2.0.10-alpha. Reported pseudonymously.
4628 - Make the format and order of STREAM events for DNS lookups
4629 consistent among the various ways to launch DNS lookups. Fixes
4630 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
4631 - Correct our check for which versions of Tor support the EXTEND2
4632 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
4633 later, when support was really added in version 0.2.4.8-alpha.
4634 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
4636 o Minor bugfixes (other):
4637 - Correctly store microdescriptors and extrainfo descriptors with
4638 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
4639 Bug reported by "cypherpunks".
4640 - Increase the width of the field used to remember a connection's
4641 link protocol version to two bytes. Harmless for now, since the
4642 only currently recognized versions are one byte long. Reported
4643 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
4644 - If the state file's path bias counts are invalid (presumably from a
4645 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
4646 additional checks and log messages to the scaling of Path Bias
4647 counts, in case there still are remaining issues with scaling.
4648 Should help resolve bug 8235.
4649 - Eliminate several instances where we use "Nickname=ID" to refer to
4650 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
4651 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
4652 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
4654 o Minor bugfixes (syscalls):
4655 - Always check the return values of functions fcntl() and
4656 setsockopt(). We don't believe these are ever actually failing in
4657 practice, but better safe than sorry. Also, checking these return
4658 values should please analysis tools like Coverity. Patch from
4659 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
4660 - Use direct writes rather than stdio when building microdescriptor
4661 caches, in an attempt to mitigate bug 8031, or at least make it
4664 o Minor bugfixes (config):
4665 - When rejecting a configuration because we were unable to parse a
4666 quoted string, log an actual error message. Fixes bug 7950; bugfix
4668 - Behave correctly when the user disables LearnCircuitBuildTimeout
4669 but doesn't tell us what they would like the timeout to be. Fixes
4670 bug 6304; bugfix on 0.2.2.14-alpha.
4671 - When autodetecting the number of CPUs, use the number of available
4672 CPUs in preference to the number of configured CPUs. Inform the
4673 user if this reduces the number of available CPUs. Fixes bug 8002;
4674 bugfix on 0.2.3.1-alpha.
4675 - Make it an error when you set EntryNodes but disable UseGuardNodes,
4676 since it will (surprisingly to some users) ignore EntryNodes. Fixes
4677 bug 8180; bugfix on 0.2.3.11-alpha.
4678 - Allow TestingTorNetworks to override the 4096-byte minimum for
4679 the Fast threshold. Otherwise they can't bootstrap until they've
4680 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
4681 - Fix some logic errors when the user manually overrides the
4682 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
4685 o Minor bugfixes (log messages to help diagnose bugs):
4686 - If we fail to free a microdescriptor because of bug 7164, log
4687 the filename and line number from which we tried to free it.
4688 - Add another diagnostic to the heartbeat message: track and log
4689 overhead that TLS is adding to the data we write. If this is
4690 high, we are sending too little data to SSL_write at a time.
4691 Diagnostic for bug 7707.
4692 - Add more detail to a log message about relaxed timeouts, to help
4694 - Warn more aggressively when flushing microdescriptors to a
4695 microdescriptor cache fails, in an attempt to mitigate bug 8031,
4696 or at least make it more diagnosable.
4697 - Improve debugging output to help track down bug 8185 ("Bug:
4698 outgoing relay cell has n_chan==NULL. Dropping.")
4699 - Log the purpose of a path-bias testing circuit correctly.
4700 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
4702 o Minor bugfixes (0.2.4.x log messages that were too noisy):
4703 - Don't attempt to relax the timeout of already opened 1-hop circuits.
4704 They might never timeout. This should eliminate some/all cases of
4705 the relaxed timeout log message.
4706 - Use circuit creation time for network liveness evaluation. This
4707 should eliminate warning log messages about liveness caused
4708 by changes in timeout evaluation. Fixes bug 6572; bugfix on
4710 - Reduce a path bias length check from notice to info. The message
4711 is triggered when creating controller circuits. Fixes bug 8196;
4712 bugfix on 0.2.4.8-alpha.
4713 - Fix a path state issue that triggered a notice during relay startup.
4714 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
4715 - Reduce occurrences of warns about circuit purpose in
4716 connection_ap_expire_building(). Fixes bug 8477; bugfix on
4719 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
4720 - If we encounter a write failure on a SOCKS connection before we
4721 finish our SOCKS handshake, don't warn that we closed the
4722 connection before we could send a SOCKS reply. Fixes bug 8427;
4723 bugfix on 0.1.0.1-rc.
4724 - Correctly recognize that [::1] is a loopback address. Fixes
4725 bug 8377; bugfix on 0.2.1.3-alpha.
4726 - Fix a directory authority warn caused when we have a large amount
4727 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
4728 - Don't log inappropriate heartbeat messages when hibernating: a
4729 hibernating node is _expected_ to drop out of the consensus,
4730 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
4731 bugfix on 0.2.3.1-alpha.
4732 - Don't complain about bootstrapping problems while hibernating.
4733 These complaints reflect a general code problem, but not one
4734 with any problematic effects (no connections are actually
4735 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
4737 o Documentation fixes:
4738 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
4739 names match. Fixes bug 7768.
4740 - Make the torify manpage no longer refer to tsocks; torify hasn't
4741 supported tsocks since 0.2.3.14-alpha.
4742 - Make the tor manpage no longer reference tsocks.
4743 - Fix the GeoIPExcludeUnknown documentation to refer to
4744 ExcludeExitNodes rather than the currently nonexistent
4745 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
4748 - The tor-tsocks.conf is no longer distributed or installed. We
4749 recommend that tsocks users use torsocks instead. Resolves
4753 Changes in version 0.2.4.11-alpha - 2013-03-11
4754 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
4755 more robust, makes hidden service authentication work again, and
4756 resolves a DPI fingerprint for Tor's SSL transport.
4758 o Major features (directory authorities):
4759 - Directory authorities now support a new consensus method (17)
4760 where they cap the published bandwidth of servers for which
4761 insufficient bandwidth measurements exist. Fixes part of bug 2286.
4762 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
4763 serve any v2 directory information. Now we can test disabling the
4764 old deprecated v2 directory format, and see whether doing so has
4765 any effect on network load. Begins to fix bug 6783.
4766 - Directory authorities now include inside each vote a statement of
4767 the performance thresholds they used when assigning flags.
4768 Implements ticket 8151.
4770 o Major bugfixes (directory authorities):
4771 - Stop marking every relay as having been down for one hour every
4772 time we restart a directory authority. These artificial downtimes
4773 were messing with our Stable and Guard flag calculations. Fixes
4774 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
4776 o Major bugfixes (hidden services):
4777 - Allow hidden service authentication to succeed again. When we
4778 refactored the hidden service introduction code back
4779 in 0.2.4.1-alpha, we didn't update the code that checks
4780 whether authentication information is present, causing all
4781 authentication checks to return "false". Fix for bug 8207; bugfix
4782 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
4784 o Minor features (relays, bridges):
4785 - Make bridge relays check once a minute for whether their IP
4786 address has changed, rather than only every 15 minutes. Resolves
4788 - Refactor resolve_my_address() so it returns the method by which we
4789 decided our public IP address (explicitly configured, resolved from
4790 explicit hostname, guessed from interfaces, learned by gethostname).
4791 Now we can provide more helpful log messages when a relay guesses
4792 its IP address incorrectly (e.g. due to unexpected lines in
4793 /etc/hosts). Resolves ticket 2267.
4794 - Teach bridge-using clients to avoid 0.2.2 bridges when making
4795 microdescriptor-related dir requests, and only fall back to normal
4796 descriptors if none of their bridges can handle microdescriptors
4797 (as opposed to the fix in ticket 4013, which caused them to fall
4798 back to normal descriptors if *any* of their bridges preferred
4799 them). Resolves ticket 4994.
4800 - Randomize the lifetime of our SSL link certificate, so censors can't
4801 use the static value for filtering Tor flows. Resolves ticket 8443;
4802 related to ticket 4014 which was included in 0.2.2.33.
4803 - Support a new version of the link protocol that allows 4-byte circuit
4804 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
4805 a possible resource exhaustion issue. Closes ticket 7351; implements
4808 o Minor features (portability):
4809 - Tweak the curve25519-donna*.c implementations to tolerate systems
4810 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
4811 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
4812 the signs of types during autoconf. This is better than our old
4813 approach, which didn't work when cross-compiling.
4814 - Detect the sign of enum values, rather than assuming that MSC is the
4815 only compiler where enum types are all signed. Fixes bug 7727;
4816 bugfix on 0.2.4.10-alpha.
4818 o Minor features (other):
4819 - Say "KBytes" rather than "KB" in the man page (for various values
4820 of K), to further reduce confusion about whether Tor counts in
4821 units of memory or fractions of units of memory. Resolves ticket 7054.
4822 - Clear the high bit on curve25519 public keys before passing them to
4823 our backend, in case we ever wind up using a backend that doesn't do
4824 so itself. If we used such a backend, and *didn't* clear the high bit,
4825 we could wind up in a situation where users with such backends would
4826 be distinguishable from users without. Fixes bug 8121; bugfix on
4828 - Update to the March 6 2013 Maxmind GeoLite Country database.
4830 o Minor bugfixes (clients):
4831 - When we receive a RELAY_END cell with the reason DONE, or with no
4832 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
4833 status as "connection refused". Previously we reported these cases
4834 as success but then immediately closed the connection. Fixes bug
4835 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
4836 - Downgrade an assertion in connection_ap_expire_beginning to an
4837 LD_BUG message. The fix for bug 8024 should prevent this message
4838 from displaying, but just in case, a warn that we can diagnose
4839 is better than more assert crashes. Fixes bug 8065; bugfix on
4841 - Lower path use bias thresholds to .80 for notice and .60 for warn.
4842 Also make the rate limiting flags for the path use bias log messages
4843 independent from the original path bias flags. Fixes bug 8161;
4844 bugfix on 0.2.4.10-alpha.
4846 o Minor bugfixes (relays):
4847 - Stop trying to resolve our hostname so often (e.g. every time we
4848 think about doing a directory fetch). Now we reuse the cached
4849 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
4850 and 2410 (bugfix on 0.1.2.2-alpha).
4851 - Stop sending a stray "(null)" in some cases for the server status
4852 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
4854 - When choosing which stream on a formerly stalled circuit to wake
4855 first, make better use of the platform's weak RNG. Previously,
4856 we had been using the % ("modulo") operator to try to generate a
4857 1/N chance of picking each stream, but this behaves badly with
4858 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
4860 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
4861 Irix's random() only return 15 bits; Solaris's random() returns more
4862 bits but its RAND_MAX says it only returns 15, and so on. Motivated
4863 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
4865 o Minor bugfixes (directory authorities):
4866 - Directory authorities now use less space when formatting identical
4867 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
4870 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
4871 - Avoid leaking memory if we fail to compute a consensus signature
4872 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
4873 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
4875 - Fix a memory leak during safe-cookie controller authentication.
4876 Bugfix on 0.2.3.13-alpha.
4877 - Avoid memory leak of IPv6 policy content if we fail to format it into
4878 a router descriptor. Bugfix on 0.2.4.7-alpha.
4880 o Minor bugfixes (other code correctness issues):
4881 - Avoid a crash if we fail to generate an extrainfo descriptor.
4882 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
4884 - When detecting the largest possible file descriptor (in order to
4885 close all file descriptors when launching a new program), actually
4886 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
4887 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
4889 - Fix a copy-and-paste error when adding a missing A1 to a routerset
4890 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
4891 Bugfix on 0.2.4.10-alpha.
4892 - Fix an impossible-to-trigger integer overflow when estimating how
4893 long our onionskin queue would take. (This overflow would require us
4894 to accept 4 million onionskins before processing 100 of them.) Fixes
4895 bug 8210; bugfix on 0.2.4.10-alpha.
4897 o Code simplification and refactoring:
4898 - Add a wrapper function for the common "log a message with a
4902 Changes in version 0.2.4.10-alpha - 2013-02-04
4903 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
4904 certain attacks that flood the network with relays; changes the queue
4905 for circuit create requests from a sized-based limit to a time-based
4906 limit; resumes building with MSVC on Windows; and fixes a wide variety
4909 o Major bugfixes (directory authority):
4910 - When computing directory thresholds, ignore any rejected-as-sybil
4911 nodes during the computation so that they can't influence Fast,
4912 Guard, etc. (We should have done this for proposal 109.) Fixes
4914 - When marking a node as a likely sybil, reset its uptime metrics
4915 to zero, so that it cannot time towards getting marked as Guard,
4916 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
4920 - When a TLS write is partially successful but incomplete, remember
4921 that the flushed part has been flushed, and notice that bytes were
4922 actually written. Reported and fixed pseudonymously. Fixes bug
4923 7708; bugfix on Tor 0.1.0.5-rc.
4924 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
4925 ID: these could be used to create unexpected streams and circuits
4926 which would count as "present" to some parts of Tor but "absent"
4927 to others, leading to zombie circuits and streams or to a bandwidth
4928 denial-of-service. Fixes bug 7889; bugfix on every released version
4929 of Tor. Reported by "oftc_must_be_destroyed".
4930 - Rename all macros in our local copy of queue.h to begin with "TOR_".
4931 This change seems the only good way to permanently prevent conflicts
4932 with queue.h on various operating systems. Fixes bug 8107; bugfix
4935 o Major features (relay):
4936 - Instead of limiting the number of queued onionskins (aka circuit
4937 create requests) to a fixed, hard-to-configure number, we limit
4938 the size of the queue based on how many we expect to be able to
4939 process in a given amount of time. We estimate the time it will
4940 take to process an onionskin based on average processing time
4941 of previous onionskins. Closes ticket 7291. You'll never have to
4942 configure MaxOnionsPending again.
4944 o Major features (portability):
4945 - Resume building correctly with MSVC and Makefile.nmake. This patch
4946 resolves numerous bugs and fixes reported by ultramage, including
4947 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
4948 - Make the ntor and curve25519 code build correctly with MSVC.
4949 Fix on 0.2.4.8-alpha.
4952 - When directory authorities are computing thresholds for flags,
4953 never let the threshold for the Fast flag fall below 4096
4954 bytes. Also, do not consider nodes with extremely low bandwidths
4955 when deciding thresholds for various directory flags. This change
4956 should raise our threshold for Fast relays, possibly in turn
4957 improving overall network performance; see ticket 1854. Resolves
4959 - The Tor client now ignores sub-domain components of a .onion
4960 address. This change makes HTTP "virtual" hosting
4961 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
4962 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
4963 hosted on the same hidden service. Implements proposal 204.
4964 - We compute the overhead from passing onionskins back and forth to
4965 cpuworkers, and report it when dumping statistics in response to
4966 SIGUSR1. Supports ticket 7291.
4968 o Minor features (path selection):
4969 - When deciding whether we have enough descriptors to build circuits,
4970 instead of looking at raw relay counts, look at which fraction
4971 of (bandwidth-weighted) paths we're able to build. This approach
4972 keeps clients from building circuits if their paths are likely to
4973 stand out statistically. The default fraction of paths needed is
4974 taken from the consensus directory; you can override it with the
4975 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
4976 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
4977 and we have GeoIP information, also exclude all nodes with unknown
4978 countries "??" and "A1". This behavior is controlled by the
4979 new GeoIPExcludeUnknown option: you can make such nodes always
4980 excluded with "GeoIPExcludeUnknown 1", and disable the feature
4981 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
4982 gets you the default behavior. Implements feature 7706.
4983 - Path Use Bias: Perform separate accounting for successful circuit
4984 use. Keep separate statistics on stream attempt rates versus stream
4985 success rates for each guard. Provide configurable thresholds to
4986 determine when to emit log messages or disable use of guards that
4987 fail too many stream attempts. Resolves ticket 7802.
4989 o Minor features (log messages):
4990 - When learning a fingerprint for a bridge, log its corresponding
4991 transport type. Implements ticket 7896.
4992 - Improve the log message when "Bug/attack: unexpected sendme cell
4993 from client" occurs, to help us track bug 8093.
4996 - Remove a couple of extraneous semicolons that were upsetting the
4997 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
4998 bugfix on 0.2.2.1-alpha.
4999 - Remove a source of rounding error during path bias count scaling;
5000 don't count cannibalized circuits as used for path bias until we
5001 actually try to use them; and fix a circuit_package_relay_cell()
5002 warning message about n_chan==NULL. Fixes bug 7802.
5003 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
5004 actually link against nacl when we're configured to use it. Fixes
5005 bug 7972; bugfix on 0.2.4.8-alpha.
5006 - Compile correctly with the --disable-curve25519 option. Fixes
5007 bug 8153; bugfix on 0.2.4.8-alpha.
5009 o Build improvements:
5010 - Do not report status verbosely from autogen.sh unless the -v flag
5011 is specified. Fixes issue 4664. Patch from Onizuka.
5012 - Replace all calls to snprintf() outside of src/ext with
5013 tor_snprintf(). Also remove the #define to replace snprintf with
5014 _snprintf on Windows; they have different semantics, and all of
5015 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
5016 - Try to detect if we are ever building on a platform where
5017 memset(...,0,...) does not set the value of a double to 0.0. Such
5018 platforms are permitted by the C standard, though in practice
5019 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
5020 currently support them, but it's better to detect them and fail
5021 than to perform erroneously.
5024 - Stop exporting estimates of v2 and v3 directory traffic shares
5025 in extrainfo documents. They were unneeded and sometimes inaccurate.
5026 Also stop exporting any v2 directory request statistics. Resolves
5028 - Drop support for detecting and warning about versions of Libevent
5029 before 1.3e. Nothing reasonable ships with them any longer;
5030 warning the user about them shouldn't be needed. Resolves ticket
5033 o Code simplifications and refactoring:
5034 - Rename "isin" functions to "contains", for grammar. Resolves
5036 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
5037 with the natural logarithm function from the system libm. Resolves
5041 Changes in version 0.2.4.9-alpha - 2013-01-15
5042 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
5046 - Fix backward compatibility logic when receiving an embedded ntor
5047 handshake tunneled in a CREATE cell. This clears up the "Bug:
5048 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
5052 Changes in version 0.2.4.8-alpha - 2013-01-14
5053 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
5054 risks, adds a new stronger and faster circuit handshake, and offers
5055 stronger and faster link encryption when both sides support it.
5058 - Preliminary support for directory guards (proposal 207): when
5059 possible, clients now use their entry guards for non-anonymous
5060 directory requests. This can help prevent client enumeration. Note
5061 that this behavior only works when we have a usable consensus
5062 directory, and when options about what to download are more or less
5063 standard. In the future we should re-bootstrap from our guards,
5064 rather than re-bootstrapping from the preconfigured list of
5065 directory sources that ships with Tor. Resolves ticket 6526.
5066 - Tor relays and clients now support a better CREATE/EXTEND cell
5067 format, allowing the sender to specify multiple address, identity,
5068 and handshake types. Implements Robert Ransom's proposal 200;
5071 o Major features (new circuit handshake):
5072 - Tor now supports a new circuit extension handshake designed by Ian
5073 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
5074 circuit extension handshake, later called "TAP", was a bit slow
5075 (especially on the relay side), had a fragile security proof, and
5076 used weaker keys than we'd now prefer. The new circuit handshake
5077 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
5078 function, making it significantly more secure than the older
5079 handshake, and significantly faster. Tor can use one of two built-in
5080 pure-C curve25519-donna implementations by Adam Langley, or it
5081 can link against the "nacl" library for a tuned version if present.
5083 The built-in version is very fast for 64-bit systems when building
5084 with GCC. The built-in 32-bit version is still faster than the
5085 old TAP protocol, but using libnacl is better on most such hosts.
5087 Clients don't currently use this protocol by default, since
5088 comparatively few clients support it so far. To try it, set
5089 UseNTorHandshake to 1.
5091 Implements proposal 216; closes ticket 7202.
5093 o Major features (better link encryption):
5094 - Relays can now enable the ECDHE TLS ciphersuites when available
5095 and appropriate. These ciphersuites let us negotiate forward-secure
5096 TLS secret keys more safely and more efficiently than with our
5097 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
5098 public relays prefer the (faster) P224 group, and bridges prefer
5099 the (more common) P256 group; you can override this with the
5102 Enabling these ciphers was a little tricky, since for a long time,
5103 clients had been claiming to support them without actually doing
5104 so, in order to foil fingerprinting. But with the client-side
5105 implementation of proposal 198 in 0.2.3.17-beta, clients can now
5106 match the ciphers from recent Firefox versions *and* list the
5107 ciphers they actually mean, so relays can believe such clients
5108 when they advertise ECDHE support in their TLS ClientHello messages.
5110 This feature requires clients running 0.2.3.17-beta or later,
5111 and requires both sides to be running OpenSSL 1.0.0 or later
5112 with ECC support. OpenSSL 1.0.1, with the compile-time option
5113 "enable-ec_nistp_64_gcc_128", is highly recommended.
5115 Implements the relay side of proposal 198; closes ticket 7200.
5118 - Avoid crashing when, as a relay without IPv6-exit support, a
5119 client insists on getting an IPv6 address or nothing. Fixes bug
5120 7814; bugfix on 0.2.4.7-alpha.
5123 - Improve circuit build timeout handling for hidden services.
5124 In particular: adjust build timeouts more accurately depending
5125 upon the number of hop-RTTs that a particular circuit type
5126 undergoes. Additionally, launch intro circuits in parallel
5127 if they timeout, and take the first one to reply as valid.
5128 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
5129 separate error codes; or at least, don't break for that reason.
5130 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
5131 - Update to the January 2 2013 Maxmind GeoLite Country database.
5133 o Minor features (testing):
5134 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
5135 (P-256) Diffie-Hellman handshakes to src/or/bench.
5136 - Add benchmark functions to test onion handshake performance.
5138 o Minor features (path bias detection):
5139 - Alter the Path Bias log messages to be more descriptive in terms
5140 of reporting timeouts and other statistics.
5141 - Create three levels of Path Bias log messages, as opposed to just
5142 two. These are configurable via consensus as well as via the torrc
5143 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
5144 The default values are 0.70, 0.50, and 0.30 respectively.
5145 - Separate the log message levels from the decision to drop guards,
5146 which also is available via torrc option PathBiasDropGuards.
5147 PathBiasDropGuards still defaults to 0 (off).
5148 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
5149 in combination with PathBiasExtremeRate.
5150 - Increase the default values for PathBiasScaleThreshold and
5151 PathBiasCircThreshold from (200, 20) to (300, 150).
5152 - Add in circuit usage accounting to path bias. If we try to use a
5153 built circuit but fail for any reason, it counts as path bias.
5154 Certain classes of circuits where the adversary gets to pick your
5155 destination node are exempt from this accounting. Usage accounting
5156 can be specifically disabled via consensus parameter or torrc.
5157 - Convert all internal path bias state to double-precision floating
5158 point, to avoid roundoff error and other issues.
5159 - Only record path bias information for circuits that have completed
5160 *two* hops. Assuming end-to-end tagging is the attack vector, this
5161 makes us more resilient to ambient circuit failure without any
5162 detection capability loss.
5164 o Minor bugfixes (log messages):
5165 - Rate-limit the "No circuits are opened. Relaxed timeout for a
5166 circuit with channel state open..." message to once per hour to
5167 keep it from filling the notice logs. Mitigates bug 7799 but does
5168 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
5169 - Avoid spurious warnings when configuring multiple client ports of
5170 which only some are nonlocal. Previously, we had claimed that some
5171 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
5174 o Code simplifications and refactoring:
5175 - Get rid of a couple of harmless clang warnings, where we compared
5176 enums to ints. These warnings are newly introduced in clang 3.2.
5177 - Split the onion.c file into separate modules for the onion queue
5178 and the different handshakes it supports.
5179 - Remove the marshalling/unmarshalling code for sending requests to
5180 cpuworkers over a socket, and instead just send structs. The
5181 recipient will always be the same Tor binary as the sender, so
5182 any encoding is overkill.
5185 Changes in version 0.2.4.7-alpha - 2012-12-24
5186 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
5187 directory mirrors for more robust bootstrapping; fixes more issues where
5188 clients with changing network conditions refuse to make any circuits;
5189 adds initial support for exiting to IPv6 addresses; resumes being able
5190 to update our GeoIP database, and includes the geoip6 file this time;
5191 turns off the client-side DNS cache by default due to privacy risks;
5192 and fixes a variety of other issues.
5194 o Major features (client resilience):
5195 - Add a new "FallbackDir" torrc option to use when we can't use
5196 a directory mirror from the consensus (either because we lack a
5197 consensus, or because they're all down). Currently, all authorities
5198 are fallbacks by default, and there are no other default fallbacks,
5199 but that will change. This option will allow us to give clients a
5200 longer list of servers to try to get a consensus from when first
5201 connecting to the Tor network, and thereby reduce load on the
5202 directory authorities. Implements proposal 206, "Preconfigured
5203 directory sources for bootstrapping". We also removed the old
5204 "FallbackNetworkstatus" option, since we never got it working well
5205 enough to use it. Closes bug 572.
5206 - If we have no circuits open, use a relaxed timeout (the
5207 95-percentile cutoff) until a circuit succeeds. This heuristic
5208 should allow Tor to succeed at building circuits even when the
5209 network connection drastically changes. Should help with bug 3443.
5211 o Major features (IPv6):
5212 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
5213 connectivity, then set the IPv6Exit flag to 1. Also make sure your
5214 exit policy reads as you would like: the address * applies to all
5215 address families, whereas *4 is IPv4 address only, and *6 is IPv6
5216 addresses only. On the client side, you'll need to wait until the
5217 authorities have upgraded, wait for enough exits to support IPv6,
5218 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
5219 ticket 5547, implements proposal 117 as revised in proposal 208.
5221 We DO NOT recommend that clients with actual anonymity needs start
5222 using IPv6 over Tor yet, since not enough exits support it yet.
5224 o Major features (geoip database):
5225 - Maxmind began labelling Tor relays as being in country "A1",
5226 which breaks by-country node selection inside Tor. Now we use a
5227 script to replace "A1" ("Anonymous Proxy") entries in our geoip
5228 file with real country codes. This script fixes about 90% of "A1"
5229 entries automatically and uses manual country code assignments to
5230 fix the remaining 10%. See src/config/README.geoip for details.
5231 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
5232 Country database, as modified above.
5234 o Major bugfixes (client-side DNS):
5235 - Turn off the client-side DNS cache by default. Updating and using
5236 the DNS cache is now configurable on a per-client-port
5237 level. SOCKSPort, DNSPort, etc lines may now contain
5238 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
5239 cache these types of DNS answers when we receive them from an
5240 exit node in response to an application request on this port, and
5241 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
5242 cached DNS answers of these types, we shouldn't use them. It's
5243 potentially risky to use cached DNS answers at the client, since
5244 doing so can indicate to one exit what answers we've gotten
5245 for DNS lookups in the past. With IPv6, this becomes especially
5246 problematic. Using cached DNS answers for requests on the same
5247 circuit would present less linkability risk, since all traffic
5248 on a circuit is already linkable, but it would also provide
5249 little performance benefit: the exit node caches DNS replies
5250 too. Implements a simplified version of Proposal 205. Implements
5253 o Major bugfixes (other):
5254 - Alter circuit build timeout measurement to start at the point
5255 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
5256 initialization). This should make our timeout measurements more
5257 uniform. Previously, we were sometimes including ORconn setup time
5258 in our circuit build time measurements. Should resolve bug 3443.
5259 - Fix an assertion that could trigger in hibernate_go_dormant() when
5260 closing an or_connection_t: call channel_mark_for_close() rather
5261 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
5263 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
5264 7655; bugfix on 0.2.4.6-alpha.
5267 - Add a new torrc option "ServerTransportListenAddr" to let bridge
5268 operators select the address where their pluggable transports will
5269 listen for connections. Resolves ticket 7013.
5270 - Allow an optional $ before the node identity digest in the
5271 controller command GETINFO ns/id/<identity>, for consistency with
5272 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
5273 - Log packaged cell fullness as part of the heartbeat message.
5274 Diagnosis to try to determine the extent of bug 7743.
5276 o Minor features (IPv6):
5277 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
5278 prefer to hand out virtual IPv6 addresses, since there are more of
5279 them and we can't run out. To override this behavior and make IPv4
5280 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
5281 or DNSPort you're using for resolving. Implements ticket 7571.
5282 - AutomapHostsOnResolve responses are now randomized, to avoid
5283 annoying situations where Tor is restarted and applications
5284 connect to the wrong addresses.
5285 - Never try more than 1000 times to pick a new virtual address when
5286 AutomapHostsOnResolve is set. That's good enough so long as we
5287 aren't close to handing out our entire virtual address space;
5288 if you're getting there, it's best to switch to IPv6 virtual
5292 - The ADDRMAP command can no longer generate an ill-formed error
5293 code on a failed MAPADDRESS. It now says "internal" rather than
5294 an English sentence fragment with spaces in the middle. Bugfix on
5296 - Fix log messages and comments to avoid saying "GMT" when we mean
5297 "UTC". Fixes bug 6113.
5298 - Compile on win64 using mingw64. Fixes bug 7260; patches from
5300 - Fix a crash when debugging unit tests on Windows: deallocate a
5301 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
5302 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
5305 - The DirServer option is now DirAuthority, for consistency with
5306 current naming patterns. You can still use the old DirServer form.
5308 o Code simplification and refactoring:
5309 - Move the client-side address-map/virtual-address/DNS-cache code
5310 out of connection_edge.c into a new addressmap.c module.
5311 - Remove unused code for parsing v1 directories and "running routers"
5312 documents. Fixes bug 6887.
5315 Changes in version 0.2.3.25 - 2012-11-19
5316 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
5317 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
5318 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
5319 programmer, and friend. Unstinting in his dedication to the cause of
5320 freedom, he inspired and helped many of us as we began our work on
5321 anonymity, and inspires us still. Please honor his memory by writing
5322 software to protect people's freedoms, and by helping others to do so.
5324 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
5325 significantly reduced directory overhead (via microdescriptors),
5326 enormous crypto performance improvements for fast relays on new
5327 enough hardware, a new v3 TLS handshake protocol that can better
5328 resist fingerprinting, support for protocol obfuscation plugins (aka
5329 pluggable transports), better scalability for hidden services, IPv6
5330 support for bridges, performance improvements like allowing clients
5331 to skip the first round-trip on the circuit ("optimistic data") and
5332 refilling token buckets more often, a new "stream isolation" design
5333 to isolate different applications on different circuits, and many
5334 stability, security, and privacy fixes.
5337 - Tor tries to wipe potentially sensitive data after using it, so
5338 that if some subsequent security failure exposes Tor's memory,
5339 the damage will be limited. But we had a bug where the compiler
5340 was eliminating these wipe operations when it decided that the
5341 memory was no longer visible to a (correctly running) program,
5342 hence defeating our attempt at defense in depth. We fix that
5343 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
5344 is unlikely to optimize away. Future versions of Tor may use
5345 a less ridiculously heavy approach for this. Fixes bug 7352.
5346 Reported in an article by Andrey Karpov.
5349 - Fix a harmless bug when opting against publishing a relay descriptor
5350 because DisableNetwork is set. Fixes bug 7464; bugfix on
5354 Changes in version 0.2.4.6-alpha - 2012-11-13
5355 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
5356 makes our defense-in-depth memory wiping more reliable, and begins to
5357 count IPv6 addresses in bridge statistics,
5360 - Fix an assertion failure that could occur when closing a connection
5361 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
5363 - Tor tries to wipe potentially sensitive data after using it, so
5364 that if some subsequent security failure exposes Tor's memory,
5365 the damage will be limited. But we had a bug where the compiler
5366 was eliminating these wipe operations when it decided that the
5367 memory was no longer visible to a (correctly running) program,
5368 hence defeating our attempt at defense in depth. We fix that
5369 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
5370 is unlikely to optimize away. Future versions of Tor may use
5371 a less ridiculously heavy approach for this. Fixes bug 7352.
5372 Reported in an article by Andrey Karpov.
5375 - Add GeoIP database for IPv6 addresses. The new config option
5377 - Bridge statistics now count bridge clients connecting over IPv6:
5378 bridge statistics files now list "bridge-ip-versions" and
5379 extra-info documents list "geoip6-db-digest". The control protocol
5380 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
5381 implementation by "shkoo", addressing ticket 5055.
5384 - Warn when we are binding low ports when hibernation is enabled;
5385 previously we had warned when we were _advertising_ low ports with
5386 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
5387 - Fix a harmless bug when opting against publishing a relay descriptor
5388 because DisableNetwork is set. Fixes bug 7464; bugfix on
5390 - Add warning message when a managed proxy dies during configuration.
5391 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
5392 - Fix a linking error when building tor-fw-helper without miniupnp.
5393 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
5394 - Check for closing an or_connection_t without going through correct
5395 channel functions; emit a warning and then call
5396 connection_or_close_for_error() so we don't assert as in bugs 7212
5398 - Compile correctly on compilers without C99 designated initializer
5399 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
5400 - Avoid a possible assert that can occur when channel_send_destroy() is
5401 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
5402 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
5403 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
5404 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
5405 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
5407 o Code simplification and refactoring:
5408 - Start using OpenBSD's implementation of queue.h, so that we don't
5409 need to hand-roll our own pointer and list structures whenever we
5410 need them. (We can't rely on a sys/queue.h, since some operating
5411 systems don't have them, and the ones that do have them don't all
5412 present the same extensions.)
5415 Changes in version 0.2.4.5-alpha - 2012-10-25
5416 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
5417 two important security vulnerabilities that could lead to remotely
5418 triggerable relay crashes, fix a major bug that was preventing clients
5419 from choosing suitable exit nodes, and refactor some of our code.
5421 o Major bugfixes (security, also in 0.2.3.24-rc):
5422 - Fix a group of remotely triggerable assertion failures related to
5423 incorrect link protocol negotiation. Found, diagnosed, and fixed
5424 by "some guy from France". Fix for CVE-2012-2250; bugfix on
5426 - Fix a denial of service attack by which any directory authority
5427 could crash all the others, or by which a single v2 directory
5428 authority could crash everybody downloading v2 directory
5429 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
5431 o Major bugfixes (also in 0.2.3.24-rc):
5432 - When parsing exit policy summaries from microdescriptors, we had
5433 previously been ignoring the last character in each one, so that
5434 "accept 80,443,8080" would be treated by clients as indicating
5435 a node that allows access to ports 80, 443, and 808. That would
5436 lead to clients attempting connections that could never work,
5437 and ignoring exit nodes that would support their connections. Now
5438 clients parse these exit policy summaries correctly. Fixes bug 7192;
5439 bugfix on 0.2.3.1-alpha.
5441 o Minor bugfixes (also in 0.2.3.24-rc):
5442 - Clients now consider the ClientRejectInternalAddresses config option
5443 when using a microdescriptor consensus stanza to decide whether
5444 an exit relay would allow exiting to an internal address. Fixes
5445 bug 7190; bugfix on 0.2.3.1-alpha.
5448 - Only disable TLS session ticket support when running as a TLS
5449 server. Now clients will blend better with regular Firefox
5450 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
5452 o Code simplification and refactoring:
5453 - Start using OpenBSD's implementation of queue.h (originally by
5455 - Move the entry node code from circuitbuild.c to its own file.
5456 - Move the circuit build timeout tracking code from circuitbuild.c
5460 Changes in version 0.2.3.24-rc - 2012-10-25
5461 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
5462 could lead to remotely triggerable relay crashes, and fixes
5463 a major bug that was preventing clients from choosing suitable exit
5466 o Major bugfixes (security):
5467 - Fix a group of remotely triggerable assertion failures related to
5468 incorrect link protocol negotiation. Found, diagnosed, and fixed
5469 by "some guy from France". Fix for CVE-2012-2250; bugfix on
5471 - Fix a denial of service attack by which any directory authority
5472 could crash all the others, or by which a single v2 directory
5473 authority could crash everybody downloading v2 directory
5474 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
5477 - When parsing exit policy summaries from microdescriptors, we had
5478 previously been ignoring the last character in each one, so that
5479 "accept 80,443,8080" would be treated by clients as indicating
5480 a node that allows access to ports 80, 443, and 808. That would
5481 lead to clients attempting connections that could never work,
5482 and ignoring exit nodes that would support their connections. Now
5483 clients parse these exit policy summaries correctly. Fixes bug 7192;
5484 bugfix on 0.2.3.1-alpha.
5487 - Clients now consider the ClientRejectInternalAddresses config option
5488 when using a microdescriptor consensus stanza to decide whether
5489 an exit relay would allow exiting to an internal address. Fixes
5490 bug 7190; bugfix on 0.2.3.1-alpha.
5493 Changes in version 0.2.4.4-alpha - 2012-10-20
5494 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
5495 vulnerability introduced by a change in OpenSSL, fixes a remotely
5496 triggerable assert, and adds new channel_t and circuitmux_t abstractions
5497 that will make it easier to test new connection transport and cell
5498 scheduling algorithms.
5500 o New directory authorities (also in 0.2.3.23-rc):
5501 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
5502 authority. Closes ticket 5749.
5504 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
5505 - Disable TLS session tickets. OpenSSL's implementation was giving
5506 our TLS session keys the lifetime of our TLS context objects, when
5507 perfect forward secrecy would want us to discard anything that
5508 could decrypt a link connection as soon as the link connection
5509 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
5510 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
5511 - Discard extraneous renegotiation attempts once the V3 link
5512 protocol has been initiated. Failure to do so left us open to
5513 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
5514 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
5516 o Internal abstraction features:
5517 - Introduce new channel_t abstraction between circuits and
5518 or_connection_t to allow for implementing alternate OR-to-OR
5519 transports. A channel_t is an abstract object which can either be a
5520 cell-bearing channel, which is responsible for authenticating and
5521 handshaking with the remote OR and transmitting cells to and from
5522 it, or a listening channel, which spawns new cell-bearing channels
5523 at the request of remote ORs. Implements part of ticket 6465.
5524 - Also new is the channel_tls_t subclass of channel_t, adapting it
5525 to the existing or_connection_t code. The V2/V3 protocol handshaking
5526 code which formerly resided in command.c has been moved below the
5527 channel_t abstraction layer and may be found in channeltls.c now.
5528 Implements the rest of ticket 6465.
5529 - Introduce new circuitmux_t storing the queue of circuits for
5530 a channel; this encapsulates and abstracts the queue logic and
5531 circuit selection policy, and allows the latter to be overridden
5532 easily by switching out a policy object. The existing EWMA behavior
5533 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
5535 o Required libraries:
5536 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
5537 strongly recommended.
5540 - Warn users who run hidden services on a Tor client with
5541 UseEntryGuards disabled that their hidden services will be
5542 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
5543 attack which motivated Tor to support entry guards in the first
5544 place). Resolves ticket 6889.
5545 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
5546 dhill. Resolves ticket 6982.
5547 - Option OutboundBindAddress can be specified multiple times and
5548 accepts IPv6 addresses. Resolves ticket 6876.
5550 o Minor bugfixes (also in 0.2.3.23-rc):
5551 - Don't serve or accept v2 hidden service descriptors over a
5552 relay's DirPort. It's never correct to do so, and disabling it
5553 might make it more annoying to exploit any bugs that turn up in the
5554 descriptor-parsing code. Fixes bug 7149.
5555 - Fix two cases in src/or/transports.c where we were calling
5556 fmt_addr() twice in a parameter list. Bug found by David
5557 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
5558 - Fix memory leaks whenever we logged any message about the "path
5559 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
5560 - When relays refuse a "create" cell because their queue of pending
5561 create cells is too big (typically because their cpu can't keep up
5562 with the arrival rate), send back reason "resource limit" rather
5563 than reason "internal", so network measurement scripts can get a
5564 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
5567 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
5568 - Free some more still-in-use memory at exit, to make hunting for
5569 memory leaks easier. Resolves bug 7029.
5570 - When a Tor client gets a "truncated" relay cell, the first byte of
5571 its payload specifies why the circuit was truncated. We were
5572 ignoring this 'reason' byte when tearing down the circuit, resulting
5573 in the controller not being told why the circuit closed. Now we
5574 pass the reason from the truncated cell to the controller. Bugfix
5575 on 0.1.2.3-alpha; fixes bug 7039.
5576 - Downgrade "Failed to hand off onionskin" messages to "debug"
5577 severity, since they're typically redundant with the "Your computer
5578 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
5579 - Make clients running with IPv6 bridges connect over IPv6 again,
5580 even without setting new config options ClientUseIPv6 and
5581 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
5582 - Use square brackets around IPv6 addresses in numerous places
5583 that needed them, including log messages, HTTPS CONNECT proxy
5584 requests, TransportProxy statefile entries, and pluggable transport
5585 extra-info lines. Fixes bug 7011; patch by David Fifield.
5587 o Code refactoring and cleanup:
5588 - Source files taken from other packages now reside in src/ext;
5589 previously they were scattered around the rest of Tor.
5590 - Avoid use of reserved identifiers in our C code. The C standard
5591 doesn't like us declaring anything that starts with an
5592 underscore, so let's knock it off before we get in trouble. Fix
5593 for bug 1031; bugfix on the first Tor commit.
5596 Changes in version 0.2.3.23-rc - 2012-10-20
5597 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
5598 vulnerability introduced by a change in OpenSSL, and fixes a variety
5599 of smaller bugs in preparation for the release.
5601 o New directory authorities:
5602 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
5603 authority. Closes ticket 5749.
5605 o Major bugfixes (security/privacy):
5606 - Disable TLS session tickets. OpenSSL's implementation was giving
5607 our TLS session keys the lifetime of our TLS context objects, when
5608 perfect forward secrecy would want us to discard anything that
5609 could decrypt a link connection as soon as the link connection
5610 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
5611 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
5612 - Discard extraneous renegotiation attempts once the V3 link
5613 protocol has been initiated. Failure to do so left us open to
5614 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
5615 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
5618 - Fix a possible crash bug when checking for deactivated circuits
5619 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
5620 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
5622 o Minor bugfixes (on 0.2.3.x):
5623 - Fix two cases in src/or/transports.c where we were calling
5624 fmt_addr() twice in a parameter list. Bug found by David
5625 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
5626 - Convert an assert in the pathbias code to a log message. The assert
5627 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
5628 bugfix on 0.2.3.17-beta.
5629 - Fix memory leaks whenever we logged any message about the "path
5630 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
5632 o Minor bugfixes (on 0.2.2.x and earlier):
5633 - Don't serve or accept v2 hidden service descriptors over a relay's
5634 DirPort. It's never correct to do so, and disabling it might
5635 make it more annoying to exploit any bugs that turn up in the
5636 descriptor-parsing code. Fixes bug 7149.
5637 - When relays refuse a "create" cell because their queue of pending
5638 create cells is too big (typically because their cpu can't keep up
5639 with the arrival rate), send back reason "resource limit" rather
5640 than reason "internal", so network measurement scripts can get a
5641 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
5642 - Correct file sizes when reading binary files on Cygwin, to avoid
5643 a bug where Tor would fail to read its state file. Fixes bug 6844;
5644 bugfix on 0.1.2.7-alpha.
5645 - Avoid undefined behavior when parsing the list of supported
5646 rendezvous/introduction protocols in a hidden service descriptor.
5647 Previously, Tor would have confused (as-yet-unused) protocol version
5648 numbers greater than 32 with lower ones on many platforms. Fixes
5649 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
5651 o Documentation fixes:
5652 - Clarify that hidden services are TCP only. Fixes bug 6024.
5655 Changes in version 0.2.4.3-alpha - 2012-09-22
5656 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
5657 assertion, resumes letting relays test reachability of their DirPort,
5658 and cleans up a bunch of smaller bugs.
5661 - Fix an assertion failure in tor_timegm() that could be triggered
5662 by a badly formatted directory object. Bug found by fuzzing with
5663 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5666 - Fix a possible crash bug when checking for deactivated circuits
5667 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
5668 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
5669 - Allow routers to detect that their own DirPorts are running. When
5670 we removed support for versions_supports_begindir, we also
5671 accidentally removed the mechanism we used to self-test our
5672 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
5673 bugfix on 0.2.4.2-alpha.
5675 o Security features:
5676 - Switch to a completely time-invariant approach for picking nodes
5677 weighted by bandwidth. Our old approach would run through the
5678 part of the loop after it had made its choice slightly slower
5679 than it ran through the part of the loop before it had made its
5680 choice. Addresses ticket 6538.
5681 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
5682 by tor2web clients allows hidden services to identify tor2web
5683 clients through their repeated selection of the same rendezvous
5684 and introduction point circuit endpoints (their guards). Resolves
5688 - Enable Tor to read configuration, state, and key information from
5689 a FIFO. Previously Tor would only read from files with a positive
5690 stat.st_size. Code from meejah; fixes bug 6044.
5693 - Correct file sizes when reading binary files on Cygwin, to avoid
5694 a bug where Tor would fail to read its state file. Fixes bug 6844;
5695 bugfix on 0.1.2.7-alpha.
5696 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
5697 bugfix on 0.2.0.3-alpha.
5698 - When complaining about a client port on a public address, log
5699 which address we're complaining about. Fixes bug 4020; bugfix on
5700 0.2.3.3-alpha. Patch by Tom Fitzhenry.
5701 - Convert an assert in the pathbias code to a log message. The assert
5702 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
5703 bugfix on 0.2.3.17-beta.
5704 - Our new buildsystem was overzealous about rebuilding manpages: it
5705 would rebuild them all whenever any one of them changed. Now our
5706 dependency checking should be correct. Fixes bug 6843; bugfix on
5708 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
5709 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
5710 - Correct log printout about which address family is preferred
5711 when connecting to a bridge with both an IPv4 and IPv6 OR port.
5712 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
5714 o Minor bugfixes (code cleanliness):
5715 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
5716 with large values. This situation was untriggered, but nevertheless
5717 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
5718 - Reject consensus votes with more than 64 known-flags. We aren't even
5719 close to that limit yet, and our code doesn't handle it correctly.
5720 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
5721 - Avoid undefined behavior when parsing the list of supported
5722 rendezvous/introduction protocols in a hidden service descriptor.
5723 Previously, Tor would have confused (as-yet-unused) protocol version
5724 numbers greater than 32 with lower ones on many platforms. Fixes
5725 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
5726 - Fix handling of rendezvous client authorization types over 8.
5727 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
5728 - Fix building with older versions of GCC (2.95, for one) that don't
5729 like preprocessor directives inside macro arguments. Found by
5730 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
5731 - Switch weighted node selection rule from using a list of doubles
5732 to using a list of int64_t. This change should make the process
5733 slightly easier to debug and maintain. Needed to finish ticket 6538.
5735 o Code simplification and refactoring:
5736 - Move the generic "config" code into a new file, and have "config.c"
5737 hold only torrc- and state-related code. Resolves ticket 6823.
5738 - Move the core of our "choose a weighted element at random" logic
5739 into its own function, and give it unit tests. Now the logic is
5740 testable, and a little less fragile too.
5741 - Removed the testing_since field of node_t, which hasn't been used
5742 for anything since 0.2.0.9-alpha.
5744 o Documentation fixes:
5745 - Clarify that hidden services are TCP only. Fixes bug 6024.
5746 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
5750 Changes in version 0.2.3.22-rc - 2012-09-11
5751 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
5755 - Fix an assertion failure in tor_timegm() that could be triggered
5756 by a badly formatted directory object. Bug found by fuzzing with
5757 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5760 - Avoid segfault when starting up having run with an extremely old
5761 version of Tor and parsing its state file. Fixes bug 6801; bugfix
5765 Changes in version 0.2.2.39 - 2012-09-11
5766 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
5770 - Fix an assertion failure in tor_timegm() that could be triggered
5771 by a badly formatted directory object. Bug found by fuzzing with
5772 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5773 - Do not crash when comparing an address with port value 0 to an
5774 address policy. This bug could have been used to cause a remote
5775 assertion failure by or against directory authorities, or to
5776 allow some applications to crash clients. Fixes bug 6690; bugfix
5780 Changes in version 0.2.4.2-alpha - 2012-09-10
5781 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
5782 raises the default rate limiting even more, and makes the bootstrapping
5783 log messages less noisy.
5786 - Automatically forward the TCP ports of pluggable transport
5787 proxies using tor-fw-helper if PortForwarding is enabled. Implements
5791 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
5792 to 1GB/1GB. The previous defaults were intended to be "basically
5793 infinite", but it turns out they're now limiting our 100mbit+
5794 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
5795 last time we raised it).
5798 - Detect when we're running with a version of OpenSSL other than the
5799 one we compiled with. This has occasionally given people hard-to-
5801 - Log fewer lines at level "notice" about our OpenSSL and Libevent
5802 versions and capabilities when everything is going right. Resolves
5803 part of ticket 6736.
5804 - Directory authorities no long accept descriptors for any version of
5805 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
5806 These versions are insecure, unsupported, or both. Implements
5810 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
5811 to start with a triple-underscore so the controller won't touch it.
5812 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
5813 - Avoid segfault when starting up having run with an extremely old
5814 version of Tor and parsing its state file. Fixes bug 6801; bugfix
5816 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
5817 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
5818 - Don't follow the NULL pointer if microdescriptor generation fails.
5819 (This does not appear to be triggerable, but it's best to be safe.)
5820 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
5821 - Fix mis-declared dependencies on src/common/crypto.c and
5822 src/or/tor_main.c that could break out-of-tree builds under some
5823 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
5824 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
5825 6778; bugfix on 0.2.4.1-alpha.
5826 - Fix a harmless (in this case) build warning for implicitly
5827 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
5830 - Now that all versions before 0.2.2.x are disallowed, we no longer
5831 need to work around their missing features. Thus we can remove a
5832 bunch of compatibility code.
5835 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
5836 TCP ports to forward. In the past it only accepted two ports:
5837 the ORPort and the DirPort.
5840 Changes in version 0.2.4.1-alpha - 2012-09-05
5841 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
5842 bridgedb; lets relays use IPv6 addresses and directory authorities
5843 advertise them; and switches to a cleaner build interface.
5845 This is the first alpha release in a new series, so expect there to
5846 be bugs. Users who would rather test out a more stable branch should
5847 stay with 0.2.3.x for now.
5849 o Major features (bridges):
5850 - Bridges now report the pluggable transports they support to the
5851 bridge authority, so it can pass the supported transports on to
5852 bridgedb and/or eventually do reachability testing. Implements
5855 o Major features (IPv6):
5856 - Bridge authorities now accept IPv6 bridge addresses and include
5857 them in network status documents. Implements ticket 5534.
5858 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
5859 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
5860 to happen. Implements ticket 5535.
5861 - All kind of relays, not just bridges, can now advertise an IPv6
5862 OR port. Implements ticket 6362.
5863 - Directory authorities vote on IPv6 OR ports using the new consensus
5864 method 14. Implements ticket 6363.
5866 o Major features (build):
5867 - Switch to a nonrecursive Makefile structure. Now instead of each
5868 Makefile.am invoking other Makefile.am's, there is a master
5869 Makefile.am that includes the others. This change makes our build
5870 process slightly more maintainable, and improves parallelism for
5871 building with make -j. Original patch by Stewart Smith; various
5872 fixes by Jim Meyering.
5873 - Where available, we now use automake's "silent" make rules by
5874 default, so that warnings are easier to spot. You can get the old
5875 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
5877 o Minor features (code security and spec conformance):
5878 - Clear keys and key-derived material left on the stack in
5879 rendservice.c and rendclient.c. Check return value of
5880 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
5881 These fixes should make us more forward-secure against cold-boot
5882 attacks and the like. Fixes bug 2385.
5883 - Reject EXTEND cells sent to nonexistent streams. According to the
5884 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
5885 we were only checking for stream IDs that were currently in use.
5886 Found while hunting for more instances of bug 6271. Bugfix on
5887 0.0.2pre8, which introduced incremental circuit construction.
5889 o Minor features (streamlining);
5890 - No longer include the "opt" prefix when generating routerinfos
5891 or v2 directories: it has been needless since Tor 0.1.2. Closes
5893 - Remove some now-needless code that tried to aggressively flush
5894 OR connections as data was added to them. Since 0.2.0.1-alpha, our
5895 cell queue logic has saved us from the failure mode that this code
5896 was supposed to prevent. Removing this code will limit the number
5897 of baroque control flow paths through Tor's network logic. Reported
5898 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
5900 o Minor features (controller):
5901 - Add a "GETINFO signal/names" control port command. Implements
5903 - Provide default values for all options via "GETINFO config/defaults".
5904 Implements ticket 4971.
5906 o Minor features (IPv6):
5907 - New config option "AuthDirHasIPv6Connectivity 1" that directory
5908 authorities should set if they have IPv6 connectivity and want to
5909 do reachability tests for IPv6 relays. Implements feature 5974.
5910 - A relay with an IPv6 OR port now sends that address in NETINFO
5911 cells (in addition to its other address). Implements ticket 6364.
5913 o Minor features (log messages):
5914 - Omit the first heartbeat log message, because it never has anything
5915 useful to say, and it clutters up the bootstrapping messages.
5916 Resolves ticket 6758.
5917 - Don't log about reloading the microdescriptor cache at startup. Our
5918 bootstrap warnings are supposed to tell the user when there's a
5919 problem, and our bootstrap notices say when there isn't. Resolves
5920 ticket 6759; bugfix on 0.2.2.6-alpha.
5921 - Don't log "I learned some more directory information" when we're
5922 reading cached directory information. Reserve it for when new
5923 directory information arrives in response to a fetch. Resolves
5925 - Prevent rounding error in path bias counts when scaling
5926 them down, and use the correct scale factor default. Also demote
5927 some path bias related log messages down a level and make others
5928 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
5929 - We no longer warn so much when generating manpages from their
5932 o Code simplifications and refactoring:
5933 - Enhance our internal sscanf replacement so that we can eliminate
5934 the last remaining uses of the system sscanf. (Though those uses
5935 of sscanf were safe, sscanf itself is generally error prone, so
5936 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
5938 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
5939 - Move last_reachable and testing_since from routerinfo_t to node_t.
5940 Implements ticket 5529.
5941 - Add replaycache_t structure, functions and unit tests, then refactor
5942 rend_service_introduce() to be more clear to read, improve, debug,
5943 and test. Resolves bug 6177.
5944 - Finally remove support for malloc_good_size and malloc_usable_size.
5945 We had hoped that these functions would let us eke a little more
5946 memory out of our malloc implementation. Unfortunately, the only
5947 implementations that provided these functions are also ones that
5948 are already efficient about not overallocation: they never got us
5949 more than 7 or so bytes per allocation. Removing them saves us a
5950 little code complexity and a nontrivial amount of build complexity.
5953 - Tor maintainers now require Automake version 1.9 or later to build
5954 Tor from the Git repository. (Automake is not required when building
5955 from a source distribution.)
5958 Changes in version 0.2.3.21-rc - 2012-09-05
5959 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
5960 series. It fixes a trio of potential security bugs, fixes a bug where
5961 we were leaving some of the fast relays out of the microdescriptor
5962 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
5963 and cleans up other smaller issues.
5965 o Major bugfixes (security):
5966 - Tear down the circuit if we get an unexpected SENDME cell. Clients
5967 could use this trick to make their circuits receive cells faster
5968 than our flow control would have allowed, or to gum up the network,
5969 or possibly to do targeted memory denial-of-service attacks on
5970 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
5971 from July 2002, before the release of Tor 0.0.0. We had committed
5972 this patch previously, but we had to revert it because of bug 6271.
5973 Now that 6271 is fixed, this patch appears to work.
5974 - Reject any attempt to extend to an internal address. Without
5975 this fix, a router could be used to probe addresses on an internal
5976 network to see whether they were accepting connections. Fixes bug
5977 6710; bugfix on 0.0.8pre1.
5978 - Do not crash when comparing an address with port value 0 to an
5979 address policy. This bug could have been used to cause a remote
5980 assertion failure by or against directory authorities, or to
5981 allow some applications to crash clients. Fixes bug 6690; bugfix
5985 - Remove the upper bound on microdescriptor length. We were hitting
5986 the limit for routers with complex exit policies or family
5987 declarations, causing clients to not use them. Fixes the first
5988 piece of bug 6404; fix on 0.2.2.6-alpha.
5989 - Detect "ORPort 0" as meaning, uniformly, that we're not running
5990 as a relay. Previously, some of our code would treat the presence
5991 of any ORPort line as meaning that we should act like a relay,
5992 even though our new listener code would correctly not open any
5993 ORPorts for ORPort 0. Similar bugs in other Port options are also
5994 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
5997 - Avoid a pair of double-free and use-after-mark bugs that can
5998 occur with certain timings in canceled and re-received DNS
5999 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
6000 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
6001 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
6002 - Allow one-hop directory fetching circuits the full "circuit build
6003 timeout" period, rather than just half of it, before failing them
6004 and marking the relay down. This fix should help reduce cases where
6005 clients declare relays (or worse, bridges) unreachable because
6006 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
6007 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
6009 - Authorities no longer include any router in their microdescriptor
6010 consensuses for which they couldn't generate or agree on a
6011 microdescriptor. Fixes the second piece of bug 6404; fix on
6013 - Detect and reject attempts to specify both "FooPort" and
6014 "FooPort 0" in the same configuration domain. (It's still okay
6015 to have a FooPort in your configuration file, and use "FooPort 0"
6016 on the command line to disable it.) Fixes the second half of bug
6017 6507; bugfix on 0.2.3.3-alpha.
6018 - Make wildcarded addresses (that is, ones beginning with "*.") work
6019 when provided via the controller's MapAddress command. Previously,
6020 they were accepted, but we never actually noticed that they were
6021 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
6022 - Avoid crashing on a malformed state file where EntryGuardPathBias
6023 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
6024 - Add a (probably redundant) memory clear between iterations of
6025 the router status voting loop, to prevent future coding errors
6026 where data might leak between iterations of the loop. Resolves
6029 o Minor bugfixes (log messages):
6030 - Downgrade "set buildtimeout to low value" messages to "info"
6031 severity; they were never an actual problem, there was never
6032 anything reasonable to do about them, and they tended to spam logs
6033 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
6034 - Downgrade path-bias warning messages to "info". We'll try to get
6035 them working better in 0.2.4. Add internal circuit construction
6036 state to protect against the noisy warn message "Unexpectedly high
6037 circuit_successes". Also add some additional rate-limited notice
6038 messages to help determine the root cause of the warn. Fixes bug
6039 6475. Bugfix against 0.2.3.17-beta.
6040 - Move log message when unable to find a microdesc in a routerstatus
6041 entry to parse time. Previously we'd spam this warning every time
6042 we tried to figure out which microdescriptors to download. Fixes
6043 the third piece of bug 6404; fix on 0.2.3.18-rc.
6046 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
6047 change when the authority is deciding whether to accept a newly
6048 uploaded descriptor. Implements ticket 6423.
6049 - Add missing documentation for consensus and microdesc files.
6050 Resolves ticket 6732.
6053 Changes in version 0.2.2.38 - 2012-08-12
6054 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
6055 attack that could in theory leak path information.
6058 - Avoid an uninitialized memory read when reading a vote or consensus
6059 document that has an unrecognized flavor name. This read could
6060 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
6061 - Try to leak less information about what relays a client is
6062 choosing to a side-channel attacker. Previously, a Tor client would
6063 stop iterating through the list of available relays as soon as it
6064 had chosen one, thus finishing a little earlier when it picked
6065 a router earlier in the list. If an attacker can recover this
6066 timing information (nontrivial but not proven to be impossible),
6067 they could learn some coarse-grained information about which relays
6068 a client was picking (middle nodes in particular are likelier to
6069 be affected than exits). The timing attack might be mitigated by
6070 other factors (see bug 6537 for some discussion), but it's best
6071 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
6074 Changes in version 0.2.3.20-rc - 2012-08-05
6075 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
6076 series. It fixes a pair of code security bugs and a potential anonymity
6077 issue, updates our RPM spec files, and cleans up other smaller issues.
6080 - Avoid read-from-freed-memory and double-free bugs that could occur
6081 when a DNS request fails while launching it. Fixes bug 6480;
6082 bugfix on 0.2.0.1-alpha.
6083 - Avoid an uninitialized memory read when reading a vote or consensus
6084 document that has an unrecognized flavor name. This read could
6085 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
6086 - Try to leak less information about what relays a client is
6087 choosing to a side-channel attacker. Previously, a Tor client would
6088 stop iterating through the list of available relays as soon as it
6089 had chosen one, thus finishing a little earlier when it picked
6090 a router earlier in the list. If an attacker can recover this
6091 timing information (nontrivial but not proven to be impossible),
6092 they could learn some coarse-grained information about which relays
6093 a client was picking (middle nodes in particular are likelier to
6094 be affected than exits). The timing attack might be mitigated by
6095 other factors (see bug 6537 for some discussion), but it's best
6096 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
6099 - Try to make the warning when giving an obsolete SOCKSListenAddress
6100 a little more useful.
6101 - Terminate active server managed proxies if Tor stops being a
6102 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
6103 - Provide a better error message about possible OSX Asciidoc failure
6104 reasons. Fixes bug 6436.
6105 - Warn when Tor is configured to use accounting in a way that can
6106 link a hidden service to some other hidden service or public
6107 address. Resolves ticket 6490.
6110 - Check return value of fputs() when writing authority certificate
6111 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
6112 - Ignore ServerTransportPlugin lines when Tor is not configured as
6113 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
6114 - When disabling guards for having too high a proportion of failed
6115 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
6119 - Update our default RPM spec files to work with mock and rpmbuild
6120 on RHEL/Fedora. They have an updated set of dependencies and
6121 conflicts, a fix for an ancient typo when creating the "_tor"
6122 user, and better instructions. Thanks to Ondrej Mikle for the
6123 patch series. Fixes bug 6043.
6126 - Make it possible to set the TestingTorNetwork configuration
6127 option using AlternateDirAuthority and AlternateBridgeAuthority
6128 as an alternative to setting DirServer. Addresses ticket 6377.
6131 - Clarify the documentation for the Alternate*Authority options.
6133 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
6135 o Code simplification and refactoring:
6136 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
6137 10 lines. Also, don't nest them. Doing so in the past has
6138 led to hard-to-debug code. The new style is to use the
6139 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
6142 Changes in version 0.2.3.19-rc - 2012-07-06
6143 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
6144 series. It fixes the compile on Windows, reverts to a GeoIP database
6145 that isn't as broken, and fixes a flow control bug that has been around
6146 since the beginning of Tor.
6149 - Fix a bug handling SENDME cells on nonexistent streams that could
6150 result in bizarre window values. Report and patch contributed
6151 pseudonymously. Fixes part of bug 6271. This bug was introduced
6152 before the first Tor release, in svn commit r152.
6153 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
6154 June 2012 database, Maxmind marked many Tor relays as country "A1",
6155 which will cause risky behavior for clients that set EntryNodes
6156 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
6157 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
6158 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
6161 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
6162 bugfix on 0.2.1.10-alpha.
6165 Changes in version 0.2.3.18-rc - 2012-06-28
6166 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
6167 series. It fixes a few smaller bugs, but generally appears stable.
6168 Please test it and let us know whether it is!
6171 - Allow wildcarded mapaddress targets to be specified on the
6172 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
6173 - Make our linker option detection code more robust against linkers
6174 such as on FreeBSD 8, where a bad combination of options completes
6175 successfully but makes an unrunnable binary. Fixes bug 6173;
6176 bugfix on 0.2.3.17-beta.
6178 o Minor bugfixes (on 0.2.2.x and earlier):
6179 - Avoid a false positive in the util/threads unit test by increasing
6180 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
6181 - Replace "Sending publish request" log messages with "Launching
6182 upload", so that they no longer confusingly imply that we're
6183 sending something to a directory we might not even be connected
6184 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
6185 - Make sure to set *socket_error in all error cases in
6186 connection_connect(), so it can't produce a warning about
6187 errno being zero from errno_to_orconn_end_reason(). Bugfix on
6188 0.2.1.1-alpha; resolves ticket 6028.
6189 - Downgrade "Got a certificate, but we already have it" log messages
6190 from warning to info, except when we're a dirauth. Fixes bug 5238;
6191 bugfix on 0.2.1.7-alpha.
6192 - When checking for requested signatures on the latest consensus
6193 before serving it to a client, make sure to check the right
6194 consensus flavor. Bugfix on 0.2.2.6-alpha.
6195 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
6196 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
6198 o Minor bugfixes (on 0.2.3.x):
6199 - Make format_helper_exit_status() avoid unnecessary space padding
6200 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
6202 - Downgrade a message about cleaning the microdescriptor cache to
6203 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
6204 - Log a BUG message at severity INFO if we have a networkstatus with
6205 a missing entry for some microdescriptor. Continues on a patch
6207 - Improve the log message when a managed proxy fails to launch. Fixes
6208 bug 5099; bugfix on 0.2.3.6-alpha.
6209 - Don't do DNS lookups when parsing corrupted managed proxy protocol
6210 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
6211 - When formatting wildcarded address mappings for the controller,
6212 be sure to include "*." as appropriate. Partially fixes bug 6244;
6213 bugfix on 0.2.3.9-alpha.
6214 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
6215 Bugfix on 0.2.3.13-alpha.
6216 - Stop logging messages about running with circuit timeout learning
6217 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
6218 - Disable a spurious warning about reading on a marked and flushing
6219 connection. We shouldn't be doing that, but apparently we
6220 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
6221 - Fix a bug that stopped AllowDotExit from working on addresses
6222 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
6225 o Code simplification, refactoring, unit tests:
6226 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
6227 Libevent's notion of cached time when possible.
6228 - Remove duplicate code for invoking getrlimit() from control.c.
6229 - Add a unit test for the environment_variable_names_equal function.
6232 - Document the --defaults-torrc option, and the new (in 0.2.3)
6233 semantics for overriding, extending, and clearing lists of
6234 options. Closes bug 4748.
6237 Changes in version 0.2.3.17-beta - 2012-06-15
6238 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
6239 gets our TLS handshake back on track for being able to blend in with
6240 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
6241 with Vidalia, and otherwise continues to get us closer to a release
6245 - Enable gcc and ld hardening by default. Resolves ticket 5210.
6246 - Update TLS cipher list to match Firefox 8 and later. Resolves
6248 - Implement the client side of proposal 198: remove support for
6249 clients falsely claiming to support standard ciphersuites that
6250 they can actually provide. As of modern OpenSSL versions, it's not
6251 necessary to fake any standard ciphersuite, and doing so prevents
6252 us from using better ciphersuites in the future, since servers
6253 can't know whether an advertised ciphersuite is really supported or
6254 not. Some hosts -- notably, ones with very old versions of OpenSSL
6255 or where OpenSSL has been built with ECC disabled -- will stand
6256 out because of this change; TBB users should not be affected.
6259 - Change the default value for DynamicDHGroups (introduced in
6260 0.2.3.9-alpha) to 0. This feature can make Tor relays less
6261 identifiable by their use of the mod_ssl DH group, but at
6262 the cost of some usability (#4721) and bridge tracing (#6087)
6263 regressions. Resolves ticket 5598.
6264 - Send a CRLF at the end of each STATUS_* control protocol event. This
6265 bug tickled a bug in Vidalia which would make it freeze. Fixes
6266 bug 6094; bugfix on 0.2.3.16-alpha.
6269 - Disable writing on marked-for-close connections when they are
6270 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
6271 bug 5263; bugfix on 0.0.2pre13, where we first added a special
6272 case for flushing marked connections.
6273 - Detect SSL handshake even when the initial attempt to write the
6274 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
6275 - Change the AllowDotExit rules so they should actually work.
6276 We now enforce AllowDotExit only immediately after receiving an
6277 address via SOCKS or DNSPort: other sources are free to provide
6278 .exit addresses after the resolution occurs. Fixes bug 3940;
6279 bugfix on 0.2.2.1-alpha.
6280 - Fix a (harmless) integer overflow in cell statistics reported by
6281 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
6282 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
6283 right places and never depends on the consensus parameters or
6284 computes adaptive timeouts when it is disabled. Fixes bug 5049;
6285 bugfix on 0.2.2.14-alpha.
6286 - When building Tor on Windows with -DUNICODE (not default), ensure
6287 that error messages, filenames, and DNS server names are always
6288 NUL-terminated when we convert them to a single-byte encoding.
6289 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
6290 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
6291 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
6292 - Fix an edge case where TestingTorNetwork is set but the authorities
6293 and relays all have an uptime of zero, where the private Tor network
6294 could briefly lack support for hidden services. Fixes bug 3886;
6295 bugfix on 0.2.2.18-alpha.
6296 - Correct the manpage's descriptions for the default values of
6297 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
6299 - Fix the documentation for the --hush and --quiet command line
6300 options, which changed their behavior back in 0.2.3.3-alpha.
6301 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
6305 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
6306 more information to it, so that we can track it down in case it
6307 returns again. Mitigates bug 5235.
6308 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
6309 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
6310 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
6311 - Warn the user when HTTPProxy, but no other proxy type, is
6312 configured. This can cause surprising behavior: it doesn't send
6313 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
6314 directory traffic only. Resolves ticket 4663.
6315 - Issue a notice if a guard completes less than 40% of your circuits.
6316 Threshold is configurable by torrc option PathBiasNoticeRate and
6317 consensus parameter pb_noticepct. There is additional, off-by-
6318 default code to disable guards which fail too many circuits.
6319 Addresses ticket 5458.
6320 - Update to the June 6 2012 Maxmind GeoLite Country database.
6322 o Code simplifications and refactoring:
6323 - Remove validate_pluggable_transports_config(): its warning
6324 message is now handled by connection_or_connect().
6327 Changes in version 0.2.2.37 - 2012-06-06
6328 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
6329 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
6333 - Work around a bug in OpenSSL that broke renegotiation with TLS
6334 1.1 and TLS 1.2. Without this workaround, all attempts to speak
6335 the v2 Tor connection protocol when both sides were using OpenSSL
6336 1.0.1 would fail. Resolves ticket 6033.
6337 - When waiting for a client to renegotiate, don't allow it to add
6338 any bytes to the input buffer. This fixes a potential DoS issue.
6339 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
6340 - Fix an edge case where if we fetch or publish a hidden service
6341 descriptor, we might build a 4-hop circuit and then use that circuit
6342 for exiting afterwards -- even if the new last hop doesn't obey our
6343 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
6346 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
6347 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
6350 - Tell GCC and Clang to check for any errors in format strings passed
6351 to the tor_v*(print|scan)f functions.
6354 Changes in version 0.2.3.16-alpha - 2012-06-05
6355 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
6356 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
6357 currently). It also fixes a variety of smaller bugs and other cleanups
6358 that get us closer to a release candidate.
6360 o Major bugfixes (general):
6361 - Work around a bug in OpenSSL that broke renegotiation with TLS
6362 1.1 and TLS 1.2. Without this workaround, all attempts to speak
6363 the v2 Tor connection protocol when both sides were using OpenSSL
6364 1.0.1 would fail. Resolves ticket 6033.
6365 - When waiting for a client to renegotiate, don't allow it to add
6366 any bytes to the input buffer. This fixes a potential DoS issue.
6367 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
6368 - Pass correct OR address to managed proxies (like obfsproxy),
6369 even when ORListenAddress is used. Fixes bug 4865; bugfix on
6371 - The advertised platform of a router now includes only its operating
6372 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
6373 service pack level (for Windows) or its CPU architecture (for Unix).
6374 We also no longer include the "git-XYZ" tag in the version. Resolves
6377 o Major bugfixes (clients):
6378 - If we are unable to find any exit that supports our predicted ports,
6379 stop calling them predicted, so that we don't loop and build
6380 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
6381 which introduced predicted ports.
6382 - Fix an edge case where if we fetch or publish a hidden service
6383 descriptor, we might build a 4-hop circuit and then use that circuit
6384 for exiting afterwards -- even if the new last hop doesn't obey our
6385 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
6386 - Check at each new consensus whether our entry guards were picked
6387 long enough ago that we should rotate them. Previously, we only
6388 did this check at startup, which could lead to us holding a guard
6389 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
6390 - When fetching a bridge descriptor from a bridge authority,
6391 always do so anonymously, whether we have been able to open
6392 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
6393 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
6394 but we'll need to wait for bug 6010 before it's actually usable.
6396 o Major bugfixes (directory authorities):
6397 - When computing weight parameters, behave more robustly in the
6398 presence of a bad bwweightscale value. Previously, the authorities
6399 would crash if they agreed on a sufficiently broken weight_scale
6400 value: now, they use a reasonable default and carry on. Partial
6401 fix for 5786; bugfix on 0.2.2.17-alpha.
6402 - Check more thoroughly to prevent a rogue authority from
6403 double-voting on any consensus directory parameter. Previously,
6404 authorities would crash in this case if the total number of
6405 votes for any parameter exceeded the number of active voters,
6406 but would let it pass otherwise. Partial fix for bug 5786; bugfix
6410 - Rate-limit log messages when asked to connect anonymously to
6411 a private address. When these hit, they tended to hit fast and
6412 often. Also, don't bother trying to connect to addresses that we
6413 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
6414 reply makes us think we have been lied to, even when the address the
6415 client tried to connect to was "localhost." Resolves ticket 2822.
6416 - Allow packagers to insert an extra string in server descriptor
6417 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
6418 Resolves the rest of ticket 2988.
6419 - Raise the threshold of server descriptors needed (75%) and exit
6420 server descriptors needed (50%) before we will declare ourselves
6421 bootstrapped. This will make clients start building circuits a
6422 little later, but makes the initially constructed circuits less
6423 skewed and less in conflict with further directory fetches. Fixes
6425 - Close any connection that sends unrecognized junk before the
6426 handshake. Solves an issue noted in bug 4369.
6427 - Improve log messages about managed transports. Resolves ticket 5070.
6428 - Tag a bridge's descriptor as "never to be sent unencrypted".
6429 This shouldn't matter, since bridges don't open non-anonymous
6430 connections to the bridge authority and don't allow unencrypted
6431 directory connections from clients, but we might as well make
6432 sure. Closes bug 5139.
6433 - Expose our view of whether we have gone dormant to the controller,
6434 via a new "GETINFO dormant" value. Torbutton and other controllers
6435 can use this to avoid doing periodic requests through Tor while
6436 it's dormant (bug 4718). Fixes bug 5954.
6437 - Tell GCC and Clang to check for any errors in format strings passed
6438 to the tor_v*(print|scan)f functions.
6439 - Update to the May 1 2012 Maxmind GeoLite Country database.
6441 o Minor bugfixes (already included in 0.2.2.36):
6442 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
6443 Fixes bug 5346; bugfix on 0.0.8pre3.
6444 - Correct parsing of certain date types in parse_http_time().
6445 Without this patch, If-Modified-Since would behave
6446 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
6447 Esteban Manchado Velázques.
6448 - Make our number-parsing functions always treat too-large values
6449 as an error, even when those values exceed the width of the
6450 underlying type. Previously, if the caller provided these
6451 functions with minima or maxima set to the extreme values of the
6452 underlying integer type, these functions would return those
6453 values on overflow rather than treating overflow as an error.
6454 Fixes part of bug 5786; bugfix on 0.0.9.
6455 - If we hit the error case where routerlist_insert() replaces an
6456 existing (old) server descriptor, make sure to remove that
6457 server descriptor from the old_routers list. Fix related to bug
6458 1776. Bugfix on 0.2.2.18-alpha.
6459 - Clarify the behavior of MaxCircuitDirtiness with hidden service
6460 circuits. Fixes issue 5259.
6462 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
6463 - Prevent a null-pointer dereference when receiving a data cell
6464 for a nonexistent stream when the circuit in question has an
6465 empty deliver window. We don't believe this is triggerable,
6466 since we don't currently allow deliver windows to become empty,
6467 but the logic is tricky enough that it's better to make the code
6468 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
6469 - Fix a memory leak when trying to launch a DNS request when the
6470 network is disabled or the nameservers are unconfigurable. Fixes
6471 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
6472 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
6473 - Don't hold a Windows file handle open for every file mapping;
6474 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
6476 - Avoid O(n^2) performance characteristics when parsing a large
6477 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
6478 - Format more doubles with %f, not %lf. Patch from grarpamp to make
6479 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
6481 - Make our replacement implementation of strtok_r() compatible with
6482 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
6483 bugfix on 0.2.2.1-alpha.
6484 - Fix a NULL-pointer dereference on a badly formed
6485 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
6486 bugfix on 0.2.2.9-alpha.
6487 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
6488 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
6489 - Defensively refactor rend_mid_rendezvous() so that protocol
6490 violations and length checks happen in the beginning. Fixes
6492 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
6493 that IPv6 stuff will compile on MSVC, and compilation issues
6494 will be easier to track down. Fixes bug 5861.
6496 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
6497 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
6498 resource exhaustion, so that clients can adjust their load to
6499 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
6500 started using END_STREAM_REASON_RESOURCELIMIT.
6501 - Don't check for whether the address we're using for outbound
6502 connections has changed until after the outbound connection has
6503 completed. On Windows, getsockname() doesn't succeed until the
6504 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
6505 - If the configuration tries to set MyFamily on a bridge, refuse to
6506 do so, and warn about the security implications. Fixes bug 4657;
6507 bugfix on 0.2.0.3-alpha.
6508 - If the client fails to set a reasonable set of ciphersuites
6509 during its v2 handshake renegotiation, allow the renegotiation to
6510 continue nevertheless (i.e. send all the required certificates).
6511 Fixes bug 4591; bugfix on 0.2.0.20-rc.
6512 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
6513 option is set to 0 (which Vidalia version 0.2.16 now does when
6514 a SAVECONF attempt fails), perform other actions that SIGHUP
6515 usually causes (like reopening the logs). Fixes bug 5095; bugfix
6517 - If we fail to write a microdescriptor to the disk cache, do not
6518 continue replacing the old microdescriptor file. Fixes bug 2954;
6519 bugfix on 0.2.2.6-alpha.
6520 - Exit nodes don't need to fetch certificates for authorities that
6521 they don't recognize; only directory authorities, bridges,
6522 and caches need to do that. Fixes part of bug 2297; bugfix on
6524 - Correctly handle checking the permissions on the parent
6525 directory of a control socket in the root directory. Bug found
6526 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
6528 - When told to add a bridge with the same digest as a preexisting
6529 bridge but a different addr:port, change the addr:port as
6530 requested. Previously we would not notice the change. Fixes half
6531 of bug 5603; fix on 0.2.2.26-beta.
6532 - End AUTHCHALLENGE error messages (in the control protocol) with
6533 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
6535 o Minor bugfixes (on 0.2.3.x):
6536 - Turn an assertion (that the number of handshakes received as a
6537 server is not < 1) into a warning. Fixes bug 4873; bugfix on
6539 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
6540 we had reversed them when the answer was cached.) Fixes bug
6541 5723; bugfix on 0.2.3.1-alpha.
6542 - Work correctly on Linux systems with accept4 support advertised in
6543 their headers, but without accept4 support in the kernel. Fix
6544 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
6545 - When told to add a bridge with the same addr:port as a preexisting
6546 bridge but a different transport, change the transport as
6547 requested. Previously we would not notice the change. Fixes half
6548 of bug 5603; fix on 0.2.3.2-alpha.
6549 - Avoid a "double-reply" warning when replying to a SOCKS request
6550 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
6551 bugfix on 0.2.3.4-alpha.
6552 - Fix a bug where a bridge authority crashes if it has seen no
6553 directory requests when it's time to write statistics to disk.
6554 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
6556 - Don't try to open non-control listeners when DisableNetwork is set.
6557 Previously, we'd open all listeners, then immediately close them.
6558 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
6559 - Don't abort the managed proxy protocol if the managed proxy
6560 sends us an unrecognized line; ignore it instead. Fixes bug
6561 5910; bugfix on 0.2.3.9-alpha.
6562 - Fix a compile warning in crypto.c when compiling with clang 3.1.
6563 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
6564 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
6565 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
6566 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
6567 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
6568 - Resolve numerous small warnings and build issues with MSVC. Resolves
6571 o Documentation fixes:
6572 - Improve the manual's documentation for the NT Service command-line
6573 options. Addresses ticket 3964.
6574 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
6575 - Document the changes to the ORPort and DirPort options, and the
6576 fact that {OR/Dir}ListenAddress is now unnecessary (and
6577 therefore deprecated). Resolves ticket 5597.
6580 - Remove the torrc.bridge file: we don't use it for anything, and
6581 it had become badly desynchronized from torrc.sample. Resolves
6585 Changes in version 0.2.2.36 - 2012-05-24
6586 Tor 0.2.2.36 updates the addresses for two of the eight directory
6587 authorities, fixes some potential anonymity and security issues,
6588 and fixes several crash bugs.
6590 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
6591 known flaws, and nobody should be using them. You should upgrade. If
6592 you're using a Linux or BSD and its packages are obsolete, stop using
6593 those packages and upgrade anyway.
6595 o Directory authority changes:
6596 - Change IP address for maatuska (v3 directory authority).
6597 - Change IP address for ides (v3 directory authority), and rename
6601 - When building or running with any version of OpenSSL earlier
6602 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
6603 versions have a bug (CVE-2011-4576) in which their block cipher
6604 padding includes uninitialized data, potentially leaking sensitive
6605 information to any peer with whom they make a SSLv3 connection. Tor
6606 does not use SSL v3 by default, but a hostile client or server
6607 could force an SSLv3 connection in order to gain information that
6608 they shouldn't have been able to get. The best solution here is to
6609 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
6610 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
6611 to make sure that the bug can't happen.
6612 - Never use a bridge or a controller-supplied node as an exit, even
6613 if its exit policy allows it. Found by wanoskarnet. Fixes bug
6614 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
6615 and 0.2.0.3-alpha (for bridge-purpose descriptors).
6616 - Only build circuits if we have a sufficient threshold of the total
6617 descriptors that are marked in the consensus with the "Exit"
6618 flag. This mitigates an attack proposed by wanoskarnet, in which
6619 all of a client's bridges collude to restrict the exit nodes that
6620 the client knows about. Fixes bug 5343.
6621 - Provide controllers with a safer way to implement the cookie
6622 authentication mechanism. With the old method, if another locally
6623 running program could convince a controller that it was the Tor
6624 process, then that program could trick the controller into telling
6625 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
6626 authentication method uses a challenge-response approach to prevent
6627 this attack. Fixes bug 5185; implements proposal 193.
6630 - Avoid logging uninitialized data when unable to decode a hidden
6631 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
6632 - Avoid a client-side assertion failure when receiving an INTRODUCE2
6633 cell on a general purpose circuit. Fixes bug 5644; bugfix on
6635 - Fix builds when the path to sed, openssl, or sha1sum contains
6636 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
6638 - Correct our replacements for the timeradd() and timersub() functions
6639 on platforms that lack them (for example, Windows). The timersub()
6640 function is used when expiring circuits, while timeradd() is
6641 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
6642 bugfix on 0.2.2.24-alpha.
6643 - Fix the SOCKET_OK test that we use to tell when socket
6644 creation fails so that it works on Win64. Fixes part of bug 4533;
6645 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
6648 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
6649 Fixes bug 5346; bugfix on 0.0.8pre3.
6650 - Make our number-parsing functions always treat too-large values
6651 as an error, even when those values exceed the width of the
6652 underlying type. Previously, if the caller provided these
6653 functions with minima or maxima set to the extreme values of the
6654 underlying integer type, these functions would return those
6655 values on overflow rather than treating overflow as an error.
6656 Fixes part of bug 5786; bugfix on 0.0.9.
6657 - Older Linux kernels erroneously respond to strange nmap behavior
6658 by having accept() return successfully with a zero-length
6659 socket. When this happens, just close the connection. Previously,
6660 we would try harder to learn the remote address: but there was
6661 no such remote address to learn, and our method for trying to
6662 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
6663 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
6664 - Correct parsing of certain date types in parse_http_time().
6665 Without this patch, If-Modified-Since would behave
6666 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
6667 Esteban Manchado Velázques.
6668 - Change the BridgePassword feature (part of the "bridge community"
6669 design, which is not yet implemented) to use a time-independent
6670 comparison. The old behavior might have allowed an adversary
6671 to use timing to guess the BridgePassword value. Fixes bug 5543;
6672 bugfix on 0.2.0.14-alpha.
6673 - Detect and reject certain misformed escape sequences in
6674 configuration values. Previously, these values would cause us
6675 to crash if received in a torrc file or over an authenticated
6676 control port. Bug found by Esteban Manchado Velázquez, and
6677 independently by Robert Connolly from Matta Consulting who further
6678 noted that it allows a post-authentication heap overflow. Patch
6679 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
6680 bugfix on 0.2.0.16-alpha.
6681 - Fix a compile warning when using the --enable-openbsd-malloc
6682 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
6683 - During configure, detect when we're building with clang version
6684 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
6685 CFLAGS. clang doesn't support them yet.
6686 - When sending an HTTP/1.1 proxy request, include a Host header.
6687 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
6688 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
6689 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
6690 - If we hit the error case where routerlist_insert() replaces an
6691 existing (old) server descriptor, make sure to remove that
6692 server descriptor from the old_routers list. Fix related to bug
6693 1776. Bugfix on 0.2.2.18-alpha.
6695 o Minor bugfixes (documentation and log messages):
6696 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
6697 Fixes bug 4856; bugfix on Tor 0.0.6.
6698 - Update "ClientOnly" man page entry to explain that there isn't
6699 really any point to messing with it. Resolves ticket 5005.
6700 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
6701 directory authority option (introduced in Tor 0.2.2.34).
6702 - Downgrade the "We're missing a certificate" message from notice
6703 to info: people kept mistaking it for a real problem, whereas it
6704 is seldom the problem even when we are failing to bootstrap. Fixes
6705 bug 5067; bugfix on 0.2.0.10-alpha.
6706 - Correctly spell "connect" in a log message on failure to create a
6707 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
6708 - Clarify the behavior of MaxCircuitDirtiness with hidden service
6709 circuits. Fixes issue 5259.
6712 - Directory authorities now reject versions of Tor older than
6713 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
6714 inclusive. These versions accounted for only a small fraction of
6715 the Tor network, and have numerous known security issues. Resolves
6717 - Update to the May 1 2012 Maxmind GeoLite Country database.
6720 - When sending or relaying a RELAY_EARLY cell, we used to convert
6721 it to a RELAY cell if the connection was using the v1 link
6722 protocol. This was a workaround for older versions of Tor, which
6723 didn't handle RELAY_EARLY cells properly. Now that all supported
6724 versions can handle RELAY_EARLY cells, and now that we're enforcing
6725 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
6726 remove this workaround. Addresses bug 4786.
6729 Changes in version 0.2.3.15-alpha - 2012-04-30
6730 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
6731 the development branch build on Windows again.
6733 o Minor bugfixes (on 0.2.2.x and earlier):
6734 - Make sure that there are no unhandled pending TLS errors before
6735 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
6736 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
6737 Bugfix on 0.1.0.5-rc; fixes bug 4528.
6738 - Fix an assert that directory authorities could trigger on sighup
6739 during some configuration state transitions. We now don't treat
6740 it as a fatal error when the new descriptor we just generated in
6741 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
6742 - After we pick a directory mirror, we would refuse to use it if
6743 it's in our ExcludeExitNodes list, resulting in mysterious failures
6744 to bootstrap for people who just wanted to avoid exiting from
6745 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
6746 - When building with --enable-static-tor on OpenBSD, do not
6747 erroneously attempt to link -lrt. Fixes bug 5103.
6749 o Minor bugfixes (on 0.2.3.x):
6750 - When Tor is built with kernel headers from a recent (last few
6751 years) Linux kernel, do not fail to run on older (pre-2.6.28
6752 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
6753 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
6755 - Fix compilation with miniupnpc version 1.6; patch from
6756 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
6757 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
6758 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
6759 - Fix compilation on platforms without unistd.h, or where environ
6760 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
6763 - Directory authorities are now a little more lenient at accepting
6764 older router descriptors, or newer router descriptors that don't
6765 make big changes. This should help ameliorate past and future
6766 issues where routers think they have uploaded valid descriptors,
6767 but the authorities don't think so. Fix for ticket 2479.
6768 - Make the code that clients use to detect an address change be
6769 IPv6-aware, so that it won't fill clients' logs with error
6770 messages when trying to get the IPv4 address of an IPv6
6771 connection. Implements ticket 5537.
6774 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
6775 authorities needed to use it for a while to keep the network working
6776 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
6777 that was six months ago. As of now, it should no longer be needed
6781 Changes in version 0.2.3.14-alpha - 2012-04-23
6782 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
6783 candidate. It also dramatically speeds up AES: fast relays should
6784 consider switching to the newer OpenSSL library.
6786 o Directory authority changes:
6787 - Change IP address for ides (v3 directory authority), and rename
6791 - Avoid logging uninitialized data when unable to decode a hidden
6792 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
6793 - Avoid a client-side assertion failure when receiving an INTRODUCE2
6794 cell on a general purpose circuit. Fixes bug 5644; bugfix on
6796 - If authorities are unable to get a v2 consensus document from other
6797 directory authorities, they no longer fall back to fetching
6798 them from regular directory caches. Fixes bug 5635; bugfix on
6799 0.2.2.26-beta, where routers stopped downloading v2 consensus
6801 - When we start a Tor client with a normal consensus already cached,
6802 be willing to download a microdescriptor consensus. Fixes bug 4011;
6803 fix on 0.2.3.1-alpha.
6805 o Major features (performance):
6806 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
6807 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
6808 vectorized AES implementations as appropriate. These can be much,
6809 much faster than other AES implementations.
6811 o Minor bugfixes (0.2.2.x and earlier):
6812 - Don't launch more than 10 service-side introduction-point circuits
6813 for a hidden service in five minutes. Previously, we would consider
6814 launching more introduction-point circuits if at least one second
6815 had passed without any introduction-point circuits failing. Fixes
6816 bug 4607; bugfix on 0.0.7pre1.
6817 - Change the BridgePassword feature (part of the "bridge community"
6818 design, which is not yet implemented) to use a time-independent
6819 comparison. The old behavior might have allowed an adversary
6820 to use timing to guess the BridgePassword value. Fixes bug 5543;
6821 bugfix on 0.2.0.14-alpha.
6822 - Enforce correct return behavior of tor_vsscanf() when the '%%'
6823 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
6824 - When sending an HTTP/1.1 proxy request, include a Host header.
6825 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
6826 - Don't log that we have "decided to publish new relay descriptor"
6827 unless we are actually publishing a descriptor. Fixes bug 3942;
6828 bugfix on 0.2.2.28-beta.
6830 o Minor bugfixes (0.2.3.x):
6831 - Fix a bug where a bridge authority crashes (on a failed assert)
6832 if it has seen no directory requests when it's time to write
6833 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
6834 - Fix bug stomping on ORPort option NoListen and ignoring option
6835 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
6836 - In the testsuite, provide a large enough buffer in the tor_sscanf
6837 unit test. Otherwise we'd overrun that buffer and crash during
6838 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
6840 - Make sure we create the keys directory if it doesn't exist and we're
6841 about to store the dynamic Diffie-Hellman parameters. Fixes bug
6842 5572; bugfix on 0.2.3.13-alpha.
6843 - Fix a small memory leak when trying to decode incorrect base16
6844 authenticator during SAFECOOKIE authentication. Found by
6845 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
6848 - Add more information to a log statement that might help track down
6849 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
6850 non-IP address" messages (or any Bug messages, for that matter!),
6851 please let us know about it.
6852 - Relays now understand an IPv6 address when they get one from a
6853 directory server. Resolves ticket 4875.
6854 - Resolve IPv6 addresses in bridge and entry statistics to country
6855 code "??" which means we at least count them. Resolves ticket 5053;
6856 improves on 0.2.3.9-alpha.
6857 - Update to the April 3 2012 Maxmind GeoLite Country database.
6858 - Begin a doc/state-contents.txt file to explain the contents of
6859 the Tor state file. Fixes bug 2987.
6861 o Default torrc changes:
6862 - Stop listing "socksport 9050" in torrc.sample. We open a socks
6863 port on 9050 by default anyway, so this should not change anything
6865 - Stop mentioning the deprecated *ListenAddress options in
6866 torrc.sample. Fixes bug 5438.
6867 - Document unit of bandwidth related options in sample torrc.
6871 - The "torify" script no longer supports the "tsocks" socksifier
6872 tool, since tsocks doesn't support DNS and UDP right for Tor.
6873 Everyone should be using torsocks instead. Fixes bugs 3530 and
6874 5180. Based on a patch by "ugh".
6877 - Change the symmetric cipher interface so that creating and
6878 initializing a stream cipher are no longer separate functions.
6879 - Remove all internal support for unpadded RSA. We never used it, and
6880 it would be a bad idea to start.
6883 Changes in version 0.2.3.13-alpha - 2012-03-26
6884 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
6885 in managed pluggable transports, as well as providing other cleanups
6886 that get us closer to a release candidate.
6888 o Directory authority changes:
6889 - Change IP address for maatuska (v3 directory authority).
6892 - Provide controllers with a safer way to implement the cookie
6893 authentication mechanism. With the old method, if another locally
6894 running program could convince a controller that it was the Tor
6895 process, then that program could trick the controller into telling
6896 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
6897 authentication method uses a challenge-response approach to prevent
6898 this attack. Fixes bug 5185, implements proposal 193.
6899 - Never use a bridge or a controller-supplied node as an exit, even
6900 if its exit policy allows it. Found by wanoskarnet. Fixes bug
6901 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
6902 and 0.2.0.3-alpha (for bridge-purpose descriptors).
6903 - Only build circuits if we have a sufficient threshold of the total
6904 descriptors that are marked in the consensus with the "Exit"
6905 flag. This mitigates an attack proposed by wanoskarnet, in which
6906 all of a client's bridges collude to restrict the exit nodes that
6907 the client knows about. Fixes bug 5343.
6909 o Major bugfixes (on Tor 0.2.3.x):
6910 - Avoid an assert when managed proxies like obfsproxy are configured,
6911 and we receive HUP signals or setconf attempts too rapidly. This
6912 situation happens most commonly when Vidalia tries to attach to
6913 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
6914 bugfix on 0.2.3.6-alpha.
6915 - Fix a relay-side pluggable transports bug where managed proxies were
6916 unreachable from the Internet, because Tor asked them to bind on
6917 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
6918 - Stop discarding command-line arguments when TestingTorNetwork
6919 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
6920 0.2.3.9-alpha, where task 4552 added support for two layers of
6922 - Resume allowing the unit tests to run in gdb. This was accidentally
6923 made impossible when the DisableDebuggerAttachment option was
6924 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
6925 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
6926 0.2.3.11-alpha. Reported by Anthony G. Basile.
6928 o Minor bugfixes (on 0.2.2.x and earlier):
6929 - Ensure we don't cannibalize circuits that are longer than three hops
6930 already, so we don't end up making circuits with 5 or more
6931 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
6932 0.1.0.1-rc which introduced cannibalization.
6933 - Detect and reject certain misformed escape sequences in
6934 configuration values. Previously, these values would cause us
6935 to crash if received in a torrc file or over an authenticated
6936 control port. Bug found by Esteban Manchado Velázquez, and
6937 independently by Robert Connolly from Matta Consulting who further
6938 noted that it allows a post-authentication heap overflow. Patch
6939 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
6940 bugfix on 0.2.0.16-alpha.
6941 - Fix a compile warning when using the --enable-openbsd-malloc
6942 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
6943 - Directory caches no longer refuse to clean out descriptors because
6944 of missing v2 networkstatus documents, unless they're configured
6945 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
6946 0.2.2.26-beta. Patch by Daniel Bryg.
6947 - Update to the latest version of the tinytest unit testing framework.
6948 This includes a couple of bugfixes that can be relevant for
6949 running forked unit tests on Windows, and removes all reserved
6952 o Minor bugfixes (on 0.2.3.x):
6953 - On a failed pipe() call, don't leak file descriptors. Fixes bug
6954 4296; bugfix on 0.2.3.1-alpha.
6955 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
6956 until after we have received a CERTS cell. Fixes bug 4361; bugfix
6957 on 0.2.3.6-alpha. Patch by "frosty".
6958 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
6959 option, so that the IP stack doesn't decide to use it for IPv4
6960 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
6961 - Ensure that variables set in Tor's environment cannot override
6962 environment variables that Tor passes to a managed
6963 pluggable-transport proxy. Previously, Tor would pass every
6964 variable in its environment to managed proxies along with the new
6965 ones, in such a way that on many operating systems, the inherited
6966 environment variables would override those which Tor tried to
6967 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
6968 bugfix on 0.2.3.9-alpha for Windows.
6971 - A wide variety of new unit tests by Esteban Manchado Velázquez.
6972 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
6973 - Update to the March 6 2012 Maxmind GeoLite Country database.
6976 Changes in version 0.2.3.12-alpha - 2012-02-13
6977 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
6978 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
6979 when Tor is configured to use a pluggable transport like obfsproxy.
6982 - Fix builds when the path to sed, openssl, or sha1sum contains
6983 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
6985 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
6986 connections. This change should allow busy exit relays to stop
6987 running out of available sockets as quickly. Fixes bug 4950;
6988 bugfix on 0.2.2.26-beta.
6989 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
6990 would ask the bridge for microdescriptors, which are only supported
6991 in 0.2.3.x, and then fail to bootstrap when it didn't get the
6992 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
6993 - Properly set up obfsproxy's environment when in managed mode. The
6994 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
6995 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
6996 5076 and 5082; bugfix on 0.2.3.6-alpha.
6999 - Use the dead_strip option when building Tor on OS X. This reduces
7000 binary size by almost 19% when linking openssl and libevent
7001 statically, which we do for Tor Browser Bundle.
7002 - Fix broken URLs in the sample torrc file, and tell readers about
7003 the OutboundBindAddress, ExitPolicyRejectPrivate, and
7004 PublishServerDescriptor options. Addresses bug 4652.
7005 - Update to the February 7 2012 Maxmind GeoLite Country database.
7008 - Downgrade the "We're missing a certificate" message from notice
7009 to info: people kept mistaking it for a real problem, whereas it
7010 is seldom the problem even when we are failing to bootstrap. Fixes
7011 bug 5067; bugfix on 0.2.0.10-alpha.
7012 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
7013 managed pluggable transport server proxy's environment.
7014 Previously, we would put it there, even though Tor doesn't
7015 implement an 'extended server port' yet, and even though Tor
7016 almost certainly isn't listening at that address. For now, we set
7017 it to an empty string to avoid crashing older obfsproxies. Bugfix
7019 - Log the heartbeat message every HeartbeatPeriod seconds, not every
7020 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
7021 0.2.3.1-alpha. Bug reported by Scott Bennett.
7022 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
7023 bugfix on 0.2.3.11-alpha.
7024 - Update "ClientOnly" man page entry to explain that there isn't
7025 really any point to messing with it. Resolves ticket 5005.
7026 - Use the correct CVE number for CVE-2011-4576 in our comments and
7027 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
7030 o Code simplifications and refactoring:
7031 - Use the _WIN32 macro throughout our code to detect Windows.
7032 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
7036 Changes in version 0.2.3.11-alpha - 2012-01-22
7037 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
7038 the last step of the plan to limit maximum circuit length, includes
7039 a wide variety of hidden service performance and correctness fixes,
7040 works around an OpenSSL security flaw if your distro is too stubborn
7041 to upgrade, and fixes a bunch of smaller issues.
7044 - Now that Tor 0.2.0.x is completely deprecated, enable the final
7045 part of "Proposal 110: Avoiding infinite length circuits" by
7046 refusing all circuit-extend requests that do not use a relay_early
7047 cell. This change helps Tor resist a class of denial-of-service
7048 attacks by limiting the maximum circuit length.
7049 - Adjust the number of introduction points that a hidden service
7050 will try to maintain based on how long its introduction points
7051 remain in use and how many introductions they handle. Fixes
7053 - Try to use system facilities for enumerating local interface
7054 addresses, before falling back to our old approach (which was
7055 binding a UDP socket, and calling getsockname() on it). That
7056 approach was scaring OS X users whose draconian firewall
7057 software warned about binding to UDP sockets, regardless of
7058 whether packets were sent. Now we try to use getifaddrs(),
7059 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
7060 system supports. Resolves ticket 1827.
7062 o Major security workaround:
7063 - When building or running with any version of OpenSSL earlier
7064 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
7065 versions have a bug (CVE-2011-4576) in which their block cipher
7066 padding includes uninitialized data, potentially leaking sensitive
7067 information to any peer with whom they make a SSLv3 connection. Tor
7068 does not use SSL v3 by default, but a hostile client or server
7069 could force an SSLv3 connection in order to gain information that
7070 they shouldn't have been able to get. The best solution here is to
7071 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
7072 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
7073 to make sure that the bug can't happen.
7076 - Fix the SOCKET_OK test that we use to tell when socket
7077 creation fails so that it works on Win64. Fixes part of bug 4533;
7078 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
7079 - Correct our replacements for the timeradd() and timersub() functions
7080 on platforms that lack them (for example, Windows). The timersub()
7081 function is used when expiring circuits, while timeradd() is
7082 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
7083 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
7084 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
7085 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
7086 bug at runtime, not compile time, because some distributions hack
7087 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
7088 on 0.2.3.9-alpha. Found by Pascal.
7090 o Minor features (controller):
7091 - Use absolute path names when reporting the torrc filename in the
7092 control protocol, so a controller can more easily find the torrc
7093 file. Resolves bug 1101.
7094 - Extend the control protocol to report flags that control a circuit's
7095 path selection in CIRC events and in replies to 'GETINFO
7096 circuit-status'. Implements part of ticket 2411.
7097 - Extend the control protocol to report the hidden service address
7098 and current state of a hidden-service-related circuit in CIRC
7099 events and in replies to 'GETINFO circuit-status'. Implements part
7101 - When reporting the path to the cookie file to the controller,
7102 give an absolute path. Resolves ticket 4881.
7103 - Allow controllers to request an event notification whenever a
7104 circuit is cannibalized or its purpose is changed. Implements
7105 part of ticket 3457.
7106 - Include the creation time of a circuit in CIRC and CIRC2
7107 control-port events and the list produced by the 'GETINFO
7108 circuit-status' control-port command.
7110 o Minor features (directory authorities):
7111 - Directory authorities now reject versions of Tor older than
7112 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
7113 inclusive. These versions accounted for only a small fraction of
7114 the Tor network, and have numerous known security issues. Resolves
7116 - Authority operators can now vote for all relays in a given
7117 set of countries to be BadDir/BadExit/Invalid/Rejected.
7118 - Provide two consensus parameters (FastFlagMinThreshold and
7119 FastFlagMaxThreshold) to control the range of allowable bandwidths
7120 for the Fast directory flag. These allow authorities to run
7121 experiments on appropriate requirements for being a "Fast" node.
7122 The AuthDirFastGuarantee config value still applies. Implements
7124 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
7125 directory authority option (introduced in Tor 0.2.2.34).
7127 o Minor features (other):
7128 - Don't disable the DirPort when we cannot exceed our AccountingMax
7129 limit during this interval because the effective bandwidthrate is
7130 low enough. This is useful in a situation where AccountMax is only
7131 used as an additional safeguard or to provide statistics.
7132 - Prepend an informative header to generated dynamic_dh_params files.
7133 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
7134 EntryNodes will have no effect. Resolves issue 2571.
7135 - Log more useful messages when we fail to disable debugger
7137 - Log which authority we're missing votes from when we go to fetch
7138 them from the other auths.
7139 - Log (at debug level) whenever a circuit's purpose is changed.
7140 - Add missing documentation for the MaxClientCircuitsPending,
7141 UseMicrodescriptors, UserspaceIOCPBuffers, and
7142 _UseFilteringSSLBufferevents options, all introduced during
7144 - Update to the January 3 2012 Maxmind GeoLite Country database.
7146 o Minor bugfixes (hidden services):
7147 - Don't close hidden service client circuits which have almost
7148 finished connecting to their destination when they reach
7149 the normal circuit-build timeout. Previously, we would close
7150 introduction circuits which are waiting for an acknowledgement
7151 from the introduction point, and rendezvous circuits which have
7152 been specified in an INTRODUCE1 cell sent to a hidden service,
7153 after the normal CBT. Now, we mark them as 'timed out', and launch
7154 another rendezvous attempt in parallel. This behavior change can
7155 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
7156 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
7157 - Don't close hidden-service-side rendezvous circuits when they
7158 reach the normal circuit-build timeout. This behavior change can
7159 be disabled using the new
7160 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
7161 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
7162 - Make sure we never mark the wrong rendezvous circuit as having
7163 had its introduction cell acknowleged by the introduction-point
7164 relay. Previously, when we received an INTRODUCE_ACK cell on a
7165 client-side hidden-service introduction circuit, we might have
7166 marked a rendezvous circuit other than the one we specified in
7167 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
7168 a warning message and interfered with the hidden service
7169 connection-establishment process. Fixes bug 4759; bugfix on
7170 0.2.3.3-alpha, when we added the stream-isolation feature which
7171 might cause Tor to open multiple rendezvous circuits for the same
7173 - Don't trigger an assertion failure when we mark a new client-side
7174 hidden-service introduction circuit for close during the process
7175 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
7178 o Minor bugfixes (log messages):
7179 - Correctly spell "connect" in a log message on failure to create a
7180 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
7182 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
7183 Fixes bug 4856; bugfix on Tor 0.0.6.
7184 - Fix the log message describing how we work around discovering
7185 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
7186 4837; bugfix on 0.2.2.9-alpha.
7187 - When logging about a disallowed .exit name, do not also call it
7188 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
7190 o Minor bugfixes (build fixes):
7191 - During configure, detect when we're building with clang version
7192 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
7193 CFLAGS. clang doesn't support them yet.
7194 - During configure, search for library containing cos function as
7195 libm lives in libcore on some platforms (BeOS/Haiku). Linking
7196 against libm was hard-coded before. Fixes the first part of bug
7197 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
7199 - Detect attempts to build Tor on (as yet hypothetical) versions
7200 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
7201 fix for bug 4533. Bugfix on 0.2.2.28-beta.
7202 - Preprocessor directives should not be put inside the arguments
7203 of a macro. This would break compilation with GCC releases prior
7204 to version 3.3. We would never recommend such an old GCC version,
7205 but it is apparently required for binary compatibility on some
7206 platforms (namely, certain builds of Haiku). Fixes the other part
7207 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
7210 o Minor bugfixes (other):
7211 - Older Linux kernels erroneously respond to strange nmap behavior
7212 by having accept() return successfully with a zero-length
7213 socket. When this happens, just close the connection. Previously,
7214 we would try harder to learn the remote address: but there was
7215 no such remote address to learn, and our method for trying to
7216 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
7217 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
7218 - Fix null-pointer access that could occur if TLS allocation failed.
7219 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
7220 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
7221 accidentally been reverted.
7222 - Fix our implementation of crypto_random_hostname() so it can't
7223 overflow on ridiculously large inputs. (No Tor version has ever
7224 provided this kind of bad inputs, but let's be correct in depth.)
7225 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
7226 - Find more places in the code that should have been testing for
7227 invalid sockets using the SOCKET_OK macro. Required for a fix
7228 for bug 4533. Bugfix on 0.2.2.28-beta.
7229 - Fix an assertion failure when, while running with bufferevents, a
7230 connection finishes connecting after it is marked for close, but
7231 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
7232 - test_util_spawn_background_ok() hardcoded the expected value
7233 for ENOENT to 2. This isn't portable as error numbers are
7234 platform specific, and particularly the hurd has ENOENT at
7235 0x40000002. Construct expected string at runtime, using the correct
7236 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
7237 - Reject attempts to disable DisableDebuggerAttachment while Tor is
7238 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
7239 - Use an appropriate-width type for sockets in tor-fw-helper on
7240 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
7243 - When sending or relaying a RELAY_EARLY cell, we used to convert
7244 it to a RELAY cell if the connection was using the v1 link
7245 protocol. This was a workaround for older versions of Tor, which
7246 didn't handle RELAY_EARLY cells properly. Now that all supported
7247 versions can handle RELAY_EARLY cells, and now that we're enforcing
7248 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
7249 remove this workaround. Addresses bug 4786.
7251 o Code simplifications and refactoring:
7252 - Use OpenSSL's built-in SSL_state_string_long() instead of our
7253 own homebrewed ssl_state_to_string() replacement. Patch from
7254 Emile Snyder. Fixes bug 4653.
7255 - Use macros to indicate OpenSSL versions, so we don't need to worry
7256 about accidental hexadecimal bit shifts.
7257 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
7259 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
7260 - Use the smartlist_add_asprintf() alias more consistently.
7261 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
7262 invalid value, rather than just -1.
7263 - Rename a handful of old identifiers, mostly related to crypto
7264 structures and crypto functions. By convention, our "create an
7265 object" functions are called "type_new()", our "free an object"
7266 functions are called "type_free()", and our types indicate that
7267 they are types only with a final "_t". But a handful of older
7268 types and functions broke these rules, with function names like
7269 "type_create" or "subsystem_op_type", or with type names like
7273 Changes in version 0.2.3.10-alpha - 2011-12-16
7274 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
7275 Tor's buffers code. Absolutely everybody should upgrade.
7277 The bug relied on an incorrect calculation when making data continuous
7278 in one of our IO buffers, if the first chunk of the buffer was
7279 misaligned by just the wrong amount. The miscalculation would allow an
7280 attacker to overflow a piece of heap-allocated memory. To mount this
7281 attack, the attacker would need to either open a SOCKS connection to
7282 Tor's SocksPort (usually restricted to localhost), or target a Tor
7283 instance configured to make its connections through a SOCKS proxy
7284 (which Tor does not do by default).
7286 Good security practice requires that all heap-overflow bugs should be
7287 presumed to be exploitable until proven otherwise, so we are treating
7288 this as a potential code execution attack. Please upgrade immediately!
7289 This bug does not affect bufferevents-based builds of Tor. Special
7290 thanks to "Vektor" for reporting this issue to us!
7292 This release also contains a few minor bugfixes for issues discovered
7296 - Fix a heap overflow bug that could occur when trying to pull
7297 data into the first chunk of a buffer, when that chunk had
7298 already had some data drained from it. Fixes CVE-2011-2778;
7299 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7302 - If we can't attach streams to a rendezvous circuit when we
7303 finish connecting to a hidden service, clear the rendezvous
7304 circuit's stream-isolation state and try to attach streams
7305 again. Previously, we cleared rendezvous circuits' isolation
7306 state either too early (if they were freshly built) or not at all
7307 (if they had been built earlier and were cannibalized). Bugfix on
7308 0.2.3.3-alpha; fixes bug 4655.
7309 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
7310 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
7311 - Fix an assertion failure when a relay with accounting enabled
7312 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
7315 - Update to the December 6 2011 Maxmind GeoLite Country database.
7318 Changes in version 0.2.2.35 - 2011-12-16
7319 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
7320 buffers code. Absolutely everybody should upgrade.
7322 The bug relied on an incorrect calculation when making data continuous
7323 in one of our IO buffers, if the first chunk of the buffer was
7324 misaligned by just the wrong amount. The miscalculation would allow an
7325 attacker to overflow a piece of heap-allocated memory. To mount this
7326 attack, the attacker would need to either open a SOCKS connection to
7327 Tor's SocksPort (usually restricted to localhost), or target a Tor
7328 instance configured to make its connections through a SOCKS proxy
7329 (which Tor does not do by default).
7331 Good security practice requires that all heap-overflow bugs should be
7332 presumed to be exploitable until proven otherwise, so we are treating
7333 this as a potential code execution attack. Please upgrade immediately!
7334 This bug does not affect bufferevents-based builds of Tor. Special
7335 thanks to "Vektor" for reporting this issue to us!
7337 Tor 0.2.2.35 also fixes several bugs in previous versions, including
7338 crash bugs for unusual configurations, and a long-term bug that
7339 would prevent Tor from starting on Windows machines with draconian
7342 With this release, we remind everyone that 0.2.0.x has reached its
7343 formal end-of-life. Those Tor versions have many known flaws, and
7344 nobody should be using them. You should upgrade -- ideally to the
7345 0.2.2.x series. If you're using a Linux or BSD and its packages are
7346 obsolete, stop using those packages and upgrade anyway.
7348 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
7349 longer receive support after some time in early 2012.
7352 - Fix a heap overflow bug that could occur when trying to pull
7353 data into the first chunk of a buffer, when that chunk had
7354 already had some data drained from it. Fixes CVE-2011-2778;
7355 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7356 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
7357 that it doesn't attempt to allocate a socketpair. This could cause
7358 some problems on Windows systems with overzealous firewalls. Fix for
7359 bug 4457; workaround for Libevent versions 2.0.1-alpha through
7361 - If we mark an OR connection for close based on a cell we process,
7362 don't process any further cells on it. We already avoid further
7363 reads on marked-for-close connections, but now we also discard the
7364 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
7365 which was the first version where we might mark a connection for
7366 close based on processing a cell on it.
7367 - Correctly sanity-check that we don't underflow on a memory
7368 allocation (and then assert) for hidden service introduction
7369 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7370 bugfix on 0.2.1.5-alpha.
7371 - Fix a memory leak when we check whether a hidden service
7372 descriptor has any usable introduction points left. Fixes bug
7373 4424. Bugfix on 0.2.2.25-alpha.
7374 - Don't crash when we're running as a relay and don't have a GeoIP
7375 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
7376 we've had in the 0.2.3.x branch already.
7377 - When running as a client, do not print a misleading (and plain
7378 wrong) log message that we're collecting "directory request"
7379 statistics: clients don't collect statistics. Also don't create a
7380 useless (because empty) stats file in the stats/ directory. Fixes
7381 bug 4353; bugfix on 0.2.2.34.
7384 - Detect failure to initialize Libevent. This fix provides better
7385 detection for future instances of bug 4457.
7386 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
7387 function. This was eating up hideously large amounts of time on some
7388 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
7389 - Resolve an integer overflow bug in smartlist_ensure_capacity().
7390 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
7392 - Don't warn about unused log_mutex in log.c when building with
7393 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
7394 0.1.0.6-rc which introduced --disable-threads.
7395 - When configuring, starting, or stopping an NT service, stop
7396 immediately after the service configuration attempt has succeeded
7397 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
7398 - When sending a NETINFO cell, include the original address
7399 received for the other side, not its canonical address. Found
7400 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
7401 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
7402 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
7403 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
7404 occurred when a client tried to fetch a descriptor for a bridge
7405 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
7406 - Backport fixes for a pair of compilation warnings on Windows.
7407 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
7408 - If we had ever tried to call tor_addr_to_str on an address of
7409 unknown type, we would have done a strdup on an uninitialized
7410 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
7411 Reported by "troll_un".
7412 - Correctly detect and handle transient lookup failures from
7413 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
7414 Reported by "troll_un".
7415 - Fix null-pointer access that could occur if TLS allocation failed.
7416 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
7417 - Use tor_socket_t type for listener argument to accept(). Fixes bug
7418 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
7421 - Add two new config options for directory authorities:
7422 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
7423 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
7424 that is always sufficient to satisfy the bandwidth requirement for
7425 the Guard flag. Now it will be easier for researchers to simulate
7426 Tor networks with different values. Resolves ticket 4484.
7427 - When Tor ignores a hidden service specified in its configuration,
7428 include the hidden service's directory in the warning message.
7429 Previously, we would only tell the user that some hidden service
7430 was ignored. Bugfix on 0.0.6; fixes bug 4426.
7431 - Update to the December 6 2011 Maxmind GeoLite Country database.
7433 o Packaging changes:
7434 - Make it easier to automate expert package builds on Windows,
7435 by removing an absolute path from makensis.exe command.
7438 Changes in version 0.2.1.32 - 2011-12-16
7439 Tor 0.2.1.32 backports important security and privacy fixes for
7440 oldstable. This release is intended only for package maintainers and
7441 others who cannot use the 0.2.2 stable series. All others should be
7442 using Tor 0.2.2.x or newer.
7444 The Tor 0.2.1.x series will reach formal end-of-life some time in
7445 early 2012; we will stop releasing patches for it then.
7447 o Major bugfixes (also included in 0.2.2.x):
7448 - Correctly sanity-check that we don't underflow on a memory
7449 allocation (and then assert) for hidden service introduction
7450 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7451 bugfix on 0.2.1.5-alpha.
7452 - Fix a heap overflow bug that could occur when trying to pull
7453 data into the first chunk of a buffer, when that chunk had
7454 already had some data drained from it. Fixes CVE-2011-2778;
7455 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
7458 - Update to the December 6 2011 Maxmind GeoLite Country database.
7461 Changes in version 0.2.3.9-alpha - 2011-12-08
7462 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
7463 a "DisableNetwork" security feature that bundles can use to avoid
7464 touching the network until bridges are configured, moves forward on
7465 the pluggable transport design, fixes a flaw in the hidden service
7466 design that unnecessarily prevented clients with wrong clocks from
7467 reaching hidden services, and fixes a wide variety of other issues.
7470 - Clients can now connect to private bridges over IPv6. Bridges
7471 still need at least one IPv4 address in order to connect to
7472 other relays. Note that we don't yet handle the case where the
7473 user has two bridge lines for the same bridge (one IPv4, one
7474 IPv6). Implements parts of proposal 186.
7475 - New "DisableNetwork" config option to prevent Tor from launching any
7476 connections or accepting any connections except on a control port.
7477 Bundles and controllers can set this option before letting Tor talk
7478 to the rest of the network, for example to prevent any connections
7479 to a non-bridge address. Packages like Orbot can also use this
7480 option to instruct Tor to save power when the network is off.
7481 - Clients and bridges can now be configured to use a separate
7482 "transport" proxy. This approach makes the censorship arms race
7483 easier by allowing bridges to use protocol obfuscation plugins. It
7484 implements the "managed proxy" part of proposal 180 (ticket 3472).
7485 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
7486 implementation. It makes AES_CTR about 7% faster than our old one
7487 (which was about 10% faster than the one OpenSSL used to provide).
7488 Resolves ticket 4526.
7489 - Add a "tor2web mode" for clients that want to connect to hidden
7490 services non-anonymously (and possibly more quickly). As a safety
7491 measure to try to keep users from turning this on without knowing
7492 what they are doing, tor2web mode must be explicitly enabled at
7493 compile time, and a copy of Tor compiled to run in tor2web mode
7494 cannot be used as a normal Tor client. Implements feature 2553.
7495 - Add experimental support for running on Windows with IOCP and no
7496 kernel-space socket buffers. This feature is controlled by a new
7497 "UserspaceIOCPBuffers" config option (off by default), which has
7498 no effect unless Tor has been built with support for bufferevents,
7499 is running on Windows, and has enabled IOCP. This may, in the long
7500 run, help solve or mitigate bug 98.
7501 - Use a more secure consensus parameter voting algorithm. Now at
7502 least three directory authorities or a majority of them must
7503 vote on a given parameter before it will be included in the
7504 consensus. Implements proposal 178.
7507 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
7508 They used to check that the timestamp was within 30 minutes
7509 of their system clock, so they could cap the size of their
7510 replay-detection cache, but that approach unnecessarily refused
7511 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
7512 the v3 intro-point protocol (the first one which sent a timestamp
7513 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
7514 - Only use the EVP interface when AES acceleration is enabled,
7515 to avoid a 5-7% performance regression. Resolves issue 4525;
7516 bugfix on 0.2.3.8-alpha.
7518 o Privacy/anonymity features (bridge detection):
7519 - Make bridge SSL certificates a bit more stealthy by using random
7520 serial numbers, in the same fashion as OpenSSL when generating
7521 self-signed certificates. Implements ticket 4584.
7522 - Introduce a new config option "DynamicDHGroups", enabled by
7523 default, which provides each bridge with a unique prime DH modulus
7524 to be used during SSL handshakes. This option attempts to help
7525 against censors who might use the Apache DH modulus as a static
7526 identifier for bridges. Addresses ticket 4548.
7528 o Minor features (new/different config options):
7529 - New configuration option "DisableDebuggerAttachment" (on by default)
7530 to prevent basic debugging attachment attempts by other processes.
7531 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
7532 - Allow MapAddress directives to specify matches against super-domains,
7533 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
7534 Implements issue 933.
7535 - Slightly change behavior of "list" options (that is, config
7536 options that can appear more than once) when they appear both in
7537 torrc and on the command line. Previously, the command-line options
7538 would be appended to the ones from torrc. Now, the command-line
7539 options override the torrc options entirely. This new behavior
7540 allows the user to override list options (like exit policies and
7541 ports to listen on) from the command line, rather than simply
7542 appending to the list.
7543 - You can get the old (appending) command-line behavior for "list"
7544 options by prefixing the option name with a "+".
7545 - You can remove all the values for a "list" option from the command
7546 line without adding any new ones by prefixing the option name
7548 - Add experimental support for a "defaults" torrc file to be parsed
7549 before the regular torrc. Torrc options override the defaults file's
7550 options in the same way that the command line overrides the torrc.
7551 The SAVECONF controller command saves only those options which
7552 differ between the current configuration and the defaults file. HUP
7553 reloads both files. (Note: This is an experimental feature; its
7554 behavior will probably be refined in future 0.2.3.x-alpha versions
7555 to better meet packagers' needs.) Implements task 4552.
7558 - Try to make the introductory warning message that Tor prints on
7559 startup more useful for actually finding help and information.
7560 Resolves ticket 2474.
7561 - Running "make version" now displays the version of Tor that
7562 we're about to build. Idea from katmagic; resolves issue 4400.
7563 - Expire old or over-used hidden service introduction points.
7564 Required by fix for bug 3460.
7565 - Move the replay-detection cache for the RSA-encrypted parts of
7566 INTRODUCE2 cells to the introduction point data structures.
7567 Previously, we would use one replay-detection cache per hidden
7568 service. Required by fix for bug 3460.
7569 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
7570 public key replay-detection cache from 60 minutes to 5 minutes. This
7571 replay-detection cache is now used only to detect multiple
7572 INTRODUCE2 cells specifying the same rendezvous point, so we can
7573 avoid launching multiple simultaneous attempts to connect to it.
7575 o Minor bugfixes (on Tor 0.2.2.x and earlier):
7576 - Resolve an integer overflow bug in smartlist_ensure_capacity().
7577 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
7579 - Fix a minor formatting issue in one of tor-gencert's error messages.
7581 - Prevent a false positive from the check-spaces script, by disabling
7582 the "whitespace between function name and (" check for functions
7584 - Fix a log message suggesting that people contact a non-existent
7585 email address. Fixes bug 3448.
7586 - Fix null-pointer access that could occur if TLS allocation failed.
7587 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
7588 - Report a real bootstrap problem to the controller on router
7589 identity mismatch. Previously we just said "foo", which probably
7590 made a lot of sense at the time. Fixes bug 4169; bugfix on
7592 - If we had ever tried to call tor_addr_to_str() on an address of
7593 unknown type, we would have done a strdup() on an uninitialized
7594 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
7595 Reported by "troll_un".
7596 - Correctly detect and handle transient lookup failures from
7597 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
7598 Reported by "troll_un".
7599 - Use tor_socket_t type for listener argument to accept(). Fixes bug
7600 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
7601 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
7602 bug 4532; found by "troll_un".
7604 o Minor bugfixes (on Tor 0.2.3.x):
7605 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
7607 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
7608 circuit for use as a hidden service client's rendezvous point.
7609 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
7610 with help from wanoskarnet.
7611 - Restore behavior of overriding SocksPort, ORPort, and similar
7612 options from the command line. Bugfix on 0.2.3.3-alpha.
7615 - Properly handle the case where the build-tree is not the same
7616 as the source tree when generating src/common/common_sha1.i,
7617 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
7618 bugfix on 0.2.0.1-alpha.
7620 o Code simplifications, cleanups, and refactorings:
7621 - Remove the pure attribute from all functions that used it
7622 previously. In many cases we assigned it incorrectly, because the
7623 functions might assert or call impure functions, and we don't have
7624 evidence that keeping the pure attribute is worthwhile. Implements
7625 changes suggested in ticket 4421.
7626 - Remove some dead code spotted by coverity. Fixes cid 432.
7627 Bugfix on 0.2.3.1-alpha, closes bug 4637.
7630 Changes in version 0.2.3.8-alpha - 2011-11-22
7631 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
7632 socketpair-related bug that has been bothering Windows users. It adds
7633 support to serve microdescriptors to controllers, so Vidalia's network
7634 map can resume listing relays (once Vidalia implements its side),
7635 and adds better support for hardware AES acceleration. Finally, it
7636 starts the process of adjusting the bandwidth cutoff for getting the
7637 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
7638 that tiny relays harm performance more than they help network capacity.
7641 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
7642 that it doesn't attempt to allocate a socketpair. This could cause
7643 some problems on Windows systems with overzealous firewalls. Fix for
7644 bug 4457; workaround for Libevent versions 2.0.1-alpha through
7646 - Correctly sanity-check that we don't underflow on a memory
7647 allocation (and then assert) for hidden service introduction
7648 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
7649 bugfix on 0.2.1.5-alpha.
7650 - Remove the artificially low cutoff of 20KB to guarantee the Fast
7651 flag. In the past few years the average relay speed has picked
7652 up, and while the "top 7/8 of the network get the Fast flag" and
7653 "all relays with 20KB or more of capacity get the Fast flag" rules
7654 used to have the same result, now the top 7/8 of the network has
7655 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
7656 - Fix a rare assertion failure when checking whether a v0 hidden
7657 service descriptor has any usable introduction points left, and
7658 we don't have enough information to build a circuit to the first
7659 intro point named in the descriptor. The HS client code in
7660 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
7661 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
7662 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
7663 - Make bridge authorities not crash when they are asked for their own
7664 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
7665 - When running as a client, do not print a misleading (and plain
7666 wrong) log message that we're collecting "directory request"
7667 statistics: clients don't collect statistics. Also don't create a
7668 useless (because empty) stats file in the stats/ directory. Fixes
7669 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
7672 - Allow Tor controllers like Vidalia to obtain the microdescriptor
7673 for a relay by identity digest or nickname. Previously,
7674 microdescriptors were only available by their own digests, so a
7675 controller would have to ask for and parse the whole microdescriptor
7676 consensus in order to look up a single relay's microdesc. Fixes
7677 bug 3832; bugfix on 0.2.3.1-alpha.
7678 - Use OpenSSL's EVP interface for AES encryption, so that all AES
7679 operations can use hardware acceleration (if present). Resolves
7682 o Minor bugfixes (on 0.2.2.x and earlier):
7683 - Detect failure to initialize Libevent. This fix provides better
7684 detection for future instances of bug 4457.
7685 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
7686 function. This was eating up hideously large amounts of time on some
7687 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
7688 - Don't warn about unused log_mutex in log.c when building with
7689 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
7690 0.1.0.6-rc which introduced --disable-threads.
7691 - Allow manual 'authenticate' commands to the controller interface
7692 from netcat (nc) as well as telnet. We were rejecting them because
7693 they didn't come with the expected whitespace at the end of the
7694 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
7695 - Fix some (not actually triggerable) buffer size checks in usage of
7696 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
7698 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
7699 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
7700 - When configuring, starting, or stopping an NT service, stop
7701 immediately after the service configuration attempt has succeeded
7702 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
7703 - When sending a NETINFO cell, include the original address
7704 received for the other side, not its canonical address. Found
7705 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
7706 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
7707 can pick them up when the tests aren't disabled. Bugfix on
7708 0.2.2.4-alpha which introduced tinytest.
7709 - Fix a memory leak when we check whether a hidden service
7710 descriptor has any usable introduction points left. Fixes bug
7711 4424. Bugfix on 0.2.2.25-alpha.
7712 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
7713 occurred when a client tried to fetch a descriptor for a bridge
7714 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
7716 o Minor bugfixes (on 0.2.3.x):
7717 - Make util unit tests build correctly with MSVC. Bugfix on
7718 0.2.3.3-alpha. Patch by Gisle Vanem.
7719 - Successfully detect AUTH_CHALLENGE cells with no recognized
7720 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
7722 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
7723 it should still send a NETINFO cell to allow the connection to
7724 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
7726 - Log less loudly when we get an invalid authentication certificate
7727 from a source other than a directory authority: it's not unusual
7728 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
7730 - Tolerate servers with more clock skew in their authentication
7731 certificates than previously. Fixes bug 4371; bugfix on
7733 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
7734 on 0.2.3.4-alpha and 0.2.3.6-alpha.
7737 - Add two new config options for directory authorities:
7738 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
7739 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
7740 that is always sufficient to satisfy the bandwidth requirement for
7741 the Guard flag. Now it will be easier for researchers to simulate
7742 Tor networks with different values. Resolves ticket 4484.
7743 - When Tor ignores a hidden service specified in its configuration,
7744 include the hidden service's directory in the warning message.
7745 Previously, we would only tell the user that some hidden service
7746 was ignored. Bugfix on 0.0.6; fixes bug 4426.
7747 - When we fail to initialize Libevent, retry with IOCP disabled so we
7748 don't need to turn on multi-threading support in Libevent, which in
7749 turn requires a working socketpair(). This is a workaround for bug
7750 4457, which affects Libevent versions from 2.0.1-alpha through
7752 - Detect when we try to build on a platform that doesn't define
7753 AF_UNSPEC to 0. We don't work there, so refuse to compile.
7754 - Update to the November 1 2011 Maxmind GeoLite Country database.
7756 o Packaging changes:
7757 - Make it easier to automate expert package builds on Windows,
7758 by removing an absolute path from makensis.exe command.
7760 o Code simplifications and refactoring:
7761 - Remove some redundant #include directives throughout the code.
7762 Patch from Andrea Gelmini.
7763 - Unconditionally use OpenSSL's AES implementation instead of our
7764 old built-in one. OpenSSL's AES has been better for a while, and
7765 relatively few servers should still be on any version of OpenSSL
7766 that doesn't have good optimized assembly AES.
7767 - Use the name "CERTS" consistently to refer to the new cell type;
7768 we were calling it CERT in some places and CERTS in others.
7771 - Numerous new unit tests for functions in util.c and address.c by
7773 - The long-disabled benchmark tests are now split into their own
7774 ./src/test/bench binary.
7775 - The benchmark tests can now use more accurate timers than
7776 gettimeofday() when such timers are available.
7779 Changes in version 0.2.3.7-alpha - 2011-10-30
7780 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
7781 the new v3 handshake. It also resolves yet another bridge address
7785 - If we mark an OR connection for close based on a cell we process,
7786 don't process any further cells on it. We already avoid further
7787 reads on marked-for-close connections, but now we also discard the
7788 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
7789 which was the first version where we might mark a connection for
7790 close based on processing a cell on it.
7791 - Fix a double-free bug that would occur when we received an invalid
7792 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
7793 bugfix on 0.2.3.6-alpha.
7794 - Bridges no longer include their address in NETINFO cells on outgoing
7795 OR connections, to allow them to blend in better with clients.
7796 Removes another avenue for enumerating bridges. Reported by
7797 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
7798 cells were introduced.
7801 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
7802 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
7805 Changes in version 0.2.3.6-alpha - 2011-10-26
7806 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
7807 anonymity vulnerability where an attacker can deanonymize Tor
7808 users. Everybody should upgrade.
7810 This release also features support for a new v3 connection handshake
7811 protocol, and fixes to make hidden service connections more robust.
7814 - Implement a new handshake protocol (v3) for authenticating Tors to
7815 each other over TLS. It should be more resistant to fingerprinting
7816 than previous protocols, and should require less TLS hacking for
7817 future Tor implementations. Implements proposal 176.
7818 - Allow variable-length padding cells to disguise the length of
7819 Tor's TLS records. Implements part of proposal 184.
7821 o Privacy/anonymity fixes (clients):
7822 - Clients and bridges no longer send TLS certificate chains on
7823 outgoing OR connections. Previously, each client or bridge would
7824 use the same cert chain for all outgoing OR connections until
7825 its IP address changes, which allowed any relay that the client
7826 or bridge contacted to determine which entry guards it is using.
7827 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7828 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7829 no longer considers that connection as suitable for satisfying a
7830 circuit EXTEND request. Now relays can protect clients from the
7831 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7832 - Directory authorities no longer assign the Guard flag to relays
7833 that haven't upgraded to the above "refuse EXTEND requests
7834 to client connections" fix. Now directory authorities can
7835 protect clients from the CVE-2011-2768 issue even if neither
7836 the clients nor the relays have upgraded yet. There's a new
7837 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
7838 to let us transition smoothly, else tomorrow there would be no
7841 o Major bugfixes (hidden services):
7842 - Improve hidden service robustness: when an attempt to connect to
7843 a hidden service ends, be willing to refetch its hidden service
7844 descriptors from each of the HSDir relays responsible for them
7845 immediately. Previously, we would not consider refetching the
7846 service's descriptors from each HSDir for 15 minutes after the last
7847 fetch, which was inconvenient if the hidden service was not running
7848 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
7849 - When one of a hidden service's introduction points appears to be
7850 unreachable, stop trying it. Previously, we would keep trying
7851 to build circuits to the introduction point until we lost the
7852 descriptor, usually because the user gave up and restarted Tor.
7853 Partly fixes bug 3825.
7854 - Don't launch a useless circuit after failing to use one of a
7855 hidden service's introduction points. Previously, we would
7856 launch a new introduction circuit, but not set the hidden service
7857 which that circuit was intended to connect to, so it would never
7858 actually be used. A different piece of code would then create a
7859 new introduction circuit correctly. Bug reported by katmagic and
7860 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
7862 o Major bugfixes (other):
7863 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7864 that they initiated. Relays could distinguish incoming bridge
7865 connections from client connections, creating another avenue for
7866 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7867 Found by "frosty_un".
7868 - Don't update the AccountingSoftLimitHitAt state file entry whenever
7869 tor gets started. This prevents a wrong average bandwidth
7870 estimate, which would cause relays to always start a new accounting
7871 interval at the earliest possible moment. Fixes bug 2003; bugfix
7872 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
7873 immensely in tracking this bug down.
7874 - Fix a crash bug when changing node restrictions while a DNS lookup
7875 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
7878 o Minor bugfixes (on 0.2.2.x and earlier):
7879 - When a hidden service turns an extra service-side introduction
7880 circuit into a general-purpose circuit, free the rend_data and
7881 intro_key fields first, so we won't leak memory if the circuit
7882 is cannibalized for use as another service-side introduction
7883 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
7884 - Rephrase the log message emitted if the TestSocks check is
7885 successful. Patch from Fabian Keil; fixes bug 4094.
7886 - Bridges now skip DNS self-tests, to act a little more stealthily.
7887 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
7888 bridges. Patch by "warms0x".
7889 - Remove a confusing dollar sign from the example fingerprint in the
7890 man page, and also make the example fingerprint a valid one. Fixes
7891 bug 4309; bugfix on 0.2.1.3-alpha.
7892 - Fix internal bug-checking logic that was supposed to catch
7893 failures in digest generation so that it will fail more robustly
7894 if we ask for a nonexistent algorithm. Found by Coverity Scan.
7895 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
7896 - Report any failure in init_keys() calls launched because our
7897 IP address has changed. Spotted by Coverity Scan. Bugfix on
7898 0.1.1.4-alpha; fixes CID 484.
7900 o Minor bugfixes (on 0.2.3.x):
7901 - Fix a bug in configure.in that kept it from building a configure
7902 script with autoconf versions earlier than 2.61. Fixes bug 2430;
7903 bugfix on 0.2.3.1-alpha.
7904 - Don't warn users that they are exposing a client port to the
7905 Internet if they have specified an RFC1918 address. Previously,
7906 we would warn if the user had specified any non-loopback
7907 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
7908 - Fix memory leaks in the failing cases of the new SocksPort and
7909 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
7910 fixes coverity CIDs 485, 486, and 487.
7913 - When a hidden service's introduction point times out, consider
7914 trying it again during the next attempt to connect to the
7915 HS. Previously, we would not try it again unless a newly fetched
7916 descriptor contained it. Required by fixes for bugs 1297 and 3825.
7917 - The next version of Windows will be called Windows 8, and it has
7918 a major version of 6, minor version of 2. Correctly identify that
7919 version instead of calling it "Very recent version". Resolves
7920 ticket 4153; reported by funkstar.
7921 - The Bridge Authority now writes statistics on how many bridge
7922 descriptors it gave out in total, and how many unique descriptors
7923 it gave out. It also lists how often the most and least commonly
7924 fetched descriptors were given out, as well as the median and
7925 25th/75th percentile. Implements tickets 4200 and 4294.
7926 - Update to the October 4 2011 Maxmind GeoLite Country database.
7928 o Code simplifications and refactoring:
7929 - Remove some old code to remember statistics about which descriptors
7930 we've served as a directory mirror. The feature wasn't used and
7931 is outdated now that microdescriptors are around.
7932 - Rename Tor functions that turn strings into addresses, so that
7933 "parse" indicates that no hostname resolution occurs, and
7934 "lookup" indicates that hostname resolution may occur. This
7935 should help prevent mistakes in the future. Fixes bug 3512.
7938 Changes in version 0.2.2.34 - 2011-10-26
7939 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
7940 can deanonymize Tor users. Everybody should upgrade.
7942 The attack relies on four components: 1) Clients reuse their TLS cert
7943 when talking to different relays, so relays can recognize a user by
7944 the identity key in her cert. 2) An attacker who knows the client's
7945 identity key can probe each guard relay to see if that identity key
7946 is connected to that guard relay right now. 3) A variety of active
7947 attacks in the literature (starting from "Low-Cost Traffic Analysis
7948 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
7949 discover the guard relays that a Tor user visiting the website is using.
7950 4) Clients typically pick three guards at random, so the set of guards
7951 for a given user could well be a unique fingerprint for her. This
7952 release fixes components #1 and #2, which is enough to block the attack;
7953 the other two remain as open research problems. Special thanks to
7954 "frosty_un" for reporting the issue to us!
7956 Clients should upgrade so they are no longer recognizable by the TLS
7957 certs they present. Relays should upgrade so they no longer allow a
7958 remote attacker to probe them to test whether unpatched clients are
7959 currently connected to them.
7961 This release also fixes several vulnerabilities that allow an attacker
7962 to enumerate bridge relays. Some bridge enumeration attacks still
7963 remain; see for example proposal 188.
7965 o Privacy/anonymity fixes (clients):
7966 - Clients and bridges no longer send TLS certificate chains on
7967 outgoing OR connections. Previously, each client or bridge would
7968 use the same cert chain for all outgoing OR connections until
7969 its IP address changes, which allowed any relay that the client
7970 or bridge contacted to determine which entry guards it is using.
7971 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7972 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7973 no longer considers that connection as suitable for satisfying a
7974 circuit EXTEND request. Now relays can protect clients from the
7975 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7976 - Directory authorities no longer assign the Guard flag to relays
7977 that haven't upgraded to the above "refuse EXTEND requests
7978 to client connections" fix. Now directory authorities can
7979 protect clients from the CVE-2011-2768 issue even if neither
7980 the clients nor the relays have upgraded yet. There's a new
7981 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
7982 to let us transition smoothly, else tomorrow there would be no
7985 o Privacy/anonymity fixes (bridge enumeration):
7986 - Bridge relays now do their directory fetches inside Tor TLS
7987 connections, like all the other clients do, rather than connecting
7988 directly to the DirPort like public relays do. Removes another
7989 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
7990 - Bridges relays now build circuits for themselves in a more similar
7991 way to how clients build them. Removes another avenue for
7992 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
7993 when bridges were introduced.
7994 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7995 that they initiated. Relays could distinguish incoming bridge
7996 connections from client connections, creating another avenue for
7997 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7998 Found by "frosty_un".
8001 - Fix a crash bug when changing node restrictions while a DNS lookup
8002 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
8004 - Don't launch a useless circuit after failing to use one of a
8005 hidden service's introduction points. Previously, we would
8006 launch a new introduction circuit, but not set the hidden service
8007 which that circuit was intended to connect to, so it would never
8008 actually be used. A different piece of code would then create a
8009 new introduction circuit correctly. Bug reported by katmagic and
8010 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
8013 - Change an integer overflow check in the OpenBSD_Malloc code so
8014 that GCC is less likely to eliminate it as impossible. Patch
8015 from Mansour Moufid. Fixes bug 4059.
8016 - When a hidden service turns an extra service-side introduction
8017 circuit into a general-purpose circuit, free the rend_data and
8018 intro_key fields first, so we won't leak memory if the circuit
8019 is cannibalized for use as another service-side introduction
8020 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
8021 - Bridges now skip DNS self-tests, to act a little more stealthily.
8022 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
8023 bridges. Patch by "warms0x".
8024 - Fix internal bug-checking logic that was supposed to catch
8025 failures in digest generation so that it will fail more robustly
8026 if we ask for a nonexistent algorithm. Found by Coverity Scan.
8027 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
8028 - Report any failure in init_keys() calls launched because our
8029 IP address has changed. Spotted by Coverity Scan. Bugfix on
8030 0.1.1.4-alpha; fixes CID 484.
8032 o Minor bugfixes (log messages and documentation):
8033 - Remove a confusing dollar sign from the example fingerprint in the
8034 man page, and also make the example fingerprint a valid one. Fixes
8035 bug 4309; bugfix on 0.2.1.3-alpha.
8036 - The next version of Windows will be called Windows 8, and it has
8037 a major version of 6, minor version of 2. Correctly identify that
8038 version instead of calling it "Very recent version". Resolves
8039 ticket 4153; reported by funkstar.
8040 - Downgrade log messages about circuit timeout calibration from
8041 "notice" to "info": they don't require or suggest any human
8042 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
8043 bugfix on 0.2.2.14-alpha.
8046 - Turn on directory request statistics by default and include them in
8047 extra-info descriptors. Don't break if we have no GeoIP database.
8048 Backported from 0.2.3.1-alpha; implements ticket 3951.
8049 - Update to the October 4 2011 Maxmind GeoLite Country database.
8052 Changes in version 0.2.1.31 - 2011-10-26
8053 Tor 0.2.1.31 backports important security and privacy fixes for
8054 oldstable. This release is intended only for package maintainers and
8055 others who cannot use the 0.2.2 stable series. All others should be
8056 using Tor 0.2.2.x or newer.
8058 o Security fixes (also included in 0.2.2.x):
8059 - Replace all potentially sensitive memory comparison operations
8060 with versions whose runtime does not depend on the data being
8061 compared. This will help resist a class of attacks where an
8062 adversary can use variations in timing information to learn
8063 sensitive data. Fix for one case of bug 3122. (Safe memcmp
8064 implementation by Robert Ransom based partially on code by DJB.)
8065 - Fix an assert in parsing router descriptors containing IPv6
8066 addresses. This one took down the directory authorities when
8067 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
8069 o Privacy/anonymity fixes (also included in 0.2.2.x):
8070 - Clients and bridges no longer send TLS certificate chains on
8071 outgoing OR connections. Previously, each client or bridge would
8072 use the same cert chain for all outgoing OR connections until
8073 its IP address changes, which allowed any relay that the client
8074 or bridge contacted to determine which entry guards it is using.
8075 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8076 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8077 no longer considers that connection as suitable for satisfying a
8078 circuit EXTEND request. Now relays can protect clients from the
8079 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8080 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8081 that they initiated. Relays could distinguish incoming bridge
8082 connections from client connections, creating another avenue for
8083 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8084 Found by "frosty_un".
8085 - When receiving a hidden service descriptor, check that it is for
8086 the hidden service we wanted. Previously, Tor would store any
8087 hidden service descriptors that a directory gave it, whether it
8088 wanted them or not. This wouldn't have let an attacker impersonate
8089 a hidden service, but it did let directories pre-seed a client
8090 with descriptors that it didn't want. Bugfix on 0.0.6.
8091 - Avoid linkability based on cached hidden service descriptors: forget
8092 all hidden service descriptors cached as a client when processing a
8093 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
8094 - Make the bridge directory authority refuse to answer directory
8095 requests for "all" descriptors. It used to include bridge
8096 descriptors in its answer, which was a major information leak.
8097 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
8098 - Don't attach new streams to old rendezvous circuits after SIGNAL
8099 NEWNYM. Previously, we would keep using an existing rendezvous
8100 circuit if it remained open (i.e. if it were kept open by a
8101 long-lived stream, or if a new stream were attached to it before
8102 Tor could notice that it was old and no longer in use). Bugfix on
8103 0.1.1.15-rc; fixes bug 3375.
8105 o Minor bugfixes (also included in 0.2.2.x):
8106 - When we restart our relay, we might get a successful connection
8107 from the outside before we've started our reachability tests,
8108 triggering a warning: "ORPort found reachable, but I have no
8109 routerinfo yet. Failing to inform controller of success." This
8110 bug was harmless unless Tor is running under a controller
8111 like Vidalia, in which case the controller would never get a
8112 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
8114 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
8115 enabled. Fixes bug 1526.
8116 - Remove undocumented option "-F" from tor-resolve: it hasn't done
8117 anything since 0.2.1.16-rc.
8118 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
8119 None of the cases where we did this before were wrong, but by making
8120 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
8121 - Fix a rare crash bug that could occur when a client was configured
8122 with a large number of bridges. Fixes bug 2629; bugfix on
8123 0.2.1.2-alpha. Bugfix by trac user "shitlei".
8124 - Correct the warning displayed when a rendezvous descriptor exceeds
8125 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
8127 - Fix an uncommon assertion failure when running with DNSPort under
8128 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
8129 - When warning about missing zlib development packages during compile,
8130 give the correct package names. Bugfix on 0.2.0.1-alpha.
8131 - Require that introduction point keys and onion keys have public
8132 exponent 65537. Bugfix on 0.2.0.10-alpha.
8133 - Do not crash when our configuration file becomes unreadable, for
8134 example due to a permissions change, between when we start up
8135 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
8137 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
8139 - Always NUL-terminate the sun_path field of a sockaddr_un before
8140 passing it to the kernel. (Not a security issue: kernels are
8141 smart enough to reject bad sockaddr_uns.) Found by Coverity;
8142 CID #428. Bugfix on Tor 0.2.0.3-alpha.
8143 - Don't stack-allocate the list of supplementary GIDs when we're
8144 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
8145 could take up to 256K, which is way too much stack. Found by
8146 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
8148 o Minor bugfixes (only in 0.2.1.x):
8149 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
8150 rely on them. Bugfix on 0.2.1.30.
8151 - Use git revisions instead of svn revisions when generating our
8152 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
8154 o Minor features (also included in 0.2.2.x):
8155 - Adjust the expiration time on our SSL session certificates to
8156 better match SSL certs seen in the wild. Resolves ticket 4014.
8157 - Allow nameservers with IPv6 address. Resolves bug 2574.
8158 - Update to the October 4 2011 Maxmind GeoLite Country database.
8161 Changes in version 0.2.3.5-alpha - 2011-09-28
8162 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
8163 bridge relays; fixes an assertion error that many users started hitting
8164 today; and adds the ability to refill token buckets more often than
8165 once per second, allowing significant performance improvements.
8168 - Bridge relays now do their directory fetches inside Tor TLS
8169 connections, like all the other clients do, rather than connecting
8170 directly to the DirPort like public relays do. Removes another
8171 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
8172 - Bridges relays now build circuits for themselves in a more similar
8173 way to how clients build them. Removes another avenue for
8174 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
8175 when bridges were introduced.
8178 - Fix an "Assertion md->held_by_node == 1 failed" error that could
8179 occur when the same microdescriptor was referenced by two node_t
8180 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
8182 o Major features (networking):
8183 - Add a new TokenBucketRefillInterval option to refill token buckets
8184 more frequently than once per second. This should improve network
8185 performance, alleviate queueing problems, and make traffic less
8186 bursty. Implements proposal 183; closes ticket 3630. Design by
8187 Florian Tschorsch and Björn Scheuermann; implementation by
8191 - Change an integer overflow check in the OpenBSD_Malloc code so
8192 that GCC is less likely to eliminate it as impossible. Patch
8193 from Mansour Moufid. Fixes bug 4059.
8195 o Minor bugfixes (usability):
8196 - Downgrade log messages about circuit timeout calibration from
8197 "notice" to "info": they don't require or suggest any human
8198 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
8199 bugfix on 0.2.2.14-alpha.
8201 o Minor features (diagnostics):
8202 - When the system call to create a listener socket fails, log the
8203 error message explaining why. This may help diagnose bug 4027.
8206 Changes in version 0.2.3.4-alpha - 2011-09-13
8207 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
8208 tweak to Tor's TLS handshake that makes relays and bridges that run
8209 this new version reachable from Iran again. It also fixes a few new
8210 bugs in 0.2.3.x, and teaches relays to recognize when they're not
8211 listed in the network consensus and republish.
8213 o Major bugfixes (also part of 0.2.2.33):
8214 - Avoid an assertion failure when reloading a configuration with
8215 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
8216 3923; bugfix on 0.2.2.25-alpha.
8218 o Minor features (security, also part of 0.2.2.33):
8219 - Check for replays of the public-key encrypted portion of an
8220 INTRODUCE1 cell, in addition to the current check for replays of
8221 the g^x value. This prevents a possible class of active attacks
8222 by an attacker who controls both an introduction point and a
8223 rendezvous point, and who uses the malleability of AES-CTR to
8224 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
8225 that these attacks are infeasible (requiring the attacker to send
8226 on the order of zettabytes of altered cells in a short interval),
8227 but we'd rather block them off in case there are any classes of
8228 this attack that we missed. Reported by Willem Pinckaers.
8230 o Minor features (also part of 0.2.2.33):
8231 - Adjust the expiration time on our SSL session certificates to
8232 better match SSL certs seen in the wild. Resolves ticket 4014.
8233 - Change the default required uptime for a relay to be accepted as
8234 a HSDir (hidden service directory) from 24 hours to 25 hours.
8235 Improves on 0.2.0.10-alpha; resolves ticket 2649.
8236 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
8237 authorities to abstain from voting on assignment of the HSDir
8238 consensus flag. Related to bug 2649.
8239 - Update to the September 6 2011 Maxmind GeoLite Country database.
8241 o Minor bugfixes (also part of 0.2.2.33):
8242 - Demote the 'replay detected' log message emitted when a hidden
8243 service receives the same Diffie-Hellman public key in two different
8244 INTRODUCE2 cells to info level. A normal Tor client can cause that
8245 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
8246 fixes part of bug 2442.
8247 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
8248 level. There is nothing that a hidden service's operator can do
8249 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
8251 - Clarify a log message specifying the characters permitted in
8252 HiddenServiceAuthorizeClient client names. Previously, the log
8253 message said that "[A-Za-z0-9+-_]" were permitted; that could have
8254 given the impression that every ASCII character between "+" and "_"
8255 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
8257 o Build fixes (also part of 0.2.2.33):
8258 - Clean up some code issues that prevented Tor from building on older
8259 BSDs. Fixes bug 3894; reported by "grarpamp".
8260 - Search for a platform-specific version of "ar" when cross-compiling.
8261 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
8264 - Fix a bug where the SocksPort option (for example) would get
8265 ignored and replaced by the default if a SocksListenAddress
8266 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
8270 - Relays now try regenerating and uploading their descriptor more
8271 frequently if they are not listed in the consensus, or if the
8272 version of their descriptor listed in the consensus is too
8273 old. This fix should prevent situations where a server declines
8274 to re-publish itself because it has done so too recently, even
8275 though the authorities decided not to list its recent-enough
8276 descriptor. Fix for bug 3327.
8279 - Relays now include a reason for regenerating their descriptors
8280 in an HTTP header when uploading to the authorities. This will
8281 make it easier to debug descriptor-upload issues in the future.
8282 - When starting as root and then changing our UID via the User
8283 control option, and we have a ControlSocket configured, make sure
8284 that the ControlSocket is owned by the same account that Tor will
8285 run under. Implements ticket 3421; fix by Jérémy Bobbio.
8288 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
8289 utility function used in the control-port code). This shouldn't
8290 ever happen unless Tor is completely out of memory, but if it did
8291 happen and Tor somehow recovered from it, Tor could have sent a log
8292 message to a control port in the middle of a reply to a controller
8293 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
8294 - Make 'FetchUselessDescriptors' cause all descriptor types and
8295 all consensus types (including microdescriptors) to get fetched.
8296 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
8299 - Make a new "entry connection" struct as an internal subtype of "edge
8300 connection", to simplify the code and make exit connections smaller.
8303 Changes in version 0.2.2.33 - 2011-09-13
8304 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
8305 TLS handshake that makes relays and bridges that run this new version
8306 reachable from Iran again.
8309 - Avoid an assertion failure when reloading a configuration with
8310 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
8311 3923; bugfix on 0.2.2.25-alpha.
8313 o Minor features (security):
8314 - Check for replays of the public-key encrypted portion of an
8315 INTRODUCE1 cell, in addition to the current check for replays of
8316 the g^x value. This prevents a possible class of active attacks
8317 by an attacker who controls both an introduction point and a
8318 rendezvous point, and who uses the malleability of AES-CTR to
8319 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
8320 that these attacks are infeasible (requiring the attacker to send
8321 on the order of zettabytes of altered cells in a short interval),
8322 but we'd rather block them off in case there are any classes of
8323 this attack that we missed. Reported by Willem Pinckaers.
8326 - Adjust the expiration time on our SSL session certificates to
8327 better match SSL certs seen in the wild. Resolves ticket 4014.
8328 - Change the default required uptime for a relay to be accepted as
8329 a HSDir (hidden service directory) from 24 hours to 25 hours.
8330 Improves on 0.2.0.10-alpha; resolves ticket 2649.
8331 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
8332 authorities to abstain from voting on assignment of the HSDir
8333 consensus flag. Related to bug 2649.
8334 - Update to the September 6 2011 Maxmind GeoLite Country database.
8336 o Minor bugfixes (documentation and log messages):
8337 - Correct the man page to explain that HashedControlPassword and
8338 CookieAuthentication can both be set, in which case either method
8339 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
8340 when we decided to allow these config options to both be set. Issue
8342 - Demote the 'replay detected' log message emitted when a hidden
8343 service receives the same Diffie-Hellman public key in two different
8344 INTRODUCE2 cells to info level. A normal Tor client can cause that
8345 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
8346 fixes part of bug 2442.
8347 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
8348 level. There is nothing that a hidden service's operator can do
8349 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
8351 - Clarify a log message specifying the characters permitted in
8352 HiddenServiceAuthorizeClient client names. Previously, the log
8353 message said that "[A-Za-z0-9+-_]" were permitted; that could have
8354 given the impression that every ASCII character between "+" and "_"
8355 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
8358 - Provide a substitute implementation of lround() for MSVC, which
8359 apparently lacks it. Patch from Gisle Vanem.
8360 - Clean up some code issues that prevented Tor from building on older
8361 BSDs. Fixes bug 3894; reported by "grarpamp".
8362 - Search for a platform-specific version of "ar" when cross-compiling.
8363 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
8366 Changes in version 0.2.3.3-alpha - 2011-09-01
8367 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
8368 security, and provides client-side support for the microdescriptor
8369 and optimistic data features introduced earlier in the 0.2.3.x
8370 series. It also includes numerous critical bugfixes in the (optional)
8371 bufferevent-based networking backend.
8373 o Major features (stream isolation):
8374 - You can now configure Tor so that streams from different
8375 applications are isolated on different circuits, to prevent an
8376 attacker who sees your streams as they leave an exit node from
8377 linking your sessions to one another. To do this, choose some way
8378 to distinguish the applications: have them connect to different
8379 SocksPorts, or have one of them use SOCKS4 while the other uses
8380 SOCKS5, or have them pass different authentication strings to the
8381 SOCKS proxy. Then, use the new SocksPort syntax to configure the
8382 degree of isolation you need. This implements Proposal 171.
8383 - There's a new syntax for specifying multiple client ports (such as
8384 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
8385 multiple *Port entries with full addr:port syntax on each.
8386 The old *ListenAddress format is still supported, but you can't
8387 mix it with the new *Port syntax.
8389 o Major features (other):
8390 - Enable microdescriptor fetching by default for clients. This allows
8391 clients to download a much smaller amount of directory information.
8392 To disable it (and go back to the old-style consensus and
8393 descriptors), set "UseMicrodescriptors 0" in your torrc file.
8394 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
8395 "PortForwarding" config option), now supports Windows.
8396 - When using an exit relay running 0.2.3.x, clients can now
8397 "optimistically" send data before the exit relay reports that
8398 the stream has opened. This saves a round trip when starting
8399 connections where the client speaks first (such as web browsing).
8400 This behavior is controlled by a consensus parameter (currently
8401 disabled). To turn it on or off manually, use the "OptimisticData"
8402 torrc option. Implements proposal 181; code by Ian Goldberg.
8404 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
8405 - When using IOCP on Windows, we need to enable Libevent windows
8407 - The IOCP backend now works even when the user has not specified
8408 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
8409 Fixes part of bug 3752.
8410 - Correctly record the bytes we've read and written when using
8411 bufferevents, so that we can include them in our bandwidth history
8412 and advertised bandwidth. Fixes bug 3803.
8413 - Apply rate-limiting only at the bottom of a chain of filtering
8414 bufferevents. This prevents us from filling up internal read
8415 buffers and violating rate-limits when filtering bufferevents
8416 are enabled. Fixes part of bug 3804.
8417 - Add high-watermarks to the output buffers for filtered
8418 bufferevents. This prevents us from filling up internal write
8419 buffers and wasting CPU cycles when filtering bufferevents are
8420 enabled. Fixes part of bug 3804.
8421 - Correctly notice when data has been written from a bufferevent
8422 without flushing it completely. Fixes bug 3805.
8423 - Fix a bug where server-side tunneled bufferevent-based directory
8424 streams would get closed prematurely. Fixes bug 3814.
8425 - Fix a use-after-free error with per-connection rate-limiting
8426 buckets. Fixes bug 3888.
8428 o Major bugfixes (also part of 0.2.2.31-rc):
8429 - If we're configured to write our ControlPorts to disk, only write
8430 them after switching UID and creating the data directory. This way,
8431 we don't fail when starting up with a nonexistent DataDirectory
8432 and a ControlPortWriteToFile setting based on that directory. Fixes
8433 bug 3747; bugfix on Tor 0.2.2.26-beta.
8436 - Added a new CONF_CHANGED event so that controllers can be notified
8437 of any configuration changes made by other controllers, or by the
8438 user. Implements ticket 1692.
8439 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
8440 leak when using bufferevents, and lets Libevent worry about how to
8441 best copy data out of a buffer.
8442 - Replace files in stats/ rather than appending to them. Now that we
8443 include statistics in extra-info descriptors, it makes no sense to
8444 keep old statistics forever. Implements ticket 2930.
8446 o Minor features (build compatibility):
8447 - Limited, experimental support for building with nmake and MSVC.
8448 - Provide a substitute implementation of lround() for MSVC, which
8449 apparently lacks it. Patch from Gisle Vanem.
8451 o Minor features (also part of 0.2.2.31-rc):
8452 - Update to the August 2 2011 Maxmind GeoLite Country database.
8454 o Minor bugfixes (on 0.2.3.x-alpha):
8455 - Fix a spurious warning when parsing SOCKS requests with
8456 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
8457 - Get rid of a harmless warning that could happen on relays running
8458 with bufferevents. The warning was caused by someone doing an http
8459 request to a relay's orport. Also don't warn for a few related
8460 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
8462 o Minor bugfixes (on 2.2.x and earlier):
8463 - Correct the man page to explain that HashedControlPassword and
8464 CookieAuthentication can both be set, in which case either method
8465 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
8466 when we decided to allow these config options to both be set. Issue
8468 - The "--quiet" and "--hush" options now apply not only to Tor's
8469 behavior before logs are configured, but also to Tor's behavior in
8470 the absense of configured logs. Fixes bug 3550; bugfix on
8473 o Minor bugfixes (also part of 0.2.2.31-rc):
8474 - Write several files in text mode, on OSes that distinguish text
8475 mode from binary mode (namely, Windows). These files are:
8476 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
8477 that collect those statistics; 'client_keys' and 'hostname' for
8478 hidden services that use authentication; and (in the tor-gencert
8479 utility) newly generated identity and signing keys. Previously,
8480 we wouldn't specify text mode or binary mode, leading to an
8481 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
8482 the DirRecordUsageByCountry option which would have triggered
8483 the assertion failure was added), although this assertion failure
8484 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
8485 - Selectively disable deprecation warnings on OS X because Lion
8486 started deprecating the shipped copy of openssl. Fixes bug 3643.
8487 - Remove an extra pair of quotation marks around the error
8488 message in control-port STATUS_GENERAL BUG events. Bugfix on
8489 0.1.2.6-alpha; fixes bug 3732.
8490 - When unable to format an address as a string, report its value
8491 as "???" rather than reusing the last formatted address. Bugfix
8494 o Code simplifications and refactoring:
8495 - Rewrite the listener-selection logic so that parsing which ports
8496 we want to listen on is now separate from binding to the ports
8500 - Building Tor with bufferevent support now requires Libevent
8501 2.0.13-stable or later. Previous versions of Libevent had bugs in
8502 SSL-related bufferevents and related issues that would make Tor
8503 work badly with bufferevents. Requiring 2.0.13-stable also allows
8504 Tor with bufferevents to take advantage of Libevent APIs
8505 introduced after 2.0.8-rc.
8508 Changes in version 0.2.2.32 - 2011-08-27
8509 The Tor 0.2.2 release series is dedicated to the memory of Andreas
8510 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
8511 a founder of the PETS community, a leader in our field, a mentor,
8512 and a friend. He left us with these words: "I had the possibility
8513 to contribute to this world that is not as it should be. I hope I
8514 could help in some areas to make the world a better place, and that
8515 I could also encourage other people to be engaged in improving the
8516 world. Please, stay engaged. This world needs you, your love, your
8517 initiative -- now I cannot be part of that anymore."
8519 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
8520 ready. More than two years in the making, this release features improved
8521 client performance and hidden service reliability, better compatibility
8522 for Android, correct behavior for bridges that listen on more than
8523 one address, more extensible and flexible directory object handling,
8524 better reporting of network statistics, improved code security, and
8525 many many other features and bugfixes.
8528 Changes in version 0.2.2.31-rc - 2011-08-17
8529 Tor 0.2.2.31-rc is the second and hopefully final release candidate
8530 for the Tor 0.2.2.x series.
8533 - Remove an extra pair of quotation marks around the error
8534 message in control-port STATUS_GENERAL BUG events. Bugfix on
8535 0.1.2.6-alpha; fixes bug 3732.
8536 - If we're configured to write our ControlPorts to disk, only write
8537 them after switching UID and creating the data directory. This way,
8538 we don't fail when starting up with a nonexistent DataDirectory
8539 and a ControlPortWriteToFile setting based on that directory. Fixes
8540 bug 3747; bugfix on Tor 0.2.2.26-beta.
8543 - Update to the August 2 2011 Maxmind GeoLite Country database.
8546 - Allow GETINFO fingerprint to return a fingerprint even when
8547 we have not yet built a router descriptor. Fixes bug 3577;
8548 bugfix on 0.2.0.1-alpha.
8549 - Write several files in text mode, on OSes that distinguish text
8550 mode from binary mode (namely, Windows). These files are:
8551 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
8552 that collect those statistics; 'client_keys' and 'hostname' for
8553 hidden services that use authentication; and (in the tor-gencert
8554 utility) newly generated identity and signing keys. Previously,
8555 we wouldn't specify text mode or binary mode, leading to an
8556 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
8557 the DirRecordUsageByCountry option which would have triggered
8558 the assertion failure was added), although this assertion failure
8559 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
8560 - Selectively disable deprecation warnings on OS X because Lion
8561 started deprecating the shipped copy of openssl. Fixes bug 3643.
8562 - When unable to format an address as a string, report its value
8563 as "???" rather than reusing the last formatted address. Bugfix
8567 Changes in version 0.2.3.2-alpha - 2011-07-18
8568 Tor 0.2.3.2-alpha introduces two new experimental features:
8569 microdescriptors and pluggable transports. It also continues cleaning
8570 up a variety of recently introduced features.
8573 - Clients can now use microdescriptors instead of regular descriptors
8574 to build circuits. Microdescriptors are authority-generated
8575 summaries of regular descriptors' contents, designed to change
8576 very rarely (see proposal 158 for details). This feature is
8577 designed to save bandwidth, especially for clients on slow internet
8578 connections. It's off by default for now, since nearly no caches
8579 support it, but it will be on-by-default for clients in a future
8580 version. You can use the UseMicrodescriptors option to turn it on.
8581 - Tor clients using bridges can now be configured to use a separate
8582 'transport' proxy for each bridge. This approach helps to resist
8583 censorship by allowing bridges to use protocol obfuscation
8584 plugins. It implements part of proposal 180. Implements ticket 2841.
8585 - While we're trying to bootstrap, record how many TLS connections
8586 fail in each state, and report which states saw the most failures
8587 in response to any bootstrap failures. This feature may speed up
8588 diagnosis of censorship events. Implements ticket 3116.
8590 o Major bugfixes (on 0.2.3.1-alpha):
8591 - When configuring a large set of nodes in EntryNodes (as with
8592 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
8593 random subset to be guards, and choose them in random
8594 order. Fixes bug 2798.
8595 - Tor could crash when remembering a consensus in a non-used consensus
8596 flavor without having a current consensus set. Fixes bug 3361.
8597 - Comparing an unknown address to a microdescriptor's shortened exit
8598 policy would always give a "rejected" result. Fixes bug 3599.
8599 - Using microdescriptors as a client no longer prevents Tor from
8600 uploading and downloading hidden service descriptors. Fixes
8604 - Allow nameservers with IPv6 address. Resolves bug 2574.
8605 - Accept attempts to include a password authenticator in the
8606 handshake, as supported by SOCKS5. This handles SOCKS clients that
8607 don't know how to omit a password when authenticating. Resolves
8609 - When configuring a large set of nodes in EntryNodes, and there are
8610 enough of them listed as Guard so that we don't need to consider
8611 the non-guard entries, prefer the ones listed with the Guard flag.
8612 - Check for and recover from inconsistency in the microdescriptor
8613 cache. This will make it harder for us to accidentally free a
8614 microdescriptor without removing it from the appropriate data
8615 structures. Fixes issue 3135; issue noted by "wanoskarnet".
8616 - Log SSL state transitions at log level DEBUG, log domain
8617 HANDSHAKE. This can be useful for debugging censorship events.
8618 Implements ticket 3264.
8619 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
8620 implements ticket 3439.
8622 o Minor bugfixes (on 0.2.3.1-alpha):
8623 - Do not free all general-purpose regular descriptors just
8624 because microdescriptor use is enabled. Fixes bug 3113.
8625 - Correctly link libevent_openssl when --enable-static-libevent
8626 is passed to configure. Fixes bug 3118.
8627 - Bridges should not complain during their heartbeat log messages that
8628 they are unlisted in the consensus: that's more or less the point
8629 of being a bridge. Fixes bug 3183.
8630 - Report a SIGNAL event to controllers when acting on a delayed
8631 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
8632 event to the controller if we acted on a SIGNAL NEWNYM command
8633 immediately, and otherwise not report a SIGNAL event for the
8634 command at all. Fixes bug 3349.
8635 - Fix a crash when handling the SIGNAL controller command or
8636 reporting ERR-level status events with bufferevents enabled. Found
8637 by Robert Ransom. Fixes bug 3367.
8638 - Always ship the tor-fw-helper manpage in our release tarballs.
8639 Fixes bug 3389. Reported by Stephen Walker.
8640 - Fix a class of double-mark-for-close bugs when bufferevents
8641 are enabled. Fixes bug 3403.
8642 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
8643 - Add SIGNAL to the list returned by the 'GETINFO events/names'
8644 control-port command. Fixes part of bug 3465.
8645 - Prevent using negative indices during unit test runs when read_all()
8646 fails. Spotted by coverity.
8647 - Fix a rare memory leak when checking the nodelist without it being
8648 present. Found by coverity.
8649 - Only try to download a microdescriptor-flavored consensus from
8650 a directory cache that provides them.
8652 o Minor bugfixes (on 0.2.2.x and earlier):
8653 - Assert that hidden-service-related operations are not performed
8654 using single-hop circuits. Previously, Tor would assert that
8655 client-side streams are not attached to single-hop circuits,
8656 but not that other sensitive operations on the client and service
8657 side are not performed using single-hop circuits. Fixes bug 3332;
8659 - Don't publish a new relay descriptor when we reload our onion key,
8660 unless the onion key has actually changed. Fixes bug 3263 and
8661 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
8662 - Allow GETINFO fingerprint to return a fingerprint even when
8663 we have not yet built a router descriptor. Fixes bug 3577;
8664 bugfix on 0.2.0.1-alpha.
8665 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
8666 on 0.2.2.4-alpha; fixes bug 3427.
8668 o Code simplification and refactoring:
8669 - Use tor_sscanf() in place of scanf() in more places through the
8670 code. This makes us a little more locale-independent, and
8671 should help shut up code-analysis tools that can't tell
8672 a safe sscanf string from a dangerous one.
8673 - Use tt_assert(), not tor_assert(), for checking for test failures.
8674 This makes the unit tests more able to go on in the event that
8676 - Split connection_about_to_close() into separate functions for each
8680 - On Windows, we now define the _WIN32_WINNT macros only if they
8681 are not already defined. This lets the person building Tor decide,
8682 if they want, to require a later version of Windows.
8685 Changes in version 0.2.2.30-rc - 2011-07-07
8686 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
8687 series. It fixes a few smaller bugs, but generally appears stable.
8688 Please test it and let us know whether it is!
8691 - Send a SUCCEEDED stream event to the controller when a reverse
8692 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
8693 discovered by katmagic.
8694 - Always NUL-terminate the sun_path field of a sockaddr_un before
8695 passing it to the kernel. (Not a security issue: kernels are
8696 smart enough to reject bad sockaddr_uns.) Found by Coverity;
8697 CID #428. Bugfix on Tor 0.2.0.3-alpha.
8698 - Don't stack-allocate the list of supplementary GIDs when we're
8699 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
8700 could take up to 256K, which is way too much stack. Found by
8701 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
8702 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
8703 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
8704 fixes part of bug 3465.
8705 - Fix a memory leak when receiving a descriptor for a hidden
8706 service we didn't ask for. Found by Coverity; CID #30. Bugfix
8710 - Update to the July 1 2011 Maxmind GeoLite Country database.
8713 Changes in version 0.2.2.29-beta - 2011-06-20
8714 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
8715 have bridge lines in their torrc but don't want to use them; gets
8716 us closer to having the control socket feature working on Debian;
8717 and fixes a variety of smaller bugs.
8720 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
8721 When we changed the default behavior to "use bridges if any
8722 are listed in the torrc", we surprised users who had bridges
8723 in their torrc files but who didn't actually want to use them.
8724 Partial resolution for bug 3354.
8727 - Don't attach new streams to old rendezvous circuits after SIGNAL
8728 NEWNYM. Previously, we would keep using an existing rendezvous
8729 circuit if it remained open (i.e. if it were kept open by a
8730 long-lived stream, or if a new stream were attached to it before
8731 Tor could notice that it was old and no longer in use). Bugfix on
8732 0.1.1.15-rc; fixes bug 3375.
8735 - Fix a bug when using ControlSocketsGroupWritable with User. The
8736 directory's group would be checked against the current group, not
8737 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
8738 bugfix on 0.2.2.26-beta.
8739 - Make connection_printf_to_buf()'s behavior sane. Its callers
8740 expect it to emit a CRLF iff the format string ends with CRLF;
8741 it actually emitted a CRLF iff (a) the format string ended with
8742 CRLF or (b) the resulting string was over 1023 characters long or
8743 (c) the format string did not end with CRLF *and* the resulting
8744 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
8745 fixes part of bug 3407.
8746 - Make send_control_event_impl()'s behavior sane. Its callers
8747 expect it to always emit a CRLF at the end of the string; it
8748 might have emitted extra control characters as well. Bugfix on
8749 0.1.1.9-alpha; fixes another part of bug 3407.
8750 - Make crypto_rand_int() check the value of its input correctly.
8751 Previously, it accepted values up to UINT_MAX, but could return a
8752 negative number if given a value above INT_MAX+1. Found by George
8753 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
8754 - Avoid a segfault when reading a malformed circuit build state
8755 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
8757 - When asked about a DNS record type we don't support via a
8758 client DNSPort, reply with NOTIMPL rather than an empty
8759 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
8760 - Fix a rare memory leak during stats writing. Found by coverity.
8763 - Update to the June 1 2011 Maxmind GeoLite Country database.
8765 o Code simplifications and refactoring:
8766 - Remove some dead code as indicated by coverity.
8767 - Remove a few dead assignments during router parsing. Found by
8769 - Add some forgotten return value checks during unit tests. Found
8771 - Don't use 1-bit wide signed bit fields. Found by coverity.
8774 Changes in version 0.2.2.28-beta - 2011-06-04
8775 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
8776 fixed a big bug in whether relays stay in the consensus consistently,
8777 we moved closer to handling bridges and hidden services correctly,
8778 and we started the process of better handling the dreaded "my Vidalia
8779 died, and now my Tor demands a password when I try to reconnect to it"
8783 - Don't decide to make a new descriptor when receiving a HUP signal.
8784 This bug has caused a lot of 0.2.2.x relays to disappear from the
8785 consensus periodically. Fixes the most common case of triggering
8786 bug 1810; bugfix on 0.2.2.7-alpha.
8787 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
8788 - Don't try to build descriptors if "ORPort auto" is set and we
8789 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
8791 - Resolve a crash that occurred when setting BridgeRelay to 1 with
8792 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
8793 - Apply circuit timeouts to opened hidden-service-related circuits
8794 based on the correct start time. Previously, we would apply the
8795 circuit build timeout based on time since the circuit's creation;
8796 it was supposed to be applied based on time since the circuit
8797 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
8798 - Use the same circuit timeout for client-side introduction
8799 circuits as for other four-hop circuits, rather than the timeout
8800 for single-hop directory-fetch circuits; the shorter timeout may
8801 have been appropriate with the static circuit build timeout in
8802 0.2.1.x and earlier, but caused many hidden service access attempts
8803 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
8804 on 0.2.2.2-alpha; fixes another part of bug 1297.
8805 - In ticket 2511 we fixed a case where you could use an unconfigured
8806 bridge if you had configured it as a bridge the last time you ran
8807 Tor. Now fix another edge case: if you had configured it as a bridge
8808 but then switched to a different bridge via the controller, you
8809 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
8813 - Add an __OwningControllerProcess configuration option and a
8814 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
8815 that when it exits, Tor will shut down. Implements feature 3049.
8816 - If "UseBridges 1" is set and no bridges are configured, Tor will
8817 now refuse to build any circuits until some bridges are set.
8818 If "UseBridges auto" is set, Tor will use bridges if they are
8819 configured and we are not running as a server, but otherwise will
8820 make circuits as usual. The new default is "auto". Patch by anonym,
8821 so the Tails LiveCD can stop automatically revealing you as a Tor
8825 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
8826 - Remove a trailing asterisk from "exit-policy/default" in the
8827 output of the control port command "GETINFO info/names". Bugfix
8829 - Use a wide type to hold sockets when built for 64-bit Windows builds.
8831 - Warn when the user configures two HiddenServiceDir lines that point
8832 to the same directory. Bugfix on 0.0.6 (the version introducing
8833 HiddenServiceDir); fixes bug 3289.
8834 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
8835 part of bug 2748; bugfix on 0.2.0.10-alpha.
8836 - Log malformed requests for rendezvous descriptors as protocol
8837 warnings, not warnings. Also, use a more informative log message
8838 in case someone sees it at log level warning without prior
8839 info-level messages. Fixes the other part of bug 2748; bugfix
8841 - Clear the table recording the time of the last request for each
8842 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
8843 Previously, we would clear our HS descriptor cache on SIGNAL
8844 NEWNYM, but if we had previously retrieved a descriptor (or tried
8845 to) from every directory responsible for it, we would refuse to
8846 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
8848 - Fix a log message that said "bits" while displaying a value in
8849 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
8851 - When checking for 1024-bit keys, check for 1024 bits, not 128
8852 bytes. This allows Tor to correctly discard keys of length 1017
8853 through 1023. Bugfix on 0.0.9pre5.
8856 - Relays now log the reason for publishing a new relay descriptor,
8857 so we have a better chance of hunting down instances of bug 1810.
8858 Resolves ticket 3252.
8859 - Revise most log messages that refer to nodes by nickname to
8860 instead use the "$key=nickname at address" format. This should be
8861 more useful, especially since nicknames are less and less likely
8862 to be unique. Resolves ticket 3045.
8863 - Log (at info level) when purging pieces of hidden-service-client
8864 state because of SIGNAL NEWNYM.
8867 - Remove undocumented option "-F" from tor-resolve: it hasn't done
8868 anything since 0.2.1.16-rc.
8871 Changes in version 0.2.2.27-beta - 2011-05-18
8872 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
8873 release, and also adds a few more general bugfixes.
8876 - Fix a crash bug when changing bridges in a running Tor process.
8877 Fixes bug 3213; bugfix on 0.2.2.26-beta.
8878 - When the controller configures a new bridge, don't wait 10 to 60
8879 seconds before trying to fetch its descriptor. Bugfix on
8880 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
8883 - Require that onion keys have exponent 65537 in microdescriptors too.
8884 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
8885 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
8886 Changed the limit to 512 characters by removing base64 newlines.
8887 Fixes bug 2752. Fix by Michael Yakubovich.
8888 - When a client starts or stops using bridges, never use a circuit
8889 that was built before the configuration change. This behavior could
8890 put at risk a user who uses bridges to ensure that her traffic
8891 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
8895 Changes in version 0.2.2.26-beta - 2011-05-17
8896 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
8897 also introduces a new "socksport auto" approach that should make it
8898 easier to run multiple Tors on the same system, and does a lot of
8899 cleanup to get us closer to a release candidate.
8901 o Security/privacy fixes:
8902 - Replace all potentially sensitive memory comparison operations
8903 with versions whose runtime does not depend on the data being
8904 compared. This will help resist a class of attacks where an
8905 adversary can use variations in timing information to learn
8906 sensitive data. Fix for one case of bug 3122. (Safe memcmp
8907 implementation by Robert Ransom based partially on code by DJB.)
8908 - When receiving a hidden service descriptor, check that it is for
8909 the hidden service we wanted. Previously, Tor would store any
8910 hidden service descriptors that a directory gave it, whether it
8911 wanted them or not. This wouldn't have let an attacker impersonate
8912 a hidden service, but it did let directories pre-seed a client
8913 with descriptors that it didn't want. Bugfix on 0.0.6.
8914 - On SIGHUP, do not clear out all TrackHostExits mappings, client
8915 DNS cache entries, and virtual address mappings: that's what
8916 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
8919 - The options SocksPort, ControlPort, and so on now all accept a
8920 value "auto" that opens a socket on an OS-selected port. A
8921 new ControlPortWriteToFile option tells Tor to write its
8922 actual control port or ports to a chosen file. If the option
8923 ControlPortFileGroupReadable is set, the file is created as
8924 group-readable. Now users can run two Tor clients on the same
8925 system without needing to manually mess with parameters. Resolves
8926 part of ticket 3076.
8927 - Set SO_REUSEADDR on all sockets, not just listeners. This should
8928 help busy exit nodes avoid running out of useable ports just
8929 because all the ports have been used in the near past. Resolves
8933 - New "GETINFO net/listeners/(type)" controller command to return
8934 a list of addresses and ports that are bound for listeners for a
8935 given connection type. This is useful when the user has configured
8936 "SocksPort auto" and the controller needs to know which port got
8937 chosen. Resolves another part of ticket 3076.
8938 - Add a new ControlSocketsGroupWritable configuration option: when
8939 it is turned on, ControlSockets are group-writeable by the default
8940 group of the current user. Patch by Jérémy Bobbio; implements
8942 - Tor now refuses to create a ControlSocket in a directory that is
8943 world-readable (or group-readable if ControlSocketsGroupWritable
8944 is 0). This is necessary because some operating systems do not
8945 enforce permissions on an AF_UNIX sockets. Permissions on the
8946 directory holding the socket, however, seems to work everywhere.
8947 - Rate-limit a warning about failures to download v2 networkstatus
8948 documents. Resolves part of bug 1352.
8949 - Backport code from 0.2.3.x that allows directory authorities to
8950 clean their microdescriptor caches. Needed to resolve bug 2230.
8951 - When an HTTPS proxy reports "403 Forbidden", we now explain
8952 what it means rather than calling it an unexpected status code.
8953 Closes bug 2503. Patch from Michael Yakubovich.
8954 - Update to the May 1 2011 Maxmind GeoLite Country database.
8957 - Authorities now clean their microdesc cache periodically and when
8958 reading from disk initially, not only when adding new descriptors.
8959 This prevents a bug where we could lose microdescriptors. Bugfix
8960 on 0.2.2.6-alpha. Fixes bug 2230.
8961 - Do not crash when our configuration file becomes unreadable, for
8962 example due to a permissions change, between when we start up
8963 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
8965 - Avoid a bug that would keep us from replacing a microdescriptor
8966 cache on Windows. (We would try to replace the file while still
8967 holding it open. That's fine on Unix, but Windows doesn't let us
8968 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
8969 - Add missing explanations for the authority-related torrc options
8970 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
8971 man page. Resolves issue 2379.
8972 - As an authority, do not upload our own vote or signature set to
8973 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
8974 it would get flagged as a duplicate. Resolves bug 3026.
8975 - Accept hidden service descriptors if we think we might be a hidden
8976 service directory, regardless of what our consensus says. This
8977 helps robustness, since clients and hidden services can sometimes
8978 have a more up-to-date view of the network consensus than we do,
8979 and if they think that the directory authorities list us a HSDir,
8980 we might actually be one. Related to bug 2732; bugfix on
8982 - When a controller changes TrackHostExits, remove mappings for
8983 hosts that should no longer have their exits tracked. Bugfix on
8985 - When a controller changes VirtualAddrNetwork, remove any mappings
8986 for hosts that were automapped to the old network. Bugfix on
8988 - When a controller changes one of the AutomapHosts* options, remove
8989 any mappings for hosts that should no longer be automapped. Bugfix
8991 - Do not reset the bridge descriptor download status every time we
8992 re-parse our configuration or get a configuration change. Fixes
8993 bug 3019; bugfix on 0.2.0.3-alpha.
8995 o Minor bugfixes (code cleanup):
8996 - When loading the microdesc journal, remember its current size.
8997 In 0.2.2, this helps prevent the microdesc journal from growing
8998 without limit on authorities (who are the only ones to use it in
8999 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
9000 Fix posted by "cypherpunks."
9001 - The microdesc journal is supposed to get rebuilt only if it is
9002 at least _half_ the length of the store, not _twice_ the length
9003 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
9004 - Fix a potential null-pointer dereference while computing a
9005 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
9007 - Avoid a possible null-pointer dereference when rebuilding the mdesc
9008 cache without actually having any descriptors to cache. Bugfix on
9009 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
9010 - If we fail to compute the identity digest of a v3 legacy keypair,
9011 warn, and don't use a buffer-full of junk instead. Bugfix on
9012 0.2.1.1-alpha; fixes bug 3106.
9013 - Resolve an untriggerable issue in smartlist_string_num_isin(),
9014 where if the function had ever in the future been used to check
9015 for the presence of a too-large number, it would have given an
9016 incorrect result. (Fortunately, we only used it for 16-bit
9017 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
9018 - Require that introduction point keys and onion handshake keys
9019 have a public exponent of 65537. Starts to fix bug 3207; bugfix
9023 - Caches no longer download and serve v2 networkstatus documents
9024 unless FetchV2Networkstatus flag is set: these documents haven't
9025 haven't been used by clients or relays since 0.2.0.x. Resolves
9029 Changes in version 0.2.3.1-alpha - 2011-05-05
9030 Tor 0.2.3.1-alpha adds some new experimental features, including support
9031 for an improved network IO backend, IOCP networking on Windows,
9032 microdescriptor caching, "fast-start" support for streams, and automatic
9033 home router configuration. There are also numerous internal improvements
9034 to try to make the code easier for developers to work with.
9036 This is the first alpha release in a new series, so expect there to be
9037 bugs. Users who would rather test out a more stable branch should
9038 stay with 0.2.2.x for now.
9041 - Tor can now optionally build with the "bufferevents" buffered IO
9042 backend provided by Libevent 2. To use this feature, make sure you
9043 have the latest possible version of Libevent, and pass the
9044 --enable-bufferevents flag to configure when building Tor from
9045 source. This feature will make our networking code more flexible,
9046 let us stack layers on each other, and let us use more efficient
9047 zero-copy transports where available.
9048 - As an experimental feature, Tor can use IOCP for networking on Windows.
9049 Once this code is tuned and optimized, it promises much better
9050 performance than the select-based backend we've used in the past. To
9051 try this feature, you must build Tor with Libevent 2, configure Tor
9052 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
9053 your torrc. There are known bugs here: only try this if you can help
9054 debug it as it breaks.
9055 - The EntryNodes option can now include country codes like {de} or IP
9056 addresses or network masks. Previously we had disallowed these options
9057 because we didn't have an efficient way to keep the list up to
9058 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
9059 - Exit nodes now accept and queue data on not-yet-connected streams.
9060 Previously, the client wasn't allowed to send data until the stream was
9061 connected, which slowed down all connections. This change will enable
9062 clients to perform a "fast-start" on streams and send data without
9063 having to wait for a confirmation that the stream has opened. (Patch
9064 from Ian Goldberg; implements the server side of Proposal 174.)
9065 - Tor now has initial support for automatic port mapping on the many
9066 home routers that support NAT-PMP or UPnP. (Not yet supported on
9067 Windows). To build the support code, you'll need to have libnatpnp
9068 library and/or the libminiupnpc library, and you'll need to enable the
9069 feature specifically by passing "--enable-upnp" and/or
9070 "--enable-natpnp" to configure. To turn it on, use the new
9071 PortForwarding option.
9072 - Caches now download, cache, and serve multiple "flavors" of the
9073 consensus, including a flavor that describes microdescriptors.
9074 - Caches now download, cache, and serve microdescriptors -- small
9075 summaries of router descriptors that are authenticated by all of the
9076 directory authorities. Once enough caches are running this code,
9077 clients will be able to save significant amounts of directory bandwidth
9078 by downloading microdescriptors instead of router descriptors.
9081 - Make logging resolution configurable with a new LogTimeGranularity
9082 option, and change the default from 1 millisecond to 1 second.
9083 Implements enhancement 1668.
9084 - We log which torrc file we're using on startup. Implements ticket
9086 - Ordinarily, Tor does not count traffic from private addresses (like
9087 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
9088 There is now a new option, CountPrivateBandwidth, to disable this
9089 behavior. Patch from Daniel Cagara.
9090 - New --enable-static-tor configure option for building Tor as
9091 statically as possible. Idea, general hackery and thoughts from
9092 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
9094 - If you set the NumCPUs option to 0, Tor will now try to detect how
9095 many CPUs you have. This is the new default behavior.
9096 - Turn on directory request statistics by default and include them in
9097 extra-info descriptors. Don't break if we have no GeoIP database.
9098 - Relays that set "ConnDirectionStatistics 1" write statistics on the
9099 bidirectional use of connections to disk every 24 hours.
9100 - Add a GeoIP file digest to the extra-info descriptor. Implements
9102 - The NodeFamily option -- which let you declare that you want to
9103 consider nodes to be part of a family whether they list themselves
9104 that way or not -- now allows IP address ranges and country codes.
9105 - Add a new 'Heartbeat' log message type to periodically log a message
9106 describing Tor's status at level Notice. This feature is meant for
9107 operators who log at notice, and want to make sure that their Tor
9108 server is still working. Implementation by George Kadianakis.
9110 o Minor bugfixes (on 0.2.2.25-alpha):
9111 - When loading the microdesc journal, remember its current size.
9112 In 0.2.2, this helps prevent the microdesc journal from growing
9113 without limit on authorities (who are the only ones to use it in
9114 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
9115 Fix posted by "cypherpunks."
9116 - The microdesc journal is supposed to get rebuilt only if it is
9117 at least _half_ the length of the store, not _twice_ the length
9118 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
9119 - If as an authority we fail to compute the identity digest of a v3
9120 legacy keypair, warn, and don't use a buffer-full of junk instead.
9121 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
9122 - Authorities now clean their microdesc cache periodically and when
9123 reading from disk initially, not only when adding new descriptors.
9124 This prevents a bug where we could lose microdescriptors. Bugfix
9127 o Minor features (controller):
9128 - Add a new SIGNAL event to the controller interface so that
9129 controllers can be notified when Tor handles a signal. Resolves
9130 issue 1955. Patch by John Brooks.
9131 - Add a new GETINFO option to get total bytes read and written. Patch
9132 from pipe, revised by atagar. Resolves ticket 2345.
9133 - Implement some GETINFO controller fields to provide information about
9134 the Tor process's pid, euid, username, and resource limits.
9137 - Our build system requires automake 1.6 or later to create the
9138 Makefile.in files. Previously, you could have used 1.4.
9139 This only affects developers and people building Tor from git;
9140 people who build Tor from the source distribution without changing
9141 the Makefile.am files should be fine.
9142 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
9143 so on. This is more robust against some of the failure modes
9144 associated with running the autotools pieces on their own.
9146 o Minor packaging issues:
9147 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
9148 already created. Patch from Andreas Stieger. Fixes bug 2573.
9150 o Code simplifications and refactoring:
9151 - A major revision to our internal node-selecting and listing logic.
9152 Tor already had at least two major ways to look at the question of
9153 "which Tor servers do we know about": a list of router descriptors,
9154 and a list of entries in the current consensus. With
9155 microdescriptors, we're adding a third. Having so many systems
9156 without an abstraction layer over them was hurting the codebase.
9157 Now, we have a new "node_t" abstraction that presents a consistent
9158 interface to a client's view of a Tor node, and holds (nearly) all
9159 of the mutable state formerly in routerinfo_t and routerstatus_t.
9160 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
9161 no longer link against Libevent: they never used it, but
9162 our library structure used to force them to link it.
9165 - Remove some old code to work around even older versions of Tor that
9166 used forked processes to handle DNS requests. Such versions of Tor
9167 are no longer in use as servers.
9169 o Documentation fixes:
9170 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
9171 - Add missing documentation for the authority-related torrc options
9172 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
9176 Changes in version 0.2.2.25-alpha - 2011-04-29
9177 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
9178 robust, routers no longer overreport their bandwidth, Win7 should crash
9179 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
9180 now prevents hidden service-related activity from being linkable. It
9181 provides more information to Vidalia so you can see if your bridge is
9182 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
9183 StrictNodes configuration options to make them more reliable, more
9184 understandable, and more regularly applied. If you use those options,
9185 please see the revised documentation for them in the manual page.
9188 - Relays were publishing grossly inflated bandwidth values because
9189 they were writing their state files wrong--now they write the
9190 correct value. Also, resume reading bandwidth history from the
9191 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
9192 - Improve hidden service robustness: When we find that we have
9193 extended a hidden service's introduction circuit to a relay not
9194 listed as an introduction point in the HS descriptor we currently
9195 have, retry with an introduction point from the current
9196 descriptor. Previously we would just give up. Fixes bugs 1024 and
9197 1930; bugfix on 0.2.0.10-alpha.
9198 - Clients now stop trying to use an exit node associated with a given
9199 destination by TrackHostExits if they fail to reach that exit node.
9200 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
9201 - Fix crash bug on platforms where gmtime and localtime can return
9202 NULL. Windows 7 users were running into this one. Fixes part of bug
9203 2077. Bugfix on all versions of Tor. Found by boboper.
9205 o Security and stability fixes:
9206 - Don't double-free a parsable, but invalid, microdescriptor, even if
9207 it is followed in the blob we're parsing by an unparsable
9208 microdescriptor. Fixes an issue reported in a comment on bug 2954.
9209 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
9210 - If the Nickname configuration option isn't given, Tor would pick a
9211 nickname based on the local hostname as the nickname for a relay.
9212 Because nicknames are not very important in today's Tor and the
9213 "Unnamed" nickname has been implemented, this is now problematic
9214 behavior: It leaks information about the hostname without being
9215 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
9216 introduced the Unnamed nickname. Reported by tagnaq.
9217 - Fix an uncommon assertion failure when running with DNSPort under
9218 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
9219 - Avoid linkability based on cached hidden service descriptors: forget
9220 all hidden service descriptors cached as a client when processing a
9221 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
9224 - Export GeoIP information on bridge usage to controllers even if we
9225 have not yet been running for 24 hours. Now Vidalia bridge operators
9226 can get more accurate and immediate feedback about their
9227 contributions to the network.
9229 o Major features and bugfixes (node selection):
9230 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
9231 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
9232 options. Previously, we had been ambiguous in describing what
9233 counted as an "exit" node, and what operations exactly "StrictNodes
9234 0" would permit. This created confusion when people saw nodes built
9235 through unexpected circuits, and made it hard to tell real bugs from
9236 surprises. Now the intended behavior is:
9237 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
9238 a node that delivers user traffic outside the Tor network.
9239 . "Entry", in the context of EntryNodes, means a node used as the
9240 first hop of a multihop circuit. It doesn't include direct
9241 connections to directory servers.
9242 . "ExcludeNodes" applies to all nodes.
9243 . "StrictNodes" changes the behavior of ExcludeNodes only. When
9244 StrictNodes is set, Tor should avoid all nodes listed in
9245 ExcludeNodes, even when it will make user requests fail. When
9246 StrictNodes is *not* set, then Tor should follow ExcludeNodes
9247 whenever it can, except when it must use an excluded node to
9248 perform self-tests, connect to a hidden service, provide a
9249 hidden service, fulfill a .exit request, upload directory
9250 information, or fetch directory information.
9251 Collectively, the changes to implement the behavior fix bug 1090.
9252 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
9253 a node is listed in both, it's treated as excluded.
9254 - ExcludeNodes now applies to directory nodes -- as a preference if
9255 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
9256 Don't exclude all the directory authorities and set StrictNodes to 1
9257 unless you really want your Tor to break.
9258 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
9259 - ExcludeExitNodes now overrides .exit requests.
9260 - We don't use bridges listed in ExcludeNodes.
9261 - When StrictNodes is 1:
9262 . We now apply ExcludeNodes to hidden service introduction points
9263 and to rendezvous points selected by hidden service users. This
9264 can make your hidden service less reliable: use it with caution!
9265 . If we have used ExcludeNodes on ourself, do not try relay
9266 reachability self-tests.
9267 . If we have excluded all the directory authorities, we will not
9268 even try to upload our descriptor if we're a relay.
9269 . Do not honor .exit requests to an excluded node.
9270 - Remove a misfeature that caused us to ignore the Fast/Stable flags
9271 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
9272 - When the set of permitted nodes changes, we now remove any mappings
9273 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
9275 - We never cannibalize a circuit that had excluded nodes on it, even
9276 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
9277 - Revert a change where we would be laxer about attaching streams to
9278 circuits than when building the circuits. This was meant to prevent
9279 a set of bugs where streams were never attachable, but our improved
9280 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
9281 - Keep track of how many times we launch a new circuit to handle a
9282 given stream. Too many launches could indicate an inconsistency
9283 between our "launch a circuit to handle this stream" logic and our
9284 "attach this stream to one of the available circuits" logic.
9285 - Improve log messages related to excluded nodes.
9288 - Fix a spurious warning when moving from a short month to a long
9289 month on relays with month-based BandwidthAccounting. Bugfix on
9290 0.2.2.17-alpha; fixes bug 3020.
9291 - When a client finds that an origin circuit has run out of 16-bit
9292 stream IDs, we now mark it as unusable for new streams. Previously,
9293 we would try to close the entire circuit. Bugfix on 0.0.6.
9294 - Add a forgotten cast that caused a compile warning on OS X 10.6.
9295 Bugfix on 0.2.2.24-alpha.
9296 - Be more careful about reporting the correct error from a failed
9297 connect() system call. Under some circumstances, it was possible to
9298 look at an incorrect value for errno when sending the end reason.
9299 Bugfix on 0.1.0.1-rc.
9300 - Correctly handle an "impossible" overflow cases in connection byte
9301 counting, where we write or read more than 4GB on an edge connection
9302 in a single second. Bugfix on 0.1.2.8-beta.
9303 - Correct the warning displayed when a rendezvous descriptor exceeds
9304 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
9306 - Clients and hidden services now use HSDir-flagged relays for hidden
9307 service descriptor downloads and uploads even if the relays have no
9308 DirPort set and the client has disabled TunnelDirConns. This will
9309 eventually allow us to give the HSDir flag to relays with no
9310 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
9311 - Downgrade "no current certificates known for authority" message from
9312 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
9313 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
9314 2917. Bugfix on 0.1.1.1-alpha.
9315 - Only limit the lengths of single HS descriptors, even when multiple
9316 HS descriptors are published to an HSDir relay in a single POST
9317 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
9318 - Write the current time into the LastWritten line in our state file,
9319 rather than the time from the previous write attempt. Also, stop
9320 trying to use a time of -1 in our log statements. Fixes bug 3039;
9321 bugfix on 0.2.2.14-alpha.
9322 - Be more consistent in our treatment of file system paths. "~" should
9323 get expanded to the user's home directory in the Log config option.
9324 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
9325 feature for the -f and --DataDirectory options.
9328 - Make sure every relay writes a state file at least every 12 hours.
9329 Previously, a relay could go for weeks without writing its state
9330 file, and on a crash could lose its bandwidth history, capacity
9331 estimates, client country statistics, and so on. Addresses bug 3012.
9332 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
9333 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
9334 clients are already deprecated because of security bugs.
9335 - Don't allow v0 hidden service authorities to act as clients.
9336 Required by fix for bug 3000.
9337 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
9338 by fix for bug 3000.
9339 - Ensure that no empty [dirreq-](read|write)-history lines are added
9340 to an extrainfo document. Implements ticket 2497.
9342 o Code simplification and refactoring:
9343 - Remove workaround code to handle directory responses from servers
9344 that had bug 539 (they would send HTTP status 503 responses _and_
9345 send a body too). Since only server versions before
9346 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
9347 keep the workaround in place.
9348 - Remove the old 'fuzzy time' logic. It was supposed to be used for
9349 handling calculations where we have a known amount of clock skew and
9350 an allowed amount of unknown skew. But we only used it in three
9351 places, and we never adjusted the known/unknown skew values. This is
9352 still something we might want to do someday, but if we do, we'll
9353 want to do it differently.
9354 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
9355 None of the cases where we did this before were wrong, but by making
9356 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
9357 - Use GetTempDir to find the proper temporary directory location on
9358 Windows when generating temporary files for the unit tests. Patch by
9362 Changes in version 0.2.2.24-alpha - 2011-04-08
9363 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
9364 prevented Tor clients from effectively using "multihomed" bridges,
9365 that is, bridges that listen on multiple ports or IP addresses so users
9366 can continue to use some of their addresses even if others get blocked.
9369 - Fix a bug where bridge users who configure the non-canonical
9370 address of a bridge automatically switch to its canonical
9371 address. If a bridge listens at more than one address, it should be
9372 able to advertise those addresses independently and any non-blocked
9373 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
9375 - If you configured Tor to use bridge A, and then quit and
9376 configured Tor to use bridge B instead, it would happily continue
9377 to use bridge A if it's still reachable. While this behavior is
9378 a feature if your goal is connectivity, in some scenarios it's a
9379 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
9380 - Directory authorities now use data collected from their own
9381 uptime observations when choosing whether to assign the HSDir flag
9382 to relays, instead of trusting the uptime value the relay reports in
9383 its descriptor. This change helps prevent an attack where a small
9384 set of nodes with frequently-changing identity keys can blackhole
9385 a hidden service. (Only authorities need upgrade; others will be
9386 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
9389 - When we restart our relay, we might get a successful connection
9390 from the outside before we've started our reachability tests,
9391 triggering a warning: "ORPort found reachable, but I have no
9392 routerinfo yet. Failing to inform controller of success." This
9393 bug was harmless unless Tor is running under a controller
9394 like Vidalia, in which case the controller would never get a
9395 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
9397 - Make directory authorities more accurate at recording when
9398 relays that have failed several reachability tests became
9399 unreachable, so we can provide more accuracy at assigning Stable,
9400 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
9401 - Fix an issue that prevented static linking of libevent on
9402 some platforms (notably Linux). Fixes bug 2698; bugfix on
9403 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
9404 the --with-static-libevent configure option).
9405 - We now ask the other side of a stream (the client or the exit)
9406 for more data on that stream when the amount of queued data on
9407 that stream dips low enough. Previously, we wouldn't ask the
9408 other side for more data until either it sent us more data (which
9409 it wasn't supposed to do if it had exhausted its window!) or we
9410 had completely flushed all our queued data. This flow control fix
9411 should improve throughput. Fixes bug 2756; bugfix on the earliest
9412 released versions of Tor (svn commit r152).
9413 - Avoid a double-mark-for-free warning when failing to attach a
9414 transparent proxy connection. (We thought we had fixed this in
9415 0.2.2.23-alpha, but it turns out our fix was checking the wrong
9416 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
9417 bug) and 0.2.2.23-alpha (the incorrect fix).
9418 - When warning about missing zlib development packages during compile,
9419 give the correct package names. Bugfix on 0.2.0.1-alpha.
9422 - Directory authorities now log the source of a rejected POSTed v3
9424 - Make compilation with clang possible when using
9425 --enable-gcc-warnings by removing two warning options that clang
9426 hasn't implemented yet and by fixing a few warnings. Implements
9428 - When expiring circuits, use microsecond timers rather than
9429 one-second timers. This can avoid an unpleasant situation where a
9430 circuit is launched near the end of one second and expired right
9431 near the beginning of the next, and prevent fluctuations in circuit
9433 - Use computed circuit-build timeouts to decide when to launch
9434 parallel introduction circuits for hidden services. (Previously,
9435 we would retry after 15 seconds.)
9436 - Update to the April 1 2011 Maxmind GeoLite Country database.
9439 - Create the /var/run/tor directory on startup on OpenSUSE if it is
9440 not already created. Patch from Andreas Stieger. Fixes bug 2573.
9442 o Documentation changes:
9443 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
9444 - Resolve all doxygen warnings except those for missing documentation.
9446 - Add doxygen documentation for more functions, fields, and types.
9449 Changes in version 0.2.2.23-alpha - 2011-03-08
9450 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
9451 they restart they don't lose their bandwidth capacity estimate. This
9452 release also fixes a diverse set of user-facing bugs, ranging from
9453 relays overrunning their rate limiting to clients falsely warning about
9454 clock skew to bridge descriptor leaks by our bridge directory authority.
9457 - Stop sending a CLOCK_SKEW controller status event whenever
9458 we fetch directory information from a relay that has a wrong clock.
9459 Instead, only inform the controller when it's a trusted authority
9460 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
9461 the rest of bug 1074.
9462 - Fix an assert in parsing router descriptors containing IPv6
9463 addresses. This one took down the directory authorities when
9464 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
9465 - Make the bridge directory authority refuse to answer directory
9466 requests for "all" descriptors. It used to include bridge
9467 descriptors in its answer, which was a major information leak.
9468 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
9469 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
9470 Tor would ignore their RelayBandwidthBurst setting,
9471 potentially using more bandwidth than expected. Bugfix on
9472 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
9473 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
9474 hidserv" in her torrc. The 'hidserv' argument never controlled
9475 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
9478 - Relays now save observed peak bandwidth throughput rates to their
9479 state file (along with total usage, which was already saved)
9480 so that they can determine their correct estimated bandwidth on
9481 restart. Resolves bug 1863, where Tor relays would reset their
9482 estimated bandwidth to 0 after restarting.
9483 - Directory authorities now take changes in router IP address and
9484 ORPort into account when determining router stability. Previously,
9485 if a router changed its IP or ORPort, the authorities would not
9486 treat it as having any downtime for the purposes of stability
9487 calculation, whereas clients would experience downtime since the
9488 change could take a while to propagate to them. Resolves issue 1035.
9489 - Enable Address Space Layout Randomization (ASLR) and Data Execution
9490 Prevention (DEP) by default on Windows to make it harder for
9491 attackers to exploit vulnerabilities. Patch from John Brooks.
9493 o Minor bugfixes (on 0.2.1.x and earlier):
9494 - Fix a rare crash bug that could occur when a client was configured
9495 with a large number of bridges. Fixes bug 2629; bugfix on
9496 0.2.1.2-alpha. Bugfix by trac user "shitlei".
9497 - Avoid a double mark-for-free warning when failing to attach a
9498 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
9500 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
9501 found by "cypherpunks". This bug was introduced before the first
9502 Tor release, in svn commit r110.
9503 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
9504 don't mention them in the manpage. Fixes bug 2450; issue
9505 spotted by keb and G-Lo.
9506 - Fix a bug in bandwidth history state parsing that could have been
9507 triggered if a future version of Tor ever changed the timing
9508 granularity at which bandwidth history is measured. Bugfix on
9510 - When a relay decides that its DNS is too broken for it to serve
9511 as an exit server, it advertised itself as a non-exit, but
9512 continued to act as an exit. This could create accidental
9513 partitioning opportunities for users. Instead, if a relay is
9514 going to advertise reject *:* as its exit policy, it should
9515 really act with exit policy "reject *:*". Fixes bug 2366.
9516 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
9517 - In the special case where you configure a public exit relay as your
9518 bridge, Tor would be willing to use that exit relay as the last
9519 hop in your circuit as well. Now we fail that circuit instead.
9520 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
9521 - Fix a bug with our locking implementation on Windows that couldn't
9522 correctly detect when a file was already locked. Fixes bug 2504,
9523 bugfix on 0.2.1.6-alpha.
9524 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
9525 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
9527 - Set target port in get_interface_address6() correctly. Bugfix
9528 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
9529 - Directory authorities are now more robust to hops back in time
9530 when calculating router stability. Previously, if a run of uptime
9531 or downtime appeared to be negative, the calculation could give
9532 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
9534 - Fix an assert that got triggered when using the TestingTorNetwork
9535 configuration option and then issuing a GETINFO config-text control
9536 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
9538 o Minor bugfixes (on 0.2.2.x):
9539 - Clients should not weight BadExit nodes as Exits in their node
9540 selection. Similarly, directory authorities should not count BadExit
9541 bandwidth as Exit bandwidth when computing bandwidth-weights.
9542 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
9543 - Correctly clear our dir_read/dir_write history when there is an
9544 error parsing any bw history value from the state file. Bugfix on
9546 - Resolve a bug in verifying signatures of directory objects
9547 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
9548 Fixes bug 2409. Found by "piebeer".
9549 - Bridge authorities no longer crash on SIGHUP when they try to
9550 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
9554 - Log less aggressively about circuit timeout changes, and improve
9555 some other circuit timeout messages. Resolves bug 2004.
9556 - Log a little more clearly about the times at which we're no longer
9557 accepting new connections. Resolves bug 2181.
9558 - Reject attempts at the client side to open connections to private
9559 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
9560 a randomly chosen exit node. Attempts to do so are always
9561 ill-defined, generally prevented by exit policies, and usually
9562 in error. This will also help to detect loops in transparent
9563 proxy configurations. You can disable this feature by setting
9564 "ClientRejectInternalAddresses 0" in your torrc.
9565 - Always treat failure to allocate an RSA key as an unrecoverable
9567 - Update to the March 1 2011 Maxmind GeoLite Country database.
9569 o Minor features (log subsystem):
9570 - Add documentation for configuring logging at different severities in
9571 different log domains. We've had this feature since 0.2.1.1-alpha,
9572 but for some reason it never made it into the manpage. Fixes
9574 - Make it simpler to specify "All log domains except for A and B".
9575 Previously you needed to say "[*,~A,~B]". Now you can just say
9577 - Add a "LogMessageDomains 1" option to include the domains of log
9578 messages along with the messages. Without this, there's no way
9579 to use log domains without reading the source or doing a lot
9582 o Packaging changes:
9583 - Stop shipping the Tor specs files and development proposal documents
9584 in the tarball. They are now in a separate git repository at
9585 git://git.torproject.org/torspec.git
9588 Changes in version 0.2.1.30 - 2011-02-23
9589 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
9590 change is a slight tweak to Tor's TLS handshake that makes relays
9591 and bridges that run this new version reachable from Iran again.
9592 We don't expect this tweak will win the arms race long-term, but it
9593 buys us time until we roll out a better solution.
9596 - Stop sending a CLOCK_SKEW controller status event whenever
9597 we fetch directory information from a relay that has a wrong clock.
9598 Instead, only inform the controller when it's a trusted authority
9599 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
9600 the rest of bug 1074.
9601 - Fix a bounds-checking error that could allow an attacker to
9602 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
9604 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
9605 Tor would ignore their RelayBandwidthBurst setting,
9606 potentially using more bandwidth than expected. Bugfix on
9607 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
9608 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
9609 hidserv" in her torrc. The 'hidserv' argument never controlled
9610 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
9613 - Adjust our TLS Diffie-Hellman parameters to match those used by
9615 - Update to the February 1 2011 Maxmind GeoLite Country database.
9618 - Check for and reject overly long directory certificates and
9619 directory tokens before they have a chance to hit any assertions.
9620 Bugfix on 0.2.1.28. Found by "doorss".
9621 - Bring the logic that gathers routerinfos and assesses the
9622 acceptability of circuits into line. This prevents a Tor OP from
9623 getting locked in a cycle of choosing its local OR as an exit for a
9624 path (due to a .exit request) and then rejecting the circuit because
9625 its OR is not listed yet. It also prevents Tor clients from using an
9626 OR running in the same instance as an exit (due to a .exit request)
9627 if the OR does not meet the same requirements expected of an OR
9628 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
9630 o Packaging changes:
9631 - Stop shipping the Tor specs files and development proposal documents
9632 in the tarball. They are now in a separate git repository at
9633 git://git.torproject.org/torspec.git
9634 - Do not include Git version tags as though they are SVN tags when
9635 generating a tarball from inside a repository that has switched
9636 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
9639 Changes in version 0.2.2.22-alpha - 2011-01-25
9640 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
9641 main other change is a slight tweak to Tor's TLS handshake that makes
9642 relays and bridges that run this new version reachable from Iran again.
9643 We don't expect this tweak will win the arms race long-term, but it
9644 will buy us a bit more time until we roll out a better solution.
9647 - Fix a bounds-checking error that could allow an attacker to
9648 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
9650 - Don't assert when changing from bridge to relay or vice versa
9651 via the controller. The assert happened because we didn't properly
9652 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
9653 bug 2433. Reported by bastik.
9656 - Adjust our TLS Diffie-Hellman parameters to match those used by
9658 - Provide a log message stating which geoip file we're parsing
9659 instead of just stating that we're parsing the geoip file.
9660 Implements ticket 2432.
9663 - Check for and reject overly long directory certificates and
9664 directory tokens before they have a chance to hit any assertions.
9665 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
9668 Changes in version 0.2.2.21-alpha - 2011-01-15
9669 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
9670 continues our recent code security audit work. The main fix resolves
9671 a remote heap overflow vulnerability that can allow remote code
9672 execution (CVE-2011-0427). Other fixes address a variety of assert
9673 and crash bugs, most of which we think are hard to exploit remotely.
9675 o Major bugfixes (security), also included in 0.2.1.29:
9676 - Fix a heap overflow bug where an adversary could cause heap
9677 corruption. This bug probably allows remote code execution
9678 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
9680 - Prevent a denial-of-service attack by disallowing any
9681 zlib-compressed data whose compression factor is implausibly
9682 high. Fixes part of bug 2324; reported by "doorss".
9683 - Zero out a few more keys in memory before freeing them. Fixes
9684 bug 2384 and part of bug 2385. These key instances found by
9685 "cypherpunks", based on Andrew Case's report about being able
9686 to find sensitive data in Tor's memory space if you have enough
9687 permissions. Bugfix on 0.0.2pre9.
9689 o Major bugfixes (crashes), also included in 0.2.1.29:
9690 - Prevent calls to Libevent from inside Libevent log handlers.
9691 This had potential to cause a nasty set of crashes, especially
9692 if running Libevent with debug logging enabled, and running
9693 Tor with a controller watching for low-severity log messages.
9694 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
9695 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
9696 underflow errors there too. Fixes the other part of bug 2324.
9697 - Fix a bug where we would assert if we ever had a
9698 cached-descriptors.new file (or another file read directly into
9699 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
9700 on 0.2.1.25. Found by doorss.
9701 - Fix some potential asserts and parsing issues with grossly
9702 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
9705 o Minor bugfixes (other), also included in 0.2.1.29:
9706 - Fix a bug with handling misformed replies to reverse DNS lookup
9707 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
9708 bug reported by doorss.
9709 - Fix compilation on mingw when a pthreads compatibility library
9710 has been installed. (We don't want to use it, so we shouldn't
9711 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
9712 - Fix a bug where we would declare that we had run out of virtual
9713 addresses when the address space was only half-exhausted. Bugfix
9715 - Correctly handle the case where AutomapHostsOnResolve is set but
9716 no virtual addresses are available. Fixes bug 2328; bugfix on
9717 0.1.2.1-alpha. Bug found by doorss.
9718 - Correctly handle wrapping around when we run out of virtual
9719 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
9721 o Minor features, also included in 0.2.1.29:
9722 - Update to the January 1 2011 Maxmind GeoLite Country database.
9723 - Introduce output size checks on all of our decryption functions.
9725 o Build changes, also included in 0.2.1.29:
9726 - Tor does not build packages correctly with Automake 1.6 and earlier;
9727 added a check to Makefile.am to make sure that we're building with
9728 Automake 1.7 or later.
9729 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
9730 because we built it with a too-old version of automake. Thus that
9731 release broke ./configure --enable-openbsd-malloc, which is popular
9732 among really fast exit relays on Linux.
9734 o Major bugfixes, new in 0.2.2.21-alpha:
9735 - Prevent crash/heap corruption when the cbtnummodes consensus
9736 parameter is set to 0 or large values. Fixes bug 2317; bugfix
9739 o Major features, new in 0.2.2.21-alpha:
9740 - Introduce minimum/maximum values that clients will believe
9741 from the consensus. Now we'll have a better chance to avoid crashes
9742 or worse when a consensus param has a weird value.
9744 o Minor features, new in 0.2.2.21-alpha:
9745 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
9746 used on bridges, and it makes bridge scanning somewhat easier.
9747 - If writing the state file to disk fails, wait up to an hour before
9748 retrying again, rather than trying again each second. Fixes bug
9749 2346; bugfix on Tor 0.1.1.3-alpha.
9750 - Make Libevent log messages get delivered to controllers later,
9751 and not from inside the Libevent log handler. This prevents unsafe
9752 reentrant Libevent calls while still letting the log messages
9754 - Detect platforms that brokenly use a signed size_t, and refuse to
9755 build there. Found and analyzed by doorss and rransom.
9756 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
9759 o Minor bugfixes, new in 0.2.2.21-alpha:
9760 - Handle SOCKS messages longer than 128 bytes long correctly, rather
9761 than waiting forever for them to finish. Fixes bug 2330; bugfix
9762 on 0.2.0.16-alpha. Found by doorss.
9763 - Add assertions to check for overflow in arguments to
9764 base32_encode() and base32_decode(); fix a signed-unsigned
9765 comparison there too. These bugs are not actually reachable in Tor,
9766 but it's good to prevent future errors too. Found by doorss.
9767 - Correctly detect failures to create DNS requests when using Libevent
9768 versions before v2. (Before Libevent 2, we used our own evdns
9769 implementation. Its return values for Libevent's evdns_resolve_*()
9770 functions are not consistent with those from Libevent.) Fixes bug
9771 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
9773 o Documentation, new in 0.2.2.21-alpha:
9774 - Document the default socks host and port (127.0.0.1:9050) for
9778 Changes in version 0.2.1.29 - 2011-01-15
9779 Tor 0.2.1.29 continues our recent code security audit work. The main
9780 fix resolves a remote heap overflow vulnerability that can allow remote
9781 code execution. Other fixes address a variety of assert and crash bugs,
9782 most of which we think are hard to exploit remotely.
9784 o Major bugfixes (security):
9785 - Fix a heap overflow bug where an adversary could cause heap
9786 corruption. This bug probably allows remote code execution
9787 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
9789 - Prevent a denial-of-service attack by disallowing any
9790 zlib-compressed data whose compression factor is implausibly
9791 high. Fixes part of bug 2324; reported by "doorss".
9792 - Zero out a few more keys in memory before freeing them. Fixes
9793 bug 2384 and part of bug 2385. These key instances found by
9794 "cypherpunks", based on Andrew Case's report about being able
9795 to find sensitive data in Tor's memory space if you have enough
9796 permissions. Bugfix on 0.0.2pre9.
9798 o Major bugfixes (crashes):
9799 - Prevent calls to Libevent from inside Libevent log handlers.
9800 This had potential to cause a nasty set of crashes, especially
9801 if running Libevent with debug logging enabled, and running
9802 Tor with a controller watching for low-severity log messages.
9803 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
9804 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
9805 underflow errors there too. Fixes the other part of bug 2324.
9806 - Fix a bug where we would assert if we ever had a
9807 cached-descriptors.new file (or another file read directly into
9808 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
9809 on 0.2.1.25. Found by doorss.
9810 - Fix some potential asserts and parsing issues with grossly
9811 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
9814 o Minor bugfixes (other):
9815 - Fix a bug with handling misformed replies to reverse DNS lookup
9816 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
9817 bug reported by doorss.
9818 - Fix compilation on mingw when a pthreads compatibility library
9819 has been installed. (We don't want to use it, so we shouldn't
9820 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
9821 - Fix a bug where we would declare that we had run out of virtual
9822 addresses when the address space was only half-exhausted. Bugfix
9824 - Correctly handle the case where AutomapHostsOnResolve is set but
9825 no virtual addresses are available. Fixes bug 2328; bugfix on
9826 0.1.2.1-alpha. Bug found by doorss.
9827 - Correctly handle wrapping around to when we run out of virtual
9828 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
9829 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
9830 because we built it with a too-old version of automake. Thus that
9831 release broke ./configure --enable-openbsd-malloc, which is popular
9832 among really fast exit relays on Linux.
9835 - Update to the January 1 2011 Maxmind GeoLite Country database.
9836 - Introduce output size checks on all of our decryption functions.
9839 - Tor does not build packages correctly with Automake 1.6 and earlier;
9840 added a check to Makefile.am to make sure that we're building with
9841 Automake 1.7 or later.
9844 Changes in version 0.2.2.20-alpha - 2010-12-17
9845 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
9846 exploitable bugs. We also fix a variety of other significant bugs,
9847 change the IP address for one of our directory authorities, and update
9848 the minimum version that Tor relays must run to join the network.
9851 - Fix a remotely exploitable bug that could be used to crash instances
9852 of Tor remotely by overflowing on the heap. Remote-code execution
9853 hasn't been confirmed, but can't be ruled out. Everyone should
9854 upgrade. Bugfix on the 0.1.1 series and later.
9855 - Fix a bug that could break accounting on 64-bit systems with large
9856 time_t values, making them hibernate for impossibly long intervals.
9857 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
9858 - Fix a logic error in directory_fetches_from_authorities() that
9859 would cause all _non_-exits refusing single-hop-like circuits
9860 to fetch from authorities, when we wanted to have _exits_ fetch
9861 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
9863 - Fix a stream fairness bug that would cause newer streams on a given
9864 circuit to get preference when reading bytes from the origin or
9865 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
9866 introduced before the first Tor release, in svn revision r152.
9868 o Directory authority changes:
9869 - Change IP address and ports for gabelmoo (v3 directory authority).
9872 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
9873 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
9874 - Fix an off-by-one error in calculating some controller command
9875 argument lengths. Fortunately, this mistake is harmless since
9876 the controller code does redundant NUL termination too. Found by
9877 boboper. Bugfix on 0.1.1.1-alpha.
9878 - Do not dereference NULL if a bridge fails to build its
9879 extra-info descriptor. Found by an anonymous commenter on
9880 Trac. Bugfix on 0.2.2.19-alpha.
9883 - Update to the December 1 2010 Maxmind GeoLite Country database.
9884 - Directory authorities now reject relays running any versions of
9885 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
9886 known bugs that keep RELAY_EARLY cells from working on rendezvous
9887 circuits. Followup to fix for bug 2081.
9888 - Directory authorities now reject relays running any version of Tor
9889 older than 0.2.0.26-rc. That version is the earliest that fetches
9890 current directory information correctly. Fixes bug 2156.
9891 - Report only the top 10 ports in exit-port stats in order not to
9892 exceed the maximum extra-info descriptor length of 50 KB. Implements
9896 Changes in version 0.2.1.28 - 2010-12-17
9897 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
9898 exploitable bugs. We also took this opportunity to change the IP address
9899 for one of our directory authorities, and to update the geoip database
9903 - Fix a remotely exploitable bug that could be used to crash instances
9904 of Tor remotely by overflowing on the heap. Remote-code execution
9905 hasn't been confirmed, but can't be ruled out. Everyone should
9906 upgrade. Bugfix on the 0.1.1 series and later.
9908 o Directory authority changes:
9909 - Change IP address and ports for gabelmoo (v3 directory authority).
9912 - Update to the December 1 2010 Maxmind GeoLite Country database.
9915 Changes in version 0.2.1.27 - 2010-11-23
9916 Yet another OpenSSL security patch broke its compatibility with Tor:
9917 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
9918 also took this opportunity to fix several crash bugs, integrate a new
9919 directory authority, and update the bundled GeoIP database.
9922 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
9923 No longer set the tlsext_host_name extension on server SSL objects;
9924 but continue to set it on client SSL objects. Our goal in setting
9925 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
9926 bugfix on 0.2.1.1-alpha.
9927 - Do not log messages to the controller while shrinking buffer
9928 freelists. Doing so would sometimes make the controller connection
9929 try to allocate a buffer chunk, which would mess up the internals
9930 of the freelist and cause an assertion failure. Fixes bug 1125;
9931 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
9932 - Learn our external IP address when we're a relay or bridge, even if
9933 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
9934 where we introduced bridge relays that don't need to publish to
9935 be useful. Fixes bug 2050.
9936 - Do even more to reject (and not just ignore) annotations on
9937 router descriptors received anywhere but from the cache. Previously
9938 we would ignore such annotations at first, but cache them to disk
9939 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
9940 - When you're using bridges and your network goes away and your
9941 bridges get marked as down, recover when you attempt a new socks
9942 connection (if the network is back), rather than waiting up to an
9943 hour to try fetching new descriptors for your bridges. Bugfix on
9944 0.2.0.3-alpha; fixes bug 1981.
9947 - Move to the November 2010 Maxmind GeoLite country db (rather
9948 than the June 2009 ip-to-country GeoIP db) for our statistics that
9949 count how many users relays are seeing from each country. Now we'll
9950 have more accurate data, especially for many African countries.
9952 o New directory authorities:
9953 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
9957 - Fix an assertion failure that could occur in directory caches or
9958 bridge users when using a very short voting interval on a testing
9959 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
9961 - Enforce multiplicity rules when parsing annotations. Bugfix on
9962 0.2.0.8-alpha. Found by piebeer.
9963 - Allow handshaking OR connections to take a full KeepalivePeriod
9964 seconds to handshake. Previously, we would close them after
9965 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
9966 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
9968 - When building with --enable-gcc-warnings on OpenBSD, disable
9969 warnings in system headers. This makes --enable-gcc-warnings
9970 pass on OpenBSD 4.8.
9973 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
9974 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
9975 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
9976 Servers can start sending this code when enough clients recognize
9977 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
9978 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
9979 Patch from mingw-san.
9982 - Remove the old debian/ directory from the main Tor distribution.
9983 The official Tor-for-debian git repository lives at the URL
9984 https://git.torproject.org/debian/tor.git
9985 - Stop shipping the old doc/website/ directory in the tarball. We
9986 changed the website format in late 2010, and what we shipped in
9987 0.2.1.26 really wasn't that useful anyway.
9990 Changes in version 0.2.2.19-alpha - 2010-11-22
9991 Yet another OpenSSL security patch broke its compatibility with Tor:
9992 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
9995 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
9996 No longer set the tlsext_host_name extension on server SSL objects;
9997 but continue to set it on client SSL objects. Our goal in setting
9998 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
9999 bugfix on 0.2.1.1-alpha.
10002 - Try harder not to exceed the maximum length of 50 KB when writing
10003 statistics to extra-info descriptors. This bug was triggered by very
10004 fast relays reporting exit-port, entry, and dirreq statistics.
10005 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
10006 - Publish a router descriptor even if generating an extra-info
10007 descriptor fails. Previously we would not publish a router
10008 descriptor without an extra-info descriptor; this can cause fast
10009 exit relays collecting exit-port statistics to drop from the
10010 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
10013 Changes in version 0.2.2.18-alpha - 2010-11-16
10014 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
10015 us lately, makes unpublished bridge relays able to detect their IP
10016 address, and fixes a wide variety of other bugs to get us much closer
10017 to a stable release.
10020 - Do even more to reject (and not just ignore) annotations on
10021 router descriptors received anywhere but from the cache. Previously
10022 we would ignore such annotations at first, but cache them to disk
10023 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
10024 - Do not log messages to the controller while shrinking buffer
10025 freelists. Doing so would sometimes make the controller connection
10026 try to allocate a buffer chunk, which would mess up the internals
10027 of the freelist and cause an assertion failure. Fixes bug 1125;
10028 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
10029 - Learn our external IP address when we're a relay or bridge, even if
10030 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
10031 where we introduced bridge relays that don't need to publish to
10032 be useful. Fixes bug 2050.
10033 - Maintain separate TLS contexts and certificates for incoming and
10034 outgoing connections in bridge relays. Previously we would use the
10035 same TLS contexts and certs for incoming and outgoing connections.
10036 Bugfix on 0.2.0.3-alpha; addresses bug 988.
10037 - Maintain separate identity keys for incoming and outgoing TLS
10038 contexts in bridge relays. Previously we would use the same
10039 identity keys for incoming and outgoing TLS contexts. Bugfix on
10040 0.2.0.3-alpha; addresses the other half of bug 988.
10041 - Avoid an assertion failure when we as an authority receive a
10042 duplicate upload of a router descriptor that we already have,
10043 but which we previously considered an obsolete descriptor.
10044 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
10045 - Avoid a crash bug triggered by looking at a dangling pointer while
10046 setting the network status consensus. Found by Robert Ransom.
10047 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
10048 - Fix a logic error where servers that _didn't_ act as exits would
10049 try to keep their server lists more aggressively up to date than
10050 exits, when it was supposed to be the other way around. Bugfix
10053 o Minor bugfixes (on Tor 0.2.1.x and earlier):
10054 - When we're trying to guess whether we know our IP address as
10055 a relay, we would log various ways that we failed to guess
10056 our address, but never log that we ended up guessing it
10057 successfully. Now add a log line to help confused and anxious
10058 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
10059 - Bring the logic that gathers routerinfos and assesses the
10060 acceptability of circuits into line. This prevents a Tor OP from
10061 getting locked in a cycle of choosing its local OR as an exit for a
10062 path (due to a .exit request) and then rejecting the circuit because
10063 its OR is not listed yet. It also prevents Tor clients from using an
10064 OR running in the same instance as an exit (due to a .exit request)
10065 if the OR does not meet the same requirements expected of an OR
10066 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
10067 - Correctly describe errors that occur when generating a TLS object.
10068 Previously we would attribute them to a failure while generating a
10069 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
10071 - Enforce multiplicity rules when parsing annotations. Bugfix on
10072 0.2.0.8-alpha. Found by piebeer.
10073 - Fix warnings that newer versions of autoconf produced during
10074 ./autogen.sh. These warnings appear to be harmless in our case,
10075 but they were extremely verbose. Fixes bug 2020.
10077 o Minor bugfixes (on Tor 0.2.2.x):
10078 - Enable protection of small arrays whenever we build with gcc
10079 hardening features, not only when also building with warnings
10080 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
10083 - Make hidden services work better in private Tor networks by not
10084 requiring any uptime to join the hidden service descriptor
10085 DHT. Implements ticket 2088.
10086 - Rate-limit the "your application is giving Tor only an IP address"
10087 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
10088 - When AllowSingleHopExits is set, print a warning to explain to the
10089 relay operator why most clients are avoiding her relay.
10090 - Update to the November 1 2010 Maxmind GeoLite Country database.
10092 o Code simplifications and refactoring:
10093 - When we fixed bug 1038 we had to put in a restriction not to send
10094 RELAY_EARLY cells on rend circuits. This was necessary as long
10095 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
10096 active. Now remove this obsolete check. Resolves bug 2081.
10097 - Some options used different conventions for uppercasing of acronyms
10098 when comparing manpage and source. Fix those in favor of the
10099 manpage, as it makes sense to capitalize acronyms.
10100 - Remove the torrc.complete file. It hasn't been kept up to date
10101 and users will have better luck checking out the manpage.
10102 - Remove the obsolete "NoPublish" option; it has been flagged
10103 as obsolete and has produced a warning since 0.1.1.18-rc.
10104 - Remove everything related to building the expert bundle for OS X.
10105 It has confused many users, doesn't work right on OS X 10.6,
10106 and is hard to get rid of once installed. Resolves bug 1274.
10109 Changes in version 0.2.2.17-alpha - 2010-09-30
10110 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
10111 to use one-hop circuits (which can put the exit relays at higher risk,
10112 plus unbalance the network); fixes a big bug in bandwidth accounting
10113 for relays that want to limit their monthly bandwidth use; fixes a
10114 big pile of bugs in how clients tolerate temporary network failure;
10115 and makes our adaptive circuit build timeout feature (which improves
10116 client performance if your network is fast while not breaking things
10117 if your network is slow) better handle bad networks.
10120 - Exit relays now try harder to block exit attempts from unknown
10121 relays, to make it harder for people to use them as one-hop proxies
10122 a la tortunnel. Controlled by the refuseunknownexits consensus
10123 parameter (currently enabled), or you can override it on your
10124 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
10126 o Major bugfixes (0.2.1.x and earlier):
10127 - Fix a bug in bandwidth accounting that could make us use twice
10128 the intended bandwidth when our interval start changes due to
10129 daylight saving time. Now we tolerate skew in stored vs computed
10130 interval starts: if the start of the period changes by no more than
10131 50% of the period's duration, we remember bytes that we transferred
10132 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
10133 - Always search the Windows system directory for system DLLs, and
10134 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
10135 - When you're using bridges and your network goes away and your
10136 bridges get marked as down, recover when you attempt a new socks
10137 connection (if the network is back), rather than waiting up to an
10138 hour to try fetching new descriptors for your bridges. Bugfix on
10139 0.2.0.3-alpha; fixes bug 1981.
10141 o Major bugfixes (on 0.2.2.x):
10142 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
10144 - Fix a segfault that could happen when operating a bridge relay with
10145 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
10146 - The consensus bandwidth-weights (used by clients to choose fast
10147 relays) entered an unexpected edge case in September where
10148 Exits were much scarcer than Guards, resulting in bad weight
10149 recommendations. Now we compute them using new constraints that
10150 should succeed in all cases. Also alter directory authorities to
10151 not include the bandwidth-weights line if they fail to produce
10152 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
10153 - When weighting bridges during path selection, we used to trust
10154 the bandwidths they provided in their descriptor, only capping them
10155 at 10MB/s. This turned out to be problematic for two reasons:
10156 Bridges could claim to handle a lot more traffic then they
10157 actually would, thus making more clients pick them and have a
10158 pretty effective DoS attack. The other issue is that new bridges
10159 that might not have a good estimate for their bw capacity yet
10160 would not get used at all unless no other bridges are available
10161 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
10163 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
10164 - Ignore cannibalized circuits when recording circuit build times.
10165 This should provide for a minor performance improvement for hidden
10166 service users using 0.2.2.14-alpha, and should remove two spurious
10167 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
10168 - Simplify the logic that causes us to decide if the network is
10169 unavailable for purposes of recording circuit build times. If we
10170 receive no cells whatsoever for the entire duration of a circuit's
10171 full measured lifetime, the network is probably down. Also ignore
10172 one-hop directory fetching circuit timeouts when calculating our
10173 circuit build times. These changes should hopefully reduce the
10174 cases where we see ridiculous circuit build timeouts for people
10175 with spotty wireless connections. Fixes part of bug 1772; bugfix
10177 - Prevent the circuit build timeout from becoming larger than
10178 the maximum build time we have ever seen. Also, prevent the time
10179 period for measurement circuits from becoming larger than twice that
10180 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
10183 - When we run out of directory information such that we can't build
10184 circuits, but then get enough that we can build circuits, log when
10185 we actually construct a circuit, so the user has a better chance of
10186 knowing what's going on. Fixes bug 1362.
10187 - Be more generous with how much bandwidth we'd use up (with
10188 accounting enabled) before entering "soft hibernation". Previously,
10189 we'd refuse new connections and circuits once we'd used up 95% of
10190 our allotment. Now, we use up 95% of our allotment, AND make sure
10191 that we have no more than 500MB (or 3 hours of expected traffic,
10192 whichever is lower) remaining before we enter soft hibernation.
10193 - If we've configured EntryNodes and our network goes away and/or all
10194 our entrynodes get marked down, optimistically retry them all when
10195 a new socks application request appears. Fixes bug 1882.
10196 - Add some more defensive programming for architectures that can't
10197 handle unaligned integer accesses. We don't know of any actual bugs
10198 right now, but that's the best time to fix them. Fixes bug 1943.
10199 - Support line continuations in the torrc config file. If a line
10200 ends with a single backslash character, the newline is ignored, and
10201 the configuration value is treated as continuing on the next line.
10204 o Minor bugfixes (on 0.2.1.x and earlier):
10205 - For bandwidth accounting, calculate our expected bandwidth rate
10206 based on the time during which we were active and not in
10207 soft-hibernation during the last interval. Previously, we were
10208 also considering the time spent in soft-hibernation. If this
10209 was a long time, we would wind up underestimating our bandwidth
10210 by a lot, and skewing our wakeup time towards the start of the
10211 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
10213 o Minor bugfixes (on 0.2.2.x):
10214 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
10215 which were disabled by the circuit build timeout changes in
10216 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
10217 - Make sure we don't warn about missing bandwidth weights when
10218 choosing bridges or other relays not in the consensus. Bugfix on
10219 0.2.2.10-alpha; fixes bug 1805.
10220 - In our logs, do not double-report signatures from unrecognized
10221 authorities both as "from unknown authority" and "not
10222 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
10225 Changes in version 0.2.2.16-alpha - 2010-09-17
10226 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
10227 evident at exit relays), and also continues to resolve all the little
10228 bugs that have been filling up trac lately.
10230 o Major bugfixes (stream-level fairness):
10231 - When receiving a circuit-level SENDME for a blocked circuit, try
10232 to package cells fairly from all the streams that had previously
10233 been blocked on that circuit. Previously, we had started with the
10234 oldest stream, and allowed each stream to potentially exhaust
10235 the circuit's package window. This gave older streams on any
10236 given circuit priority over newer ones. Fixes bug 1937. Detected
10237 originally by Camilo Viecco. This bug was introduced before the
10238 first Tor release, in svn commit r152: it is the new winner of
10239 the longest-lived bug prize.
10240 - When the exit relay got a circuit-level sendme cell, it started
10241 reading on the exit streams, even if had 500 cells queued in the
10242 circuit queue already, so the circuit queue just grew and grew in
10243 some cases. We fix this by not re-enabling reading on receipt of a
10244 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
10245 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
10247 - Newly created streams were allowed to read cells onto circuits,
10248 even if the circuit's cell queue was blocked and waiting to drain.
10249 This created potential unfairness, as older streams would be
10250 blocked, but newer streams would gladly fill the queue completely.
10251 We add code to detect this situation and prevent any stream from
10252 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
10256 - Update to the September 1 2010 Maxmind GeoLite Country database.
10257 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
10258 not. This would lead to a cookie that is still not group readable.
10259 Closes bug 1843. Suggested by katmagic.
10260 - When logging a rate-limited warning, we now mention how many messages
10261 got suppressed since the last warning.
10262 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
10263 do individual connection-level rate limiting of clients. The torrc
10264 config options with the same names trump the consensus params, if
10265 both are present. Replaces the old "bwconnrate" and "bwconnburst"
10266 consensus params which were broken from 0.2.2.7-alpha through
10267 0.2.2.14-alpha. Closes bug 1947.
10268 - When a router changes IP address or port, authorities now launch
10269 a new reachability test for it. Implements ticket 1899.
10270 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
10271 2 no signature, 4 required" messages about consensus signatures
10272 easier to read, and make sure they get logged at the same severity
10273 as the messages explaining which keys are which. Fixes bug 1290.
10274 - Don't warn when we have a consensus that we can't verify because
10275 of missing certificates, unless those certificates are ones
10276 that we have been trying and failing to download. Fixes bug 1145.
10277 - If you configure your bridge with a known identity fingerprint,
10278 and the bridge authority is unreachable (as it is in at least
10279 one country now), fall back to directly requesting the descriptor
10280 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
10282 - When building with --enable-gcc-warnings on OpenBSD, disable
10283 warnings in system headers. This makes --enable-gcc-warnings
10284 pass on OpenBSD 4.8.
10286 o Minor bugfixes (on 0.2.1.x and earlier):
10287 - Authorities will now attempt to download consensuses if their
10288 own efforts to make a live consensus have failed. This change
10289 means authorities that restart will fetch a valid consensus, and
10290 it means authorities that didn't agree with the current consensus
10291 will still fetch and serve it if it has enough signatures. Bugfix
10292 on 0.2.0.9-alpha; fixes bug 1300.
10293 - Ensure DNS requests launched by "RESOLVE" commands from the
10294 controller respect the __LeaveStreamsUnattached setconf options. The
10295 same goes for requests launched via DNSPort or transparent
10296 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
10297 - Allow handshaking OR connections to take a full KeepalivePeriod
10298 seconds to handshake. Previously, we would close them after
10299 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
10300 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
10302 - Rate-limit "Failed to hand off onionskin" warnings.
10303 - Never relay a cell for a circuit we have already destroyed.
10304 Between marking a circuit as closeable and finally closing it,
10305 it may have been possible for a few queued cells to get relayed,
10306 even though they would have been immediately dropped by the next
10307 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
10308 - Never queue a cell for a circuit that's already been marked
10310 - Never vote for a server as "Running" if we have a descriptor for
10311 it claiming to be hibernating, and that descriptor was published
10312 more recently than our last contact with the server. Bugfix on
10313 0.2.0.3-alpha; fixes bug 911.
10314 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
10317 o Minor bugfixes (on 0.2.2.x):
10318 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
10319 down if a directory fetch fails and you've configured either
10320 bridges or EntryNodes. The intent was to mark the relay as down
10321 _unless_ you're using bridges or EntryNodes, since if you are
10322 then you could quickly run out of entry points.
10323 - Fix the Windows directory-listing code. A bug introduced in
10324 0.2.2.14-alpha could make Windows directory servers forget to load
10325 some of their cached v2 networkstatus files.
10326 - Really allow clients to use relays as bridges. Fixes bug 1776;
10327 bugfix on 0.2.2.15-alpha.
10328 - Demote a warn to info that happens when the CellStatistics option
10329 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
10330 Reported by Moritz Bartl.
10331 - On Windows, build correctly either with or without Unicode support.
10332 This is necessary so that Tor can support fringe platforms like
10333 Windows 98 (which has no Unicode), or Windows CE (which has no
10334 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
10337 - Add a unit test for cross-platform directory-listing code.
10340 Changes in version 0.2.2.15-alpha - 2010-08-18
10341 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
10342 fixes a variety of other bugs that were preventing performance
10343 experiments from moving forward, fixes several bothersome memory leaks,
10344 and generally closes a lot of smaller bugs that have been filling up
10348 - Stop assigning the HSDir flag to relays that disable their
10349 DirPort (and thus will refuse to answer directory requests). This
10350 fix should dramatically improve the reachability of hidden services:
10351 hidden services and hidden service clients pick six HSDir relays
10352 to store and retrieve the hidden service descriptor, and currently
10353 about half of the HSDir relays will refuse to work. Bugfix on
10354 0.2.0.10-alpha; fixes part of bug 1693.
10355 - The PerConnBWRate and Burst config options, along with the
10356 bwconnrate and bwconnburst consensus params, initialized each conn's
10357 token bucket values only when the connection is established. Now we
10358 update them if the config options change, and update them every time
10359 we get a new consensus. Otherwise we can encounter an ugly edge
10360 case where we initialize an OR conn to client-level bandwidth,
10361 but then later the relay joins the consensus and we leave it
10362 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
10363 - Fix a regression that caused Tor to rebind its ports if it receives
10364 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
10367 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
10368 should give us approximately 40-50% more Guard-flagged nodes,
10369 improving the anonymity the Tor network can provide and also
10370 decreasing the dropoff in throughput that relays experience when
10371 they first get the Guard flag.
10372 - Allow enabling or disabling the *Statistics config options while
10376 - Update to the August 1 2010 Maxmind GeoLite Country database.
10377 - Have the controller interface give a more useful message than
10378 "Internal Error" in response to failed GETINFO requests.
10379 - Warn when the same option is provided more than once in a torrc
10380 file, on the command line, or in a single SETCONF statement, and
10381 the option is one that only accepts a single line. Closes bug 1384.
10382 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
10383 Patch from mingw-san.
10384 - Add support for the country code "{??}" in torrc options like
10385 ExcludeNodes, to indicate all routers of unknown country. Closes
10387 - Relays report the number of bytes spent on answering directory
10388 requests in extra-info descriptors similar to {read,write}-history.
10389 Implements enhancement 1790.
10391 o Minor bugfixes (on 0.2.1.x and earlier):
10392 - Complain if PublishServerDescriptor is given multiple arguments that
10393 include 0 or 1. This configuration will be rejected in the future.
10394 Bugfix on 0.2.0.1-alpha; closes bug 1107.
10395 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
10396 Bugfix on 0.2.0.13-alpha; closes bug 928.
10397 - Change "Application request when we're believed to be offline."
10398 notice to "Application request when we haven't used client
10399 functionality lately.", to clarify that it's not an error. Bugfix
10400 on 0.0.9.3; fixes bug 1222.
10401 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
10402 would return "551 Internal error" rather than "552 Unrecognized key
10403 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
10404 - Users can't configure a regular relay to be their bridge. It didn't
10405 work because when Tor fetched the bridge descriptor, it found
10406 that it already had it, and didn't realize that the purpose of the
10407 descriptor had changed. Now we replace routers with a purpose other
10408 than bridge with bridge descriptors when fetching them. Bugfix on
10409 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
10410 refetch the descriptor with router purpose 'general', disabling
10412 - Fix a rare bug in rend_fn unit tests: we would fail a test when
10413 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
10414 on 0.2.0.10-alpha; fixes bug 1808.
10415 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
10416 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
10417 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
10418 Servers can start sending this code when enough clients recognize
10419 it. Also update the spec to reflect this new reason. Bugfix on
10420 0.1.0.1-rc; fixes part of bug 1793.
10421 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
10422 when we switch from being a public relay to a bridge. Otherwise
10423 there will still be clients that see the relay in their consensus,
10424 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
10426 - Instead of giving an assertion failure on an internal mismatch
10427 on estimated freelist size, just log a BUG warning and try later.
10428 Mitigates but does not fix bug 1125.
10429 - Fix an assertion failure that could occur in caches or bridge users
10430 when using a very short voting interval on a testing network.
10431 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
10433 o Minor bugfixes (on 0.2.2.x):
10434 - Alter directory authorities to always consider Exit-flagged nodes
10435 as potential Guard nodes in their votes. The actual decision to
10436 use Exits as Guards is done in the consensus bandwidth weights.
10437 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
10438 - When the controller is reporting the purpose of circuits that
10439 didn't finish building before the circuit build timeout, it was
10440 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
10441 - Our libevent version parsing code couldn't handle versions like
10442 1.4.14b-stable and incorrectly warned the user about using an
10443 old and broken version of libevent. Treat 1.4.14b-stable like
10444 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
10446 - Don't use substitution references like $(VAR:MOD) when
10447 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
10448 '$(:x)' to 'x' rather than the empty string. This bites us in
10449 doc/ when configured with --disable-asciidoc. Bugfix on
10450 0.2.2.9-alpha; fixes bug 1773.
10451 - Remove a spurious hidden service server-side log notice about
10452 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
10454 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
10456 - Correctly report written bytes on linked connections. Found while
10457 implementing 1790. Bugfix on 0.2.2.4-alpha.
10458 - Fix three memory leaks: one in circuit_build_times_parse_state(),
10459 one in dirvote_add_signatures_to_pending_consensus(), and one every
10460 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
10461 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
10463 o Code simplifications and refactoring:
10464 - Take a first step towards making or.h smaller by splitting out
10465 function definitions for all source files in src/or/. Leave
10466 structures and defines in or.h for now.
10467 - Remove a bunch of unused function declarations as well as a block of
10468 #if 0'd code from the unit tests. Closes bug 1824.
10469 - New unit tests for exit-port history statistics; refactored exit
10470 statistics code to be more easily tested.
10471 - Remove the old debian/ directory from the main Tor distribution.
10472 The official Tor-for-debian git repository lives at the URL
10473 https://git.torproject.org/debian/tor.git
10476 Changes in version 0.2.2.14-alpha - 2010-07-12
10477 Tor 0.2.2.14-alpha greatly improves client-side handling of
10478 circuit build timeouts, which are used to estimate speed and improve
10479 performance. We also move to a much better GeoIP database, port Tor to
10480 Windows CE, introduce new compile flags that improve code security,
10481 add an eighth v3 directory authority, and address a lot of more
10485 - Tor directory authorities no longer crash when started with a
10486 cached-microdesc-consensus file in their data directory. Bugfix
10487 on 0.2.2.6-alpha; fixes bug 1532.
10488 - Treat an unset $HOME like an empty $HOME rather than triggering an
10489 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
10490 - Ignore negative and large circuit build timeout values that can
10491 happen during a suspend or hibernate. These values caused various
10492 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
10493 - Alter calculation of Pareto distribution parameter 'Xm' for
10494 Circuit Build Timeout learning to use the weighted average of the
10495 top N=3 modes (because we have three entry guards). Considering
10496 multiple modes should improve the timeout calculation in some cases,
10497 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
10499 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
10500 right censored distribution model. This approach improves over the
10501 synthetic timeout generation approach that was producing insanely
10502 high timeout values. Now we calculate build timeouts using truncated
10503 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
10504 - Do not close circuits that are under construction when they reach
10505 the circuit build timeout. Instead, leave them building (but do not
10506 use them) for up until the time corresponding to the 95th percentile
10507 on the Pareto CDF or 60 seconds, whichever is greater. This is done
10508 to provide better data for the new Pareto model. This percentile
10509 can be controlled by the consensus.
10512 - Move to the June 2010 Maxmind GeoLite country db (rather than the
10513 June 2009 ip-to-country GeoIP db) for our statistics that count
10514 how many users relays are seeing from each country. Now we have
10515 more accurate data for many African countries.
10516 - Port Tor to build and run correctly on Windows CE systems, using
10517 the wcecompat library. Contributed by Valerio Lupi.
10518 - New "--enable-gcc-hardening" ./configure flag (off by default)
10519 to turn on gcc compile time hardening options. It ensures
10520 that signed ints have defined behavior (-fwrapv), enables
10521 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
10522 with canaries (-fstack-protector-all), turns on ASLR protection if
10523 supported by the kernel (-fPIE, -pie), and adds additional security
10524 related warnings. Verified to work on Mac OS X and Debian Lenny.
10525 - New "--enable-linker-hardening" ./configure flag (off by default)
10526 to turn on ELF specific hardening features (relro, now). This does
10527 not work with Mac OS X or any other non-ELF binary format.
10529 o New directory authorities:
10530 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
10534 - New config option "WarnUnsafeSocks 0" disables the warning that
10535 occurs whenever Tor receives a socks handshake using a version of
10536 the socks protocol that can only provide an IP address (rather
10537 than a hostname). Setups that do DNS locally over Tor are fine,
10538 and we shouldn't spam the logs in that case.
10539 - Convert the HACKING file to asciidoc, and add a few new sections
10540 to it, explaining how we use Git, how we make changelogs, and
10541 what should go in a patch.
10542 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
10543 event, to give information on the current rate of circuit timeouts
10544 over our stored history.
10545 - Add ability to disable circuit build time learning via consensus
10546 parameter and via a LearnCircuitBuildTimeout config option. Also
10547 automatically disable circuit build time calculation if we are
10548 either a AuthoritativeDirectory, or if we fail to write our state
10549 file. Fixes bug 1296.
10550 - More gracefully handle corrupt state files, removing asserts
10551 in favor of saving a backup and resetting state.
10552 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
10556 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
10558 - When a2x fails, mention that the user could disable manpages instead
10559 of trying to fix their asciidoc installation.
10560 - Where available, use Libevent 2.0's periodic timers so that our
10561 once-per-second cleanup code gets called even more closely to
10562 once per second than it would otherwise. Fixes bug 943.
10563 - If you run a bridge that listens on multiple IP addresses, and
10564 some user configures a bridge address that uses a different IP
10565 address than your bridge writes in its router descriptor, and the
10566 user doesn't specify an identity key, their Tor would discard the
10567 descriptor because "it isn't one of our configured bridges", and
10568 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
10569 Bugfix on 0.2.0.3-alpha.
10570 - If OpenSSL fails to make a duplicate of a private or public key, log
10571 an error message and try to exit cleanly. May help with debugging
10572 if bug 1209 ever remanifests.
10573 - Save a couple bytes in memory allocation every time we escape
10574 certain characters in a string. Patch from Florian Zumbiehl.
10575 - Make it explicit that we don't cannibalize one-hop circuits. This
10576 happens in the wild, but doesn't turn out to be a problem because
10577 we fortunately don't use those circuits. Many thanks to outofwords
10578 for the initial analysis and to swissknife who confirmed that
10579 two-hop circuits are actually created.
10580 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
10581 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
10582 - Eliminate a case where a circuit build time warning was displayed
10583 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
10586 Changes in version 0.2.1.26 - 2010-05-02
10587 Tor 0.2.1.26 addresses the recent connection and memory overload
10588 problems we've been seeing on relays, especially relays with their
10589 DirPort open. If your relay has been crashing, or you turned it off
10590 because it used too many resources, give this release a try.
10592 This release also fixes yet another instance of broken OpenSSL libraries
10593 that was causing some relays to drop out of the consensus.
10596 - Teach relays to defend themselves from connection overload. Relays
10597 now close idle circuits early if it looks like they were intended
10598 for directory fetches. Relays are also more aggressive about closing
10599 TLS connections that have no circuits on them. Such circuits are
10600 unlikely to be re-used, and tens of thousands of them were piling
10601 up at the fast relays, causing the relays to run out of sockets
10602 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
10603 their directory fetches over TLS).
10604 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
10605 that claim to be earlier than 0.9.8m, but which have in reality
10606 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
10607 behavior. Possible fix for some cases of bug 1346.
10608 - Directory mirrors were fetching relay descriptors only from v2
10609 directory authorities, rather than v3 authorities like they should.
10610 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
10611 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
10614 - Finally get rid of the deprecated and now harmful notion of "clique
10615 mode", where directory authorities maintain TLS connections to
10619 - In the util/threads test, no longer free the test_mutex before all
10620 worker threads have finished. Bugfix on 0.2.1.6-alpha.
10621 - The master thread could starve the worker threads quite badly on
10622 certain systems, causing them to run only partially in the allowed
10623 window. This resulted in test failures. Now the master thread sleeps
10624 occasionally for a few microseconds while the two worker-threads
10625 compete for the mutex. Bugfix on 0.2.0.1-alpha.
10628 Changes in version 0.2.2.13-alpha - 2010-04-24
10629 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
10630 problems we've been seeing on relays, especially relays with their
10631 DirPort open. If your relay has been crashing, or you turned it off
10632 because it used too many resources, give this release a try.
10635 - Teach relays to defend themselves from connection overload. Relays
10636 now close idle circuits early if it looks like they were intended
10637 for directory fetches. Relays are also more aggressive about closing
10638 TLS connections that have no circuits on them. Such circuits are
10639 unlikely to be re-used, and tens of thousands of them were piling
10640 up at the fast relays, causing the relays to run out of sockets
10641 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
10642 their directory fetches over TLS).
10645 - Finally get rid of the deprecated and now harmful notion of "clique
10646 mode", where directory authorities maintain TLS connections to
10648 - Directory authorities now do an immediate reachability check as soon
10649 as they hear about a new relay. This change should slightly reduce
10650 the time between setting up a relay and getting listed as running
10651 in the consensus. It should also improve the time between setting
10652 up a bridge and seeing use by bridge users.
10653 - Directory authorities no longer launch a TLS connection to every
10654 relay as they startup. Now that we have 2k+ descriptors cached,
10655 the resulting network hiccup is becoming a burden. Besides,
10656 authorities already avoid voting about Running for the first half
10657 hour of their uptime.
10660 Changes in version 0.2.2.12-alpha - 2010-04-20
10661 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
10662 handle and vote on descriptors. It was causing relays to drop out of
10666 - Many relays have been falling out of the consensus lately because
10667 not enough authorities know about their descriptor for them to get
10668 a majority of votes. When we deprecated the v2 directory protocol,
10669 we got rid of the only way that v3 authorities can hear from each
10670 other about other descriptors. Now authorities examine every v3
10671 vote for new descriptors, and fetch them from that authority. Bugfix
10673 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
10674 and a warning in or.h related to bandwidth_weight_rule_t that
10675 prevented clean compile on OS X. Fixes bug 1363; bugfix on
10677 - Fix a segfault on relays when DirReqStatistics is enabled
10678 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
10682 - Demote a confusing TLS warning that relay operators might get when
10683 someone tries to talk to their OrPort. It is neither the operator's
10684 fault nor can they do anything about it. Fixes bug 1364; bugfix
10688 Changes in version 0.2.2.11-alpha - 2010-04-15
10689 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
10690 libraries that was causing some relays to drop out of the consensus.
10693 - Directory mirrors were fetching relay descriptors only from v2
10694 directory authorities, rather than v3 authorities like they should.
10695 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
10696 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
10697 - Fix a parsing error that made every possible value of
10698 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
10699 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
10700 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
10701 about the option without breaking older ones.
10702 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
10703 that claim to be earlier than 0.9.8m, but which have in reality
10704 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
10705 behavior. Possible fix for some cases of bug 1346.
10708 - Experiment with a more aggressive approach to preventing clients
10709 from making one-hop exit streams. Exit relays who want to try it
10710 out can set "RefuseUnknownExits 1" in their torrc, and then look
10711 for "Attempt by %s to open a stream" log messages. Let us know
10713 - Add support for statically linking zlib by specifying
10714 --enable-static-zlib, to go with our support for statically linking
10715 openssl and libevent. Resolves bug 1358.
10718 - Fix a segfault that happens whenever a Tor client that is using
10719 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
10721 - When we cleaned up the contrib/tor-exit-notice.html file, we left
10722 out the first line. Fixes bug 1295.
10723 - When building the manpage from a tarball, we required asciidoc, but
10724 the asciidoc -> roff/html conversion was already done for the
10725 tarball. Make 'make' complain only when we need asciidoc (either
10726 because we're compiling directly from git, or because we altered
10727 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
10728 - When none of the directory authorities vote on any params, Tor
10729 segfaulted when trying to make the consensus from the votes. We
10730 didn't trigger the bug in practice, because authorities do include
10731 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
10734 - In the util/threads test, no longer free the test_mutex before all
10735 worker threads have finished. Bugfix on 0.2.1.6-alpha.
10736 - The master thread could starve the worker threads quite badly on
10737 certain systems, causing them to run only partially in the allowed
10738 window. This resulted in test failures. Now the master thread sleeps
10739 occasionally for a few microseconds while the two worker-threads
10740 compete for the mutex. Bugfix on 0.2.0.1-alpha.
10743 Changes in version 0.2.2.10-alpha - 2010-03-07
10744 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
10745 could prevent relays from guessing their IP address correctly. It also
10746 starts the groundwork for another client-side performance boost, since
10747 currently we're not making efficient use of relays that have both the
10748 Guard flag and the Exit flag.
10751 - Fix a regression from our patch for bug 1244 that caused relays
10752 to guess their IP address incorrectly if they didn't set Address
10753 in their torrc and/or their address fails to resolve. Bugfix on
10754 0.2.2.9-alpha; fixes bug 1269.
10756 o Major features (performance):
10757 - Directory authorities now compute consensus weightings that instruct
10758 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
10759 and no flag. Clients that use these weightings will distribute
10760 network load more evenly across these different relay types. The
10761 weightings are in the consensus so we can change them globally in
10762 the future. Extra thanks to "outofwords" for finding some nasty
10763 security bugs in the first implementation of this feature.
10765 o Minor features (performance):
10766 - Always perform router selections using weighted relay bandwidth,
10767 even if we don't need a high capacity circuit at the time. Non-fast
10768 circuits now only differ from fast ones in that they can use relays
10769 not marked with the Fast flag. This "feature" could turn out to
10770 be a horrible bug; we should investigate more before it goes into
10774 - Allow disabling building of the manpages. Skipping the manpage
10775 speeds up the build considerably.
10777 o Minor bugfixes (on 0.2.2.x):
10778 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
10779 Bugfix on 0.2.2.9-alpha.
10780 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
10781 config option. Bugfix on 0.2.2.7-alpha.
10782 - Ship the asciidoc-helper file in the tarball, so that people can
10783 build from source if they want to, and touching the .1.txt files
10784 doesn't break the build. Bugfix on 0.2.2.9-alpha.
10786 o Minor bugfixes (on 0.2.1.x or earlier):
10787 - Fix a dereference-then-NULL-check sequence when publishing
10788 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
10790 - Fix another dereference-then-NULL-check sequence. Bugfix on
10791 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
10792 - Make sure we treat potentially not NUL-terminated strings correctly.
10793 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
10795 o Code simplifications and refactoring:
10796 - Fix some urls in the exit notice file and make it XHTML1.1 strict
10797 compliant. Based on a patch from Christian Kujau.
10798 - Don't use sed in asciidoc-helper anymore.
10799 - Make the build process fail if asciidoc cannot be found and
10800 building with asciidoc isn't disabled.
10803 Changes in version 0.2.2.9-alpha - 2010-02-22
10804 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
10805 location of a directory authority, and cleans up a bunch of small bugs.
10807 o Directory authority changes:
10808 - Change IP address for dannenberg (v3 directory authority), and
10809 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
10810 service directory authority) from the list.
10813 - Make Tor work again on the latest OS X: when deciding whether to
10814 use strange flags to turn TLS renegotiation on, detect the OpenSSL
10815 version at run-time, not compile time. We need to do this because
10816 Apple doesn't update its dev-tools headers when it updates its
10817 libraries in a security patch.
10818 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
10819 that could happen on 32-bit platforms with 64-bit time_t. Also fix
10820 a memory leak when requesting a hidden service descriptor we've
10821 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
10823 - Authorities could be tricked into giving out the Exit flag to relays
10824 that didn't allow exiting to any ports. This bug could screw
10825 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
10826 1238. Bug discovered by Martin Kowalczyk.
10827 - When freeing a session key, zero it out completely. We only zeroed
10828 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
10829 patched by ekir. Fixes bug 1254.
10832 - Fix static compilation by listing the openssl libraries in the right
10833 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
10834 - Resume handling .exit hostnames in a special way: originally we
10835 stripped the .exit part and used the requested exit relay. In
10836 0.2.2.1-alpha we stopped treating them in any special way, meaning
10837 if you use a .exit address then Tor will pass it on to the exit
10838 relay. Now we reject the .exit stream outright, since that behavior
10839 might be more expected by the user. Found and diagnosed by Scott
10840 Bennett and Downie on or-talk.
10841 - Don't spam the controller with events when we have no file
10842 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
10843 for log messages was already solved from bug 748.)
10844 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
10846 - Make the DNSPort option work with libevent 2.x. Don't alter the
10847 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
10848 - Emit a GUARD DROPPED controller event for a case we missed.
10849 - Make more fields in the controller protocol case-insensitive, since
10850 control-spec.txt said they were.
10851 - Refactor resolve_my_address() to not use gethostbyname() anymore.
10852 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
10853 - Fix a spec conformance issue: the network-status-version token
10854 must be the first token in a v3 consensus or vote. Discovered by
10855 parakeep. Bugfix on 0.2.0.3-alpha.
10857 o Code simplifications and refactoring:
10858 - Generate our manpage and HTML documentation using Asciidoc. This
10859 change should make it easier to maintain the documentation, and
10860 produce nicer HTML.
10861 - Remove the --enable-iphone option. According to reports from Marco
10862 Bonetti, Tor builds fine without any special tweaking on recent
10863 iPhone SDK versions.
10864 - Removed some unnecessary files from the source distribution. The
10865 AUTHORS file has now been merged into the people page on the
10866 website. The roadmaps and design doc can now be found in the
10867 projects directory in svn.
10868 - Enabled various circuit build timeout constants to be controlled
10869 by consensus parameters. Also set better defaults for these
10870 parameters based on experimentation on broadband and simulated
10871 high latency links.
10874 - The 'EXTENDCIRCUIT' control port command can now be used with
10875 a circ id of 0 and no path. This feature will cause Tor to build
10876 a new 'fast' general purpose circuit using its own path selection
10878 - Added a BUILDTIMEOUT_SET controller event to describe changes
10879 to the circuit build timeout.
10880 - Future-proof the controller protocol a bit by ignoring keyword
10881 arguments we do not recognize.
10882 - Expand homedirs passed to tor-checkkey. This should silence a
10883 coverity complaint about passing a user-supplied string into
10884 open() without checking it.
10887 Changes in version 0.2.1.25 - 2010-03-16
10888 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
10889 prevent relays from guessing their IP address correctly. It also fixes
10890 several minor potential security bugs.
10893 - Fix a regression from our patch for bug 1244 that caused relays
10894 to guess their IP address incorrectly if they didn't set Address
10895 in their torrc and/or their address fails to resolve. Bugfix on
10896 0.2.1.23; fixes bug 1269.
10897 - When freeing a session key, zero it out completely. We only zeroed
10898 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
10899 patched by ekir. Fixes bug 1254.
10902 - Fix a dereference-then-NULL-check sequence when publishing
10903 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
10905 - Fix another dereference-then-NULL-check sequence. Bugfix on
10906 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
10907 - Make sure we treat potentially not NUL-terminated strings correctly.
10908 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
10912 Changes in version 0.2.1.24 - 2010-02-21
10913 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
10917 - Work correctly out-of-the-box with even more vendor-patched versions
10918 of OpenSSL. In particular, make it so Debian and OS X don't need
10919 customized patches to run/build.
10922 Changes in version 0.2.1.23 - 2010-02-13
10923 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
10924 again on the latest OS X, and updates the location of a directory
10927 o Major bugfixes (performance):
10928 - We were selecting our guards uniformly at random, and then weighting
10929 which of our guards we'd use uniformly at random. This imbalance
10930 meant that Tor clients were severely limited on throughput (and
10931 probably latency too) by the first hop in their circuit. Now we
10932 select guards weighted by currently advertised bandwidth. We also
10933 automatically discard guards picked using the old algorithm. Fixes
10934 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
10937 - Make Tor work again on the latest OS X: when deciding whether to
10938 use strange flags to turn TLS renegotiation on, detect the OpenSSL
10939 version at run-time, not compile time. We need to do this because
10940 Apple doesn't update its dev-tools headers when it updates its
10941 libraries in a security patch.
10942 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
10943 that could happen on 32-bit platforms with 64-bit time_t. Also fix
10944 a memory leak when requesting a hidden service descriptor we've
10945 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
10948 o Directory authority changes:
10949 - Change IP address for dannenberg (v3 directory authority), and
10950 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
10951 service directory authority) from the list.
10954 - Refactor resolve_my_address() to not use gethostbyname() anymore.
10955 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
10958 - Avoid a mad rush at the beginning of each month when each client
10959 rotates half of its guards. Instead we spread the rotation out
10960 throughout the month, but we still avoid leaving a precise timestamp
10961 in the state file about when we first picked the guard. Improves
10962 over the behavior introduced in 0.1.2.17.
10965 Changes in version 0.2.2.8-alpha - 2010-01-26
10966 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
10967 causing bridge relays to disappear. If you're running a bridge,
10971 - Fix a memory corruption bug on bridges that occured during the
10972 inclusion of stats data in extra-info descriptors. Also fix the
10973 interface for geoip_get_bridge_stats* to prevent similar bugs in
10974 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
10975 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
10978 - Ignore OutboundBindAddress when connecting to localhost.
10979 Connections to localhost need to come _from_ localhost, or else
10980 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
10984 Changes in version 0.2.2.7-alpha - 2010-01-19
10985 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
10986 as laying the groundwork for further relay-side performance fixes. It
10987 also starts cleaning up client behavior with respect to the EntryNodes,
10988 ExitNodes, and StrictNodes config options.
10990 This release also rotates two directory authority keys, due to a
10991 security breach of some of the Torproject servers.
10993 o Directory authority changes:
10994 - Rotate keys (both v3 identity and relay identity) for moria1
10997 o Major features (performance):
10998 - We were selecting our guards uniformly at random, and then weighting
10999 which of our guards we'd use uniformly at random. This imbalance
11000 meant that Tor clients were severely limited on throughput (and
11001 probably latency too) by the first hop in their circuit. Now we
11002 select guards weighted by currently advertised bandwidth. We also
11003 automatically discard guards picked using the old algorithm. Fixes
11004 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
11005 - When choosing which cells to relay first, relays can now favor
11006 circuits that have been quiet recently, to provide lower latency
11007 for low-volume circuits. By default, relays enable or disable this
11008 feature based on a setting in the consensus. You can override
11009 this default by using the new "CircuitPriorityHalflife" config
11010 option. Design and code by Ian Goldberg, Can Tang, and Chris
11012 - Add separate per-conn write limiting to go with the per-conn read
11013 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
11014 but never per-conn write limits.
11015 - New consensus params "bwconnrate" and "bwconnburst" to let us
11016 rate-limit client connections as they enter the network. It's
11017 controlled in the consensus so we can turn it on and off for
11018 experiments. It's starting out off. Based on proposal 163.
11020 o Major features (relay selection options):
11021 - Switch to a StrictNodes config option, rather than the previous
11022 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
11023 "StrictExcludeNodes" option.
11024 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
11025 change during a config reload, mark and discard all our origin
11026 circuits. This fix should address edge cases where we change the
11027 config options and but then choose a circuit that we created before
11029 - If EntryNodes or ExitNodes are set, be more willing to use an
11030 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
11032 - Make EntryNodes config option much more aggressive even when
11033 StrictNodes is not set. Before it would prepend your requested
11034 entrynodes to your list of guard nodes, but feel free to use others
11035 after that. Now it chooses only from your EntryNodes if any of
11036 those are available, and only falls back to others if a) they're
11037 all down and b) StrictNodes is not set.
11038 - Now we refresh your entry guards from EntryNodes at each consensus
11039 fetch -- rather than just at startup and then they slowly rot as
11040 the network changes.
11043 - Stop bridge directory authorities from answering dbg-stability.txt
11044 directory queries, which would let people fetch a list of all
11045 bridge identities they track. Bugfix on 0.2.1.6-alpha.
11048 - Log a notice when we get a new control connection. Now it's easier
11049 for security-conscious users to recognize when a local application
11050 is knocking on their controller door. Suggested by bug 1196.
11051 - New config option "CircuitStreamTimeout" to override our internal
11052 timeout schedule for how many seconds until we detach a stream from
11053 a circuit and try a new circuit. If your network is particularly
11054 slow, you might want to set this to a number like 60.
11055 - New controller command "getinfo config-text". It returns the
11056 contents that Tor would write if you send it a SAVECONF command,
11057 so the controller can write the file to disk itself.
11058 - New options for SafeLogging to allow scrubbing only log messages
11059 generated while acting as a relay.
11060 - Ship the bridges spec file in the tarball too.
11061 - Avoid a mad rush at the beginning of each month when each client
11062 rotates half of its guards. Instead we spread the rotation out
11063 throughout the month, but we still avoid leaving a precise timestamp
11064 in the state file about when we first picked the guard. Improves
11065 over the behavior introduced in 0.1.2.17.
11067 o Minor bugfixes (compiling):
11068 - Fix compilation on OS X 10.3, which has a stub mlockall() but
11069 hides it. Bugfix on 0.2.2.6-alpha.
11070 - Fix compilation on Solaris by removing support for the
11071 DisableAllSwap config option. Solaris doesn't have an rlimit for
11072 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
11075 o Minor bugfixes (crashes):
11076 - Do not segfault when writing buffer stats when we haven't observed
11077 a single circuit to report about. Found by Fabian Lanze. Bugfix on
11079 - If we're in the pathological case where there's no exit bandwidth
11080 but there is non-exit bandwidth, or no guard bandwidth but there
11081 is non-guard bandwidth, don't crash during path selection. Bugfix
11083 - Fix an impossible-to-actually-trigger buffer overflow in relay
11084 descriptor generation. Bugfix on 0.1.0.15.
11086 o Minor bugfixes (privacy):
11087 - Fix an instance where a Tor directory mirror might accidentally
11088 log the IP address of a misbehaving Tor client. Bugfix on
11090 - Don't list Windows capabilities in relay descriptors. We never made
11091 use of them, and maybe it's a bad idea to publish them. Bugfix
11094 o Minor bugfixes (other):
11095 - Resolve an edge case in path weighting that could make us misweight
11096 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
11097 - Fix statistics on client numbers by country as seen by bridges that
11098 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
11099 intervals instead of variable 12-to-48-hour intervals.
11100 - After we free an internal connection structure, overwrite it
11101 with a different memory value than we use for overwriting a freed
11102 internal circuit structure. Should help with debugging. Suggested
11104 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
11107 o Removed features:
11108 - Remove the HSAuthorityRecordStats option that version 0 hidden
11109 service authorities could have used to track statistics of overall
11110 hidden service usage.
11113 Changes in version 0.2.1.22 - 2010-01-19
11114 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
11115 authorities -- it would tell you its whole history of bridge descriptors
11116 if you make the right directory request. This stable update also
11117 rotates two of the seven v3 directory authority keys and locations.
11119 o Directory authority changes:
11120 - Rotate keys (both v3 identity and relay identity) for moria1
11124 - Stop bridge directory authorities from answering dbg-stability.txt
11125 directory queries, which would let people fetch a list of all
11126 bridge identities they track. Bugfix on 0.2.1.6-alpha.
11129 Changes in version 0.2.1.21 - 2009-12-21
11130 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
11131 library. If you use Tor on Linux / Unix and you're getting SSL
11132 renegotiation errors, upgrading should help. We also recommend an
11133 upgrade if you're an exit relay.
11136 - Work around a security feature in OpenSSL 0.9.8l that prevents our
11137 handshake from working unless we explicitly tell OpenSSL that we
11138 are using SSL renegotiation safely. We are, of course, but OpenSSL
11139 0.9.8l won't work unless we say we are.
11140 - Avoid crashing if the client is trying to upload many bytes and the
11141 circuit gets torn down at the same time, or if the flip side
11142 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
11145 - Do not refuse to learn about authority certs and v2 networkstatus
11146 documents that are older than the latest consensus. This bug might
11147 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
11148 Spotted and fixed by xmux.
11149 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
11150 trigger platform-specific option misparsing case found by Coverity
11152 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
11153 trigger assert. Fixes bug 1173.
11156 Changes in version 0.2.2.6-alpha - 2009-11-19
11157 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
11158 support for the new lower-footprint "microdescriptor" directory design,
11159 future-proofing our consensus format against new hash functions or
11160 other changes, and an Android port. It also makes Tor compatible with
11161 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
11164 - Directory authorities can now create, vote on, and serve multiple
11165 parallel formats of directory data as part of their voting process.
11166 Partially implements Proposal 162: "Publish the consensus in
11168 - Directory authorities can now agree on and publish small summaries
11169 of router information that clients can use in place of regular
11170 server descriptors. This transition will eventually allow clients
11171 to use far less bandwidth for downloading information about the
11172 network. Begins the implementation of Proposal 158: "Clients
11173 download consensus + microdescriptors".
11174 - The directory voting system is now extensible to use multiple hash
11175 algorithms for signatures and resource selection. Newer formats
11176 are signed with SHA256, with a possibility for moving to a better
11177 hash algorithm in the future.
11178 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
11179 current and future memory pages via mlockall(). On supported
11180 platforms (modern Linux and probably BSD but not Windows or OS X),
11181 this should effectively disable any and all attempts to page out
11182 memory. This option requires that you start your Tor as root --
11183 if you use DisableAllSwap, please consider using the User option
11184 to properly reduce the privileges of your Tor.
11185 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
11186 to help Tor build correctly for Android phones.
11189 - Work around a security feature in OpenSSL 0.9.8l that prevents our
11190 handshake from working unless we explicitly tell OpenSSL that we
11191 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
11192 won't work unless we say we are.
11195 - Fix a crash bug when trying to initialize the evdns module in
11196 Libevent 2. Bugfix on 0.2.1.16-rc.
11197 - Stop logging at severity 'warn' when some other Tor client tries
11198 to establish a circuit with us using weak DH keys. It's a protocol
11199 violation, but that doesn't mean ordinary users need to hear about
11200 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
11201 - Do not refuse to learn about authority certs and v2 networkstatus
11202 documents that are older than the latest consensus. This bug might
11203 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
11204 Spotted and fixed by xmux.
11205 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
11206 - If all authorities restart at once right before a consensus vote,
11207 nobody will vote about "Running", and clients will get a consensus
11208 with no usable relays. Instead, authorities refuse to build a
11209 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
11210 - If your relay can't keep up with the number of incoming create
11211 cells, it would log one warning per failure into your logs. Limit
11212 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
11213 - Bridges now use "reject *:*" as their default exit policy. Bugfix
11214 on 0.2.0.3-alpha; fixes bug 1113.
11215 - Fix a memory leak on directory authorities during voting that was
11216 introduced in 0.2.2.1-alpha. Found via valgrind.
11219 Changes in version 0.2.1.20 - 2009-10-15
11220 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
11221 services at once, prepares for more performance improvements, and
11222 fixes a bunch of smaller bugs.
11224 The Windows and OS X bundles also include a more recent Vidalia,
11225 and switch from Privoxy to Polipo.
11227 The OS X installers are now drag and drop. It's best to un-install
11228 Tor/Vidalia and then install this new bundle, rather than upgrade. If
11229 you want to upgrade, you'll need to update the paths for Tor and Polipo
11230 in the Vidalia Settings window.
11233 - Send circuit or stream sendme cells when our window has decreased
11234 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
11235 by Karsten when testing the "reduce circuit window" performance
11236 patch. Bugfix on the 54th commit on Tor -- from July 2002,
11237 before the release of Tor 0.0.0. This is the new winner of the
11239 - Fix a remotely triggerable memory leak when a consensus document
11240 contains more than one signature from the same voter. Bugfix on
11242 - Avoid segfault in rare cases when finishing an introduction circuit
11243 as a client and finding out that we don't have an introduction key
11244 for it. Fixes bug 1073. Reported by Aaron Swartz.
11247 - Tor now reads the "circwindow" parameter out of the consensus,
11248 and uses that value for its circuit package window rather than the
11249 default of 1000 cells. Begins the implementation of proposal 168.
11251 o New directory authorities:
11252 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
11254 - Move moria1 and tonga to alternate IP addresses.
11257 - Fix a signed/unsigned compile warning in 0.2.1.19.
11258 - Fix possible segmentation fault on directory authorities. Bugfix on
11260 - Fix an extremely rare infinite recursion bug that could occur if
11261 we tried to log a message after shutting down the log subsystem.
11262 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
11263 - Fix an obscure bug where hidden services on 64-bit big-endian
11264 systems might mis-read the timestamp in v3 introduce cells, and
11265 refuse to connect back to the client. Discovered by "rotor".
11266 Bugfix on 0.2.1.6-alpha.
11267 - We were triggering a CLOCK_SKEW controller status event whenever
11268 we connect via the v2 connection protocol to any relay that has
11269 a wrong clock. Instead, we should only inform the controller when
11270 it's a trusted authority that claims our clock is wrong. Bugfix
11271 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
11272 - We were telling the controller about CHECKING_REACHABILITY and
11273 REACHABILITY_FAILED status events whenever we launch a testing
11274 circuit or notice that one has failed. Instead, only tell the
11275 controller when we want to inform the user of overall success or
11276 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
11278 - Don't warn when we're using a circuit that ends with a node
11279 excluded in ExcludeExitNodes, but the circuit is not used to access
11280 the outside world. This should help fix bug 1090. Bugfix on
11282 - Work around a small memory leak in some versions of OpenSSL that
11283 stopped the memory used by the hostname TLS extension from being
11287 - Add a "getinfo status/accepted-server-descriptor" controller
11288 command, which is the recommended way for controllers to learn
11289 whether our server descriptor has been successfully received by at
11290 least on directory authority. Un-recommend good-server-descriptor
11291 getinfo and status events until we have a better design for them.
11294 Changes in version 0.2.2.5-alpha - 2009-10-11
11295 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
11298 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
11300 o Directory authorities:
11301 - Temporarily (just for this release) move dizum to an alternate
11305 Changes in version 0.2.2.4-alpha - 2009-10-10
11306 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
11307 introduces a new unit test framework, shifts directry authority
11308 addresses around to reduce the impact from recent blocking events,
11309 and fixes a few smaller bugs.
11312 - Fix several more asserts in the circuit_build_times code, for
11313 example one that causes Tor to fail to start once we have
11314 accumulated 5000 build times in the state file. Bugfixes on
11315 0.2.2.2-alpha; fixes bug 1108.
11317 o New directory authorities:
11318 - Move moria1 and Tonga to alternate IP addresses.
11321 - Log SSL state transitions at debug level during handshake, and
11322 include SSL states in error messages. This may help debug future
11323 SSL handshake issues.
11324 - Add a new "Handshake" log domain for activities that happen
11325 during the TLS handshake.
11326 - Revert to the "June 3 2009" ip-to-country file. The September one
11327 seems to have removed most US IP addresses.
11328 - Directory authorities now reject Tor relays with versions less than
11329 0.1.2.14. This step cuts out four relays from the current network,
11330 none of which are very big.
11333 - Fix a couple of smaller issues with gathering statistics. Bugfixes
11335 - Fix two memory leaks in the error case of
11336 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
11337 - Don't count one-hop circuits when we're estimating how long it
11338 takes circuits to build on average. Otherwise we'll set our circuit
11339 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
11340 - Directory authorities no longer change their opinion of, or vote on,
11341 whether a router is Running, unless they have themselves been
11342 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
11345 o Code simplifications and refactoring:
11346 - Revise our unit tests to use the "tinytest" framework, so we
11347 can run tests in their own processes, have smarter setup/teardown
11348 code, and so on. The unit test code has moved to its own
11349 subdirectory, and has been split into multiple modules.
11352 Changes in version 0.2.2.3-alpha - 2009-09-23
11353 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
11356 - Fix an overzealous assert in our new circuit build timeout code.
11357 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
11360 - If the networkstatus consensus tells us that we should use a
11361 negative circuit package window, ignore it. Otherwise we'll
11362 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
11365 Changes in version 0.2.2.2-alpha - 2009-09-21
11366 Tor 0.2.2.2-alpha introduces our latest performance improvement for
11367 clients: Tor tracks the average time it takes to build a circuit, and
11368 avoids using circuits that take too long to build. For fast connections,
11369 this feature can cut your expected latency in half. For slow or flaky
11370 connections, it could ruin your Tor experience. Let us know if it does!
11373 - Tor now tracks how long it takes to build client-side circuits
11374 over time, and adapts its timeout to local network performance.
11375 Since a circuit that takes a long time to build will also provide
11376 bad performance, we get significant latency improvements by
11377 discarding the slowest 20% of circuits. Specifically, Tor creates
11378 circuits more aggressively than usual until it has enough data
11379 points for a good timeout estimate. Implements proposal 151.
11380 We are especially looking for reports (good and bad) from users with
11381 both EDGE and broadband connections that can move from broadband
11382 to EDGE and find out if the build-time data in the .tor/state gets
11383 reset without loss of Tor usability. You should also see a notice
11384 log message telling you that Tor has reset its timeout.
11385 - Directory authorities can now vote on arbitary integer values as
11386 part of the consensus process. This is designed to help set
11387 network-wide parameters. Implements proposal 167.
11388 - Tor now reads the "circwindow" parameter out of the consensus,
11389 and uses that value for its circuit package window rather than the
11390 default of 1000 cells. Begins the implementation of proposal 168.
11393 - Fix a remotely triggerable memory leak when a consensus document
11394 contains more than one signature from the same voter. Bugfix on
11398 - Fix an extremely rare infinite recursion bug that could occur if
11399 we tried to log a message after shutting down the log subsystem.
11400 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
11401 - Fix parsing for memory or time units given without a space between
11402 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
11403 - A networkstatus vote must contain exactly one signature. Spec
11404 conformance issue. Bugfix on 0.2.0.3-alpha.
11405 - Fix an obscure bug where hidden services on 64-bit big-endian
11406 systems might mis-read the timestamp in v3 introduce cells, and
11407 refuse to connect back to the client. Discovered by "rotor".
11408 Bugfix on 0.2.1.6-alpha.
11409 - We were triggering a CLOCK_SKEW controller status event whenever
11410 we connect via the v2 connection protocol to any relay that has
11411 a wrong clock. Instead, we should only inform the controller when
11412 it's a trusted authority that claims our clock is wrong. Bugfix
11413 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
11414 - We were telling the controller about CHECKING_REACHABILITY and
11415 REACHABILITY_FAILED status events whenever we launch a testing
11416 circuit or notice that one has failed. Instead, only tell the
11417 controller when we want to inform the user of overall success or
11418 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
11420 - Don't warn when we're using a circuit that ends with a node
11421 excluded in ExcludeExitNodes, but the circuit is not used to access
11422 the outside world. This should help fix bug 1090, but more problems
11423 remain. Bugfix on 0.2.1.6-alpha.
11424 - Work around a small memory leak in some versions of OpenSSL that
11425 stopped the memory used by the hostname TLS extension from being
11427 - Make our 'torify' script more portable; if we have only one of
11428 'torsocks' or 'tsocks' installed, don't complain to the user;
11429 and explain our warning about tsocks better.
11432 - Add a "getinfo status/accepted-server-descriptor" controller
11433 command, which is the recommended way for controllers to learn
11434 whether our server descriptor has been successfully received by at
11435 least on directory authority. Un-recommend good-server-descriptor
11436 getinfo and status events until we have a better design for them.
11437 - Update to the "September 4 2009" ip-to-country file.
11440 Changes in version 0.2.2.1-alpha - 2009-08-26
11441 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
11442 Tor clients to bootstrap on networks where only port 80 is reachable,
11443 makes it more straightforward to support hardware crypto accelerators,
11444 and starts the groundwork for gathering stats safely at relays.
11447 - Start the process of disabling ".exit" address notation, since it
11448 can be used for a variety of esoteric application-level attacks
11449 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
11452 o New directory authorities:
11453 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
11457 - New AccelName and AccelDir options add support for dynamic OpenSSL
11458 hardware crypto acceleration engines.
11459 - Tor now supports tunneling all of its outgoing connections over
11460 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
11461 configuration options. Code by Christopher Davis.
11464 - Send circuit or stream sendme cells when our window has decreased
11465 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
11466 by Karsten when testing the "reduce circuit window" performance
11467 patch. Bugfix on the 54th commit on Tor -- from July 2002,
11468 before the release of Tor 0.0.0. This is the new winner of the
11471 o New options for gathering stats safely:
11472 - Directory mirrors that set "DirReqStatistics 1" write statistics
11473 about directory requests to disk every 24 hours. As compared to the
11474 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
11475 1) stats are written to disk exactly every 24 hours; 2) estimated
11476 shares of v2 and v3 requests are determined as mean values, not at
11477 the end of a measurement period; 3) unresolved requests are listed
11478 with country code '??'; 4) directories also measure download times.
11479 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
11480 number of exit streams and transferred bytes per port to disk every
11482 - Relays that set "CellStatistics 1" write statistics on how long
11483 cells spend in their circuit queues to disk every 24 hours.
11484 - Entry nodes that set "EntryStatistics 1" write statistics on the
11485 rough number and origins of connecting clients to disk every 24
11487 - Relays that write any of the above statistics to disk and set
11488 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
11489 their extra-info documents.
11492 - New --digests command-line switch to output the digests of the
11493 source files Tor was built with.
11494 - The "torify" script now uses torsocks where available.
11495 - The memarea code now uses a sentinel value at the end of each area
11496 to make sure nothing writes beyond the end of an area. This might
11497 help debug some conceivable causes of bug 930.
11498 - Time and memory units in the configuration file can now be set to
11499 fractional units. For example, "2.5 GB" is now a valid value for
11501 - Certain Tor clients (such as those behind check.torproject.org) may
11502 want to fetch the consensus in an extra early manner. To enable this
11503 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
11504 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
11505 as only certain clients who must have this information sooner should
11507 - Instead of adding the svn revision to the Tor version string, report
11508 the git commit (when we're building from a git checkout).
11511 - If any of the v3 certs we download are unparseable, we should
11512 actually notice the failure so we don't retry indefinitely. Bugfix
11513 on 0.2.0.x; reported by "rotator".
11514 - If the cached cert file is unparseable, warn but don't exit.
11515 - Fix possible segmentation fault on directory authorities. Bugfix on
11517 - When Tor fails to parse a descriptor of any kind, dump it to disk.
11518 Might help diagnosing bug 1051.
11520 o Deprecated and removed features:
11521 - The controller no longer accepts the old obsolete "addr-mappings/"
11522 or "unregistered-servers-" GETINFO values.
11523 - Hidden services no longer publish version 0 descriptors, and clients
11524 do not request or use version 0 descriptors. However, the old hidden
11525 service authorities still accept and serve version 0 descriptors
11526 when contacted by older hidden services/clients.
11527 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
11528 always on; using them is necessary for correct forward-compatible
11530 - Remove support for .noconnect style addresses. Nobody was using
11531 them, and they provided another avenue for detecting Tor users
11532 via application-level web tricks.
11534 o Packaging changes:
11535 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
11536 installer bundles. See
11537 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
11538 for details of what's new in Vidalia 0.2.3.
11539 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
11540 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
11541 configuration file, rather than the old Privoxy.
11542 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
11543 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
11544 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
11545 better compatibility with OS X 10.6, aka Snow Leopard.
11546 - OS X Vidalia Bundle: The multi-package installer is now replaced
11547 by a simple drag and drop to the /Applications folder. This change
11548 occurred with the upgrade to Vidalia 0.2.3.
11551 Changes in version 0.2.1.19 - 2009-07-28
11552 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
11553 services on Tor 0.2.1.3-alpha through 0.2.1.18.
11556 - Make accessing hidden services on 0.2.1.x work right again.
11557 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
11558 part of patch provided by "optimist".
11561 - When a relay/bridge is writing out its identity key fingerprint to
11562 the "fingerprint" file and to its logs, write it without spaces. Now
11563 it will look like the fingerprints in our bridges documentation,
11564 and confuse fewer users.
11567 - Relays no longer publish a new server descriptor if they change
11568 their MaxAdvertisedBandwidth config option but it doesn't end up
11569 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
11570 fixes bug 1026. Patch from Sebastian.
11571 - Avoid leaking memory every time we get a create cell but we have
11572 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
11573 fixes bug 1034. Reported by BarkerJr.
11576 Changes in version 0.2.1.18 - 2009-07-24
11577 Tor 0.2.1.18 lays the foundations for performance improvements,
11578 adds status events to help users diagnose bootstrap problems, adds
11579 optional authentication/authorization for hidden services, fixes a
11580 variety of potential anonymity problems, and includes a huge pile of
11581 other features and bug fixes.
11584 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
11587 Changes in version 0.2.1.17-rc - 2009-07-07
11588 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
11589 candidate for the 0.2.1.x series. It lays the groundwork for further
11590 client performance improvements, and also fixes a big bug with directory
11591 authorities that were causing them to assign Guard and Stable flags
11594 The Windows bundles also finally include the geoip database that we
11595 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
11596 should actually install Torbutton rather than giving you a cryptic
11597 failure message (oops).
11600 - Clients now use the bandwidth values in the consensus, rather than
11601 the bandwidth values in each relay descriptor. This approach opens
11602 the door to more accurate bandwidth estimates once the directory
11603 authorities start doing active measurements. Implements more of
11607 - When Tor clients restart after 1-5 days, they discard all their
11608 cached descriptors as too old, but they still use the cached
11609 consensus document. This approach is good for robustness, but
11610 bad for performance: since they don't know any bandwidths, they
11611 end up choosing at random rather than weighting their choice by
11612 speed. Fixed by the above feature of putting bandwidths in the
11613 consensus. Bugfix on 0.2.0.x.
11614 - Directory authorities were neglecting to mark relays down in their
11615 internal histories if the relays fall off the routerlist without
11616 ever being found unreachable. So there were relays in the histories
11617 that haven't been seen for eight months, and are listed as being
11618 up for eight months. This wreaked havoc on the "median wfu"
11619 and "median mtbf" calculations, in turn making Guard and Stable
11620 flags very wrong, hurting network performance. Fixes bugs 696 and
11621 969. Bugfix on 0.2.0.6-alpha.
11624 - Serve the DirPortFrontPage page even when we have been approaching
11625 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
11626 - The control port would close the connection before flushing long
11627 replies, such as the network consensus, if a QUIT command was issued
11628 before the reply had completed. Now, the control port flushes all
11629 pending replies before closing the connection. Also fixed a spurious
11630 warning when a QUIT command is issued after a malformed or rejected
11631 AUTHENTICATE command, but before the connection was closed. Patch
11632 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
11633 - When we can't find an intro key for a v2 hidden service descriptor,
11634 fall back to the v0 hidden service descriptor and log a bug message.
11635 Workaround for bug 1024.
11636 - Fix a log message that did not respect the SafeLogging option.
11640 - If we're a relay and we change our IP address, be more verbose
11641 about the reason that made us change. Should help track down
11642 further bugs for relays on dynamic IP addresses.
11645 Changes in version 0.2.0.35 - 2009-06-24
11647 - Avoid crashing in the presence of certain malformed descriptors.
11648 Found by lark, and by automated fuzzing.
11649 - Fix an edge case where a malicious exit relay could convince a
11650 controller that the client's DNS question resolves to an internal IP
11651 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
11654 - Finally fix the bug where dynamic-IP relays disappear when their
11655 IP address changes: directory mirrors were mistakenly telling
11656 them their old address if they asked via begin_dir, so they
11657 never got an accurate answer about their new address, so they
11658 just vanished after a day. For belt-and-suspenders, relays that
11659 don't set Address in their config now avoid using begin_dir for
11660 all direct connections. Should fix bugs 827, 883, and 900.
11661 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
11662 that would occur on some exit nodes when DNS failures and timeouts
11663 occurred in certain patterns. Fix for bug 957.
11666 - When starting with a cache over a few days old, do not leak
11667 memory for the obsolete router descriptors in it. Bugfix on
11668 0.2.0.33; fixes bug 672.
11669 - Hidden service clients didn't use a cached service descriptor that
11670 was older than 15 minutes, but wouldn't fetch a new one either,
11671 because there was already one in the cache. Now, fetch a v2
11672 descriptor unless the same descriptor was added to the cache within
11673 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
11676 Changes in version 0.2.1.16-rc - 2009-06-20
11677 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
11678 a bunch of minor bugs.
11681 - Fix an edge case where a malicious exit relay could convince a
11682 controller that the client's DNS question resolves to an internal IP
11683 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
11685 o Major performance improvements (on 0.2.0.x):
11686 - Disable and refactor some debugging checks that forced a linear scan
11687 over the whole server-side DNS cache. These accounted for over 50%
11688 of CPU time on a relatively busy exit node's gprof profile. Found
11690 - Disable some debugging checks that appeared in exit node profile
11694 - Update to the "June 3 2009" ip-to-country file.
11695 - Do not have tor-resolve automatically refuse all .onion addresses;
11696 if AutomapHostsOnResolve is set in your torrc, this will work fine.
11698 o Minor bugfixes (on 0.2.0.x):
11699 - Log correct error messages for DNS-related network errors on
11701 - Fix a race condition that could cause crashes or memory corruption
11702 when running as a server with a controller listening for log
11704 - Avoid crashing when we have a policy specified in a DirPolicy or
11705 SocksPolicy or ReachableAddresses option with ports set on it,
11706 and we re-load the policy. May fix bug 996.
11707 - Hidden service clients didn't use a cached service descriptor that
11708 was older than 15 minutes, but wouldn't fetch a new one either,
11709 because there was already one in the cache. Now, fetch a v2
11710 descriptor unless the same descriptor was added to the cache within
11711 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
11713 o Minor bugfixes (on 0.2.1.x):
11714 - Don't warn users about low port and hibernation mix when they
11715 provide a *ListenAddress directive to fix that. Bugfix on
11717 - When switching back and forth between bridge mode, do not start
11718 gathering GeoIP data until two hours have passed.
11719 - Do not complain that the user has requested an excluded node as
11720 an exit when the node is not really an exit. This could happen
11721 because the circuit was for testing, or an introduction point.
11725 Changes in version 0.2.1.15-rc - 2009-05-25
11726 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
11727 series. It fixes a major bug on fast exit relays, as well as a variety
11728 of more minor bugs.
11730 o Major bugfixes (on 0.2.0.x):
11731 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
11732 that would occur on some exit nodes when DNS failures and timeouts
11733 occurred in certain patterns. Fix for bug 957.
11735 o Minor bugfixes (on 0.2.0.x):
11736 - Actually return -1 in the error case for read_bandwidth_usage().
11737 Harmless bug, since we currently don't care about the return value
11738 anywhere. Bugfix on 0.2.0.9-alpha.
11739 - Provide a more useful log message if bug 977 (related to buffer
11740 freelists) ever reappears, and do not crash right away.
11741 - Fix an assertion failure on 64-bit platforms when we allocated
11742 memory right up to the end of a memarea, then realigned the memory
11743 one step beyond the end. Fixes a possible cause of bug 930.
11744 - Protect the count of open sockets with a mutex, so we can't
11745 corrupt it when two threads are closing or opening sockets at once.
11746 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
11747 - Don't allow a bridge to publish its router descriptor to a
11748 non-bridge directory authority. Fixes part of bug 932.
11749 - When we change to or from being a bridge, reset our counts of
11750 client usage by country. Fixes bug 932.
11751 - Fix a bug that made stream bandwidth get misreported to the
11753 - Stop using malloc_usable_size() to use more area than we had
11754 actually allocated: it was safe, but made valgrind really unhappy.
11755 - Fix a memory leak when v3 directory authorities load their keys
11756 and cert from disk. Bugfix on 0.2.0.1-alpha.
11758 o Minor bugfixes (on 0.2.1.x):
11759 - Fix use of freed memory when deciding to mark a non-addable
11760 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
11763 Changes in version 0.2.1.14-rc - 2009-04-12
11764 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
11765 series. It begins fixing some major performance problems, and also
11766 finally addresses the bug that was causing relays on dynamic IP
11767 addresses to fall out of the directory.
11770 - Clients replace entry guards that were chosen more than a few months
11771 ago. This change should significantly improve client performance,
11772 especially once more people upgrade, since relays that have been
11773 a guard for a long time are currently overloaded.
11775 o Major bugfixes (on 0.2.0):
11776 - Finally fix the bug where dynamic-IP relays disappear when their
11777 IP address changes: directory mirrors were mistakenly telling
11778 them their old address if they asked via begin_dir, so they
11779 never got an accurate answer about their new address, so they
11780 just vanished after a day. For belt-and-suspenders, relays that
11781 don't set Address in their config now avoid using begin_dir for
11782 all direct connections. Should fix bugs 827, 883, and 900.
11783 - Relays were falling out of the networkstatus consensus for
11784 part of a day if they changed their local config but the
11785 authorities discarded their new descriptor as "not sufficiently
11786 different". Now directory authorities accept a descriptor as changed
11787 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
11788 patch by Sebastian.
11789 - Avoid crashing in the presence of certain malformed descriptors.
11790 Found by lark, and by automated fuzzing.
11793 - When generating circuit events with verbose nicknames for
11794 controllers, try harder to look up nicknames for routers on a
11795 circuit. (Previously, we would look in the router descriptors we had
11796 for nicknames, but not in the consensus.) Partial fix for bug 941.
11797 - If the bridge config line doesn't specify a port, assume 443.
11798 This makes bridge lines a bit smaller and easier for users to
11800 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
11801 bytes (aka 20KB/s), to match our documentation. Also update
11802 directory authorities so they always assign the Fast flag to relays
11803 with 20KB/s of capacity. Now people running relays won't suddenly
11804 find themselves not seeing any use, if the network gets faster
11806 - Update to the "April 3 2009" ip-to-country file.
11809 - Avoid trying to print raw memory to the logs when we decide to
11810 give up on downloading a given relay descriptor. Bugfix on
11812 - In tor-resolve, when the Tor client to use is specified by
11813 <hostname>:<port>, actually use the specified port rather than
11814 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
11815 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
11816 - When starting with a cache over a few days old, do not leak
11817 memory for the obsolete router descriptors in it. Bugfix on
11819 - Avoid double-free on list of successfully uploaded hidden
11820 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
11821 - Change memarea_strndup() implementation to work even when
11822 duplicating a string at the end of a page. This bug was
11823 harmless for now, but could have meant crashes later. Fix by
11824 lark. Bugfix on 0.2.1.1-alpha.
11825 - Limit uploaded directory documents to be 16M rather than 500K.
11826 The directory authorities were refusing v3 consensus votes from
11827 other authorities, since the votes are now 504K. Fixes bug 959;
11828 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
11829 - Directory authorities should never send a 503 "busy" response to
11830 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
11834 Changes in version 0.2.1.13-alpha - 2009-03-09
11835 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
11836 cleanups. We're finally getting close to a release candidate.
11839 - Correctly update the list of which countries we exclude as
11840 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
11841 lark. Bugfix on 0.2.1.6-alpha.
11843 o Minor bugfixes (on 0.2.0.x and earlier):
11844 - Automatically detect MacOSX versions earlier than 10.4.0, and
11845 disable kqueue from inside Tor when running with these versions.
11846 We previously did this from the startup script, but that was no
11847 help to people who didn't use the startup script. Resolves bug 863.
11848 - When we had picked an exit node for a connection, but marked it as
11849 "optional", and it turned out we had no onion key for the exit,
11850 stop wanting that exit and try again. This situation may not
11851 be possible now, but will probably become feasible with proposal
11852 158. Spotted by rovv. Fixes another case of bug 752.
11853 - Clients no longer cache certificates for authorities they do not
11854 recognize. Bugfix on 0.2.0.9-alpha.
11855 - When we can't transmit a DNS request due to a network error, retry
11856 it after a while, and eventually transmit a failing response to
11857 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
11858 - If the controller claimed responsibility for a stream, but that
11859 stream never finished making its connection, it would live
11860 forever in circuit_wait state. Now we close it after SocksTimeout
11861 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
11862 - Drop begin cells to a hidden service if they come from the middle
11863 of a circuit. Patch from lark.
11864 - When we erroneously receive two EXTEND cells for the same circuit
11865 ID on the same connection, drop the second. Patch from lark.
11866 - Fix a crash that occurs on exit nodes when a nameserver request
11867 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
11868 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
11870 - Do not assume that a stack-allocated character array will be
11871 64-bit aligned on platforms that demand that uint64_t access is
11872 aligned. Possible fix for bug 604.
11873 - Parse dates and IPv4 addresses in a locale- and libc-independent
11874 manner, to avoid platform-dependent behavior on malformed input.
11875 - Build correctly when configured to build outside the main source
11876 path. Patch from Michael Gold.
11877 - We were already rejecting relay begin cells with destination port
11878 of 0. Now also reject extend cells with destination port or address
11879 of 0. Suggested by lark.
11881 o Minor bugfixes (on 0.2.1.x):
11882 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
11883 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
11884 - If we're an exit node, scrub the IP address to which we are exiting
11885 in the logs. Bugfix on 0.2.1.8-alpha.
11888 - On Linux, use the prctl call to re-enable core dumps when the user
11890 - New controller event NEWCONSENSUS that lists the networkstatus
11891 lines for every recommended relay. Now controllers like Torflow
11892 can keep up-to-date on which relays they should be using.
11893 - Update to the "February 26 2009" ip-to-country file.
11896 Changes in version 0.2.0.34 - 2009-02-08
11897 Tor 0.2.0.34 features several more security-related fixes. You should
11898 upgrade, especially if you run an exit relay (remote crash) or a
11899 directory authority (remote infinite loop), or you're on an older
11900 (pre-XP) or not-recently-patched Windows (remote exploit).
11902 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
11903 have many known flaws, and nobody should be using them. You should
11904 upgrade. If you're using a Linux or BSD and its packages are obsolete,
11905 stop using those packages and upgrade anyway.
11908 - Fix an infinite-loop bug on handling corrupt votes under certain
11909 circumstances. Bugfix on 0.2.0.8-alpha.
11910 - Fix a temporary DoS vulnerability that could be performed by
11911 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
11912 - Avoid a potential crash on exit nodes when processing malformed
11913 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
11914 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
11915 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
11918 - Fix compilation on systems where time_t is a 64-bit integer.
11919 Patch from Matthias Drochner.
11920 - Don't consider expiring already-closed client connections. Fixes
11921 bug 893. Bugfix on 0.0.2pre20.
11924 Changes in version 0.2.1.12-alpha - 2009-02-08
11925 Tor 0.2.1.12-alpha features several more security-related fixes. You
11926 should upgrade, especially if you run an exit relay (remote crash) or
11927 a directory authority (remote infinite loop), or you're on an older
11928 (pre-XP) or not-recently-patched Windows (remote exploit). It also
11929 includes a big pile of minor bugfixes and cleanups.
11932 - Fix an infinite-loop bug on handling corrupt votes under certain
11933 circumstances. Bugfix on 0.2.0.8-alpha.
11934 - Fix a temporary DoS vulnerability that could be performed by
11935 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
11936 - Avoid a potential crash on exit nodes when processing malformed
11937 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
11940 - Let controllers actually ask for the "clients_seen" event for
11941 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
11942 reported by Matt Edman.
11943 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
11945 - Fix a bug in address parsing that was preventing bridges or hidden
11946 service targets from being at IPv6 addresses.
11947 - Solve a bug that kept hardware crypto acceleration from getting
11948 enabled when accounting was turned on. Fixes bug 907. Bugfix on
11950 - Remove a bash-ism from configure.in to build properly on non-Linux
11951 platforms. Bugfix on 0.2.1.1-alpha.
11952 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
11953 headers. Bugfix on 0.2.0.10-alpha.
11954 - Don't consider expiring already-closed client connections. Fixes
11955 bug 893. Bugfix on 0.0.2pre20.
11956 - Fix another interesting corner-case of bug 891 spotted by rovv:
11957 Previously, if two hosts had different amounts of clock drift, and
11958 one of them created a new connection with just the wrong timing,
11959 the other might decide to deprecate the new connection erroneously.
11960 Bugfix on 0.1.1.13-alpha.
11961 - Resolve a very rare crash bug that could occur when the user forced
11962 a nameserver reconfiguration during the middle of a nameserver
11963 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
11964 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
11965 Bugfix on 0.2.1.7-alpha.
11966 - If we're using bridges and our network goes away, be more willing
11967 to forgive our bridges and try again when we get an application
11968 request. Bugfix on 0.2.0.x.
11971 - Support platforms where time_t is 64 bits long. (Congratulations,
11972 NetBSD!) Patch from Matthias Drochner.
11973 - Add a 'getinfo status/clients-seen' controller command, in case
11974 controllers want to hear clients_seen events but connect late.
11977 - Disable GCC's strict alias optimization by default, to avoid the
11978 likelihood of its introducing subtle bugs whenever our code violates
11979 the letter of C99's alias rules.
11982 Changes in version 0.2.0.33 - 2009-01-21
11983 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
11984 useful to users. It also finally fixes a bug where a relay or client
11985 that's been off for many days would take a long time to bootstrap.
11987 This update also fixes an important security-related bug reported by
11988 Ilja van Sprundel. You should upgrade. (We'll send out more details
11989 about the bug once people have had some time to upgrade.)
11992 - Fix a heap-corruption bug that may be remotely triggerable on
11993 some platforms. Reported by Ilja van Sprundel.
11996 - When a stream at an exit relay is in state "resolving" or
11997 "connecting" and it receives an "end" relay cell, the exit relay
11998 would silently ignore the end cell and not close the stream. If
11999 the client never closes the circuit, then the exit relay never
12000 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
12001 reported by "wood".
12002 - When sending CREATED cells back for a given circuit, use a 64-bit
12003 connection ID to find the right connection, rather than an addr:port
12004 combination. Now that we can have multiple OR connections between
12005 the same ORs, it is no longer possible to use addr:port to uniquely
12006 identify a connection.
12007 - Bridge relays that had DirPort set to 0 would stop fetching
12008 descriptors shortly after startup, and then briefly resume
12009 after a new bandwidth test and/or after publishing a new bridge
12010 descriptor. Bridge users that try to bootstrap from them would
12011 get a recent networkstatus but would get descriptors from up to
12012 18 hours earlier, meaning most of the descriptors were obsolete
12013 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
12014 - Prevent bridge relays from serving their 'extrainfo' document
12015 to anybody who asks, now that extrainfo docs include potentially
12016 sensitive aggregated client geoip summaries. Bugfix on
12018 - If the cached networkstatus consensus is more than five days old,
12019 discard it rather than trying to use it. In theory it could be
12020 useful because it lists alternate directory mirrors, but in practice
12021 it just means we spend many minutes trying directory mirrors that
12022 are long gone from the network. Also discard router descriptors as
12023 we load them if they are more than five days old, since the onion
12024 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
12027 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
12028 could make gcc generate non-functional binary search code. Bugfix
12030 - Build correctly on platforms without socklen_t.
12031 - Compile without warnings on solaris.
12032 - Avoid potential crash on internal error during signature collection.
12033 Fixes bug 864. Patch from rovv.
12034 - Correct handling of possible malformed authority signing key
12035 certificates with internal signature types. Fixes bug 880.
12036 Bugfix on 0.2.0.3-alpha.
12037 - Fix a hard-to-trigger resource leak when logging credential status.
12039 - When we can't initialize DNS because the network is down, do not
12040 automatically stop Tor from starting. Instead, we retry failed
12041 dns_init() every 10 minutes, and change the exit policy to reject
12042 *:* until one succeeds. Fixes bug 691.
12043 - Use 64 bits instead of 32 bits for connection identifiers used with
12044 the controller protocol, to greatly reduce risk of identifier reuse.
12045 - When we're choosing an exit node for a circuit, and we have
12046 no pending streams, choose a good general exit rather than one that
12047 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
12048 - Fix another case of assuming, when a specific exit is requested,
12049 that we know more than the user about what hosts it allows.
12050 Fixes one case of bug 752. Patch from rovv.
12051 - Clip the MaxCircuitDirtiness config option to a minimum of 10
12052 seconds. Warn the user if lower values are given in the
12053 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
12054 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
12055 user if lower values are given in the configuration. Bugfix on
12056 0.1.1.17-rc. Patch by Sebastian.
12057 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
12058 the cache because we already had a v0 descriptor with the same ID.
12059 Bugfix on 0.2.0.18-alpha.
12060 - Fix a race condition when freeing keys shared between main thread
12061 and CPU workers that could result in a memory leak. Bugfix on
12062 0.1.0.1-rc. Fixes bug 889.
12063 - Send a valid END cell back when a client tries to connect to a
12064 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
12065 840. Patch from rovv.
12066 - Check which hops rendezvous stream cells are associated with to
12067 prevent possible guess-the-streamid injection attacks from
12068 intermediate hops. Fixes another case of bug 446. Based on patch
12070 - If a broken client asks a non-exit router to connect somewhere,
12071 do not even do the DNS lookup before rejecting the connection.
12072 Fixes another case of bug 619. Patch from rovv.
12073 - When a relay gets a create cell it can't decrypt (e.g. because it's
12074 using the wrong onion key), we were dropping it and letting the
12075 client time out. Now actually answer with a destroy cell. Fixes
12076 bug 904. Bugfix on 0.0.2pre8.
12078 o Minor bugfixes (hidden services):
12079 - Do not throw away existing introduction points on SIGHUP. Bugfix on
12080 0.0.6pre1. Patch by Karsten. Fixes bug 874.
12083 - Report the case where all signatures in a detached set are rejected
12084 differently than the case where there is an error handling the
12086 - When we realize that another process has modified our cached
12087 descriptors, print out a more useful error message rather than
12088 triggering an assertion. Fixes bug 885. Patch from Karsten.
12089 - Implement the 0x20 hack to better resist DNS poisoning: set the
12090 case on outgoing DNS requests randomly, and reject responses that do
12091 not match the case correctly. This logic can be disabled with the
12092 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
12093 of servers that do not reliably preserve case in replies. See
12094 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
12096 - Check DNS replies for more matching fields to better resist DNS
12098 - Never use OpenSSL compression: it wastes RAM and CPU trying to
12099 compress cells, which are basically all encrypted, compressed, or
12103 Changes in version 0.2.1.11-alpha - 2009-01-20
12104 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
12105 week it will take a long time to bootstrap again" bug. It also fixes
12106 an important security-related bug reported by Ilja van Sprundel. You
12107 should upgrade. (We'll send out more details about the bug once people
12108 have had some time to upgrade.)
12111 - Fix a heap-corruption bug that may be remotely triggerable on
12112 some platforms. Reported by Ilja van Sprundel.
12115 - Discard router descriptors as we load them if they are more than
12116 five days old. Otherwise if Tor is off for a long time and then
12117 starts with cached descriptors, it will try to use the onion
12118 keys in those obsolete descriptors when building circuits. Bugfix
12119 on 0.2.0.x. Fixes bug 887.
12122 - Try to make sure that the version of Libevent we're running with
12123 is binary-compatible with the one we built with. May address bug
12125 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
12126 for bug 905. Bugfix on 0.2.1.7-alpha.
12127 - Add a new --enable-local-appdata configuration switch to change
12128 the default location of the datadir on win32 from APPDATA to
12129 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
12130 entirely. Patch from coderman.
12133 - Make outbound DNS packets respect the OutboundBindAddress setting.
12134 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
12135 - When our circuit fails at the first hop (e.g. we get a destroy
12136 cell back), avoid using that OR connection anymore, and also
12137 tell all the one-hop directory requests waiting for it that they
12138 should fail. Bugfix on 0.2.1.3-alpha.
12139 - In the torify(1) manpage, mention that tsocks will leak your
12143 Changes in version 0.2.1.10-alpha - 2009-01-06
12144 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
12145 would make the bridge relay not so useful if it had DirPort set to 0,
12146 and one that could let an attacker learn a little bit of information
12147 about the bridge's users), and a bug that would cause your Tor relay
12148 to ignore a circuit create request it can't decrypt (rather than reply
12149 with an error). It also fixes a wide variety of other bugs.
12152 - If the cached networkstatus consensus is more than five days old,
12153 discard it rather than trying to use it. In theory it could
12154 be useful because it lists alternate directory mirrors, but in
12155 practice it just means we spend many minutes trying directory
12156 mirrors that are long gone from the network. Helps bug 887 a bit;
12158 - Bridge relays that had DirPort set to 0 would stop fetching
12159 descriptors shortly after startup, and then briefly resume
12160 after a new bandwidth test and/or after publishing a new bridge
12161 descriptor. Bridge users that try to bootstrap from them would
12162 get a recent networkstatus but would get descriptors from up to
12163 18 hours earlier, meaning most of the descriptors were obsolete
12164 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
12165 - Prevent bridge relays from serving their 'extrainfo' document
12166 to anybody who asks, now that extrainfo docs include potentially
12167 sensitive aggregated client geoip summaries. Bugfix on
12171 - New controller event "clients_seen" to report a geoip-based summary
12172 of which countries we've seen clients from recently. Now controllers
12173 like Vidalia can show bridge operators that they're actually making
12175 - Build correctly against versions of OpenSSL 0.9.8 or later built
12176 without support for deprecated functions.
12177 - Update to the "December 19 2008" ip-to-country file.
12179 o Minor bugfixes (on 0.2.0.x):
12180 - Authorities now vote for the Stable flag for any router whose
12181 weighted MTBF is at least 5 days, regardless of the mean MTBF.
12182 - Do not remove routers as too old if we do not have any consensus
12183 document. Bugfix on 0.2.0.7-alpha.
12184 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
12185 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
12186 - When an exit relay resolves a stream address to a local IP address,
12187 do not just keep retrying that same exit relay over and
12188 over. Instead, just close the stream. Addresses bug 872. Bugfix
12189 on 0.2.0.32. Patch from rovv.
12190 - If a hidden service sends us an END cell, do not consider
12191 retrying the connection; just close it. Patch from rovv.
12192 - When we made bridge authorities stop serving bridge descriptors over
12193 unencrypted links, we also broke DirPort reachability testing for
12194 bridges. So bridges with a non-zero DirPort were printing spurious
12195 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
12196 - When a relay gets a create cell it can't decrypt (e.g. because it's
12197 using the wrong onion key), we were dropping it and letting the
12198 client time out. Now actually answer with a destroy cell. Fixes
12199 bug 904. Bugfix on 0.0.2pre8.
12200 - Squeeze 2-5% out of client performance (according to oprofile) by
12201 improving the implementation of some policy-manipulation functions.
12203 o Minor bugfixes (on 0.2.1.x):
12204 - Make get_interface_address() function work properly again; stop
12205 guessing the wrong parts of our address as our address.
12206 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
12207 send on that circuit. Otherwise we might violate the proposal-110
12208 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
12210 - When we're sending non-EXTEND cells to the first hop in a circuit,
12211 for example to use an encrypted directory connection, we don't need
12212 to use RELAY_EARLY cells: the first hop knows what kind of cell
12213 it is, and nobody else can even see the cell type. Conserving
12214 RELAY_EARLY cells makes it easier to cannibalize circuits like
12216 - Stop logging nameserver addresses in reverse order.
12217 - If we are retrying a directory download slowly over and over, do
12218 not automatically give up after the 254th failure. Bugfix on
12220 - Resume reporting accurate "stream end" reasons to the local control
12221 port. They were lost in the changes for Proposal 148. Bugfix on
12224 o Deprecated and removed features:
12225 - The old "tor --version --version" command, which would print out
12226 the subversion "Id" of most of the source files, is now removed. It
12227 turned out to be less useful than we'd expected, and harder to
12230 o Code simplifications and refactoring:
12231 - Change our header file guard macros to be less likely to conflict
12232 with system headers. Adam Langley noticed that we were conflicting
12233 with log.h on Android.
12234 - Tool-assisted documentation cleanup. Nearly every function or
12235 static variable in Tor should have its own documentation now.
12238 Changes in version 0.2.1.9-alpha - 2008-12-25
12239 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
12241 o New directory authorities:
12242 - gabelmoo (the authority run by Karsten Loesing) now has a new
12246 - Never use a connection with a mismatched address to extend a
12247 circuit, unless that connection is canonical. A canonical
12248 connection is one whose address is authenticated by the router's
12249 identity key, either in a NETINFO cell or in a router descriptor.
12250 - Avoid a possible memory corruption bug when receiving hidden service
12251 descriptors. Bugfix on 0.2.1.6-alpha.
12254 - Fix a logic error that would automatically reject all but the first
12255 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
12256 part of bug 813/868. Bug spotted by coderman.
12257 - When a stream at an exit relay is in state "resolving" or
12258 "connecting" and it receives an "end" relay cell, the exit relay
12259 would silently ignore the end cell and not close the stream. If
12260 the client never closes the circuit, then the exit relay never
12261 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
12262 reported by "wood".
12263 - When we can't initialize DNS because the network is down, do not
12264 automatically stop Tor from starting. Instead, retry failed
12265 dns_init() every 10 minutes, and change the exit policy to reject
12266 *:* until one succeeds. Fixes bug 691.
12269 - Give a better error message when an overzealous init script says
12270 "sudo -u username tor --user username". Makes Bug 882 easier for
12272 - When a directory authority gives us a new guess for our IP address,
12273 log which authority we used. Hopefully this will help us debug
12274 the recent complaints about bad IP address guesses.
12275 - Detect svn revision properly when we're using git-svn.
12276 - Try not to open more than one descriptor-downloading connection
12277 to an authority at once. This should reduce load on directory
12278 authorities. Fixes bug 366.
12279 - Add cross-certification to newly generated certificates, so that
12280 a signing key is enough information to look up a certificate.
12281 Partial implementation of proposal 157.
12282 - Start serving certificates by <identity digest, signing key digest>
12283 pairs. Partial implementation of proposal 157.
12284 - Clients now never report any stream end reason except 'MISC'.
12285 Implements proposal 148.
12286 - On platforms with a maximum syslog string length, truncate syslog
12287 messages to that length ourselves, rather than relying on the
12288 system to do it for us.
12289 - Optimize out calls to time(NULL) that occur for every IO operation,
12290 or for every cell. On systems where time() is a slow syscall,
12291 this fix will be slightly helpful.
12292 - Exit servers can now answer resolve requests for ip6.arpa addresses.
12293 - When we download a descriptor that we then immediately (as
12294 a directory authority) reject, do not retry downloading it right
12295 away. Should save some bandwidth on authorities. Fix for bug
12296 888. Patch by Sebastian Hahn.
12297 - When a download gets us zero good descriptors, do not notify
12298 Tor that new directory information has arrived.
12299 - Avoid some nasty corner cases in the logic for marking connections
12300 as too old or obsolete or noncanonical for circuits. Partial
12303 o Minor features (controller):
12304 - New CONSENSUS_ARRIVED event to note when a new consensus has
12305 been fetched and validated.
12306 - When we realize that another process has modified our cached
12307 descriptors file, print out a more useful error message rather
12308 than triggering an assertion. Fixes bug 885. Patch from Karsten.
12309 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
12310 controllers to prevent SIGHUP from reloading the
12311 configuration. Fixes bug 856.
12314 - Resume using the correct "REASON=" stream when telling the
12315 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
12316 - When a canonical connection appears later in our internal list
12317 than a noncanonical one for a given OR ID, always use the
12318 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
12320 - Clip the MaxCircuitDirtiness config option to a minimum of 10
12321 seconds. Warn the user if lower values are given in the
12322 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
12323 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
12324 user if lower values are given in the configuration. Bugfix on
12325 0.1.1.17-rc. Patch by Sebastian.
12326 - Fix a race condition when freeing keys shared between main thread
12327 and CPU workers that could result in a memory leak. Bugfix on
12328 0.1.0.1-rc. Fixes bug 889.
12330 o Minor bugfixes (hidden services):
12331 - Do not throw away existing introduction points on SIGHUP (bugfix on
12332 0.0.6pre1); also, do not stall hidden services because we're
12333 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
12334 by John Brooks. Patch by Karsten. Fixes bug 874.
12335 - Fix a memory leak when we decline to add a v2 rendezvous
12336 descriptor to the cache because we already had a v0 descriptor
12337 with the same ID. Bugfix on 0.2.0.18-alpha.
12339 o Deprecated and removed features:
12340 - RedirectExits has been removed. It was deprecated since
12342 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
12343 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
12344 - Cell pools are now always enabled; --disable-cell-pools is ignored.
12346 o Code simplifications and refactoring:
12347 - Rename the confusing or_is_obsolete field to the more appropriate
12348 is_bad_for_new_circs, and move it to or_connection_t where it
12350 - Move edge-only flags from connection_t to edge_connection_t: not
12351 only is this better coding, but on machines of plausible alignment,
12352 it should save 4-8 bytes per connection_t. "Every little bit helps."
12353 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
12354 for consistency; keep old option working for backward compatibility.
12355 - Simplify the code for finding connections to use for a circuit.
12358 Changes in version 0.2.1.8-alpha - 2008-12-08
12359 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
12360 builds better on unusual platforms like Solaris and old OS X, and
12361 fixes a variety of other issues.
12364 - New DirPortFrontPage option that takes an html file and publishes
12365 it as "/" on the DirPort. Now relay operators can provide a
12366 disclaimer without needing to set up a separate webserver. There's
12367 a sample disclaimer in contrib/tor-exit-notice.html.
12370 - When the client is choosing entry guards, now it selects at most
12371 one guard from a given relay family. Otherwise we could end up with
12372 all of our entry points into the network run by the same operator.
12373 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
12376 - Fix a DOS opportunity during the voting signature collection process
12377 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
12378 - Fix a possible segfault when establishing an exit connection. Bugfix
12382 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
12384 - Made Tor a little less aggressive about deleting expired
12385 certificates. Partial fix for bug 854.
12386 - Stop doing unaligned memory access that generated bus errors on
12387 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
12388 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
12389 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
12390 - Make USR2 log-level switch take effect immediately. Bugfix on
12392 - If one win32 nameserver fails to get added, continue adding the
12393 rest, and don't automatically fail.
12394 - Use fcntl() for locking when flock() is not available. Should fix
12395 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
12396 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
12397 could make gcc generate non-functional binary search code. Bugfix
12399 - Build correctly on platforms without socklen_t.
12400 - Avoid potential crash on internal error during signature collection.
12401 Fixes bug 864. Patch from rovv.
12402 - Do not use C's stdio library for writing to log files. This will
12403 improve logging performance by a minute amount, and will stop
12404 leaking fds when our disk is full. Fixes bug 861.
12405 - Stop erroneous use of O_APPEND in cases where we did not in fact
12406 want to re-seek to the end of a file before every last write().
12407 - Correct handling of possible malformed authority signing key
12408 certificates with internal signature types. Fixes bug 880. Bugfix
12410 - Fix a hard-to-trigger resource leak when logging credential status.
12414 - Directory mirrors no longer fetch the v1 directory or
12415 running-routers files. They are obsolete, and nobody asks for them
12416 anymore. This is the first step to making v1 authorities obsolete.
12418 o Minor features (controller):
12419 - Return circuit purposes in response to GETINFO circuit-status. Fixes
12423 Changes in version 0.2.0.32 - 2008-11-20
12424 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
12425 packages (and maybe other packages) noticed by Theo de Raadt, fixes
12426 a smaller security flaw that might allow an attacker to access local
12427 services, further improves hidden service performance, and fixes a
12428 variety of other issues.
12431 - The "User" and "Group" config options did not clear the
12432 supplementary group entries for the Tor process. The "User" option
12433 is now more robust, and we now set the groups to the specified
12434 user's primary group. The "Group" option is now ignored. For more
12435 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
12436 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
12437 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
12438 - The "ClientDNSRejectInternalAddresses" config option wasn't being
12439 consistently obeyed: if an exit relay refuses a stream because its
12440 exit policy doesn't allow it, we would remember what IP address
12441 the relay said the destination address resolves to, even if it's
12442 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
12445 - Fix a DOS opportunity during the voting signature collection process
12446 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
12448 o Major bugfixes (hidden services):
12449 - When fetching v0 and v2 rendezvous service descriptors in parallel,
12450 we were failing the whole hidden service request when the v0
12451 descriptor fetch fails, even if the v2 fetch is still pending and
12452 might succeed. Similarly, if the last v2 fetch fails, we were
12453 failing the whole hidden service request even if a v0 fetch is
12454 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
12455 - When extending a circuit to a hidden service directory to upload a
12456 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
12457 requests failed, because the router descriptor has not been
12458 downloaded yet. In these cases, do not attempt to upload the
12459 rendezvous descriptor, but wait until the router descriptor is
12460 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
12461 descriptor from a hidden service directory for which the router
12462 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
12466 - Fix several infrequent memory leaks spotted by Coverity.
12467 - When testing for libevent functions, set the LDFLAGS variable
12468 correctly. Found by Riastradh.
12469 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
12470 bootstrapping with tunneled directory connections. Bugfix on
12471 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
12472 - When asked to connect to A.B.exit:80, if we don't know the IP for A
12473 and we know that server B rejects most-but-not all connections to
12474 port 80, we would previously reject the connection. Now, we assume
12475 the user knows what they were asking for. Fixes bug 752. Bugfix
12476 on 0.0.9rc5. Diagnosed by BarkerJr.
12477 - If we overrun our per-second write limits a little, count this as
12478 having used up our write allocation for the second, and choke
12479 outgoing directory writes. Previously, we had only counted this when
12480 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
12481 Bugfix on 0.2.0.x (??).
12482 - Remove the old v2 directory authority 'lefkada' from the default
12483 list. It has been gone for many months.
12484 - Stop doing unaligned memory access that generated bus errors on
12485 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
12486 - Make USR2 log-level switch take effect immediately. Bugfix on
12489 o Minor bugfixes (controller):
12490 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
12491 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
12494 Changes in version 0.2.1.7-alpha - 2008-11-08
12495 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
12496 packages (and maybe other packages) noticed by Theo de Raadt, fixes
12497 a smaller security flaw that might allow an attacker to access local
12498 services, adds better defense against DNS poisoning attacks on exit
12499 relays, further improves hidden service performance, and fixes a
12500 variety of other issues.
12503 - The "ClientDNSRejectInternalAddresses" config option wasn't being
12504 consistently obeyed: if an exit relay refuses a stream because its
12505 exit policy doesn't allow it, we would remember what IP address
12506 the relay said the destination address resolves to, even if it's
12507 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
12508 - The "User" and "Group" config options did not clear the
12509 supplementary group entries for the Tor process. The "User" option
12510 is now more robust, and we now set the groups to the specified
12511 user's primary group. The "Group" option is now ignored. For more
12512 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
12513 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
12514 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
12515 - Do not use or believe expired v3 authority certificates. Patch
12516 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
12519 - Now NodeFamily and MyFamily config options allow spaces in
12520 identity fingerprints, so it's easier to paste them in.
12521 Suggested by Lucky Green.
12522 - Implement the 0x20 hack to better resist DNS poisoning: set the
12523 case on outgoing DNS requests randomly, and reject responses that do
12524 not match the case correctly. This logic can be disabled with the
12525 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
12526 of servers that do not reliably preserve case in replies. See
12527 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
12529 - Preserve case in replies to DNSPort requests in order to support
12530 the 0x20 hack for resisting DNS poisoning attacks.
12532 o Hidden service performance improvements:
12533 - When the client launches an introduction circuit, retry with a
12534 new circuit after 30 seconds rather than 60 seconds.
12535 - Launch a second client-side introduction circuit in parallel
12536 after a delay of 15 seconds (based on work by Christian Wilms).
12537 - Hidden services start out building five intro circuits rather
12538 than three, and when the first three finish they publish a service
12539 descriptor using those. Now we publish our service descriptor much
12540 faster after restart.
12543 - Minor fix in the warning messages when you're having problems
12544 bootstrapping; also, be more forgiving of bootstrap problems when
12545 we're still making incremental progress on a given bootstrap phase.
12546 - When we're choosing an exit node for a circuit, and we have
12547 no pending streams, choose a good general exit rather than one that
12548 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
12549 - Send a valid END cell back when a client tries to connect to a
12550 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
12551 840. Patch from rovv.
12552 - If a broken client asks a non-exit router to connect somewhere,
12553 do not even do the DNS lookup before rejecting the connection.
12554 Fixes another case of bug 619. Patch from rovv.
12555 - Fix another case of assuming, when a specific exit is requested,
12556 that we know more than the user about what hosts it allows.
12557 Fixes another case of bug 752. Patch from rovv.
12558 - Check which hops rendezvous stream cells are associated with to
12559 prevent possible guess-the-streamid injection attacks from
12560 intermediate hops. Fixes another case of bug 446. Based on patch
12562 - Avoid using a negative right-shift when comparing 32-bit
12563 addresses. Possible fix for bug 845 and bug 811.
12564 - Make the assert_circuit_ok() function work correctly on circuits that
12565 have already been marked for close.
12566 - Fix read-off-the-end-of-string error in unit tests when decoding
12567 introduction points.
12568 - Fix uninitialized size field for memory area allocation: may improve
12569 memory performance during directory parsing.
12570 - Treat duplicate certificate fetches as failures, so that we do
12571 not try to re-fetch an expired certificate over and over and over.
12572 - Do not say we're fetching a certificate when we'll in fact skip it
12573 because of a pending download.
12576 Changes in version 0.2.1.6-alpha - 2008-09-30
12577 Tor 0.2.1.6-alpha further improves performance and robustness of
12578 hidden services, starts work on supporting per-country relay selection,
12579 and fixes a variety of smaller issues.
12582 - Implement proposal 121: make it possible to build hidden services
12583 that only certain clients are allowed to connect to. This is
12584 enforced at several points, so that unauthorized clients are unable
12585 to send INTRODUCE cells to the service, or even (depending on the
12586 type of authentication) to learn introduction points. This feature
12587 raises the bar for certain kinds of active attacks against hidden
12588 services. Code by Karsten Loesing.
12589 - Relays now store and serve v2 hidden service descriptors by default,
12590 i.e., the new default value for HidServDirectoryV2 is 1. This is
12591 the last step in proposal 114, which aims to make hidden service
12592 lookups more reliable.
12593 - Start work to allow node restrictions to include country codes. The
12594 syntax to exclude nodes in a country with country code XX is
12595 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
12596 refinement to decide what config options should take priority if
12597 you ask to both use a particular node and exclude it.
12598 - Allow ExitNodes list to include IP ranges and country codes, just
12599 like the Exclude*Nodes lists. Patch from Robert Hogan.
12602 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
12603 Tor to fail to start if you had it configured to use a bridge
12604 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
12605 - When extending a circuit to a hidden service directory to upload a
12606 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
12607 requests failed, because the router descriptor had not been
12608 downloaded yet. In these cases, we now wait until the router
12609 descriptor is downloaded, and then retry. Likewise, clients
12610 now skip over a hidden service directory if they don't yet have
12611 its router descriptor, rather than futilely requesting it and
12612 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
12614 - When fetching v0 and v2 rendezvous service descriptors in parallel,
12615 we were failing the whole hidden service request when the v0
12616 descriptor fetch fails, even if the v2 fetch is still pending and
12617 might succeed. Similarly, if the last v2 fetch fails, we were
12618 failing the whole hidden service request even if a v0 fetch is
12619 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
12620 - DNS replies need to have names matching their requests, but
12621 these names should be in the questions section, not necessarily
12622 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
12625 - Update to the "September 1 2008" ip-to-country file.
12626 - Allow ports 465 and 587 in the default exit policy again. We had
12627 rejected them in 0.1.0.15, because back in 2005 they were commonly
12628 misconfigured and ended up as spam targets. We hear they are better
12629 locked down these days.
12630 - Use a lockfile to make sure that two Tor processes are not
12631 simultaneously running with the same datadir.
12632 - Serve the latest v3 networkstatus consensus via the control
12633 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
12634 - Better logging about stability/reliability calculations on directory
12636 - Drop the requirement to have an open dir port for storing and
12637 serving v2 hidden service descriptors.
12638 - Directory authorities now serve a /tor/dbg-stability.txt URL to
12639 help debug WFU and MTBF calculations.
12640 - Implement most of Proposal 152: allow specialized servers to permit
12641 single-hop circuits, and clients to use those servers to build
12642 single-hop circuits when using a specialized controller. Patch
12643 from Josh Albrecht. Resolves feature request 768.
12644 - Add a -p option to tor-resolve for specifying the SOCKS port: some
12645 people find host:port too confusing.
12646 - Make TrackHostExit mappings expire a while after their last use, not
12647 after their creation. Patch from Robert Hogan.
12648 - Provide circuit purposes along with circuit events to the controller.
12651 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
12653 - Fixed some memory leaks -- some quite frequent, some almost
12654 impossible to trigger -- based on results from Coverity.
12655 - When testing for libevent functions, set the LDFLAGS variable
12656 correctly. Found by Riastradh.
12657 - Fix an assertion bug in parsing policy-related options; possible fix
12659 - Catch and report a few more bootstrapping failure cases when Tor
12660 fails to establish a TCP connection. Cleanup on 0.2.1.x.
12661 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
12662 bootstrapping with tunneled directory connections. Bugfix on
12663 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
12664 - When asked to connect to A.B.exit:80, if we don't know the IP for A
12665 and we know that server B rejects most-but-not all connections to
12666 port 80, we would previously reject the connection. Now, we assume
12667 the user knows what they were asking for. Fixes bug 752. Bugfix
12668 on 0.0.9rc5. Diagnosed by BarkerJr.
12669 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
12670 service directories if they have no advertised dir port. Bugfix
12672 - If we overrun our per-second write limits a little, count this as
12673 having used up our write allocation for the second, and choke
12674 outgoing directory writes. Previously, we had only counted this when
12675 we had met our limits precisely. Fixes bug 824. Patch by rovv.
12676 Bugfix on 0.2.0.x (??).
12677 - Avoid a "0 divided by 0" calculation when calculating router uptime
12678 at directory authorities. Bugfix on 0.2.0.8-alpha.
12679 - Make DNS resolved controller events into "CLOSED", not
12680 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
12682 - Fix a bug where an unreachable relay would establish enough
12683 reachability testing circuits to do a bandwidth test -- if
12684 we already have a connection to the middle hop of the testing
12685 circuit, then it could establish the last hop by using the existing
12686 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
12687 circuits no longer use entry guards in 0.2.1.3-alpha.
12688 - If we have correct permissions on $datadir, we complain to stdout
12689 and fail to start. But dangerous permissions on
12690 $datadir/cached-status/ would cause us to open a log and complain
12691 there. Now complain to stdout and fail to start in both cases. Fixes
12692 bug 820, reported by seeess.
12693 - Remove the old v2 directory authority 'lefkada' from the default
12694 list. It has been gone for many months.
12696 o Code simplifications and refactoring:
12697 - Revise the connection_new functions so that a more typesafe variant
12698 exists. This will work better with Coverity, and let us find any
12699 actual mistakes we're making here.
12700 - Refactor unit testing logic so that dmalloc can be used sensibly
12701 with unit tests to check for memory leaks.
12702 - Move all hidden-service related fields from connection and circuit
12703 structure to substructures: this way they won't eat so much memory.
12706 Changes in version 0.2.0.31 - 2008-09-03
12707 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
12708 a big bug we're seeing where in rare cases traffic from one Tor stream
12709 gets mixed into another stream, and fixes a variety of smaller issues.
12712 - Make sure that two circuits can never exist on the same connection
12713 with the same circuit ID, even if one is marked for close. This
12714 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
12715 - Relays now reject risky extend cells: if the extend cell includes
12716 a digest of all zeroes, or asks to extend back to the relay that
12717 sent the extend cell, tear down the circuit. Ideas suggested
12719 - If not enough of our entry guards are available so we add a new
12720 one, we might use the new one even if it overlapped with the
12721 current circuit's exit relay (or its family). Anonymity bugfix
12722 pointed out by rovv.
12725 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
12726 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
12727 - Correctly detect the presence of the linux/netfilter_ipv4.h header
12728 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
12729 - Pick size of default geoip filename string correctly on windows.
12730 Fixes bug 806. Bugfix on 0.2.0.30.
12731 - Make the autoconf script accept the obsolete --with-ssl-dir
12732 option as an alias for the actually-working --with-openssl-dir
12733 option. Fix the help documentation to recommend --with-openssl-dir.
12734 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
12735 - When using the TransPort option on OpenBSD, and using the User
12736 option to change UID and drop privileges, make sure to open
12737 /dev/pf before dropping privileges. Fixes bug 782. Patch from
12738 Christopher Davis. Bugfix on 0.1.2.1-alpha.
12739 - Try to attach connections immediately upon receiving a RENDEZVOUS2
12740 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
12741 on the client side when connecting to a hidden service. Bugfix
12742 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
12743 - When closing an application-side connection because its circuit is
12744 getting torn down, generate the stream event correctly. Bugfix on
12745 0.1.2.x. Anonymous patch.
12748 Changes in version 0.2.1.5-alpha - 2008-08-31
12749 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
12750 in a lot of the infrastructure for adding authorization to hidden
12751 services, lays the groundwork for having clients read their load
12752 balancing information out of the networkstatus consensus rather than
12753 the individual router descriptors, addresses two potential anonymity
12754 issues, and fixes a variety of smaller issues.
12757 - Convert many internal address representations to optionally hold
12759 - Generate and accept IPv6 addresses in many protocol elements.
12760 - Make resolver code handle nameservers located at ipv6 addresses.
12761 - Begin implementation of proposal 121 ("Client authorization for
12762 hidden services"): configure hidden services with client
12763 authorization, publish descriptors for them, and configure
12764 authorization data for hidden services at clients. The next
12765 step is to actually access hidden services that perform client
12767 - More progress toward proposal 141: Network status consensus
12768 documents and votes now contain bandwidth information for each
12769 router and a summary of that router's exit policy. Eventually this
12770 will be used by clients so that they do not have to download every
12771 known descriptor before building circuits.
12773 o Major bugfixes (on 0.2.0.x and before):
12774 - When sending CREATED cells back for a given circuit, use a 64-bit
12775 connection ID to find the right connection, rather than an addr:port
12776 combination. Now that we can have multiple OR connections between
12777 the same ORs, it is no longer possible to use addr:port to uniquely
12778 identify a connection.
12779 - Relays now reject risky extend cells: if the extend cell includes
12780 a digest of all zeroes, or asks to extend back to the relay that
12781 sent the extend cell, tear down the circuit. Ideas suggested
12783 - If not enough of our entry guards are available so we add a new
12784 one, we might use the new one even if it overlapped with the
12785 current circuit's exit relay (or its family). Anonymity bugfix
12786 pointed out by rovv.
12789 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
12790 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
12791 - When using the TransPort option on OpenBSD, and using the User
12792 option to change UID and drop privileges, make sure to open /dev/pf
12793 before dropping privileges. Fixes bug 782. Patch from Christopher
12794 Davis. Bugfix on 0.1.2.1-alpha.
12795 - Correctly detect the presence of the linux/netfilter_ipv4.h header
12796 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
12797 - Add a missing safe_str() call for a debug log message.
12798 - Use 64 bits instead of 32 bits for connection identifiers used with
12799 the controller protocol, to greatly reduce risk of identifier reuse.
12800 - Make the autoconf script accept the obsolete --with-ssl-dir
12801 option as an alias for the actually-working --with-openssl-dir
12802 option. Fix the help documentation to recommend --with-openssl-dir.
12803 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
12806 - Rate-limit too-many-sockets messages: when they happen, they happen
12807 a lot. Resolves bug 748.
12808 - Resist DNS poisoning a little better by making sure that names in
12809 answer sections match.
12810 - Print the SOCKS5 error message string as well as the error code
12811 when a tor-resolve request fails. Patch from Jacob.
12814 Changes in version 0.2.1.4-alpha - 2008-08-04
12815 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
12818 - The address part of exit policies was not correctly written
12819 to router descriptors. This generated router descriptors that failed
12820 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
12822 - Tor triggered a false assert when extending a circuit to a relay
12823 but we already have a connection open to that relay. Noticed by
12824 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
12827 - Fix a hidden service logging bug: in some edge cases, the router
12828 descriptor of a previously picked introduction point becomes
12829 obsolete and we need to give up on it rather than continually
12830 complaining that it has become obsolete. Observed by xiando. Bugfix
12833 o Removed features:
12834 - Take out the TestVia config option, since it was a workaround for
12835 a bug that was fixed in Tor 0.1.1.21.
12838 Changes in version 0.2.1.3-alpha - 2008-08-03
12839 Tor 0.2.1.3-alpha implements most of the pieces to prevent
12840 infinite-length circuit attacks (see proposal 110); fixes a bug that
12841 might cause exit relays to corrupt streams they send back; allows
12842 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
12843 ExcludeExitNodes config options; and fixes a big pile of bugs.
12845 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
12846 - Send a bootstrap problem "warn" event on the first problem if the
12847 reason is NO_ROUTE (that is, our network is down).
12850 - Implement most of proposal 110: The first K cells to be sent
12851 along a circuit are marked as special "early" cells; only K "early"
12852 cells will be allowed. Once this code is universal, we can block
12853 certain kinds of DOS attack by requiring that EXTEND commands must
12854 be sent using an "early" cell.
12857 - Try to attach connections immediately upon receiving a RENDEZVOUS2
12858 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
12859 on the client side when connecting to a hidden service. Bugfix
12860 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
12861 - Ensure that two circuits can never exist on the same connection
12862 with the same circuit ID, even if one is marked for close. This
12863 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
12866 - When relays do their initial bandwidth measurement, don't limit
12867 to just our entry guards for the test circuits. Otherwise we tend
12868 to have multiple test circuits going through a single entry guard,
12869 which makes our bandwidth test less accurate. Fixes part of bug 654;
12870 patch contributed by Josh Albrecht.
12871 - Add an ExcludeExitNodes option so users can list a set of nodes
12872 that should be be excluded from the exit node position, but
12873 allowed elsewhere. Implements proposal 151.
12874 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
12875 ExcludeNodes and ExcludeExitNodes lists.
12876 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
12877 be more efficient. Formerly it was quadratic in the number of
12878 servers; now it should be linear. Fixes bug 509.
12879 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
12880 and n_conn_id_digest fields into a separate structure that's
12881 only needed when the circuit has not yet attached to an n_conn.
12884 - Change the contrib/tor.logrotate script so it makes the new
12885 logs as "_tor:_tor" rather than the default, which is generally
12886 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
12887 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
12888 warnings (occasionally), but it can also cause the compiler to
12889 eliminate error-checking code. Suggested by Peter Gutmann.
12890 - When a hidden service is giving up on an introduction point candidate
12891 that was not included in the last published rendezvous descriptor,
12892 don't reschedule publication of the next descriptor. Fixes bug 763.
12894 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
12895 HiddenServiceExcludeNodes as obsolete: they never worked properly,
12896 and nobody claims to be using them. Fixes bug 754. Bugfix on
12897 0.1.0.1-rc. Patch from Christian Wilms.
12898 - Fix a small alignment and memory-wasting bug on buffer chunks.
12901 o Minor bugfixes (controller):
12902 - When closing an application-side connection because its circuit
12903 is getting torn down, generate the stream event correctly.
12904 Bugfix on 0.1.2.x. Anonymous patch.
12906 o Removed features:
12907 - Remove all backward-compatibility code to support relays running
12908 versions of Tor so old that they no longer work at all on the
12912 Changes in version 0.2.0.30 - 2008-07-15
12914 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
12915 warnings (occasionally), but it can also cause the compiler to
12916 eliminate error-checking code. Suggested by Peter Gutmann.
12919 Changes in version 0.2.0.29-rc - 2008-07-08
12920 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
12921 hidden-service performance bugs, and fixes a bunch of smaller bugs.
12924 - If you have more than one bridge but don't know their keys,
12925 you would only launch a request for the descriptor of the first one
12926 on your list. (Tor considered launching requests for the others, but
12927 found that it already had a connection on the way for $0000...0000
12928 so it didn't open another.) Bugfix on 0.2.0.x.
12929 - If you have more than one bridge but don't know their keys, and the
12930 connection to one of the bridges failed, you would cancel all
12931 pending bridge connections. (After all, they all have the same
12932 digest.) Bugfix on 0.2.0.x.
12933 - When a hidden service was trying to establish an introduction point,
12934 and Tor had built circuits preemptively for such purposes, we
12935 were ignoring all the preemptive circuits and launching a new one
12936 instead. Bugfix on 0.2.0.14-alpha.
12937 - When a hidden service was trying to establish an introduction point,
12938 and Tor *did* manage to reuse one of the preemptively built
12939 circuits, it didn't correctly remember which one it used,
12940 so it asked for another one soon after, until there were no
12941 more preemptive circuits, at which point it launched one from
12942 scratch. Bugfix on 0.0.9.x.
12943 - Make directory servers include the X-Your-Address-Is: http header in
12944 their responses even for begin_dir conns. Now clients who only
12945 ever use begin_dir connections still have a way to learn their IP
12946 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
12949 - Fix a macro/CPP interaction that was confusing some compilers:
12950 some GCCs don't like #if/#endif pairs inside macro arguments.
12952 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
12953 Fixes bug 704; fix from Steven Murdoch.
12954 - When opening /dev/null in finish_daemonize(), do not pass the
12955 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
12956 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
12957 - Correctly detect transparent proxy support on Linux hosts that
12958 require in.h to be included before netfilter_ipv4.h. Patch
12960 - Disallow session resumption attempts during the renegotiation
12961 stage of the v2 handshake protocol. Clients should never be trying
12962 session resumption at this point, but apparently some did, in
12963 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
12964 found by Geoff Goodell.
12967 Changes in version 0.2.1.2-alpha - 2008-06-20
12968 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
12969 make it easier to set up your own private Tor network; fixes several
12970 big bugs with using more than one bridge relay; fixes a big bug with
12971 offering hidden services quickly after Tor starts; and uses a better
12972 API for reporting potential bootstrapping problems to the controller.
12975 - New TestingTorNetwork config option to allow adjustment of
12976 previously constant values that, while reasonable, could slow
12977 bootstrapping. Implements proposal 135. Patch from Karsten.
12980 - If you have more than one bridge but don't know their digests,
12981 you would only learn a request for the descriptor of the first one
12982 on your list. (Tor considered launching requests for the others, but
12983 found that it already had a connection on the way for $0000...0000
12984 so it didn't open another.) Bugfix on 0.2.0.x.
12985 - If you have more than one bridge but don't know their digests,
12986 and the connection to one of the bridges failed, you would cancel
12987 all pending bridge connections. (After all, they all have the
12988 same digest.) Bugfix on 0.2.0.x.
12989 - When establishing a hidden service, introduction points that
12990 originate from cannibalized circuits are completely ignored and not
12991 included in rendezvous service descriptors. This might be another
12992 reason for delay in making a hidden service available. Bugfix
12993 from long ago (0.0.9.x?)
12996 - Allow OpenSSL to use dynamic locks if it wants.
12997 - When building a consensus, do not include routers that are down.
12998 This will cut down 30% to 40% on consensus size. Implements
13000 - In directory authorities' approved-routers files, allow
13001 fingerprints with or without space.
13002 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
13003 controller can query our current bootstrap state in case it attaches
13004 partway through and wants to catch up.
13005 - Send an initial "Starting" bootstrap status event, so we have a
13006 state to start out in.
13009 - Asking for a conditional consensus at .../consensus/<fingerprints>
13010 would crash a dirserver if it did not already have a
13011 consensus. Bugfix on 0.2.1.1-alpha.
13012 - Clean up some macro/CPP interactions: some GCC versions don't like
13013 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
13016 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
13017 - Directory authorities shouldn't complain about bootstrapping
13018 problems just because they do a lot of reachability testing and
13019 some of the connection attempts fail.
13020 - Start sending "count" and "recommendation" key/value pairs in
13021 bootstrap problem status events, so the controller can hear about
13022 problems even before Tor decides they're worth reporting for sure.
13023 - If you're using bridges, generate "bootstrap problem" warnings
13024 as soon as you run out of working bridges, rather than waiting
13025 for ten failures -- which will never happen if you have less than
13027 - If we close our OR connection because there's been a circuit
13028 pending on it for too long, we were telling our bootstrap status
13029 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
13032 Changes in version 0.2.1.1-alpha - 2008-06-13
13033 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
13034 were making the Tor process bloat especially on Linux; makes our TLS
13035 handshake blend in better; sends "bootstrap phase" status events to
13036 the controller, so it can keep the user informed of progress (and
13037 problems) fetching directory information and establishing circuits;
13038 and adds a variety of smaller features.
13041 - More work on making our TLS handshake blend in: modify the list
13042 of ciphers advertised by OpenSSL in client mode to even more
13043 closely resemble a common web browser. We cheat a little so that
13044 we can advertise ciphers that the locally installed OpenSSL doesn't
13046 - Start sending "bootstrap phase" status events to the controller,
13047 so it can keep the user informed of progress fetching directory
13048 information and establishing circuits. Also inform the controller
13049 if we think we're stuck at a particular bootstrap phase. Implements
13051 - Resume using OpenSSL's RAND_poll() for better (and more portable)
13052 cross-platform entropy collection again. We used to use it, then
13053 stopped using it because of a bug that could crash systems that
13054 called RAND_poll when they had a lot of fds open. It looks like the
13055 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
13056 at startup, and to call RAND_poll() when we reseed later only if
13057 we have a non-buggy OpenSSL version.
13060 - When we choose to abandon a new entry guard because we think our
13061 older ones might be better, close any circuits pending on that
13062 new entry guard connection. This fix should make us recover much
13063 faster when our network is down and then comes back. Bugfix on
13064 0.1.2.8-beta; found by lodger.
13066 o Memory fixes and improvements:
13067 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
13068 to avoid unused RAM in buffer chunks and memory pools.
13069 - Speed up parsing and cut down on memory fragmentation by using
13070 stack-style allocations for parsing directory objects. Previously,
13071 this accounted for over 40% of allocations from within Tor's code
13072 on a typical directory cache.
13073 - Use a Bloom filter rather than a digest-based set to track which
13074 descriptors we need to keep around when we're cleaning out old
13075 router descriptors. This speeds up the computation significantly,
13076 and may reduce fragmentation.
13077 - Reduce the default smartlist size from 32 to 16; it turns out that
13078 most smartlists hold around 8-12 elements tops.
13079 - Make dumpstats() log the fullness and size of openssl-internal
13081 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
13082 patch to their OpenSSL, turn it on to save memory on servers. This
13083 patch will (with any luck) get included in a mainline distribution
13085 - Never use OpenSSL compression: it wastes RAM and CPU trying to
13086 compress cells, which are basically all encrypted, compressed,
13090 - Stop reloading the router list from disk for no reason when we
13091 run out of reachable directory mirrors. Once upon a time reloading
13092 it would set the 'is_running' flag back to 1 for them. It hasn't
13093 done that for a long time.
13094 - In very rare situations new hidden service descriptors were
13095 published earlier than 30 seconds after the last change to the
13096 service. (We currently think that a hidden service descriptor
13097 that's been stable for 30 seconds is worth publishing.)
13100 - Allow separate log levels to be configured for different logging
13101 domains. For example, this allows one to log all notices, warnings,
13102 or errors, plus all memory management messages of level debug or
13103 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
13104 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
13105 and stop using a warning that had become unfixably verbose under
13107 - New --hush command-line option similar to --quiet. While --quiet
13108 disables all logging to the console on startup, --hush limits the
13109 output to messages of warning and error severity.
13110 - Servers support a new URL scheme for consensus downloads that
13111 allows the client to specify which authorities are trusted.
13112 The server then only sends the consensus if the client will trust
13113 it. Otherwise a 404 error is sent back. Clients use this
13114 new scheme when the server supports it (meaning it's running
13115 0.2.1.1-alpha or later). Implements proposal 134.
13116 - New configure/torrc options (--enable-geoip-stats,
13117 DirRecordUsageByCountry) to record how many IPs we've served
13118 directory info to in each country code, how many status documents
13119 total we've sent to each country code, and what share of the total
13120 directory requests we should expect to see.
13121 - Use the TLS1 hostname extension to more closely resemble browser
13123 - Lots of new unit tests.
13124 - Add a macro to implement the common pattern of iterating through
13125 two parallel lists in lockstep.
13128 Changes in version 0.2.0.28-rc - 2008-06-13
13129 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
13130 performance bug, and fixes a bunch of smaller bugs.
13133 - Fix a bug where, when we were choosing the 'end stream reason' to
13134 put in our relay end cell that we send to the exit relay, Tor
13135 clients on Windows were sometimes sending the wrong 'reason'. The
13136 anonymity problem is that exit relays may be able to guess whether
13137 the client is running Windows, thus helping partition the anonymity
13138 set. Down the road we should stop sending reasons to exit relays,
13139 or otherwise prevent future versions of this bug.
13142 - While setting up a hidden service, some valid introduction circuits
13143 were overlooked and abandoned. This might be the reason for
13144 the long delay in making a hidden service available. Bugfix on
13148 - Update to the "June 9 2008" ip-to-country file.
13149 - Run 'make test' as part of 'make dist', so we stop releasing so
13150 many development snapshots that fail their unit tests.
13153 - When we're checking if we have enough dir info for each relay
13154 to begin establishing circuits, make sure that we actually have
13155 the descriptor listed in the consensus, not just any descriptor.
13157 - Bridge relays no longer print "xx=0" in their extrainfo document
13158 for every single country code in the geoip db. Bugfix on
13160 - Only warn when we fail to load the geoip file if we were planning to
13161 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
13162 - If we change our MaxAdvertisedBandwidth and then reload torrc,
13163 Tor won't realize it should publish a new relay descriptor. Fixes
13164 bug 688, reported by mfr. Bugfix on 0.1.2.x.
13165 - When we haven't had any application requests lately, don't bother
13166 logging that we have expired a bunch of descriptors. Bugfix
13168 - Make relay cells written on a connection count as non-padding when
13169 tracking how long a connection has been in use. Bugfix on
13170 0.2.0.1-alpha. Spotted by lodger.
13171 - Fix unit tests in 0.2.0.27-rc.
13172 - Fix compile on Windows.
13175 Changes in version 0.2.0.27-rc - 2008-06-03
13176 Tor 0.2.0.27-rc adds a few features we left out of the earlier
13177 release candidates. In particular, we now include an IP-to-country
13178 GeoIP database, so controllers can easily look up what country a
13179 given relay is in, and so bridge relays can give us some sanitized
13180 summaries about which countries are making use of bridges. (See proposal
13181 126-geoip-fetching.txt for details.)
13184 - Include an IP-to-country GeoIP file in the tarball, so bridge
13185 relays can report sanitized summaries of the usage they're seeing.
13188 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
13189 Robert Hogan. Fixes the first part of bug 681.
13190 - Make bridge authorities never serve extrainfo docs.
13191 - Add support to detect Libevent versions in the 1.4.x series
13193 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
13194 - Include a new contrib/tor-exit-notice.html file that exit relay
13195 operators can put on their website to help reduce abuse queries.
13198 - When tunneling an encrypted directory connection, and its first
13199 circuit fails, do not leave it unattached and ask the controller
13200 to deal. Fixes the second part of bug 681.
13201 - Make bridge authorities correctly expire old extrainfo documents
13205 Changes in version 0.2.0.26-rc - 2008-05-13
13206 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
13207 in Debian's OpenSSL packages. All users running any 0.2.0.x version
13208 should upgrade, whether they're running Debian or not.
13210 o Major security fixes:
13211 - Use new V3 directory authority keys on the tor26, gabelmoo, and
13212 moria1 V3 directory authorities. The old keys were generated with
13213 a vulnerable version of Debian's OpenSSL package, and must be
13214 considered compromised. Other authorities' keys were not generated
13215 with an affected version of OpenSSL.
13218 - List authority signatures as "unrecognized" based on DirServer
13219 lines, not on cert cache. Bugfix on 0.2.0.x.
13222 - Add a new V3AuthUseLegacyKey option to make it easier for
13223 authorities to change their identity keys if they have to.
13226 Changes in version 0.2.0.25-rc - 2008-04-23
13227 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
13230 - Remember to initialize threading before initializing logging.
13231 Otherwise, many BSD-family implementations will crash hard on
13232 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
13235 - Authorities correctly free policies on bad servers on
13236 exit. Fixes bug 672. Bugfix on 0.2.0.x.
13239 Changes in version 0.2.0.24-rc - 2008-04-22
13240 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
13241 v3 directory authority, makes relays with dynamic IP addresses and no
13242 DirPort notice more quickly when their IP address changes, fixes a few
13243 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
13245 o New directory authorities:
13246 - Take lefkada out of the list of v3 directory authorities, since
13247 it has been down for months.
13248 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
13252 - Detect address changes more quickly on non-directory mirror
13253 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
13255 o Minor features (security):
13256 - Reject requests for reverse-dns lookup of names that are in
13257 a private address space. Patch from lodger.
13258 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
13261 o Minor bugfixes (crashes):
13262 - Avoid a rare assert that can trigger when Tor doesn't have much
13263 directory information yet and it tries to fetch a v2 hidden
13264 service descriptor. Fixes bug 651, reported by nwf.
13265 - Initialize log mutex before initializing dmalloc. Otherwise,
13266 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
13267 - Use recursive pthread mutexes in order to avoid deadlock when
13268 logging debug-level messages to a controller. Bug spotted by nwf,
13269 bugfix on 0.2.0.16-alpha.
13271 o Minor bugfixes (resource management):
13272 - Keep address policies from leaking memory: start their refcount
13273 at 1, not 2. Bugfix on 0.2.0.16-alpha.
13274 - Free authority certificates on exit, so they don't look like memory
13275 leaks. Bugfix on 0.2.0.19-alpha.
13276 - Free static hashtables for policy maps and for TLS connections on
13277 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
13278 - Avoid allocating extra space when computing consensuses on 64-bit
13279 platforms. Bug spotted by aakova.
13281 o Minor bugfixes (misc):
13282 - Do not read the configuration file when we've only been told to
13283 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
13284 based on patch from Sebastian Hahn.
13285 - Exit relays that are used as a client can now reach themselves
13286 using the .exit notation, rather than just launching an infinite
13287 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
13288 - When attempting to open a logfile fails, tell us why.
13289 - Fix a dumb bug that was preventing us from knowing that we should
13290 preemptively build circuits to handle expected directory requests.
13291 Fixes bug 660. Bugfix on 0.1.2.x.
13292 - Warn less verbosely about clock skew from netinfo cells from
13293 untrusted sources. Fixes bug 663.
13294 - Make controller stream events for DNS requests more consistent,
13295 by adding "new stream" events for DNS requests, and removing
13296 spurious "stream closed" events" for cached reverse resolves.
13297 Patch from mwenge. Fixes bug 646.
13298 - Correctly notify one-hop connections when a circuit build has
13299 failed. Possible fix for bug 669. Found by lodger.
13302 Changes in version 0.2.0.23-rc - 2008-03-24
13303 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
13304 makes bootstrapping faster if the first directory mirror you contact
13305 is down. The bundles also include the new Vidalia 0.1.2 release.
13308 - When a tunneled directory request is made to a directory server
13309 that's down, notice after 30 seconds rather than 120 seconds. Also,
13310 fail any begindir streams that are pending on it, so they can
13311 retry elsewhere. This was causing multi-minute delays on bootstrap.
13314 Changes in version 0.2.0.22-rc - 2008-03-18
13315 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
13316 enables encrypted directory connections by default for non-relays, fixes
13317 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
13318 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
13321 - Enable encrypted directory connections by default for non-relays,
13322 so censor tools that block Tor directory connections based on their
13323 plaintext patterns will no longer work. This means Tor works in
13324 certain censored countries by default again.
13327 - Make sure servers always request certificates from clients during
13328 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
13329 - Do not enter a CPU-eating loop when a connection is closed in
13330 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
13331 diagnosed by lodger; bugfix on 0.2.0.20-rc.
13332 - Fix assertion failure that could occur when a blocked circuit
13333 became unblocked, and it had pending client DNS requests. Bugfix
13334 on 0.2.0.1-alpha. Fixes bug 632.
13336 o Minor bugfixes (on 0.1.2.x):
13337 - Generate "STATUS_SERVER" events rather than misspelled
13338 "STATUS_SEVER" events. Caught by mwenge.
13339 - When counting the number of bytes written on a TLS connection,
13340 look at the BIO actually used for writing to the network, not
13341 at the BIO used (sometimes) to buffer data for the network.
13342 Looking at different BIOs could result in write counts on the
13343 order of ULONG_MAX. Fixes bug 614.
13344 - On Windows, correctly detect errors when listing the contents of
13345 a directory. Fix from lodger.
13347 o Minor bugfixes (on 0.2.0.x):
13348 - Downgrade "sslv3 alert handshake failure" message to INFO.
13349 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
13350 left BandwidthRate and BandwidthBurst at the default, we would be
13351 silently limited by those defaults. Now raise them to match the
13352 RelayBandwidth* values.
13353 - Fix the SVK version detection logic to work correctly on a branch.
13354 - Make --enable-openbsd-malloc work correctly on Linux with alpha
13355 CPUs. Fixes bug 625.
13356 - Logging functions now check that the passed severity is sane.
13357 - Use proper log levels in the testsuite call of
13358 get_interface_address6().
13359 - When using a nonstandard malloc, do not use the platform values for
13360 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
13361 - Make the openbsd malloc code use 8k pages on alpha CPUs and
13363 - Detect mismatched page sizes when using --enable-openbsd-malloc.
13364 - Avoid double-marked-for-close warning when certain kinds of invalid
13365 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
13366 for bug 617. Bugfix on 0.2.0.1-alpha.
13367 - Make sure that the "NULL-means-reject *:*" convention is followed by
13368 all the policy manipulation functions, avoiding some possible crash
13369 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
13370 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
13371 actually works, and doesn't warn about every single reverse lookup.
13372 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
13375 - Only log guard node status when guard node status has changed.
13376 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
13377 make "INFO" 75% less verbose.
13380 Changes in version 0.2.0.21-rc - 2008-03-02
13381 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
13382 makes Tor work well with Vidalia again, fixes a rare assert bug,
13383 and fixes a pair of more minor bugs. The bundles also include Vidalia
13384 0.1.0 and Torbutton 1.1.16.
13387 - The control port should declare that it requires password auth
13388 when HashedControlSessionPassword is set too. Patch from Matt Edman;
13389 bugfix on 0.2.0.20-rc. Fixes bug 615.
13390 - Downgrade assert in connection_buckets_decrement() to a log message.
13391 This may help us solve bug 614, and in any case will make its
13392 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
13393 - We were sometimes miscounting the number of bytes read from the
13394 network, causing our rate limiting to not be followed exactly.
13395 Bugfix on 0.2.0.16-alpha. Reported by lodger.
13398 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
13399 OpenSSL versions should have been working fine. Diagnosis and patch
13400 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
13401 Bugfix on 0.2.0.20-rc.
13404 Changes in version 0.2.0.20-rc - 2008-02-24
13405 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
13406 makes more progress towards normalizing Tor's TLS handshake, makes
13407 hidden services work better again, helps relays bootstrap if they don't
13408 know their IP address, adds optional support for linking in openbsd's
13409 allocator or tcmalloc, allows really fast relays to scale past 15000
13410 sockets, and fixes a bunch of minor bugs reported by Veracode.
13413 - Enable the revised TLS handshake based on the one designed by
13414 Steven Murdoch in proposal 124, as revised in proposal 130. It
13415 includes version negotiation for OR connections as described in
13416 proposal 105. The new handshake is meant to be harder for censors
13417 to fingerprint, and it adds the ability to detect certain kinds of
13418 man-in-the-middle traffic analysis attacks. The version negotiation
13419 feature will allow us to improve Tor's link protocol more safely
13421 - Choose which bridge to use proportional to its advertised bandwidth,
13422 rather than uniformly at random. This should speed up Tor for
13423 bridge users. Also do this for people who set StrictEntryNodes.
13424 - When a TrackHostExits-chosen exit fails too many times in a row,
13425 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
13428 - Resolved problems with (re-)fetching hidden service descriptors.
13429 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
13430 and 0.2.0.19-alpha.
13431 - If we only ever used Tor for hidden service lookups or posts, we
13432 would stop building circuits and start refusing connections after
13433 24 hours, since we falsely believed that Tor was dormant. Reported
13434 by nwf; bugfix on 0.1.2.x.
13435 - Servers that don't know their own IP address should go to the
13436 authorities for their first directory fetch, even if their DirPort
13437 is off or if they don't know they're reachable yet. This will help
13438 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
13439 - When counting the number of open sockets, count not only the number
13440 of sockets we have received from the socket() call, but also
13441 the number we've gotten from accept() and socketpair(). This bug
13442 made us fail to count all sockets that we were using for incoming
13443 connections. Bugfix on 0.2.0.x.
13444 - Fix code used to find strings within buffers, when those strings
13445 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
13446 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
13447 - Add a new __HashedControlSessionPassword option for controllers
13448 to use for one-off session password hashes that shouldn't get
13449 saved to disk by SAVECONF --- Vidalia users were accumulating a
13450 pile of HashedControlPassword lines in their torrc files, one for
13451 each time they had restarted Tor and then clicked Save. Make Tor
13452 automatically convert "HashedControlPassword" to this new option but
13453 only when it's given on the command line. Partial fix for bug 586.
13455 o Minor features (performance):
13456 - Tune parameters for cell pool allocation to minimize amount of
13458 - Add OpenBSD malloc code from phk as an optional malloc
13459 replacement on Linux: some glibc libraries do very poorly
13460 with Tor's memory allocation patterns. Pass
13461 --enable-openbsd-malloc to get the replacement malloc code.
13462 - Add a --with-tcmalloc option to the configure script to link
13463 against tcmalloc (if present). Does not yet search for
13464 non-system include paths.
13465 - Stop imposing an arbitrary maximum on the number of file descriptors
13466 used for busy servers. Bug reported by Olaf Selke; patch from
13469 o Minor features (other):
13470 - When SafeLogging is disabled, log addresses along with all TLS
13472 - When building with --enable-gcc-warnings, check for whether Apple's
13473 warning "-Wshorten-64-to-32" is available.
13474 - Add a --passphrase-fd argument to the tor-gencert command for
13477 o Minor bugfixes (memory leaks and code problems):
13478 - We were leaking a file descriptor if Tor started with a zero-length
13479 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
13480 - Detect size overflow in zlib code. Reported by Justin Ferguson and
13482 - We were comparing the raw BridgePassword entry with a base64'ed
13483 version of it, when handling a "/tor/networkstatus-bridges"
13484 directory request. Now compare correctly. Noticed by Veracode.
13485 - Recover from bad tracked-since value in MTBF-history file.
13486 Should fix bug 537.
13487 - Alter the code that tries to recover from unhandled write
13488 errors, to not try to flush onto a socket that's given us
13489 unhandled errors. Bugfix on 0.1.2.x.
13490 - Make Unix controlsockets work correctly on OpenBSD. Patch from
13491 tup. Bugfix on 0.2.0.3-alpha.
13493 o Minor bugfixes (other):
13494 - If we have an extra-info document for our server, always make
13495 it available on the control port, even if we haven't gotten
13496 a copy of it from an authority yet. Patch from mwenge.
13497 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
13498 - Directory mirrors no longer include a guess at the client's IP
13499 address if the connection appears to be coming from the same /24
13500 network; it was producing too many wrong guesses.
13501 - Make the new hidden service code respect the SafeLogging setting.
13502 Bugfix on 0.2.0.x. Patch from Karsten.
13503 - When starting as an authority, do not overwrite all certificates
13504 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
13505 - If we're trying to flush the last bytes on a connection (for
13506 example, when answering a directory request), reset the
13507 time-to-give-up timeout every time we manage to write something
13508 on the socket. Bugfix on 0.1.2.x.
13509 - Change the behavior of "getinfo status/good-server-descriptor"
13510 so it doesn't return failure when any authority disappears.
13511 - Even though the man page said that "TrackHostExits ." should
13512 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
13513 - Report TLS "zero return" case as a "clean close" and "IO error"
13514 as a "close". Stop calling closes "unexpected closes": existing
13515 Tors don't use SSL_close(), so having a connection close without
13516 the TLS shutdown handshake is hardly unexpected.
13517 - Send NAMESERVER_STATUS messages for a single failed nameserver
13520 o Code simplifications and refactoring:
13521 - Remove the tor_strpartition function: its logic was confused,
13522 and it was only used for one thing that could be implemented far
13526 Changes in version 0.2.0.19-alpha - 2008-02-09
13527 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
13528 handshake, makes path selection for relays more secure and IP address
13529 guessing more robust, and generally fixes a lot of bugs in preparation
13530 for calling the 0.2.0 branch stable.
13533 - Do not include recognizeable strings in the commonname part of
13534 Tor's x509 certificates.
13537 - If we're a relay, avoid picking ourselves as an introduction point,
13538 a rendezvous point, or as the final hop for internal circuits. Bug
13539 reported by taranis and lodger. Bugfix on 0.1.2.x.
13540 - Patch from "Andrew S. Lists" to catch when we contact a directory
13541 mirror at IP address X and he says we look like we're coming from
13542 IP address X. Bugfix on 0.1.2.x.
13544 o Minor features (security):
13545 - Be more paranoid about overwriting sensitive memory on free(),
13546 as a defensive programming tactic to ensure forward secrecy.
13548 o Minor features (directory authority):
13549 - Actually validate the options passed to AuthDirReject,
13550 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
13551 - Reject router descriptors with out-of-range bandwidthcapacity or
13552 bandwidthburst values.
13554 o Minor features (controller):
13555 - Reject controller commands over 1MB in length. This keeps rogue
13556 processes from running us out of memory.
13558 o Minor features (misc):
13559 - Give more descriptive well-formedness errors for out-of-range
13560 hidden service descriptor/protocol versions.
13561 - Make memory debugging information describe more about history
13562 of cell allocation, so we can help reduce our memory use.
13564 o Deprecated features (controller):
13565 - The status/version/num-versioning and status/version/num-concurring
13566 GETINFO options are no longer useful in the v3 directory protocol:
13567 treat them as deprecated, and warn when they're used.
13570 - When our consensus networkstatus has been expired for a while, stop
13571 being willing to build circuits using it. Fixes bug 401. Bugfix
13573 - Directory caches now fetch certificates from all authorities
13574 listed in a networkstatus consensus, even when they do not
13575 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
13576 - When connecting to a bridge without specifying its key, insert
13577 the connection into the identity-to-connection map as soon as
13578 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
13579 - Detect versions of OS X where malloc_good_size() is present in the
13580 library but never actually declared. Resolves bug 587. Bugfix
13582 - Stop incorrectly truncating zlib responses to directory authority
13583 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
13584 - Stop recommending that every server operator send mail to tor-ops.
13585 Resolves bug 597. Bugfix on 0.1.2.x.
13586 - Don't trigger an assert if we start a directory authority with a
13587 private IP address (like 127.0.0.1).
13588 - Avoid possible failures when generating a directory with routers
13589 with over-long versions strings, or too many flags set. Bugfix
13591 - If an attempt to launch a DNS resolve request over the control
13592 port fails because we have overrun the limit on the number of
13593 connections, tell the controller that the request has failed.
13594 - Avoid using too little bandwidth when our clock skips a few
13595 seconds. Bugfix on 0.1.2.x.
13596 - Fix shell error when warning about missing packages in configure
13597 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
13598 - Do not become confused when receiving a spurious VERSIONS-like
13599 cell from a confused v1 client. Bugfix on 0.2.0.x.
13600 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
13601 introduction points for a hidden service have failed. Patch from
13602 Karsten Loesing. Bugfix on 0.2.0.x.
13604 o Code simplifications and refactoring:
13605 - Remove some needless generality from cpuworker code, for improved
13607 - Stop overloading the circuit_t.onionskin field for both "onionskin
13608 from a CREATE cell that we are waiting for a cpuworker to be
13609 assigned" and "onionskin from an EXTEND cell that we are going to
13610 send to an OR as soon as we are connected". Might help with bug 600.
13611 - Add an in-place version of aes_crypt() so that we can avoid doing a
13612 needless memcpy() call on each cell payload.
13615 Changes in version 0.2.0.18-alpha - 2008-01-25
13616 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
13617 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
13618 that can warn or reject connections to ports generally associated with
13619 vulnerable-plaintext protocols.
13621 o New directory authorities:
13622 - Set up dannenberg (run by CCC) as the sixth v3 directory
13626 - Fix a major memory leak when attempting to use the v2 TLS
13627 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
13628 - We accidentally enabled the under-development v2 TLS handshake
13629 code, which was causing log entries like "TLS error while
13630 renegotiating handshake". Disable it again. Resolves bug 590.
13631 - We were computing the wrong Content-Length: header for directory
13632 responses that need to be compressed on the fly, causing clients
13633 asking for those items to always fail. Bugfix on 0.2.0.x; partially
13637 - Avoid going directly to the directory authorities even if you're a
13638 relay, if you haven't found yourself reachable yet or if you've
13639 decided not to advertise your dirport yet. Addresses bug 556.
13640 - If we've gone 12 hours since our last bandwidth check, and we
13641 estimate we have less than 50KB bandwidth capacity but we could
13642 handle more, do another bandwidth test.
13643 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
13644 Tor can warn and/or refuse connections to ports commonly used with
13645 vulnerable-plaintext protocols. Currently we warn on ports 23,
13646 109, 110, and 143, but we don't reject any.
13649 - When we setconf ClientOnly to 1, close any current OR and Dir
13650 listeners. Reported by mwenge.
13651 - When we get a consensus that's been signed by more people than
13652 we expect, don't log about it; it's not a big deal. Reported
13656 - Don't answer "/tor/networkstatus-bridges" directory requests if
13657 the request isn't encrypted.
13658 - Make "ClientOnly 1" config option disable directory ports too.
13659 - Patches from Karsten Loesing to make v2 hidden services more
13660 robust: work even when there aren't enough HSDir relays available;
13661 retry when a v2 rend desc fetch fails; but don't retry if we
13662 already have a usable v0 rend desc.
13665 Changes in version 0.2.0.17-alpha - 2008-01-17
13666 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
13669 - Make the tor-gencert man page get included correctly in the tarball.
13672 Changes in version 0.2.0.16-alpha - 2008-01-17
13673 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
13674 Loesing, and generally cleans up a lot of features and minor bugs.
13676 o New directory authorities:
13677 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
13680 o Major performance improvements:
13681 - Switch our old ring buffer implementation for one more like that
13682 used by free Unix kernels. The wasted space in a buffer with 1mb
13683 of data will now be more like 8k than 1mb. The new implementation
13684 also avoids realloc();realloc(); patterns that can contribute to
13685 memory fragmentation.
13688 - Configuration files now accept C-style strings as values. This
13689 helps encode characters not allowed in the current configuration
13690 file format, such as newline or #. Addresses bug 557.
13691 - Although we fixed bug 539 (where servers would send HTTP status 503
13692 responses _and_ send a body too), there are still servers out
13693 there that haven't upgraded. Therefore, make clients parse such
13694 bodies when they receive them.
13695 - When we're not serving v2 directory information, there is no reason
13696 to actually keep any around. Remove the obsolete files and directory
13697 on startup if they are very old and we aren't going to serve them.
13699 o Minor performance improvements:
13700 - Reference-count and share copies of address policy entries; only 5%
13701 of them were actually distinct.
13702 - Never walk through the list of logs if we know that no log is
13703 interested in a given message.
13706 - When an authority has not signed a consensus, do not try to
13707 download a nonexistent "certificate with key 00000000". Bugfix
13708 on 0.2.0.x. Fixes bug 569.
13709 - Fix a rare assert error when we're closing one of our threads:
13710 use a mutex to protect the list of logs, so we never write to the
13711 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
13712 bug 575, which is kind of the revenge of bug 222.
13713 - Patch from Karsten Loesing to complain less at both the client
13714 and the relay when a relay used to have the HSDir flag but doesn't
13715 anymore, and we try to upload a hidden service descriptor.
13716 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
13718 - Do not try to download missing certificates until we have tried
13719 to check our fallback consensus. Fixes bug 583.
13720 - Make bridges round reported GeoIP stats info up to the nearest
13721 estimate, not down. Now we can distinguish between "0 people from
13722 this country" and "1 person from this country".
13723 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
13724 - Avoid possible segfault if key generation fails in
13725 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
13726 - Avoid segfault in the case where a badly behaved v2 versioning
13727 directory sends a signed networkstatus with missing client-versions.
13729 - Avoid segfaults on certain complex invocations of
13730 router_get_by_hexdigest(). Bugfix on 0.1.2.
13731 - Correct bad index on array access in parse_http_time(). Bugfix
13733 - Fix possible bug in vote generation when server versions are present
13734 but client versions are not.
13735 - Fix rare bug on REDIRECTSTREAM control command when called with no
13736 port set: it could erroneously report an error when none had
13738 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
13739 compressing large objects and find ourselves with more than 4k
13740 left over. Bugfix on 0.2.0.
13741 - Fix a small memory leak when setting up a hidden service.
13742 - Fix a few memory leaks that could in theory happen under bizarre
13744 - Fix an assert if we post a general-purpose descriptor via the
13745 control port but that descriptor isn't mentioned in our current
13746 network consensus. Bug reported by Jon McLachlan; bugfix on
13749 o Minor features (controller):
13750 - Get NS events working again. Patch from tup.
13751 - The GETCONF command now escapes and quotes configuration values
13752 that don't otherwise fit into the torrc file.
13753 - The SETCONF command now handles quoted values correctly.
13755 o Minor features (directory authorities):
13756 - New configuration options to override default maximum number of
13757 servers allowed on a single IP address. This is important for
13758 running a test network on a single host.
13759 - Actually implement the -s option to tor-gencert.
13760 - Add a manual page for tor-gencert.
13762 o Minor features (bridges):
13763 - Bridge authorities no longer serve bridge descriptors over
13764 unencrypted connections.
13766 o Minor features (other):
13767 - Add hidden services and DNSPorts to the list of things that make
13768 Tor accept that it has running ports. Change starting Tor with no
13769 ports from a fatal error to a warning; we might change it back if
13770 this turns out to confuse anybody. Fixes bug 579.
13773 Changes in version 0.1.2.19 - 2008-01-17
13774 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
13775 exit policy a little bit more conservative so it's safer to run an
13776 exit relay on a home system, and fixes a variety of smaller issues.
13779 - Exit policies now reject connections that are addressed to a
13780 relay's public (external) IP address too, unless
13781 ExitPolicyRejectPrivate is turned off. We do this because too
13782 many relays are running nearby to services that trust them based
13783 on network address.
13786 - When the clock jumps forward a lot, do not allow the bandwidth
13787 buckets to become negative. Fixes bug 544.
13788 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
13789 on every successful resolve. Reported by Mike Perry.
13790 - Purge old entries from the "rephist" database and the hidden
13791 service descriptor database even when DirPort is zero.
13792 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
13793 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
13794 crashing or mis-answering these requests.
13795 - When we decide to send a 503 response to a request for servers, do
13796 not then also send the server descriptors: this defeats the whole
13797 purpose. Fixes bug 539.
13800 - Changing the ExitPolicyRejectPrivate setting should cause us to
13801 rebuild our server descriptor.
13802 - Fix handling of hex nicknames when answering controller requests for
13803 networkstatus by name, or when deciding whether to warn about
13804 unknown routers in a config option. (Patch from mwenge.)
13805 - Fix a couple of hard-to-trigger autoconf problems that could result
13806 in really weird results on platforms whose sys/types.h files define
13807 nonstandard integer types.
13808 - Don't try to create the datadir when running --verify-config or
13809 --hash-password. Resolves bug 540.
13810 - If we were having problems getting a particular descriptor from the
13811 directory caches, and then we learned about a new descriptor for
13812 that router, we weren't resetting our failure count. Reported
13814 - Although we fixed bug 539 (where servers would send HTTP status 503
13815 responses _and_ send a body too), there are still servers out there
13816 that haven't upgraded. Therefore, make clients parse such bodies
13817 when they receive them.
13818 - Run correctly on systems where rlim_t is larger than unsigned long.
13819 This includes some 64-bit systems.
13820 - Run correctly on platforms (like some versions of OS X 10.5) where
13821 the real limit for number of open files is OPEN_FILES, not rlim_max
13822 from getrlimit(RLIMIT_NOFILES).
13823 - Avoid a spurious free on base64 failure.
13824 - Avoid segfaults on certain complex invocations of
13825 router_get_by_hexdigest().
13826 - Fix rare bug on REDIRECTSTREAM control command when called with no
13827 port set: it could erroneously report an error when none had
13831 Changes in version 0.2.0.15-alpha - 2007-12-25
13832 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
13833 features added in 0.2.0.13-alpha.
13836 - Fix several remotely triggerable asserts based on DirPort requests
13837 for a v2 or v3 networkstatus object before we were prepared. This
13838 was particularly bad for 0.2.0.13 and later bridge relays, who
13839 would never have a v2 networkstatus and would thus always crash
13840 when used. Bugfixes on 0.2.0.x.
13841 - Estimate the v3 networkstatus size more accurately, rather than
13842 estimating it at zero bytes and giving it artificially high priority
13843 compared to other directory requests. Bugfix on 0.2.0.x.
13846 - Fix configure.in logic for cross-compilation.
13847 - When we load a bridge descriptor from the cache, and it was
13848 previously unreachable, mark it as retriable so we won't just
13849 ignore it. Also, try fetching a new copy immediately. Bugfixes
13851 - The bridge GeoIP stats were counting other relays, for example
13852 self-reachability and authority-reachability tests.
13855 - Support compilation to target iPhone; patch from cjacker huang.
13856 To build for iPhone, pass the --enable-iphone option to configure.
13859 Changes in version 0.2.0.14-alpha - 2007-12-23
13861 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
13862 without a datadirectory from a previous Tor install. Reported
13864 - Fix a crash when we fetch a descriptor that turns out to be
13865 unexpected (it used to be in our networkstatus when we started
13866 fetching it, but it isn't in our current networkstatus), and we
13867 aren't using bridges. Bugfix on 0.2.0.x.
13868 - Fix a crash when accessing hidden services: it would work the first
13869 time you use a given introduction point for your service, but
13870 on subsequent requests we'd be using garbage memory. Fixed by
13871 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
13872 - Fix a crash when we load a bridge descriptor from disk but we don't
13873 currently have a Bridge line for it in our torrc. Bugfix on
13877 - If bridge authorities set BridgePassword, they will serve a
13878 snapshot of known bridge routerstatuses from their DirPort to
13879 anybody who knows that password. Unset by default.
13882 - Make the unit tests build again.
13883 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
13884 - Make PublishServerDescriptor default to 1, so the default doesn't
13885 have to change as we invent new directory protocol versions.
13886 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
13887 be included unless sys/time.h is already included. Fixes
13888 bug 553. Bugfix on 0.2.0.x.
13889 - If we receive a general-purpose descriptor and then receive an
13890 identical bridge-purpose descriptor soon after, don't discard
13891 the next one as a duplicate.
13894 - If BridgeRelay is set to 1, then the default for
13895 PublishServerDescriptor is now "bridge" rather than "v2,v3".
13896 - If the user sets RelayBandwidthRate but doesn't set
13897 RelayBandwidthBurst, then make them equal rather than erroring out.
13900 Changes in version 0.2.0.13-alpha - 2007-12-21
13901 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
13902 Goodell, fixes many more bugs, and adds a lot of infrastructure for
13905 o New directory authorities:
13906 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
13910 - Only update guard status (usable / not usable) once we have
13911 enough directory information. This was causing us to always pick
13912 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
13913 causing us to discard all our guards on startup if we hadn't been
13914 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
13915 - Purge old entries from the "rephist" database and the hidden
13916 service descriptor databases even when DirPort is zero. Bugfix
13918 - We were ignoring our RelayBandwidthRate for the first 30 seconds
13919 after opening a circuit -- even a relayed circuit. Bugfix on
13921 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
13922 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
13923 crashing or mis-answering these types of requests.
13924 - Relays were publishing their server descriptor to v1 and v2
13925 directory authorities, but they didn't try publishing to v3-only
13926 authorities. Fix this; and also stop publishing to v1 authorities.
13928 - When we were reading router descriptors from cache, we were ignoring
13929 the annotations -- so for example we were reading in bridge-purpose
13930 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
13931 - When we decided to send a 503 response to a request for servers, we
13932 were then also sending the server descriptors: this defeats the
13933 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
13936 - Bridge relays now behave like clients with respect to time
13937 intervals for downloading new consensus documents -- otherwise they
13938 stand out. Bridge users now wait until the end of the interval,
13939 so their bridge relay will be sure to have a new consensus document.
13940 - Three new config options (AlternateDirAuthority,
13941 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
13942 user selectively replace the default directory authorities by type,
13943 rather than the all-or-nothing replacement that DirServer offers.
13944 - Tor can now be configured to read a GeoIP file from disk in one
13945 of two formats. This can be used by controllers to map IP addresses
13946 to countries. Eventually, it may support exit-by-country.
13947 - When possible, bridge relays remember which countries users
13948 are coming from, and report aggregate information in their
13949 extra-info documents, so that the bridge authorities can learn
13950 where Tor is blocked.
13951 - Bridge directory authorities now do reachability testing on the
13952 bridges they know. They provide router status summaries to the
13953 controller via "getinfo ns/purpose/bridge", and also dump summaries
13954 to a file periodically.
13955 - Stop fetching directory info so aggressively if your DirPort is
13956 on but your ORPort is off; stop fetching v2 dir info entirely.
13957 You can override these choices with the new FetchDirInfoEarly
13961 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
13962 consensus documents when there are too many relays at a single
13963 IP address. Now clear it in v2 network status documents too, and
13964 also clear it in routerinfo_t when the relay is no longer listed
13965 in the relevant networkstatus document.
13966 - Don't crash if we get an unexpected value for the
13967 PublishServerDescriptor config option. Reported by Matt Edman;
13968 bugfix on 0.2.0.9-alpha.
13969 - Our new v2 hidden service descriptor format allows descriptors
13970 that have no introduction points. But Tor crashed when we tried
13971 to build a descriptor with no intro points (and it would have
13972 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
13973 by Karsten Loesing.
13974 - Fix building with dmalloc 5.5.2 with glibc.
13975 - Reject uploaded descriptors and extrainfo documents if they're
13976 huge. Otherwise we'll cache them all over the network and it'll
13977 clog everything up. Reported by Aljosha Judmayer.
13978 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
13979 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
13980 - When the DANGEROUS_VERSION controller status event told us we're
13981 running an obsolete version, it used the string "OLD" to describe
13982 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
13983 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
13984 - If we can't expand our list of entry guards (e.g. because we're
13985 using bridges or we have StrictEntryNodes set), don't mark relays
13986 down when they fail a directory request. Otherwise we're too quick
13987 to mark all our entry points down. Bugfix on 0.1.2.x.
13988 - Fix handling of hex nicknames when answering controller requests for
13989 networkstatus by name, or when deciding whether to warn about unknown
13990 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
13991 - Fix a couple of hard-to-trigger autoconf problems that could result
13992 in really weird results on platforms whose sys/types.h files define
13993 nonstandard integer types. Bugfix on 0.1.2.x.
13994 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
13995 - Don't crash on name lookup when we have no current consensus. Fixes
13996 bug 538; bugfix on 0.2.0.x.
13997 - Only Tors that want to mirror the v2 directory info should
13998 create the "cached-status" directory in their datadir. (All Tors
13999 used to create it.) Bugfix on 0.2.0.9-alpha.
14000 - Directory authorities should only automatically download Extra Info
14001 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
14004 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
14005 consumers. (We already do this on HUP.)
14006 - Authorities and caches fetch the v2 networkstatus documents
14007 less often, now that v3 is encouraged.
14008 - Add a new config option BridgeRelay that specifies you want to
14009 be a bridge relay. Right now the only difference is that it makes
14010 you answer begin_dir requests, and it makes you cache dir info,
14011 even if your DirPort isn't on.
14012 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
14013 ask about source, timestamp of arrival, purpose, etc. We need
14014 something like this to help Vidalia not do GeoIP lookups on bridge
14016 - Allow multiple HashedControlPassword config lines, to support
14017 multiple controller passwords.
14018 - Authorities now decide whether they're authoritative for a given
14019 router based on the router's purpose.
14020 - New config options AuthDirBadDir and AuthDirListBadDirs for
14021 authorities to mark certain relays as "bad directories" in the
14022 networkstatus documents. Also supports the "!baddir" directive in
14023 the approved-routers file.
14026 Changes in version 0.2.0.12-alpha - 2007-11-16
14027 This twelfth development snapshot fixes some more build problems as
14028 well as a few minor bugs.
14031 - Make it build on OpenBSD again. Patch from tup.
14032 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
14033 package-building for Red Hat, OS X, etc.
14035 o Minor bugfixes (on 0.1.2.x):
14036 - Changing the ExitPolicyRejectPrivate setting should cause us to
14037 rebuild our server descriptor.
14039 o Minor bugfixes (on 0.2.0.x):
14040 - When we're lacking a consensus, don't try to perform rendezvous
14041 operations. Reported by Karsten Loesing.
14042 - Fix a small memory leak whenever we decide against using a
14043 newly picked entry guard. Reported by Mike Perry.
14044 - When authorities detected more than two relays running on the same
14045 IP address, they were clearing all the status flags but forgetting
14046 to clear the "hsdir" flag. So clients were being told that a
14047 given relay was the right choice for a v2 hsdir lookup, yet they
14048 never had its descriptor because it was marked as 'not running'
14050 - If we're trying to fetch a bridge descriptor and there's no way
14051 the bridge authority could help us (for example, we don't know
14052 a digest, or there is no bridge authority), don't be so eager to
14053 fall back to asking the bridge authority.
14054 - If we're using bridges or have strictentrynodes set, and our
14055 chosen exit is in the same family as all our bridges/entry guards,
14056 then be flexible about families.
14059 - When we negotiate a v2 link-layer connection (not yet implemented),
14060 accept RELAY_EARLY cells and turn them into RELAY cells if we've
14061 negotiated a v1 connection for their next step. Initial code for
14065 Changes in version 0.2.0.11-alpha - 2007-11-12
14066 This eleventh development snapshot fixes some build problems with
14067 the previous snapshot. It also includes a more secure-by-default exit
14068 policy for relays, fixes an enormous memory leak for exit relays, and
14069 fixes another bug where servers were falling out of the directory list.
14072 - Exit policies now reject connections that are addressed to a
14073 relay's public (external) IP address too, unless
14074 ExitPolicyRejectPrivate is turned off. We do this because too
14075 many relays are running nearby to services that trust them based
14076 on network address. Bugfix on 0.1.2.x.
14079 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
14080 on every successful resolve. Reported by Mike Perry; bugfix
14082 - On authorities, never downgrade to old router descriptors simply
14083 because they're listed in the consensus. This created a catch-22
14084 where we wouldn't list a new descriptor because there was an
14085 old one in the consensus, and we couldn't get the new one in the
14086 consensus because we wouldn't list it. Possible fix for bug 548.
14087 Also, this might cause bug 543 to appear on authorities; if so,
14088 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
14090 o Packaging fixes on 0.2.0.10-alpha:
14091 - We were including instructions about what to do with the
14092 src/config/fallback-consensus file, but we weren't actually
14093 including it in the tarball. Disable all of that for now.
14096 - Allow people to say PreferTunnelledDirConns rather than
14097 PreferTunneledDirConns, for those alternate-spellers out there.
14100 - Don't reevaluate all the information from our consensus document
14101 just because we've downloaded a v2 networkstatus that we intend
14102 to cache. Fixes bug 545; bugfix on 0.2.0.x.
14105 Changes in version 0.2.0.10-alpha - 2007-11-10
14106 This tenth development snapshot adds a third v3 directory authority
14107 run by Mike Perry, adds most of Karsten Loesing's new hidden service
14108 descriptor format, fixes a bad crash bug and new bridge bugs introduced
14109 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
14110 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
14111 addresses many more minor issues.
14113 o New directory authorities:
14114 - Set up ides (run by Mike Perry) as the third v3 directory authority.
14117 - Allow tunnelled directory connections to ask for an encrypted
14118 "begin_dir" connection or an anonymized "uses a full Tor circuit"
14119 connection independently. Now we can make anonymized begin_dir
14120 connections for (e.g.) more secure hidden service posting and
14122 - More progress on proposal 114: code from Karsten Loesing to
14123 implement new hidden service descriptor format.
14124 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
14125 accommodate the growing number of servers that use the default
14126 and are reaching it.
14127 - Directory authorities use a new formula for selecting which nodes
14128 to advertise as Guards: they must be in the top 7/8 in terms of
14129 how long we have known about them, and above the median of those
14130 nodes in terms of weighted fractional uptime.
14131 - Make "not enough dir info yet" warnings describe *why* Tor feels
14132 it doesn't have enough directory info yet.
14135 - Stop servers from crashing if they set a Family option (or
14136 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
14138 - Make bridge users work again -- the move to v3 directories in
14139 0.2.0.9-alpha had introduced a number of bugs that made bridges
14140 no longer work for clients.
14141 - When the clock jumps forward a lot, do not allow the bandwidth
14142 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
14144 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
14145 - When the consensus lists a router descriptor that we previously were
14146 mirroring, but that we considered non-canonical, reload the
14147 descriptor as canonical. This fixes bug 543 where Tor servers
14148 would start complaining after a few days that they don't have
14149 enough directory information to build a circuit.
14150 - Consider replacing the current consensus when certificates arrive
14151 that make the pending consensus valid. Previously, we were only
14152 considering replacement when the new certs _didn't_ help.
14153 - Fix an assert error on startup if we didn't already have the
14154 consensus and certs cached in our datadirectory: we were caching
14155 the consensus in consensus_waiting_for_certs but then free'ing it
14157 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
14158 Request) if we need more v3 certs but we've already got pending
14159 requests for all of them.
14160 - Correctly back off from failing certificate downloads. Fixes
14162 - Authorities don't vote on the Running flag if they have been running
14163 for less than 30 minutes themselves. Fixes bug 547, where a newly
14164 started authority would vote that everyone was down.
14166 o New requirements:
14167 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
14168 it, it had no AES, and it hasn't seen any security patches since
14172 - Clients now hold circuitless TLS connections open for 1.5 times
14173 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
14174 rebuild a new circuit over them within that timeframe. Previously,
14175 they held them open only for KeepalivePeriod (5 minutes).
14176 - Use "If-Modified-Since" to avoid retrieving consensus
14177 networkstatuses that we already have.
14178 - When we have no consensus, check FallbackNetworkstatusFile (defaults
14179 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
14180 we start knowing some directory caches.
14181 - When we receive a consensus from the future, warn about skew.
14182 - Improve skew reporting: try to give the user a better log message
14183 about how skewed they are, and how much this matters.
14184 - When we have a certificate for an authority, believe that
14185 certificate's claims about the authority's IP address.
14186 - New --quiet command-line option to suppress the default console log.
14187 Good in combination with --hash-password.
14188 - Authorities send back an X-Descriptor-Not-New header in response to
14189 an accepted-but-discarded descriptor upload. Partially implements
14191 - Make the log message for "tls error. breaking." more useful.
14192 - Better log messages about certificate downloads, to attempt to
14193 track down the second incarnation of bug 546.
14195 o Minor features (bridges):
14196 - If bridge users set UpdateBridgesFromAuthority, but the digest
14197 they ask for is a 404 from the bridge authority, they now fall
14198 back to trying the bridge directly.
14199 - Bridges now use begin_dir to publish their server descriptor to
14200 the bridge authority, even when they haven't set TunnelDirConns.
14202 o Minor features (controller):
14203 - When reporting clock skew, and we know that the clock is _at least
14204 as skewed_ as some value, but we don't know the actual value,
14205 report the value as a "minimum skew."
14208 - Update linux-tor-prio.sh script to allow QoS based on the uid of
14209 the Tor process. Patch from Marco Bonetti with tweaks from Mike
14213 - Refuse to start if both ORPort and UseBridges are set. Bugfix
14214 on 0.2.0.x, suggested by Matt Edman.
14215 - Don't stop fetching descriptors when FetchUselessDescriptors is
14216 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
14217 reported by tup and ioerror.
14218 - Better log message on vote from unknown authority.
14219 - Don't log "Launching 0 request for 0 router" message.
14221 o Minor bugfixes (memory leaks):
14222 - Stop leaking memory every time we parse a v3 certificate. Bugfix
14224 - Stop leaking memory every time we load a v3 certificate. Bugfix
14225 on 0.2.0.1-alpha. Fixes bug 536.
14226 - Stop leaking a cached networkstatus on exit. Bugfix on
14228 - Stop leaking voter information every time we free a consensus.
14229 Bugfix on 0.2.0.3-alpha.
14230 - Stop leaking signed data every time we check a voter signature.
14231 Bugfix on 0.2.0.3-alpha.
14232 - Stop leaking a signature every time we fail to parse a consensus or
14233 a vote. Bugfix on 0.2.0.3-alpha.
14234 - Stop leaking v2_download_status_map on shutdown. Bugfix on
14236 - Stop leaking conn->nickname every time we make a connection to a
14237 Tor relay without knowing its expected identity digest (e.g. when
14238 using bridges). Bugfix on 0.2.0.3-alpha.
14240 - Minor bugfixes (portability):
14241 - Run correctly on platforms where rlim_t is larger than unsigned
14242 long, and/or where the real limit for number of open files is
14243 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
14244 particular, these may be needed for OS X 10.5.
14247 Changes in version 0.1.2.18 - 2007-10-28
14248 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
14249 hidden service introduction that were causing huge delays, and a big
14250 bug that was causing some servers to disappear from the network status
14251 lists for a few hours each day.
14253 o Major bugfixes (crashes):
14254 - If a connection is shut down abruptly because of something that
14255 happened inside connection_flushed_some(), do not call
14256 connection_finished_flushing(). Should fix bug 451:
14257 "connection_stop_writing: Assertion conn->write_event failed"
14258 Bugfix on 0.1.2.7-alpha.
14259 - Fix possible segfaults in functions called from
14260 rend_process_relay_cell().
14262 o Major bugfixes (hidden services):
14263 - Hidden services were choosing introduction points uniquely by
14264 hexdigest, but when constructing the hidden service descriptor
14265 they merely wrote the (potentially ambiguous) nickname.
14266 - Clients now use the v2 intro format for hidden service
14267 connections: they specify their chosen rendezvous point by identity
14268 digest rather than by (potentially ambiguous) nickname. These
14269 changes could speed up hidden service connections dramatically.
14271 o Major bugfixes (other):
14272 - Stop publishing a new server descriptor just because we get a
14273 HUP signal. This led (in a roundabout way) to some servers getting
14274 dropped from the networkstatus lists for a few hours each day.
14275 - When looking for a circuit to cannibalize, consider family as well
14276 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
14277 circuit cannibalization).
14278 - When a router wasn't listed in a new networkstatus, we were leaving
14279 the flags for that router alone -- meaning it remained Named,
14280 Running, etc -- even though absence from the networkstatus means
14281 that it shouldn't be considered to exist at all anymore. Now we
14282 clear all the flags for routers that fall out of the networkstatus
14283 consensus. Fixes bug 529.
14286 - Don't try to access (or alter) the state file when running
14287 --list-fingerprint or --verify-config or --hash-password. Resolves
14289 - When generating information telling us how to extend to a given
14290 router, do not try to include the nickname if it is
14291 absent. Resolves bug 467.
14292 - Fix a user-triggerable segfault in expand_filename(). (There isn't
14293 a way to trigger this remotely.)
14294 - When sending a status event to the controller telling it that an
14295 OR address is reachable, set the port correctly. (Previously we
14296 were reporting the dir port.)
14297 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
14298 command. Bugfix on 0.1.2.17.
14299 - When loading bandwidth history, do not believe any information in
14300 the future. Fixes bug 434.
14301 - When loading entry guard information, do not believe any information
14303 - When we have our clock set far in the future and generate an
14304 onion key, then re-set our clock to be correct, we should not stop
14305 the onion key from getting rotated.
14306 - On some platforms, accept() can return a broken address. Detect
14307 this more quietly, and deal accordingly. Fixes bug 483.
14308 - It's not actually an error to find a non-pending entry in the DNS
14309 cache when canceling a pending resolve. Don't log unless stuff
14310 is fishy. Resolves bug 463.
14311 - Don't reset trusted dir server list when we set a configuration
14312 option. Patch from Robert Hogan.
14313 - Don't try to create the datadir when running --verify-config or
14314 --hash-password. Resolves bug 540.
14317 Changes in version 0.2.0.9-alpha - 2007-10-24
14318 This ninth development snapshot switches clients to the new v3 directory
14319 system; allows servers to be listed in the network status even when they
14320 have the same nickname as a registered server; and fixes many other
14321 bugs including a big one that was causing some servers to disappear
14322 from the network status lists for a few hours each day.
14324 o Major features (directory system):
14325 - Clients now download v3 consensus networkstatus documents instead
14326 of v2 networkstatus documents. Clients and caches now base their
14327 opinions about routers on these consensus documents. Clients only
14328 download router descriptors listed in the consensus.
14329 - Authorities now list servers who have the same nickname as
14330 a different named server, but list them with a new flag,
14331 "Unnamed". Now we can list servers that happen to pick the same
14332 nickname as a server that registered two years ago and then
14333 disappeared. Partially implements proposal 122.
14334 - If the consensus lists a router as "Unnamed", the name is assigned
14335 to a different router: do not identify the router by that name.
14336 Partially implements proposal 122.
14337 - Authorities can now come to a consensus on which method to use to
14338 compute the consensus. This gives us forward compatibility.
14341 - Stop publishing a new server descriptor just because we HUP or
14342 when we find our DirPort to be reachable but won't actually publish
14343 it. New descriptors without any real changes are dropped by the
14344 authorities, and can screw up our "publish every 18 hours" schedule.
14346 - When a router wasn't listed in a new networkstatus, we were leaving
14347 the flags for that router alone -- meaning it remained Named,
14348 Running, etc -- even though absence from the networkstatus means
14349 that it shouldn't be considered to exist at all anymore. Now we
14350 clear all the flags for routers that fall out of the networkstatus
14351 consensus. Fixes bug 529; bugfix on 0.1.2.x.
14352 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
14353 extrainfo documents and then discard them immediately for not
14354 matching the latest router. Bugfix on 0.2.0.1-alpha.
14356 o Minor features (v3 directory protocol):
14357 - Allow tor-gencert to generate a new certificate without replacing
14359 - Allow certificates to include an address.
14360 - When we change our directory-cache settings, reschedule all voting
14361 and download operations.
14362 - Reattempt certificate downloads immediately on failure, as long as
14363 we haven't failed a threshold number of times yet.
14364 - Delay retrying consensus downloads while we're downloading
14365 certificates to verify the one we just got. Also, count getting a
14366 consensus that we already have (or one that isn't valid) as a failure,
14367 and count failing to get the certificates after 20 minutes as a
14369 - Build circuits and download descriptors even if our consensus is a
14370 little expired. (This feature will go away once authorities are
14373 o Minor features (router descriptor cache):
14374 - If we find a cached-routers file that's been sitting around for more
14375 than 28 days unmodified, then most likely it's a leftover from
14376 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
14378 - When we (as a cache) download a descriptor because it was listed
14379 in a consensus, remember when the consensus was supposed to expire,
14380 and don't expire the descriptor until then.
14382 o Minor features (performance):
14383 - Call routerlist_remove_old_routers() much less often. This should
14384 speed startup, especially on directory caches.
14385 - Don't try to launch new descriptor downloads quite so often when we
14386 already have enough directory information to build circuits.
14387 - Base64 decoding was actually showing up on our profile when parsing
14388 the initial descriptor file; switch to an in-process all-at-once
14389 implementation that's about 3.5x times faster than calling out to
14392 o Minor features (compilation):
14393 - Detect non-ASCII platforms (if any still exist) and refuse to
14394 build there: some of our code assumes that 'A' is 65 and so on.
14396 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
14397 - Make the "next period" votes into "current period" votes immediately
14398 after publishing the consensus; avoid a heisenbug that made them
14399 stick around indefinitely.
14400 - When we discard a vote as a duplicate, do not report this as
14402 - Treat missing v3 keys or certificates as an error when running as a
14403 v3 directory authority.
14404 - When we're configured to be a v3 authority, but we're only listed
14405 as a non-v3 authority in our DirServer line for ourself, correct
14407 - If an authority doesn't have a qualified hostname, just put
14408 its address in the vote. This fixes the problem where we referred to
14409 "moria on moria:9031."
14410 - Distinguish between detached signatures for the wrong period, and
14411 detached signatures for a divergent vote.
14412 - Fix a small memory leak when computing a consensus.
14413 - When there's no concensus, we were forming a vote every 30
14414 minutes, but writing the "valid-after" line in our vote based
14415 on our configured V3AuthVotingInterval: so unless the intervals
14416 matched up, we immediately rejected our own vote because it didn't
14417 start at the voting interval that caused us to construct a vote.
14419 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
14420 - Delete unverified-consensus when the real consensus is set.
14421 - Consider retrying a consensus networkstatus fetch immediately
14422 after one fails: don't wait 60 seconds to notice.
14423 - When fetching a consensus as a cache, wait until a newer consensus
14424 should exist before trying to replace the current one.
14425 - Use a more forgiving schedule for retrying failed consensus
14426 downloads than for other types.
14428 o Minor bugfixes (other directory issues):
14429 - Correct the implementation of "download votes by digest." Bugfix on
14431 - Authorities no longer send back "400 you're unreachable please fix
14432 it" errors to Tor servers that aren't online all the time. We're
14433 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
14435 o Minor bugfixes (controller):
14436 - Don't reset trusted dir server list when we set a configuration
14437 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
14438 - Respond to INT and TERM SIGNAL commands before we execute the
14439 signal, in case the signal shuts us down. We had a patch in
14440 0.1.2.1-alpha that tried to do this by queueing the response on
14441 the connection's buffer before shutting down, but that really
14442 isn't the same thing at all. Bug located by Matt Edman.
14444 o Minor bugfixes (misc):
14445 - Correctly check for bad options to the "PublishServerDescriptor"
14446 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
14447 - Stop leaking memory on failing case of base32_decode, and make
14448 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
14449 - Don't try to download extrainfo documents when we're trying to
14450 fetch enough directory info to build a circuit: having enough
14451 info should get priority. Bugfix on 0.2.0.x.
14452 - Don't complain that "your server has not managed to confirm that its
14453 ports are reachable" if we haven't been able to build any circuits
14454 yet. Bug found by spending four hours without a v3 consensus. Bugfix
14456 - Detect the reason for failing to mmap a descriptor file we just
14457 wrote, and give a more useful log message. Fixes bug 533. Bugfix
14460 o Code simplifications and refactoring:
14461 - Remove support for the old bw_accounting file: we've been storing
14462 bandwidth accounting information in the state file since
14463 0.1.2.5-alpha. This may result in bandwidth accounting errors
14464 if you try to upgrade from 0.1.1.x or earlier, or if you try to
14465 downgrade to 0.1.1.x or earlier.
14466 - New convenience code to locate a file within the DataDirectory.
14467 - Move non-authority functionality out of dirvote.c.
14468 - Refactor the arguments for router_pick_{directory_|trusteddir}server
14469 so that they all take the same named flags.
14472 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
14473 Unix users an easy way to script their Tor process (e.g. by
14474 adjusting bandwidth based on the time of the day).
14477 Changes in version 0.2.0.8-alpha - 2007-10-12
14478 This eighth development snapshot fixes a crash bug that's been bothering
14479 us since February 2007, lets bridge authorities store a list of bridge
14480 descriptors they've seen, gets v3 directory voting closer to working,
14481 starts caching v3 directory consensus documents on directory mirrors,
14482 and fixes a variety of smaller issues including some minor memory leaks.
14484 o Major features (router descriptor cache):
14485 - Store routers in a file called cached-descriptors instead of in
14486 cached-routers. Initialize cached-descriptors from cached-routers
14487 if the old format is around. The new format allows us to store
14488 annotations along with descriptors.
14489 - Use annotations to record the time we received each descriptor, its
14490 source, and its purpose.
14491 - Disable the SETROUTERPURPOSE controller command: it is now
14493 - Controllers should now specify cache=no or cache=yes when using
14494 the +POSTDESCRIPTOR command.
14495 - Bridge authorities now write bridge descriptors to disk, meaning
14496 we can export them to other programs and begin distributing them
14499 o Major features (directory authorities):
14500 - When a v3 authority is missing votes or signatures, it now tries
14502 - Directory authorities track weighted fractional uptime as well as
14503 weighted mean-time-between failures. WFU is suitable for deciding
14504 whether a node is "usually up", while MTBF is suitable for deciding
14505 whether a node is "likely to stay up." We need both, because
14506 "usually up" is a good requirement for guards, while "likely to
14507 stay up" is a good requirement for long-lived connections.
14509 o Major features (v3 directory system):
14510 - Caches now download v3 network status documents as needed,
14511 and download the descriptors listed in them.
14512 - All hosts now attempt to download and keep fresh v3 authority
14513 certificates, and re-attempt after failures.
14514 - More internal-consistency checks for vote parsing.
14516 o Major bugfixes (crashes):
14517 - If a connection is shut down abruptly because of something that
14518 happened inside connection_flushed_some(), do not call
14519 connection_finished_flushing(). Should fix bug 451. Bugfix on
14522 o Major bugfixes (performance):
14523 - Fix really bad O(n^2) performance when parsing a long list of
14524 routers: Instead of searching the entire list for an "extra-info "
14525 string which usually wasn't there, once for every routerinfo
14526 we read, just scan lines forward until we find one we like.
14528 - When we add data to a write buffer in response to the data on that
14529 write buffer getting low because of a flush, do not consider the
14530 newly added data as a candidate for immediate flushing, but rather
14531 make it wait until the next round of writing. Otherwise, we flush
14532 and refill recursively, and a single greedy TLS connection can
14533 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
14535 o Minor features (v3 authority system):
14536 - Add more ways for tools to download the votes that lead to the
14538 - Send a 503 when low on bandwidth and a vote, consensus, or
14539 certificate is requested.
14540 - If-modified-since is now implemented properly for all kinds of
14541 certificate requests.
14543 o Minor bugfixes (network statuses):
14544 - Tweak the implementation of proposal 109 slightly: allow at most
14545 two Tor servers on the same IP address, except if it's the location
14546 of a directory authority, in which case allow five. Bugfix on
14549 o Minor bugfixes (controller):
14550 - When sending a status event to the controller telling it that an
14551 OR address is reachable, set the port correctly. (Previously we
14552 were reporting the dir port.) Bugfix on 0.1.2.x.
14554 o Minor bugfixes (v3 directory system):
14555 - Fix logic to look up a cert by its signing key digest. Bugfix on
14557 - Only change the reply to a vote to "OK" if it's not already
14558 set. This gets rid of annoying "400 OK" log messages, which may
14559 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
14560 - When we get a valid consensus, recompute the voting schedule.
14561 - Base the valid-after time of a vote on the consensus voting
14562 schedule, not on our preferred schedule.
14563 - Make the return values and messages from signature uploads and
14564 downloads more sensible.
14565 - Fix a memory leak when serving votes and consensus documents, and
14566 another when serving certificates.
14568 o Minor bugfixes (performance):
14569 - Use a slightly simpler string hashing algorithm (copying Python's
14570 instead of Java's) and optimize our digest hashing algorithm to take
14571 advantage of 64-bit platforms and to remove some possibly-costly
14573 - Fix a minor memory leak whenever we parse guards from our state
14574 file. Bugfix on 0.2.0.7-alpha.
14575 - Fix a minor memory leak whenever we write out a file. Bugfix on
14577 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
14578 command. Bugfix on 0.2.0.5-alpha.
14580 o Minor bugfixes (portability):
14581 - On some platforms, accept() can return a broken address. Detect
14582 this more quietly, and deal accordingly. Fixes bug 483.
14583 - Stop calling tor_strlower() on uninitialized memory in some cases.
14584 Bugfix in 0.2.0.7-alpha.
14586 o Minor bugfixes (usability):
14587 - Treat some 403 responses from directory servers as INFO rather than
14588 WARN-severity events.
14589 - It's not actually an error to find a non-pending entry in the DNS
14590 cache when canceling a pending resolve. Don't log unless stuff is
14591 fishy. Resolves bug 463.
14593 o Minor bugfixes (anonymity):
14594 - Never report that we've used more bandwidth than we're willing to
14595 relay: it leaks how much non-relay traffic we're using. Resolves
14597 - When looking for a circuit to cannibalize, consider family as well
14598 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
14599 circuit cannibalization).
14601 o Code simplifications and refactoring:
14602 - Make a bunch of functions static. Remove some dead code.
14603 - Pull out about a third of the really big routerlist.c; put it in a
14604 new module, networkstatus.c.
14605 - Merge the extra fields in local_routerstatus_t back into
14606 routerstatus_t: we used to need one routerstatus_t for each
14607 authority's opinion, plus a local_routerstatus_t for the locally
14608 computed consensus opinion. To save space, we put the locally
14609 modified fields into local_routerstatus_t, and only the common
14610 stuff into routerstatus_t. But once v3 directories are in use,
14611 clients and caches will no longer need to hold authority opinions;
14612 thus, the rationale for keeping the types separate is now gone.
14613 - Make the code used to reschedule and reattempt downloads more
14615 - Turn all 'Are we a directory server/mirror?' logic into a call to
14617 - Remove the code to generate the oldest (v1) directory format.
14618 The code has been disabled since 0.2.0.5-alpha.
14621 Changes in version 0.2.0.7-alpha - 2007-09-21
14622 This seventh development snapshot makes bridges work again, makes bridge
14623 authorities work for the first time, fixes two huge performance flaws
14624 in hidden services, and fixes a variety of minor issues.
14626 o New directory authorities:
14627 - Set up moria1 and tor26 as the first v3 directory authorities. See
14628 doc/spec/dir-spec.txt for details on the new directory design.
14630 o Major bugfixes (crashes):
14631 - Fix possible segfaults in functions called from
14632 rend_process_relay_cell(). Bugfix on 0.1.2.x.
14634 o Major bugfixes (bridges):
14635 - Fix a bug that made servers send a "404 Not found" in response to
14636 attempts to fetch their server descriptor. This caused Tor servers
14637 to take many minutes to establish reachability for their DirPort,
14638 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
14639 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
14640 users configure that and specify a bridge with an identity
14641 fingerprint, now they will lookup the bridge descriptor at the
14642 default bridge authority via a one-hop tunnel, but once circuits
14643 are established they will switch to a three-hop tunnel for later
14644 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
14646 o Major bugfixes (hidden services):
14647 - Hidden services were choosing introduction points uniquely by
14648 hexdigest, but when constructing the hidden service descriptor
14649 they merely wrote the (potentially ambiguous) nickname.
14650 - Clients now use the v2 intro format for hidden service
14651 connections: they specify their chosen rendezvous point by identity
14652 digest rather than by (potentially ambiguous) nickname. Both
14653 are bugfixes on 0.1.2.x, and they could speed up hidden service
14654 connections dramatically. Thanks to Karsten Loesing.
14656 o Minor features (security):
14657 - As a client, do not believe any server that tells us that an
14658 address maps to an internal address space.
14659 - Make it possible to enable HashedControlPassword and
14660 CookieAuthentication at the same time.
14662 o Minor features (guard nodes):
14663 - Tag every guard node in our state file with the version that
14664 we believe added it, or with our own version if we add it. This way,
14665 if a user temporarily runs an old version of Tor and then switches
14666 back to a new one, she doesn't automatically lose her guards.
14668 o Minor features (speed):
14669 - When implementing AES counter mode, update only the portions of the
14670 counter buffer that need to change, and don't keep separate
14671 network-order and host-order counters when they are the same (i.e.,
14672 on big-endian hosts.)
14674 o Minor features (controller):
14675 - Accept LF instead of CRLF on controller, since some software has a
14676 hard time generating real Internet newlines.
14677 - Add GETINFO values for the server status events
14678 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
14681 o Removed features:
14682 - Routers no longer include bandwidth-history lines in their
14683 descriptors; this information is already available in extra-info
14684 documents, and including it in router descriptors took up 60%
14685 (!) of compressed router descriptor downloads. Completes
14686 implementation of proposal 104.
14687 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
14688 and TorControl.py, as they use the old v0 controller protocol,
14689 and are obsoleted by TorFlow anyway.
14690 - Drop support for v1 rendezvous descriptors, since we never used
14691 them anyway, and the code has probably rotted by now. Based on
14692 patch from Karsten Loesing.
14693 - On OSX, stop warning the user that kqueue support in libevent is
14694 "experimental", since it seems to have worked fine for ages.
14697 - When generating information telling us how to extend to a given
14698 router, do not try to include the nickname if it is absent. Fixes
14699 bug 467. Bugfix on 0.2.0.3-alpha.
14700 - Fix a user-triggerable (but not remotely-triggerable) segfault
14701 in expand_filename(). Bugfix on 0.1.2.x.
14702 - Fix a memory leak when freeing incomplete requests from DNSPort.
14703 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
14704 - Don't try to access (or alter) the state file when running
14705 --list-fingerprint or --verify-config or --hash-password. (Resolves
14706 bug 499.) Bugfix on 0.1.2.x.
14707 - Servers used to decline to publish their DirPort if their
14708 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
14709 were below a threshold. Now they only look at BandwidthRate and
14710 RelayBandwidthRate. Bugfix on 0.1.2.x.
14711 - Remove an optimization in the AES counter-mode code that assumed
14712 that the counter never exceeded 2^68. When the counter can be set
14713 arbitrarily as an IV (as it is by Karsten's new hidden services
14714 code), this assumption no longer holds. Bugfix on 0.1.2.x.
14715 - Resume listing "AUTHORITY" flag for authorities in network status.
14716 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
14718 o Code simplifications and refactoring:
14719 - Revamp file-writing logic so we don't need to have the entire
14720 contents of a file in memory at once before we write to disk. Tor,
14722 - Turn "descriptor store" into a full-fledged type.
14723 - Move all NT services code into a separate source file.
14724 - Unify all code that computes medians, percentile elements, etc.
14725 - Get rid of a needless malloc when parsing address policies.
14728 Changes in version 0.1.2.17 - 2007-08-30
14729 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
14730 X bundles. Vidalia 0.0.14 makes authentication required for the
14731 ControlPort in the default configuration, which addresses important
14732 security risks. Everybody who uses Vidalia (or another controller)
14735 In addition, this Tor update fixes major load balancing problems with
14736 path selection, which should speed things up a lot once many people
14739 o Major bugfixes (security):
14740 - We removed support for the old (v0) control protocol. It has been
14741 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
14742 become more of a headache than it's worth.
14744 o Major bugfixes (load balancing):
14745 - When choosing nodes for non-guard positions, weight guards
14746 proportionally less, since they already have enough load. Patch
14748 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
14749 will allow fast Tor servers to get more attention.
14750 - When we're upgrading from an old Tor version, forget our current
14751 guards and pick new ones according to the new weightings. These
14752 three load balancing patches could raise effective network capacity
14753 by a factor of four. Thanks to Mike Perry for measurements.
14755 o Major bugfixes (stream expiration):
14756 - Expire not-yet-successful application streams in all cases if
14757 they've been around longer than SocksTimeout. Right now there are
14758 some cases where the stream will live forever, demanding a new
14759 circuit every 15 seconds. Fixes bug 454; reported by lodger.
14761 o Minor features (controller):
14762 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
14763 is valid before any authentication has been received. It tells
14764 a controller what kind of authentication is expected, and what
14765 protocol is spoken. Implements proposal 119.
14767 o Minor bugfixes (performance):
14768 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
14769 greatly speeding up loading cached-routers from disk on startup.
14770 - Disable sentinel-based debugging for buffer code: we squashed all
14771 the bugs that this was supposed to detect a long time ago, and now
14772 its only effect is to change our buffer sizes from nice powers of
14773 two (which platform mallocs tend to like) to values slightly over
14774 powers of two (which make some platform mallocs sad).
14776 o Minor bugfixes (misc):
14777 - If exit bandwidth ever exceeds one third of total bandwidth, then
14778 use the correct formula to weight exit nodes when choosing paths.
14779 Based on patch from Mike Perry.
14780 - Choose perfectly fairly among routers when choosing by bandwidth and
14781 weighting by fraction of bandwidth provided by exits. Previously, we
14782 would choose with only approximate fairness, and correct ourselves
14783 if we ran off the end of the list.
14784 - If we require CookieAuthentication but we fail to write the
14785 cookie file, we would warn but not exit, and end up in a state
14786 where no controller could authenticate. Now we exit.
14787 - If we require CookieAuthentication, stop generating a new cookie
14788 every time we change any piece of our config.
14789 - Refuse to start with certain directory authority keys, and
14790 encourage people using them to stop.
14791 - Terminate multi-line control events properly. Original patch
14793 - Fix a minor memory leak when we fail to find enough suitable
14794 servers to choose a circuit.
14795 - Stop leaking part of the descriptor when we run into a particularly
14796 unparseable piece of it.
14799 Changes in version 0.2.0.6-alpha - 2007-08-26
14800 This sixth development snapshot features a new Vidalia version in the
14801 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
14802 the ControlPort in the default configuration, which addresses important
14805 In addition, this snapshot fixes major load balancing problems
14806 with path selection, which should speed things up a lot once many
14807 people have upgraded. The directory authorities also use a new
14808 mean-time-between-failure approach to tracking which servers are stable,
14809 rather than just looking at the most recent uptime.
14811 o New directory authorities:
14812 - Set up Tonga as the default bridge directory authority.
14815 - Directory authorities now track servers by weighted
14816 mean-times-between-failures. When we have 4 or more days of data,
14817 use measured MTBF rather than declared uptime to decide whether
14818 to call a router Stable. Implements proposal 108.
14820 o Major bugfixes (load balancing):
14821 - When choosing nodes for non-guard positions, weight guards
14822 proportionally less, since they already have enough load. Patch
14824 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
14825 will allow fast Tor servers to get more attention.
14826 - When we're upgrading from an old Tor version, forget our current
14827 guards and pick new ones according to the new weightings. These
14828 three load balancing patches could raise effective network capacity
14829 by a factor of four. Thanks to Mike Perry for measurements.
14831 o Major bugfixes (descriptor parsing):
14832 - Handle unexpected whitespace better in malformed descriptors. Bug
14833 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
14836 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
14837 GETINFO for Torstat to use until it can switch to using extrainfos.
14838 - Optionally (if built with -DEXPORTMALLINFO) export the output
14839 of mallinfo via http, as tor/mallinfo.txt. Only accessible
14843 - Do not intermix bridge routers with controller-added
14844 routers. (Bugfix on 0.2.0.x)
14845 - Do not fail with an assert when accept() returns an unexpected
14846 address family. Addresses but does not wholly fix bug 483. (Bugfix
14848 - Let directory authorities startup even when they can't generate
14849 a descriptor immediately, e.g. because they don't know their
14851 - Stop putting the authentication cookie in a file called "0"
14852 in your working directory if you don't specify anything for the
14853 new CookieAuthFile option. Reported by Matt Edman.
14854 - Make it possible to read the PROTOCOLINFO response in a way that
14855 conforms to our control-spec. Reported by Matt Edman.
14856 - Fix a minor memory leak when we fail to find enough suitable
14857 servers to choose a circuit. Bugfix on 0.1.2.x.
14858 - Stop leaking part of the descriptor when we run into a particularly
14859 unparseable piece of it. Bugfix on 0.1.2.x.
14860 - Unmap the extrainfo cache file on exit.
14863 Changes in version 0.2.0.5-alpha - 2007-08-19
14864 This fifth development snapshot fixes compilation on Windows again;
14865 fixes an obnoxious client-side bug that slowed things down and put
14866 extra load on the network; gets us closer to using the v3 directory
14867 voting scheme; makes it easier for Tor controllers to use cookie-based
14868 authentication; and fixes a variety of other bugs.
14870 o Removed features:
14871 - Version 1 directories are no longer generated in full. Instead,
14872 authorities generate and serve "stub" v1 directories that list
14873 no servers. This will stop Tor versions 0.1.0.x and earlier from
14874 working, but (for security reasons) nobody should be running those
14877 o Major bugfixes (compilation, 0.2.0.x):
14878 - Try to fix Win32 compilation again: improve checking for IPv6 types.
14879 - Try to fix MSVC compilation: build correctly on platforms that do
14880 not define s6_addr16 or s6_addr32.
14881 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
14884 o Major bugfixes (stream expiration):
14885 - Expire not-yet-successful application streams in all cases if
14886 they've been around longer than SocksTimeout. Right now there are
14887 some cases where the stream will live forever, demanding a new
14888 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
14889 reported by lodger.
14891 o Minor features (directory servers):
14892 - When somebody requests a list of statuses or servers, and we have
14893 none of those, return a 404 rather than an empty 200.
14895 o Minor features (directory voting):
14896 - Store v3 consensus status consensuses on disk, and reload them
14899 o Minor features (security):
14900 - Warn about unsafe ControlPort configurations.
14901 - Refuse to start with certain directory authority keys, and
14902 encourage people using them to stop.
14904 o Minor features (controller):
14905 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
14906 is valid before any authentication has been received. It tells
14907 a controller what kind of authentication is expected, and what
14908 protocol is spoken. Implements proposal 119.
14909 - New config option CookieAuthFile to choose a new location for the
14910 cookie authentication file, and config option
14911 CookieAuthFileGroupReadable to make it group-readable.
14913 o Minor features (unit testing):
14914 - Add command-line arguments to unit-test executable so that we can
14915 invoke any chosen test from the command line rather than having
14916 to run the whole test suite at once; and so that we can turn on
14917 logging for the unit tests.
14919 o Minor bugfixes (on 0.1.2.x):
14920 - If we require CookieAuthentication but we fail to write the
14921 cookie file, we would warn but not exit, and end up in a state
14922 where no controller could authenticate. Now we exit.
14923 - If we require CookieAuthentication, stop generating a new cookie
14924 every time we change any piece of our config.
14925 - When loading bandwidth history, do not believe any information in
14926 the future. Fixes bug 434.
14927 - When loading entry guard information, do not believe any information
14929 - When we have our clock set far in the future and generate an
14930 onion key, then re-set our clock to be correct, we should not stop
14931 the onion key from getting rotated.
14932 - Clean up torrc sample config file.
14933 - Do not automatically run configure from autogen.sh. This
14934 non-standard behavior tended to annoy people who have built other
14937 o Minor bugfixes (on 0.2.0.x):
14938 - Fix a bug with AutomapHostsOnResolve that would always cause
14939 the second request to fail. Bug reported by Kate. Bugfix on
14941 - Fix a bug in ADDRMAP controller replies that would sometimes
14942 try to print a NULL. Patch from tup.
14943 - Read v3 directory authority keys from the right location.
14944 - Numerous bugfixes to directory voting code.
14947 Changes in version 0.1.2.16 - 2007-08-01
14948 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
14949 remote attacker in certain situations to rewrite the user's torrc
14950 configuration file. This can completely compromise anonymity of users
14951 in most configurations, including those running the Vidalia bundles,
14952 TorK, etc. Or worse.
14954 o Major security fixes:
14955 - Close immediately after missing authentication on control port;
14956 do not allow multiple authentication attempts.
14959 Changes in version 0.2.0.4-alpha - 2007-08-01
14960 This fourth development snapshot fixes a critical security vulnerability
14961 for most users, specifically those running Vidalia, TorK, etc. Everybody
14962 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
14964 o Major security fixes:
14965 - Close immediately after missing authentication on control port;
14966 do not allow multiple authentication attempts.
14968 o Major bugfixes (compilation):
14969 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
14972 o Minor features (performance):
14973 - Be even more aggressive about releasing RAM from small
14974 empty buffers. Thanks to our free-list code, this shouldn't be too
14975 performance-intensive.
14976 - Disable sentinel-based debugging for buffer code: we squashed all
14977 the bugs that this was supposed to detect a long time ago, and
14978 now its only effect is to change our buffer sizes from nice
14979 powers of two (which platform mallocs tend to like) to values
14980 slightly over powers of two (which make some platform mallocs sad).
14981 - Log malloc statistics from mallinfo() on platforms where it
14985 Changes in version 0.2.0.3-alpha - 2007-07-29
14986 This third development snapshot introduces new experimental
14987 blocking-resistance features and a preliminary version of the v3
14988 directory voting design, and includes many other smaller features
14992 - The first pieces of our "bridge" design for blocking-resistance
14993 are implemented. People can run bridge directory authorities;
14994 people can run bridges; and people can configure their Tor clients
14995 with a set of bridges to use as the first hop into the Tor network.
14996 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
14998 - Create listener connections before we setuid to the configured
14999 User and Group. Now non-Windows users can choose port values
15000 under 1024, start Tor as root, and have Tor bind those ports
15001 before it changes to another UID. (Windows users could already
15003 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
15004 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
15005 on "vserver" accounts. (Patch from coderman.)
15006 - Be even more aggressive about separating local traffic from relayed
15007 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
15009 o Major features (experimental):
15010 - First cut of code for "v3 dir voting": directory authorities will
15011 vote on a common network status document rather than each publishing
15012 their own opinion. This code needs more testing and more corner-case
15013 handling before it's ready for use.
15016 - Directory authorities now call routers Fast if their bandwidth is
15017 at least 100KB/s, and consider their bandwidth adequate to be a
15018 Guard if it is at least 250KB/s, no matter the medians. This fix
15019 complements proposal 107. [Bugfix on 0.1.2.x]
15020 - Directory authorities now never mark more than 3 servers per IP as
15021 Valid and Running. (Implements proposal 109, by Kevin Bauer and
15023 - Minor change to organizationName and commonName generation
15024 procedures in TLS certificates during Tor handshakes, to invalidate
15025 some earlier censorware approaches. This is not a long-term
15026 solution, but applying it will give us a bit of time to look into
15027 the epidemiology of countermeasures as they spread.
15029 o Major bugfixes (directory):
15030 - Rewrite directory tokenization code to never run off the end of
15031 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
15033 o Minor features (controller):
15034 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
15035 match requests to applications. (Patch from Robert Hogan.)
15036 - Report address and port correctly on connections to DNSPort. (Patch
15037 from Robert Hogan.)
15038 - Add a RESOLVE command to launch hostname lookups. (Original patch
15039 from Robert Hogan.)
15040 - Add GETINFO status/enough-dir-info to let controllers tell whether
15041 Tor has downloaded sufficient directory information. (Patch
15043 - You can now use the ControlSocket option to tell Tor to listen for
15044 controller connections on Unix domain sockets on systems that
15045 support them. (Patch from Peter Palfrader.)
15046 - STREAM NEW events are generated for DNSPort requests and for
15047 tunneled directory connections. (Patch from Robert Hogan.)
15048 - New "GETINFO address-mappings/*" command to get address mappings
15049 with expiry information. "addr-mappings/*" is now deprecated.
15052 o Minor features (misc):
15053 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
15055 - The tor-gencert tool for v3 directory authorities now creates all
15056 files as readable to the file creator only, and write-protects
15057 the authority identity key.
15058 - When dumping memory usage, list bytes used in buffer memory
15060 - When running with dmalloc, dump more stats on hup and on exit.
15061 - Directory authorities now fail quickly and (relatively) harmlessly
15062 if they generate a network status document that is somehow
15065 o Traffic load balancing improvements:
15066 - If exit bandwidth ever exceeds one third of total bandwidth, then
15067 use the correct formula to weight exit nodes when choosing paths.
15068 (Based on patch from Mike Perry.)
15069 - Choose perfectly fairly among routers when choosing by bandwidth and
15070 weighting by fraction of bandwidth provided by exits. Previously, we
15071 would choose with only approximate fairness, and correct ourselves
15072 if we ran off the end of the list. [Bugfix on 0.1.2.x]
15074 o Performance improvements:
15075 - Be more aggressive with freeing buffer RAM or putting it on the
15077 - Use Critical Sections rather than Mutexes for synchronizing threads
15078 on win32; Mutexes are heavier-weight, and designed for synchronizing
15081 o Deprecated and removed features:
15082 - RedirectExits is now deprecated.
15083 - Stop allowing address masks that do not correspond to bit prefixes.
15084 We have warned about these for a really long time; now it's time
15085 to reject them. (Patch from croup.)
15087 o Minor bugfixes (directory):
15088 - Fix another crash bug related to extra-info caching. (Bug found by
15089 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
15090 - Directories no longer return a "304 not modified" when they don't
15091 have the networkstatus the client asked for. Also fix a memory
15092 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
15093 - We had accidentally labelled 0.1.2.x directory servers as not
15094 suitable for begin_dir requests, and had labelled no directory
15095 servers as suitable for uploading extra-info documents. [Bugfix
15098 o Minor bugfixes (dns):
15099 - Fix a crash when DNSPort is set more than once. (Patch from Robert
15100 Hogan.) [Bugfix on 0.2.0.2-alpha]
15101 - Add DNSPort connections to the global connection list, so that we
15102 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
15104 - Fix a dangling reference that could lead to a crash when DNSPort is
15105 changed or closed (Patch from Robert Hogan.) [Bugfix on
15108 o Minor bugfixes (controller):
15109 - Provide DNS expiry times in GMT, not in local time. For backward
15110 compatibility, ADDRMAP events only provide GMT expiry in an extended
15111 field. "GETINFO address-mappings" always does the right thing.
15112 - Use CRLF line endings properly in NS events.
15113 - Terminate multi-line control events properly. (Original patch
15114 from tup.) [Bugfix on 0.1.2.x-alpha]
15115 - Do not include spaces in SOURCE_ADDR fields in STREAM
15116 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
15119 Changes in version 0.1.2.15 - 2007-07-17
15120 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
15121 problems, fixes compilation on BSD, and fixes a variety of other
15122 bugs. Everybody should upgrade.
15124 o Major bugfixes (compilation):
15125 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
15127 o Major bugfixes (crashes):
15128 - Try even harder not to dereference the first character after
15129 an mmap(). Reported by lodger.
15130 - Fix a crash bug in directory authorities when we re-number the
15131 routerlist while inserting a new router.
15132 - When the cached-routers file is an even multiple of the page size,
15133 don't run off the end and crash. (Fixes bug 455; based on idea
15135 - Fix eventdns.c behavior on Solaris: It is critical to include
15136 orconfig.h _before_ sys/types.h, so that we can get the expected
15137 definition of _FILE_OFFSET_BITS.
15139 o Major bugfixes (security):
15140 - Fix a possible buffer overrun when using BSD natd support. Bug
15142 - When sending destroy cells from a circuit's origin, don't include
15143 the reason for tearing down the circuit. The spec says we didn't,
15144 and now we actually don't. Reported by lodger.
15145 - Keep streamids from different exits on a circuit separate. This
15146 bug may have allowed other routers on a given circuit to inject
15147 cells into streams. Reported by lodger; fixes bug 446.
15148 - If there's a never-before-connected-to guard node in our list,
15149 never choose any guards past it. This way we don't expand our
15150 guard list unless we need to.
15152 o Minor bugfixes (guard nodes):
15153 - Weight guard selection by bandwidth, so that low-bandwidth nodes
15154 don't get overused as guards.
15156 o Minor bugfixes (directory):
15157 - Correctly count the number of authorities that recommend each
15158 version. Previously, we were under-counting by 1.
15159 - Fix a potential crash bug when we load many server descriptors at
15160 once and some of them make others of them obsolete. Fixes bug 458.
15162 o Minor bugfixes (hidden services):
15163 - Stop tearing down the whole circuit when the user asks for a
15164 connection to a port that the hidden service didn't configure.
15167 o Minor bugfixes (misc):
15168 - On Windows, we were preventing other processes from reading
15169 cached-routers while Tor was running. Reported by janbar.
15170 - Fix a possible (but very unlikely) bug in picking routers by
15171 bandwidth. Add a log message to confirm that it is in fact
15172 unlikely. Patch from lodger.
15173 - Backport a couple of memory leak fixes.
15174 - Backport miscellaneous cosmetic bugfixes.
15177 Changes in version 0.2.0.2-alpha - 2007-06-02
15178 o Major bugfixes on 0.2.0.1-alpha:
15179 - Fix an assertion failure related to servers without extra-info digests.
15180 Resolves bugs 441 and 442.
15182 o Minor features (directory):
15183 - Support "If-Modified-Since" when answering HTTP requests for
15184 directories, running-routers documents, and network-status documents.
15185 (There's no need to support it for router descriptors, since those
15186 are downloaded by descriptor digest.)
15188 o Minor build issues:
15189 - Clear up some MIPSPro compiler warnings.
15190 - When building from a tarball on a machine that happens to have SVK
15191 installed, report the micro-revision as whatever version existed
15192 in the tarball, not as "x".
15195 Changes in version 0.2.0.1-alpha - 2007-06-01
15196 This early development snapshot provides new features for people running
15197 Tor as both a client and a server (check out the new RelayBandwidth
15198 config options); lets Tor run as a DNS proxy; and generally moves us
15199 forward on a lot of fronts.
15201 o Major features, server usability:
15202 - New config options RelayBandwidthRate and RelayBandwidthBurst:
15203 a separate set of token buckets for relayed traffic. Right now
15204 relayed traffic is defined as answers to directory requests, and
15205 OR connections that don't have any local circuits on them.
15207 o Major features, client usability:
15208 - A client-side DNS proxy feature to replace the need for
15209 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
15210 for DNS requests on port 9999, use the Tor network to resolve them
15211 anonymously, and send the reply back like a regular DNS server.
15212 The code still only implements a subset of DNS.
15213 - Make PreferTunneledDirConns and TunnelDirConns work even when
15214 we have no cached directory info. This means Tor clients can now
15215 do all of their connections protected by TLS.
15217 o Major features, performance and efficiency:
15218 - Directory authorities accept and serve "extra info" documents for
15219 routers. These documents contain fields from router descriptors
15220 that aren't usually needed, and that use a lot of excess
15221 bandwidth. Once these fields are removed from router descriptors,
15222 the bandwidth savings should be about 60%. [Partially implements
15224 - Servers upload extra-info documents to any authority that accepts
15225 them. Authorities (and caches that have been configured to download
15226 extra-info documents) download them as needed. [Partially implements
15228 - Change the way that Tor buffers data that it is waiting to write.
15229 Instead of queueing data cells in an enormous ring buffer for each
15230 client->OR or OR->OR connection, we now queue cells on a separate
15231 queue for each circuit. This lets us use less slack memory, and
15232 will eventually let us be smarter about prioritizing different kinds
15234 - Use memory pools to allocate cells with better speed and memory
15235 efficiency, especially on platforms where malloc() is inefficient.
15236 - Stop reading on edge connections when their corresponding circuit
15237 buffers are full; start again as the circuits empty out.
15239 o Major features, other:
15240 - Add an HSAuthorityRecordStats option that hidden service authorities
15241 can use to track statistics of overall hidden service usage without
15242 logging information that would be very useful to an attacker.
15243 - Start work implementing multi-level keys for directory authorities:
15244 Add a standalone tool to generate key certificates. (Proposal 103.)
15247 - Directory authorities now call routers Stable if they have an
15248 uptime of at least 30 days, even if that's not the median uptime
15249 in the network. Implements proposal 107, suggested by Kevin Bauer
15252 o Minor fixes (resource management):
15253 - Count the number of open sockets separately from the number
15254 of active connection_t objects. This will let us avoid underusing
15255 our allocated connection limit.
15256 - We no longer use socket pairs to link an edge connection to an
15257 anonymous directory connection or a DirPort test connection.
15258 Instead, we track the link internally and transfer the data
15259 in-process. This saves two sockets per "linked" connection (at the
15260 client and at the server), and avoids the nasty Windows socketpair()
15262 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
15263 for every single inactive connection_t. Free items from the
15264 4k/16k-buffer free lists when they haven't been used for a while.
15266 o Minor features (build):
15267 - Make autoconf search for libevent, openssl, and zlib consistently.
15268 - Update deprecated macros in configure.in.
15269 - When warning about missing headers, tell the user to let us
15270 know if the compile succeeds anyway, so we can downgrade the
15272 - Include the current subversion revision as part of the version
15273 string: either fetch it directly if we're in an SVN checkout, do
15274 some magic to guess it if we're in an SVK checkout, or use
15275 the last-detected version if we're building from a .tar.gz.
15276 Use this version consistently in log messages.
15278 o Minor features (logging):
15279 - Always prepend "Bug: " to any log message about a bug.
15280 - Put a platform string (e.g. "Linux i686") in the startup log
15281 message, so when people paste just their logs, we know if it's
15282 OpenBSD or Windows or what.
15283 - When logging memory usage, break down memory used in buffers by
15286 o Minor features (directory system):
15287 - New config option V2AuthoritativeDirectory that all directory
15288 authorities should set. This will let future authorities choose
15289 not to serve V2 directory information.
15290 - Directory authorities allow multiple router descriptors and/or extra
15291 info documents to be uploaded in a single go. This will make
15292 implementing proposal 104 simpler.
15294 o Minor features (controller):
15295 - Add a new config option __DisablePredictedCircuits designed for
15296 use by the controller, when we don't want Tor to build any circuits
15298 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
15299 so we can exit from the middle of the circuit.
15300 - Implement "getinfo status/circuit-established".
15301 - Implement "getinfo status/version/..." so a controller can tell
15302 whether the current version is recommended, and whether any versions
15303 are good, and how many authorities agree. (Patch from shibz.)
15305 o Minor features (hidden services):
15306 - Allow multiple HiddenServicePort directives with the same virtual
15307 port; when they occur, the user is sent round-robin to one
15308 of the target ports chosen at random. Partially fixes bug 393 by
15309 adding limited ad-hoc round-robining.
15311 o Minor features (other):
15313 - Add a new AutomapHostsOnResolve option: when it is enabled, any
15314 resolve request for hosts matching a given pattern causes Tor to
15315 generate an internal virtual address mapping for that host. This
15316 allows DNSPort to work sensibly with hidden service users. By
15317 default, .exit and .onion addresses are remapped; the list of
15318 patterns can be reconfigured with AutomapHostsSuffixes.
15319 - Add an "-F" option to tor-resolve to force a resolve for a .onion
15320 address. Thanks to the AutomapHostsOnResolve option, this is no
15321 longer a completely silly thing to do.
15322 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
15323 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
15324 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
15325 minus 1 byte: the actual maximum declared bandwidth.
15327 o Removed features:
15328 - Removed support for the old binary "version 0" controller protocol.
15329 This has been deprecated since 0.1.1, and warnings have been issued
15330 since 0.1.2. When we encounter a v0 control message, we now send
15331 back an error and close the connection.
15332 - Remove the old "dns worker" server DNS code: it hasn't been default
15333 since 0.1.2.2-alpha, and all the servers seem to be using the new
15336 o Minor bugfixes (portability):
15337 - Even though Windows is equally happy with / and \ as path separators,
15338 try to use \ consistently on Windows and / consistently on Unix: it
15339 makes the log messages nicer.
15340 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
15341 - Read resolv.conf files correctly on platforms where read() returns
15342 partial results on small file reads.
15344 o Minor bugfixes (directory):
15345 - Correctly enforce that elements of directory objects do not appear
15346 more often than they are allowed to appear.
15347 - When we are reporting the DirServer line we just parsed, we were
15348 logging the second stanza of the key fingerprint, not the first.
15350 o Minor bugfixes (logging):
15351 - When we hit an EOF on a log (probably because we're shutting down),
15352 don't try to remove the log from the list: just mark it as
15353 unusable. (Bulletproofs against bug 222.)
15355 o Minor bugfixes (other):
15356 - In the exitlist script, only consider the most recently published
15357 server descriptor for each server. Also, when the user requests
15358 a list of servers that _reject_ connections to a given address,
15359 explicitly exclude the IPs that also have servers that accept
15360 connections to that address. (Resolves bug 405.)
15361 - Stop allowing hibernating servers to be "stable" or "fast".
15362 - On Windows, we were preventing other processes from reading
15363 cached-routers while Tor was running. (Reported by janbar)
15364 - Make the NodeFamilies config option work. (Reported by
15365 lodger -- it has never actually worked, even though we added it
15367 - Check return values from pthread_mutex functions.
15368 - Don't save non-general-purpose router descriptors to the disk cache,
15369 because we have no way of remembering what their purpose was when
15371 - Add even more asserts to hunt down bug 417.
15372 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
15373 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
15374 Add a log message to confirm that it is in fact unlikely.
15376 o Minor bugfixes (controller):
15377 - Make 'getinfo fingerprint' return a 551 error if we're not a
15378 server, so we match what the control spec claims we do. Reported
15380 - Fix a typo in an error message when extendcircuit fails that
15381 caused us to not follow the \r\n-based delimiter protocol. Reported
15384 o Code simplifications and refactoring:
15385 - Stop passing around circuit_t and crypt_path_t pointers that are
15386 implicit in other procedure arguments.
15387 - Drop the old code to choke directory connections when the
15388 corresponding OR connections got full: thanks to the cell queue
15389 feature, OR conns don't get full any more.
15390 - Make dns_resolve() handle attaching connections to circuits
15391 properly, so the caller doesn't have to.
15392 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
15393 - Keep the connection array as a dynamic smartlist_t, rather than as
15394 a fixed-sized array. This is important, as the number of connections
15395 is becoming increasingly decoupled from the number of sockets.
15398 Changes in version 0.1.2.14 - 2007-05-25
15399 Tor 0.1.2.14 changes the addresses of two directory authorities (this
15400 change especially affects those who serve or use hidden services),
15401 and fixes several other crash- and security-related bugs.
15403 o Directory authority changes:
15404 - Two directory authorities (moria1 and moria2) just moved to new
15405 IP addresses. This change will particularly affect those who serve
15406 or use hidden services.
15408 o Major bugfixes (crashes):
15409 - If a directory server runs out of space in the connection table
15410 as it's processing a begin_dir request, it will free the exit stream
15411 but leave it attached to the circuit, leading to unpredictable
15412 behavior. (Reported by seeess, fixes bug 425.)
15413 - Fix a bug in dirserv_remove_invalid() that would cause authorities
15414 to corrupt memory under some really unlikely scenarios.
15415 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
15416 - Avoid segfaults when reading from mmaped descriptor file. (Reported
15419 o Major bugfixes (security):
15420 - When choosing an entry guard for a circuit, avoid using guards
15421 that are in the same family as the chosen exit -- not just guards
15422 that are exactly the chosen exit. (Reported by lodger.)
15424 o Major bugfixes (resource management):
15425 - If a directory authority is down, skip it when deciding where to get
15426 networkstatus objects or descriptors. Otherwise we keep asking
15427 every 10 seconds forever. Fixes bug 384.
15428 - Count it as a failure if we fetch a valid network-status but we
15429 don't want to keep it. Otherwise we'll keep fetching it and keep
15430 not wanting to keep it. Fixes part of bug 422.
15431 - If all of our dirservers have given us bad or no networkstatuses
15432 lately, then stop hammering them once per minute even when we
15433 think they're failed. Fixes another part of bug 422.
15436 - Actually set the purpose correctly for descriptors inserted with
15437 purpose=controller.
15438 - When we have k non-v2 authorities in our DirServer config,
15439 we ignored the last k authorities in the list when updating our
15441 - Correctly back-off from requesting router descriptors that we are
15442 having a hard time downloading.
15443 - Read resolv.conf files correctly on platforms where read() returns
15444 partial results on small file reads.
15445 - Don't rebuild the entire router store every time we get 32K of
15446 routers: rebuild it when the journal gets very large, or when
15447 the gaps in the store get very large.
15450 - When routers publish SVN revisions in their router descriptors,
15451 authorities now include those versions correctly in networkstatus
15453 - Warn when using a version of libevent before 1.3b to run a server on
15454 OSX or BSD: these versions interact badly with userspace threads.
15457 Changes in version 0.1.2.13 - 2007-04-24
15458 This release features some major anonymity fixes, such as safer path
15459 selection; better client performance; faster bootstrapping, better
15460 address detection, and better DNS support for servers; write limiting as
15461 well as read limiting to make servers easier to run; and a huge pile of
15462 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
15464 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
15465 of the Freenode IRC network, remembering his patience and vision for
15466 free speech on the Internet.
15469 - Fix a memory leak when we ask for "all" networkstatuses and we
15470 get one we don't recognize.
15471 - Add more asserts to hunt down bug 417.
15472 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
15475 Changes in version 0.1.2.12-rc - 2007-03-16
15477 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
15478 directory information requested inside Tor connections (i.e. via
15479 begin_dir cells). It only triggered when the same connection was
15480 serving other data at the same time. Reported by seeess.
15483 - When creating a circuit via the controller, send a 'launched'
15484 event when we're done, so we follow the spec better.
15487 Changes in version 0.1.2.11-rc - 2007-03-15
15488 o Minor bugfixes (controller), reported by daejees:
15489 - Correct the control spec to match how the code actually responds
15490 to 'getinfo addr-mappings/*'.
15491 - The control spec described a GUARDS event, but the code
15492 implemented a GUARD event. Standardize on GUARD, but let people
15493 ask for GUARDS too.
15496 Changes in version 0.1.2.10-rc - 2007-03-07
15497 o Major bugfixes (Windows):
15498 - Do not load the NT services library functions (which may not exist)
15499 just to detect if we're a service trying to shut down. Now we run
15500 on Win98 and friends again.
15502 o Minor bugfixes (other):
15503 - Clarify a couple of log messages.
15504 - Fix a misleading socks5 error number.
15507 Changes in version 0.1.2.9-rc - 2007-03-02
15508 o Major bugfixes (Windows):
15509 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
15510 of the usual GCC "%llu". This prevents a bug when saving 64-bit
15511 int configuration values: the high-order 32 bits would get
15512 truncated. In particular, we were being bitten by the default
15513 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
15514 and maybe also bug 397.)
15516 o Minor bugfixes (performance):
15517 - Use OpenSSL's AES implementation on platforms where it's faster.
15518 This could save us as much as 10% CPU usage.
15520 o Minor bugfixes (server):
15521 - Do not rotate onion key immediately after setting it for the first
15524 o Minor bugfixes (directory authorities):
15525 - Stop calling servers that have been hibernating for a long time
15526 "stable". Also, stop letting hibernating or obsolete servers affect
15527 uptime and bandwidth cutoffs.
15528 - Stop listing hibernating servers in the v1 directory.
15530 o Minor bugfixes (hidden services):
15531 - Upload hidden service descriptors slightly less often, to reduce
15532 load on authorities.
15534 o Minor bugfixes (other):
15535 - Fix an assert that could trigger if a controller quickly set then
15536 cleared EntryNodes. Bug found by Udo van den Heuvel.
15537 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
15539 - Fix a potential race condition in the rpm installer. Found by
15541 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
15542 of 2 as indicating that the server is completely bad; it sometimes
15543 means that the server is just bad for the request in question. (may fix
15544 the last of bug 326.)
15545 - Disable encrypted directory connections when we don't have a server
15546 descriptor for the destination. We'll get this working again in
15550 Changes in version 0.1.2.8-beta - 2007-02-26
15551 o Major bugfixes (crashes):
15552 - Stop crashing when the controller asks us to resetconf more than
15553 one config option at once. (Vidalia 0.0.11 does this.)
15554 - Fix a crash that happened on Win98 when we're given command-line
15555 arguments: don't try to load NT service functions from advapi32.dll
15556 except when we need them. (Bug introduced in 0.1.2.7-alpha;
15558 - Fix a longstanding obscure crash bug that could occur when
15559 we run out of DNS worker processes. (Resolves bug 390.)
15561 o Major bugfixes (hidden services):
15562 - Correctly detect whether hidden service descriptor downloads are
15563 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
15565 o Major bugfixes (accounting):
15566 - When we start during an accounting interval before it's time to wake
15567 up, remember to wake up at the correct time. (May fix bug 342.)
15569 o Minor bugfixes (controller):
15570 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
15571 clear the corresponding on_circuit variable, and remember later
15572 that we don't need to send a redundant CLOSED event. Resolves part
15574 - Report events where a resolve succeeded or where we got a socks
15575 protocol error correctly, rather than calling both of them
15577 - Change reported stream target addresses to IP consistently when
15578 we finally get the IP from an exit node.
15579 - Send log messages to the controller even if they happen to be very
15582 o Minor bugfixes (other):
15583 - Display correct results when reporting which versions are
15584 recommended, and how recommended they are. (Resolves bug 383.)
15585 - Improve our estimates for directory bandwidth to be less random:
15586 guess that an unrecognized directory will have the average bandwidth
15587 from all known directories, not that it will have the average
15588 bandwidth from those directories earlier than it on the list.
15589 - If we start a server with ClientOnly 1, then set ClientOnly to 0
15590 and hup, stop triggering an assert based on an empty onion_key.
15591 - On platforms with no working mmap() equivalent, don't warn the
15592 user when cached-routers doesn't exist.
15593 - Warn the user when mmap() [or its equivalent] fails for some reason
15594 other than file-not-found.
15595 - Don't warn the user when cached-routers.new doesn't exist: that's
15596 perfectly fine when starting up for the first time.
15597 - When EntryNodes are configured, rebuild the guard list to contain,
15598 in order: the EntryNodes that were guards before; the rest of the
15599 EntryNodes; the nodes that were guards before.
15600 - Mask out all signals in sub-threads; only the libevent signal
15601 handler should be processing them. This should prevent some crashes
15602 on some machines using pthreads. (Patch from coderman.)
15603 - Fix switched arguments on memset in the implementation of
15604 tor_munmap() for systems with no mmap() call.
15605 - When Tor receives a router descriptor that it asked for, but
15606 no longer wants (because it has received fresh networkstatuses
15607 in the meantime), do not warn the user. Cache the descriptor if
15608 we're a cache; drop it if we aren't.
15609 - Make earlier entry guards _really_ get retried when the network
15611 - On a malformed DNS reply, always give an error to the corresponding
15613 - Build with recent libevents on platforms that do not define the
15614 nonstandard types "u_int8_t" and friends.
15616 o Minor features (controller):
15617 - Warn the user when an application uses the obsolete binary v0
15618 control protocol. We're planning to remove support for it during
15619 the next development series, so it's good to give people some
15621 - Add STREAM_BW events to report per-entry-stream bandwidth
15622 use. (Patch from Robert Hogan.)
15623 - Rate-limit SIGNEWNYM signals in response to controllers that
15624 impolitely generate them for every single stream. (Patch from
15625 mwenge; closes bug 394.)
15626 - Make REMAP stream events have a SOURCE (cache or exit), and
15627 make them generated in every case where we get a successful
15628 connected or resolved cell.
15630 o Minor bugfixes (performance):
15631 - Call router_have_min_dir_info half as often. (This is showing up in
15632 some profiles, but not others.)
15633 - When using GCC, make log_debug never get called at all, and its
15634 arguments never get evaluated, when no debug logs are configured.
15635 (This is showing up in some profiles, but not others.)
15638 - Remove some never-implemented options. Mark PathlenCoinWeight as
15640 - Implement proposal 106: Stop requiring clients to have well-formed
15641 certificates; stop checking nicknames in certificates. (Clients
15642 have certificates so that they can look like Tor servers, but in
15643 the future we might want to allow them to look like regular TLS
15644 clients instead. Nicknames in certificates serve no purpose other
15645 than making our protocol easier to recognize on the wire.)
15646 - Revise messages on handshake failure again to be even more clear about
15647 which are incoming connections and which are outgoing.
15648 - Discard any v1 directory info that's over 1 month old (for
15649 directories) or over 1 week old (for running-routers lists).
15650 - Do not warn when individual nodes in the configuration's EntryNodes,
15651 ExitNodes, etc are down: warn only when all possible nodes
15652 are down. (Fixes bug 348.)
15653 - Always remove expired routers and networkstatus docs before checking
15654 whether we have enough information to build circuits. (Fixes
15656 - Put a lower-bound on MaxAdvertisedBandwidth.
15659 Changes in version 0.1.2.7-alpha - 2007-02-06
15660 o Major bugfixes (rate limiting):
15661 - Servers decline directory requests much more aggressively when
15662 they're low on bandwidth. Otherwise they end up queueing more and
15663 more directory responses, which can't be good for latency.
15664 - But never refuse directory requests from local addresses.
15665 - Fix a memory leak when sending a 503 response for a networkstatus
15667 - Be willing to read or write on local connections (e.g. controller
15668 connections) even when the global rate limiting buckets are empty.
15669 - If our system clock jumps back in time, don't publish a negative
15670 uptime in the descriptor. Also, don't let the global rate limiting
15671 buckets go absurdly negative.
15672 - Flush local controller connection buffers periodically as we're
15673 writing to them, so we avoid queueing 4+ megabytes of data before
15676 o Major bugfixes (NT services):
15677 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
15678 command-line flag so that admins can override the default by saying
15679 "tor --service install --user "SomeUser"". This will not affect
15680 existing installed services. Also, warn the user that the service
15681 will look for its configuration file in the service user's
15682 %appdata% directory. (We can't do the 'hardwire the user's appdata
15683 directory' trick any more, since we may not have read access to that
15686 o Major bugfixes (other):
15687 - Previously, we would cache up to 16 old networkstatus documents
15688 indefinitely, if they came from nontrusted authorities. Now we
15689 discard them if they are more than 10 days old.
15690 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
15692 - Detect and reject malformed DNS responses containing circular
15694 - If exits are rare enough that we're not marking exits as guards,
15695 ignore exit bandwidth when we're deciding the required bandwidth
15697 - When we're handling a directory connection tunneled over Tor,
15698 don't fill up internal memory buffers with all the data we want
15699 to tunnel; instead, only add it if the OR connection that will
15700 eventually receive it has some room for it. (This can lead to
15701 slowdowns in tunneled dir connections; a better solution will have
15702 to wait for 0.2.0.)
15704 o Minor bugfixes (dns):
15705 - Add some defensive programming to eventdns.c in an attempt to catch
15706 possible memory-stomping bugs.
15707 - Detect and reject DNS replies containing IPv4 or IPv6 records with
15708 an incorrect number of bytes. (Previously, we would ignore the
15710 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
15711 in the correct order, and doesn't crash.
15712 - Free memory held in recently-completed DNS lookup attempts on exit.
15713 This was not a memory leak, but may have been hiding memory leaks.
15714 - Handle TTL values correctly on reverse DNS lookups.
15715 - Treat failure to parse resolv.conf as an error.
15717 o Minor bugfixes (other):
15718 - Fix crash with "tor --list-fingerprint" (reported by seeess).
15719 - When computing clock skew from directory HTTP headers, consider what
15720 time it was when we finished asking for the directory, not what
15722 - Expire socks connections if they spend too long waiting for the
15723 handshake to finish. Previously we would let them sit around for
15724 days, if the connecting application didn't close them either.
15725 - And if the socks handshake hasn't started, don't send a
15726 "DNS resolve socks failed" handshake reply; just close it.
15727 - Stop using C functions that OpenBSD's linker doesn't like.
15728 - Don't launch requests for descriptors unless we have networkstatuses
15729 from at least half of the authorities. This delays the first
15730 download slightly under pathological circumstances, but can prevent
15731 us from downloading a bunch of descriptors we don't need.
15732 - Do not log IPs with TLS failures for incoming TLS
15733 connections. (Fixes bug 382.)
15734 - If the user asks to use invalid exit nodes, be willing to use
15736 - Stop using the reserved ac_cv namespace in our configure script.
15737 - Call stat() slightly less often; use fstat() when possible.
15738 - Refactor the way we handle pending circuits when an OR connection
15739 completes or fails, in an attempt to fix a rare crash bug.
15740 - Only rewrite a conn's address based on X-Forwarded-For: headers
15741 if it's a parseable public IP address; and stop adding extra quotes
15742 to the resulting address.
15745 - Weight directory requests by advertised bandwidth. Now we can
15746 let servers enable write limiting but still allow most clients to
15747 succeed at their directory requests. (We still ignore weights when
15748 choosing a directory authority; I hope this is a feature.)
15751 - Create a new file ReleaseNotes which was the old ChangeLog. The
15752 new ChangeLog file now includes the summaries for all development
15754 - Check for addresses with invalid characters at the exit as well
15755 as at the client, and warn less verbosely when they fail. You can
15756 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
15757 - Adapt a patch from goodell to let the contrib/exitlist script
15758 take arguments rather than require direct editing.
15759 - Inform the server operator when we decide not to advertise a
15760 DirPort due to AccountingMax enabled or a low BandwidthRate. It
15761 was confusing Zax, so now we're hopefully more helpful.
15762 - Bring us one step closer to being able to establish an encrypted
15763 directory tunnel without knowing a descriptor first. Still not
15764 ready yet. As part of the change, now assume we can use a
15765 create_fast cell if we don't know anything about a router.
15766 - Allow exit nodes to use nameservers running on ports other than 53.
15767 - Servers now cache reverse DNS replies.
15768 - Add an --ignore-missing-torrc command-line option so that we can
15769 get the "use sensible defaults if the configuration file doesn't
15770 exist" behavior even when specifying a torrc location on the command
15773 o Minor features (controller):
15774 - Track reasons for OR connection failure; make these reasons
15775 available via the controller interface. (Patch from Mike Perry.)
15776 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
15777 can learn when clients are sending malformed hostnames to Tor.
15778 - Clean up documentation for controller status events.
15779 - Add a REMAP status to stream events to note that a stream's
15780 address has changed because of a cached address or a MapAddress
15784 Changes in version 0.1.2.6-alpha - 2007-01-09
15786 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
15787 connection handles more than 4 gigs in either direction, we crash.
15788 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
15789 advertised exit node, somebody might try to exit from us when
15790 we're bootstrapping and before we've built our descriptor yet.
15791 Refuse the connection rather than crashing.
15794 - Warn if we (as a server) find that we've resolved an address that we
15795 weren't planning to resolve.
15796 - Warn that using select() on any libevent version before 1.1 will be
15797 unnecessarily slow (even for select()).
15798 - Flush ERR-level controller status events just like we currently
15799 flush ERR-level log events, so that a Tor shutdown doesn't prevent
15800 the controller from learning about current events.
15802 o Minor features (more controller status events):
15803 - Implement EXTERNAL_ADDRESS server status event so controllers can
15804 learn when our address changes.
15805 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
15806 can learn when directories reject our descriptor.
15807 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
15808 can learn when a client application is speaking a non-socks protocol
15810 - Implement DANGEROUS_SOCKS client status event so controllers
15811 can learn when a client application is leaking DNS addresses.
15812 - Implement BUG general status event so controllers can learn when
15813 Tor is unhappy about its internal invariants.
15814 - Implement CLOCK_SKEW general status event so controllers can learn
15815 when Tor thinks the system clock is set incorrectly.
15816 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
15817 server status events so controllers can learn when their descriptors
15818 are accepted by a directory.
15819 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
15820 server status events so controllers can learn about Tor's progress in
15821 deciding whether it's reachable from the outside.
15822 - Implement BAD_LIBEVENT general status event so controllers can learn
15823 when we have a version/method combination in libevent that needs to
15825 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
15826 and DNS_USELESS server status events so controllers can learn
15827 about changes to DNS server status.
15829 o Minor features (directory):
15830 - Authorities no longer recommend exits as guards if this would shift
15831 too much load to the exit nodes.
15834 Changes in version 0.1.2.5-alpha - 2007-01-06
15836 - Enable write limiting as well as read limiting. Now we sacrifice
15837 capacity if we're pushing out lots of directory traffic, rather
15838 than overrunning the user's intended bandwidth limits.
15839 - Include TLS overhead when counting bandwidth usage; previously, we
15840 would count only the bytes sent over TLS, but not the bytes used
15842 - Support running the Tor service with a torrc not in the same
15843 directory as tor.exe and default to using the torrc located in
15844 the %appdata%\Tor\ of the user who installed the service. Patch
15846 - Servers now check for the case when common DNS requests are going to
15847 wildcarded addresses (i.e. all getting the same answer), and change
15848 their exit policy to reject *:* if it's happening.
15849 - Implement BEGIN_DIR cells, so we can connect to the directory
15850 server via TLS to do encrypted directory requests rather than
15851 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
15852 config options if you like.
15854 o Minor features (config and docs):
15855 - Start using the state file to store bandwidth accounting data:
15856 the bw_accounting file is now obsolete. We'll keep generating it
15857 for a while for people who are still using 0.1.2.4-alpha.
15858 - Try to batch changes to the state file so that we do as few
15859 disk writes as possible while still storing important things in
15861 - The state file and the bw_accounting file get saved less often when
15862 the AvoidDiskWrites config option is set.
15863 - Make PIDFile work on Windows (untested).
15864 - Add internal descriptions for a bunch of configuration options:
15865 accessible via controller interface and in comments in saved
15867 - Reject *:563 (NNTPS) in the default exit policy. We already reject
15868 NNTP by default, so this seems like a sensible addition.
15869 - Clients now reject hostnames with invalid characters. This should
15870 avoid some inadvertent info leaks. Add an option
15871 AllowNonRFC953Hostnames to disable this behavior, in case somebody
15872 is running a private network with hosts called @, !, and #.
15873 - Add a maintainer script to tell us which options are missing
15874 documentation: "make check-docs".
15875 - Add a new address-spec.txt document to describe our special-case
15876 addresses: .exit, .onion, and .noconnnect.
15878 o Minor features (DNS):
15879 - Ongoing work on eventdns infrastructure: now it has dns server
15880 and ipv6 support. One day Tor will make use of it.
15881 - Add client-side caching for reverse DNS lookups.
15882 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
15883 - When we change nameservers or IP addresses, reset and re-launch
15884 our tests for DNS hijacking.
15886 o Minor features (directory):
15887 - Authorities now specify server versions in networkstatus. This adds
15888 about 2% to the size of compressed networkstatus docs, and allows
15889 clients to tell which servers support BEGIN_DIR and which don't.
15890 The implementation is forward-compatible with a proposed future
15891 protocol version scheme not tied to Tor versions.
15892 - DirServer configuration lines now have an orport= option so
15893 clients can open encrypted tunnels to the authorities without
15894 having downloaded their descriptors yet. Enabled for moria1,
15895 moria2, tor26, and lefkada now in the default configuration.
15896 - Directory servers are more willing to send a 503 "busy" if they
15897 are near their write limit, especially for v1 directory requests.
15898 Now they can use their limited bandwidth for actual Tor traffic.
15899 - Clients track responses with status 503 from dirservers. After a
15900 dirserver has given us a 503, we try not to use it until an hour has
15901 gone by, or until we have no dirservers that haven't given us a 503.
15902 - When we get a 503 from a directory, and we're not a server, we don't
15903 count the failure against the total number of failures allowed
15904 for the thing we're trying to download.
15905 - Report X-Your-Address-Is correctly from tunneled directory
15906 connections; don't report X-Your-Address-Is when it's an internal
15907 address; and never believe reported remote addresses when they're
15909 - Protect against an unlikely DoS attack on directory servers.
15910 - Add a BadDirectory flag to network status docs so that authorities
15911 can (eventually) tell clients about caches they believe to be
15914 o Minor features (controller):
15915 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
15916 - Reimplement GETINFO so that info/names stays in sync with the
15918 - Implement "GETINFO fingerprint".
15919 - Implement "SETEVENTS GUARD" so controllers can get updates on
15920 entry guard status as it changes.
15922 o Minor features (clean up obsolete pieces):
15923 - Remove some options that have been deprecated since at least
15924 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
15925 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
15926 to set log options.
15927 - We no longer look for identity and onion keys in "identity.key" and
15928 "onion.key" -- these were replaced by secret_id_key and
15929 secret_onion_key in 0.0.8pre1.
15930 - We no longer require unrecognized directory entries to be
15933 o Major bugfixes (security):
15934 - Stop sending the HttpProxyAuthenticator string to directory
15935 servers when directory connections are tunnelled through Tor.
15936 - Clients no longer store bandwidth history in the state file.
15937 - Do not log introduction points for hidden services if SafeLogging
15939 - When generating bandwidth history, round down to the nearest
15940 1k. When storing accounting data, round up to the nearest 1k.
15941 - When we're running as a server, remember when we last rotated onion
15942 keys, so that we will rotate keys once they're a week old even if
15943 we never stay up for a week ourselves.
15945 o Major bugfixes (other):
15946 - Fix a longstanding bug in eventdns that prevented the count of
15947 timed-out resolves from ever being reset. This bug caused us to
15948 give up on a nameserver the third time it timed out, and try it
15949 10 seconds later... and to give up on it every time it timed out
15951 - Take out the '5 second' timeout from the connection retry
15952 schedule. Now the first connect attempt will wait a full 10
15953 seconds before switching to a new circuit. Perhaps this will help
15954 a lot. Based on observations from Mike Perry.
15955 - Fix a bug on the Windows implementation of tor_mmap_file() that
15956 would prevent the cached-routers file from ever loading. Reported
15960 - Fix an assert failure when a directory authority sets
15961 AuthDirRejectUnlisted and then receives a descriptor from an
15962 unlisted router. Reported by seeess.
15963 - Avoid a double-free when parsing malformed DirServer lines.
15964 - Fix a bug when a BSD-style PF socket is first used. Patch from
15966 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
15967 to resolve an address at a given exit node even when they ask for
15969 - Servers no longer ever list themselves in their "family" line,
15970 even if configured to do so. This makes it easier to configure
15971 family lists conveniently.
15972 - When running as a server, don't fall back to 127.0.0.1 when no
15973 nameservers are configured in /etc/resolv.conf; instead, make the
15974 user fix resolv.conf or specify nameservers explicitly. (Resolves
15976 - Stop accepting certain malformed ports in configured exit policies.
15977 - Don't re-write the fingerprint file every restart, unless it has
15979 - Stop warning when a single nameserver fails: only warn when _all_ of
15980 our nameservers have failed. Also, when we only have one nameserver,
15981 raise the threshold for deciding that the nameserver is dead.
15982 - Directory authorities now only decide that routers are reachable
15983 if their identity keys are as expected.
15984 - When the user uses bad syntax in the Log config line, stop
15985 suggesting other bad syntax as a replacement.
15986 - Correctly detect ipv6 DNS capability on OpenBSD.
15988 o Minor bugfixes (controller):
15989 - Report the circuit number correctly in STREAM CLOSED events. Bug
15990 reported by Mike Perry.
15991 - Do not report bizarre values for results of accounting GETINFOs
15992 when the last second's write or read exceeds the allotted bandwidth.
15993 - Report "unrecognized key" rather than an empty string when the
15994 controller tries to fetch a networkstatus that doesn't exist.
15997 Changes in version 0.1.1.26 - 2006-12-14
15998 o Security bugfixes:
15999 - Stop sending the HttpProxyAuthenticator string to directory
16000 servers when directory connections are tunnelled through Tor.
16001 - Clients no longer store bandwidth history in the state file.
16002 - Do not log introduction points for hidden services if SafeLogging
16006 - Fix an assert failure when a directory authority sets
16007 AuthDirRejectUnlisted and then receives a descriptor from an
16008 unlisted router (reported by seeess).
16011 Changes in version 0.1.2.4-alpha - 2006-12-03
16013 - Add support for using natd; this allows FreeBSDs earlier than
16014 5.1.2 to have ipfw send connections through Tor without using
16015 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
16018 - Make all connections to addresses of the form ".noconnect"
16019 immediately get closed. This lets application/controller combos
16020 successfully test whether they're talking to the same Tor by
16021 watching for STREAM events.
16022 - Make cross.sh cross-compilation script work even when autogen.sh
16023 hasn't been run. (Patch from Michael Mohr.)
16024 - Statistics dumped by -USR2 now include a breakdown of public key
16025 operations, for profiling.
16028 - Fix a major leak when directory authorities parse their
16029 approved-routers list, a minor memory leak when we fail to pick
16030 an exit node, and a few rare leaks on errors.
16031 - Handle TransPort connections even when the server sends data before
16032 the client sends data. Previously, the connection would just hang
16033 until the client sent data. (Patch from tup based on patch from
16035 - Avoid assert failure when our cached-routers file is empty on
16039 - Don't log spurious warnings when we see a circuit close reason we
16040 don't recognize; it's probably just from a newer version of Tor.
16041 - Have directory authorities allow larger amounts of drift in uptime
16042 without replacing the server descriptor: previously, a server that
16043 restarted every 30 minutes could have 48 "interesting" descriptors
16045 - Start linking to the Tor specification and Tor reference manual
16046 correctly in the Windows installer.
16047 - Add Vidalia to the OS X uninstaller script, so when we uninstall
16048 Tor/Privoxy we also uninstall Vidalia.
16049 - Resume building on Irix64, and fix a lot of warnings from its
16050 MIPSpro C compiler.
16051 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
16052 when we're running as a client.
16055 Changes in version 0.1.1.25 - 2006-11-04
16057 - When a client asks us to resolve (rather than connect to)
16058 an address, and we have a cached answer, give them the cached
16059 answer. Previously, we would give them no answer at all.
16060 - We were building exactly the wrong circuits when we predict
16061 hidden service requirements, meaning Tor would have to build all
16062 its circuits on demand.
16063 - If none of our live entry guards have a high uptime, but we
16064 require a guard with a high uptime, try adding a new guard before
16065 we give up on the requirement. This patch should make long-lived
16066 connections more stable on average.
16067 - When testing reachability of our DirPort, don't launch new
16068 tests when there's already one in progress -- unreachable
16069 servers were stacking up dozens of testing streams.
16071 o Security bugfixes:
16072 - When the user sends a NEWNYM signal, clear the client-side DNS
16073 cache too. Otherwise we continue to act on previous information.
16076 - Avoid a memory corruption bug when creating a hash table for
16078 - Avoid possibility of controller-triggered crash when misusing
16079 certain commands from a v0 controller on platforms that do not
16080 handle printf("%s",NULL) gracefully.
16081 - Avoid infinite loop on unexpected controller input.
16082 - Don't log spurious warnings when we see a circuit close reason we
16083 don't recognize; it's probably just from a newer version of Tor.
16084 - Add Vidalia to the OS X uninstaller script, so when we uninstall
16085 Tor/Privoxy we also uninstall Vidalia.
16088 Changes in version 0.1.2.3-alpha - 2006-10-29
16090 - Prepare for servers to publish descriptors less often: never
16091 discard a descriptor simply for being too old until either it is
16092 recommended by no authorities, or until we get a better one for
16093 the same router. Make caches consider retaining old recommended
16094 routers for even longer.
16095 - If most authorities set a BadExit flag for a server, clients
16096 don't think of it as a general-purpose exit. Clients only consider
16097 authorities that advertise themselves as listing bad exits.
16098 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
16099 headers for content, so that we can work better in the presence of
16100 caching HTTP proxies.
16101 - Allow authorities to list nodes as bad exits by fingerprint or by
16104 o Minor features, controller:
16105 - Add a REASON field to CIRC events; for backward compatibility, this
16106 field is sent only to controllers that have enabled the extended
16107 event format. Also, add additional reason codes to explain why
16108 a given circuit has been destroyed or truncated. (Patches from
16110 - Add a REMOTE_REASON field to extended CIRC events to tell the
16111 controller about why a remote OR told us to close a circuit.
16112 - Stream events also now have REASON and REMOTE_REASON fields,
16113 working much like those for circuit events.
16114 - There's now a GETINFO ns/... field so that controllers can ask Tor
16115 about the current status of a router.
16116 - A new event type "NS" to inform a controller when our opinion of
16117 a router's status has changed.
16118 - Add a GETINFO events/names and GETINFO features/names so controllers
16119 can tell which events and features are supported.
16120 - A new CLEARDNSCACHE signal to allow controllers to clear the
16121 client-side DNS cache without expiring circuits.
16123 o Security bugfixes:
16124 - When the user sends a NEWNYM signal, clear the client-side DNS
16125 cache too. Otherwise we continue to act on previous information.
16128 - Avoid sending junk to controllers or segfaulting when a controller
16129 uses EVENT_NEW_DESC with verbose nicknames.
16130 - Stop triggering asserts if the controller tries to extend hidden
16131 service circuits (reported by mwenge).
16132 - Avoid infinite loop on unexpected controller input.
16133 - When the controller does a "GETINFO network-status", tell it
16134 about even those routers whose descriptors are very old, and use
16135 long nicknames where appropriate.
16136 - Change NT service functions to be loaded on demand. This lets us
16137 build with MinGW without breaking Tor for Windows 98 users.
16138 - Do DirPort reachability tests less often, since a single test
16139 chews through many circuits before giving up.
16140 - In the hidden service example in torrc.sample, stop recommending
16141 esoteric and discouraged hidden service options.
16142 - When stopping an NT service, wait up to 10 sec for it to actually
16143 stop. Patch from Matt Edman; resolves bug 295.
16144 - Fix handling of verbose nicknames with ORCONN controller events:
16145 make them show up exactly when requested, rather than exactly when
16147 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
16148 printing a duplicate "$" in the keys we send (reported by mwenge).
16149 - Correctly set maximum connection limit on Cygwin. (This time
16151 - Try to detect Windows correctly when cross-compiling.
16152 - Detect the size of the routers file correctly even if it is
16153 corrupted (on systems without mmap) or not page-aligned (on systems
16154 with mmap). This bug was harmless.
16155 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
16156 to open a stream fails; now we do in more cases. This should
16157 make clients able to find a good exit faster in some cases, since
16158 unhandleable requests will now get an error rather than timing out.
16159 - Resolve two memory leaks when rebuilding the on-disk router cache
16160 (reported by fookoowa).
16161 - Clean up minor code warnings suggested by the MIPSpro C compiler,
16162 and reported by some Centos users.
16163 - Controller signals now work on non-Unix platforms that don't define
16164 SIGUSR1 and SIGUSR2 the way we expect.
16165 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
16166 values before failing, and always enables eventdns.
16167 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
16168 Try to fix this in configure.in by checking for most functions
16169 before we check for libevent.
16172 Changes in version 0.1.2.2-alpha - 2006-10-07
16174 - Make our async eventdns library on-by-default for Tor servers,
16175 and plan to deprecate the separate dnsworker threads.
16176 - Add server-side support for "reverse" DNS lookups (using PTR
16177 records so clients can determine the canonical hostname for a given
16178 IPv4 address). Only supported by servers using eventdns; servers
16179 now announce in their descriptors whether they support eventdns.
16180 - Specify and implement client-side SOCKS5 interface for reverse DNS
16181 lookups (see doc/socks-extensions.txt).
16182 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
16183 connect to directory servers through Tor. Previously, clients needed
16184 to find Tor exits to make private connections to directory servers.
16185 - Avoid choosing Exit nodes for entry or middle hops when the
16186 total bandwidth available from non-Exit nodes is much higher than
16187 the total bandwidth available from Exit nodes.
16188 - Workaround for name servers (like Earthlink's) that hijack failing
16189 DNS requests and replace the no-such-server answer with a "helpful"
16190 redirect to an advertising-driven search portal. Also work around
16191 DNS hijackers who "helpfully" decline to hijack known-invalid
16192 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
16193 lets you turn it off.
16194 - Send out a burst of long-range padding cells once we've established
16195 that we're reachable. Spread them over 4 circuits, so hopefully
16196 a few will be fast. This exercises our bandwidth and bootstraps
16197 us into the directory more quickly.
16199 o New/improved config options:
16200 - Add new config option "ResolvConf" to let the server operator
16201 choose an alternate resolve.conf file when using eventdns.
16202 - Add an "EnforceDistinctSubnets" option to control our "exclude
16203 servers on the same /16" behavior. It's still on by default; this
16204 is mostly for people who want to operate private test networks with
16205 all the machines on the same subnet.
16206 - If one of our entry guards is on the ExcludeNodes list, or the
16207 directory authorities don't think it's a good guard, treat it as
16208 if it were unlisted: stop using it as a guard, and throw it off
16209 the guards list if it stays that way for a long time.
16210 - Allow directory authorities to be marked separately as authorities
16211 for the v1 directory protocol, the v2 directory protocol, and
16212 as hidden service directories, to make it easier to retire old
16213 authorities. V1 authorities should set "HSAuthoritativeDir 1"
16214 to continue being hidden service authorities too.
16215 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
16217 o Minor features, controller:
16218 - Fix CIRC controller events so that controllers can learn the
16219 identity digests of non-Named servers used in circuit paths.
16220 - Let controllers ask for more useful identifiers for servers. Instead
16221 of learning identity digests for un-Named servers and nicknames
16222 for Named servers, the new identifiers include digest, nickname,
16223 and indication of Named status. Off by default; see control-spec.txt
16224 for more information.
16225 - Add a "getinfo address" controller command so it can display Tor's
16226 best guess to the user.
16227 - New controller event to alert the controller when our server
16228 descriptor has changed.
16229 - Give more meaningful errors on controller authentication failure.
16231 o Minor features, other:
16232 - When asked to resolve a hostname, don't use non-exit servers unless
16233 requested to do so. This allows servers with broken DNS to be
16234 useful to the network.
16235 - Divide eventdns log messages into warn and info messages.
16236 - Reserve the nickname "Unnamed" for routers that can't pick
16237 a hostname: any router can call itself Unnamed; directory
16238 authorities will never allocate Unnamed to any particular router;
16239 clients won't believe that any router is the canonical Unnamed.
16240 - Only include function names in log messages for info/debug messages.
16241 For notice/warn/err, the content of the message should be clear on
16242 its own, and printing the function name only confuses users.
16243 - Avoid some false positives during reachability testing: don't try
16244 to test via a server that's on the same /24 as us.
16245 - If we fail to build a circuit to an intended enclave, and it's
16246 not mandatory that we use that enclave, stop wanting it.
16247 - When eventdns is enabled, allow multithreaded builds on NetBSD and
16248 OpenBSD. (We had previously disabled threads on these platforms
16249 because they didn't have working thread-safe resolver functions.)
16251 o Major bugfixes, anonymity/security:
16252 - If a client asked for a server by name, and there's a named server
16253 in our network-status but we don't have its descriptor yet, we
16254 could return an unnamed server instead.
16255 - Fix NetBSD bug that could allow someone to force uninitialized RAM
16256 to be sent to a server's DNS resolver. This only affects NetBSD
16257 and other platforms that do not bounds-check tolower().
16258 - Reject (most) attempts to use Tor circuits with length one. (If
16259 many people start using Tor as a one-hop proxy, exit nodes become
16260 a more attractive target for compromise.)
16261 - Just because your DirPort is open doesn't mean people should be
16262 able to remotely teach you about hidden service descriptors. Now
16263 only accept rendezvous posts if you've got HSAuthoritativeDir set.
16265 o Major bugfixes, other:
16266 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
16267 - When a client asks the server to resolve (not connect to)
16268 an address, and it has a cached answer, give them the cached answer.
16269 Previously, the server would give them no answer at all.
16270 - Allow really slow clients to not hang up five minutes into their
16271 directory downloads (suggested by Adam J. Richter).
16272 - We were building exactly the wrong circuits when we anticipated
16273 hidden service requirements, meaning Tor would have to build all
16274 its circuits on demand.
16275 - Avoid crashing when we mmap a router cache file of size 0.
16276 - When testing reachability of our DirPort, don't launch new
16277 tests when there's already one in progress -- unreachable
16278 servers were stacking up dozens of testing streams.
16280 o Minor bugfixes, correctness:
16281 - If we're a directory mirror and we ask for "all" network status
16282 documents, we would discard status documents from authorities
16283 we don't recognize.
16284 - Avoid a memory corruption bug when creating a hash table for
16286 - Avoid controller-triggered crash when misusing certain commands
16287 from a v0 controller on platforms that do not handle
16288 printf("%s",NULL) gracefully.
16289 - Don't crash when a controller sends a third argument to an
16290 "extendcircuit" request.
16291 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
16292 response; fix error code when "getinfo dir/status/" fails.
16293 - Avoid crash when telling controller stream-status and a stream
16295 - Patch from Adam Langley to fix assert() in eventdns.c.
16296 - Fix a debug log message in eventdns to say "X resolved to Y"
16297 instead of "X resolved to X".
16298 - Make eventdns give strings for DNS errors, not just error numbers.
16299 - Track unreachable entry guards correctly: don't conflate
16300 'unreachable by us right now' with 'listed as down by the directory
16301 authorities'. With the old code, if a guard was unreachable by
16302 us but listed as running, it would clog our guard list forever.
16303 - Behave correctly in case we ever have a network with more than
16304 2GB/s total advertised capacity.
16305 - Make TrackExitHosts case-insensitive, and fix the behavior of
16306 ".suffix" TrackExitHosts items to avoid matching in the middle of
16308 - Finally fix the openssl warnings from newer gccs that believe that
16309 ignoring a return value is okay, but casting a return value and
16310 then ignoring it is a sign of madness.
16311 - Prevent the contrib/exitlist script from printing the same
16312 result more than once.
16313 - Patch from Steve Hildrey: Generate network status correctly on
16314 non-versioning dirservers.
16315 - Don't listen to the X-Your-Address-Is hint if you did the lookup
16316 via Tor; otherwise you'll think you're the exit node's IP address.
16318 o Minor bugfixes, performance:
16319 - Two small performance improvements on parsing descriptors.
16320 - Major performance improvement on inserting descriptors: change
16321 algorithm from O(n^2) to O(n).
16322 - Make the common memory allocation path faster on machines where
16323 malloc(0) returns a pointer.
16324 - Start remembering X-Your-Address-Is directory hints even if you're
16325 a client, so you can become a server more smoothly.
16326 - Avoid duplicate entries on MyFamily line in server descriptor.
16328 o Packaging, features:
16329 - Remove architecture from OS X builds. The official builds are
16330 now universal binaries.
16331 - The Debian package now uses --verify-config when (re)starting,
16332 to distinguish configuration errors from other errors.
16333 - Update RPMs to require libevent 1.1b.
16335 o Packaging, bugfixes:
16336 - Patches so Tor builds with MinGW on Windows.
16337 - Patches so Tor might run on Cygwin again.
16338 - Resume building on non-gcc compilers and ancient gcc. Resume
16339 building with the -O0 compile flag. Resume building cleanly on
16341 - Run correctly on OS X platforms with case-sensitive filesystems.
16342 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
16343 - Add autoconf checks so Tor can build on Solaris x86 again.
16346 - Documented (and renamed) ServerDNSSearchDomains and
16347 ServerDNSResolvConfFile options.
16348 - Be clearer that the *ListenAddress directives can be repeated
16352 Changes in version 0.1.1.24 - 2006-09-29
16354 - Allow really slow clients to not hang up five minutes into their
16355 directory downloads (suggested by Adam J. Richter).
16356 - Fix major performance regression from 0.1.0.x: instead of checking
16357 whether we have enough directory information every time we want to
16358 do something, only check when the directory information has changed.
16359 This should improve client CPU usage by 25-50%.
16360 - Don't crash if, after a server has been running for a while,
16361 it can't resolve its hostname.
16364 - Allow Tor to start when RunAsDaemon is set but no logs are set.
16365 - Don't crash when the controller receives a third argument to an
16366 "extendcircuit" request.
16367 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
16368 response; fix error code when "getinfo dir/status/" fails.
16369 - Fix configure.in to not produce broken configure files with
16370 more recent versions of autoconf. Thanks to Clint for his auto*
16372 - Fix security bug on NetBSD that could allow someone to force
16373 uninitialized RAM to be sent to a server's DNS resolver. This
16374 only affects NetBSD and other platforms that do not bounds-check
16376 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
16377 methods: these are known to be buggy.
16378 - If we're a directory mirror and we ask for "all" network status
16379 documents, we would discard status documents from authorities
16380 we don't recognize.
16383 Changes in version 0.1.2.1-alpha - 2006-08-27
16385 - Add "eventdns" async dns library from Adam Langley, tweaked to
16386 build on OSX and Windows. Only enabled if you pass the
16387 --enable-eventdns argument to configure.
16388 - Allow servers with no hostname or IP address to learn their
16389 IP address by asking the directory authorities. This code only
16390 kicks in when you would normally have exited with a "no address"
16391 error. Nothing's authenticated, so use with care.
16392 - Rather than waiting a fixed amount of time between retrying
16393 application connections, we wait only 5 seconds for the first,
16394 10 seconds for the second, and 15 seconds for each retry after
16395 that. Hopefully this will improve the expected user experience.
16396 - Patch from Tup to add support for transparent AP connections:
16397 this basically bundles the functionality of trans-proxy-tor
16398 into the Tor mainline. Now hosts with compliant pf/netfilter
16399 implementations can redirect TCP connections straight to Tor
16400 without diverting through SOCKS. Needs docs.
16401 - Busy directory servers save lots of memory by spooling server
16402 descriptors, v1 directories, and v2 networkstatus docs to buffers
16403 as needed rather than en masse. Also mmap the cached-routers
16404 files, so we don't need to keep the whole thing in memory too.
16405 - Automatically avoid picking more than one node from the same
16406 /16 network when constructing a circuit.
16407 - Revise and clean up the torrc.sample that we ship with; add
16408 a section for BandwidthRate and BandwidthBurst.
16411 - Split circuit_t into origin_circuit_t and or_circuit_t, and
16412 split connection_t into edge, or, dir, control, and base structs.
16413 These will save quite a bit of memory on busy servers, and they'll
16414 also help us track down bugs in the code and bugs in the spec.
16415 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
16416 or later. Log when we are doing this, so we can diagnose it when
16417 it fails. (Also, recommend libevent 1.1b for kqueue and
16418 win32 methods; deprecate libevent 1.0b harder; make libevent
16419 recommendation system saner.)
16420 - Start being able to build universal binaries on OS X (thanks
16422 - Export the default exit policy via the control port, so controllers
16423 don't need to guess what it is / will be later.
16424 - Add a man page entry for ProtocolWarnings.
16425 - Add TestVia config option to the man page.
16426 - Remove even more protocol-related warnings from Tor server logs,
16427 such as bad TLS handshakes and malformed begin cells.
16428 - Stop fetching descriptors if you're not a dir mirror and you
16429 haven't tried to establish any circuits lately. [This currently
16430 causes some dangerous behavior, because when you start up again
16431 you'll use your ancient server descriptors.]
16432 - New DirPort behavior: if you have your dirport set, you download
16433 descriptors aggressively like a directory mirror, whether or not
16434 your ORPort is set.
16435 - Get rid of the router_retry_connections notion. Now routers
16436 no longer try to rebuild long-term connections to directory
16437 authorities, and directory authorities no longer try to rebuild
16438 long-term connections to all servers. We still don't hang up
16439 connections in these two cases though -- we need to look at it
16440 more carefully to avoid flapping, and we likely need to wait til
16441 0.1.1.x is obsolete.
16442 - Drop compatibility with obsolete Tors that permit create cells
16443 to have the wrong circ_id_type.
16444 - Re-enable per-connection rate limiting. Get rid of the "OP
16445 bandwidth" concept. Lay groundwork for "bandwidth classes" --
16446 separate global buckets that apply depending on what sort of conn
16448 - Start publishing one minute or so after we find our ORPort
16449 to be reachable. This will help reduce the number of descriptors
16450 we have for ourselves floating around, since it's quite likely
16451 other things (e.g. DirPort) will change during that minute too.
16452 - Fork the v1 directory protocol into its own spec document,
16453 and mark dir-spec.txt as the currently correct (v2) spec.
16456 - When we find our DirPort to be reachable, publish a new descriptor
16457 so we'll tell the world (reported by pnx).
16458 - Publish a new descriptor after we hup/reload. This is important
16459 if our config has changed such that we'll want to start advertising
16460 our DirPort now, etc.
16461 - Allow Tor to start when RunAsDaemon is set but no logs are set.
16462 - When we have a state file we cannot parse, tell the user and
16463 move it aside. Now we avoid situations where the user starts
16464 Tor in 1904, Tor writes a state file with that timestamp in it,
16465 the user fixes her clock, and Tor refuses to start.
16466 - Fix configure.in to not produce broken configure files with
16467 more recent versions of autoconf. Thanks to Clint for his auto*
16469 - "tor --verify-config" now exits with -1(255) or 0 depending on
16470 whether the config options are bad or good.
16471 - Resolve bug 321 when using dnsworkers: append a period to every
16472 address we resolve at the exit node, so that we do not accidentally
16473 pick up local addresses, and so that failing searches are retried
16474 in the resolver search domains. (This is already solved for
16475 eventdns.) (This breaks Blossom servers for now.)
16476 - If we are using an exit enclave and we can't connect, e.g. because
16477 its webserver is misconfigured to not listen on localhost, then
16478 back off and try connecting from somewhere else before we fail.
16481 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
16482 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
16483 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
16484 when the IP address is mapped through MapAddress to a hostname.
16485 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
16486 useless IPv6 DNS resolves.
16487 - Patch suggested by Karsten Loesing: respond to SIGNAL command
16488 before we execute the signal, in case the signal shuts us down.
16489 - Clean up AllowInvalidNodes man page entry.
16490 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
16491 - Add more asserts to track down an assert error on a windows Tor
16492 server with connection_add being called with socket == -1.
16493 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
16494 - Fix misleading log messages: an entry guard that is "unlisted",
16495 as well as not known to be "down" (because we've never heard
16496 of it), is not therefore "up".
16497 - Remove code to special-case "-cvs" ending, since it has not
16498 actually mattered since 0.0.9.
16499 - Make our socks5 handling more robust to broken socks clients:
16500 throw out everything waiting on the buffer in between socks
16501 handshake phases, since they can't possibly (so the theory
16502 goes) have predicted what we plan to respond to them.
16505 Changes in version 0.1.1.23 - 2006-07-30
16507 - Fast Tor servers, especially exit nodes, were triggering asserts
16508 due to a bug in handling the list of pending DNS resolves. Some
16509 bugs still remain here; we're hunting them.
16510 - Entry guards could crash clients by sending unexpected input.
16511 - More fixes on reachability testing: if you find yourself reachable,
16512 then don't ever make any client requests (so you stop predicting
16513 circuits), then hup or have your clock jump, then later your IP
16514 changes, you won't think circuits are working, so you won't try to
16515 test reachability, so you won't publish.
16518 - Avoid a crash if the controller does a resetconf firewallports
16519 and then a setconf fascistfirewall=1.
16520 - Avoid an integer underflow when the dir authority decides whether
16521 a router is stable: we might wrongly label it stable, and compute
16522 a slightly wrong median stability, when a descriptor is published
16524 - Fix a place where we might trigger an assert if we can't build our
16525 own server descriptor yet.
16528 Changes in version 0.1.1.22 - 2006-07-05
16530 - Fix a big bug that was causing servers to not find themselves
16531 reachable if they changed IP addresses. Since only 0.1.1.22+
16532 servers can do reachability testing correctly, now we automatically
16533 make sure to test via one of these.
16534 - Fix to allow clients and mirrors to learn directory info from
16535 descriptor downloads that get cut off partway through.
16536 - Directory authorities had a bug in deciding if a newly published
16537 descriptor was novel enough to make everybody want a copy -- a few
16538 servers seem to be publishing new descriptors many times a minute.
16540 - Fix a rare bug that was causing some servers to complain about
16541 "closing wedged cpuworkers" and skip some circuit create requests.
16542 - Make the Exit flag in directory status documents actually work.
16545 Changes in version 0.1.1.21 - 2006-06-10
16546 o Crash and assert fixes from 0.1.1.20:
16547 - Fix a rare crash on Tor servers that have enabled hibernation.
16548 - Fix a seg fault on startup for Tor networks that use only one
16549 directory authority.
16550 - Fix an assert from a race condition that occurs on Tor servers
16551 while exiting, where various threads are trying to log that they're
16552 exiting, and delete the logs, at the same time.
16553 - Make our unit tests pass again on certain obscure platforms.
16556 - Add support for building SUSE RPM packages.
16557 - Speed up initial bootstrapping for clients: if we are making our
16558 first ever connection to any entry guard, then don't mark it down
16560 - When only one Tor server in the network is labelled as a guard,
16561 and we've already picked him, we would cycle endlessly picking him
16562 again, being unhappy about it, etc. Now we specifically exclude
16563 current guards when picking a new guard.
16564 - Servers send create cells more reliably after the TLS connection
16565 is established: we were sometimes forgetting to send half of them
16566 when we had more than one pending.
16567 - If we get a create cell that asks us to extend somewhere, but the
16568 Tor server there doesn't match the expected digest, we now send
16569 a destroy cell back, rather than silently doing nothing.
16570 - Make options->RedirectExit work again.
16571 - Make cookie authentication for the controller work again.
16572 - Stop being picky about unusual characters in the arguments to
16573 mapaddress. It's none of our business.
16574 - Add a new config option "TestVia" that lets you specify preferred
16575 middle hops to use for test circuits. Perhaps this will let me
16576 debug the reachability problems better.
16578 o Log / documentation fixes:
16579 - If we're a server and some peer has a broken TLS certificate, don't
16580 log about it unless ProtocolWarnings is set, i.e., we want to hear
16581 about protocol violations by others.
16582 - Fix spelling of VirtualAddrNetwork in man page.
16583 - Add a better explanation at the top of the autogenerated torrc file
16584 about what happened to our old torrc.
16587 Changes in version 0.1.1.20 - 2006-05-23
16589 - Downgrade a log severity where servers complain that they're
16591 - Avoid a compile warning on FreeBSD.
16592 - Remove string size limit on NEWDESC messages; solve bug 291.
16593 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
16594 more thoroughly when we're running on windows.
16597 Changes in version 0.1.1.19-rc - 2006-05-03
16599 - Regenerate our local descriptor if it's dirty and we try to use
16600 it locally (e.g. if it changes during reachability detection).
16601 - If we setconf our ORPort to 0, we continued to listen on the
16602 old ORPort and receive connections.
16603 - Avoid a second warning about machine/limits.h on Debian
16605 - Be willing to add our own routerinfo into the routerlist.
16606 Now authorities will include themselves in their directories
16607 and network-statuses.
16608 - Stop trying to upload rendezvous descriptors to every
16609 directory authority: only try the v1 authorities.
16610 - Servers no longer complain when they think they're not
16611 registered with the directory authorities. There were too many
16613 - Backport dist-rpm changes so rpms can be built without errors.
16616 - Implement an option, VirtualAddrMask, to set which addresses
16617 get handed out in response to mapaddress requests. This works
16618 around a bug in tsocks where 127.0.0.0/8 is never socksified.
16621 Changes in version 0.1.1.18-rc - 2006-04-10
16623 - Work harder to download live network-statuses from all the
16624 directory authorities we know about. Improve the threshold
16625 decision logic so we're more robust to edge cases.
16626 - When fetching rendezvous descriptors, we were willing to ask
16627 v2 authorities too, which would always return 404.
16630 - Stop listing down or invalid nodes in the v1 directory. This will
16631 reduce its bulk by about 1/3, and reduce load on directory
16633 - When deciding whether a router is Fast or Guard-worthy, consider
16634 his advertised BandwidthRate and not just the BandwidthCapacity.
16635 - No longer ship INSTALL and README files -- they are useless now.
16636 - Force rpmbuild to behave and honor target_cpu.
16637 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
16638 - Start to include translated versions of the tor-doc-*.html
16639 files, along with the screenshots. Still needs more work.
16640 - Start sending back 512 and 451 errors if mapaddress fails,
16641 rather than not sending anything back at all.
16642 - When we fail to bind or listen on an incoming or outgoing
16643 socket, we should close it before failing. otherwise we just
16644 leak it. (thanks to weasel for finding.)
16645 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
16646 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
16647 - Make NoPublish (even though deprecated) work again.
16648 - Fix a minor security flaw where a versioning auth dirserver
16649 could list a recommended version many times in a row to make
16650 clients more convinced that it's recommended.
16651 - Fix crash bug if there are two unregistered servers running
16652 with the same nickname, one of them is down, and you ask for
16653 them by nickname in your EntryNodes or ExitNodes. Also, try
16654 to pick the one that's running rather than an arbitrary one.
16655 - Fix an infinite loop we could hit if we go offline for too long.
16656 - Complain when we hit WSAENOBUFS on recv() or write() too.
16657 Perhaps this will help us hunt the bug.
16658 - If you're not a versioning dirserver, don't put the string
16659 "client-versions \nserver-versions \n" in your network-status.
16660 - Lower the minimum required number of file descriptors to 1000,
16661 so we can have some overhead for Valgrind on Linux, where the
16662 default ulimit -n is 1024.
16665 - Add tor.dizum.com as the fifth authoritative directory server.
16666 - Add a new config option FetchUselessDescriptors, off by default,
16667 for when you plan to run "exitlist" on your client and you want
16668 to know about even the non-running descriptors.
16671 Changes in version 0.1.1.17-rc - 2006-03-28
16673 - Clients and servers since 0.1.1.10-alpha have been expiring
16674 connections whenever they are idle for 5 minutes and they *do*
16675 have circuits on them. Oops. With this new version, clients will
16676 discard their previous entry guard choices and avoid choosing
16677 entry guards running these flawed versions.
16678 - Fix memory leak when uncompressing concatenated zlib streams. This
16679 was causing substantial leaks over time on Tor servers.
16680 - The v1 directory was including servers as much as 48 hours old,
16681 because that's how the new routerlist->routers works. Now only
16682 include them if they're 20 hours old or less.
16685 - Resume building on irix64, netbsd 2.0, etc.
16686 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
16688 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
16689 and it is confusing some users.
16690 - Mirrors stop caching the v1 directory so often.
16691 - Make the max number of old descriptors that a cache will hold
16692 rise with the number of directory authorities, so we can scale.
16693 - Change our win32 uname() hack to be more forgiving about what
16694 win32 versions it thinks it's found.
16697 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
16699 - When the controller's *setconf commands fail, collect an error
16700 message in a string and hand it back to the controller.
16701 - Make the v2 dir's "Fast" flag based on relative capacity, just
16702 like "Stable" is based on median uptime. Name everything in the
16703 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
16704 - Log server fingerprint on startup, so new server operators don't
16705 have to go hunting around their filesystem for it.
16706 - Return a robots.txt on our dirport to discourage google indexing.
16707 - Let the controller ask for GETINFO dir/status/foo so it can ask
16708 directly rather than connecting to the dir port. Only works when
16709 dirport is set for now.
16711 o New config options rather than constants in the code:
16712 - SocksTimeout: How long do we let a socks connection wait
16713 unattached before we fail it?
16714 - CircuitBuildTimeout: Cull non-open circuits that were born
16715 at least this many seconds ago.
16716 - CircuitIdleTimeout: Cull open clean circuits that were born
16717 at least this many seconds ago.
16720 Changes in version 0.1.1.16-rc - 2006-03-18
16721 o Bugfixes on 0.1.1.15-rc:
16722 - Fix assert when the controller asks to attachstream a connect-wait
16723 or resolve-wait stream.
16724 - Now do address rewriting when the controller asks us to attach
16725 to a particular circuit too. This will let Blossom specify
16726 "moria2.exit" without having to learn what moria2's IP address is.
16727 - Make the "tor --verify-config" command-line work again, so people
16728 can automatically check if their torrc will parse.
16729 - Authoritative dirservers no longer require an open connection from
16730 a server to consider him "reachable". We need this change because
16731 when we add new auth dirservers, old servers won't know not to
16733 - Let Tor build on Sun CC again.
16734 - Fix an off-by-one buffer size in dirserv.c that magically never
16735 hit our three authorities but broke sjmurdoch's own tor network.
16736 - If we as a directory mirror don't know of any v1 directory
16737 authorities, then don't try to cache any v1 directories.
16738 - Stop warning about unknown servers in our family when they are
16739 given as hex digests.
16740 - Stop complaining as quickly to the server operator that he
16741 hasn't registered his nickname/key binding.
16742 - Various cleanups so we can add new V2 Auth Dirservers.
16743 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
16744 reflect the updated flags in our v2 dir protocol.
16745 - Resume allowing non-printable characters for exit streams (both
16746 for connecting and for resolving). Now we tolerate applications
16747 that don't follow the RFCs. But continue to block malformed names
16750 o Bugfixes on 0.1.0.x:
16751 - Fix assert bug in close_logs(): when we close and delete logs,
16752 remove them all from the global "logfiles" list.
16753 - Fix minor integer overflow in calculating when we expect to use up
16754 our bandwidth allocation before hibernating.
16755 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
16756 there are multiple SSLs installed with different versions.
16757 - When we try to be a server and Address is not explicitly set and
16758 our hostname resolves to a private IP address, try to use an
16759 interface address if it has a public address. Now Windows machines
16760 that think of themselves as localhost can work by default.
16763 - Let the controller ask for GETINFO dir/server/foo so it can ask
16764 directly rather than connecting to the dir port.
16765 - Let the controller tell us about certain router descriptors
16766 that it doesn't want Tor to use in circuits. Implement
16767 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
16768 - New config option SafeSocks to reject all application connections
16769 using unsafe socks protocols. Defaults to off.
16772 Changes in version 0.1.1.15-rc - 2006-03-11
16773 o Bugfixes and cleanups:
16774 - When we're printing strings from the network, don't try to print
16775 non-printable characters. This protects us against shell escape
16776 sequence exploits, and also against attacks to fool humans into
16777 misreading their logs.
16778 - Fix a bug where Tor would fail to establish any connections if you
16779 left it off for 24 hours and then started it: we were happy with
16780 the obsolete network statuses, but they all referred to router
16781 descriptors that were too old to fetch, so we ended up with no
16782 valid router descriptors.
16783 - Fix a seg fault in the controller's "getinfo orconn-status"
16784 command while listing status on incoming handshaking connections.
16785 Introduce a status name "NEW" for these connections.
16786 - If we get a linelist or linelist_s config option from the torrc
16787 (e.g. ExitPolicy) and it has no value, warn and skip rather than
16788 silently resetting it to its default.
16789 - Don't abandon entry guards until they've been down or gone for
16791 - Cleaner and quieter log messages.
16794 - New controller signal NEWNYM that makes new application requests
16795 use clean circuits.
16796 - Add a new circuit purpose 'controller' to let the controller ask
16797 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
16798 controller command to let you specify the purpose if you're
16799 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
16800 command to let you change a circuit's purpose after it's been
16802 - Accept "private:*" in routerdesc exit policies; not generated yet
16803 because older Tors do not understand it.
16804 - Add BSD-style contributed startup script "rc.subr" from Peter
16808 Changes in version 0.1.1.14-alpha - 2006-02-20
16809 o Bugfixes on 0.1.1.x:
16810 - Don't die if we ask for a stdout or stderr log (even implicitly)
16811 and we're set to RunAsDaemon -- just warn.
16812 - We still had a few bugs in the OR connection rotation code that
16813 caused directory servers to slowly aggregate connections to other
16814 fast Tor servers. This time for sure!
16815 - Make log entries on Win32 include the name of the function again.
16816 - We were treating a pair of exit policies if they were equal even
16817 if one said accept and the other said reject -- causing us to
16818 not always publish a new descriptor since we thought nothing
16820 - Retry pending server downloads as well as pending networkstatus
16821 downloads when we unexpectedly get a socks request.
16822 - We were ignoring the IS_FAST flag in the directory status,
16823 meaning we were willing to pick trivial-bandwidth nodes for "fast"
16825 - If the controller's SAVECONF command fails (e.g. due to file
16826 permissions), let the controller know that it failed.
16829 - If we're trying to be a Tor server and running Windows 95/98/ME
16830 as a server, explain that we'll likely crash.
16831 - When we're a server, a client asks for an old-style directory,
16832 and our write bucket is empty, don't give it to him. This way
16833 small servers can continue to serve the directory *sometimes*,
16834 without getting overloaded.
16835 - Compress exit policies even more -- look for duplicate lines
16837 - Clients now honor the "guard" flag in the router status when
16838 picking entry guards, rather than looking at is_fast or is_stable.
16839 - Retain unrecognized lines in $DATADIR/state file, so that we can
16840 be forward-compatible.
16841 - Generate 18.0.0.0/8 address policy format in descs when we can;
16842 warn when the mask is not reducible to a bit-prefix.
16843 - Let the user set ControlListenAddress in the torrc. This can be
16844 dangerous, but there are some cases (like a secured LAN) where it
16846 - Split ReachableAddresses into ReachableDirAddresses and
16847 ReachableORAddresses, so we can restrict Dir conns to port 80
16848 and OR conns to port 443.
16849 - Now we can target arch and OS in rpm builds (contributed by
16850 Phobos). Also make the resulting dist-rpm filename match the
16852 - New config options to help controllers: FetchServerDescriptors
16853 and FetchHidServDescriptors for whether to fetch server
16854 info and hidserv info or let the controller do it, and
16855 PublishServerDescriptor and PublishHidServDescriptors.
16856 - Also let the controller set the __AllDirActionsPrivate config
16857 option if you want all directory fetches/publishes to happen via
16858 Tor (it assumes your controller bootstraps your circuits).
16861 Changes in version 0.1.0.17 - 2006-02-17
16862 o Crash bugfixes on 0.1.0.x:
16863 - When servers with a non-zero DirPort came out of hibernation,
16864 sometimes they would trigger an assert.
16866 o Other important bugfixes:
16867 - On platforms that don't have getrlimit (like Windows), we were
16868 artificially constraining ourselves to a max of 1024
16869 connections. Now just assume that we can handle as many as 15000
16870 connections. Hopefully this won't cause other problems.
16872 o Backported features:
16873 - When we're a server, a client asks for an old-style directory,
16874 and our write bucket is empty, don't give it to him. This way
16875 small servers can continue to serve the directory *sometimes*,
16876 without getting overloaded.
16877 - Whenever you get a 503 in response to a directory fetch, try
16878 once more. This will become important once servers start sending
16879 503's whenever they feel busy.
16880 - Fetch a new directory every 120 minutes, not every 40 minutes.
16881 Now that we have hundreds of thousands of users running the old
16882 directory algorithm, it's starting to hurt a lot.
16883 - Bump up the period for forcing a hidden service descriptor upload
16884 from 20 minutes to 1 hour.
16887 Changes in version 0.1.1.13-alpha - 2006-02-09
16888 o Crashes in 0.1.1.x:
16889 - When you tried to setconf ORPort via the controller, Tor would
16890 crash. So people using TorCP to become a server were sad.
16891 - Solve (I hope) the stack-smashing bug that we were seeing on fast
16892 servers. The problem appears to be something do with OpenSSL's
16893 random number generation, or how we call it, or something. Let me
16894 know if the crashes continue.
16895 - Turn crypto hardware acceleration off by default, until we find
16896 somebody smart who can test it for us. (It appears to produce
16897 seg faults in at least some cases.)
16898 - Fix a rare assert error when we've tried all intro points for
16899 a hidden service and we try fetching the service descriptor again:
16900 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
16903 - Fix a major load balance bug: we were round-robining in 16 KB
16904 chunks, and servers with bandwidthrate of 20 KB, while downloading
16905 a 600 KB directory, would starve their other connections. Now we
16906 try to be a bit more fair.
16907 - Dir authorities and mirrors were never expiring the newest
16908 descriptor for each server, causing memory and directory bloat.
16909 - Fix memory-bloating and connection-bloating bug on servers: We
16910 were never closing any connection that had ever had a circuit on
16911 it, because we were checking conn->n_circuits == 0, yet we had a
16912 bug that let it go negative.
16913 - Make Tor work using squid as your http proxy again -- squid
16914 returns an error if you ask for a URL that's too long, and it uses
16915 a really generic error message. Plus, many people are behind a
16916 transparent squid so they don't even realize it.
16917 - On platforms that don't have getrlimit (like Windows), we were
16918 artificially constraining ourselves to a max of 1024
16919 connections. Now just assume that we can handle as many as 15000
16920 connections. Hopefully this won't cause other problems.
16921 - Add a new config option ExitPolicyRejectPrivate which defaults to
16922 1. This means all exit policies will begin with rejecting private
16923 addresses, unless the server operator explicitly turns it off.
16926 - Clients no longer download descriptors for non-running
16928 - Before we add new directory authorities, we should make it
16929 clear that only v1 authorities should receive/publish hidden
16930 service descriptors.
16933 - As soon as we've fetched some more directory info, immediately
16934 try to download more server descriptors. This way we don't have
16935 a 10 second pause during initial bootstrapping.
16936 - Remove even more loud log messages that the server operator can't
16938 - When we're running an obsolete or un-recommended version, make
16939 the log message more clear about what the problem is and what
16940 versions *are* still recommended.
16941 - Provide a more useful warn message when our onion queue gets full:
16942 the CPU is too slow or the exit policy is too liberal.
16943 - Don't warn when we receive a 503 from a dirserver/cache -- this
16944 will pave the way for them being able to refuse if they're busy.
16945 - When we fail to bind a listener, try to provide a more useful
16946 log message: e.g., "Is Tor already running?"
16947 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
16948 Goldberg can prove things about our handshake protocol more
16950 - MaxConn has been obsolete for a while now. Document the ConnLimit
16951 config option, which is a *minimum* number of file descriptors
16952 that must be available else Tor refuses to start.
16953 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
16954 if you log to syslog and want something other than LOG_DAEMON.
16955 - Make dirservers generate a separate "guard" flag to mean,
16956 "would make a good entry guard". Make clients parse it and vote
16957 on it. Not used by clients yet.
16958 - Implement --with-libevent-dir option to ./configure. Also, improve
16959 search techniques to find libevent, and use those for openssl too.
16960 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
16961 - Only start testing reachability once we've established a
16962 circuit. This will make startup on dirservers less noisy.
16963 - Don't try to upload hidden service descriptors until we have
16964 established a circuit.
16965 - Fix the controller's "attachstream 0" command to treat conn like
16966 it just connected, doing address remapping, handling .exit and
16967 .onion idioms, and so on. Now we're more uniform in making sure
16968 that the controller hears about new and closing connections.
16971 Changes in version 0.1.1.12-alpha - 2006-01-11
16972 o Bugfixes on 0.1.1.x:
16973 - The fix to close duplicate server connections was closing all
16974 Tor client connections if they didn't establish a circuit
16975 quickly enough. Oops.
16976 - Fix minor memory issue (double-free) that happened on exit.
16978 o Bugfixes on 0.1.0.x:
16979 - Tor didn't warn when it failed to open a log file.
16982 Changes in version 0.1.1.11-alpha - 2006-01-10
16983 o Crashes in 0.1.1.x:
16984 - Include all the assert/crash fixes from 0.1.0.16.
16985 - If you start Tor and then quit very quickly, there were some
16986 races that tried to free things that weren't allocated yet.
16987 - Fix a rare memory stomp if you're running hidden services.
16988 - Fix segfault when specifying DirServer in config without nickname.
16989 - Fix a seg fault when you finish connecting to a server but at
16990 that moment you dump his server descriptor.
16991 - Extendcircuit and Attachstream controller commands would
16992 assert/crash if you don't give them enough arguments.
16993 - Fix an assert error when we're out of space in the connection_list
16994 and we try to post a hidden service descriptor (reported by weasel).
16995 - If you specify a relative torrc path and you set RunAsDaemon in
16996 your torrc, then it chdir()'s to the new directory. If you HUP,
16997 it tries to load the new torrc location, fails, and exits.
16998 The fix: no longer allow a relative path to torrc using -f.
17001 - Implement "entry guards": automatically choose a handful of entry
17002 nodes and stick with them for all circuits. Only pick new guards
17003 when the ones you have are unsuitable, and if the old guards
17004 become suitable again, switch back. This will increase security
17005 dramatically against certain end-point attacks. The EntryNodes
17006 config option now provides some hints about which entry guards you
17007 want to use most; and StrictEntryNodes means to only use those.
17008 - New directory logic: download by descriptor digest, not by
17009 fingerprint. Caches try to download all listed digests from
17010 authorities; clients try to download "best" digests from caches.
17011 This avoids partitioning and isolating attacks better.
17012 - Make the "stable" router flag in network-status be the median of
17013 the uptimes of running valid servers, and make clients pay
17014 attention to the network-status flags. Thus the cutoff adapts
17015 to the stability of the network as a whole, making IRC, IM, etc
17016 connections more reliable.
17019 - Tor servers with dynamic IP addresses were needing to wait 18
17020 hours before they could start doing reachability testing using
17021 the new IP address and ports. This is because they were using
17022 the internal descriptor to learn what to test, yet they were only
17023 rebuilding the descriptor once they decided they were reachable.
17024 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
17025 to download certain server descriptors, throw them away, and then
17026 fetch them again after 30 minutes. Now mirrors throw away these
17027 server descriptors so clients can't get them.
17028 - We were leaving duplicate connections to other ORs open for a week,
17029 rather than closing them once we detect a duplicate. This only
17030 really affected authdirservers, but it affected them a lot.
17031 - Spread the authdirservers' reachability testing over the entire
17032 testing interval, so we don't try to do 500 TLS's at once every
17036 - If the network is down, and we try to connect to a conn because
17037 we have a circuit in mind, and we timeout (30 seconds) because the
17038 network never answers, we were expiring the circuit, but we weren't
17039 obsoleting the connection or telling the entry_guards functions.
17040 - Some Tor servers process billions of cells per day. These statistics
17041 need to be uint64_t's.
17042 - Check for integer overflows in more places, when adding elements
17043 to smartlists. This could possibly prevent a buffer overflow
17044 on malicious huge inputs. I don't see any, but I haven't looked
17046 - ReachableAddresses kept growing new "reject *:*" lines on every
17048 - When you "setconf log" via the controller, it should remove all
17049 logs. We were automatically adding back in a "log notice stdout".
17050 - Newly bootstrapped Tor networks couldn't establish hidden service
17051 circuits until they had nodes with high uptime. Be more tolerant.
17052 - We were marking servers down when they could not answer every piece
17053 of the directory request we sent them. This was far too harsh.
17054 - Fix the torify (tsocks) config file to not use Tor for localhost
17056 - Directory authorities now go to the proper authority when asking for
17057 a networkstatus, even when they want a compressed one.
17058 - Fix a harmless bug that was causing Tor servers to log
17059 "Got an end because of misc error, but we're not an AP. Closing."
17060 - Authorities were treating their own descriptor changes as cosmetic,
17061 meaning the descriptor available in the network-status and the
17062 descriptor that clients downloaded were different.
17063 - The OS X installer was adding a symlink for tor_resolve but
17064 the binary was called tor-resolve (reported by Thomas Hardly).
17065 - Workaround a problem with some http proxies where they refuse GET
17066 requests that specify "Content-Length: 0" (reported by Adrian).
17067 - Fix wrong log message when you add a "HiddenServiceNodes" config
17068 line without any HiddenServiceDir line (reported by Chris Thomas).
17071 - Write the TorVersion into the state file so we have a prayer of
17072 keeping forward and backward compatibility.
17073 - Revive the FascistFirewall config option rather than eliminating it:
17074 now it's a synonym for ReachableAddresses *:80,*:443.
17075 - Clients choose directory servers from the network status lists,
17076 not from their internal list of router descriptors. Now they can
17077 go to caches directly rather than needing to go to authorities
17079 - Directory authorities ignore router descriptors that have only
17080 cosmetic differences: do this for 0.1.0.x servers now too.
17081 - Add a new flag to network-status indicating whether the server
17082 can answer v2 directory requests too.
17083 - Authdirs now stop whining so loudly about bad descriptors that
17084 they fetch from other dirservers. So when there's a log complaint,
17085 it's for sure from a freshly uploaded descriptor.
17086 - Reduce memory requirements in our structs by changing the order
17088 - There used to be two ways to specify your listening ports in a
17089 server descriptor: on the "router" line and with a separate "ports"
17090 line. Remove support for the "ports" line.
17091 - New config option "AuthDirRejectUnlisted" for auth dirservers as
17092 a panic button: if we get flooded with unusable servers we can
17093 revert to only listing servers in the approved-routers file.
17094 - Auth dir servers can now mark a fingerprint as "!reject" or
17095 "!invalid" in the approved-routers file (as its nickname), to
17096 refuse descriptors outright or include them but marked as invalid.
17097 - Servers store bandwidth history across restarts/crashes.
17098 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
17099 get a better idea of why their circuits failed. Not used yet.
17100 - Directory mirrors now cache up to 16 unrecognized network-status
17101 docs. Now we can add new authdirservers and they'll be cached too.
17102 - When picking a random directory, prefer non-authorities if any
17104 - New controller option "getinfo desc/all-recent" to fetch the
17105 latest server descriptor for every router that Tor knows about.
17108 Changes in version 0.1.0.16 - 2006-01-02
17109 o Crash bugfixes on 0.1.0.x:
17110 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
17111 corrupting the heap, losing FDs, or crashing when we need to resize
17112 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
17113 - It turns out sparc64 platforms crash on unaligned memory access
17114 too -- so detect and avoid this.
17115 - Handle truncated compressed data correctly (by detecting it and
17117 - Fix possible-but-unlikely free(NULL) in control.c.
17118 - When we were closing connections, there was a rare case that
17119 stomped on memory, triggering seg faults and asserts.
17120 - Avoid potential infinite recursion when building a descriptor. (We
17121 don't know that it ever happened, but better to fix it anyway.)
17122 - We were neglecting to unlink marked circuits from soon-to-close OR
17123 connections, which caused some rare scribbling on freed memory.
17124 - Fix a memory stomping race bug when closing the joining point of two
17125 rendezvous circuits.
17126 - Fix an assert in time parsing found by Steven Murdoch.
17128 o Other bugfixes on 0.1.0.x:
17129 - When we're doing reachability testing, provide more useful log
17130 messages so the operator knows what to expect.
17131 - Do not check whether DirPort is reachable when we are suppressing
17132 advertising it because of hibernation.
17133 - When building with -static or on Solaris, we sometimes needed -ldl.
17134 - When we're deciding whether a stream has enough circuits around
17135 that can handle it, count the freshly dirty ones and not the ones
17136 that are so dirty they won't be able to handle it.
17137 - When we're expiring old circuits, we had a logic error that caused
17138 us to close new rendezvous circuits rather than old ones.
17139 - Give a more helpful log message when you try to change ORPort via
17140 the controller: you should upgrade Tor if you want that to work.
17141 - We were failing to parse Tor versions that start with "Tor ".
17142 - Tolerate faulty streams better: when a stream fails for reason
17143 exitpolicy, stop assuming that the router is lying about his exit
17144 policy. When a stream fails for reason misc, allow it to retry just
17145 as if it was resolvefailed. When a stream has failed three times,
17146 reset its failure count so we can try again and get all three tries.
17149 Changes in version 0.1.1.10-alpha - 2005-12-11
17150 o Correctness bugfixes on 0.1.0.x:
17151 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
17152 corrupting the heap, losing FDs, or crashing when we need to resize
17153 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
17154 - Stop doing the complex voodoo overkill checking for insecure
17155 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
17156 - When we were closing connections, there was a rare case that
17157 stomped on memory, triggering seg faults and asserts.
17158 - We were neglecting to unlink marked circuits from soon-to-close OR
17159 connections, which caused some rare scribbling on freed memory.
17160 - When we're deciding whether a stream has enough circuits around
17161 that can handle it, count the freshly dirty ones and not the ones
17162 that are so dirty they won't be able to handle it.
17163 - Recover better from TCP connections to Tor servers that are
17164 broken but don't tell you (it happens!); and rotate TLS
17165 connections once a week.
17166 - When we're expiring old circuits, we had a logic error that caused
17167 us to close new rendezvous circuits rather than old ones.
17168 - Fix a scary-looking but apparently harmless bug where circuits
17169 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
17170 servers, and never switch to state CIRCUIT_STATE_OPEN.
17171 - When building with -static or on Solaris, we sometimes needed to
17173 - Give a useful message when people run Tor as the wrong user,
17174 rather than telling them to start chowning random directories.
17175 - We were failing to inform the controller about new .onion streams.
17177 o Security bugfixes on 0.1.0.x:
17178 - Refuse server descriptors if the fingerprint line doesn't match
17179 the included identity key. Tor doesn't care, but other apps (and
17180 humans) might actually be trusting the fingerprint line.
17181 - We used to kill the circuit when we receive a relay command we
17182 don't recognize. Now we just drop it.
17183 - Start obeying our firewall options more rigorously:
17184 . If we can't get to a dirserver directly, try going via Tor.
17185 . Don't ever try to connect (as a client) to a place our
17186 firewall options forbid.
17187 . If we specify a proxy and also firewall options, obey the
17188 firewall options even when we're using the proxy: some proxies
17189 can only proxy to certain destinations.
17190 - Fix a bug found by Lasse Overlier: when we were making internal
17191 circuits (intended to be cannibalized later for rendezvous and
17192 introduction circuits), we were picking them so that they had
17193 useful exit nodes. There was no need for this, and it actually
17194 aids some statistical attacks.
17195 - Start treating internal circuits and exit circuits separately.
17196 It's important to keep them separate because internal circuits
17197 have their last hops picked like middle hops, rather than like
17198 exit hops. So exiting on them will break the user's expectations.
17200 o Bugfixes on 0.1.1.x:
17201 - Take out the mis-feature where we tried to detect IP address
17202 flapping for people with DynDNS, and chose not to upload a new
17203 server descriptor sometimes.
17204 - Try to be compatible with OpenSSL 0.9.6 again.
17205 - Log fix: when the controller is logging about .onion addresses,
17206 sometimes it didn't include the ".onion" part of the address.
17207 - Don't try to modify options->DirServers internally -- if the
17208 user didn't specify any, just add the default ones directly to
17209 the trusted dirserver list. This fixes a bug where people running
17210 controllers would use SETCONF on some totally unrelated config
17211 option, and Tor would start yelling at them about changing their
17213 - Let the controller's redirectstream command specify a port, in
17214 case the controller wants to change that too.
17215 - When we requested a pile of server descriptors, we sometimes
17216 accidentally launched a duplicate request for the first one.
17217 - Bugfix for trackhostexits: write down the fingerprint of the
17218 chosen exit, not its nickname, because the chosen exit might not
17220 - When parsing foo.exit, if foo is unknown, and we are leaving
17221 circuits unattached, set the chosen_exit field and leave the
17222 address empty. This matters because controllers got confused
17224 - Directory authorities no longer try to download server
17225 descriptors that they know they will reject.
17227 o Features and updates:
17228 - Replace balanced trees with hash tables: this should make stuff
17229 significantly faster.
17230 - Resume using the AES counter-mode implementation that we ship,
17231 rather than OpenSSL's. Ours is significantly faster.
17232 - Many other CPU and memory improvements.
17233 - Add a new config option FastFirstHopPK (on by default) so clients
17234 do a trivial crypto handshake for their first hop, since TLS has
17235 already taken care of confidentiality and authentication.
17236 - Add a new config option TestSocks so people can see if their
17237 applications are using socks4, socks4a, socks5-with-ip, or
17238 socks5-with-hostname. This way they don't have to keep mucking
17239 with tcpdump and wondering if something got cached somewhere.
17240 - Warn when listening on a public address for socks. I suspect a
17241 lot of people are setting themselves up as open socks proxies,
17242 and they have no idea that jerks on the Internet are using them,
17243 since they simply proxy the traffic into the Tor network.
17244 - Add "private:*" as an alias in configuration for policies. Now
17245 you can simplify your exit policy rather than needing to list
17246 every single internal or nonroutable network space.
17247 - Add a new controller event type that allows controllers to get
17248 all server descriptors that were uploaded to a router in its role
17249 as authoritative dirserver.
17250 - Start shipping socks-extensions.txt, tor-doc-unix.html,
17251 tor-doc-server.html, and stylesheet.css in the tarball.
17252 - Stop shipping tor-doc.html in the tarball.
17255 Changes in version 0.1.1.9-alpha - 2005-11-15
17256 o Usability improvements:
17257 - Start calling it FooListenAddress rather than FooBindAddress,
17258 since few of our users know what it means to bind an address
17260 - Reduce clutter in server logs. We're going to try to make
17261 them actually usable now. New config option ProtocolWarnings that
17262 lets you hear about how _other Tors_ are breaking the protocol. Off
17264 - Divide log messages into logging domains. Once we put some sort
17265 of interface on this, it will let people looking at more verbose
17266 log levels specify the topics they want to hear more about.
17267 - Make directory servers return better http 404 error messages
17268 instead of a generic "Servers unavailable".
17269 - Check for even more Windows version flags when writing the platform
17270 string in server descriptors, and note any we don't recognize.
17271 - Clean up more of the OpenSSL memory when exiting, so we can detect
17272 memory leaks better.
17273 - Make directory authorities be non-versioning, non-naming by
17274 default. Now we can add new directory servers without requiring
17275 their operators to pay close attention.
17276 - When logging via syslog, include the pid whenever we provide
17277 a log entry. Suggested by Todd Fries.
17279 o Performance improvements:
17280 - Directory servers now silently throw away new descriptors that
17281 haven't changed much if the timestamps are similar. We do this to
17282 tolerate older Tor servers that upload a new descriptor every 15
17283 minutes. (It seemed like a good idea at the time.)
17284 - Inline bottleneck smartlist functions; use fast versions by default.
17285 - Add a "Map from digest to void*" abstraction digestmap_t so we
17286 can do less hex encoding/decoding. Use it in router_get_by_digest()
17287 to resolve a performance bottleneck.
17288 - Allow tor_gzip_uncompress to extract as much as possible from
17289 truncated compressed data. Try to extract as many
17290 descriptors as possible from truncated http responses (when
17291 DIR_PURPOSE_FETCH_ROUTERDESC).
17292 - Make circ->onionskin a pointer, not a static array. moria2 was using
17293 125000 circuit_t's after it had been up for a few weeks, which
17294 translates to 20+ megs of wasted space.
17295 - The private half of our EDH handshake keys are now chosen out
17296 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
17298 o Security improvements:
17299 - Start making directory caches retain old routerinfos, so soon
17300 clients can start asking by digest of descriptor rather than by
17301 fingerprint of server.
17302 - Add half our entropy from RAND_poll in OpenSSL. This knows how
17303 to use egd (if present), openbsd weirdness (if present), vms/os2
17304 weirdness (if we ever port there), and more in the future.
17306 o Bugfixes on 0.1.0.x:
17307 - Do round-robin writes of at most 16 kB per write. This might be
17308 more fair on loaded Tor servers, and it might resolve our Windows
17309 crash bug. It might also slow things down.
17310 - Our TLS handshakes were generating a single public/private
17311 keypair for the TLS context, rather than making a new one for
17312 each new connections. Oops. (But we were still rotating them
17313 periodically, so it's not so bad.)
17314 - When we were cannibalizing a circuit with a particular exit
17315 node in mind, we weren't checking to see if that exit node was
17316 already present earlier in the circuit. Oops.
17317 - When a Tor server's IP changes (e.g. from a dyndns address),
17318 upload a new descriptor so clients will learn too.
17319 - Really busy servers were keeping enough circuits open on stable
17320 connections that they were wrapping around the circuit_id
17321 space. (It's only two bytes.) This exposed a bug where we would
17322 feel free to reuse a circuit_id even if it still exists but has
17323 been marked for close. Try to fix this bug. Some bug remains.
17324 - If we would close a stream early (e.g. it asks for a .exit that
17325 we know would refuse it) but the LeaveStreamsUnattached config
17326 option is set by the controller, then don't close it.
17328 o Bugfixes on 0.1.1.8-alpha:
17329 - Fix a big pile of memory leaks, some of them serious.
17330 - Do not try to download a routerdesc if we would immediately reject
17332 - Resume inserting a newline between all router descriptors when
17333 generating (old style) signed directories, since our spec says
17335 - When providing content-type application/octet-stream for
17336 server descriptors using .z, we were leaving out the
17337 content-encoding header. Oops. (Everything tolerated this just
17338 fine, but that doesn't mean we need to be part of the problem.)
17339 - Fix a potential seg fault in getconf and getinfo using version 1
17340 of the controller protocol.
17341 - Avoid crash: do not check whether DirPort is reachable when we
17342 are suppressing it because of hibernation.
17343 - Make --hash-password not crash on exit.
17346 Changes in version 0.1.1.8-alpha - 2005-10-07
17347 o New features (major):
17348 - Clients don't download or use the directory anymore. Now they
17349 download and use network-statuses from the trusted dirservers,
17350 and fetch individual server descriptors as needed from mirrors.
17351 See dir-spec.txt for all the gory details.
17352 - Be more conservative about whether to advertise our DirPort.
17353 The main change is to not advertise if we're running at capacity
17354 and either a) we could hibernate or b) our capacity is low and
17355 we're using a default DirPort.
17356 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
17358 o New features (minor):
17359 - Try to be smart about when to retry network-status and
17360 server-descriptor fetches. Still needs some tuning.
17361 - Stop parsing, storing, or using running-routers output (but
17362 mirrors still cache and serve it).
17363 - Consider a threshold of versioning dirservers (dirservers who have
17364 an opinion about which Tor versions are still recommended) before
17365 deciding whether to warn the user that he's obsolete.
17366 - Dirservers can now reject/invalidate by key and IP, with the
17367 config options "AuthDirInvalid" and "AuthDirReject". This is
17368 useful since currently we automatically list servers as running
17369 and usable even if we know they're jerks.
17370 - Provide dire warnings to any users who set DirServer; move it out
17371 of torrc.sample and into torrc.complete.
17372 - Add MyFamily to torrc.sample in the server section.
17373 - Add nicknames to the DirServer line, so we can refer to them
17374 without requiring all our users to memorize their IP addresses.
17375 - When we get an EOF or a timeout on a directory connection, note
17376 how many bytes of serverdesc we are dropping. This will help
17377 us determine whether it is smart to parse incomplete serverdesc
17379 - Add a new function to "change pseudonyms" -- that is, to stop
17380 using any currently-dirty circuits for new streams, so we don't
17381 link new actions to old actions. Currently it's only called on
17382 HUP (or SIGNAL RELOAD).
17383 - On sighup, if UseHelperNodes changed to 1, use new circuits.
17384 - Start using RAND_bytes rather than RAND_pseudo_bytes from
17385 OpenSSL. Also, reseed our entropy every hour, not just at
17386 startup. And entropy in 512-bit chunks, not 160-bit chunks.
17388 o Fixes on 0.1.1.7-alpha:
17389 - Nobody ever implemented EVENT_ADDRMAP for control protocol
17390 version 0, so don't let version 0 controllers ask for it.
17391 - If you requested something with too many newlines via the
17392 v1 controller protocol, you could crash tor.
17393 - Fix a number of memory leaks, including some pretty serious ones.
17394 - Re-enable DirPort testing again, so Tor servers will be willing
17395 to advertise their DirPort if it's reachable.
17396 - On TLS handshake, only check the other router's nickname against
17397 its expected nickname if is_named is set.
17399 o Fixes forward-ported from 0.1.0.15:
17400 - Don't crash when we don't have any spare file descriptors and we
17401 try to spawn a dns or cpu worker.
17402 - Make the numbers in read-history and write-history into uint64s,
17403 so they don't overflow and publish negatives in the descriptor.
17405 o Fixes on 0.1.0.x:
17406 - For the OS X package's modified privoxy config file, comment
17407 out the "logfile" line so we don't log everything passed
17409 - We were whining about using socks4 or socks5-with-local-lookup
17410 even when it's an IP in the "virtual" range we designed exactly
17412 - We were leaking some memory every time the client changes IPs.
17413 - Never call free() on tor_malloc()d memory. This will help us
17414 use dmalloc to detect memory leaks.
17415 - Check for named servers when looking them up by nickname;
17416 warn when we'recalling a non-named server by its nickname;
17417 don't warn twice about the same name.
17418 - Try to list MyFamily elements by key, not by nickname, and warn
17419 if we've not heard of the server.
17420 - Make windows platform detection (uname equivalent) smarter.
17421 - It turns out sparc64 doesn't like unaligned access either.
17424 Changes in version 0.1.0.15 - 2005-09-23
17425 o Bugfixes on 0.1.0.x:
17426 - Reject ports 465 and 587 (spam targets) in default exit policy.
17427 - Don't crash when we don't have any spare file descriptors and we
17428 try to spawn a dns or cpu worker.
17429 - Get rid of IgnoreVersion undocumented config option, and make us
17430 only warn, never exit, when we're running an obsolete version.
17431 - Don't try to print a null string when your server finds itself to
17432 be unreachable and the Address config option is empty.
17433 - Make the numbers in read-history and write-history into uint64s,
17434 so they don't overflow and publish negatives in the descriptor.
17435 - Fix a minor memory leak in smartlist_string_remove().
17436 - We were only allowing ourselves to upload a server descriptor at
17437 most every 20 minutes, even if it changed earlier than that.
17438 - Clean up log entries that pointed to old URLs.
17441 Changes in version 0.1.1.7-alpha - 2005-09-14
17442 o Fixes on 0.1.1.6-alpha:
17443 - Exit servers were crashing when people asked them to make a
17444 connection to an address not in their exit policy.
17445 - Looking up a non-existent stream for a v1 control connection would
17447 - Fix a seg fault if we ask a dirserver for a descriptor by
17448 fingerprint but he doesn't know about him.
17449 - SETCONF was appending items to linelists, not clearing them.
17450 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
17451 out and refuse the setconf if it would fail.
17452 - Downgrade the dirserver log messages when whining about
17456 - Add Peter Palfrader's check-tor script to tor/contrib/
17457 It lets you easily check whether a given server (referenced by
17458 nickname) is reachable by you.
17459 - Numerous changes to move towards client-side v2 directories. Not
17462 o Fixes on 0.1.0.x:
17463 - If the user gave tor an odd number of command-line arguments,
17464 we were silently ignoring the last one. Now we complain and fail.
17465 [This wins the oldest-bug prize -- this bug has been present since
17466 November 2002, as released in Tor 0.0.0.]
17467 - Do not use unaligned memory access on alpha, mips, or mipsel.
17468 It *works*, but is very slow, so we treat them as if it doesn't.
17469 - Retry directory requests if we fail to get an answer we like
17470 from a given dirserver (we were retrying before, but only if
17471 we fail to connect).
17472 - When writing the RecommendedVersions line, sort them first.
17473 - When the client asked for a rendezvous port that the hidden
17474 service didn't want to provide, we were sending an IP address
17475 back along with the end cell. Fortunately, it was zero. But stop
17477 - Correct "your server is reachable" log entries to indicate that
17478 it was self-testing that told us so.
17481 Changes in version 0.1.1.6-alpha - 2005-09-09
17482 o Fixes on 0.1.1.5-alpha:
17483 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
17484 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
17485 - Fix bug with tor_memmem finding a match at the end of the string.
17486 - Make unit tests run without segfaulting.
17487 - Resolve some solaris x86 compile warnings.
17488 - Handle duplicate lines in approved-routers files without warning.
17489 - Fix bug where as soon as a server refused any requests due to his
17490 exit policy (e.g. when we ask for localhost and he tells us that's
17491 127.0.0.1 and he won't do it), we decided he wasn't obeying his
17492 exit policy using him for any exits.
17493 - Only do openssl hardware accelerator stuff if openssl version is
17496 o New controller features/fixes:
17497 - Add a "RESETCONF" command so you can set config options like
17498 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
17499 a config option in the torrc with no value, then it clears it
17500 entirely (rather than setting it to its default).
17501 - Add a "GETINFO config-file" to tell us where torrc is.
17502 - Avoid sending blank lines when GETINFO replies should be empty.
17503 - Add a QUIT command for the controller (for using it manually).
17504 - Fix a bug in SAVECONF that was adding default dirservers and
17505 other redundant entries to the torrc file.
17507 o Start on the new directory design:
17508 - Generate, publish, cache, serve new network-status format.
17509 - Publish individual descriptors (by fingerprint, by "all", and by
17511 - Publish client and server recommended versions separately.
17512 - Allow tor_gzip_uncompress() to handle multiple concatenated
17513 compressed strings. Serve compressed groups of router
17514 descriptors. The compression logic here could be more
17516 - Distinguish v1 authorities (all currently trusted directories)
17517 from v2 authorities (all trusted directories).
17518 - Change DirServers config line to note which dirs are v1 authorities.
17519 - Add configuration option "V1AuthoritativeDirectory 1" which
17520 moria1, moria2, and tor26 should set.
17521 - Remove option when getting directory cache to see whether they
17522 support running-routers; they all do now. Replace it with one
17523 to see whether caches support v2 stuff.
17526 - Dirservers now do their own external reachability testing of each
17527 Tor server, and only list them as running if they've been found to
17528 be reachable. We also send back warnings to the server's logs if
17529 it uploads a descriptor that we already believe is unreachable.
17530 - Implement exit enclaves: if we know an IP address for the
17531 destination, and there's a running Tor server at that address
17532 which allows exit to the destination, then extend the circuit to
17533 that exit first. This provides end-to-end encryption and end-to-end
17534 authentication. Also, if the user wants a .exit address or enclave,
17535 use 4 hops rather than 3, and cannibalize a general circ for it
17537 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
17538 controller. Also, rotate dns and cpu workers if the controller
17539 changes options that will affect them; and initialize the dns
17540 worker cache tree whether or not we start out as a server.
17541 - Only upload a new server descriptor when options change, 18
17542 hours have passed, uptime is reset, or bandwidth changes a lot.
17543 - Check [X-]Forwarded-For headers in HTTP requests when generating
17544 log messages. This lets people run dirservers (and caches) behind
17545 Apache but still know which IP addresses are causing warnings.
17547 o Config option changes:
17548 - Replace (Fascist)Firewall* config options with a new
17549 ReachableAddresses option that understands address policies.
17550 For example, "ReachableAddresses *:80,*:443"
17551 - Get rid of IgnoreVersion undocumented config option, and make us
17552 only warn, never exit, when we're running an obsolete version.
17553 - Make MonthlyAccountingStart config option truly obsolete now.
17555 o Fixes on 0.1.0.x:
17556 - Reject ports 465 and 587 in the default exit policy, since
17557 people have started using them for spam too.
17558 - It turns out we couldn't bootstrap a network since we added
17559 reachability detection in 0.1.0.1-rc. Good thing the Tor network
17560 has never gone down. Add an AssumeReachable config option to let
17561 servers and dirservers bootstrap. When we're trying to build a
17562 high-uptime or high-bandwidth circuit but there aren't enough
17563 suitable servers, try being less picky rather than simply failing.
17564 - Our logic to decide if the OR we connected to was the right guy
17565 was brittle and maybe open to a mitm for unverified routers.
17566 - We weren't cannibalizing circuits correctly for
17567 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
17568 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
17569 build those from scratch. This should make hidden services faster.
17570 - Predict required circuits better, with an eye toward making hidden
17571 services faster on the service end.
17572 - Retry streams if the exit node sends back a 'misc' failure. This
17573 should result in fewer random failures. Also, after failing
17574 from resolve failed or misc, reset the num failures, so we give
17575 it a fair shake next time we try.
17576 - Clean up the rendezvous warn log msgs, and downgrade some to info.
17577 - Reduce severity on logs about dns worker spawning and culling.
17578 - When we're shutting down and we do something like try to post a
17579 server descriptor or rendezvous descriptor, don't complain that
17580 we seem to be unreachable. Of course we are, we're shutting down.
17581 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
17582 We don't use them yet, but maybe one day our DNS resolver will be
17583 able to discover them.
17584 - Make ContactInfo mandatory for authoritative directory servers.
17585 - Require server descriptors to list IPv4 addresses -- hostnames
17586 are no longer allowed. This also fixes some potential security
17587 problems with people providing hostnames as their address and then
17588 preferentially resolving them to partition users.
17589 - Change log line for unreachability to explicitly suggest /etc/hosts
17590 as the culprit. Also make it clearer what IP address and ports we're
17591 testing for reachability.
17592 - Put quotes around user-supplied strings when logging so users are
17593 more likely to realize if they add bad characters (like quotes)
17595 - Let auth dir servers start without specifying an Address config
17597 - Make unit tests (and other invocations that aren't the real Tor)
17598 run without launching listeners, creating subdirectories, and so on.
17601 Changes in version 0.1.1.5-alpha - 2005-08-08
17602 o Bugfixes included in 0.1.0.14.
17604 o Bugfixes on 0.1.0.x:
17605 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
17606 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
17607 it would silently using ignore the 6668.
17610 Changes in version 0.1.0.14 - 2005-08-08
17611 o Bugfixes on 0.1.0.x:
17612 - Fix the other half of the bug with crypto handshakes
17614 - Fix an assert trigger if you send a 'signal term' via the
17615 controller when it's listening for 'event info' messages.
17618 Changes in version 0.1.1.4-alpha - 2005-08-04
17619 o Bugfixes included in 0.1.0.13.
17622 - Improve tor_gettimeofday() granularity on windows.
17623 - Make clients regenerate their keys when their IP address changes.
17624 - Implement some more GETINFO goodness: expose helper nodes, config
17625 options, getinfo keys.
17628 Changes in version 0.1.0.13 - 2005-08-04
17629 o Bugfixes on 0.1.0.x:
17630 - Fix a critical bug in the security of our crypto handshakes.
17631 - Fix a size_t underflow in smartlist_join_strings2() that made
17632 it do bad things when you hand it an empty smartlist.
17633 - Fix Windows installer to ship Tor license (thanks to Aphex for
17634 pointing out this oversight) and put a link to the doc directory
17636 - Explicitly set no-unaligned-access for sparc: it turns out the
17637 new gcc's let you compile broken code, but that doesn't make it
17641 Changes in version 0.1.1.3-alpha - 2005-07-23
17642 o Bugfixes on 0.1.1.2-alpha:
17643 - Fix a bug in handling the controller's "post descriptor"
17645 - Fix several bugs in handling the controller's "extend circuit"
17647 - Fix a bug in handling the controller's "stream status" event.
17648 - Fix an assert failure if we have a controller listening for
17649 circuit events and we go offline.
17650 - Re-allow hidden service descriptors to publish 0 intro points.
17651 - Fix a crash when generating your hidden service descriptor if
17652 you don't have enough intro points already.
17654 o New features on 0.1.1.2-alpha:
17655 - New controller function "getinfo accounting", to ask how
17656 many bytes we've used in this time period.
17657 - Experimental support for helper nodes: a lot of the risk from
17658 a small static adversary comes because users pick new random
17659 nodes every time they rebuild a circuit. Now users will try to
17660 stick to the same small set of entry nodes if they can. Not
17661 enabled by default yet.
17663 o Bugfixes on 0.1.0.12:
17664 - If you're an auth dir server, always publish your dirport,
17665 even if you haven't yet found yourself to be reachable.
17666 - Fix a size_t underflow in smartlist_join_strings2() that made
17667 it do bad things when you hand it an empty smartlist.
17670 Changes in version 0.1.0.12 - 2005-07-18
17671 o New directory servers:
17672 - tor26 has changed IP address.
17674 o Bugfixes on 0.1.0.x:
17675 - Fix a possible double-free in tor_gzip_uncompress().
17676 - When --disable-threads is set, do not search for or link against
17677 pthreads libraries.
17678 - Don't trigger an assert if an authoritative directory server
17679 claims its dirport is 0.
17680 - Fix bug with removing Tor as an NT service: some people were
17681 getting "The service did not return an error." Thanks to Matt
17685 Changes in version 0.1.1.2-alpha - 2005-07-15
17686 o New directory servers:
17687 - tor26 has changed IP address.
17689 o Bugfixes on 0.1.0.x, crashes/leaks:
17690 - Port the servers-not-obeying-their-exit-policies fix from
17692 - Fix an fd leak in start_daemon().
17693 - On Windows, you can't always reopen a port right after you've
17694 closed it. So change retry_listeners() to only close and re-open
17695 ports that have changed.
17696 - Fix a possible double-free in tor_gzip_uncompress().
17698 o Bugfixes on 0.1.0.x, usability:
17699 - When tor_socketpair() fails in Windows, give a reasonable
17700 Windows-style errno back.
17701 - Let people type "tor --install" as well as "tor -install" when
17703 want to make it an NT service.
17704 - NT service patch from Matt Edman to improve error messages.
17705 - When the controller asks for a config option with an abbreviated
17706 name, give the full name in our response.
17707 - Correct the man page entry on TrackHostExitsExpire.
17708 - Looks like we were never delivering deflated (i.e. compressed)
17709 running-routers lists, even when asked. Oops.
17710 - When --disable-threads is set, do not search for or link against
17711 pthreads libraries.
17713 o Bugfixes on 0.1.1.x:
17714 - Fix a seg fault with autodetecting which controller version is
17718 - New hidden service descriptor format: put a version in it, and
17719 let people specify introduction/rendezvous points that aren't
17720 in "the directory" (which is subjective anyway).
17721 - Allow the DEBUG controller event to work again. Mark certain log
17722 entries as "don't tell this to controllers", so we avoid cycles.
17725 Changes in version 0.1.0.11 - 2005-06-30
17726 o Bugfixes on 0.1.0.x:
17727 - Fix major security bug: servers were disregarding their
17728 exit policies if clients behaved unexpectedly.
17729 - Make OS X init script check for missing argument, so we don't
17730 confuse users who invoke it incorrectly.
17731 - Fix a seg fault in "tor --hash-password foo".
17732 - The MAPADDRESS control command was broken.
17735 Changes in version 0.1.1.1-alpha - 2005-06-29
17737 - Make OS X init script check for missing argument, so we don't
17738 confuse users who invoke it incorrectly.
17739 - Fix a seg fault in "tor --hash-password foo".
17740 - Fix a possible way to DoS dirservers.
17741 - When we complain that your exit policy implicitly allows local or
17742 private address spaces, name them explicitly so operators can
17744 - Make the log message less scary when all the dirservers are
17745 temporarily unreachable.
17746 - We were printing the number of idle dns workers incorrectly when
17750 - Revised controller protocol (version 1) that uses ascii rather
17751 than binary. Add supporting libraries in python and java so you
17752 can use the controller from your applications without caring how
17753 our protocol works.
17754 - Spiffy new support for crypto hardware accelerators. Can somebody
17758 Changes in version 0.0.9.10 - 2005-06-16
17759 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
17760 - Refuse relay cells that claim to have a length larger than the
17761 maximum allowed. This prevents a potential attack that could read
17762 arbitrary memory (e.g. keys) from an exit server's process
17766 Changes in version 0.1.0.10 - 2005-06-14
17767 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
17768 libevent before 1.1a.
17771 Changes in version 0.1.0.9-rc - 2005-06-09
17773 - Reset buf->highwater every time buf_shrink() is called, not just on
17774 a successful shrink. This was causing significant memory bloat.
17775 - Fix buffer overflow when checking hashed passwords.
17776 - Security fix: if seeding the RNG on Win32 fails, quit.
17777 - Allow seeding the RNG on Win32 even when you're not running as
17779 - Disable threading on Solaris too. Something is wonky with it,
17780 cpuworkers, and reentrant libs.
17781 - Reenable the part of the code that tries to flush as soon as an
17782 OR outbuf has a full TLS record available. Perhaps this will make
17783 OR outbufs not grow as huge except in rare cases, thus saving lots
17784 of CPU time plus memory.
17785 - Reject malformed .onion addresses rather then passing them on as
17786 normal web requests.
17787 - Adapt patch from Adam Langley: fix possible memory leak in
17788 tor_lookup_hostname().
17789 - Initialize libevent later in the startup process, so the logs are
17790 already established by the time we start logging libevent warns.
17791 - Use correct errno on win32 if libevent fails.
17792 - Check and warn about known-bad/slow libevent versions.
17793 - Pay more attention to the ClientOnly config option.
17794 - Have torctl.in/tor.sh.in check for location of su binary (needed
17796 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
17797 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
17798 HttpProxyAuthenticator
17799 - Stop warning about sigpipes in the logs. We're going to
17800 pretend that getting these occassionally is normal and fine.
17801 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
17803 installer screens; and don't put stuff into StartupItems unless
17804 the user asks you to.
17805 - Require servers that use the default dirservers to have public IP
17806 addresses. We have too many servers that are configured with private
17807 IPs and their admins never notice the log entries complaining that
17808 their descriptors are being rejected.
17809 - Add OSX uninstall instructions. An actual uninstall script will
17813 Changes in version 0.1.0.8-rc - 2005-05-23
17815 - It turns out that kqueue on OS X 10.3.9 was causing kernel
17816 panics. Disable kqueue on all OS X Tors.
17817 - Fix RPM: remove duplicate line accidentally added to the rpm
17819 - Disable threads on openbsd too, since its gethostaddr is not
17821 - Tolerate libevent 0.8 since it still works, even though it's
17823 - Enable building on Red Hat 9.0 again.
17824 - Allow the middle hop of the testing circuit to be running any
17825 version, now that most of them have the bugfix to let them connect
17826 to unknown servers. This will allow reachability testing to work
17827 even when 0.0.9.7-0.0.9.9 become obsolete.
17828 - Handle relay cells with rh.length too large. This prevents
17829 a potential attack that could read arbitrary memory (maybe even
17830 keys) from the exit server's process.
17831 - We screwed up the dirport reachability testing when we don't yet
17832 have a cached version of the directory. Hopefully now fixed.
17833 - Clean up router_load_single_router() (used by the controller),
17834 so it doesn't seg fault on error.
17835 - Fix a minor memory leak when somebody establishes an introduction
17836 point at your Tor server.
17837 - If a socks connection ends because read fails, don't warn that
17838 you're not sending a socks reply back.
17841 - Add HttpProxyAuthenticator config option too, that works like
17842 the HttpsProxyAuthenticator config option.
17843 - Encode hashed controller passwords in hex instead of base64,
17844 to make it easier to write controllers.
17847 Changes in version 0.1.0.7-rc - 2005-05-17
17849 - Fix a bug in the OS X package installer that prevented it from
17850 installing on Tiger.
17851 - Fix a script bug in the OS X package installer that made it
17852 complain during installation.
17853 - Find libevent even if it's hiding in /usr/local/ and your
17854 CFLAGS and LDFLAGS don't tell you to look there.
17855 - Be able to link with libevent as a shared library (the default
17856 after 1.0d), even if it's hiding in /usr/local/lib and even
17857 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
17858 assuming you're running gcc. Otherwise fail and give a useful
17860 - Fix a bug in the RPM packager: set home directory for _tor to
17861 something more reasonable when first installing.
17862 - Free a minor amount of memory that is still reachable on exit.
17865 Changes in version 0.1.0.6-rc - 2005-05-14
17867 - Implement --disable-threads configure option. Disable threads on
17868 netbsd by default, because it appears to have no reentrant resolver
17870 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
17871 release (1.1) detects and disables kqueue if it's broken.
17872 - Append default exit policy before checking for implicit internal
17873 addresses. Now we don't log a bunch of complaints on startup
17874 when using the default exit policy.
17875 - Some people were putting "Address " in their torrc, and they had
17876 a buggy resolver that resolved " " to 0.0.0.0. Oops.
17877 - If DataDir is ~/.tor, and that expands to /.tor, then default to
17878 LOCALSTATEDIR/tor instead.
17879 - Fix fragmented-message bug in TorControl.py.
17880 - Resolve a minor bug which would prevent unreachable dirports
17881 from getting suppressed in the published descriptor.
17882 - When the controller gave us a new descriptor, we weren't resolving
17883 it immediately, so Tor would think its address was 0.0.0.0 until
17884 we fetched a new directory.
17885 - Fix an uppercase/lowercase case error in suppressing a bogus
17886 libevent warning on some Linuxes.
17889 - Begin scrubbing sensitive strings from logs by default. Turn off
17890 the config option SafeLogging if you need to do debugging.
17891 - Switch to a new buffer management algorithm, which tries to avoid
17892 reallocing and copying quite as much. In first tests it looks like
17893 it uses *more* memory on average, but less cpu.
17894 - First cut at support for "create-fast" cells. Clients can use
17895 these when extending to their first hop, since the TLS already
17896 provides forward secrecy and authentication. Not enabled on
17898 - When dirservers refuse a router descriptor, we now log its
17899 contactinfo, platform, and the poster's IP address.
17900 - Call tor_free_all instead of connections_free_all after forking, to
17901 save memory on systems that need to fork.
17902 - Whine at you if you're a server and you don't set your contactinfo.
17903 - Implement --verify-config command-line option to check if your torrc
17904 is valid without actually launching Tor.
17905 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
17906 rather than just rejecting it.
17909 Changes in version 0.1.0.5-rc - 2005-04-27
17911 - Stop trying to print a null pointer if an OR conn fails because
17912 we didn't like its cert.
17914 - Switch our internal buffers implementation to use a ring buffer,
17915 to hopefully improve performance for fast servers a lot.
17916 - Add HttpsProxyAuthenticator support (basic auth only), based
17917 on patch from Adam Langley.
17918 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
17919 the fast servers that have been joining lately.
17920 - Give hidden service accesses extra time on the first attempt,
17921 since 60 seconds is often only barely enough. This might improve
17923 - Improve performance for dirservers: stop re-parsing the whole
17924 directory every time you regenerate it.
17925 - Add more debugging info to help us find the weird dns freebsd
17926 pthreads bug; cleaner debug messages to help track future issues.
17929 Changes in version 0.0.9.9 - 2005-04-23
17930 o Bugfixes on 0.0.9.x:
17931 - If unofficial Tor clients connect and send weird TLS certs, our
17932 Tor server triggers an assert. This release contains a minimal
17933 backport from the broader fix that we put into 0.1.0.4-rc.
17936 Changes in version 0.1.0.4-rc - 2005-04-23
17938 - If unofficial Tor clients connect and send weird TLS certs, our
17939 Tor server triggers an assert. Stop asserting, and start handling
17940 TLS errors better in other situations too.
17941 - When the controller asks us to tell it about all the debug-level
17942 logs, it turns out we were generating debug-level logs while
17943 telling it about them, which turns into a bad loop. Now keep
17944 track of whether you're sending a debug log to the controller,
17945 and don't log when you are.
17946 - Fix the "postdescriptor" feature of the controller interface: on
17947 non-complete success, only say "done" once.
17949 - Clients are now willing to load balance over up to 2mB, not 1mB,
17950 of advertised bandwidth capacity.
17951 - Add a NoPublish config option, so you can be a server (e.g. for
17952 testing running Tor servers in other Tor networks) without
17953 publishing your descriptor to the primary dirservers.
17956 Changes in version 0.1.0.3-rc - 2005-04-08
17957 o Improvements on 0.1.0.2-rc:
17958 - Client now retries when streams end early for 'hibernating' or
17959 'resource limit' reasons, rather than failing them.
17960 - More automated handling for dirserver operators:
17961 - Automatically approve nodes running 0.1.0.2-rc or later,
17962 now that the the reachability detection stuff is working.
17963 - Now we allow two unverified servers with the same nickname
17964 but different keys. But if a nickname is verified, only that
17965 nickname+key are allowed.
17966 - If you're an authdirserver connecting to an address:port,
17967 and it's not the OR you were expecting, forget about that
17968 descriptor. If he *was* the one you were expecting, then forget
17969 about all other descriptors for that address:port.
17970 - Allow servers to publish descriptors from 12 hours in the future.
17971 Corollary: only whine about clock skew from the dirserver if
17972 he's a trusted dirserver (since now even verified servers could
17973 have quite wrong clocks).
17974 - Adjust maximum skew and age for rendezvous descriptors: let skew
17975 be 48 hours rather than 90 minutes.
17976 - Efficiency improvements:
17977 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
17978 it much faster to look up a circuit for each relay cell.
17979 - Remove most calls to assert_all_pending_dns_resolves_ok(),
17980 since they're eating our cpu on exit nodes.
17981 - Stop wasting time doing a case insensitive comparison for every
17982 dns name every time we do any lookup. Canonicalize the names to
17983 lowercase and be done with it.
17984 - Start sending 'truncated' cells back rather than destroy cells,
17985 if the circuit closes in front of you. This means we won't have
17986 to abandon partially built circuits.
17987 - Only warn once per nickname from add_nickname_list_to_smartlist
17988 per failure, so an entrynode or exitnode choice that's down won't
17990 - Put a note in the torrc about abuse potential with the default
17992 - Revise control spec and implementation to allow all log messages to
17993 be sent to controller with their severities intact (suggested by
17994 Matt Edman). Update TorControl to handle new log event types.
17995 - Provide better explanation messages when controller's POSTDESCRIPTOR
17997 - Stop putting nodename in the Platform string in server descriptors.
17998 It doesn't actually help, and it is confusing/upsetting some people.
18000 o Bugfixes on 0.1.0.2-rc:
18001 - We were printing the host mask wrong in exit policies in server
18002 descriptors. This isn't a critical bug though, since we were still
18003 obeying the exit policy internally.
18004 - Fix Tor when compiled with libevent but without pthreads: move
18005 connection_unregister() from _connection_free() to
18007 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
18008 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
18009 when we look through the connection array, we'll find any of the
18010 cpu/dnsworkers. This is no good.
18012 o Bugfixes on 0.0.9.8:
18013 - Fix possible bug on threading platforms (e.g. win32) which was
18014 leaking a file descriptor whenever a cpuworker or dnsworker died.
18015 - When using preferred entry or exit nodes, ignore whether the
18016 circuit wants uptime or capacity. They asked for the nodes, they
18018 - chdir() to your datadirectory at the *end* of the daemonize process,
18019 not the beginning. This was a problem because the first time you
18020 run tor, if your datadir isn't there, and you have runasdaemon set
18021 to 1, it will try to chdir to it before it tries to create it. Oops.
18022 - Handle changed router status correctly when dirserver reloads
18023 fingerprint file. We used to be dropping all unverified descriptors
18024 right then. The bug was hidden because we would immediately
18025 fetch a directory from another dirserver, which would include the
18026 descriptors we just dropped.
18027 - When we're connecting to an OR and he's got a different nickname/key
18028 than we were expecting, only complain loudly if we're an OP or a
18029 dirserver. Complaining loudly to the OR admins just confuses them.
18030 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
18031 artificially capped at 500kB.
18034 Changes in version 0.0.9.8 - 2005-04-07
18035 o Bugfixes on 0.0.9.x:
18036 - We have a bug that I haven't found yet. Sometimes, very rarely,
18037 cpuworkers get stuck in the 'busy' state, even though the cpuworker
18038 thinks of itself as idle. This meant that no new circuits ever got
18039 established. Here's a workaround to kill any cpuworker that's been
18040 busy for more than 100 seconds.
18043 Changes in version 0.1.0.2-rc - 2005-04-01
18044 o Bugfixes on 0.1.0.1-rc:
18045 - Fixes on reachability detection:
18046 - Don't check for reachability while hibernating.
18047 - If ORPort is reachable but DirPort isn't, still publish the
18048 descriptor, but zero out DirPort until it's found reachable.
18049 - When building testing circs for ORPort testing, use only
18050 high-bandwidth nodes, so fewer circuits fail.
18051 - Complain about unreachable ORPort separately from unreachable
18052 DirPort, so the user knows what's going on.
18053 - Make sure we only conclude ORPort reachability if we didn't
18054 initiate the conn. Otherwise we could falsely conclude that
18055 we're reachable just because we connected to the guy earlier
18056 and he used that same pipe to extend to us.
18057 - Authdirservers shouldn't do ORPort reachability detection,
18058 since they're in clique mode, so it will be rare to find a
18059 server not already connected to them.
18060 - When building testing circuits, always pick middle hops running
18061 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
18062 bug. (This is a kludge; it will go away when 0.0.9.x becomes
18064 - When we decide we're reachable, actually publish our descriptor
18066 - Fix bug in redirectstream in the controller.
18067 - Fix the state descriptor strings so logs don't claim edge streams
18068 are in a different state than they actually are.
18069 - Use recent libevent features when possible (this only really affects
18070 win32 and osx right now, because the new libevent with these
18071 features hasn't been released yet). Add code to suppress spurious
18073 - Prevent possible segfault in connection_close_unattached_ap().
18074 - Fix newlines on torrc in win32.
18075 - Improve error msgs when tor-resolve fails.
18077 o Improvements on 0.0.9.x:
18078 - New experimental script tor/contrib/ExerciseServer.py (needs more
18079 work) that uses the controller interface to build circuits and
18080 fetch pages over them. This will help us bootstrap servers that
18081 have lots of capacity but haven't noticed it yet.
18082 - New experimental script tor/contrib/PathDemo.py (needs more work)
18083 that uses the controller interface to let you choose whole paths
18085 "<hostname>.<path,separated by dots>.<length of path>.path"
18086 - When we've connected to an OR and handshaked but didn't like
18087 the result, we were closing the conn without sending destroy
18088 cells back for pending circuits. Now send those destroys.
18091 Changes in version 0.0.9.7 - 2005-04-01
18092 o Bugfixes on 0.0.9.x:
18093 - Fix another race crash bug (thanks to Glenn Fink for reporting).
18094 - Compare identity to identity, not to nickname, when extending to
18095 a router not already in the directory. This was preventing us from
18096 extending to unknown routers. Oops.
18097 - Make sure to create OS X Tor user in <500 range, so we aren't
18098 creating actual system users.
18099 - Note where connection-that-hasn't-sent-end was marked, and fix
18100 a few really loud instances of this harmless bug (it's fixed more
18104 Changes in version 0.1.0.1-rc - 2005-03-28
18106 - Add reachability testing. Your Tor server will automatically try
18107 to see if its ORPort and DirPort are reachable from the outside,
18108 and it won't upload its descriptor until it decides they are.
18109 - Handle unavailable hidden services better. Handle slow or busy
18110 hidden services better.
18111 - Add support for CONNECTing through https proxies, with "HttpsProxy"
18113 - New exit policy: accept most low-numbered ports, rather than
18114 rejecting most low-numbered ports.
18115 - More Tor controller support (still experimental). See
18116 http://tor.eff.org/doc/control-spec.txt for all the new features,
18117 including signals to emulate unix signals from any platform;
18118 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
18119 closestream; closecircuit; etc.
18120 - Make nt services work and start on startup on win32 (based on
18121 patch by Matt Edman).
18122 - Add a new AddressMap config directive to rewrite incoming socks
18123 addresses. This lets you, for example, declare an implicit
18124 required exit node for certain sites.
18125 - Add a new TrackHostExits config directive to trigger addressmaps
18126 for certain incoming socks addresses -- for sites that break when
18127 your exit keeps changing (based on patch by Mike Perry).
18128 - Redo the client-side dns cache so it's just an addressmap too.
18129 - Notice when our IP changes, and reset stats/uptime/reachability.
18130 - When an application is using socks5, give him the whole variety of
18131 potential socks5 responses (connect refused, host unreachable, etc),
18132 rather than just "success" or "failure".
18133 - A more sane version numbering system. See
18134 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
18135 - New contributed script "exitlist": a simple python script to
18136 parse directories and find Tor nodes that exit to listed
18138 - New contributed script "privoxy-tor-toggle" to toggle whether
18139 Privoxy uses Tor. Seems to be configured for Debian by default.
18140 - Report HTTP reasons to client when getting a response from directory
18141 servers -- so you can actually know what went wrong.
18142 - New config option MaxAdvertisedBandwidth which lets you advertise
18143 a low bandwidthrate (to not attract as many circuits) while still
18144 allowing a higher bandwidthrate in reality.
18146 o Robustness/stability fixes:
18147 - Make Tor use Niels Provos's libevent instead of its current
18148 poll-but-sometimes-select mess. This will let us use faster async
18149 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
18151 - pthread support now too. This was forced because when we forked,
18152 we ended up wasting a lot of duplicate ram over time. Also switch
18153 to foo_r versions of some library calls to allow reentry and
18155 - Better handling for heterogeneous / unreliable nodes:
18156 - Annotate circuits w/ whether they aim to contain high uptime nodes
18157 and/or high capacity nodes. When building circuits, choose
18159 - This means that every single node in an intro rend circuit,
18160 not just the last one, will have a minimum uptime.
18161 - New config option LongLivedPorts to indicate application streams
18162 that will want high uptime circuits.
18163 - Servers reset uptime when a dir fetch entirely fails. This
18164 hopefully reflects stability of the server's network connectivity.
18165 - If somebody starts his tor server in Jan 2004 and then fixes his
18166 clock, don't make his published uptime be a year.
18167 - Reset published uptime when you wake up from hibernation.
18168 - Introduce a notion of 'internal' circs, which are chosen without
18169 regard to the exit policy of the last hop. Intro and rendezvous
18170 circs must be internal circs, to avoid leaking information. Resolve
18171 and connect streams can use internal circs if they want.
18172 - New circuit pooling algorithm: make sure to have enough circs around
18173 to satisfy any predicted ports, and also make sure to have 2 internal
18174 circs around if we've required internal circs lately (and with high
18175 uptime if we've seen that lately too).
18176 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
18177 which describes how often we retry making new circuits if current
18178 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
18179 how long we're willing to make use of an already-dirty circuit.
18180 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
18181 circ as necessary, if there are any completed ones lying around
18182 when we try to launch one.
18183 - Make hidden services try to establish a rendezvous for 30 seconds,
18184 rather than for n (where n=3) attempts to build a circuit.
18185 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
18186 "ShutdownWaitLength".
18187 - Try to be more zealous about calling connection_edge_end when
18188 things go bad with edge conns in connection.c.
18189 - Revise tor-spec to add more/better stream end reasons.
18190 - Revise all calls to connection_edge_end to avoid sending "misc",
18191 and to take errno into account where possible.
18194 - Fix a race condition that can trigger an assert, when we have a
18195 pending create cell and an OR connection fails right then.
18196 - Fix several double-mark-for-close bugs, e.g. where we were finding
18197 a conn for a cell even if that conn is already marked for close.
18198 - Make sequence of log messages when starting on win32 with no config
18199 file more reasonable.
18200 - When choosing an exit node for a new non-internal circ, don't take
18201 into account whether it'll be useful for any pending x.onion
18202 addresses -- it won't.
18203 - Turn addr_policy_compare from a tristate to a quadstate; this should
18204 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
18205 for google.com" problem.
18206 - Make "platform" string in descriptor more accurate for Win32 servers,
18207 so it's not just "unknown platform".
18208 - Fix an edge case in parsing config options (thanks weasel).
18209 If they say "--" on the commandline, it's not an option.
18210 - Reject odd-looking addresses at the client (e.g. addresses that
18211 contain a colon), rather than having the server drop them because
18213 - tor-resolve requests were ignoring .exit if there was a working circuit
18214 they could use instead.
18215 - REUSEADDR on normal platforms means you can rebind to the port
18216 right after somebody else has let it go. But REUSEADDR on win32
18217 means to let you bind to the port _even when somebody else
18218 already has it bound_! So, don't do that on Win32.
18219 - Change version parsing logic: a version is "obsolete" if it is not
18220 recommended and (1) there is a newer recommended version in the
18221 same series, or (2) there are no recommended versions in the same
18222 series, but there are some recommended versions in a newer series.
18223 A version is "new" if it is newer than any recommended version in
18225 - Stop most cases of hanging up on a socks connection without sending
18229 - Require BandwidthRate to be at least 20kB/s for servers.
18230 - When a dirserver causes you to give a warn, mention which dirserver
18232 - New config option DirAllowPrivateAddresses for authdirservers.
18233 Now by default they refuse router descriptors that have non-IP or
18234 private-IP addresses.
18235 - Stop publishing socksport in the directory, since it's not
18236 actually meant to be public. For compatibility, publish a 0 there
18238 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
18239 smart" value, that is low for servers and high for clients.
18240 - If our clock jumps forward by 100 seconds or more, assume something
18241 has gone wrong with our network and abandon all not-yet-used circs.
18242 - Warn when exit policy implicitly allows local addresses.
18243 - If we get an incredibly skewed timestamp from a dirserver mirror
18244 that isn't a verified OR, don't warn -- it's probably him that's
18246 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
18247 cookies to disk and doesn't log each web request to disk. (Thanks
18248 to Brett Carrington for pointing this out.)
18249 - When a client asks us for a dir mirror and we don't have one,
18250 launch an attempt to get a fresh one.
18251 - If we're hibernating and we get a SIGINT, exit immediately.
18252 - Add --with-dmalloc ./configure option, to track memory leaks.
18253 - And try to free all memory on closing, so we can detect what
18255 - Cache local dns resolves correctly even when they're .exit
18257 - Give a better warning when some other server advertises an
18258 ORPort that is actually an apache running ssl.
18259 - Add "opt hibernating 1" to server descriptor to make it clearer
18260 whether the server is hibernating.
18263 Changes in version 0.0.9.6 - 2005-03-24
18264 o Bugfixes on 0.0.9.x (crashes and asserts):
18265 - Add new end stream reasons to maintainance branch. Fix bug where
18266 reason (8) could trigger an assert. Prevent bug from recurring.
18267 - Apparently win32 stat wants paths to not end with a slash.
18268 - Fix assert triggers in assert_cpath_layer_ok(), where we were
18269 blowing away the circuit that conn->cpath_layer points to, then
18270 checking to see if the circ is well-formed. Backport check to make
18271 sure we dont use the cpath on a closed connection.
18272 - Prevent circuit_resume_edge_reading_helper() from trying to package
18273 inbufs for marked-for-close streams.
18274 - Don't crash on hup if your options->address has become unresolvable.
18275 - Some systems (like OS X) sometimes accept() a connection and tell
18276 you the remote host is 0.0.0.0:0. If this happens, due to some
18277 other mis-features, we get confused; so refuse the conn for now.
18279 o Bugfixes on 0.0.9.x (other):
18280 - Fix harmless but scary "Unrecognized content encoding" warn message.
18281 - Add new stream error reason: TORPROTOCOL reason means "you are not
18282 speaking a version of Tor I understand; say bye-bye to your stream."
18283 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
18284 into the future, now that we are more tolerant of skew. This
18285 resolves a bug where a Tor server would refuse to cache a directory
18286 because all the directories it gets are too far in the future;
18287 yet the Tor server never logs any complaints about clock skew.
18288 - Mac packaging magic: make man pages useable, and do not overwrite
18289 existing torrc files.
18290 - Make OS X log happily to /var/log/tor/tor.log
18293 Changes in version 0.0.9.5 - 2005-02-22
18294 o Bugfixes on 0.0.9.x:
18295 - Fix an assert race at exit nodes when resolve requests fail.
18296 - Stop picking unverified dir mirrors--it only leads to misery.
18297 - Patch from Matt Edman to make NT services work better. Service
18298 support is still not compiled into the executable by default.
18299 - Patch from Dmitri Bely so the Tor service runs better under
18300 the win32 SYSTEM account.
18301 - Make tor-resolve actually work (?) on Win32.
18302 - Fix a sign bug when getrlimit claims to have 4+ billion
18303 file descriptors available.
18304 - Stop refusing to start when bandwidthburst == bandwidthrate.
18305 - When create cells have been on the onion queue more than five
18306 seconds, just send back a destroy and take them off the list.
18309 Changes in version 0.0.9.4 - 2005-02-03
18310 o Bugfixes on 0.0.9:
18311 - Fix an assert bug that took down most of our servers: when
18312 a server claims to have 1 GB of bandwidthburst, don't
18314 - Don't crash as badly if we have spawned the max allowed number
18315 of dnsworkers, or we're out of file descriptors.
18316 - Block more file-sharing ports in the default exit policy.
18317 - MaxConn is now automatically set to the hard limit of max
18318 file descriptors we're allowed (ulimit -n), minus a few for
18320 - Give a clearer message when servers need to raise their
18321 ulimit -n when they start running out of file descriptors.
18322 - SGI Compatibility patches from Jan Schaumann.
18323 - Tolerate a corrupt cached directory better.
18324 - When a dirserver hasn't approved your server, list which one.
18325 - Go into soft hibernation after 95% of the bandwidth is used,
18326 not 99%. This is especially important for daily hibernators who
18327 have a small accounting max. Hopefully it will result in fewer
18328 cut connections when the hard hibernation starts.
18329 - Load-balance better when using servers that claim more than
18330 800kB/s of capacity.
18331 - Make NT services work (experimental, only used if compiled in).
18334 Changes in version 0.0.9.3 - 2005-01-21
18335 o Bugfixes on 0.0.9:
18336 - Backport the cpu use fixes from main branch, so busy servers won't
18337 need as much processor time.
18338 - Work better when we go offline and then come back, or when we
18339 run Tor at boot before the network is up. We do this by
18340 optimistically trying to fetch a new directory whenever an
18341 application request comes in and we think we're offline -- the
18342 human is hopefully a good measure of when the network is back.
18343 - Backport some minimal hidserv bugfixes: keep rend circuits open as
18344 long as you keep using them; actually publish hidserv descriptors
18345 shortly after they change, rather than waiting 20-40 minutes.
18346 - Enable Mac startup script by default.
18347 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
18348 - When you update AllowUnverifiedNodes or FirewallPorts via the
18349 controller's setconf feature, we were always appending, never
18351 - When you update HiddenServiceDir via setconf, it was screwing up
18352 the order of reading the lines, making it fail.
18353 - Do not rewrite a cached directory back to the cache; otherwise we
18354 will think it is recent and not fetch a newer one on startup.
18355 - Workaround for webservers that lie about Content-Encoding: Tor
18356 now tries to autodetect compressed directories and compression
18357 itself. This lets us Proxypass dir fetches through apache.
18360 Changes in version 0.0.9.2 - 2005-01-04
18361 o Bugfixes on 0.0.9 (crashes and asserts):
18362 - Fix an assert on startup when the disk is full and you're logging
18364 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
18365 style address, then we'd crash.
18366 - Fix an assert trigger when the running-routers string we get from
18367 a dirserver is broken.
18368 - Make worker threads start and run on win32. Now win32 servers
18370 - Bandaid (not actually fix, but now it doesn't crash) an assert
18371 where the dns worker dies mysteriously and the main Tor process
18372 doesn't remember anything about the address it was resolving.
18374 o Bugfixes on 0.0.9 (Win32):
18375 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
18376 name out of the warning/assert messages.
18377 - Fix a superficial "unhandled error on read" bug on win32.
18378 - The win32 installer no longer requires a click-through for our
18379 license, since our Free Software license grants rights but does not
18381 - Win32: When connecting to a dirserver fails, try another one
18382 immediately. (This was already working for non-win32 Tors.)
18383 - Stop trying to parse $HOME on win32 when hunting for default
18385 - Make tor-resolve.c work on win32 by calling network_init().
18387 o Bugfixes on 0.0.9 (other):
18388 - Make 0.0.9.x build on Solaris again.
18389 - Due to a fencepost error, we were blowing away the \n when reporting
18390 confvalue items in the controller. So asking for multiple config
18391 values at once couldn't work.
18392 - When listing circuits that are pending on an opening OR connection,
18393 if we're an OR we were listing circuits that *end* at us as
18394 being pending on every listener, dns/cpu worker, etc. Stop that.
18395 - Dirservers were failing to create 'running-routers' or 'directory'
18396 strings if we had more than some threshold of routers. Fix them so
18397 they can handle any number of routers.
18398 - Fix a superficial "Duplicate mark for close" bug.
18399 - Stop checking for clock skew for OR connections, even for servers.
18400 - Fix a fencepost error that was chopping off the last letter of any
18401 nickname that is the maximum allowed nickname length.
18402 - Update URLs in log messages so they point to the new website.
18403 - Fix a potential problem in mangling server private keys while
18404 writing to disk (not triggered yet, as far as we know).
18405 - Include the licenses for other free software we include in Tor,
18406 now that we're shipping binary distributions more regularly.
18409 Changes in version 0.0.9.1 - 2004-12-15
18410 o Bugfixes on 0.0.9:
18411 - Make hibernation actually work.
18412 - Make HashedControlPassword config option work.
18413 - When we're reporting event circuit status to a controller,
18414 don't use the stream status code.
18417 Changes in version 0.0.9 - 2004-12-12
18419 - Clean up manpage and torrc.sample file.
18420 - Clean up severities and text of log warnings.
18422 - Make servers trigger an assert when they enter hibernation.
18425 Changes in version 0.0.9rc7 - 2004-12-08
18426 o Bugfixes on 0.0.9rc:
18427 - Fix a stack-trashing crash when an exit node begins hibernating.
18428 - Avoid looking at unallocated memory while considering which
18429 ports we need to build circuits to cover.
18430 - Stop a sigpipe: when an 'end' cell races with eof from the app,
18431 we shouldn't hold-open-until-flush if the eof arrived first.
18432 - Fix a bug with init_cookie_authentication() in the controller.
18433 - When recommending new-format log lines, if the upper bound is
18434 LOG_ERR, leave it implicit.
18436 o Bugfixes on 0.0.8.1:
18437 - Fix a whole slew of memory leaks.
18438 - Fix isspace() and friends so they still make Solaris happy
18439 but also so they don't trigger asserts on win32.
18440 - Fix parse_iso_time on platforms without strptime (eg win32).
18441 - win32: tolerate extra "readable" events better.
18442 - win32: when being multithreaded, leave parent fdarray open.
18443 - Make unit tests work on win32.
18446 Changes in version 0.0.9rc6 - 2004-12-06
18447 o Bugfixes on 0.0.9pre:
18448 - Clean up some more integer underflow opportunities (not exploitable
18450 - While hibernating, hup should not regrow our listeners.
18451 - Send an end to the streams we close when we hibernate, rather
18452 than just chopping them off.
18453 - React to eof immediately on non-open edge connections.
18455 o Bugfixes on 0.0.8.1:
18456 - Calculate timeout for waiting for a connected cell from the time
18457 we sent the begin cell, not from the time the stream started. If
18458 it took a long time to establish the circuit, we would time out
18459 right after sending the begin cell.
18460 - Fix router_compare_addr_to_addr_policy: it was not treating a port
18461 of * as always matching, so we were picking reject *:* nodes as
18462 exit nodes too. Oops.
18465 - New circuit building strategy: keep a list of ports that we've
18466 used in the past 6 hours, and always try to have 2 circuits open
18467 or on the way that will handle each such port. Seed us with port
18468 80 so web users won't complain that Tor is "slow to start up".
18469 - Make kill -USR1 dump more useful stats about circuits.
18470 - When warning about retrying or giving up, print the address, so
18471 the user knows which one it's talking about.
18472 - If you haven't used a clean circuit in an hour, throw it away,
18473 just to be on the safe side. (This means after 6 hours a totally
18474 unused Tor client will have no circuits open.)
18477 Changes in version 0.0.9rc5 - 2004-12-01
18478 o Bugfixes on 0.0.8.1:
18479 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
18480 - Let resolve conns retry/expire also, rather than sticking around
18482 - If we are using select, make sure we stay within FD_SETSIZE.
18484 o Bugfixes on 0.0.9pre:
18485 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
18486 but doesn't seem to be currently; thanks to Ilja van Sprundel for
18488 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
18489 instead. Impose minima and maxima for all *Period options; impose
18490 even tighter maxima for fetching if we are a caching dirserver.
18491 Clip rather than rejecting.
18492 - Fetch cached running-routers from servers that serve it (that is,
18493 authdirservers and servers running 0.0.9rc5-cvs or later.)
18496 - Accept *:706 (silc) in default exit policy.
18497 - Implement new versioning format for post 0.1.
18498 - Support "foo.nickname.exit" addresses, to let Alice request the
18499 address "foo" as viewed by exit node "nickname". Based on a patch
18501 - Make tor --version --version dump the cvs Id of every file.
18504 Changes in version 0.0.9rc4 - 2004-11-28
18505 o Bugfixes on 0.0.8.1:
18506 - Make windows sockets actually non-blocking (oops), and handle
18507 win32 socket errors better.
18509 o Bugfixes on 0.0.9rc1:
18510 - Actually catch the -USR2 signal.
18513 Changes in version 0.0.9rc3 - 2004-11-25
18514 o Bugfixes on 0.0.8.1:
18515 - Flush the log file descriptor after we print "Tor opening log file",
18516 so we don't see those messages days later.
18518 o Bugfixes on 0.0.9rc1:
18519 - Make tor-resolve work again.
18520 - Avoid infinite loop in tor-resolve if tor hangs up on it.
18521 - Fix an assert trigger for clients/servers handling resolves.
18524 Changes in version 0.0.9rc2 - 2004-11-24
18525 o Bugfixes on 0.0.9rc1:
18526 - I broke socks5 support while fixing the eof bug.
18527 - Allow unitless bandwidths and intervals; they default to bytes
18529 - New servers don't start out hibernating; they are active until
18530 they run out of bytes, so they have a better estimate of how
18531 long it takes, and so their operators can know they're working.
18534 Changes in version 0.0.9rc1 - 2004-11-23
18535 o Bugfixes on 0.0.8.1:
18536 - Finally fix a bug that's been plaguing us for a year:
18537 With high load, circuit package window was reaching 0. Whenever
18538 we got a circuit-level sendme, we were reading a lot on each
18539 socket, but only writing out a bit. So we would eventually reach
18540 eof. This would be noticed and acted on even when there were still
18541 bytes sitting in the inbuf.
18542 - When poll() is interrupted, we shouldn't believe the revents values.
18544 o Bugfixes on 0.0.9pre6:
18545 - Fix hibernate bug that caused pre6 to be broken.
18546 - Don't keep rephist info for routers that haven't had activity for
18547 24 hours. (This matters now that clients have keys, since we track
18549 - Never call close_temp_logs while validating log options.
18550 - Fix backslash-escaping on tor.sh.in and torctl.in.
18553 - Implement weekly/monthly/daily accounting: now you specify your
18554 hibernation properties by
18555 AccountingMax N bytes|KB|MB|GB|TB
18556 AccountingStart day|week|month [day] HH:MM
18557 Defaults to "month 1 0:00".
18558 - Let bandwidth and interval config options be specified as 5 bytes,
18559 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
18560 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
18561 get back to normal.)
18562 - If your requested entry or exit node has advertised bandwidth 0,
18564 - Be more greedy about filling up relay cells -- we try reading again
18565 once we've processed the stuff we read, in case enough has arrived
18566 to fill the last cell completely.
18567 - Apply NT service patch from Osamu Fujino. Still needs more work.
18570 Changes in version 0.0.9pre6 - 2004-11-15
18571 o Bugfixes on 0.0.8.1:
18572 - Fix assert failure on malformed socks4a requests.
18573 - Use identity comparison, not nickname comparison, to choose which
18574 half of circuit-ID-space each side gets to use. This is needed
18575 because sometimes we think of a router as a nickname, and sometimes
18576 as a hex ID, and we can't predict what the other side will do.
18577 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
18578 write() call will fail and we handle it there.
18579 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
18580 and smartlist_len, which are two major profiling offenders.
18582 o Bugfixes on 0.0.9pre5:
18583 - Fix a bug in read_all that was corrupting config files on windows.
18584 - When we're raising the max number of open file descriptors to
18585 'unlimited', don't log that we just raised it to '-1'.
18586 - Include event code with events, as required by control-spec.txt.
18587 - Don't give a fingerprint when clients do --list-fingerprint:
18588 it's misleading, because it will never be the same again.
18589 - Stop using strlcpy in tor_strndup, since it was slowing us
18591 - Remove warn on startup about missing cached-directory file.
18592 - Make kill -USR1 work again.
18593 - Hibernate if we start tor during the "wait for wakeup-time" phase
18594 of an accounting interval. Log our hibernation plans better.
18595 - Authoritative dirservers now also cache their directory, so they
18596 have it on start-up.
18599 - Fetch running-routers; cache running-routers; compress
18600 running-routers; serve compressed running-routers.z
18601 - Add NSI installer script contributed by J Doe.
18602 - Commit VC6 and VC7 workspace/project files.
18603 - Commit a tor.spec for making RPM files, with help from jbash.
18604 - Add contrib/torctl.in contributed by Glenn Fink.
18605 - Implement the control-spec's SAVECONF command, to write your
18606 configuration to torrc.
18607 - Get cookie authentication for the controller closer to working.
18608 - Include control-spec.txt in the tarball.
18609 - When set_conf changes our server descriptor, upload a new copy.
18610 But don't upload it too often if there are frequent changes.
18611 - Document authentication config in man page, and document signals
18613 - Clean up confusing parts of man page and torrc.sample.
18614 - Make expand_filename handle ~ and ~username.
18615 - Use autoconf to enable largefile support where necessary. Use
18616 ftello where available, since ftell can fail at 2GB.
18617 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
18618 log more informatively.
18619 - Give a slightly more useful output for "tor -h".
18620 - Refuse application socks connections to port 0.
18621 - Check clock skew for verified servers, but allow unverified
18622 servers and clients to have any clock skew.
18623 - Break DirFetchPostPeriod into:
18624 - DirFetchPeriod for fetching full directory,
18625 - StatusFetchPeriod for fetching running-routers,
18626 - DirPostPeriod for posting server descriptor,
18627 - RendPostPeriod for posting hidden service descriptors.
18628 - Make sure the hidden service descriptors are at a random offset
18629 from each other, to hinder linkability.
18632 Changes in version 0.0.9pre5 - 2004-11-09
18633 o Bugfixes on 0.0.9pre4:
18634 - Fix a seg fault in unit tests (doesn't affect main program).
18635 - Fix an assert bug where a hidden service provider would fail if
18636 the first hop of his rendezvous circuit was down.
18637 - Hidden service operators now correctly handle version 1 style
18638 INTRODUCE1 cells (nobody generates them still, so not a critical
18640 - If do_hup fails, actually notice.
18641 - Handle more errnos from accept() without closing the listener.
18642 Some OpenBSD machines were closing their listeners because
18643 they ran out of file descriptors.
18644 - Send resolve cells to exit routers that are running a new
18645 enough version of the resolve code to work right.
18646 - Better handling of winsock includes on non-MSV win32 compilers.
18647 - Some people had wrapped their tor client/server in a script
18648 that would restart it whenever it died. This did not play well
18649 with our "shut down if your version is obsolete" code. Now people
18650 don't fetch a new directory if their local cached version is
18652 - Make our autogen.sh work on ksh as well as bash.
18655 - Hibernation: New config option "AccountingMaxKB" lets you
18656 set how many KBytes per month you want to allow your server to
18657 consume. Rather than spreading those bytes out evenly over the
18658 month, we instead hibernate for some of the month and pop up
18659 at a deterministic time, work until the bytes are consumed, then
18660 hibernate again. Config option "MonthlyAccountingStart" lets you
18661 specify which day of the month your billing cycle starts on.
18662 - Control interface: a separate program can now talk to your
18663 client/server over a socket, and get/set config options, receive
18664 notifications of circuits and streams starting/finishing/dying,
18665 bandwidth used, etc. The next step is to get some GUIs working.
18666 Let us know if you want to help out. See doc/control-spec.txt .
18667 - Ship a contrib/tor-control.py as an example script to interact
18668 with the control port.
18669 - "tor --hash-password zzyxz" will output a salted password for
18670 use in authenticating to the control interface.
18671 - New log format in config:
18672 "Log minsev[-maxsev] stdout|stderr|syslog" or
18673 "Log minsev[-maxsev] file /var/foo"
18676 - DirPolicy config option, to let people reject incoming addresses
18677 from their dirserver.
18678 - "tor --list-fingerprint" will list your identity key fingerprint
18680 - Add "pass" target for RedirectExit, to make it easier to break
18681 out of a sequence of RedirectExit rules.
18682 - Clients now generate a TLS cert too, in preparation for having
18683 them act more like real nodes.
18684 - Ship src/win32/ in the tarball, so people can use it to build.
18685 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
18687 - New "router-status" line in directory, to better bind each verified
18688 nickname to its identity key.
18689 - Deprecate unofficial config option abbreviations, and abbreviations
18690 not on the command line.
18691 - Add a pure-C tor-resolve implementation.
18692 - Use getrlimit and friends to ensure we can reach MaxConn (currently
18693 1024) file descriptors.
18695 o Code security improvements, inspired by Ilja:
18696 - Replace sprintf with snprintf. (I think they were all safe, but
18698 - Replace strcpy/strncpy with strlcpy in more places.
18699 - Avoid strcat; use snprintf or strlcat instead.
18700 - snprintf wrapper with consistent (though not C99) overflow behavior.
18703 Changes in version 0.0.9pre4 - 2004-10-17
18704 o Bugfixes on 0.0.9pre3:
18705 - If the server doesn't specify an exit policy, use the real default
18706 exit policy, not reject *:*.
18707 - Ignore fascistfirewall when uploading/downloading hidden service
18708 descriptors, since we go through Tor for those; and when using
18709 an HttpProxy, since we assume it can reach them all.
18710 - When looking for an authoritative dirserver, use only the ones
18711 configured at boot. Don't bother looking in the directory.
18712 - The rest of the fix for get_default_conf_file() on older win32.
18713 - Make 'Routerfile' config option obsolete.
18716 - New 'MyFamily nick1,...' config option for a server to
18717 specify other servers that shouldn't be used in the same circuit
18718 with it. Only believed if nick1 also specifies us.
18719 - New 'NodeFamily nick1,nick2,...' config option for a client to
18720 specify nodes that it doesn't want to use in the same circuit.
18721 - New 'Redirectexit pattern address:port' config option for a
18722 server to redirect exit connections, e.g. to a local squid.
18725 Changes in version 0.0.9pre3 - 2004-10-13
18726 o Bugfixes on 0.0.8.1:
18727 - Better torrc example lines for dirbindaddress and orbindaddress.
18728 - Improved bounds checking on parsed ints (e.g. config options and
18729 the ones we find in directories.)
18730 - Better handling of size_t vs int, so we're more robust on 64
18732 - Fix the rest of the bug where a newly started OR would appear
18733 as unverified even after we've added his fingerprint and hupped
18735 - Fix a bug from 0.0.7: when read() failed on a stream, we would
18736 close it without sending back an end. So 'connection refused'
18737 would simply be ignored and the user would get no response.
18739 o Bugfixes on 0.0.9pre2:
18740 - Serving the cached-on-disk directory to people is bad. We now
18741 provide no directory until we've fetched a fresh one.
18742 - Workaround for bug on windows where cached-directories get crlf
18744 - Make get_default_conf_file() work on older windows too.
18745 - If we write a *:* exit policy line in the descriptor, don't write
18746 any more exit policy lines.
18749 - Use only 0.0.9pre1 and later servers for resolve cells.
18750 - Make the dirservers file obsolete.
18751 - Include a dir-signing-key token in directories to tell the
18752 parsing entity which key is being used to sign.
18753 - Remove the built-in bulky default dirservers string.
18754 - New config option "Dirserver %s:%d [fingerprint]", which can be
18755 repeated as many times as needed. If no dirservers specified,
18756 default to moria1,moria2,tor26.
18757 - Make moria2 advertise a dirport of 80, so people behind firewalls
18758 will be able to get a directory.
18759 - Http proxy support
18760 - Dirservers translate requests for http://%s:%d/x to /x
18761 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
18762 be routed through this host.
18763 - Clients ask for /tor/x rather than /x for new enough dirservers.
18764 This way we can one day coexist peacefully with apache.
18765 - Clients specify a "Host: %s%d" http header, to be compatible
18766 with more proxies, and so running squid on an exit node can work.
18769 Changes in version 0.0.8.1 - 2004-10-13
18771 - Fix a seg fault that can be triggered remotely for Tor
18772 clients/servers with an open dirport.
18773 - Fix a rare assert trigger, where routerinfos for entries in
18774 our cpath would expire while we're building the path.
18775 - Fix a bug in OutboundBindAddress so it (hopefully) works.
18776 - Fix a rare seg fault for people running hidden services on
18777 intermittent connections.
18778 - Fix a bug in parsing opt keywords with objects.
18779 - Fix a stale pointer assert bug when a stream detaches and
18781 - Fix a string format vulnerability (probably not exploitable)
18782 in reporting stats locally.
18783 - Fix an assert trigger: sometimes launching circuits can fail
18784 immediately, e.g. because too many circuits have failed recently.
18785 - Fix a compile warning on 64 bit platforms.
18788 Changes in version 0.0.9pre2 - 2004-10-03
18790 - Make fetching a cached directory work for 64-bit platforms too.
18791 - Make zlib.h a required header, not an optional header.
18794 Changes in version 0.0.9pre1 - 2004-10-01
18796 - Stop using separate defaults for no-config-file and
18797 empty-config-file. Now you have to explicitly turn off SocksPort,
18798 if you don't want it open.
18799 - Fix a bug in OutboundBindAddress so it (hopefully) works.
18800 - Improve man page to mention more of the 0.0.8 features.
18801 - Fix a rare seg fault for people running hidden services on
18802 intermittent connections.
18803 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
18805 - Fix more dns related bugs: send back resolve_failed and end cells
18806 more reliably when the resolve fails, rather than closing the
18807 circuit and then trying to send the cell. Also attach dummy resolve
18808 connections to a circuit *before* calling dns_resolve(), to fix
18809 a bug where cached answers would never be sent in RESOLVED cells.
18810 - When we run out of disk space, or other log writing error, don't
18811 crash. Just stop logging to that log and continue.
18812 - We were starting to daemonize before we opened our logs, so if
18813 there were any problems opening logs, we would complain to stderr,
18814 which wouldn't work, and then mysteriously exit.
18815 - Fix a rare bug where sometimes a verified OR would connect to us
18816 before he'd uploaded his descriptor, which would cause us to
18817 assign conn->nickname as though he's unverified. Now we look through
18818 the fingerprint list to see if he's there.
18819 - Fix a rare assert trigger, where routerinfos for entries in
18820 our cpath would expire while we're building the path.
18823 - Clients can ask dirservers for /dir.z to get a compressed version
18824 of the directory. Only works for servers running 0.0.9, of course.
18825 - Make clients cache directories and use them to seed their router
18826 lists at startup. This means clients have a datadir again.
18827 - Configuration infrastructure support for warning on obsolete
18829 - Respond to content-encoding headers by trying to uncompress as
18831 - Reply with a deflated directory when a client asks for "dir.z".
18832 We could use allow-encodings instead, but allow-encodings isn't
18833 specified in HTTP 1.0.
18834 - Raise the max dns workers from 50 to 100.
18835 - Discourage people from setting their dirfetchpostperiod more often
18836 than once per minute.
18837 - Protect dirservers from overzealous descriptor uploading -- wait
18838 10 seconds after directory gets dirty, before regenerating.
18841 Changes in version 0.0.8 - 2004-08-25
18842 o Port it to SunOS 5.9 / Athena
18845 Changes in version 0.0.8rc2 - 2004-08-20
18846 o Make it compile on cygwin again.
18847 o When picking unverified routers, skip those with low uptime and/or
18848 low bandwidth, depending on what properties you care about.
18851 Changes in version 0.0.8rc1 - 2004-08-18
18852 o Changes from 0.0.7.3:
18854 - Fix assert triggers: if the other side returns an address 0.0.0.0,
18855 don't put it into the client dns cache.
18856 - If a begin failed due to exit policy, but we believe the IP address
18857 should have been allowed, switch that router to exitpolicy reject *:*
18858 until we get our next directory.
18860 - Clients choose nodes proportional to advertised bandwidth.
18861 - Avoid using nodes with low uptime as introduction points.
18862 - Handle servers with dynamic IP addresses: don't replace
18863 options->Address with the resolved one at startup, and
18864 detect our address right before we make a routerinfo each time.
18865 - 'FascistFirewall' option to pick dirservers and ORs on specific
18866 ports; plus 'FirewallPorts' config option to tell FascistFirewall
18867 which ports are open. (Defaults to 80,443)
18868 - Be more aggressive about trying to make circuits when the network
18869 has changed (e.g. when you unsuspend your laptop).
18870 - Check for time skew on http headers; report date in response to
18872 - If the entrynode config line has only one node, don't pick it as
18874 - Add strict{entry|exit}nodes config options. If set to 1, then
18875 we refuse to build circuits that don't include the specified entry
18877 - OutboundBindAddress config option, to bind to a specific
18878 IP address for outgoing connect()s.
18879 - End truncated log entries (e.g. directories) with "[truncated]".
18881 o Patches to 0.0.8preX:
18883 - Patches to compile and run on win32 again (maybe)?
18884 - Fix crash when looking for ~/.torrc with no $HOME set.
18885 - Fix a race bug in the unit tests.
18886 - Handle verified/unverified name collisions better when new
18887 routerinfo's arrive in a directory.
18888 - Sometimes routers were getting entered into the stats before
18889 we'd assigned their identity_digest. Oops.
18890 - Only pick and establish intro points after we've gotten a
18893 - AllowUnverifiedNodes config option to let circuits choose no-name
18894 routers in entry,middle,exit,introduction,rendezvous positions.
18895 Allow middle and rendezvous positions by default.
18896 - Add a man page for tor-resolve.
18899 Changes in version 0.0.7.3 - 2004-08-12
18900 o Stop dnsworkers from triggering an assert failure when you
18901 ask them to resolve the host "".
18904 Changes in version 0.0.8pre3 - 2004-08-09
18905 o Changes from 0.0.7.2:
18906 - Allow multiple ORs with same nickname in routerlist -- now when
18907 people give us one identity key for a nickname, then later
18908 another, we don't constantly complain until the first expires.
18909 - Remember used bandwidth (both in and out), and publish 15-minute
18910 snapshots for the past day into our descriptor.
18911 - You can now fetch $DIRURL/running-routers to get just the
18912 running-routers line, not the whole descriptor list. (But
18913 clients don't use this yet.)
18914 - When people mistakenly use Tor as an http proxy, point them
18915 at the tor-doc.html rather than the INSTALL.
18916 - Remove our mostly unused -- and broken -- hex_encode()
18917 function. Use base16_encode() instead. (Thanks to Timo Lindfors
18918 for pointing out this bug.)
18919 - Rotate onion keys every 12 hours, not every 2 hours, so we have
18920 fewer problems with people using the wrong key.
18921 - Change the default exit policy to reject the default edonkey,
18922 kazaa, gnutella ports.
18923 - Add replace_file() to util.[ch] to handle win32's rename().
18925 o Changes from 0.0.8preX:
18926 - Fix two bugs in saving onion keys to disk when rotating, so
18927 hopefully we'll get fewer people using old onion keys.
18928 - Fix an assert error that was making SocksPolicy not work.
18929 - Be willing to expire routers that have an open dirport -- it's
18930 just the authoritative dirservers we want to not forget.
18931 - Reject tor-resolve requests for .onion addresses early, so we
18932 don't build a whole rendezvous circuit and then fail.
18933 - When you're warning a server that he's unverified, don't cry
18934 wolf unpredictably.
18935 - Fix a race condition: don't try to extend onto a connection
18936 that's still handshaking.
18937 - For servers in clique mode, require the conn to be open before
18938 you'll choose it for your path.
18939 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
18940 end relay cell, etc.
18941 - Measure bandwidth capacity over the last 24 hours, not just 12
18942 - Bugfix: authoritative dirservers were making and signing a new
18943 directory for each client, rather than reusing the cached one.
18946 Changes in version 0.0.8pre2 - 2004-08-04
18947 o Changes from 0.0.7.2:
18949 - Check directory signature _before_ you decide whether you're
18950 you're running an obsolete version and should exit.
18951 - Check directory signature _before_ you parse the running-routers
18952 list to decide who's running or verified.
18953 - Bugfixes and features:
18954 - Check return value of fclose while writing to disk, so we don't
18955 end up with broken files when servers run out of disk space.
18956 - Log a warning if the user uses an unsafe socks variant, so people
18957 are more likely to learn about privoxy or socat.
18958 - Dirservers now include RFC1123-style dates in the HTTP headers,
18959 which one day we will use to better detect clock skew.
18961 o Changes from 0.0.8pre1:
18962 - Make it compile without warnings again on win32.
18963 - Log a warning if you're running an unverified server, to let you
18964 know you might want to get it verified.
18965 - Only pick a default nickname if you plan to be a server.
18968 Changes in version 0.0.8pre1 - 2004-07-23
18970 - Made our unit tests compile again on OpenBSD 3.5, and tor
18971 itself compile again on OpenBSD on a sparc64.
18972 - We were neglecting milliseconds when logging on win32, so
18973 everything appeared to happen at the beginning of each second.
18975 o Protocol changes:
18976 - 'Extend' relay cell payloads now include the digest of the
18977 intended next hop's identity key. Now we can verify that we're
18978 extending to the right router, and also extend to routers we
18979 hadn't heard of before.
18982 - Tor nodes can now act as relays (with an advertised ORPort)
18983 without being manually verified by the dirserver operators.
18984 - Uploaded descriptors of unverified routers are now accepted
18985 by the dirservers, and included in the directory.
18986 - Verified routers are listed by nickname in the running-routers
18987 list; unverified routers are listed as "$<fingerprint>".
18988 - We now use hash-of-identity-key in most places rather than
18989 nickname or addr:port, for improved security/flexibility.
18990 - To avoid Sybil attacks, paths still use only verified servers.
18991 But now we have a chance to play around with hybrid approaches.
18992 - Nodes track bandwidth usage to estimate capacity (not used yet).
18993 - ClientOnly option for nodes that never want to become servers.
18994 - Directory caching.
18995 - "AuthoritativeDir 1" option for the official dirservers.
18996 - Now other nodes (clients and servers) will cache the latest
18997 directory they've pulled down.
18998 - They can enable their DirPort to serve it to others.
18999 - Clients will pull down a directory from any node with an open
19000 DirPort, and check the signature/timestamp correctly.
19001 - Authoritative dirservers now fetch directories from other
19002 authdirservers, to stay better synced.
19003 - Running-routers list tells who's down also, along with noting
19004 if they're verified (listed by nickname) or unverified (listed
19006 - Allow dirservers to serve running-router list separately.
19007 This isn't used yet.
19008 - ORs connect-on-demand to other ORs
19009 - If you get an extend cell to an OR you're not connected to,
19010 connect, handshake, and forward the create cell.
19011 - The authoritative dirservers stay connected to everybody,
19012 and everybody stays connected to 0.0.7 servers, but otherwise
19013 clients/servers expire unused connections after 5 minutes.
19014 - When servers get a sigint, they delay 30 seconds (refusing new
19015 connections) then exit. A second sigint causes immediate exit.
19016 - File and name management:
19017 - Look for .torrc if no CONFDIR "torrc" is found.
19018 - If no datadir is defined, then choose, make, and secure ~/.tor
19020 - If torrc not found, exitpolicy reject *:*.
19021 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
19022 - If no nickname is defined, derive default from hostname.
19023 - Rename secret key files, e.g. identity.key -> secret_id_key,
19024 to discourage people from mailing their identity key to tor-ops.
19025 - Refuse to build a circuit before the directory has arrived --
19026 it won't work anyway, since you won't know the right onion keys
19028 - Try other dirservers immediately if the one you try is down. This
19029 should tolerate down dirservers better now.
19030 - Parse tor version numbers so we can do an is-newer-than check
19031 rather than an is-in-the-list check.
19032 - New socks command 'resolve', to let us shim gethostbyname()
19034 - A 'tor_resolve' script to access the socks resolve functionality.
19035 - A new socks-extensions.txt doc file to describe our
19036 interpretation and extensions to the socks protocols.
19037 - Add a ContactInfo option, which gets published in descriptor.
19038 - Publish OR uptime in descriptor (and thus in directory) too.
19039 - Write tor version at the top of each log file
19040 - New docs in the tarball:
19042 - Document that you should proxy your SSL traffic too.
19045 Changes in version 0.0.7.2 - 2004-07-07
19046 o A better fix for the 0.0.0.0 problem, that will hopefully
19047 eliminate the remaining related assertion failures.
19050 Changes in version 0.0.7.1 - 2004-07-04
19051 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
19052 since internally we use 0.0.0.0 to signify "not yet resolved".
19055 Changes in version 0.0.7 - 2004-06-07
19056 o Updated the man page to reflect the new features.
19059 Changes in version 0.0.7rc2 - 2004-06-06
19060 o Changes from 0.0.7rc1:
19061 - Make it build on Win32 again.
19062 o Changes from 0.0.6.2:
19063 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
19067 Changes in version 0.0.7rc1 - 2004-06-02
19069 - On sighup, we were adding another log without removing the first
19070 one. So log messages would get duplicated n times for n sighups.
19071 - Several cases of using a connection after we'd freed it. The
19072 problem was that connections that are pending resolve are in both
19073 the pending_resolve tree, and also the circuit's resolving_streams
19074 list. When you want to remove one, you must remove it from both.
19075 - Fix a double-mark-for-close where an end cell arrived for a
19076 resolving stream, and then the resolve failed.
19077 - Check directory signatures based on name of signer, not on whom
19078 we got the directory from. This will let us cache directories more
19081 - Crank up some of our constants to handle more users.
19084 Changes in version 0.0.7pre1 - 2004-06-02
19085 o Fixes for crashes and other obnoxious bugs:
19086 - Fix an epipe bug: sometimes when directory connections failed
19087 to connect, we would give them a chance to flush before closing
19089 - When we detached from a circuit because of resolvefailed, we
19090 would immediately try the same circuit twice more, and then
19091 give up on the resolve thinking we'd tried three different
19093 - Limit the number of intro circuits we'll attempt to build for a
19094 hidden service per 15-minute period.
19095 - Check recommended-software string *early*, before actually parsing
19096 the directory. Thus we can detect an obsolete version and exit,
19097 even if the new directory format doesn't parse.
19098 o Fixes for security bugs:
19099 - Remember which nodes are dirservers when you startup, and if a
19100 random OR enables his dirport, don't automatically assume he's
19101 a trusted dirserver.
19103 - Directory connections were asking the wrong poll socket to
19104 start writing, and not asking themselves to start writing.
19105 - When we detached from a circuit because we sent a begin but
19106 didn't get a connected, we would use it again the first time;
19107 but after that we would correctly switch to a different one.
19108 - Stop warning when the first onion decrypt attempt fails; they
19109 will sometimes legitimately fail now that we rotate keys.
19110 - Override unaligned-access-ok check when $host_cpu is ia64 or
19111 arm. Apparently they allow it but the kernel whines.
19112 - Dirservers try to reconnect periodically too, in case connections
19114 - Fix some memory leaks in directory servers.
19115 - Allow backslash in Win32 filenames.
19116 - Made Tor build complain-free on FreeBSD, hopefully without
19117 breaking other BSD builds. We'll see.
19119 - Doxygen markup on all functions and global variables.
19120 - Make directory functions update routerlist, not replace it. So
19121 now directory disagreements are not so critical a problem.
19122 - Remove the upper limit on number of descriptors in a dirserver's
19123 directory (not that we were anywhere close).
19124 - Allow multiple logfiles at different severity ranges.
19125 - Allow *BindAddress to specify ":port" rather than setting *Port
19126 separately. Allow multiple instances of each BindAddress config
19127 option, so you can bind to multiple interfaces if you want.
19128 - Allow multiple exit policy lines, which are processed in order.
19129 Now we don't need that huge line with all the commas in it.
19130 - Enable accept/reject policies on SOCKS connections, so you can bind
19131 to 0.0.0.0 but still control who can use your OP.
19134 Changes in version 0.0.6.2 - 2004-05-16
19135 o Our integrity-checking digest was checking only the most recent cell,
19136 not the previous cells like we'd thought.
19137 Thanks to Stefan Mark for finding the flaw!
19140 Changes in version 0.0.6.1 - 2004-05-06
19141 o Fix two bugs in our AES counter-mode implementation (this affected
19142 onion-level stream encryption, but not TLS-level). It turns
19143 out we were doing something much more akin to a 16-character
19144 polyalphabetic cipher. Oops.
19145 Thanks to Stefan Mark for finding the flaw!
19146 o Retire moria3 as a directory server, and add tor26 as a directory
19150 Changes in version 0.0.6 - 2004-05-02
19151 [version bump only]
19154 Changes in version 0.0.6rc4 - 2004-05-01
19155 o Update the built-in dirservers list to use the new directory format
19156 o Fix a rare seg fault: if a node offering a hidden service attempts
19157 to build a circuit to Alice's rendezvous point and fails before it
19158 reaches the last hop, it retries with a different circuit, but
19160 o Handle windows socket errors correctly.
19163 Changes in version 0.0.6rc3 - 2004-04-28
19164 o Don't expire non-general excess circuits (if we had enough
19165 circuits open, we were expiring rendezvous circuits -- even
19166 when they had a stream attached. oops.)
19167 o Fetch randomness from /dev/urandom better (not via fopen/fread)
19168 o Better debugging for tls errors
19169 o Some versions of openssl have an SSL_pending function that erroneously
19170 returns bytes when there is a non-application record pending.
19171 o Set Content-Type on the directory and hidserv descriptor.
19172 o Remove IVs from cipher code, since AES-ctr has none.
19173 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
19174 o We were using an array of length zero in a few places.
19175 o win32's gethostbyname can't resolve an IP to an IP.
19176 o win32's close can't close a socket.
19179 Changes in version 0.0.6rc2 - 2004-04-26
19180 o Fix a bug where we were closing tls connections intermittently.
19181 It turns out openssl keeps its errors around -- so if an error
19182 happens, and you don't ask about it, and then another openssl
19183 operation happens and succeeds, and you ask if there was an error,
19184 it tells you about the first error. Fun fun.
19185 o Fix a bug that's been lurking since 27 may 03 (!)
19186 When passing back a destroy cell, we would use the wrong circ id.
19187 'Mostly harmless', but still worth fixing.
19188 o Since we don't support truncateds much, don't bother sending them;
19189 just close the circ.
19190 o check for <machine/limits.h> so we build on NetBSD again (I hope).
19191 o don't crash if a conn that sent a begin has suddenly lost its circuit
19192 (this was quite rare).
19195 Changes in version 0.0.6rc1 - 2004-04-25
19196 o We now rotate link (tls context) keys and onion keys.
19197 o CREATE cells now include oaep padding, so you can tell
19198 if you decrypted them correctly.
19199 o Add bandwidthburst to server descriptor.
19200 o Directories now say which dirserver signed them.
19201 o Use a tor_assert macro that logs failed assertions too.
19204 Changes in version 0.0.6pre5 - 2004-04-18
19205 o changes from 0.0.6pre4:
19206 - make tor build on broken freebsd 5.2 installs
19207 - fix a failed assert when you try an intro point, get a nack, and try
19208 a second one and it works.
19209 - when alice uses a port that the hidden service doesn't accept,
19210 it now sends back an end cell (denied by exit policy). otherwise
19211 alice would just have to wait to time out.
19212 - fix another rare bug: when we had tried all the intro
19213 points for a hidden service, we fetched the descriptor
19214 again, but we left our introcirc thinking it had already
19215 sent an intro, so it kept waiting for a response...
19216 - bugfix: when you sleep your hidden-service laptop, as soon
19217 as it wakes up it tries to upload a service descriptor, but
19218 socketpair fails for some reason (localhost not up yet?).
19219 now we simply give up on that upload, and we'll try again later.
19220 i'd still like to find the bug though.
19221 - if an intro circ waiting for an ack dies before getting one, then
19223 - we were reusing stale service descriptors and refetching usable
19227 Changes in version 0.0.6pre4 - 2004-04-14
19228 o changes from 0.0.6pre3:
19229 - when bob fails to connect to the rendezvous point, and his
19230 circ didn't fail because of the rendezvous point itself, then
19231 he retries a couple of times
19232 - we expire introduction and rendezvous circs more thoroughly
19233 (sometimes they were hanging around forever)
19234 - we expire unattached rendezvous streams that have been around
19235 too long (they were sticking around forever).
19236 - fix a measly fencepost error that was crashing everybody with
19240 Changes in version 0.0.6pre3 - 2004-04-14
19241 o changes from 0.0.6pre2:
19242 - make hup work again
19243 - fix some memory leaks for dirservers
19244 - allow more skew in rendezvous descriptor timestamps, to help
19245 handle people like blanu who don't know what time it is
19246 - normal circs are 3 hops, but some rend/intro circs are 4, if
19247 the initiator doesn't get to choose the last hop
19248 - send acks for introductions, so alice can know whether to try
19250 - bob publishes intro points more correctly
19251 o changes from 0.0.5:
19252 - fix an assert trigger that's been plaguing us since the days
19253 of 0.0.2prexx (thanks weasel!)
19254 - retry stream correctly when we fail to connect because of
19255 exit-policy-reject (should try another) or can't-resolve-address
19256 (also should try another, because dns on random internet servers
19258 - when we hup a dirserver and we've *removed* a server from the
19259 approved-routers list, now we remove that server from the
19260 in-memory directories too
19263 Changes in version 0.0.6pre2 - 2004-04-08
19264 o We fixed our base32 implementation. Now it works on all architectures.
19267 Changes in version 0.0.6pre1 - 2004-04-08
19269 - Hidden services and rendezvous points are implemented. Go to
19270 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
19271 hidden services. (This only works via a socks4a proxy such as
19272 Privoxy, and currently it's quite slow.)
19275 Changes in version 0.0.5 - 2004-03-30
19276 [version bump only]
19279 Changes in version 0.0.5rc3 - 2004-03-29
19280 o Install torrc as torrc.sample -- we no longer clobber your
19282 o Re-enable recommendedversion checking (we broke it in rc2, oops)
19283 o Add in a 'notice' log level for things the operator should hear
19284 but that aren't warnings
19287 Changes in version 0.0.5rc2 - 2004-03-29
19288 o Hold socks connection open until reply is flushed (if possible)
19289 o Make exit nodes resolve IPs to IPs immediately, rather than asking
19290 the dns farm to do it.
19291 o Fix c99 aliasing warnings in rephist.c
19292 o Don't include server descriptors that are older than 24 hours in the
19294 o Give socks 'reject' replies their whole 15s to attempt to flush,
19295 rather than seeing the 60s timeout and assuming the flush had failed.
19296 o Clean automake droppings from the cvs repository
19299 Changes in version 0.0.5rc1 - 2004-03-28
19300 o Fix mangled-state bug in directory fetching (was causing sigpipes).
19301 o Only build circuits after we've fetched the directory: clients were
19302 using only the directory servers before they'd fetched a directory.
19303 This also means longer startup time; so it goes.
19304 o Fix an assert trigger where an OP would fail to handshake, and we'd
19305 expect it to have a nickname.
19306 o Work around a tsocks bug: do a socks reject when AP connection dies
19307 early, else tsocks goes into an infinite loop.
19310 Changes in version 0.0.4 - 2004-03-26
19311 o When connecting to a dirserver or OR and the network is down,
19315 Changes in version 0.0.3 - 2004-03-26
19316 o Warn and fail if server chose a nickname with illegal characters
19317 o Port to Solaris and Sparc:
19318 - include missing header fcntl.h
19319 - have autoconf find -lsocket -lnsl automatically
19320 - deal with hardware word alignment
19321 - make uname() work (solaris has a different return convention)
19322 - switch from using signal() to sigaction()
19323 o Preliminary work on reputation system:
19324 - Keep statistics on success/fail of connect attempts; they're published
19325 by kill -USR1 currently.
19326 - Add a RunTesting option to try to learn link state by creating test
19327 circuits, even when SocksPort is off.
19328 - Remove unused open circuits when there are too many.
19331 Changes in version 0.0.2 - 2004-03-19
19332 - Include strlcpy and strlcat for safer string ops
19333 - define INADDR_NONE so we compile (but still not run) on solaris
19336 Changes in version 0.0.2pre27 - 2004-03-14
19338 - Allow internal tor networks (we were rejecting internal IPs,
19339 now we allow them if they're set explicitly).
19340 - And fix a few endian issues.
19343 Changes in version 0.0.2pre26 - 2004-03-14
19345 - If a stream times out after 15s without a connected cell, don't
19346 try that circuit again: try a new one.
19347 - Retry streams at most 4 times. Then give up.
19348 - When a dirserver gets a descriptor from an unknown router, it
19349 logs its fingerprint (so the dirserver operator can choose to
19350 accept it even without mail from the server operator).
19351 - Inform unapproved servers when we reject their descriptors.
19352 - Make tor build on Windows again. It works as a client, who knows
19354 - Clearer instructions in the torrc for how to set up a server.
19355 - Be more efficient about reading fd's when our global token bucket
19356 (used for rate limiting) becomes empty.
19358 - Stop asserting that computers always go forward in time. It's
19360 - When we sent a cell (e.g. destroy) and then marked an OR connection
19361 expired, we might close it before finishing a flush if the other
19362 side isn't reading right then.
19363 - Don't allow dirservers to start if they haven't defined
19364 RecommendedVersions
19365 - We were caching transient dns failures. Oops.
19366 - Prevent servers from publishing an internal IP as their address.
19367 - Address a strcat vulnerability in circuit.c
19370 Changes in version 0.0.2pre25 - 2004-03-04
19372 - Put the OR's IP in its router descriptor, not its fqdn. That way
19373 we'll stop being stalled by gethostbyname for nodes with flaky dns,
19376 - If the user typed in an address that didn't resolve, the server
19380 Changes in version 0.0.2pre24 - 2004-03-03
19382 - Fix an assertion failure in dns.c, where we were trying to dequeue
19383 a pending dns resolve even if it wasn't pending
19384 - Fix a spurious socks5 warning about still trying to write after the
19385 connection is finished.
19386 - Hold certain marked_for_close connections open until they're finished
19387 flushing, rather than losing bytes by closing them too early.
19388 - Correctly report the reason for ending a stream
19389 - Remove some duplicate calls to connection_mark_for_close
19390 - Put switch_id and start_daemon earlier in the boot sequence, so it
19391 will actually try to chdir() to options.DataDirectory
19392 - Make 'make test' exit(1) if a test fails; fix some unit tests
19393 - Make tor fail when you use a config option it doesn't know about,
19394 rather than warn and continue.
19395 - Make --version work
19396 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
19399 Changes in version 0.0.2pre23 - 2004-02-29
19401 - Print a statement when the first circ is finished, so the user
19402 knows it's working.
19403 - If a relay cell is unrecognized at the end of the circuit,
19404 send back a destroy. (So attacks to mutate cells are more
19406 - New config option 'excludenodes' to avoid certain nodes for circuits.
19407 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
19408 so you can collect coredumps there.
19410 - Fix a bug in tls flushing where sometimes data got wedged and
19411 didn't flush until more data got sent. Hopefully this bug was
19412 a big factor in the random delays we were seeing.
19413 - Make 'connected' cells include the resolved IP, so the client
19414 dns cache actually gets populated.
19415 - Disallow changing from ORPort=0 to ORPort>0 on hup.
19416 - When we time-out on a stream and detach from the circuit, send an
19417 end cell down it first.
19418 - Only warn about an unknown router (in exitnodes, entrynodes,
19419 excludenodes) after we've fetched a directory.
19422 Changes in version 0.0.2pre22 - 2004-02-26
19424 - Servers publish less revealing uname information in descriptors.
19425 - More memory tracking and assertions, to crash more usefully when
19427 - If the default torrc isn't there, just use some default defaults.
19428 Plus provide an internal dirservers file if they don't have one.
19429 - When the user tries to use Tor as an http proxy, give them an http
19430 501 failure explaining that we're a socks proxy.
19431 - Dump a new router.desc on hup, to help confused people who change
19432 their exit policies and then wonder why router.desc doesn't reflect
19434 - Clean up the generic tor.sh init script that we ship with.
19436 - If the exit stream is pending on the resolve, and a destroy arrives,
19437 then the stream wasn't getting removed from the pending list. I
19438 think this was the one causing recent server crashes.
19439 - Use a more robust poll on OSX 10.3, since their poll is flaky.
19440 - When it couldn't resolve any dirservers, it was useless from then on.
19441 Now it reloads the RouterFile (or default dirservers) if it has no
19443 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
19444 many users don't even *have* a /usr/local/sbin/.
19447 Changes in version 0.0.2pre21 - 2004-02-18
19449 - There's a ChangeLog file that actually reflects the changelog.
19450 - There's a 'torify' wrapper script, with an accompanying
19451 tor-tsocks.conf, that simplifies the process of using tsocks for
19452 tor. It even has a man page.
19453 - The tor binary gets installed to sbin rather than bin now.
19454 - Retry streams where the connected cell hasn't arrived in 15 seconds
19455 - Clean up exit policy handling -- get the default out of the torrc,
19456 so we can update it without forcing each server operator to fix
19458 - Allow imaps and pop3s in default exit policy
19460 - Prevent picking middleman nodes as the last node in the circuit
19463 Changes in version 0.0.2pre20 - 2004-01-30
19465 - We now have a deb package, and it's in debian unstable. Go to
19466 it, apt-getters. :)
19467 - I've split the TotalBandwidth option into BandwidthRate (how many
19468 bytes per second you want to allow, long-term) and
19469 BandwidthBurst (how many bytes you will allow at once before the cap
19470 kicks in). This better token bucket approach lets you, say, set
19471 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
19472 performance while not exceeding your monthly bandwidth quota.
19473 - Push out a tls record's worth of data once you've got it, rather
19474 than waiting until you've read everything waiting to be read. This
19475 may improve performance by pipelining better. We'll see.
19476 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
19477 from failed circuits (if they haven't been connected yet) and attach
19479 - Expire old streams that haven't managed to connect. Some day we'll
19480 have them reattach to new circuits instead.
19483 - Fix several memory leaks that were causing servers to become bloated
19485 - Fix a few very rare assert triggers. A few more remain.
19486 - Setuid to User _before_ complaining about running as root.
19489 Changes in version 0.0.2pre19 - 2004-01-07
19491 - Fix deadlock condition in dns farm. We were telling a child to die by
19492 closing the parent's file descriptor to him. But newer children were
19493 inheriting the open file descriptor from the parent, and since they
19494 weren't closing it, the socket never closed, so the child never read
19495 eof, so he never knew to exit. Similarly, dns workers were holding
19496 open other sockets, leading to all sorts of chaos.
19497 - New cleaner daemon() code for forking and backgrounding.
19498 - If you log to a file, it now prints an entry at the top of the
19499 logfile so you know it's working.
19500 - The onionskin challenge length was 30 bytes longer than necessary.
19501 - Started to patch up the spec so it's not quite so out of date.
19504 Changes in version 0.0.2pre18 - 2004-01-02
19506 - Fix endian issues with the 'integrity' field in the relay header.
19507 - Fix a potential bug where connections in state
19508 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
19511 Changes in version 0.0.2pre17 - 2003-12-30
19513 - Made --debuglogfile (or any second log file, actually) work.
19514 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
19515 adversary could force us into an infinite loop.
19518 - Each onionskin handshake now includes a hash of the computed key,
19519 to prove the server's identity and help perfect forward secrecy.
19520 - Changed cell size from 256 to 512 bytes (working toward compatibility
19522 - Changed cell length to 2 bytes, and moved it to the relay header.
19523 - Implemented end-to-end integrity checking for the payloads of
19525 - Separated streamid from 'recognized' (otherwise circuits will get
19526 messed up when we try to have streams exit from the middle). We
19527 use the integrity-checking to confirm that a cell is addressed to
19529 - Randomize the initial circid and streamid values, so an adversary who
19530 breaks into a node can't learn how many circuits or streams have
19534 Changes in version 0.0.2pre16 - 2003-12-14
19536 - Fixed a bug that made HUP trigger an assert
19537 - Fixed a bug where a circuit that immediately failed wasn't being
19538 counted as a failed circuit in counting retries.
19541 - Now we close the circuit when we get a truncated cell: otherwise we're
19542 open to an anonymity attack where a bad node in the path truncates
19543 the circuit and then we open streams at him.
19544 - Add port ranges to exit policies
19545 - Add a conservative default exit policy
19546 - Warn if you're running tor as root
19547 - on HUP, retry OR connections and close/rebind listeners
19548 - options.EntryNodes: try these nodes first when picking the first node
19549 - options.ExitNodes: if your best choices happen to include any of
19550 your preferred exit nodes, you choose among just those preferred
19552 - options.ExcludedNodes: nodes that are never picked in path building
19555 Changes in version 0.0.2pre15 - 2003-12-03
19556 o Robustness and bugfixes:
19557 - Sometimes clients would cache incorrect DNS resolves, which would
19558 really screw things up.
19559 - An OP that goes offline would slowly leak all its sockets and stop
19561 - A wide variety of bugfixes in exit node selection, exit policy
19562 handling, and processing pending streams when a new circuit is
19564 - Pick nodes for a path only from those the directory says are up
19565 - Choose randomly from all running dirservers, not always the first one
19566 - Increase allowed http header size for directory fetch.
19567 - Stop writing to stderr (if we're daemonized it will be closed).
19568 - Enable -g always, so cores will be more useful to me.
19569 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
19572 - Wrote a man page. It lists commonly used options.
19575 - Change default loglevel to warn.
19576 - Make PidFile default to null rather than littering in your CWD.
19577 - OnionRouter config option is now obsolete. Instead it just checks
19579 - Moved to a single unified torrc file for both clients and servers.
19582 Changes in version 0.0.2pre14 - 2003-11-29
19583 o Robustness and bugfixes:
19584 - Force the admin to make the DataDirectory himself
19585 - to get ownership/permissions right
19586 - so clients no longer make a DataDirectory and then never use it
19587 - fix bug where a client who was offline for 45 minutes would never
19588 pull down a directory again
19589 - fix (or at least hide really well) the dns assert bug that was
19590 causing server crashes
19591 - warnings and improved robustness wrt clockskew for certs
19592 - use the native daemon(3) to daemonize, when available
19593 - exit if bind() fails
19594 - exit if neither socksport nor orport is defined
19595 - include our own tor_timegm (Win32 doesn't have its own)
19596 - bugfix for win32 with lots of connections
19597 - fix minor bias in PRNG
19598 - make dirserver more robust to corrupt cached directory
19601 - Wrote the design document (woo)
19603 o Circuit building and exit policies:
19604 - Circuits no longer try to use nodes that the directory has told them
19606 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
19607 bitcounts (18.0.0.0/8).
19608 - Make AP connections standby for a circuit if no suitable circuit
19609 exists, rather than failing
19610 - Circuits choose exit node based on addr/port, exit policies, and
19611 which AP connections are standing by
19612 - Bump min pathlen from 2 to 3
19613 - Relay end cells have a payload to describe why the stream ended.
19614 - If the stream failed because of exit policy, try again with a new
19616 - Clients have a dns cache to remember resolved addresses.
19617 - Notice more quickly when we have no working circuits
19620 - APPort is now called SocksPort
19621 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
19623 - RecommendedVersions is now a config variable rather than
19624 hardcoded (for dirservers)
19625 - Reloads config on HUP
19626 - Usage info on -h or --help
19627 - If you set User and Group config vars, it'll setu/gid to them.
19630 Changes in version 0.0.2pre13 - 2003-10-19
19631 o General stability:
19632 - SSL_write no longer fails when it returns WANTWRITE and the number
19633 of bytes in the buf has changed by the next SSL_write call.
19634 - Fix segfault fetching directory when network is down
19635 - Fix a variety of minor memory leaks
19636 - Dirservers reload the fingerprints file on HUP, so I don't have
19637 to take down the network when I approve a new router
19638 - Default server config file has explicit Address line to specify fqdn
19641 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
19642 - Make listener connections not ever alloc bufs
19644 o Autoconf improvements:
19645 - don't clobber an external CFLAGS in ./configure
19646 - Make install now works
19647 - create var/lib/tor on make install
19648 - autocreate a tor.sh initscript to help distribs
19649 - autocreate the torrc and sample-server-torrc with correct paths
19651 o Log files and Daemonizing now work:
19652 - If --DebugLogFile is specified, log to it at -l debug
19653 - If --LogFile is specified, use it instead of commandline
19654 - If --RunAsDaemon is set, tor forks and backgrounds on startup