1 Changes in version 0.2.4.1-alpha - 2012-09-05
2 Tor 0.2.4.1-alpha adds ... XXX
4 This is the first alpha release in a new series, so expect there to
5 be bugs. Users who would rather test out a more stable branch should
6 stay with 0.2.3.x for now.
8 o Major features (bridges):
9 - Bridges now report the pluggable transports they support to the
10 bridge authority, so it can pass the supported transports on to
11 bridgedb and/or eventually do reachability testing. Implements
14 o Major features (IPv6):
15 - Bridge authorities now accept IPv6 bridge addresses and include
16 them in network status documents. Implements ticket 5534.
17 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
18 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
19 to happen. Implements ticket 5535.
20 - All kind of relays, not just bridges, can now advertise an IPv6
21 OR port. Implements ticket 6362.
22 - Directory authorities vote on IPv6 OR ports using the new consensus
23 method 14. Implements ticket 6363.
25 o Major features (build):
26 - Switch to a nonrecursive Makefile structure. Now instead of each
27 Makefile.am invoking other Makefile.am's, there is a master
28 Makefile.am that includes the others. This change makes our build
29 process slightly more maintainable, and improves parallelism for
30 building with make -j. Original patch by Stewart Smith; various
31 fixes by Jim Meyering.
32 - Where available, we now use automake's "silent" make rules by
33 default, so that warnings are easier to spot. You can get the old
34 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
36 o Minor features (code security and spec conformance):
37 - Clear keys and key-derived material left on the stack in
38 rendservice.c and rendclient.c. Check return value of
39 crypto_pk_write_private_key_to_string() in end_service_load_keys().
40 These fixes should make us more forward-secure against cold-boot
41 attacks and the like. Fixes bug 2385.
42 - Reject EXTEND cells sent to nonexistent streams. According to the
43 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
44 we were only checking for stream IDs that were currently in use.
45 Found while hunting for more instances of bug 6271. Bugfix on
46 0.0.2pre8, which introduced incremental circuit construction.
48 o Minor features (streamlining);
49 - No longer include the "opt" prefix when generating routerinfos
50 or v2 directories: it has been needless since Tor 0.1.2. Closes
52 - Remove some now-needless code that tried to aggressively flush
53 OR connections as data was added to them. Since 0.2.0.1-alpha, our
54 cell queue logic has saved us from the failure mode that this code
55 was supposed to prevent. Removing this code will limit the number
56 of baroque control flow paths through Tor's network logic. Reported
57 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
59 o Minor features (controller):
60 - Add a "GETINFO signal/names" control port command. Implements
62 - Provide default values for all options via "GETINFO config/defaults".
63 Implements ticket 4971.
65 o Minor features (IPv6):
66 - New config option "AuthDirHasIPv6Connectivity auto" that ... XXX
67 Implements feature 5974.
68 - A relay with an IPv6 OR port now sends that address in NETINFO
69 cells (in addition to its other address). Implements ticket 6364.
70 - New config option AuthDirPublishIPv6. Implements ticket 6406.
72 o Minor features (log messages):
73 - Omit the first heartbeat log message, because it never has anything
74 useful to say, and it clutters up the bootstrapping messages.
76 - Don't log about reloading the microdescriptor cache at startup. Our
77 bootstrap warnings are supposed to tell the user when there's a
78 problem, and our bootstrap notices say when there isn't. Resolves
79 ticket 6759; bugfix on 0.2.2.6-alpha.
80 - Don't log "I learned some more directory information" when we're
81 reading cached directory information. Reserve it for when new
82 directory information arrives in response to a fetch. Resolves
84 - Prevent rounding error in path bias counts when scaling
85 them down, and use the correct scale factor default. Also demote
86 some path bias related log messages down a level and make others
87 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
88 - We no longer warn so much when generating manpages from their
91 o Code simplifications and refactoring:
92 - Enhance our internal sscanf replacement so that we can eliminate
93 the last remaining uses of the system sscanf. (Though those uses
94 of sscanf were safe, sscanf itself is generally error prone, so
95 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
97 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
98 - Move last_reachable and testing_since from routerinfo_t to node_t.
99 Implements ticket 5529.
100 - Add replaycache_t structure, functions and unit tests, then refactor
101 rend_service_introduce() to be more clear to read, improve, debug,
102 and test. Resolves bug 6177.
103 - Finally remove support for malloc_good_size and malloc_usable_size.
104 We had hoped that these functions would let us eke a little more
105 memory out of our malloc implementation. Unfortunately, the only
106 implementations that provided these functions are also ones that
107 are already efficient about not overallocation: they never got us
108 more than 7 or so bytes per allocation. Removing them saves us a
109 little code complexity and a nontrivial amount of build complexity.
112 - Tor maintainers now require Automake version 1.9 or later to build
113 Tor from the Git repository. (Automake is not required when building
114 from a source distribution.)
117 Changes in version 0.2.3.21-rc - 2012-09-05
118 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
119 series. It fixes a trio of potential security bugs, fixes a bug where
120 we were leaving some of the fast relays out of the microdescriptor
121 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
122 and cleans up other smaller issues.
124 o Major bugfixes (security):
125 - Tear down the circuit if we get an unexpected SENDME cell. Clients
126 could use this trick to make their circuits receive cells faster
127 than our flow control would have allowed, or to gum up the network,
128 or possibly to do targeted memory denial-of-service attacks on
129 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
130 from July 2002, before the release of Tor 0.0.0. We had committed
131 this patch previously, but we had to revert it because of bug 6271.
132 Now that 6271 is fixed, this patch appears to work.
133 - Reject any attempt to extend to an internal address. Without
134 this fix, a router could be used to probe addresses on an internal
135 network to see whether they were accepting connections. Fixes bug
136 6710; bugfix on 0.0.8pre1.
137 - Do not crash when comparing an address with port value 0 to an
138 address policy. This bug could have been used to cause a remote
139 assertion failure by or against directory authorities, or to
140 allow some applications to crash clients. Fixes bug 6690; bugfix
144 - Remove the upper bound on microdescriptor length. We were hitting
145 the limit for routers with complex exit policies or family
146 declarations, causing clients to not use them. Fixes the first
147 piece of bug 6404; fix on 0.2.2.6-alpha.
148 - Detect "ORPort 0" as meaning, uniformly, that we're not running
149 as a relay. Previously, some of our code would treat the presence
150 of any ORPort line as meaning that we should act like a relay,
151 even though our new listener code would correctly not open any
152 ORPorts for ORPort 0. Similar bugs in other Port options are also
153 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
156 - Avoid a pair of double-free and use-after-mark bugs that can
157 occur with certain timings in canceled and re-received DNS
158 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
159 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
160 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
161 - Allow one-hop directory fetching circuits the full "circuit build
162 timeout" period, rather than just half of it, before failing them
163 and marking the relay down. This fix should help reduce cases where
164 clients declare relays (or worse, bridges) unreachable because
165 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
166 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
168 - Authorities no longer include any router in their microdescriptor
169 consensuses for which they couldn't generate or agree on a
170 microdescriptor. Fixes the second piece of bug 6404; fix on
172 - Detect and reject attempts to specify both "FooPort" and
173 "FooPort 0" in the same configuration domain. (It's still okay
174 to have a FooPort in your configuration file, and use "FooPort 0"
175 on the command line to disable it.) Fixes the second half of bug
176 6507; bugfix on 0.2.3.3-alpha.
177 - Make wildcarded addresses (that is, ones beginning with "*.") work
178 when provided via the controller's MapAddress command. Previously,
179 they were accepted, but we never actually noticed that they were
180 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
181 - Add a (probably redundant) memory clear between iterations of
182 the router status voting loop, to prevent future coding errors
183 where data might leak between iterations of the loop. Resolves
186 o Minor bugfixes (log messages):
187 - Downgrade "set buildtimeout to low value" messages to "info"
188 severity; they were never an actual problem, there was never
189 anything reasonable to do about them, and they tended to spam logs
190 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
191 - Downgrade path-bias warning messages to "info". We'll try to get
192 them working better in 0.2.4. Add internal circuit construction
193 state to protect against the noisy warn message "Unexpectedly high
194 circuit_successes". Also add some additional rate-limited notice
195 messages to help determine the root cause of the warn. Fixes bug
196 6475. Bugfix against 0.2.3.17-beta.
197 - Move log message when unable to find a microdesc in a routerstatus
198 entry to parse time. Previously we'd spam this warning every time
199 we tried to figure out which microdescriptors to download. Fixes
200 the third piece of bug 6404; fix on 0.2.3.18-rc.
203 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
204 change when the authority is deciding whether to accept a newly
205 uploaded descriptor. Implements ticket 6423.
206 - Add missing documentation for consensus and microdesc files.
207 Resolves ticket 6732.
210 Changes in version 0.2.2.38 - 2012-08-12
211 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
212 attack that could in theory leak path information.
215 - Avoid an uninitialized memory read when reading a vote or consensus
216 document that has an unrecognized flavor name. This read could
217 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
218 - Try to leak less information about what relays a client is
219 choosing to a side-channel attacker. Previously, a Tor client would
220 stop iterating through the list of available relays as soon as it
221 had chosen one, thus finishing a little earlier when it picked
222 a router earlier in the list. If an attacker can recover this
223 timing information (nontrivial but not proven to be impossible),
224 they could learn some coarse-grained information about which relays
225 a client was picking (middle nodes in particular are likelier to
226 be affected than exits). The timing attack might be mitigated by
227 other factors (see bug 6537 for some discussion), but it's best
228 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
231 Changes in version 0.2.3.20-rc - 2012-08-05
232 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
233 series. It fixes a pair of code security bugs and a potential anonymity
234 issue, updates our RPM spec files, and cleans up other smaller issues.
237 - Avoid read-from-freed-memory and double-free bugs that could occur
238 when a DNS request fails while launching it. Fixes bug 6480;
239 bugfix on 0.2.0.1-alpha.
240 - Avoid an uninitialized memory read when reading a vote or consensus
241 document that has an unrecognized flavor name. This read could
242 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
243 - Try to leak less information about what relays a client is
244 choosing to a side-channel attacker. Previously, a Tor client would
245 stop iterating through the list of available relays as soon as it
246 had chosen one, thus finishing a little earlier when it picked
247 a router earlier in the list. If an attacker can recover this
248 timing information (nontrivial but not proven to be impossible),
249 they could learn some coarse-grained information about which relays
250 a client was picking (middle nodes in particular are likelier to
251 be affected than exits). The timing attack might be mitigated by
252 other factors (see bug 6537 for some discussion), but it's best
253 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
256 - Try to make the warning when giving an obsolete SOCKSListenAddress
257 a little more useful.
258 - Terminate active server managed proxies if Tor stops being a
259 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
260 - Provide a better error message about possible OSX Asciidoc failure
261 reasons. Fixes bug 6436.
262 - Warn when Tor is configured to use accounting in a way that can
263 link a hidden service to some other hidden service or public
264 address. Resolves ticket 6490.
267 - Check return value of fputs() when writing authority certificate
268 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
269 - Ignore ServerTransportPlugin lines when Tor is not configured as
270 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
271 - When disabling guards for having too high a proportion of failed
272 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
276 - Update our default RPM spec files to work with mock and rpmbuild
277 on RHEL/Fedora. They have an updated set of dependencies and
278 conflicts, a fix for an ancient typo when creating the "_tor"
279 user, and better instructions. Thanks to Ondrej Mikle for the
280 patch series. Fixes bug 6043.
283 - Make it possible to set the TestingTorNetwork configuration
284 option using AlternateDirAuthority and AlternateBridgeAuthority
285 as an alternative to setting DirServer. Addresses ticket 6377.
288 - Clarify the documentation for the Alternate*Authority options.
290 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
292 o Code simplification and refactoring:
293 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
294 10 lines. Also, don't nest them. Doing so in the past has
295 led to hard-to-debug code. The new style is to use the
296 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
299 Changes in version 0.2.3.19-rc - 2012-07-06
300 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
301 series. It fixes the compile on Windows, reverts to a GeoIP database
302 that isn't as broken, and fixes a flow control bug that has been around
303 since the beginning of Tor.
306 - Fix a bug handling SENDME cells on nonexistent streams that could
307 result in bizarre window values. Report and patch contributed
308 pseudonymously. Fixes part of bug 6271. This bug was introduced
309 before the first Tor release, in svn commit r152.
310 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
311 June 2012 database, Maxmind marked many Tor relays as country "A1",
312 which will cause risky behavior for clients that set EntryNodes
313 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
314 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
315 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
318 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
319 bugfix on 0.2.1.10-alpha.
322 Changes in version 0.2.3.18-rc - 2012-06-28
323 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
324 series. It fixes a few smaller bugs, but generally appears stable.
325 Please test it and let us know whether it is!
328 - Allow wildcarded mapaddress targets to be specified on the
329 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
330 - Make our linker option detection code more robust against linkers
331 such as on FreeBSD 8, where a bad combination of options completes
332 successfully but makes an unrunnable binary. Fixes bug 6173;
333 bugfix on 0.2.3.17-beta.
335 o Minor bugfixes (on 0.2.2.x and earlier):
336 - Avoid a false positive in the util/threads unit test by increasing
337 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
338 - Replace "Sending publish request" log messages with "Launching
339 upload", so that they no longer confusingly imply that we're
340 sending something to a directory we might not even be connected
341 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
342 - Make sure to set *socket_error in all error cases in
343 connection_connect(), so it can't produce a warning about
344 errno being zero from errno_to_orconn_end_reason(). Bugfix on
345 0.2.1.1-alpha; resolves ticket 6028.
346 - Downgrade "Got a certificate, but we already have it" log messages
347 from warning to info, except when we're a dirauth. Fixes bug 5238;
348 bugfix on 0.2.1.7-alpha.
349 - When checking for requested signatures on the latest consensus
350 before serving it to a client, make sure to check the right
351 consensus flavor. Bugfix on 0.2.2.6-alpha.
352 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
353 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
355 o Minor bugfixes (on 0.2.3.x):
356 - Make format_helper_exit_status() avoid unnecessary space padding
357 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
359 - Downgrade a message about cleaning the microdescriptor cache to
360 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
361 - Log a BUG message at severity INFO if we have a networkstatus with
362 a missing entry for some microdescriptor. Continues on a patch
364 - Improve the log message when a managed proxy fails to launch. Fixes
365 bug 5099; bugfix on 0.2.3.6-alpha.
366 - Don't do DNS lookups when parsing corrupted managed proxy protocol
367 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
368 - When formatting wildcarded address mappings for the controller,
369 be sure to include "*." as appropriate. Partially fixes bug 6244;
370 bugfix on 0.2.3.9-alpha.
371 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
372 Bugfix on 0.2.3.13-alpha.
373 - Stop logging messages about running with circuit timeout learning
374 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
375 - Disable a spurious warning about reading on a marked and flushing
376 connection. We shouldn't be doing that, but apparently we
377 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
378 - Fix a bug that stopped AllowDotExit from working on addresses
379 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
382 o Code simplification, refactoring, unit tests:
383 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
384 Libevent's notion of cached time when possible.
385 - Remove duplicate code for invoking getrlimit() from control.c.
386 - Add a unit test for the environment_variable_names_equal function.
389 - Document the --defaults-torrc option, and the new (in 0.2.3)
390 semantics for overriding, extending, and clearing lists of
391 options. Closes bug 4748.
394 Changes in version 0.2.3.17-beta - 2012-06-15
395 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
396 gets our TLS handshake back on track for being able to blend in with
397 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
398 with Vidalia, and otherwise continues to get us closer to a release
402 - Enable gcc and ld hardening by default. Resolves ticket 5210.
403 - Update TLS cipher list to match Firefox 8 and later. Resolves
405 - Implement the client side of proposal 198: remove support for
406 clients falsely claiming to support standard ciphersuites that
407 they can actually provide. As of modern OpenSSL versions, it's not
408 necessary to fake any standard ciphersuite, and doing so prevents
409 us from using better ciphersuites in the future, since servers
410 can't know whether an advertised ciphersuite is really supported or
411 not. Some hosts -- notably, ones with very old versions of OpenSSL
412 or where OpenSSL has been built with ECC disabled -- will stand
413 out because of this change; TBB users should not be affected.
416 - Change the default value for DynamicDHGroups (introduced in
417 0.2.3.9-alpha) to 0. This feature can make Tor relays less
418 identifiable by their use of the mod_ssl DH group, but at
419 the cost of some usability (#4721) and bridge tracing (#6087)
420 regressions. Resolves ticket 5598.
421 - Send a CRLF at the end of each STATUS_* control protocol event. This
422 bug tickled a bug in Vidalia which would make it freeze. Fixes
423 bug 6094; bugfix on 0.2.3.16-alpha.
426 - Disable writing on marked-for-close connections when they are
427 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
428 bug 5263; bugfix on 0.0.2pre13, where we first added a special
429 case for flushing marked connections.
430 - Detect SSL handshake even when the initial attempt to write the
431 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
432 - Change the AllowDotExit rules so they should actually work.
433 We now enforce AllowDotExit only immediately after receiving an
434 address via SOCKS or DNSPort: other sources are free to provide
435 .exit addresses after the resolution occurs. Fixes bug 3940;
436 bugfix on 0.2.2.1-alpha.
437 - Fix a (harmless) integer overflow in cell statistics reported by
438 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
439 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
440 right places and never depends on the consensus parameters or
441 computes adaptive timeouts when it is disabled. Fixes bug 5049;
442 bugfix on 0.2.2.14-alpha.
443 - When building Tor on Windows with -DUNICODE (not default), ensure
444 that error messages, filenames, and DNS server names are always
445 NUL-terminated when we convert them to a single-byte encoding.
446 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
447 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
448 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
449 - Fix an edge case where TestingTorNetwork is set but the authorities
450 and relays all have an uptime of zero, where the private Tor network
451 could briefly lack support for hidden services. Fixes bug 3886;
452 bugfix on 0.2.2.18-alpha.
453 - Correct the manpage's descriptions for the default values of
454 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
456 - Fix the documentation for the --hush and --quiet command line
457 options, which changed their behavior back in 0.2.3.3-alpha.
458 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
462 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
463 more information to it, so that we can track it down in case it
464 returns again. Mitigates bug 5235.
465 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
466 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
467 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
468 - Warn the user when HTTPProxy, but no other proxy type, is
469 configured. This can cause surprising behavior: it doesn't send
470 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
471 directory traffic only. Resolves ticket 4663.
472 - Issue a notice if a guard completes less than 40% of your circuits.
473 Threshold is configurable by torrc option PathBiasNoticeRate and
474 consensus parameter pb_noticepct. There is additional, off-by-
475 default code to disable guards which fail too many circuits.
476 Addresses ticket 5458.
477 - Update to the June 6 2012 Maxmind GeoLite Country database.
479 o Code simplifications and refactoring:
480 - Remove validate_pluggable_transports_config(): its warning
481 message is now handled by connection_or_connect().
484 Changes in version 0.2.2.37 - 2012-06-06
485 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
486 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
490 - Work around a bug in OpenSSL that broke renegotiation with TLS
491 1.1 and TLS 1.2. Without this workaround, all attempts to speak
492 the v2 Tor connection protocol when both sides were using OpenSSL
493 1.0.1 would fail. Resolves ticket 6033.
494 - When waiting for a client to renegotiate, don't allow it to add
495 any bytes to the input buffer. This fixes a potential DoS issue.
496 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
497 - Fix an edge case where if we fetch or publish a hidden service
498 descriptor, we might build a 4-hop circuit and then use that circuit
499 for exiting afterwards -- even if the new last hop doesn't obey our
500 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
503 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
504 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
507 - Tell GCC and Clang to check for any errors in format strings passed
508 to the tor_v*(print|scan)f functions.
511 Changes in version 0.2.3.16-alpha - 2012-06-05
512 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
513 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
514 currently). It also fixes a variety of smaller bugs and other cleanups
515 that get us closer to a release candidate.
517 o Major bugfixes (general):
518 - Work around a bug in OpenSSL that broke renegotiation with TLS
519 1.1 and TLS 1.2. Without this workaround, all attempts to speak
520 the v2 Tor connection protocol when both sides were using OpenSSL
521 1.0.1 would fail. Resolves ticket 6033.
522 - When waiting for a client to renegotiate, don't allow it to add
523 any bytes to the input buffer. This fixes a potential DoS issue.
524 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
525 - Pass correct OR address to managed proxies (like obfsproxy),
526 even when ORListenAddress is used. Fixes bug 4865; bugfix on
528 - The advertised platform of a router now includes only its operating
529 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
530 service pack level (for Windows) or its CPU architecture (for Unix).
531 We also no longer include the "git-XYZ" tag in the version. Resolves
534 o Major bugfixes (clients):
535 - If we are unable to find any exit that supports our predicted ports,
536 stop calling them predicted, so that we don't loop and build
537 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
538 which introduced predicted ports.
539 - Fix an edge case where if we fetch or publish a hidden service
540 descriptor, we might build a 4-hop circuit and then use that circuit
541 for exiting afterwards -- even if the new last hop doesn't obey our
542 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
543 - Check at each new consensus whether our entry guards were picked
544 long enough ago that we should rotate them. Previously, we only
545 did this check at startup, which could lead to us holding a guard
546 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
547 - When fetching a bridge descriptor from a bridge authority,
548 always do so anonymously, whether we have been able to open
549 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
550 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
551 but we'll need to wait for bug 6010 before it's actually usable.
553 o Major bugfixes (directory authorities):
554 - When computing weight parameters, behave more robustly in the
555 presence of a bad bwweightscale value. Previously, the authorities
556 would crash if they agreed on a sufficiently broken weight_scale
557 value: now, they use a reasonable default and carry on. Partial
558 fix for 5786; bugfix on 0.2.2.17-alpha.
559 - Check more thoroughly to prevent a rogue authority from
560 double-voting on any consensus directory parameter. Previously,
561 authorities would crash in this case if the total number of
562 votes for any parameter exceeded the number of active voters,
563 but would let it pass otherwise. Partial fix for bug 5786; bugfix
567 - Rate-limit log messages when asked to connect anonymously to
568 a private address. When these hit, they tended to hit fast and
569 often. Also, don't bother trying to connect to addresses that we
570 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
571 reply makes us think we have been lied to, even when the address the
572 client tried to connect to was "localhost." Resolves ticket 2822.
573 - Allow packagers to insert an extra string in server descriptor
574 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
575 Resolves the rest of ticket 2988.
576 - Raise the threshold of server descriptors needed (75%) and exit
577 server descriptors needed (50%) before we will declare ourselves
578 bootstrapped. This will make clients start building circuits a
579 little later, but makes the initially constructed circuits less
580 skewed and less in conflict with further directory fetches. Fixes
582 - Close any connection that sends unrecognized junk before the
583 handshake. Solves an issue noted in bug 4369.
584 - Improve log messages about managed transports. Resolves ticket 5070.
585 - Tag a bridge's descriptor as "never to be sent unencrypted".
586 This shouldn't matter, since bridges don't open non-anonymous
587 connections to the bridge authority and don't allow unencrypted
588 directory connections from clients, but we might as well make
589 sure. Closes bug 5139.
590 - Expose our view of whether we have gone dormant to the controller,
591 via a new "GETINFO dormant" value. Torbutton and other controllers
592 can use this to avoid doing periodic requests through Tor while
593 it's dormant (bug 4718). Fixes bug 5954.
594 - Tell GCC and Clang to check for any errors in format strings passed
595 to the tor_v*(print|scan)f functions.
596 - Update to the May 1 2012 Maxmind GeoLite Country database.
598 o Minor bugfixes (already included in 0.2.2.36):
599 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
600 Fixes bug 5346; bugfix on 0.0.8pre3.
601 - Correct parsing of certain date types in parse_http_time().
602 Without this patch, If-Modified-Since would behave
603 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
604 Esteban Manchado Velázques.
605 - Make our number-parsing functions always treat too-large values
606 as an error, even when those values exceed the width of the
607 underlying type. Previously, if the caller provided these
608 functions with minima or maxima set to the extreme values of the
609 underlying integer type, these functions would return those
610 values on overflow rather than treating overflow as an error.
611 Fixes part of bug 5786; bugfix on 0.0.9.
612 - If we hit the error case where routerlist_insert() replaces an
613 existing (old) server descriptor, make sure to remove that
614 server descriptor from the old_routers list. Fix related to bug
615 1776. Bugfix on 0.2.2.18-alpha.
616 - Clarify the behavior of MaxCircuitDirtiness with hidden service
617 circuits. Fixes issue 5259.
619 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
620 - Prevent a null-pointer dereference when receiving a data cell
621 for a nonexistent stream when the circuit in question has an
622 empty deliver window. We don't believe this is triggerable,
623 since we don't currently allow deliver windows to become empty,
624 but the logic is tricky enough that it's better to make the code
625 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
626 - Fix a memory leak when trying to launch a DNS request when the
627 network is disabled or the nameservers are unconfigurable. Fixes
628 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
629 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
630 - Don't hold a Windows file handle open for every file mapping;
631 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
633 - Avoid O(n^2) performance characteristics when parsing a large
634 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
635 - Format more doubles with %f, not %lf. Patch from grarpamp to make
636 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
638 - Make our replacement implementation of strtok_r() compatible with
639 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
640 bugfix on 0.2.2.1-alpha.
641 - Fix a NULL-pointer dereference on a badly formed
642 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
643 bugfix on 0.2.2.9-alpha.
644 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
645 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
646 - Defensively refactor rend_mid_rendezvous() so that protocol
647 violations and length checks happen in the beginning. Fixes
649 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
650 that IPv6 stuff will compile on MSVC, and compilation issues
651 will be easier to track down. Fixes bug 5861.
653 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
654 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
655 resource exhaustion, so that clients can adjust their load to
656 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
657 started using END_STREAM_REASON_RESOURCELIMIT.
658 - Don't check for whether the address we're using for outbound
659 connections has changed until after the outbound connection has
660 completed. On Windows, getsockname() doesn't succeed until the
661 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
662 - If the configuration tries to set MyFamily on a bridge, refuse to
663 do so, and warn about the security implications. Fixes bug 4657;
664 bugfix on 0.2.0.3-alpha.
665 - If the client fails to set a reasonable set of ciphersuites
666 during its v2 handshake renegotiation, allow the renegotiation to
667 continue nevertheless (i.e. send all the required certificates).
668 Fixes bug 4591; bugfix on 0.2.0.20-rc.
669 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
670 option is set to 0 (which Vidalia version 0.2.16 now does when
671 a SAVECONF attempt fails), perform other actions that SIGHUP
672 usually causes (like reopening the logs). Fixes bug 5095; bugfix
674 - If we fail to write a microdescriptor to the disk cache, do not
675 continue replacing the old microdescriptor file. Fixes bug 2954;
676 bugfix on 0.2.2.6-alpha.
677 - Exit nodes don't need to fetch certificates for authorities that
678 they don't recognize; only directory authorities, bridges,
679 and caches need to do that. Fixes part of bug 2297; bugfix on
681 - Correctly handle checking the permissions on the parent
682 directory of a control socket in the root directory. Bug found
683 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
685 - When told to add a bridge with the same digest as a preexisting
686 bridge but a different addr:port, change the addr:port as
687 requested. Previously we would not notice the change. Fixes half
688 of bug 5603; fix on 0.2.2.26-beta.
689 - End AUTHCHALLENGE error messages (in the control protocol) with
690 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
692 o Minor bugfixes (on 0.2.3.x):
693 - Turn an assertion (that the number of handshakes received as a
694 server is not < 1) into a warning. Fixes bug 4873; bugfix on
696 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
697 we had reversed them when the answer was cached.) Fixes bug
698 5723; bugfix on 0.2.3.1-alpha.
699 - Work correctly on Linux systems with accept4 support advertised in
700 their headers, but without accept4 support in the kernel. Fix
701 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
702 - When told to add a bridge with the same addr:port as a preexisting
703 bridge but a different transport, change the transport as
704 requested. Previously we would not notice the change. Fixes half
705 of bug 5603; fix on 0.2.3.2-alpha.
706 - Avoid a "double-reply" warning when replying to a SOCKS request
707 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
708 bugfix on 0.2.3.4-alpha.
709 - Fix a bug where a bridge authority crashes if it has seen no
710 directory requests when it's time to write statistics to disk.
711 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
713 - Don't try to open non-control listeners when DisableNetwork is set.
714 Previously, we'd open all listeners, then immediately close them.
715 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
716 - Don't abort the managed proxy protocol if the managed proxy
717 sends us an unrecognized line; ignore it instead. Fixes bug
718 5910; bugfix on 0.2.3.9-alpha.
719 - Fix a compile warning in crypto.c when compiling with clang 3.1.
720 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
721 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
722 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
723 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
724 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
725 - Resolve numerous small warnings and build issues with MSVC. Resolves
728 o Documentation fixes:
729 - Improve the manual's documentation for the NT Service command-line
730 options. Addresses ticket 3964.
731 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
732 - Document the changes to the ORPort and DirPort options, and the
733 fact that {OR/Dir}ListenAddress is now unnecessary (and
734 therefore deprecated). Resolves ticket 5597.
737 - Remove the torrc.bridge file: we don't use it for anything, and
738 it had become badly desynchronized from torrc.sample. Resolves
742 Changes in version 0.2.2.36 - 2012-05-24
743 Tor 0.2.2.36 updates the addresses for two of the eight directory
744 authorities, fixes some potential anonymity and security issues,
745 and fixes several crash bugs.
747 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
748 known flaws, and nobody should be using them. You should upgrade. If
749 you're using a Linux or BSD and its packages are obsolete, stop using
750 those packages and upgrade anyway.
752 o Directory authority changes:
753 - Change IP address for maatuska (v3 directory authority).
754 - Change IP address for ides (v3 directory authority), and rename
758 - When building or running with any version of OpenSSL earlier
759 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
760 versions have a bug (CVE-2011-4576) in which their block cipher
761 padding includes uninitialized data, potentially leaking sensitive
762 information to any peer with whom they make a SSLv3 connection. Tor
763 does not use SSL v3 by default, but a hostile client or server
764 could force an SSLv3 connection in order to gain information that
765 they shouldn't have been able to get. The best solution here is to
766 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
767 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
768 to make sure that the bug can't happen.
769 - Never use a bridge or a controller-supplied node as an exit, even
770 if its exit policy allows it. Found by wanoskarnet. Fixes bug
771 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
772 and 0.2.0.3-alpha (for bridge-purpose descriptors).
773 - Only build circuits if we have a sufficient threshold of the total
774 descriptors that are marked in the consensus with the "Exit"
775 flag. This mitigates an attack proposed by wanoskarnet, in which
776 all of a client's bridges collude to restrict the exit nodes that
777 the client knows about. Fixes bug 5343.
778 - Provide controllers with a safer way to implement the cookie
779 authentication mechanism. With the old method, if another locally
780 running program could convince a controller that it was the Tor
781 process, then that program could trick the controller into telling
782 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
783 authentication method uses a challenge-response approach to prevent
784 this attack. Fixes bug 5185; implements proposal 193.
787 - Avoid logging uninitialized data when unable to decode a hidden
788 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
789 - Avoid a client-side assertion failure when receiving an INTRODUCE2
790 cell on a general purpose circuit. Fixes bug 5644; bugfix on
792 - Fix builds when the path to sed, openssl, or sha1sum contains
793 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
795 - Correct our replacements for the timeradd() and timersub() functions
796 on platforms that lack them (for example, Windows). The timersub()
797 function is used when expiring circuits, while timeradd() is
798 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
799 bugfix on 0.2.2.24-alpha.
800 - Fix the SOCKET_OK test that we use to tell when socket
801 creation fails so that it works on Win64. Fixes part of bug 4533;
802 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
805 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
806 Fixes bug 5346; bugfix on 0.0.8pre3.
807 - Make our number-parsing functions always treat too-large values
808 as an error, even when those values exceed the width of the
809 underlying type. Previously, if the caller provided these
810 functions with minima or maxima set to the extreme values of the
811 underlying integer type, these functions would return those
812 values on overflow rather than treating overflow as an error.
813 Fixes part of bug 5786; bugfix on 0.0.9.
814 - Older Linux kernels erroneously respond to strange nmap behavior
815 by having accept() return successfully with a zero-length
816 socket. When this happens, just close the connection. Previously,
817 we would try harder to learn the remote address: but there was
818 no such remote address to learn, and our method for trying to
819 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
820 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
821 - Correct parsing of certain date types in parse_http_time().
822 Without this patch, If-Modified-Since would behave
823 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
824 Esteban Manchado Velázques.
825 - Change the BridgePassword feature (part of the "bridge community"
826 design, which is not yet implemented) to use a time-independent
827 comparison. The old behavior might have allowed an adversary
828 to use timing to guess the BridgePassword value. Fixes bug 5543;
829 bugfix on 0.2.0.14-alpha.
830 - Detect and reject certain misformed escape sequences in
831 configuration values. Previously, these values would cause us
832 to crash if received in a torrc file or over an authenticated
833 control port. Bug found by Esteban Manchado Velázquez, and
834 independently by Robert Connolly from Matta Consulting who further
835 noted that it allows a post-authentication heap overflow. Patch
836 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
837 bugfix on 0.2.0.16-alpha.
838 - Fix a compile warning when using the --enable-openbsd-malloc
839 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
840 - During configure, detect when we're building with clang version
841 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
842 CFLAGS. clang doesn't support them yet.
843 - When sending an HTTP/1.1 proxy request, include a Host header.
844 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
845 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
846 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
847 - If we hit the error case where routerlist_insert() replaces an
848 existing (old) server descriptor, make sure to remove that
849 server descriptor from the old_routers list. Fix related to bug
850 1776. Bugfix on 0.2.2.18-alpha.
852 o Minor bugfixes (documentation and log messages):
853 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
854 Fixes bug 4856; bugfix on Tor 0.0.6.
855 - Update "ClientOnly" man page entry to explain that there isn't
856 really any point to messing with it. Resolves ticket 5005.
857 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
858 directory authority option (introduced in Tor 0.2.2.34).
859 - Downgrade the "We're missing a certificate" message from notice
860 to info: people kept mistaking it for a real problem, whereas it
861 is seldom the problem even when we are failing to bootstrap. Fixes
862 bug 5067; bugfix on 0.2.0.10-alpha.
863 - Correctly spell "connect" in a log message on failure to create a
864 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
865 - Clarify the behavior of MaxCircuitDirtiness with hidden service
866 circuits. Fixes issue 5259.
869 - Directory authorities now reject versions of Tor older than
870 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
871 inclusive. These versions accounted for only a small fraction of
872 the Tor network, and have numerous known security issues. Resolves
874 - Update to the May 1 2012 Maxmind GeoLite Country database.
877 - When sending or relaying a RELAY_EARLY cell, we used to convert
878 it to a RELAY cell if the connection was using the v1 link
879 protocol. This was a workaround for older versions of Tor, which
880 didn't handle RELAY_EARLY cells properly. Now that all supported
881 versions can handle RELAY_EARLY cells, and now that we're enforcing
882 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
883 remove this workaround. Addresses bug 4786.
886 Changes in version 0.2.3.15-alpha - 2012-04-30
887 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
888 the development branch build on Windows again.
890 o Minor bugfixes (on 0.2.2.x and earlier):
891 - Make sure that there are no unhandled pending TLS errors before
892 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
893 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
894 Bugfix on 0.1.0.5-rc; fixes bug 4528.
895 - Fix an assert that directory authorities could trigger on sighup
896 during some configuration state transitions. We now don't treat
897 it as a fatal error when the new descriptor we just generated in
898 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
899 - After we pick a directory mirror, we would refuse to use it if
900 it's in our ExcludeExitNodes list, resulting in mysterious failures
901 to bootstrap for people who just wanted to avoid exiting from
902 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
903 - When building with --enable-static-tor on OpenBSD, do not
904 erroneously attempt to link -lrt. Fixes bug 5103.
906 o Minor bugfixes (on 0.2.3.x):
907 - When Tor is built with kernel headers from a recent (last few
908 years) Linux kernel, do not fail to run on older (pre-2.6.28
909 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
910 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
912 - Fix compilation with miniupnpc version 1.6; patch from
913 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
914 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
915 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
916 - Fix compilation on platforms without unistd.h, or where environ
917 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
920 - Directory authorities are now a little more lenient at accepting
921 older router descriptors, or newer router descriptors that don't
922 make big changes. This should help ameliorate past and future
923 issues where routers think they have uploaded valid descriptors,
924 but the authorities don't think so. Fix for ticket 2479.
925 - Make the code that clients use to detect an address change be
926 IPv6-aware, so that it won't fill clients' logs with error
927 messages when trying to get the IPv4 address of an IPv6
928 connection. Implements ticket 5537.
931 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
932 authorities needed to use it for a while to keep the network working
933 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
934 that was six months ago. As of now, it should no longer be needed
938 Changes in version 0.2.3.14-alpha - 2012-04-23
939 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
940 candidate. It also dramatically speeds up AES: fast relays should
941 consider switching to the newer OpenSSL library.
943 o Directory authority changes:
944 - Change IP address for ides (v3 directory authority), and rename
948 - Avoid logging uninitialized data when unable to decode a hidden
949 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
950 - Avoid a client-side assertion failure when receiving an INTRODUCE2
951 cell on a general purpose circuit. Fixes bug 5644; bugfix on
953 - If authorities are unable to get a v2 consensus document from other
954 directory authorities, they no longer fall back to fetching
955 them from regular directory caches. Fixes bug 5635; bugfix on
956 0.2.2.26-beta, where routers stopped downloading v2 consensus
958 - When we start a Tor client with a normal consensus already cached,
959 be willing to download a microdescriptor consensus. Fixes bug 4011;
960 fix on 0.2.3.1-alpha.
962 o Major features (performance):
963 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
964 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
965 vectorized AES implementations as appropriate. These can be much,
966 much faster than other AES implementations.
968 o Minor bugfixes (0.2.2.x and earlier):
969 - Don't launch more than 10 service-side introduction-point circuits
970 for a hidden service in five minutes. Previously, we would consider
971 launching more introduction-point circuits if at least one second
972 had passed without any introduction-point circuits failing. Fixes
973 bug 4607; bugfix on 0.0.7pre1.
974 - Change the BridgePassword feature (part of the "bridge community"
975 design, which is not yet implemented) to use a time-independent
976 comparison. The old behavior might have allowed an adversary
977 to use timing to guess the BridgePassword value. Fixes bug 5543;
978 bugfix on 0.2.0.14-alpha.
979 - Enforce correct return behavior of tor_vsscanf() when the '%%'
980 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
981 - When sending an HTTP/1.1 proxy request, include a Host header.
982 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
983 - Don't log that we have "decided to publish new relay descriptor"
984 unless we are actually publishing a descriptor. Fixes bug 3942;
985 bugfix on 0.2.2.28-beta.
987 o Minor bugfixes (0.2.3.x):
988 - Fix a bug where a bridge authority crashes (on a failed assert)
989 if it has seen no directory requests when it's time to write
990 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
991 - Fix bug stomping on ORPort option NoListen and ignoring option
992 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
993 - In the testsuite, provide a large enough buffer in the tor_sscanf
994 unit test. Otherwise we'd overrun that buffer and crash during
995 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
997 - Make sure we create the keys directory if it doesn't exist and we're
998 about to store the dynamic Diffie-Hellman parameters. Fixes bug
999 5572; bugfix on 0.2.3.13-alpha.
1000 - Fix a small memory leak when trying to decode incorrect base16
1001 authenticator during SAFECOOKIE authentication. Found by
1002 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
1005 - Add more information to a log statement that might help track down
1006 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
1007 non-IP address" messages (or any Bug messages, for that matter!),
1008 please let us know about it.
1009 - Relays now understand an IPv6 address when they get one from a
1010 directory server. Resolves ticket 4875.
1011 - Resolve IPv6 addresses in bridge and entry statistics to country
1012 code "??" which means we at least count them. Resolves ticket 5053;
1013 improves on 0.2.3.9-alpha.
1014 - Update to the April 3 2012 Maxmind GeoLite Country database.
1015 - Begin a doc/state-contents.txt file to explain the contents of
1016 the Tor state file. Fixes bug 2987.
1018 o Default torrc changes:
1019 - Stop listing "socksport 9050" in torrc.sample. We open a socks
1020 port on 9050 by default anyway, so this should not change anything
1022 - Stop mentioning the deprecated *ListenAddress options in
1023 torrc.sample. Fixes bug 5438.
1024 - Document unit of bandwidth related options in sample torrc.
1028 - The "torify" script no longer supports the "tsocks" socksifier
1029 tool, since tsocks doesn't support DNS and UDP right for Tor.
1030 Everyone should be using torsocks instead. Fixes bugs 3530 and
1031 5180. Based on a patch by "ugh".
1034 - Change the symmetric cipher interface so that creating and
1035 initializing a stream cipher are no longer separate functions.
1036 - Remove all internal support for unpadded RSA. We never used it, and
1037 it would be a bad idea to start.
1040 Changes in version 0.2.3.13-alpha - 2012-03-26
1041 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
1042 in managed pluggable transports, as well as providing other cleanups
1043 that get us closer to a release candidate.
1045 o Directory authority changes:
1046 - Change IP address for maatuska (v3 directory authority).
1049 - Provide controllers with a safer way to implement the cookie
1050 authentication mechanism. With the old method, if another locally
1051 running program could convince a controller that it was the Tor
1052 process, then that program could trick the controller into telling
1053 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
1054 authentication method uses a challenge-response approach to prevent
1055 this attack. Fixes bug 5185, implements proposal 193.
1056 - Never use a bridge or a controller-supplied node as an exit, even
1057 if its exit policy allows it. Found by wanoskarnet. Fixes bug
1058 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
1059 and 0.2.0.3-alpha (for bridge-purpose descriptors).
1060 - Only build circuits if we have a sufficient threshold of the total
1061 descriptors that are marked in the consensus with the "Exit"
1062 flag. This mitigates an attack proposed by wanoskarnet, in which
1063 all of a client's bridges collude to restrict the exit nodes that
1064 the client knows about. Fixes bug 5343.
1066 o Major bugfixes (on Tor 0.2.3.x):
1067 - Avoid an assert when managed proxies like obfsproxy are configured,
1068 and we receive HUP signals or setconf attempts too rapidly. This
1069 situation happens most commonly when Vidalia tries to attach to
1070 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
1071 bugfix on 0.2.3.6-alpha.
1072 - Fix a relay-side pluggable transports bug where managed proxies were
1073 unreachable from the Internet, because Tor asked them to bind on
1074 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
1075 - Stop discarding command-line arguments when TestingTorNetwork
1076 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
1077 0.2.3.9-alpha, where task 4552 added support for two layers of
1079 - Resume allowing the unit tests to run in gdb. This was accidentally
1080 made impossible when the DisableDebuggerAttachment option was
1081 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
1082 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
1083 0.2.3.11-alpha. Reported by Anthony G. Basile.
1085 o Minor bugfixes (on 0.2.2.x and earlier):
1086 - Ensure we don't cannibalize circuits that are longer than three hops
1087 already, so we don't end up making circuits with 5 or more
1088 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
1089 0.1.0.1-rc which introduced cannibalization.
1090 - Detect and reject certain misformed escape sequences in
1091 configuration values. Previously, these values would cause us
1092 to crash if received in a torrc file or over an authenticated
1093 control port. Bug found by Esteban Manchado Velázquez, and
1094 independently by Robert Connolly from Matta Consulting who further
1095 noted that it allows a post-authentication heap overflow. Patch
1096 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
1097 bugfix on 0.2.0.16-alpha.
1098 - Fix a compile warning when using the --enable-openbsd-malloc
1099 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
1100 - Directory caches no longer refuse to clean out descriptors because
1101 of missing v2 networkstatus documents, unless they're configured
1102 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
1103 0.2.2.26-beta. Patch by Daniel Bryg.
1104 - Update to the latest version of the tinytest unit testing framework.
1105 This includes a couple of bugfixes that can be relevant for
1106 running forked unit tests on Windows, and removes all reserved
1109 o Minor bugfixes (on 0.2.3.x):
1110 - On a failed pipe() call, don't leak file descriptors. Fixes bug
1111 4296; bugfix on 0.2.3.1-alpha.
1112 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
1113 until after we have received a CERTS cell. Fixes bug 4361; bugfix
1114 on 0.2.3.6-alpha. Patch by "frosty".
1115 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
1116 option, so that the IP stack doesn't decide to use it for IPv4
1117 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
1118 - Ensure that variables set in Tor's environment cannot override
1119 environment variables that Tor passes to a managed
1120 pluggable-transport proxy. Previously, Tor would pass every
1121 variable in its environment to managed proxies along with the new
1122 ones, in such a way that on many operating systems, the inherited
1123 environment variables would override those which Tor tried to
1124 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
1125 bugfix on 0.2.3.9-alpha for Windows.
1128 - A wide variety of new unit tests by Esteban Manchado Velázquez.
1129 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
1130 - Update to the March 6 2012 Maxmind GeoLite Country database.
1133 Changes in version 0.2.3.12-alpha - 2012-02-13
1134 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
1135 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
1136 when Tor is configured to use a pluggable transport like obfsproxy.
1139 - Fix builds when the path to sed, openssl, or sha1sum contains
1140 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
1142 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
1143 connections. This change should allow busy exit relays to stop
1144 running out of available sockets as quickly. Fixes bug 4950;
1145 bugfix on 0.2.2.26-beta.
1146 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
1147 would ask the bridge for microdescriptors, which are only supported
1148 in 0.2.3.x, and then fail to bootstrap when it didn't get the
1149 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
1150 - Properly set up obfsproxy's environment when in managed mode. The
1151 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
1152 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
1153 5076 and 5082; bugfix on 0.2.3.6-alpha.
1156 - Use the dead_strip option when building Tor on OS X. This reduces
1157 binary size by almost 19% when linking openssl and libevent
1158 statically, which we do for Tor Browser Bundle.
1159 - Fix broken URLs in the sample torrc file, and tell readers about
1160 the OutboundBindAddress, ExitPolicyRejectPrivate, and
1161 PublishServerDescriptor options. Addresses bug 4652.
1162 - Update to the February 7 2012 Maxmind GeoLite Country database.
1165 - Downgrade the "We're missing a certificate" message from notice
1166 to info: people kept mistaking it for a real problem, whereas it
1167 is seldom the problem even when we are failing to bootstrap. Fixes
1168 bug 5067; bugfix on 0.2.0.10-alpha.
1169 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
1170 managed pluggable transport server proxy's environment.
1171 Previously, we would put it there, even though Tor doesn't
1172 implement an 'extended server port' yet, and even though Tor
1173 almost certainly isn't listening at that address. For now, we set
1174 it to an empty string to avoid crashing older obfsproxies. Bugfix
1176 - Log the heartbeat message every HeartbeatPeriod seconds, not every
1177 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
1178 0.2.3.1-alpha. Bug reported by Scott Bennett.
1179 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
1180 bugfix on 0.2.3.11-alpha.
1181 - Update "ClientOnly" man page entry to explain that there isn't
1182 really any point to messing with it. Resolves ticket 5005.
1183 - Use the correct CVE number for CVE-2011-4576 in our comments and
1184 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
1187 o Code simplifications and refactoring:
1188 - Use the _WIN32 macro throughout our code to detect Windows.
1189 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
1193 Changes in version 0.2.3.11-alpha - 2012-01-22
1194 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
1195 the last step of the plan to limit maximum circuit length, includes
1196 a wide variety of hidden service performance and correctness fixes,
1197 works around an OpenSSL security flaw if your distro is too stubborn
1198 to upgrade, and fixes a bunch of smaller issues.
1201 - Now that Tor 0.2.0.x is completely deprecated, enable the final
1202 part of "Proposal 110: Avoiding infinite length circuits" by
1203 refusing all circuit-extend requests that do not use a relay_early
1204 cell. This change helps Tor resist a class of denial-of-service
1205 attacks by limiting the maximum circuit length.
1206 - Adjust the number of introduction points that a hidden service
1207 will try to maintain based on how long its introduction points
1208 remain in use and how many introductions they handle. Fixes
1210 - Try to use system facilities for enumerating local interface
1211 addresses, before falling back to our old approach (which was
1212 binding a UDP socket, and calling getsockname() on it). That
1213 approach was scaring OS X users whose draconian firewall
1214 software warned about binding to UDP sockets, regardless of
1215 whether packets were sent. Now we try to use getifaddrs(),
1216 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
1217 system supports. Resolves ticket 1827.
1219 o Major security workaround:
1220 - When building or running with any version of OpenSSL earlier
1221 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
1222 versions have a bug (CVE-2011-4576) in which their block cipher
1223 padding includes uninitialized data, potentially leaking sensitive
1224 information to any peer with whom they make a SSLv3 connection. Tor
1225 does not use SSL v3 by default, but a hostile client or server
1226 could force an SSLv3 connection in order to gain information that
1227 they shouldn't have been able to get. The best solution here is to
1228 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
1229 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
1230 to make sure that the bug can't happen.
1233 - Fix the SOCKET_OK test that we use to tell when socket
1234 creation fails so that it works on Win64. Fixes part of bug 4533;
1235 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
1236 - Correct our replacements for the timeradd() and timersub() functions
1237 on platforms that lack them (for example, Windows). The timersub()
1238 function is used when expiring circuits, while timeradd() is
1239 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
1240 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
1241 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
1242 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
1243 bug at runtime, not compile time, because some distributions hack
1244 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
1245 on 0.2.3.9-alpha. Found by Pascal.
1247 o Minor features (controller):
1248 - Use absolute path names when reporting the torrc filename in the
1249 control protocol, so a controller can more easily find the torrc
1250 file. Resolves bug 1101.
1251 - Extend the control protocol to report flags that control a circuit's
1252 path selection in CIRC events and in replies to 'GETINFO
1253 circuit-status'. Implements part of ticket 2411.
1254 - Extend the control protocol to report the hidden service address
1255 and current state of a hidden-service-related circuit in CIRC
1256 events and in replies to 'GETINFO circuit-status'. Implements part
1258 - When reporting the path to the cookie file to the controller,
1259 give an absolute path. Resolves ticket 4881.
1260 - Allow controllers to request an event notification whenever a
1261 circuit is cannibalized or its purpose is changed. Implements
1262 part of ticket 3457.
1263 - Include the creation time of a circuit in CIRC and CIRC2
1264 control-port events and the list produced by the 'GETINFO
1265 circuit-status' control-port command.
1267 o Minor features (directory authorities):
1268 - Directory authorities now reject versions of Tor older than
1269 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
1270 inclusive. These versions accounted for only a small fraction of
1271 the Tor network, and have numerous known security issues. Resolves
1273 - Authority operators can now vote for all relays in a given
1274 set of countries to be BadDir/BadExit/Invalid/Rejected.
1275 - Provide two consensus parameters (FastFlagMinThreshold and
1276 FastFlagMaxThreshold) to control the range of allowable bandwidths
1277 for the Fast directory flag. These allow authorities to run
1278 experiments on appropriate requirements for being a "Fast" node.
1279 The AuthDirFastGuarantee config value still applies.
1280 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
1281 directory authority option (introduced in Tor 0.2.2.34).
1283 o Minor features (other):
1284 - Don't disable the DirPort when we cannot exceed our AccountingMax
1285 limit during this interval because the effective bandwidthrate is
1286 low enough. This is useful in a situation where AccountMax is only
1287 used as an additional safeguard or to provide statistics.
1288 - Prepend an informative header to generated dynamic_dh_params files.
1289 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
1290 EntryNodes will have no effect. Resolves issue 2571.
1291 - Log more useful messages when we fail to disable debugger
1293 - Log which authority we're missing votes from when we go to fetch
1294 them from the other auths.
1295 - Log (at debug level) whenever a circuit's purpose is changed.
1296 - Add missing documentation for the MaxClientCircuitsPending,
1297 UseMicrodescriptors, UserspaceIOCPBuffers, and
1298 _UseFilteringSSLBufferevents options, all introduced during
1300 - Update to the January 3 2012 Maxmind GeoLite Country database.
1302 o Minor bugfixes (hidden services):
1303 - Don't close hidden service client circuits which have almost
1304 finished connecting to their destination when they reach
1305 the normal circuit-build timeout. Previously, we would close
1306 introduction circuits which are waiting for an acknowledgement
1307 from the introduction point, and rendezvous circuits which have
1308 been specified in an INTRODUCE1 cell sent to a hidden service,
1309 after the normal CBT. Now, we mark them as 'timed out', and launch
1310 another rendezvous attempt in parallel. This behavior change can
1311 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
1312 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
1313 - Don't close hidden-service-side rendezvous circuits when they
1314 reach the normal circuit-build timeout. This behaviour change can
1315 be disabled using the new
1316 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
1317 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
1318 - Make sure we never mark the wrong rendezvous circuit as having
1319 had its introduction cell acknowleged by the introduction-point
1320 relay. Previously, when we received an INTRODUCE_ACK cell on a
1321 client-side hidden-service introduction circuit, we might have
1322 marked a rendezvous circuit other than the one we specified in
1323 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
1324 a warning message and interfered with the hidden service
1325 connection-establishment process. Fixes bug 4759; bugfix on
1326 0.2.3.3-alpha, when we added the stream-isolation feature which
1327 might cause Tor to open multiple rendezvous circuits for the same
1329 - Don't trigger an assertion failure when we mark a new client-side
1330 hidden-service introduction circuit for close during the process
1331 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
1334 o Minor bugfixes (log messages):
1335 - Correctly spell "connect" in a log message on failure to create a
1336 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
1338 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
1339 Fixes bug 4856; bugfix on Tor 0.0.6.
1340 - Fix the log message describing how we work around discovering
1341 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
1342 4837; bugfix on 0.2.2.9-alpha.
1343 - When logging about a disallowed .exit name, do not also call it
1344 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
1346 o Minor bugfixes (build fixes):
1347 - During configure, detect when we're building with clang version
1348 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
1349 CFLAGS. clang doesn't support them yet.
1350 - During configure, search for library containing cos function as
1351 libm lives in libcore on some platforms (BeOS/Haiku). Linking
1352 against libm was hard-coded before. Fixes the first part of bug
1353 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
1355 - Detect attempts to build Tor on (as yet hypothetical) versions
1356 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
1357 fix for bug 4533. Bugfix on 0.2.2.28-beta.
1358 - Preprocessor directives should not be put inside the arguments
1359 of a macro. This would break compilation with GCC releases prior
1360 to version 3.3. We would never recommend such an old GCC version,
1361 but it is apparently required for binary compatibility on some
1362 platforms (namely, certain builds of Haiku). Fixes the other part
1363 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
1366 o Minor bugfixes (other):
1367 - Older Linux kernels erroneously respond to strange nmap behavior
1368 by having accept() return successfully with a zero-length
1369 socket. When this happens, just close the connection. Previously,
1370 we would try harder to learn the remote address: but there was
1371 no such remote address to learn, and our method for trying to
1372 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
1373 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
1374 - Fix null-pointer access that could occur if TLS allocation failed.
1375 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
1376 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
1377 accidentally been reverted.
1378 - Fix our implementation of crypto_random_hostname() so it can't
1379 overflow on ridiculously large inputs. (No Tor version has ever
1380 provided this kind of bad inputs, but let's be correct in depth.)
1381 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
1382 - Find more places in the code that should have been testing for
1383 invalid sockets using the SOCKET_OK macro. Required for a fix
1384 for bug 4533. Bugfix on 0.2.2.28-beta.
1385 - Fix an assertion failure when, while running with bufferevents, a
1386 connection finishes connecting after it is marked for close, but
1387 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
1388 - test_util_spawn_background_ok() hardcoded the expected value
1389 for ENOENT to 2. This isn't portable as error numbers are
1390 platform specific, and particularly the hurd has ENOENT at
1391 0x40000002. Construct expected string at runtime, using the correct
1392 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
1393 - Reject attempts to disable DisableDebuggerAttachment while Tor is
1394 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
1395 - Use an appropriate-width type for sockets in tor-fw-helper on
1396 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
1399 - When sending or relaying a RELAY_EARLY cell, we used to convert
1400 it to a RELAY cell if the connection was using the v1 link
1401 protocol. This was a workaround for older versions of Tor, which
1402 didn't handle RELAY_EARLY cells properly. Now that all supported
1403 versions can handle RELAY_EARLY cells, and now that we're enforcing
1404 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
1405 remove this workaround. Addresses bug 4786.
1407 o Code simplifications and refactoring:
1408 - Use OpenSSL's built-in SSL_state_string_long() instead of our
1409 own homebrewed ssl_state_to_string() replacement. Patch from
1410 Emile Snyder. Fixes bug 4653.
1411 - Use macros to indicate OpenSSL versions, so we don't need to worry
1412 about accidental hexadecimal bit shifts.
1413 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
1415 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
1416 - Use the smartlist_add_asprintf() alias more consistently.
1417 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
1418 invalid value, rather than just -1.
1419 - Rename a handful of old identifiers, mostly related to crypto
1420 structures and crypto functions. By convention, our "create an
1421 object" functions are called "type_new()", our "free an object"
1422 functions are called "type_free()", and our types indicate that
1423 they are types only with a final "_t". But a handful of older
1424 types and functions broke these rules, with function names like
1425 "type_create" or "subsystem_op_type", or with type names like
1429 Changes in version 0.2.3.10-alpha - 2011-12-16
1430 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
1431 Tor's buffers code. Absolutely everybody should upgrade.
1433 The bug relied on an incorrect calculation when making data continuous
1434 in one of our IO buffers, if the first chunk of the buffer was
1435 misaligned by just the wrong amount. The miscalculation would allow an
1436 attacker to overflow a piece of heap-allocated memory. To mount this
1437 attack, the attacker would need to either open a SOCKS connection to
1438 Tor's SocksPort (usually restricted to localhost), or target a Tor
1439 instance configured to make its connections through a SOCKS proxy
1440 (which Tor does not do by default).
1442 Good security practice requires that all heap-overflow bugs should be
1443 presumed to be exploitable until proven otherwise, so we are treating
1444 this as a potential code execution attack. Please upgrade immediately!
1445 This bug does not affect bufferevents-based builds of Tor. Special
1446 thanks to "Vektor" for reporting this issue to us!
1448 This release also contains a few minor bugfixes for issues discovered
1452 - Fix a heap overflow bug that could occur when trying to pull
1453 data into the first chunk of a buffer, when that chunk had
1454 already had some data drained from it. Fixes CVE-2011-2778;
1455 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1458 - If we can't attach streams to a rendezvous circuit when we
1459 finish connecting to a hidden service, clear the rendezvous
1460 circuit's stream-isolation state and try to attach streams
1461 again. Previously, we cleared rendezvous circuits' isolation
1462 state either too early (if they were freshly built) or not at all
1463 (if they had been built earlier and were cannibalized). Bugfix on
1464 0.2.3.3-alpha; fixes bug 4655.
1465 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
1466 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
1467 - Fix an assertion failure when a relay with accounting enabled
1468 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
1471 - Update to the December 6 2011 Maxmind GeoLite Country database.
1474 Changes in version 0.2.2.35 - 2011-12-16
1475 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
1476 buffers code. Absolutely everybody should upgrade.
1478 The bug relied on an incorrect calculation when making data continuous
1479 in one of our IO buffers, if the first chunk of the buffer was
1480 misaligned by just the wrong amount. The miscalculation would allow an
1481 attacker to overflow a piece of heap-allocated memory. To mount this
1482 attack, the attacker would need to either open a SOCKS connection to
1483 Tor's SocksPort (usually restricted to localhost), or target a Tor
1484 instance configured to make its connections through a SOCKS proxy
1485 (which Tor does not do by default).
1487 Good security practice requires that all heap-overflow bugs should be
1488 presumed to be exploitable until proven otherwise, so we are treating
1489 this as a potential code execution attack. Please upgrade immediately!
1490 This bug does not affect bufferevents-based builds of Tor. Special
1491 thanks to "Vektor" for reporting this issue to us!
1493 Tor 0.2.2.35 also fixes several bugs in previous versions, including
1494 crash bugs for unusual configurations, and a long-term bug that
1495 would prevent Tor from starting on Windows machines with draconian
1498 With this release, we remind everyone that 0.2.0.x has reached its
1499 formal end-of-life. Those Tor versions have many known flaws, and
1500 nobody should be using them. You should upgrade -- ideally to the
1501 0.2.2.x series. If you're using a Linux or BSD and its packages are
1502 obsolete, stop using those packages and upgrade anyway.
1504 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
1505 longer receive support after some time in early 2012.
1508 - Fix a heap overflow bug that could occur when trying to pull
1509 data into the first chunk of a buffer, when that chunk had
1510 already had some data drained from it. Fixes CVE-2011-2778;
1511 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1512 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1513 that it doesn't attempt to allocate a socketpair. This could cause
1514 some problems on Windows systems with overzealous firewalls. Fix for
1515 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1517 - If we mark an OR connection for close based on a cell we process,
1518 don't process any further cells on it. We already avoid further
1519 reads on marked-for-close connections, but now we also discard the
1520 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1521 which was the first version where we might mark a connection for
1522 close based on processing a cell on it.
1523 - Correctly sanity-check that we don't underflow on a memory
1524 allocation (and then assert) for hidden service introduction
1525 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1526 bugfix on 0.2.1.5-alpha.
1527 - Fix a memory leak when we check whether a hidden service
1528 descriptor has any usable introduction points left. Fixes bug
1529 4424. Bugfix on 0.2.2.25-alpha.
1530 - Don't crash when we're running as a relay and don't have a GeoIP
1531 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
1532 we've had in the 0.2.3.x branch already.
1533 - When running as a client, do not print a misleading (and plain
1534 wrong) log message that we're collecting "directory request"
1535 statistics: clients don't collect statistics. Also don't create a
1536 useless (because empty) stats file in the stats/ directory. Fixes
1537 bug 4353; bugfix on 0.2.2.34.
1540 - Detect failure to initialize Libevent. This fix provides better
1541 detection for future instances of bug 4457.
1542 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1543 function. This was eating up hideously large amounts of time on some
1544 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1545 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1546 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1548 - Don't warn about unused log_mutex in log.c when building with
1549 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1550 0.1.0.6-rc which introduced --disable-threads.
1551 - When configuring, starting, or stopping an NT service, stop
1552 immediately after the service configuration attempt has succeeded
1553 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1554 - When sending a NETINFO cell, include the original address
1555 received for the other side, not its canonical address. Found
1556 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1557 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
1558 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1559 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1560 occurred when a client tried to fetch a descriptor for a bridge
1561 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1562 - Backport fixes for a pair of compilation warnings on Windows.
1563 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
1564 - If we had ever tried to call tor_addr_to_str on an address of
1565 unknown type, we would have done a strdup on an uninitialized
1566 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1567 Reported by "troll_un".
1568 - Correctly detect and handle transient lookup failures from
1569 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1570 Reported by "troll_un".
1571 - Fix null-pointer access that could occur if TLS allocation failed.
1572 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1573 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1574 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1577 - Add two new config options for directory authorities:
1578 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
1579 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
1580 that is always sufficient to satisfy the bandwidth requirement for
1581 the Guard flag. Now it will be easier for researchers to simulate
1582 Tor networks with different values. Resolves ticket 4484.
1583 - When Tor ignores a hidden service specified in its configuration,
1584 include the hidden service's directory in the warning message.
1585 Previously, we would only tell the user that some hidden service
1586 was ignored. Bugfix on 0.0.6; fixes bug 4426.
1587 - Update to the December 6 2011 Maxmind GeoLite Country database.
1589 o Packaging changes:
1590 - Make it easier to automate expert package builds on Windows,
1591 by removing an absolute path from makensis.exe command.
1594 Changes in version 0.2.3.9-alpha - 2011-12-08
1595 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
1596 a "DisableNetwork" security feature that bundles can use to avoid
1597 touching the network until bridges are configured, moves forward on
1598 the pluggable transport design, fixes a flaw in the hidden service
1599 design that unnecessarily prevented clients with wrong clocks from
1600 reaching hidden services, and fixes a wide variety of other issues.
1603 - Clients can now connect to private bridges over IPv6. Bridges
1604 still need at least one IPv4 address in order to connect to
1605 other relays. Note that we don't yet handle the case where the
1606 user has two bridge lines for the same bridge (one IPv4, one
1607 IPv6). Implements parts of proposal 186.
1608 - New "DisableNetwork" config option to prevent Tor from launching any
1609 connections or accepting any connections except on a control port.
1610 Bundles and controllers can set this option before letting Tor talk
1611 to the rest of the network, for example to prevent any connections
1612 to a non-bridge address. Packages like Orbot can also use this
1613 option to instruct Tor to save power when the network is off.
1614 - Clients and bridges can now be configured to use a separate
1615 "transport" proxy. This approach makes the censorship arms race
1616 easier by allowing bridges to use protocol obfuscation plugins. It
1617 implements the "managed proxy" part of proposal 180 (ticket 3472).
1618 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
1619 implementation. It makes AES_CTR about 7% faster than our old one
1620 (which was about 10% faster than the one OpenSSL used to provide).
1621 Resolves ticket 4526.
1622 - Add a "tor2web mode" for clients that want to connect to hidden
1623 services non-anonymously (and possibly more quickly). As a safety
1624 measure to try to keep users from turning this on without knowing
1625 what they are doing, tor2web mode must be explicitly enabled at
1626 compile time, and a copy of Tor compiled to run in tor2web mode
1627 cannot be used as a normal Tor client. Implements feature 2553.
1628 - Add experimental support for running on Windows with IOCP and no
1629 kernel-space socket buffers. This feature is controlled by a new
1630 "UserspaceIOCPBuffers" config option (off by default), which has
1631 no effect unless Tor has been built with support for bufferevents,
1632 is running on Windows, and has enabled IOCP. This may, in the long
1633 run, help solve or mitigate bug 98.
1634 - Use a more secure consensus parameter voting algorithm. Now at
1635 least three directory authorities or a majority of them must
1636 vote on a given parameter before it will be included in the
1637 consensus. Implements proposal 178.
1640 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
1641 They used to check that the timestamp was within 30 minutes
1642 of their system clock, so they could cap the size of their
1643 replay-detection cache, but that approach unnecessarily refused
1644 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
1645 the v3 intro-point protocol (the first one which sent a timestamp
1646 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
1647 - Only use the EVP interface when AES acceleration is enabled,
1648 to avoid a 5-7% performance regression. Resolves issue 4525;
1649 bugfix on 0.2.3.8-alpha.
1651 o Privacy/anonymity features (bridge detection):
1652 - Make bridge SSL certificates a bit more stealthy by using random
1653 serial numbers, in the same fashion as OpenSSL when generating
1654 self-signed certificates. Implements ticket 4584.
1655 - Introduce a new config option "DynamicDHGroups", enabled by
1656 default, which provides each bridge with a unique prime DH modulus
1657 to be used during SSL handshakes. This option attempts to help
1658 against censors who might use the Apache DH modulus as a static
1659 identifier for bridges. Addresses ticket 4548.
1661 o Minor features (new/different config options):
1662 - New configuration option "DisableDebuggerAttachment" (on by default)
1663 to prevent basic debugging attachment attempts by other processes.
1664 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
1665 - Allow MapAddress directives to specify matches against super-domains,
1666 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
1667 Implements issue 933.
1668 - Slightly change behavior of "list" options (that is, config
1669 options that can appear more than once) when they appear both in
1670 torrc and on the command line. Previously, the command-line options
1671 would be appended to the ones from torrc. Now, the command-line
1672 options override the torrc options entirely. This new behavior
1673 allows the user to override list options (like exit policies and
1674 ports to listen on) from the command line, rather than simply
1675 appending to the list.
1676 - You can get the old (appending) command-line behavior for "list"
1677 options by prefixing the option name with a "+".
1678 - You can remove all the values for a "list" option from the command
1679 line without adding any new ones by prefixing the option name
1681 - Add experimental support for a "defaults" torrc file to be parsed
1682 before the regular torrc. Torrc options override the defaults file's
1683 options in the same way that the command line overrides the torrc.
1684 The SAVECONF controller command saves only those options which
1685 differ between the current configuration and the defaults file. HUP
1686 reloads both files. (Note: This is an experimental feature; its
1687 behavior will probably be refined in future 0.2.3.x-alpha versions
1688 to better meet packagers' needs.) Implements task 4552.
1691 - Try to make the introductory warning message that Tor prints on
1692 startup more useful for actually finding help and information.
1693 Resolves ticket 2474.
1694 - Running "make version" now displays the version of Tor that
1695 we're about to build. Idea from katmagic; resolves issue 4400.
1696 - Expire old or over-used hidden service introduction points.
1697 Required by fix for bug 3460.
1698 - Move the replay-detection cache for the RSA-encrypted parts of
1699 INTRODUCE2 cells to the introduction point data structures.
1700 Previously, we would use one replay-detection cache per hidden
1701 service. Required by fix for bug 3460.
1702 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
1703 public key replay-detection cache from 60 minutes to 5 minutes. This
1704 replay-detection cache is now used only to detect multiple
1705 INTRODUCE2 cells specifying the same rendezvous point, so we can
1706 avoid launching multiple simultaneous attempts to connect to it.
1708 o Minor bugfixes (on Tor 0.2.2.x and earlier):
1709 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1710 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1712 - Fix a minor formatting issue in one of tor-gencert's error messages.
1714 - Prevent a false positive from the check-spaces script, by disabling
1715 the "whitespace between function name and (" check for functions
1717 - Fix a log message suggesting that people contact a non-existent
1718 email address. Fixes bug 3448.
1719 - Fix null-pointer access that could occur if TLS allocation failed.
1720 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1721 - Report a real bootstrap problem to the controller on router
1722 identity mismatch. Previously we just said "foo", which probably
1723 made a lot of sense at the time. Fixes bug 4169; bugfix on
1725 - If we had ever tried to call tor_addr_to_str() on an address of
1726 unknown type, we would have done a strdup() on an uninitialized
1727 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1728 Reported by "troll_un".
1729 - Correctly detect and handle transient lookup failures from
1730 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1731 Reported by "troll_un".
1732 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1733 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1734 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
1735 bug 4532; found by "troll_un".
1737 o Minor bugfixes (on Tor 0.2.3.x):
1738 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
1740 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
1741 circuit for use as a hidden service client's rendezvous point.
1742 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
1743 with help from wanoskarnet.
1744 - Restore behavior of overriding SocksPort, ORPort, and similar
1745 options from the command line. Bugfix on 0.2.3.3-alpha.
1748 - Properly handle the case where the build-tree is not the same
1749 as the source tree when generating src/common/common_sha1.i,
1750 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
1751 bugfix on 0.2.0.1-alpha.
1753 o Code simplifications, cleanups, and refactorings:
1754 - Remove the pure attribute from all functions that used it
1755 previously. In many cases we assigned it incorrectly, because the
1756 functions might assert or call impure functions, and we don't have
1757 evidence that keeping the pure attribute is worthwhile. Implements
1758 changes suggested in ticket 4421.
1759 - Remove some dead code spotted by coverity. Fixes cid 432.
1760 Bugfix on 0.2.3.1-alpha, closes bug 4637.
1763 Changes in version 0.2.3.8-alpha - 2011-11-22
1764 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
1765 socketpair-related bug that has been bothering Windows users. It adds
1766 support to serve microdescriptors to controllers, so Vidalia's network
1767 map can resume listing relays (once Vidalia implements its side),
1768 and adds better support for hardware AES acceleration. Finally, it
1769 starts the process of adjusting the bandwidth cutoff for getting the
1770 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
1771 that tiny relays harm performance more than they help network capacity.
1774 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1775 that it doesn't attempt to allocate a socketpair. This could cause
1776 some problems on Windows systems with overzealous firewalls. Fix for
1777 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1779 - Correctly sanity-check that we don't underflow on a memory
1780 allocation (and then assert) for hidden service introduction
1781 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1782 bugfix on 0.2.1.5-alpha.
1783 - Remove the artificially low cutoff of 20KB to guarantee the Fast
1784 flag. In the past few years the average relay speed has picked
1785 up, and while the "top 7/8 of the network get the Fast flag" and
1786 "all relays with 20KB or more of capacity get the Fast flag" rules
1787 used to have the same result, now the top 7/8 of the network has
1788 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
1789 - Fix a rare assertion failure when checking whether a v0 hidden
1790 service descriptor has any usable introduction points left, and
1791 we don't have enough information to build a circuit to the first
1792 intro point named in the descriptor. The HS client code in
1793 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
1794 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
1795 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
1796 - Make bridge authorities not crash when they are asked for their own
1797 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
1798 - When running as a client, do not print a misleading (and plain
1799 wrong) log message that we're collecting "directory request"
1800 statistics: clients don't collect statistics. Also don't create a
1801 useless (because empty) stats file in the stats/ directory. Fixes
1802 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
1805 - Allow Tor controllers like Vidalia to obtain the microdescriptor
1806 for a relay by identity digest or nickname. Previously,
1807 microdescriptors were only available by their own digests, so a
1808 controller would have to ask for and parse the whole microdescriptor
1809 consensus in order to look up a single relay's microdesc. Fixes
1810 bug 3832; bugfix on 0.2.3.1-alpha.
1811 - Use OpenSSL's EVP interface for AES encryption, so that all AES
1812 operations can use hardware acceleration (if present). Resolves
1815 o Minor bugfixes (on 0.2.2.x and earlier):
1816 - Detect failure to initialize Libevent. This fix provides better
1817 detection for future instances of bug 4457.
1818 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1819 function. This was eating up hideously large amounts of time on some
1820 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1821 - Don't warn about unused log_mutex in log.c when building with
1822 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1823 0.1.0.6-rc which introduced --disable-threads.
1824 - Allow manual 'authenticate' commands to the controller interface
1825 from netcat (nc) as well as telnet. We were rejecting them because
1826 they didn't come with the expected whitespace at the end of the
1827 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
1828 - Fix some (not actually triggerable) buffer size checks in usage of
1829 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
1831 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
1832 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
1833 - When configuring, starting, or stopping an NT service, stop
1834 immediately after the service configuration attempt has succeeded
1835 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1836 - When sending a NETINFO cell, include the original address
1837 received for the other side, not its canonical address. Found
1838 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1839 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
1840 can pick them up when the tests aren't disabled. Bugfix on
1841 0.2.2.4-alpha which introduced tinytest.
1842 - Fix a memory leak when we check whether a hidden service
1843 descriptor has any usable introduction points left. Fixes bug
1844 4424. Bugfix on 0.2.2.25-alpha.
1845 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1846 occurred when a client tried to fetch a descriptor for a bridge
1847 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1849 o Minor bugfixes (on 0.2.3.x):
1850 - Make util unit tests build correctly with MSVC. Bugfix on
1851 0.2.3.3-alpha. Patch by Gisle Vanem.
1852 - Successfully detect AUTH_CHALLENGE cells with no recognized
1853 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
1855 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
1856 it should still send a NETINFO cell to allow the connection to
1857 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
1859 - Log less loudly when we get an invalid authentication certificate
1860 from a source other than a directory authority: it's not unusual
1861 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
1863 - Tolerate servers with more clock skew in their authentication
1864 certificates than previously. Fixes bug 4371; bugfix on
1866 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
1867 on 0.2.3.4-alpha and 0.2.3.6-alpha.
1870 - Add two new config options for directory authorities:
1871 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
1872 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
1873 that is always sufficient to satisfy the bandwidth requirement for
1874 the Guard flag. Now it will be easier for researchers to simulate
1875 Tor networks with different values. Resolves ticket 4484.
1876 - When Tor ignores a hidden service specified in its configuration,
1877 include the hidden service's directory in the warning message.
1878 Previously, we would only tell the user that some hidden service
1879 was ignored. Bugfix on 0.0.6; fixes bug 4426.
1880 - When we fail to initialize Libevent, retry with IOCP disabled so we
1881 don't need to turn on multi-threading support in Libevent, which in
1882 turn requires a working socketpair(). This is a workaround for bug
1883 4457, which affects Libevent versions from 2.0.1-alpha through
1885 - Detect when we try to build on a platform that doesn't define
1886 AF_UNSPEC to 0. We don't work there, so refuse to compile.
1887 - Update to the November 1 2011 Maxmind GeoLite Country database.
1889 o Packaging changes:
1890 - Make it easier to automate expert package builds on Windows,
1891 by removing an absolute path from makensis.exe command.
1893 o Code simplifications and refactoring:
1894 - Remove some redundant #include directives throughout the code.
1895 Patch from Andrea Gelmini.
1896 - Unconditionally use OpenSSL's AES implementation instead of our
1897 old built-in one. OpenSSL's AES has been better for a while, and
1898 relatively few servers should still be on any version of OpenSSL
1899 that doesn't have good optimized assembly AES.
1900 - Use the name "CERTS" consistently to refer to the new cell type;
1901 we were calling it CERT in some places and CERTS in others.
1904 - Numerous new unit tests for functions in util.c and address.c by
1906 - The long-disabled benchmark tests are now split into their own
1907 ./src/test/bench binary.
1908 - The benchmark tests can now use more accurate timers than
1909 gettimeofday() when such timers are available.
1912 Changes in version 0.2.3.7-alpha - 2011-10-30
1913 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
1914 the new v3 handshake. It also resolves yet another bridge address
1918 - If we mark an OR connection for close based on a cell we process,
1919 don't process any further cells on it. We already avoid further
1920 reads on marked-for-close connections, but now we also discard the
1921 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1922 which was the first version where we might mark a connection for
1923 close based on processing a cell on it.
1924 - Fix a double-free bug that would occur when we received an invalid
1925 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
1926 bugfix on 0.2.3.6-alpha.
1927 - Bridges no longer include their address in NETINFO cells on outgoing
1928 OR connections, to allow them to blend in better with clients.
1929 Removes another avenue for enumerating bridges. Reported by
1930 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
1931 cells were introduced.
1934 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
1935 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1938 Changes in version 0.2.3.6-alpha - 2011-10-26
1939 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
1940 anonymity vulnerability where an attacker can deanonymize Tor
1941 users. Everybody should upgrade.
1943 This release also features support for a new v3 connection handshake
1944 protocol, and fixes to make hidden service connections more robust.
1947 - Implement a new handshake protocol (v3) for authenticating Tors to
1948 each other over TLS. It should be more resistant to fingerprinting
1949 than previous protocols, and should require less TLS hacking for
1950 future Tor implementations. Implements proposal 176.
1951 - Allow variable-length padding cells to disguise the length of
1952 Tor's TLS records. Implements part of proposal 184.
1954 o Privacy/anonymity fixes (clients):
1955 - Clients and bridges no longer send TLS certificate chains on
1956 outgoing OR connections. Previously, each client or bridge would
1957 use the same cert chain for all outgoing OR connections until
1958 its IP address changes, which allowed any relay that the client
1959 or bridge contacted to determine which entry guards it is using.
1960 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1961 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1962 no longer considers that connection as suitable for satisfying a
1963 circuit EXTEND request. Now relays can protect clients from the
1964 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1965 - Directory authorities no longer assign the Guard flag to relays
1966 that haven't upgraded to the above "refuse EXTEND requests
1967 to client connections" fix. Now directory authorities can
1968 protect clients from the CVE-2011-2768 issue even if neither
1969 the clients nor the relays have upgraded yet. There's a new
1970 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1971 to let us transition smoothly, else tomorrow there would be no
1974 o Major bugfixes (hidden services):
1975 - Improve hidden service robustness: when an attempt to connect to
1976 a hidden service ends, be willing to refetch its hidden service
1977 descriptors from each of the HSDir relays responsible for them
1978 immediately. Previously, we would not consider refetching the
1979 service's descriptors from each HSDir for 15 minutes after the last
1980 fetch, which was inconvenient if the hidden service was not running
1981 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
1982 - When one of a hidden service's introduction points appears to be
1983 unreachable, stop trying it. Previously, we would keep trying
1984 to build circuits to the introduction point until we lost the
1985 descriptor, usually because the user gave up and restarted Tor.
1986 Partly fixes bug 3825.
1987 - Don't launch a useless circuit after failing to use one of a
1988 hidden service's introduction points. Previously, we would
1989 launch a new introduction circuit, but not set the hidden service
1990 which that circuit was intended to connect to, so it would never
1991 actually be used. A different piece of code would then create a
1992 new introduction circuit correctly. Bug reported by katmagic and
1993 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1995 o Major bugfixes (other):
1996 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1997 that they initiated. Relays could distinguish incoming bridge
1998 connections from client connections, creating another avenue for
1999 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2000 Found by "frosty_un".
2001 - Don't update the AccountingSoftLimitHitAt state file entry whenever
2002 tor gets started. This prevents a wrong average bandwidth
2003 estimate, which would cause relays to always start a new accounting
2004 interval at the earliest possible moment. Fixes bug 2003; bugfix
2005 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
2006 immensely in tracking this bug down.
2007 - Fix a crash bug when changing node restrictions while a DNS lookup
2008 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
2011 o Minor bugfixes (on 0.2.2.x and earlier):
2012 - When a hidden service turns an extra service-side introduction
2013 circuit into a general-purpose circuit, free the rend_data and
2014 intro_key fields first, so we won't leak memory if the circuit
2015 is cannibalized for use as another service-side introduction
2016 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
2017 - Rephrase the log message emitted if the TestSocks check is
2018 successful. Patch from Fabian Keil; fixes bug 4094.
2019 - Bridges now skip DNS self-tests, to act a little more stealthily.
2020 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
2021 bridges. Patch by "warms0x".
2022 - Remove a confusing dollar sign from the example fingerprint in the
2023 man page, and also make the example fingerprint a valid one. Fixes
2024 bug 4309; bugfix on 0.2.1.3-alpha.
2025 - Fix internal bug-checking logic that was supposed to catch
2026 failures in digest generation so that it will fail more robustly
2027 if we ask for a nonexistent algorithm. Found by Coverity Scan.
2028 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
2029 - Report any failure in init_keys() calls launched because our
2030 IP address has changed. Spotted by Coverity Scan. Bugfix on
2031 0.1.1.4-alpha; fixes CID 484.
2033 o Minor bugfixes (on 0.2.3.x):
2034 - Fix a bug in configure.in that kept it from building a configure
2035 script with autoconf versions earlier than 2.61. Fixes bug 2430;
2036 bugfix on 0.2.3.1-alpha.
2037 - Don't warn users that they are exposing a client port to the
2038 Internet if they have specified an RFC1918 address. Previously,
2039 we would warn if the user had specified any non-loopback
2040 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
2041 - Fix memory leaks in the failing cases of the new SocksPort and
2042 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
2043 fixes coverity CIDs 485, 486, and 487.
2046 - When a hidden service's introduction point times out, consider
2047 trying it again during the next attempt to connect to the
2048 HS. Previously, we would not try it again unless a newly fetched
2049 descriptor contained it. Required by fixes for bugs 1297 and 3825.
2050 - The next version of Windows will be called Windows 8, and it has
2051 a major version of 6, minor version of 2. Correctly identify that
2052 version instead of calling it "Very recent version". Resolves
2053 ticket 4153; reported by funkstar.
2054 - The Bridge Authority now writes statistics on how many bridge
2055 descriptors it gave out in total, and how many unique descriptors
2056 it gave out. It also lists how often the most and least commonly
2057 fetched descriptors were given out, as well as the median and
2058 25th/75th percentile. Implements tickets 4200 and 4294.
2059 - Update to the October 4 2011 Maxmind GeoLite Country database.
2061 o Code simplifications and refactoring:
2062 - Remove some old code to remember statistics about which descriptors
2063 we've served as a directory mirror. The feature wasn't used and
2064 is outdated now that microdescriptors are around.
2065 - Rename Tor functions that turn strings into addresses, so that
2066 "parse" indicates that no hostname resolution occurs, and
2067 "lookup" indicates that hostname resolution may occur. This
2068 should help prevent mistakes in the future. Fixes bug 3512.
2071 Changes in version 0.2.2.34 - 2011-10-26
2072 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
2073 can deanonymize Tor users. Everybody should upgrade.
2075 The attack relies on four components: 1) Clients reuse their TLS cert
2076 when talking to different relays, so relays can recognize a user by
2077 the identity key in her cert. 2) An attacker who knows the client's
2078 identity key can probe each guard relay to see if that identity key
2079 is connected to that guard relay right now. 3) A variety of active
2080 attacks in the literature (starting from "Low-Cost Traffic Analysis
2081 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
2082 discover the guard relays that a Tor user visiting the website is using.
2083 4) Clients typically pick three guards at random, so the set of guards
2084 for a given user could well be a unique fingerprint for her. This
2085 release fixes components #1 and #2, which is enough to block the attack;
2086 the other two remain as open research problems. Special thanks to
2087 "frosty_un" for reporting the issue to us!
2089 Clients should upgrade so they are no longer recognizable by the TLS
2090 certs they present. Relays should upgrade so they no longer allow a
2091 remote attacker to probe them to test whether unpatched clients are
2092 currently connected to them.
2094 This release also fixes several vulnerabilities that allow an attacker
2095 to enumerate bridge relays. Some bridge enumeration attacks still
2096 remain; see for example proposal 188.
2098 o Privacy/anonymity fixes (clients):
2099 - Clients and bridges no longer send TLS certificate chains on
2100 outgoing OR connections. Previously, each client or bridge would
2101 use the same cert chain for all outgoing OR connections until
2102 its IP address changes, which allowed any relay that the client
2103 or bridge contacted to determine which entry guards it is using.
2104 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2105 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2106 no longer considers that connection as suitable for satisfying a
2107 circuit EXTEND request. Now relays can protect clients from the
2108 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2109 - Directory authorities no longer assign the Guard flag to relays
2110 that haven't upgraded to the above "refuse EXTEND requests
2111 to client connections" fix. Now directory authorities can
2112 protect clients from the CVE-2011-2768 issue even if neither
2113 the clients nor the relays have upgraded yet. There's a new
2114 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
2115 to let us transition smoothly, else tomorrow there would be no
2118 o Privacy/anonymity fixes (bridge enumeration):
2119 - Bridge relays now do their directory fetches inside Tor TLS
2120 connections, like all the other clients do, rather than connecting
2121 directly to the DirPort like public relays do. Removes another
2122 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
2123 - Bridges relays now build circuits for themselves in a more similar
2124 way to how clients build them. Removes another avenue for
2125 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
2126 when bridges were introduced.
2127 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2128 that they initiated. Relays could distinguish incoming bridge
2129 connections from client connections, creating another avenue for
2130 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2131 Found by "frosty_un".
2134 - Fix a crash bug when changing node restrictions while a DNS lookup
2135 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
2137 - Don't launch a useless circuit after failing to use one of a
2138 hidden service's introduction points. Previously, we would
2139 launch a new introduction circuit, but not set the hidden service
2140 which that circuit was intended to connect to, so it would never
2141 actually be used. A different piece of code would then create a
2142 new introduction circuit correctly. Bug reported by katmagic and
2143 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
2146 - Change an integer overflow check in the OpenBSD_Malloc code so
2147 that GCC is less likely to eliminate it as impossible. Patch
2148 from Mansour Moufid. Fixes bug 4059.
2149 - When a hidden service turns an extra service-side introduction
2150 circuit into a general-purpose circuit, free the rend_data and
2151 intro_key fields first, so we won't leak memory if the circuit
2152 is cannibalized for use as another service-side introduction
2153 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
2154 - Bridges now skip DNS self-tests, to act a little more stealthily.
2155 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
2156 bridges. Patch by "warms0x".
2157 - Fix internal bug-checking logic that was supposed to catch
2158 failures in digest generation so that it will fail more robustly
2159 if we ask for a nonexistent algorithm. Found by Coverity Scan.
2160 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
2161 - Report any failure in init_keys() calls launched because our
2162 IP address has changed. Spotted by Coverity Scan. Bugfix on
2163 0.1.1.4-alpha; fixes CID 484.
2165 o Minor bugfixes (log messages and documentation):
2166 - Remove a confusing dollar sign from the example fingerprint in the
2167 man page, and also make the example fingerprint a valid one. Fixes
2168 bug 4309; bugfix on 0.2.1.3-alpha.
2169 - The next version of Windows will be called Windows 8, and it has
2170 a major version of 6, minor version of 2. Correctly identify that
2171 version instead of calling it "Very recent version". Resolves
2172 ticket 4153; reported by funkstar.
2173 - Downgrade log messages about circuit timeout calibration from
2174 "notice" to "info": they don't require or suggest any human
2175 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
2176 bugfix on 0.2.2.14-alpha.
2179 - Turn on directory request statistics by default and include them in
2180 extra-info descriptors. Don't break if we have no GeoIP database.
2181 Backported from 0.2.3.1-alpha; implements ticket 3951.
2182 - Update to the October 4 2011 Maxmind GeoLite Country database.
2185 Changes in version 0.2.1.31 - 2011-10-26
2186 Tor 0.2.1.31 backports important security and privacy fixes for
2187 oldstable. This release is intended only for package maintainers and
2188 others who cannot use the 0.2.2 stable series. All others should be
2189 using Tor 0.2.2.x or newer.
2191 o Security fixes (also included in 0.2.2.x):
2192 - Replace all potentially sensitive memory comparison operations
2193 with versions whose runtime does not depend on the data being
2194 compared. This will help resist a class of attacks where an
2195 adversary can use variations in timing information to learn
2196 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2197 implementation by Robert Ransom based partially on code by DJB.)
2198 - Fix an assert in parsing router descriptors containing IPv6
2199 addresses. This one took down the directory authorities when
2200 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
2202 o Privacy/anonymity fixes (also included in 0.2.2.x):
2203 - Clients and bridges no longer send TLS certificate chains on
2204 outgoing OR connections. Previously, each client or bridge would
2205 use the same cert chain for all outgoing OR connections until
2206 its IP address changes, which allowed any relay that the client
2207 or bridge contacted to determine which entry guards it is using.
2208 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2209 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2210 no longer considers that connection as suitable for satisfying a
2211 circuit EXTEND request. Now relays can protect clients from the
2212 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2213 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2214 that they initiated. Relays could distinguish incoming bridge
2215 connections from client connections, creating another avenue for
2216 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2217 Found by "frosty_un".
2218 - When receiving a hidden service descriptor, check that it is for
2219 the hidden service we wanted. Previously, Tor would store any
2220 hidden service descriptors that a directory gave it, whether it
2221 wanted them or not. This wouldn't have let an attacker impersonate
2222 a hidden service, but it did let directories pre-seed a client
2223 with descriptors that it didn't want. Bugfix on 0.0.6.
2224 - Avoid linkability based on cached hidden service descriptors: forget
2225 all hidden service descriptors cached as a client when processing a
2226 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
2227 - Make the bridge directory authority refuse to answer directory
2228 requests for "all" descriptors. It used to include bridge
2229 descriptors in its answer, which was a major information leak.
2230 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
2231 - Don't attach new streams to old rendezvous circuits after SIGNAL
2232 NEWNYM. Previously, we would keep using an existing rendezvous
2233 circuit if it remained open (i.e. if it were kept open by a
2234 long-lived stream, or if a new stream were attached to it before
2235 Tor could notice that it was old and no longer in use). Bugfix on
2236 0.1.1.15-rc; fixes bug 3375.
2238 o Minor bugfixes (also included in 0.2.2.x):
2239 - When we restart our relay, we might get a successful connection
2240 from the outside before we've started our reachability tests,
2241 triggering a warning: "ORPort found reachable, but I have no
2242 routerinfo yet. Failing to inform controller of success." This
2243 bug was harmless unless Tor is running under a controller
2244 like Vidalia, in which case the controller would never get a
2245 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
2247 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
2248 enabled. Fixes bug 1526.
2249 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2250 anything since 0.2.1.16-rc.
2251 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
2252 None of the cases where we did this before were wrong, but by making
2253 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
2254 - Fix a rare crash bug that could occur when a client was configured
2255 with a large number of bridges. Fixes bug 2629; bugfix on
2256 0.2.1.2-alpha. Bugfix by trac user "shitlei".
2257 - Correct the warning displayed when a rendezvous descriptor exceeds
2258 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
2260 - Fix an uncommon assertion failure when running with DNSPort under
2261 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
2262 - When warning about missing zlib development packages during compile,
2263 give the correct package names. Bugfix on 0.2.0.1-alpha.
2264 - Require that introduction point keys and onion keys have public
2265 exponent 65537. Bugfix on 0.2.0.10-alpha.
2266 - Do not crash when our configuration file becomes unreadable, for
2267 example due to a permissions change, between when we start up
2268 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2270 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2272 - Always NUL-terminate the sun_path field of a sockaddr_un before
2273 passing it to the kernel. (Not a security issue: kernels are
2274 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2275 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2276 - Don't stack-allocate the list of supplementary GIDs when we're
2277 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2278 could take up to 256K, which is way too much stack. Found by
2279 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2281 o Minor bugfixes (only in 0.2.1.x):
2282 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
2283 rely on them. Bugfix on 0.2.1.30.
2284 - Use git revisions instead of svn revisions when generating our
2285 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
2287 o Minor features (also included in 0.2.2.x):
2288 - Adjust the expiration time on our SSL session certificates to
2289 better match SSL certs seen in the wild. Resolves ticket 4014.
2290 - Allow nameservers with IPv6 address. Resolves bug 2574.
2291 - Update to the October 4 2011 Maxmind GeoLite Country database.
2294 Changes in version 0.2.3.5-alpha - 2011-09-28
2295 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
2296 bridge relays; fixes an assertion error that many users started hitting
2297 today; and adds the ability to refill token buckets more often than
2298 once per second, allowing significant performance improvements.
2301 - Bridge relays now do their directory fetches inside Tor TLS
2302 connections, like all the other clients do, rather than connecting
2303 directly to the DirPort like public relays do. Removes another
2304 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
2305 - Bridges relays now build circuits for themselves in a more similar
2306 way to how clients build them. Removes another avenue for
2307 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
2308 when bridges were introduced.
2311 - Fix an "Assertion md->held_by_node == 1 failed" error that could
2312 occur when the same microdescriptor was referenced by two node_t
2313 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
2315 o Major features (networking):
2316 - Add a new TokenBucketRefillInterval option to refill token buckets
2317 more frequently than once per second. This should improve network
2318 performance, alleviate queueing problems, and make traffic less
2319 bursty. Implements proposal 183; closes ticket 3630. Design by
2320 Florian Tschorsch and Björn Scheuermann; implementation by
2324 - Change an integer overflow check in the OpenBSD_Malloc code so
2325 that GCC is less likely to eliminate it as impossible. Patch
2326 from Mansour Moufid. Fixes bug 4059.
2328 o Minor bugfixes (usability):
2329 - Downgrade log messages about circuit timeout calibration from
2330 "notice" to "info": they don't require or suggest any human
2331 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
2332 bugfix on 0.2.2.14-alpha.
2334 o Minor features (diagnostics):
2335 - When the system call to create a listener socket fails, log the
2336 error message explaining why. This may help diagnose bug 4027.
2339 Changes in version 0.2.3.4-alpha - 2011-09-13
2340 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
2341 tweak to Tor's TLS handshake that makes relays and bridges that run
2342 this new version reachable from Iran again. It also fixes a few new
2343 bugs in 0.2.3.x, and teaches relays to recognize when they're not
2344 listed in the network consensus and republish.
2346 o Major bugfixes (also part of 0.2.2.33):
2347 - Avoid an assertion failure when reloading a configuration with
2348 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2349 3923; bugfix on 0.2.2.25-alpha.
2351 o Minor features (security, also part of 0.2.2.33):
2352 - Check for replays of the public-key encrypted portion of an
2353 INTRODUCE1 cell, in addition to the current check for replays of
2354 the g^x value. This prevents a possible class of active attacks
2355 by an attacker who controls both an introduction point and a
2356 rendezvous point, and who uses the malleability of AES-CTR to
2357 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2358 that these attacks is infeasible (requiring the attacker to send
2359 on the order of zettabytes of altered cells in a short interval),
2360 but we'd rather block them off in case there are any classes of
2361 this attack that we missed. Reported by Willem Pinckaers.
2363 o Minor features (also part of 0.2.2.33):
2364 - Adjust the expiration time on our SSL session certificates to
2365 better match SSL certs seen in the wild. Resolves ticket 4014.
2366 - Change the default required uptime for a relay to be accepted as
2367 a HSDir (hidden service directory) from 24 hours to 25 hours.
2368 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2369 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2370 authorities to abstain from voting on assignment of the HSDir
2371 consensus flag. Related to bug 2649.
2372 - Update to the September 6 2011 Maxmind GeoLite Country database.
2374 o Minor bugfixes (also part of 0.2.2.33):
2375 - Demote the 'replay detected' log message emitted when a hidden
2376 service receives the same Diffie-Hellman public key in two different
2377 INTRODUCE2 cells to info level. A normal Tor client can cause that
2378 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2379 fixes part of bug 2442.
2380 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2381 level. There is nothing that a hidden service's operator can do
2382 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2384 - Clarify a log message specifying the characters permitted in
2385 HiddenServiceAuthorizeClient client names. Previously, the log
2386 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2387 given the impression that every ASCII character between "+" and "_"
2388 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2390 o Build fixes (also part of 0.2.2.33):
2391 - Clean up some code issues that prevented Tor from building on older
2392 BSDs. Fixes bug 3894; reported by "grarpamp".
2393 - Search for a platform-specific version of "ar" when cross-compiling.
2394 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2397 - Fix a bug where the SocksPort option (for example) would get
2398 ignored and replaced by the default if a SocksListenAddress
2399 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
2403 - Relays now try regenerating and uploading their descriptor more
2404 frequently if they are not listed in the consensus, or if the
2405 version of their descriptor listed in the consensus is too
2406 old. This fix should prevent situations where a server declines
2407 to re-publish itself because it has done so too recently, even
2408 though the authorities decided not to list its recent-enough
2409 descriptor. Fix for bug 3327.
2412 - Relays now include a reason for regenerating their descriptors
2413 in an HTTP header when uploading to the authorities. This will
2414 make it easier to debug descriptor-upload issues in the future.
2415 - When starting as root and then changing our UID via the User
2416 control option, and we have a ControlSocket configured, make sure
2417 that the ControlSocket is owned by the same account that Tor will
2418 run under. Implements ticket 3421; fix by Jérémy Bobbio.
2421 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
2422 utility function used in the control-port code). This shouldn't
2423 ever happen unless Tor is completely out of memory, but if it did
2424 happen and Tor somehow recovered from it, Tor could have sent a log
2425 message to a control port in the middle of a reply to a controller
2426 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
2427 - Make 'FetchUselessDescriptors' cause all descriptor types and
2428 all consensus types (including microdescriptors) to get fetched.
2429 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
2432 - Make a new "entry connection" struct as an internal subtype of "edge
2433 connection", to simplify the code and make exit connections smaller.
2436 Changes in version 0.2.2.33 - 2011-09-13
2437 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
2438 TLS handshake that makes relays and bridges that run this new version
2439 reachable from Iran again.
2442 - Avoid an assertion failure when reloading a configuration with
2443 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2444 3923; bugfix on 0.2.2.25-alpha.
2446 o Minor features (security):
2447 - Check for replays of the public-key encrypted portion of an
2448 INTRODUCE1 cell, in addition to the current check for replays of
2449 the g^x value. This prevents a possible class of active attacks
2450 by an attacker who controls both an introduction point and a
2451 rendezvous point, and who uses the malleability of AES-CTR to
2452 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2453 that these attacks are infeasible (requiring the attacker to send
2454 on the order of zettabytes of altered cells in a short interval),
2455 but we'd rather block them off in case there are any classes of
2456 this attack that we missed. Reported by Willem Pinckaers.
2459 - Adjust the expiration time on our SSL session certificates to
2460 better match SSL certs seen in the wild. Resolves ticket 4014.
2461 - Change the default required uptime for a relay to be accepted as
2462 a HSDir (hidden service directory) from 24 hours to 25 hours.
2463 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2464 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2465 authorities to abstain from voting on assignment of the HSDir
2466 consensus flag. Related to bug 2649.
2467 - Update to the September 6 2011 Maxmind GeoLite Country database.
2469 o Minor bugfixes (documentation and log messages):
2470 - Correct the man page to explain that HashedControlPassword and
2471 CookieAuthentication can both be set, in which case either method
2472 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2473 when we decided to allow these config options to both be set. Issue
2475 - Demote the 'replay detected' log message emitted when a hidden
2476 service receives the same Diffie-Hellman public key in two different
2477 INTRODUCE2 cells to info level. A normal Tor client can cause that
2478 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2479 fixes part of bug 2442.
2480 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2481 level. There is nothing that a hidden service's operator can do
2482 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2484 - Clarify a log message specifying the characters permitted in
2485 HiddenServiceAuthorizeClient client names. Previously, the log
2486 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2487 given the impression that every ASCII character between "+" and "_"
2488 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2491 - Provide a substitute implementation of lround() for MSVC, which
2492 apparently lacks it. Patch from Gisle Vanem.
2493 - Clean up some code issues that prevented Tor from building on older
2494 BSDs. Fixes bug 3894; reported by "grarpamp".
2495 - Search for a platform-specific version of "ar" when cross-compiling.
2496 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2499 Changes in version 0.2.3.3-alpha - 2011-09-01
2500 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
2501 security, and provides client-side support for the microdescriptor
2502 and optimistic data features introduced earlier in the 0.2.3.x
2503 series. It also includes numerous critical bugfixes in the (optional)
2504 bufferevent-based networking backend.
2506 o Major features (stream isolation):
2507 - You can now configure Tor so that streams from different
2508 applications are isolated on different circuits, to prevent an
2509 attacker who sees your streams as they leave an exit node from
2510 linking your sessions to one another. To do this, choose some way
2511 to distinguish the applications: have them connect to different
2512 SocksPorts, or have one of them use SOCKS4 while the other uses
2513 SOCKS5, or have them pass different authentication strings to the
2514 SOCKS proxy. Then, use the new SocksPort syntax to configure the
2515 degree of isolation you need. This implements Proposal 171.
2516 - There's a new syntax for specifying multiple client ports (such as
2517 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
2518 multiple *Port entries with full addr:port syntax on each.
2519 The old *ListenAddress format is still supported, but you can't
2520 mix it with the new *Port syntax.
2522 o Major features (other):
2523 - Enable microdescriptor fetching by default for clients. This allows
2524 clients to download a much smaller amount of directory information.
2525 To disable it (and go back to the old-style consensus and
2526 descriptors), set "UseMicrodescriptors 0" in your torrc file.
2527 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
2528 "PortForwarding" config option), now supports Windows.
2529 - When using an exit relay running 0.2.3.x, clients can now
2530 "optimistically" send data before the exit relay reports that
2531 the stream has opened. This saves a round trip when starting
2532 connections where the client speaks first (such as web browsing).
2533 This behavior is controlled by a consensus parameter (currently
2534 disabled). To turn it on or off manually, use the "OptimisticData"
2535 torrc option. Implements proposal 181; code by Ian Goldberg.
2537 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
2538 - When using IOCP on Windows, we need to enable Libevent windows
2540 - The IOCP backend now works even when the user has not specified
2541 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
2542 Fixes part of bug 3752.
2543 - Correctly record the bytes we've read and written when using
2544 bufferevents, so that we can include them in our bandwidth history
2545 and advertised bandwidth. Fixes bug 3803.
2546 - Apply rate-limiting only at the bottom of a chain of filtering
2547 bufferevents. This prevents us from filling up internal read
2548 buffers and violating rate-limits when filtering bufferevents
2549 are enabled. Fixes part of bug 3804.
2550 - Add high-watermarks to the output buffers for filtered
2551 bufferevents. This prevents us from filling up internal write
2552 buffers and wasting CPU cycles when filtering bufferevents are
2553 enabled. Fixes part of bug 3804.
2554 - Correctly notice when data has been written from a bufferevent
2555 without flushing it completely. Fixes bug 3805.
2556 - Fix a bug where server-side tunneled bufferevent-based directory
2557 streams would get closed prematurely. Fixes bug 3814.
2558 - Fix a use-after-free error with per-connection rate-limiting
2559 buckets. Fixes bug 3888.
2561 o Major bugfixes (also part of 0.2.2.31-rc):
2562 - If we're configured to write our ControlPorts to disk, only write
2563 them after switching UID and creating the data directory. This way,
2564 we don't fail when starting up with a nonexistent DataDirectory
2565 and a ControlPortWriteToFile setting based on that directory. Fixes
2566 bug 3747; bugfix on Tor 0.2.2.26-beta.
2569 - Added a new CONF_CHANGED event so that controllers can be notified
2570 of any configuration changes made by other controllers, or by the
2571 user. Implements ticket 1692.
2572 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
2573 leak when using bufferevents, and lets Libevent worry about how to
2574 best copy data out of a buffer.
2575 - Replace files in stats/ rather than appending to them. Now that we
2576 include statistics in extra-info descriptors, it makes no sense to
2577 keep old statistics forever. Implements ticket 2930.
2579 o Minor features (build compatibility):
2580 - Limited, experimental support for building with nmake and MSVC.
2581 - Provide a substitute implementation of lround() for MSVC, which
2582 apparently lacks it. Patch from Gisle Vanem.
2584 o Minor features (also part of 0.2.2.31-rc):
2585 - Update to the August 2 2011 Maxmind GeoLite Country database.
2587 o Minor bugfixes (on 0.2.3.x-alpha):
2588 - Fix a spurious warning when parsing SOCKS requests with
2589 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
2590 - Get rid of a harmless warning that could happen on relays running
2591 with bufferevents. The warning was caused by someone doing an http
2592 request to a relay's orport. Also don't warn for a few related
2593 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
2595 o Minor bugfixes (on 2.2.x and earlier):
2596 - Correct the man page to explain that HashedControlPassword and
2597 CookieAuthentication can both be set, in which case either method
2598 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2599 when we decided to allow these config options to both be set. Issue
2601 - The "--quiet" and "--hush" options now apply not only to Tor's
2602 behavior before logs are configured, but also to Tor's behavior in
2603 the absense of configured logs. Fixes bug 3550; bugfix on
2606 o Minor bugfixes (also part of 0.2.2.31-rc):
2607 - Write several files in text mode, on OSes that distinguish text
2608 mode from binary mode (namely, Windows). These files are:
2609 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2610 that collect those statistics; 'client_keys' and 'hostname' for
2611 hidden services that use authentication; and (in the tor-gencert
2612 utility) newly generated identity and signing keys. Previously,
2613 we wouldn't specify text mode or binary mode, leading to an
2614 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2615 the DirRecordUsageByCountry option which would have triggered
2616 the assertion failure was added), although this assertion failure
2617 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2618 - Selectively disable deprecation warnings on OS X because Lion
2619 started deprecating the shipped copy of openssl. Fixes bug 3643.
2620 - Remove an extra pair of quotation marks around the error
2621 message in control-port STATUS_GENERAL BUG events. Bugfix on
2622 0.1.2.6-alpha; fixes bug 3732.
2623 - When unable to format an address as a string, report its value
2624 as "???" rather than reusing the last formatted address. Bugfix
2627 o Code simplifications and refactoring:
2628 - Rewrite the listener-selection logic so that parsing which ports
2629 we want to listen on is now separate from binding to the ports
2633 - Building Tor with bufferevent support now requires Libevent
2634 2.0.13-stable or later. Previous versions of Libevent had bugs in
2635 SSL-related bufferevents and related issues that would make Tor
2636 work badly with bufferevents. Requiring 2.0.13-stable also allows
2637 Tor with bufferevents to take advantage of Libevent APIs
2638 introduced after 2.0.8-rc.
2641 Changes in version 0.2.2.32 - 2011-08-27
2642 The Tor 0.2.2 release series is dedicated to the memory of Andreas
2643 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
2644 a founder of the PETS community, a leader in our field, a mentor,
2645 and a friend. He left us with these words: "I had the possibility
2646 to contribute to this world that is not as it should be. I hope I
2647 could help in some areas to make the world a better place, and that
2648 I could also encourage other people to be engaged in improving the
2649 world. Please, stay engaged. This world needs you, your love, your
2650 initiative -- now I cannot be part of that anymore."
2652 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
2653 ready. More than two years in the making, this release features improved
2654 client performance and hidden service reliability, better compatibility
2655 for Android, correct behavior for bridges that listen on more than
2656 one address, more extensible and flexible directory object handling,
2657 better reporting of network statistics, improved code security, and
2658 many many other features and bugfixes.
2661 Changes in version 0.2.2.31-rc - 2011-08-17
2662 Tor 0.2.2.31-rc is the second and hopefully final release candidate
2663 for the Tor 0.2.2.x series.
2666 - Remove an extra pair of quotation marks around the error
2667 message in control-port STATUS_GENERAL BUG events. Bugfix on
2668 0.1.2.6-alpha; fixes bug 3732.
2669 - If we're configured to write our ControlPorts to disk, only write
2670 them after switching UID and creating the data directory. This way,
2671 we don't fail when starting up with a nonexistent DataDirectory
2672 and a ControlPortWriteToFile setting based on that directory. Fixes
2673 bug 3747; bugfix on Tor 0.2.2.26-beta.
2676 - Update to the August 2 2011 Maxmind GeoLite Country database.
2679 - Allow GETINFO fingerprint to return a fingerprint even when
2680 we have not yet built a router descriptor. Fixes bug 3577;
2681 bugfix on 0.2.0.1-alpha.
2682 - Write several files in text mode, on OSes that distinguish text
2683 mode from binary mode (namely, Windows). These files are:
2684 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2685 that collect those statistics; 'client_keys' and 'hostname' for
2686 hidden services that use authentication; and (in the tor-gencert
2687 utility) newly generated identity and signing keys. Previously,
2688 we wouldn't specify text mode or binary mode, leading to an
2689 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2690 the DirRecordUsageByCountry option which would have triggered
2691 the assertion failure was added), although this assertion failure
2692 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2693 - Selectively disable deprecation warnings on OS X because Lion
2694 started deprecating the shipped copy of openssl. Fixes bug 3643.
2695 - When unable to format an address as a string, report its value
2696 as "???" rather than reusing the last formatted address. Bugfix
2700 Changes in version 0.2.3.2-alpha - 2011-07-18
2701 Tor 0.2.3.2-alpha introduces two new experimental features:
2702 microdescriptors and pluggable transports. It also continues cleaning
2703 up a variety of recently introduced features.
2706 - Clients can now use microdescriptors instead of regular descriptors
2707 to build circuits. Microdescriptors are authority-generated
2708 summaries of regular descriptors' contents, designed to change
2709 very rarely (see proposal 158 for details). This feature is
2710 designed to save bandwidth, especially for clients on slow internet
2711 connections. It's off by default for now, since nearly no caches
2712 support it, but it will be on-by-default for clients in a future
2713 version. You can use the UseMicrodescriptors option to turn it on.
2714 - Tor clients using bridges can now be configured to use a separate
2715 'transport' proxy for each bridge. This approach helps to resist
2716 censorship by allowing bridges to use protocol obfuscation
2717 plugins. It implements part of proposal 180. Implements ticket 2841.
2718 - While we're trying to bootstrap, record how many TLS connections
2719 fail in each state, and report which states saw the most failures
2720 in response to any bootstrap failures. This feature may speed up
2721 diagnosis of censorship events. Implements ticket 3116.
2723 o Major bugfixes (on 0.2.3.1-alpha):
2724 - When configuring a large set of nodes in EntryNodes (as with
2725 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
2726 random subset to be guards, and choose them in random
2727 order. Fixes bug 2798.
2728 - Tor could crash when remembering a consensus in a non-used consensus
2729 flavor without having a current consensus set. Fixes bug 3361.
2730 - Comparing an unknown address to a microdescriptor's shortened exit
2731 policy would always give a "rejected" result. Fixes bug 3599.
2732 - Using microdescriptors as a client no longer prevents Tor from
2733 uploading and downloading hidden service descriptors. Fixes
2737 - Allow nameservers with IPv6 address. Resolves bug 2574.
2738 - Accept attempts to include a password authenticator in the
2739 handshake, as supported by SOCKS5. This handles SOCKS clients that
2740 don't know how to omit a password when authenticating. Resolves
2742 - When configuring a large set of nodes in EntryNodes, and there are
2743 enough of them listed as Guard so that we don't need to consider
2744 the non-guard entries, prefer the ones listed with the Guard flag.
2745 - Check for and recover from inconsistency in the microdescriptor
2746 cache. This will make it harder for us to accidentally free a
2747 microdescriptor without removing it from the appropriate data
2748 structures. Fixes issue 3135; issue noted by "wanoskarnet".
2749 - Log SSL state transitions at log level DEBUG, log domain
2750 HANDSHAKE. This can be useful for debugging censorship events.
2751 Implements ticket 3264.
2752 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
2753 implements ticket 3439.
2755 o Minor bugfixes (on 0.2.3.1-alpha):
2756 - Do not free all general-purpose regular descriptors just
2757 because microdescriptor use is enabled. Fixes bug 3113.
2758 - Correctly link libevent_openssl when --enable-static-libevent
2759 is passed to configure. Fixes bug 3118.
2760 - Bridges should not complain during their heartbeat log messages that
2761 they are unlisted in the consensus: that's more or less the point
2762 of being a bridge. Fixes bug 3183.
2763 - Report a SIGNAL event to controllers when acting on a delayed
2764 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
2765 event to the controller if we acted on a SIGNAL NEWNYM command
2766 immediately, and otherwise not report a SIGNAL event for the
2767 command at all. Fixes bug 3349.
2768 - Fix a crash when handling the SIGNAL controller command or
2769 reporting ERR-level status events with bufferevents enabled. Found
2770 by Robert Ransom. Fixes bug 3367.
2771 - Always ship the tor-fw-helper manpage in our release tarballs.
2772 Fixes bug 3389. Reported by Stephen Walker.
2773 - Fix a class of double-mark-for-close bugs when bufferevents
2774 are enabled. Fixes bug 3403.
2775 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
2776 - Add SIGNAL to the list returned by the 'GETINFO events/names'
2777 control-port command. Fixes part of bug 3465.
2778 - Prevent using negative indices during unit test runs when read_all()
2779 fails. Spotted by coverity.
2780 - Fix a rare memory leak when checking the nodelist without it being
2781 present. Found by coverity.
2782 - Only try to download a microdescriptor-flavored consensus from
2783 a directory cache that provides them.
2785 o Minor bugfixes (on 0.2.2.x and earlier):
2786 - Assert that hidden-service-related operations are not performed
2787 using single-hop circuits. Previously, Tor would assert that
2788 client-side streams are not attached to single-hop circuits,
2789 but not that other sensitive operations on the client and service
2790 side are not performed using single-hop circuits. Fixes bug 3332;
2792 - Don't publish a new relay descriptor when we reload our onion key,
2793 unless the onion key has actually changed. Fixes bug 3263 and
2794 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
2795 - Allow GETINFO fingerprint to return a fingerprint even when
2796 we have not yet built a router descriptor. Fixes bug 3577;
2797 bugfix on 0.2.0.1-alpha.
2798 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
2799 on 0.2.2.4-alpha; fixes bug 3427.
2801 o Code simplification and refactoring:
2802 - Use tor_sscanf() in place of scanf() in more places through the
2803 code. This makes us a little more locale-independent, and
2804 should help shut up code-analysis tools that can't tell
2805 a safe sscanf string from a dangerous one.
2806 - Use tt_assert(), not tor_assert(), for checking for test failures.
2807 This makes the unit tests more able to go on in the event that
2809 - Split connection_about_to_close() into separate functions for each
2813 - On Windows, we now define the _WIN32_WINNT macros only if they
2814 are not already defined. This lets the person building Tor decide,
2815 if they want, to require a later version of Windows.
2818 Changes in version 0.2.2.30-rc - 2011-07-07
2819 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
2820 series. It fixes a few smaller bugs, but generally appears stable.
2821 Please test it and let us know whether it is!
2824 - Send a SUCCEEDED stream event to the controller when a reverse
2825 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
2826 discovered by katmagic.
2827 - Always NUL-terminate the sun_path field of a sockaddr_un before
2828 passing it to the kernel. (Not a security issue: kernels are
2829 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2830 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2831 - Don't stack-allocate the list of supplementary GIDs when we're
2832 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2833 could take up to 256K, which is way too much stack. Found by
2834 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2835 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
2836 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
2837 fixes part of bug 3465.
2838 - Fix a memory leak when receiving a descriptor for a hidden
2839 service we didn't ask for. Found by Coverity; CID #30. Bugfix
2843 - Update to the July 1 2011 Maxmind GeoLite Country database.
2846 Changes in version 0.2.2.29-beta - 2011-06-20
2847 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
2848 have bridge lines in their torrc but don't want to use them; gets
2849 us closer to having the control socket feature working on Debian;
2850 and fixes a variety of smaller bugs.
2853 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
2854 When we changed the default behavior to "use bridges if any
2855 are listed in the torrc", we surprised users who had bridges
2856 in their torrc files but who didn't actually want to use them.
2857 Partial resolution for bug 3354.
2860 - Don't attach new streams to old rendezvous circuits after SIGNAL
2861 NEWNYM. Previously, we would keep using an existing rendezvous
2862 circuit if it remained open (i.e. if it were kept open by a
2863 long-lived stream, or if a new stream were attached to it before
2864 Tor could notice that it was old and no longer in use). Bugfix on
2865 0.1.1.15-rc; fixes bug 3375.
2868 - Fix a bug when using ControlSocketsGroupWritable with User. The
2869 directory's group would be checked against the current group, not
2870 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
2871 bugfix on 0.2.2.26-beta.
2872 - Make connection_printf_to_buf()'s behaviour sane. Its callers
2873 expect it to emit a CRLF iff the format string ends with CRLF;
2874 it actually emitted a CRLF iff (a) the format string ended with
2875 CRLF or (b) the resulting string was over 1023 characters long or
2876 (c) the format string did not end with CRLF *and* the resulting
2877 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
2878 fixes part of bug 3407.
2879 - Make send_control_event_impl()'s behaviour sane. Its callers
2880 expect it to always emit a CRLF at the end of the string; it
2881 might have emitted extra control characters as well. Bugfix on
2882 0.1.1.9-alpha; fixes another part of bug 3407.
2883 - Make crypto_rand_int() check the value of its input correctly.
2884 Previously, it accepted values up to UINT_MAX, but could return a
2885 negative number if given a value above INT_MAX+1. Found by George
2886 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
2887 - Avoid a segfault when reading a malformed circuit build state
2888 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
2890 - When asked about a DNS record type we don't support via a
2891 client DNSPort, reply with NOTIMPL rather than an empty
2892 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
2893 - Fix a rare memory leak during stats writing. Found by coverity.
2896 - Update to the June 1 2011 Maxmind GeoLite Country database.
2898 o Code simplifications and refactoring:
2899 - Remove some dead code as indicated by coverity.
2900 - Remove a few dead assignments during router parsing. Found by
2902 - Add some forgotten return value checks during unit tests. Found
2904 - Don't use 1-bit wide signed bit fields. Found by coverity.
2907 Changes in version 0.2.2.28-beta - 2011-06-04
2908 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
2909 fixed a big bug in whether relays stay in the consensus consistently,
2910 we moved closer to handling bridges and hidden services correctly,
2911 and we started the process of better handling the dreaded "my Vidalia
2912 died, and now my Tor demands a password when I try to reconnect to it"
2916 - Don't decide to make a new descriptor when receiving a HUP signal.
2917 This bug has caused a lot of 0.2.2.x relays to disappear from the
2918 consensus periodically. Fixes the most common case of triggering
2919 bug 1810; bugfix on 0.2.2.7-alpha.
2920 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
2921 - Don't try to build descriptors if "ORPort auto" is set and we
2922 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
2924 - Resolve a crash that occurred when setting BridgeRelay to 1 with
2925 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
2926 - Apply circuit timeouts to opened hidden-service-related circuits
2927 based on the correct start time. Previously, we would apply the
2928 circuit build timeout based on time since the circuit's creation;
2929 it was supposed to be applied based on time since the circuit
2930 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
2931 - Use the same circuit timeout for client-side introduction
2932 circuits as for other four-hop circuits, rather than the timeout
2933 for single-hop directory-fetch circuits; the shorter timeout may
2934 have been appropriate with the static circuit build timeout in
2935 0.2.1.x and earlier, but caused many hidden service access attempts
2936 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
2937 on 0.2.2.2-alpha; fixes another part of bug 1297.
2938 - In ticket 2511 we fixed a case where you could use an unconfigured
2939 bridge if you had configured it as a bridge the last time you ran
2940 Tor. Now fix another edge case: if you had configured it as a bridge
2941 but then switched to a different bridge via the controller, you
2942 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
2946 - Add an __OwningControllerProcess configuration option and a
2947 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
2948 that when it exits, Tor will shut down. Implements feature 3049.
2949 - If "UseBridges 1" is set and no bridges are configured, Tor will
2950 now refuse to build any circuits until some bridges are set.
2951 If "UseBridges auto" is set, Tor will use bridges if they are
2952 configured and we are not running as a server, but otherwise will
2953 make circuits as usual. The new default is "auto". Patch by anonym,
2954 so the Tails LiveCD can stop automatically revealing you as a Tor
2958 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2959 - Remove a trailing asterisk from "exit-policy/default" in the
2960 output of the control port command "GETINFO info/names". Bugfix
2962 - Use a wide type to hold sockets when built for 64-bit Windows builds.
2964 - Warn when the user configures two HiddenServiceDir lines that point
2965 to the same directory. Bugfix on 0.0.6 (the version introducing
2966 HiddenServiceDir); fixes bug 3289.
2967 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
2968 part of bug 2748; bugfix on 0.2.0.10-alpha.
2969 - Log malformed requests for rendezvous descriptors as protocol
2970 warnings, not warnings. Also, use a more informative log message
2971 in case someone sees it at log level warning without prior
2972 info-level messages. Fixes the other part of bug 2748; bugfix
2974 - Clear the table recording the time of the last request for each
2975 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
2976 Previously, we would clear our HS descriptor cache on SIGNAL
2977 NEWNYM, but if we had previously retrieved a descriptor (or tried
2978 to) from every directory responsible for it, we would refuse to
2979 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
2981 - Fix a log message that said "bits" while displaying a value in
2982 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
2984 - When checking for 1024-bit keys, check for 1024 bits, not 128
2985 bytes. This allows Tor to correctly discard keys of length 1017
2986 through 1023. Bugfix on 0.0.9pre5.
2989 - Relays now log the reason for publishing a new relay descriptor,
2990 so we have a better chance of hunting down instances of bug 1810.
2991 Resolves ticket 3252.
2992 - Revise most log messages that refer to nodes by nickname to
2993 instead use the "$key=nickname at address" format. This should be
2994 more useful, especially since nicknames are less and less likely
2995 to be unique. Resolves ticket 3045.
2996 - Log (at info level) when purging pieces of hidden-service-client
2997 state because of SIGNAL NEWNYM.
3000 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3001 anything since 0.2.1.16-rc.
3004 Changes in version 0.2.2.27-beta - 2011-05-18
3005 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
3006 release, and also adds a few more general bugfixes.
3009 - Fix a crash bug when changing bridges in a running Tor process.
3010 Fixes bug 3213; bugfix on 0.2.2.26-beta.
3011 - When the controller configures a new bridge, don't wait 10 to 60
3012 seconds before trying to fetch its descriptor. Bugfix on
3013 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
3016 - Require that onion keys have exponent 65537 in microdescriptors too.
3017 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
3018 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
3019 Changed the limit to 512 characters by removing base64 newlines.
3020 Fixes bug 2752. Fix by Michael Yakubovich.
3021 - When a client starts or stops using bridges, never use a circuit
3022 that was built before the configuration change. This behavior could
3023 put at risk a user who uses bridges to ensure that her traffic
3024 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
3028 Changes in version 0.2.2.26-beta - 2011-05-17
3029 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
3030 also introduces a new "socksport auto" approach that should make it
3031 easier to run multiple Tors on the same system, and does a lot of
3032 cleanup to get us closer to a release candidate.
3034 o Security/privacy fixes:
3035 - Replace all potentially sensitive memory comparison operations
3036 with versions whose runtime does not depend on the data being
3037 compared. This will help resist a class of attacks where an
3038 adversary can use variations in timing information to learn
3039 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3040 implementation by Robert Ransom based partially on code by DJB.)
3041 - When receiving a hidden service descriptor, check that it is for
3042 the hidden service we wanted. Previously, Tor would store any
3043 hidden service descriptors that a directory gave it, whether it
3044 wanted them or not. This wouldn't have let an attacker impersonate
3045 a hidden service, but it did let directories pre-seed a client
3046 with descriptors that it didn't want. Bugfix on 0.0.6.
3047 - On SIGHUP, do not clear out all TrackHostExits mappings, client
3048 DNS cache entries, and virtual address mappings: that's what
3049 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
3052 - The options SocksPort, ControlPort, and so on now all accept a
3053 value "auto" that opens a socket on an OS-selected port. A
3054 new ControlPortWriteToFile option tells Tor to write its
3055 actual control port or ports to a chosen file. If the option
3056 ControlPortFileGroupReadable is set, the file is created as
3057 group-readable. Now users can run two Tor clients on the same
3058 system without needing to manually mess with parameters. Resolves
3059 part of ticket 3076.
3060 - Set SO_REUSEADDR on all sockets, not just listeners. This should
3061 help busy exit nodes avoid running out of useable ports just
3062 because all the ports have been used in the near past. Resolves
3066 - New "GETINFO net/listeners/(type)" controller command to return
3067 a list of addresses and ports that are bound for listeners for a
3068 given connection type. This is useful when the user has configured
3069 "SocksPort auto" and the controller needs to know which port got
3070 chosen. Resolves another part of ticket 3076.
3071 - Add a new ControlSocketsGroupWritable configuration option: when
3072 it is turned on, ControlSockets are group-writeable by the default
3073 group of the current user. Patch by Jérémy Bobbio; implements
3075 - Tor now refuses to create a ControlSocket in a directory that is
3076 world-readable (or group-readable if ControlSocketsGroupWritable
3077 is 0). This is necessary because some operating systems do not
3078 enforce permissions on an AF_UNIX sockets. Permissions on the
3079 directory holding the socket, however, seems to work everywhere.
3080 - Rate-limit a warning about failures to download v2 networkstatus
3081 documents. Resolves part of bug 1352.
3082 - Backport code from 0.2.3.x that allows directory authorities to
3083 clean their microdescriptor caches. Needed to resolve bug 2230.
3084 - When an HTTPS proxy reports "403 Forbidden", we now explain
3085 what it means rather than calling it an unexpected status code.
3086 Closes bug 2503. Patch from Michael Yakubovich.
3087 - Update to the May 1 2011 Maxmind GeoLite Country database.
3090 - Authorities now clean their microdesc cache periodically and when
3091 reading from disk initially, not only when adding new descriptors.
3092 This prevents a bug where we could lose microdescriptors. Bugfix
3093 on 0.2.2.6-alpha. Fixes bug 2230.
3094 - Do not crash when our configuration file becomes unreadable, for
3095 example due to a permissions change, between when we start up
3096 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3098 - Avoid a bug that would keep us from replacing a microdescriptor
3099 cache on Windows. (We would try to replace the file while still
3100 holding it open. That's fine on Unix, but Windows doesn't let us
3101 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
3102 - Add missing explanations for the authority-related torrc options
3103 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
3104 man page. Resolves issue 2379.
3105 - As an authority, do not upload our own vote or signature set to
3106 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
3107 it would get flagged as a duplicate. Resolves bug 3026.
3108 - Accept hidden service descriptors if we think we might be a hidden
3109 service directory, regardless of what our consensus says. This
3110 helps robustness, since clients and hidden services can sometimes
3111 have a more up-to-date view of the network consensus than we do,
3112 and if they think that the directory authorities list us a HSDir,
3113 we might actually be one. Related to bug 2732; bugfix on
3115 - When a controller changes TrackHostExits, remove mappings for
3116 hosts that should no longer have their exits tracked. Bugfix on
3118 - When a controller changes VirtualAddrNetwork, remove any mappings
3119 for hosts that were automapped to the old network. Bugfix on
3121 - When a controller changes one of the AutomapHosts* options, remove
3122 any mappings for hosts that should no longer be automapped. Bugfix
3124 - Do not reset the bridge descriptor download status every time we
3125 re-parse our configuration or get a configuration change. Fixes
3126 bug 3019; bugfix on 0.2.0.3-alpha.
3128 o Minor bugfixes (code cleanup):
3129 - When loading the microdesc journal, remember its current size.
3130 In 0.2.2, this helps prevent the microdesc journal from growing
3131 without limit on authorities (who are the only ones to use it in
3132 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
3133 Fix posted by "cypherpunks."
3134 - The microdesc journal is supposed to get rebuilt only if it is
3135 at least _half_ the length of the store, not _twice_ the length
3136 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
3137 - Fix a potential null-pointer dereference while computing a
3138 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
3140 - Avoid a possible null-pointer dereference when rebuilding the mdesc
3141 cache without actually having any descriptors to cache. Bugfix on
3142 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
3143 - If we fail to compute the identity digest of a v3 legacy keypair,
3144 warn, and don't use a buffer-full of junk instead. Bugfix on
3145 0.2.1.1-alpha; fixes bug 3106.
3146 - Resolve an untriggerable issue in smartlist_string_num_isin(),
3147 where if the function had ever in the future been used to check
3148 for the presence of a too-large number, it would have given an
3149 incorrect result. (Fortunately, we only used it for 16-bit
3150 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
3151 - Require that introduction point keys and onion handshake keys
3152 have a public exponent of 65537. Starts to fix bug 3207; bugfix
3156 - Caches no longer download and serve v2 networkstatus documents
3157 unless FetchV2Networkstatus flag is set: these documents haven't
3158 haven't been used by clients or relays since 0.2.0.x. Resolves
3162 Changes in version 0.2.3.1-alpha - 2011-05-05
3163 Tor 0.2.3.1-alpha adds some new experimental features, including support
3164 for an improved network IO backend, IOCP networking on Windows,
3165 microdescriptor caching, "fast-start" support for streams, and automatic
3166 home router configuration. There are also numerous internal improvements
3167 to try to make the code easier for developers to work with.
3169 This is the first alpha release in a new series, so expect there to be
3170 bugs. Users who would rather test out a more stable branch should
3171 stay with 0.2.2.x for now.
3174 - Tor can now optionally build with the "bufferevents" buffered IO
3175 backend provided by Libevent 2. To use this feature, make sure you
3176 have the latest possible version of Libevent, and pass the
3177 --enable-bufferevents flag to configure when building Tor from
3178 source. This feature will make our networking code more flexible,
3179 let us stack layers on each other, and let us use more efficient
3180 zero-copy transports where available.
3181 - As an experimental feature, Tor can use IOCP for networking on Windows.
3182 Once this code is tuned and optimized, it promises much better
3183 performance than the select-based backend we've used in the past. To
3184 try this feature, you must build Tor with Libevent 2, configure Tor
3185 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
3186 your torrc. There are known bugs here: only try this if you can help
3187 debug it as it breaks.
3188 - The EntryNodes option can now include country codes like {de} or IP
3189 addresses or network masks. Previously we had disallowed these options
3190 because we didn't have an efficient way to keep the list up to
3191 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
3192 - Exit nodes now accept and queue data on not-yet-connected streams.
3193 Previously, the client wasn't allowed to send data until the stream was
3194 connected, which slowed down all connections. This change will enable
3195 clients to perform a "fast-start" on streams and send data without
3196 having to wait for a confirmation that the stream has opened. (Patch
3197 from Ian Goldberg; implements the server side of Proposal 174.)
3198 - Tor now has initial support for automatic port mapping on the many
3199 home routers that support NAT-PMP or UPnP. (Not yet supported on
3200 Windows). To build the support code, you'll need to have libnatpnp
3201 library and/or the libminiupnpc library, and you'll need to enable the
3202 feature specifically by passing "--enable-upnp" and/or
3203 "--enable-natpnp" to configure. To turn it on, use the new
3204 PortForwarding option.
3205 - Caches now download, cache, and serve multiple "flavors" of the
3206 consensus, including a flavor that describes microdescriptors.
3207 - Caches now download, cache, and serve microdescriptors -- small
3208 summaries of router descriptors that are authenticated by all of the
3209 directory authorities. Once enough caches are running this code,
3210 clients will be able to save significant amounts of directory bandwidth
3211 by downloading microdescriptors instead of router descriptors.
3214 - Make logging resolution configurable with a new LogTimeGranularity
3215 option, and change the default from 1 millisecond to 1 second.
3216 Implements enhancement 1668.
3217 - We log which torrc file we're using on startup. Implements ticket
3219 - Ordinarily, Tor does not count traffic from private addresses (like
3220 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
3221 There is now a new option, CountPrivateBandwidth, to disable this
3222 behavior. Patch from Daniel Cagara.
3223 - New --enable-static-tor configure option for building Tor as
3224 statically as possible. Idea, general hackery and thoughts from
3225 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
3227 - If you set the NumCPUs option to 0, Tor will now try to detect how
3228 many CPUs you have. This is the new default behavior.
3229 - Turn on directory request statistics by default and include them in
3230 extra-info descriptors. Don't break if we have no GeoIP database.
3231 - Relays that set "ConnDirectionStatistics 1" write statistics on the
3232 bidirectional use of connections to disk every 24 hours.
3233 - Add a GeoIP file digest to the extra-info descriptor. Implements
3235 - The NodeFamily option -- which let you declare that you want to
3236 consider nodes to be part of a family whether they list themselves
3237 that way or not -- now allows IP address ranges and country codes.
3238 - Add a new 'Heartbeat' log message type to periodically log a message
3239 describing Tor's status at level Notice. This feature is meant for
3240 operators who log at notice, and want to make sure that their Tor
3241 server is still working. Implementation by George Kadianakis.
3243 o Minor bugfixes (on 0.2.2.25-alpha):
3244 - When loading the microdesc journal, remember its current size.
3245 In 0.2.2, this helps prevent the microdesc journal from growing
3246 without limit on authorities (who are the only ones to use it in
3247 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
3248 Fix posted by "cypherpunks."
3249 - The microdesc journal is supposed to get rebuilt only if it is
3250 at least _half_ the length of the store, not _twice_ the length
3251 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
3252 - If as an authority we fail to compute the identity digest of a v3
3253 legacy keypair, warn, and don't use a buffer-full of junk instead.
3254 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
3255 - Authorities now clean their microdesc cache periodically and when
3256 reading from disk initially, not only when adding new descriptors.
3257 This prevents a bug where we could lose microdescriptors. Bugfix
3260 o Minor features (controller):
3261 - Add a new SIGNAL event to the controller interface so that
3262 controllers can be notified when Tor handles a signal. Resolves
3263 issue 1955. Patch by John Brooks.
3264 - Add a new GETINFO option to get total bytes read and written. Patch
3265 from pipe, revised by atagar. Resolves ticket 2345.
3266 - Implement some GETINFO controller fields to provide information about
3267 the Tor process's pid, euid, username, and resource limits.
3270 - Our build system requires automake 1.6 or later to create the
3271 Makefile.in files. Previously, you could have used 1.4.
3272 This only affects developers and people building Tor from git;
3273 people who build Tor from the source distribution without changing
3274 the Makefile.am files should be fine.
3275 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
3276 so on. This is more robust against some of the failure modes
3277 associated with running the autotools pieces on their own.
3279 o Minor packaging issues:
3280 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
3281 already created. Patch from Andreas Stieger. Fixes bug 2573.
3283 o Code simplifications and refactoring:
3284 - A major revision to our internal node-selecting and listing logic.
3285 Tor already had at least two major ways to look at the question of
3286 "which Tor servers do we know about": a list of router descriptors,
3287 and a list of entries in the current consensus. With
3288 microdescriptors, we're adding a third. Having so many systems
3289 without an abstraction layer over them was hurting the codebase.
3290 Now, we have a new "node_t" abstraction that presents a consistent
3291 interface to a client's view of a Tor node, and holds (nearly) all
3292 of the mutable state formerly in routerinfo_t and routerstatus_t.
3293 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
3294 no longer link against Libevent: they never used it, but
3295 our library structure used to force them to link it.
3298 - Remove some old code to work around even older versions of Tor that
3299 used forked processes to handle DNS requests. Such versions of Tor
3300 are no longer in use as servers.
3302 o Documentation fixes:
3303 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
3304 - Add missing documentation for the authority-related torrc options
3305 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
3309 Changes in version 0.2.2.25-alpha - 2011-04-29
3310 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
3311 robust, routers no longer overreport their bandwidth, Win7 should crash
3312 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
3313 now prevents hidden service-related activity from being linkable. It
3314 provides more information to Vidalia so you can see if your bridge is
3315 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
3316 StrictNodes configuration options to make them more reliable, more
3317 understandable, and more regularly applied. If you use those options,
3318 please see the revised documentation for them in the manual page.
3321 - Relays were publishing grossly inflated bandwidth values because
3322 they were writing their state files wrong--now they write the
3323 correct value. Also, resume reading bandwidth history from the
3324 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
3325 - Improve hidden service robustness: When we find that we have
3326 extended a hidden service's introduction circuit to a relay not
3327 listed as an introduction point in the HS descriptor we currently
3328 have, retry with an introduction point from the current
3329 descriptor. Previously we would just give up. Fixes bugs 1024 and
3330 1930; bugfix on 0.2.0.10-alpha.
3331 - Clients now stop trying to use an exit node associated with a given
3332 destination by TrackHostExits if they fail to reach that exit node.
3333 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
3334 - Fix crash bug on platforms where gmtime and localtime can return
3335 NULL. Windows 7 users were running into this one. Fixes part of bug
3336 2077. Bugfix on all versions of Tor. Found by boboper.
3338 o Security and stability fixes:
3339 - Don't double-free a parsable, but invalid, microdescriptor, even if
3340 it is followed in the blob we're parsing by an unparsable
3341 microdescriptor. Fixes an issue reported in a comment on bug 2954.
3342 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
3343 - If the Nickname configuration option isn't given, Tor would pick a
3344 nickname based on the local hostname as the nickname for a relay.
3345 Because nicknames are not very important in today's Tor and the
3346 "Unnamed" nickname has been implemented, this is now problematic
3347 behavior: It leaks information about the hostname without being
3348 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
3349 introduced the Unnamed nickname. Reported by tagnaq.
3350 - Fix an uncommon assertion failure when running with DNSPort under
3351 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3352 - Avoid linkability based on cached hidden service descriptors: forget
3353 all hidden service descriptors cached as a client when processing a
3354 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3357 - Export GeoIP information on bridge usage to controllers even if we
3358 have not yet been running for 24 hours. Now Vidalia bridge operators
3359 can get more accurate and immediate feedback about their
3360 contributions to the network.
3362 o Major features and bugfixes (node selection):
3363 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
3364 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
3365 options. Previously, we had been ambiguous in describing what
3366 counted as an "exit" node, and what operations exactly "StrictNodes
3367 0" would permit. This created confusion when people saw nodes built
3368 through unexpected circuits, and made it hard to tell real bugs from
3369 surprises. Now the intended behavior is:
3370 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
3371 a node that delivers user traffic outside the Tor network.
3372 . "Entry", in the context of EntryNodes, means a node used as the
3373 first hop of a multihop circuit. It doesn't include direct
3374 connections to directory servers.
3375 . "ExcludeNodes" applies to all nodes.
3376 . "StrictNodes" changes the behavior of ExcludeNodes only. When
3377 StrictNodes is set, Tor should avoid all nodes listed in
3378 ExcludeNodes, even when it will make user requests fail. When
3379 StrictNodes is *not* set, then Tor should follow ExcludeNodes
3380 whenever it can, except when it must use an excluded node to
3381 perform self-tests, connect to a hidden service, provide a
3382 hidden service, fulfill a .exit request, upload directory
3383 information, or fetch directory information.
3384 Collectively, the changes to implement the behavior fix bug 1090.
3385 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
3386 a node is listed in both, it's treated as excluded.
3387 - ExcludeNodes now applies to directory nodes -- as a preference if
3388 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
3389 Don't exclude all the directory authorities and set StrictNodes to 1
3390 unless you really want your Tor to break.
3391 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
3392 - ExcludeExitNodes now overrides .exit requests.
3393 - We don't use bridges listed in ExcludeNodes.
3394 - When StrictNodes is 1:
3395 . We now apply ExcludeNodes to hidden service introduction points
3396 and to rendezvous points selected by hidden service users. This
3397 can make your hidden service less reliable: use it with caution!
3398 . If we have used ExcludeNodes on ourself, do not try relay
3399 reachability self-tests.
3400 . If we have excluded all the directory authorities, we will not
3401 even try to upload our descriptor if we're a relay.
3402 . Do not honor .exit requests to an excluded node.
3403 - Remove a misfeature that caused us to ignore the Fast/Stable flags
3404 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
3405 - When the set of permitted nodes changes, we now remove any mappings
3406 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
3408 - We never cannibalize a circuit that had excluded nodes on it, even
3409 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
3410 - Revert a change where we would be laxer about attaching streams to
3411 circuits than when building the circuits. This was meant to prevent
3412 a set of bugs where streams were never attachable, but our improved
3413 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
3414 - Keep track of how many times we launch a new circuit to handle a
3415 given stream. Too many launches could indicate an inconsistency
3416 between our "launch a circuit to handle this stream" logic and our
3417 "attach this stream to one of the available circuits" logic.
3418 - Improve log messages related to excluded nodes.
3421 - Fix a spurious warning when moving from a short month to a long
3422 month on relays with month-based BandwidthAccounting. Bugfix on
3423 0.2.2.17-alpha; fixes bug 3020.
3424 - When a client finds that an origin circuit has run out of 16-bit
3425 stream IDs, we now mark it as unusable for new streams. Previously,
3426 we would try to close the entire circuit. Bugfix on 0.0.6.
3427 - Add a forgotten cast that caused a compile warning on OS X 10.6.
3428 Bugfix on 0.2.2.24-alpha.
3429 - Be more careful about reporting the correct error from a failed
3430 connect() system call. Under some circumstances, it was possible to
3431 look at an incorrect value for errno when sending the end reason.
3432 Bugfix on 0.1.0.1-rc.
3433 - Correctly handle an "impossible" overflow cases in connection byte
3434 counting, where we write or read more than 4GB on an edge connection
3435 in a single second. Bugfix on 0.1.2.8-beta.
3436 - Correct the warning displayed when a rendezvous descriptor exceeds
3437 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3439 - Clients and hidden services now use HSDir-flagged relays for hidden
3440 service descriptor downloads and uploads even if the relays have no
3441 DirPort set and the client has disabled TunnelDirConns. This will
3442 eventually allow us to give the HSDir flag to relays with no
3443 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
3444 - Downgrade "no current certificates known for authority" message from
3445 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
3446 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
3447 2917. Bugfix on 0.1.1.1-alpha.
3448 - Only limit the lengths of single HS descriptors, even when multiple
3449 HS descriptors are published to an HSDir relay in a single POST
3450 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
3451 - Write the current time into the LastWritten line in our state file,
3452 rather than the time from the previous write attempt. Also, stop
3453 trying to use a time of -1 in our log statements. Fixes bug 3039;
3454 bugfix on 0.2.2.14-alpha.
3455 - Be more consistent in our treatment of file system paths. "~" should
3456 get expanded to the user's home directory in the Log config option.
3457 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
3458 feature for the -f and --DataDirectory options.
3461 - Make sure every relay writes a state file at least every 12 hours.
3462 Previously, a relay could go for weeks without writing its state
3463 file, and on a crash could lose its bandwidth history, capacity
3464 estimates, client country statistics, and so on. Addresses bug 3012.
3465 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
3466 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
3467 clients are already deprecated because of security bugs.
3468 - Don't allow v0 hidden service authorities to act as clients.
3469 Required by fix for bug 3000.
3470 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
3471 by fix for bug 3000.
3472 - Ensure that no empty [dirreq-](read|write)-history lines are added
3473 to an extrainfo document. Implements ticket 2497.
3475 o Code simplification and refactoring:
3476 - Remove workaround code to handle directory responses from servers
3477 that had bug 539 (they would send HTTP status 503 responses _and_
3478 send a body too). Since only server versions before
3479 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
3480 keep the workaround in place.
3481 - Remove the old 'fuzzy time' logic. It was supposed to be used for
3482 handling calculations where we have a known amount of clock skew and
3483 an allowed amount of unknown skew. But we only used it in three
3484 places, and we never adjusted the known/unknown skew values. This is
3485 still something we might want to do someday, but if we do, we'll
3486 want to do it differently.
3487 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3488 None of the cases where we did this before were wrong, but by making
3489 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3490 - Use GetTempDir to find the proper temporary directory location on
3491 Windows when generating temporary files for the unit tests. Patch by
3495 Changes in version 0.2.2.24-alpha - 2011-04-08
3496 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
3497 prevented Tor clients from effectively using "multihomed" bridges,
3498 that is, bridges that listen on multiple ports or IP addresses so users
3499 can continue to use some of their addresses even if others get blocked.
3502 - Fix a bug where bridge users who configure the non-canonical
3503 address of a bridge automatically switch to its canonical
3504 address. If a bridge listens at more than one address, it should be
3505 able to advertise those addresses independently and any non-blocked
3506 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
3508 - If you configured Tor to use bridge A, and then quit and
3509 configured Tor to use bridge B instead, it would happily continue
3510 to use bridge A if it's still reachable. While this behavior is
3511 a feature if your goal is connectivity, in some scenarios it's a
3512 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
3513 - Directory authorities now use data collected from their own
3514 uptime observations when choosing whether to assign the HSDir flag
3515 to relays, instead of trusting the uptime value the relay reports in
3516 its descriptor. This change helps prevent an attack where a small
3517 set of nodes with frequently-changing identity keys can blackhole
3518 a hidden service. (Only authorities need upgrade; others will be
3519 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
3522 - When we restart our relay, we might get a successful connection
3523 from the outside before we've started our reachability tests,
3524 triggering a warning: "ORPort found reachable, but I have no
3525 routerinfo yet. Failing to inform controller of success." This
3526 bug was harmless unless Tor is running under a controller
3527 like Vidalia, in which case the controller would never get a
3528 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3530 - Make directory authorities more accurate at recording when
3531 relays that have failed several reachability tests became
3532 unreachable, so we can provide more accuracy at assigning Stable,
3533 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
3534 - Fix an issue that prevented static linking of libevent on
3535 some platforms (notably Linux). Fixes bug 2698; bugfix on
3536 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
3537 the --with-static-libevent configure option).
3538 - We now ask the other side of a stream (the client or the exit)
3539 for more data on that stream when the amount of queued data on
3540 that stream dips low enough. Previously, we wouldn't ask the
3541 other side for more data until either it sent us more data (which
3542 it wasn't supposed to do if it had exhausted its window!) or we
3543 had completely flushed all our queued data. This flow control fix
3544 should improve throughput. Fixes bug 2756; bugfix on the earliest
3545 released versions of Tor (svn commit r152).
3546 - Avoid a double-mark-for-free warning when failing to attach a
3547 transparent proxy connection. (We thought we had fixed this in
3548 0.2.2.23-alpha, but it turns out our fix was checking the wrong
3549 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
3550 bug) and 0.2.2.23-alpha (the incorrect fix).
3551 - When warning about missing zlib development packages during compile,
3552 give the correct package names. Bugfix on 0.2.0.1-alpha.
3555 - Directory authorities now log the source of a rejected POSTed v3
3557 - Make compilation with clang possible when using
3558 --enable-gcc-warnings by removing two warning options that clang
3559 hasn't implemented yet and by fixing a few warnings. Implements
3561 - When expiring circuits, use microsecond timers rather than
3562 one-second timers. This can avoid an unpleasant situation where a
3563 circuit is launched near the end of one second and expired right
3564 near the beginning of the next, and prevent fluctuations in circuit
3566 - Use computed circuit-build timeouts to decide when to launch
3567 parallel introduction circuits for hidden services. (Previously,
3568 we would retry after 15 seconds.)
3569 - Update to the April 1 2011 Maxmind GeoLite Country database.
3572 - Create the /var/run/tor directory on startup on OpenSUSE if it is
3573 not already created. Patch from Andreas Stieger. Fixes bug 2573.
3575 o Documentation changes:
3576 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
3577 - Resolve all doxygen warnings except those for missing documentation.
3579 - Add doxygen documentation for more functions, fields, and types.
3582 Changes in version 0.2.2.23-alpha - 2011-03-08
3583 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
3584 they restart they don't lose their bandwidth capacity estimate. This
3585 release also fixes a diverse set of user-facing bugs, ranging from
3586 relays overrunning their rate limiting to clients falsely warning about
3587 clock skew to bridge descriptor leaks by our bridge directory authority.
3590 - Stop sending a CLOCK_SKEW controller status event whenever
3591 we fetch directory information from a relay that has a wrong clock.
3592 Instead, only inform the controller when it's a trusted authority
3593 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3594 the rest of bug 1074.
3595 - Fix an assert in parsing router descriptors containing IPv6
3596 addresses. This one took down the directory authorities when
3597 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3598 - Make the bridge directory authority refuse to answer directory
3599 requests for "all" descriptors. It used to include bridge
3600 descriptors in its answer, which was a major information leak.
3601 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3602 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3603 Tor would ignore their RelayBandwidthBurst setting,
3604 potentially using more bandwidth than expected. Bugfix on
3605 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3606 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3607 hidserv" in her torrc. The 'hidserv' argument never controlled
3608 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3611 - Relays now save observed peak bandwidth throughput rates to their
3612 state file (along with total usage, which was already saved)
3613 so that they can determine their correct estimated bandwidth on
3614 restart. Resolves bug 1863, where Tor relays would reset their
3615 estimated bandwidth to 0 after restarting.
3616 - Directory authorities now take changes in router IP address and
3617 ORPort into account when determining router stability. Previously,
3618 if a router changed its IP or ORPort, the authorities would not
3619 treat it as having any downtime for the purposes of stability
3620 calculation, whereas clients would experience downtime since the
3621 change could take a while to propagate to them. Resolves issue 1035.
3622 - Enable Address Space Layout Randomization (ASLR) and Data Execution
3623 Prevention (DEP) by default on Windows to make it harder for
3624 attackers to exploit vulnerabilities. Patch from John Brooks.
3626 o Minor bugfixes (on 0.2.1.x and earlier):
3627 - Fix a rare crash bug that could occur when a client was configured
3628 with a large number of bridges. Fixes bug 2629; bugfix on
3629 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3630 - Avoid a double mark-for-free warning when failing to attach a
3631 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
3633 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
3634 found by "cypherpunks". This bug was introduced before the first
3635 Tor release, in svn commit r110.
3636 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
3637 don't mention them in the manpage. Fixes bug 2450; issue
3638 spotted by keb and G-Lo.
3639 - Fix a bug in bandwidth history state parsing that could have been
3640 triggered if a future version of Tor ever changed the timing
3641 granularity at which bandwidth history is measured. Bugfix on
3643 - When a relay decides that its DNS is too broken for it to serve
3644 as an exit server, it advertised itself as a non-exit, but
3645 continued to act as an exit. This could create accidental
3646 partitioning opportunities for users. Instead, if a relay is
3647 going to advertise reject *:* as its exit policy, it should
3648 really act with exit policy "reject *:*". Fixes bug 2366.
3649 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
3650 - In the special case where you configure a public exit relay as your
3651 bridge, Tor would be willing to use that exit relay as the last
3652 hop in your circuit as well. Now we fail that circuit instead.
3653 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
3654 - Fix a bug with our locking implementation on Windows that couldn't
3655 correctly detect when a file was already locked. Fixes bug 2504,
3656 bugfix on 0.2.1.6-alpha.
3657 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
3658 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
3660 - Set target port in get_interface_address6() correctly. Bugfix
3661 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
3662 - Directory authorities are now more robust to hops back in time
3663 when calculating router stability. Previously, if a run of uptime
3664 or downtime appeared to be negative, the calculation could give
3665 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
3667 - Fix an assert that got triggered when using the TestingTorNetwork
3668 configuration option and then issuing a GETINFO config-text control
3669 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
3671 o Minor bugfixes (on 0.2.2.x):
3672 - Clients should not weight BadExit nodes as Exits in their node
3673 selection. Similarly, directory authorities should not count BadExit
3674 bandwidth as Exit bandwidth when computing bandwidth-weights.
3675 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
3676 - Correctly clear our dir_read/dir_write history when there is an
3677 error parsing any bw history value from the state file. Bugfix on
3679 - Resolve a bug in verifying signatures of directory objects
3680 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
3681 Fixes bug 2409. Found by "piebeer".
3682 - Bridge authorities no longer crash on SIGHUP when they try to
3683 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
3687 - Log less aggressively about circuit timeout changes, and improve
3688 some other circuit timeout messages. Resolves bug 2004.
3689 - Log a little more clearly about the times at which we're no longer
3690 accepting new connections. Resolves bug 2181.
3691 - Reject attempts at the client side to open connections to private
3692 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
3693 a randomly chosen exit node. Attempts to do so are always
3694 ill-defined, generally prevented by exit policies, and usually
3695 in error. This will also help to detect loops in transparent
3696 proxy configurations. You can disable this feature by setting
3697 "ClientRejectInternalAddresses 0" in your torrc.
3698 - Always treat failure to allocate an RSA key as an unrecoverable
3700 - Update to the March 1 2011 Maxmind GeoLite Country database.
3702 o Minor features (log subsystem):
3703 - Add documentation for configuring logging at different severities in
3704 different log domains. We've had this feature since 0.2.1.1-alpha,
3705 but for some reason it never made it into the manpage. Fixes
3707 - Make it simpler to specify "All log domains except for A and B".
3708 Previously you needed to say "[*,~A,~B]". Now you can just say
3710 - Add a "LogMessageDomains 1" option to include the domains of log
3711 messages along with the messages. Without this, there's no way
3712 to use log domains without reading the source or doing a lot
3715 o Packaging changes:
3716 - Stop shipping the Tor specs files and development proposal documents
3717 in the tarball. They are now in a separate git repository at
3718 git://git.torproject.org/torspec.git
3721 Changes in version 0.2.1.30 - 2011-02-23
3722 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
3723 change is a slight tweak to Tor's TLS handshake that makes relays
3724 and bridges that run this new version reachable from Iran again.
3725 We don't expect this tweak will win the arms race long-term, but it
3726 buys us time until we roll out a better solution.
3729 - Stop sending a CLOCK_SKEW controller status event whenever
3730 we fetch directory information from a relay that has a wrong clock.
3731 Instead, only inform the controller when it's a trusted authority
3732 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3733 the rest of bug 1074.
3734 - Fix a bounds-checking error that could allow an attacker to
3735 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3737 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3738 Tor would ignore their RelayBandwidthBurst setting,
3739 potentially using more bandwidth than expected. Bugfix on
3740 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3741 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3742 hidserv" in her torrc. The 'hidserv' argument never controlled
3743 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3746 - Adjust our TLS Diffie-Hellman parameters to match those used by
3748 - Update to the February 1 2011 Maxmind GeoLite Country database.
3751 - Check for and reject overly long directory certificates and
3752 directory tokens before they have a chance to hit any assertions.
3753 Bugfix on 0.2.1.28. Found by "doorss".
3754 - Bring the logic that gathers routerinfos and assesses the
3755 acceptability of circuits into line. This prevents a Tor OP from
3756 getting locked in a cycle of choosing its local OR as an exit for a
3757 path (due to a .exit request) and then rejecting the circuit because
3758 its OR is not listed yet. It also prevents Tor clients from using an
3759 OR running in the same instance as an exit (due to a .exit request)
3760 if the OR does not meet the same requirements expected of an OR
3761 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
3763 o Packaging changes:
3764 - Stop shipping the Tor specs files and development proposal documents
3765 in the tarball. They are now in a separate git repository at
3766 git://git.torproject.org/torspec.git
3767 - Do not include Git version tags as though they are SVN tags when
3768 generating a tarball from inside a repository that has switched
3769 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3772 Changes in version 0.2.2.22-alpha - 2011-01-25
3773 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
3774 main other change is a slight tweak to Tor's TLS handshake that makes
3775 relays and bridges that run this new version reachable from Iran again.
3776 We don't expect this tweak will win the arms race long-term, but it
3777 will buy us a bit more time until we roll out a better solution.
3780 - Fix a bounds-checking error that could allow an attacker to
3781 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3783 - Don't assert when changing from bridge to relay or vice versa
3784 via the controller. The assert happened because we didn't properly
3785 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
3786 bug 2433. Reported by bastik.
3789 - Adjust our TLS Diffie-Hellman parameters to match those used by
3791 - Provide a log message stating which geoip file we're parsing
3792 instead of just stating that we're parsing the geoip file.
3793 Implements ticket 2432.
3796 - Check for and reject overly long directory certificates and
3797 directory tokens before they have a chance to hit any assertions.
3798 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
3801 Changes in version 0.2.2.21-alpha - 2011-01-15
3802 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
3803 continues our recent code security audit work. The main fix resolves
3804 a remote heap overflow vulnerability that can allow remote code
3805 execution (CVE-2011-0427). Other fixes address a variety of assert
3806 and crash bugs, most of which we think are hard to exploit remotely.
3808 o Major bugfixes (security), also included in 0.2.1.29:
3809 - Fix a heap overflow bug where an adversary could cause heap
3810 corruption. This bug probably allows remote code execution
3811 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3813 - Prevent a denial-of-service attack by disallowing any
3814 zlib-compressed data whose compression factor is implausibly
3815 high. Fixes part of bug 2324; reported by "doorss".
3816 - Zero out a few more keys in memory before freeing them. Fixes
3817 bug 2384 and part of bug 2385. These key instances found by
3818 "cypherpunks", based on Andrew Case's report about being able
3819 to find sensitive data in Tor's memory space if you have enough
3820 permissions. Bugfix on 0.0.2pre9.
3822 o Major bugfixes (crashes), also included in 0.2.1.29:
3823 - Prevent calls to Libevent from inside Libevent log handlers.
3824 This had potential to cause a nasty set of crashes, especially
3825 if running Libevent with debug logging enabled, and running
3826 Tor with a controller watching for low-severity log messages.
3827 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3828 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3829 underflow errors there too. Fixes the other part of bug 2324.
3830 - Fix a bug where we would assert if we ever had a
3831 cached-descriptors.new file (or another file read directly into
3832 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3833 on 0.2.1.25. Found by doorss.
3834 - Fix some potential asserts and parsing issues with grossly
3835 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3838 o Minor bugfixes (other), also included in 0.2.1.29:
3839 - Fix a bug with handling misformed replies to reverse DNS lookup
3840 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3841 bug reported by doorss.
3842 - Fix compilation on mingw when a pthreads compatibility library
3843 has been installed. (We don't want to use it, so we shouldn't
3844 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3845 - Fix a bug where we would declare that we had run out of virtual
3846 addresses when the address space was only half-exhausted. Bugfix
3848 - Correctly handle the case where AutomapHostsOnResolve is set but
3849 no virtual addresses are available. Fixes bug 2328; bugfix on
3850 0.1.2.1-alpha. Bug found by doorss.
3851 - Correctly handle wrapping around when we run out of virtual
3852 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
3854 o Minor features, also included in 0.2.1.29:
3855 - Update to the January 1 2011 Maxmind GeoLite Country database.
3856 - Introduce output size checks on all of our decryption functions.
3858 o Build changes, also included in 0.2.1.29:
3859 - Tor does not build packages correctly with Automake 1.6 and earlier;
3860 added a check to Makefile.am to make sure that we're building with
3861 Automake 1.7 or later.
3862 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
3863 because we built it with a too-old version of automake. Thus that
3864 release broke ./configure --enable-openbsd-malloc, which is popular
3865 among really fast exit relays on Linux.
3867 o Major bugfixes, new in 0.2.2.21-alpha:
3868 - Prevent crash/heap corruption when the cbtnummodes consensus
3869 parameter is set to 0 or large values. Fixes bug 2317; bugfix
3872 o Major features, new in 0.2.2.21-alpha:
3873 - Introduce minimum/maximum values that clients will believe
3874 from the consensus. Now we'll have a better chance to avoid crashes
3875 or worse when a consensus param has a weird value.
3877 o Minor features, new in 0.2.2.21-alpha:
3878 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
3879 used on bridges, and it makes bridge scanning somewhat easier.
3880 - If writing the state file to disk fails, wait up to an hour before
3881 retrying again, rather than trying again each second. Fixes bug
3882 2346; bugfix on Tor 0.1.1.3-alpha.
3883 - Make Libevent log messages get delivered to controllers later,
3884 and not from inside the Libevent log handler. This prevents unsafe
3885 reentrant Libevent calls while still letting the log messages
3887 - Detect platforms that brokenly use a signed size_t, and refuse to
3888 build there. Found and analyzed by doorss and rransom.
3889 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
3892 o Minor bugfixes, new in 0.2.2.21-alpha:
3893 - Handle SOCKS messages longer than 128 bytes long correctly, rather
3894 than waiting forever for them to finish. Fixes bug 2330; bugfix
3895 on 0.2.0.16-alpha. Found by doorss.
3896 - Add assertions to check for overflow in arguments to
3897 base32_encode() and base32_decode(); fix a signed-unsigned
3898 comparison there too. These bugs are not actually reachable in Tor,
3899 but it's good to prevent future errors too. Found by doorss.
3900 - Correctly detect failures to create DNS requests when using Libevent
3901 versions before v2. (Before Libevent 2, we used our own evdns
3902 implementation. Its return values for Libevent's evdns_resolve_*()
3903 functions are not consistent with those from Libevent.) Fixes bug
3904 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
3906 o Documentation, new in 0.2.2.21-alpha:
3907 - Document the default socks host and port (127.0.0.1:9050) for
3911 Changes in version 0.2.1.29 - 2011-01-15
3912 Tor 0.2.1.29 continues our recent code security audit work. The main
3913 fix resolves a remote heap overflow vulnerability that can allow remote
3914 code execution. Other fixes address a variety of assert and crash bugs,
3915 most of which we think are hard to exploit remotely.
3917 o Major bugfixes (security):
3918 - Fix a heap overflow bug where an adversary could cause heap
3919 corruption. This bug probably allows remote code execution
3920 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3922 - Prevent a denial-of-service attack by disallowing any
3923 zlib-compressed data whose compression factor is implausibly
3924 high. Fixes part of bug 2324; reported by "doorss".
3925 - Zero out a few more keys in memory before freeing them. Fixes
3926 bug 2384 and part of bug 2385. These key instances found by
3927 "cypherpunks", based on Andrew Case's report about being able
3928 to find sensitive data in Tor's memory space if you have enough
3929 permissions. Bugfix on 0.0.2pre9.
3931 o Major bugfixes (crashes):
3932 - Prevent calls to Libevent from inside Libevent log handlers.
3933 This had potential to cause a nasty set of crashes, especially
3934 if running Libevent with debug logging enabled, and running
3935 Tor with a controller watching for low-severity log messages.
3936 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3937 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3938 underflow errors there too. Fixes the other part of bug 2324.
3939 - Fix a bug where we would assert if we ever had a
3940 cached-descriptors.new file (or another file read directly into
3941 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3942 on 0.2.1.25. Found by doorss.
3943 - Fix some potential asserts and parsing issues with grossly
3944 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3947 o Minor bugfixes (other):
3948 - Fix a bug with handling misformed replies to reverse DNS lookup
3949 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3950 bug reported by doorss.
3951 - Fix compilation on mingw when a pthreads compatibility library
3952 has been installed. (We don't want to use it, so we shouldn't
3953 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3954 - Fix a bug where we would declare that we had run out of virtual
3955 addresses when the address space was only half-exhausted. Bugfix
3957 - Correctly handle the case where AutomapHostsOnResolve is set but
3958 no virtual addresses are available. Fixes bug 2328; bugfix on
3959 0.1.2.1-alpha. Bug found by doorss.
3960 - Correctly handle wrapping around to when we run out of virtual
3961 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
3962 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
3963 because we built it with a too-old version of automake. Thus that
3964 release broke ./configure --enable-openbsd-malloc, which is popular
3965 among really fast exit relays on Linux.
3968 - Update to the January 1 2011 Maxmind GeoLite Country database.
3969 - Introduce output size checks on all of our decryption functions.
3972 - Tor does not build packages correctly with Automake 1.6 and earlier;
3973 added a check to Makefile.am to make sure that we're building with
3974 Automake 1.7 or later.
3977 Changes in version 0.2.2.20-alpha - 2010-12-17
3978 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
3979 exploitable bugs. We also fix a variety of other significant bugs,
3980 change the IP address for one of our directory authorities, and update
3981 the minimum version that Tor relays must run to join the network.
3984 - Fix a remotely exploitable bug that could be used to crash instances
3985 of Tor remotely by overflowing on the heap. Remote-code execution
3986 hasn't been confirmed, but can't be ruled out. Everyone should
3987 upgrade. Bugfix on the 0.1.1 series and later.
3988 - Fix a bug that could break accounting on 64-bit systems with large
3989 time_t values, making them hibernate for impossibly long intervals.
3990 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
3991 - Fix a logic error in directory_fetches_from_authorities() that
3992 would cause all _non_-exits refusing single-hop-like circuits
3993 to fetch from authorities, when we wanted to have _exits_ fetch
3994 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
3996 - Fix a stream fairness bug that would cause newer streams on a given
3997 circuit to get preference when reading bytes from the origin or
3998 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
3999 introduced before the first Tor release, in svn revision r152.
4001 o Directory authority changes:
4002 - Change IP address and ports for gabelmoo (v3 directory authority).
4005 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
4006 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
4007 - Fix an off-by-one error in calculating some controller command
4008 argument lengths. Fortunately, this mistake is harmless since
4009 the controller code does redundant NUL termination too. Found by
4010 boboper. Bugfix on 0.1.1.1-alpha.
4011 - Do not dereference NULL if a bridge fails to build its
4012 extra-info descriptor. Found by an anonymous commenter on
4013 Trac. Bugfix on 0.2.2.19-alpha.
4016 - Update to the December 1 2010 Maxmind GeoLite Country database.
4017 - Directory authorities now reject relays running any versions of
4018 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
4019 known bugs that keep RELAY_EARLY cells from working on rendezvous
4020 circuits. Followup to fix for bug 2081.
4021 - Directory authorities now reject relays running any version of Tor
4022 older than 0.2.0.26-rc. That version is the earliest that fetches
4023 current directory information correctly. Fixes bug 2156.
4024 - Report only the top 10 ports in exit-port stats in order not to
4025 exceed the maximum extra-info descriptor length of 50 KB. Implements
4029 Changes in version 0.2.1.28 - 2010-12-17
4030 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
4031 exploitable bugs. We also took this opportunity to change the IP address
4032 for one of our directory authorities, and to update the geoip database
4036 - Fix a remotely exploitable bug that could be used to crash instances
4037 of Tor remotely by overflowing on the heap. Remote-code execution
4038 hasn't been confirmed, but can't be ruled out. Everyone should
4039 upgrade. Bugfix on the 0.1.1 series and later.
4041 o Directory authority changes:
4042 - Change IP address and ports for gabelmoo (v3 directory authority).
4045 - Update to the December 1 2010 Maxmind GeoLite Country database.
4048 Changes in version 0.2.1.27 - 2010-11-23
4049 Yet another OpenSSL security patch broke its compatibility with Tor:
4050 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
4051 also took this opportunity to fix several crash bugs, integrate a new
4052 directory authority, and update the bundled GeoIP database.
4055 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
4056 No longer set the tlsext_host_name extension on server SSL objects;
4057 but continue to set it on client SSL objects. Our goal in setting
4058 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
4059 bugfix on 0.2.1.1-alpha.
4060 - Do not log messages to the controller while shrinking buffer
4061 freelists. Doing so would sometimes make the controller connection
4062 try to allocate a buffer chunk, which would mess up the internals
4063 of the freelist and cause an assertion failure. Fixes bug 1125;
4064 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
4065 - Learn our external IP address when we're a relay or bridge, even if
4066 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
4067 where we introduced bridge relays that don't need to publish to
4068 be useful. Fixes bug 2050.
4069 - Do even more to reject (and not just ignore) annotations on
4070 router descriptors received anywhere but from the cache. Previously
4071 we would ignore such annotations at first, but cache them to disk
4072 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
4073 - When you're using bridges and your network goes away and your
4074 bridges get marked as down, recover when you attempt a new socks
4075 connection (if the network is back), rather than waiting up to an
4076 hour to try fetching new descriptors for your bridges. Bugfix on
4077 0.2.0.3-alpha; fixes bug 1981.
4080 - Move to the November 2010 Maxmind GeoLite country db (rather
4081 than the June 2009 ip-to-country GeoIP db) for our statistics that
4082 count how many users relays are seeing from each country. Now we'll
4083 have more accurate data, especially for many African countries.
4085 o New directory authorities:
4086 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
4090 - Fix an assertion failure that could occur in directory caches or
4091 bridge users when using a very short voting interval on a testing
4092 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
4094 - Enforce multiplicity rules when parsing annotations. Bugfix on
4095 0.2.0.8-alpha. Found by piebeer.
4096 - Allow handshaking OR connections to take a full KeepalivePeriod
4097 seconds to handshake. Previously, we would close them after
4098 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4099 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4101 - When building with --enable-gcc-warnings on OpenBSD, disable
4102 warnings in system headers. This makes --enable-gcc-warnings
4103 pass on OpenBSD 4.8.
4106 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
4107 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
4108 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
4109 Servers can start sending this code when enough clients recognize
4110 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
4111 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4112 Patch from mingw-san.
4115 - Remove the old debian/ directory from the main Tor distribution.
4116 The official Tor-for-debian git repository lives at the URL
4117 https://git.torproject.org/debian/tor.git
4118 - Stop shipping the old doc/website/ directory in the tarball. We
4119 changed the website format in late 2010, and what we shipped in
4120 0.2.1.26 really wasn't that useful anyway.
4123 Changes in version 0.2.2.19-alpha - 2010-11-22
4124 Yet another OpenSSL security patch broke its compatibility with Tor:
4125 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
4128 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
4129 No longer set the tlsext_host_name extension on server SSL objects;
4130 but continue to set it on client SSL objects. Our goal in setting
4131 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
4132 bugfix on 0.2.1.1-alpha.
4135 - Try harder not to exceed the maximum length of 50 KB when writing
4136 statistics to extra-info descriptors. This bug was triggered by very
4137 fast relays reporting exit-port, entry, and dirreq statistics.
4138 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
4139 - Publish a router descriptor even if generating an extra-info
4140 descriptor fails. Previously we would not publish a router
4141 descriptor without an extra-info descriptor; this can cause fast
4142 exit relays collecting exit-port statistics to drop from the
4143 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
4146 Changes in version 0.2.2.18-alpha - 2010-11-16
4147 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
4148 us lately, makes unpublished bridge relays able to detect their IP
4149 address, and fixes a wide variety of other bugs to get us much closer
4150 to a stable release.
4153 - Do even more to reject (and not just ignore) annotations on
4154 router descriptors received anywhere but from the cache. Previously
4155 we would ignore such annotations at first, but cache them to disk
4156 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
4157 - Do not log messages to the controller while shrinking buffer
4158 freelists. Doing so would sometimes make the controller connection
4159 try to allocate a buffer chunk, which would mess up the internals
4160 of the freelist and cause an assertion failure. Fixes bug 1125;
4161 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
4162 - Learn our external IP address when we're a relay or bridge, even if
4163 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
4164 where we introduced bridge relays that don't need to publish to
4165 be useful. Fixes bug 2050.
4166 - Maintain separate TLS contexts and certificates for incoming and
4167 outgoing connections in bridge relays. Previously we would use the
4168 same TLS contexts and certs for incoming and outgoing connections.
4169 Bugfix on 0.2.0.3-alpha; addresses bug 988.
4170 - Maintain separate identity keys for incoming and outgoing TLS
4171 contexts in bridge relays. Previously we would use the same
4172 identity keys for incoming and outgoing TLS contexts. Bugfix on
4173 0.2.0.3-alpha; addresses the other half of bug 988.
4174 - Avoid an assertion failure when we as an authority receive a
4175 duplicate upload of a router descriptor that we already have,
4176 but which we previously considered an obsolete descriptor.
4177 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
4178 - Avoid a crash bug triggered by looking at a dangling pointer while
4179 setting the network status consensus. Found by Robert Ransom.
4180 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
4181 - Fix a logic error where servers that _didn't_ act as exits would
4182 try to keep their server lists more aggressively up to date than
4183 exits, when it was supposed to be the other way around. Bugfix
4186 o Minor bugfixes (on Tor 0.2.1.x and earlier):
4187 - When we're trying to guess whether we know our IP address as
4188 a relay, we would log various ways that we failed to guess
4189 our address, but never log that we ended up guessing it
4190 successfully. Now add a log line to help confused and anxious
4191 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
4192 - Bring the logic that gathers routerinfos and assesses the
4193 acceptability of circuits into line. This prevents a Tor OP from
4194 getting locked in a cycle of choosing its local OR as an exit for a
4195 path (due to a .exit request) and then rejecting the circuit because
4196 its OR is not listed yet. It also prevents Tor clients from using an
4197 OR running in the same instance as an exit (due to a .exit request)
4198 if the OR does not meet the same requirements expected of an OR
4199 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
4200 - Correctly describe errors that occur when generating a TLS object.
4201 Previously we would attribute them to a failure while generating a
4202 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
4204 - Enforce multiplicity rules when parsing annotations. Bugfix on
4205 0.2.0.8-alpha. Found by piebeer.
4206 - Fix warnings that newer versions of autoconf produced during
4207 ./autogen.sh. These warnings appear to be harmless in our case,
4208 but they were extremely verbose. Fixes bug 2020.
4210 o Minor bugfixes (on Tor 0.2.2.x):
4211 - Enable protection of small arrays whenever we build with gcc
4212 hardening features, not only when also building with warnings
4213 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
4216 - Make hidden services work better in private Tor networks by not
4217 requiring any uptime to join the hidden service descriptor
4218 DHT. Implements ticket 2088.
4219 - Rate-limit the "your application is giving Tor only an IP address"
4220 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
4221 - When AllowSingleHopExits is set, print a warning to explain to the
4222 relay operator why most clients are avoiding her relay.
4223 - Update to the November 1 2010 Maxmind GeoLite Country database.
4225 o Code simplifications and refactoring:
4226 - When we fixed bug 1038 we had to put in a restriction not to send
4227 RELAY_EARLY cells on rend circuits. This was necessary as long
4228 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
4229 active. Now remove this obsolete check. Resolves bug 2081.
4230 - Some options used different conventions for uppercasing of acronyms
4231 when comparing manpage and source. Fix those in favor of the
4232 manpage, as it makes sense to capitalize acronyms.
4233 - Remove the torrc.complete file. It hasn't been kept up to date
4234 and users will have better luck checking out the manpage.
4235 - Remove the obsolete "NoPublish" option; it has been flagged
4236 as obsolete and has produced a warning since 0.1.1.18-rc.
4237 - Remove everything related to building the expert bundle for OS X.
4238 It has confused many users, doesn't work right on OS X 10.6,
4239 and is hard to get rid of once installed. Resolves bug 1274.
4242 Changes in version 0.2.2.17-alpha - 2010-09-30
4243 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
4244 to use one-hop circuits (which can put the exit relays at higher risk,
4245 plus unbalance the network); fixes a big bug in bandwidth accounting
4246 for relays that want to limit their monthly bandwidth use; fixes a
4247 big pile of bugs in how clients tolerate temporary network failure;
4248 and makes our adaptive circuit build timeout feature (which improves
4249 client performance if your network is fast while not breaking things
4250 if your network is slow) better handle bad networks.
4253 - Exit relays now try harder to block exit attempts from unknown
4254 relays, to make it harder for people to use them as one-hop proxies
4255 a la tortunnel. Controlled by the refuseunknownexits consensus
4256 parameter (currently enabled), or you can override it on your
4257 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
4259 o Major bugfixes (0.2.1.x and earlier):
4260 - Fix a bug in bandwidth accounting that could make us use twice
4261 the intended bandwidth when our interval start changes due to
4262 daylight saving time. Now we tolerate skew in stored vs computed
4263 interval starts: if the start of the period changes by no more than
4264 50% of the period's duration, we remember bytes that we transferred
4265 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
4266 - Always search the Windows system directory for system DLLs, and
4267 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
4268 - When you're using bridges and your network goes away and your
4269 bridges get marked as down, recover when you attempt a new socks
4270 connection (if the network is back), rather than waiting up to an
4271 hour to try fetching new descriptors for your bridges. Bugfix on
4272 0.2.0.3-alpha; fixes bug 1981.
4274 o Major bugfixes (on 0.2.2.x):
4275 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
4277 - Fix a segfault that could happen when operating a bridge relay with
4278 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
4279 - The consensus bandwidth-weights (used by clients to choose fast
4280 relays) entered an unexpected edge case in September where
4281 Exits were much scarcer than Guards, resulting in bad weight
4282 recommendations. Now we compute them using new constraints that
4283 should succeed in all cases. Also alter directory authorities to
4284 not include the bandwidth-weights line if they fail to produce
4285 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
4286 - When weighting bridges during path selection, we used to trust
4287 the bandwidths they provided in their descriptor, only capping them
4288 at 10MB/s. This turned out to be problematic for two reasons:
4289 Bridges could claim to handle a lot more traffic then they
4290 actually would, thus making more clients pick them and have a
4291 pretty effective DoS attack. The other issue is that new bridges
4292 that might not have a good estimate for their bw capacity yet
4293 would not get used at all unless no other bridges are available
4294 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
4296 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
4297 - Ignore cannibalized circuits when recording circuit build times.
4298 This should provide for a minor performance improvement for hidden
4299 service users using 0.2.2.14-alpha, and should remove two spurious
4300 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
4301 - Simplify the logic that causes us to decide if the network is
4302 unavailable for purposes of recording circuit build times. If we
4303 receive no cells whatsoever for the entire duration of a circuit's
4304 full measured lifetime, the network is probably down. Also ignore
4305 one-hop directory fetching circuit timeouts when calculating our
4306 circuit build times. These changes should hopefully reduce the
4307 cases where we see ridiculous circuit build timeouts for people
4308 with spotty wireless connections. Fixes part of bug 1772; bugfix
4310 - Prevent the circuit build timeout from becoming larger than
4311 the maximum build time we have ever seen. Also, prevent the time
4312 period for measurement circuits from becoming larger than twice that
4313 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
4316 - When we run out of directory information such that we can't build
4317 circuits, but then get enough that we can build circuits, log when
4318 we actually construct a circuit, so the user has a better chance of
4319 knowing what's going on. Fixes bug 1362.
4320 - Be more generous with how much bandwidth we'd use up (with
4321 accounting enabled) before entering "soft hibernation". Previously,
4322 we'd refuse new connections and circuits once we'd used up 95% of
4323 our allotment. Now, we use up 95% of our allotment, AND make sure
4324 that we have no more than 500MB (or 3 hours of expected traffic,
4325 whichever is lower) remaining before we enter soft hibernation.
4326 - If we've configured EntryNodes and our network goes away and/or all
4327 our entrynodes get marked down, optimistically retry them all when
4328 a new socks application request appears. Fixes bug 1882.
4329 - Add some more defensive programming for architectures that can't
4330 handle unaligned integer accesses. We don't know of any actual bugs
4331 right now, but that's the best time to fix them. Fixes bug 1943.
4332 - Support line continuations in the torrc config file. If a line
4333 ends with a single backslash character, the newline is ignored, and
4334 the configuration value is treated as continuing on the next line.
4337 o Minor bugfixes (on 0.2.1.x and earlier):
4338 - For bandwidth accounting, calculate our expected bandwidth rate
4339 based on the time during which we were active and not in
4340 soft-hibernation during the last interval. Previously, we were
4341 also considering the time spent in soft-hibernation. If this
4342 was a long time, we would wind up underestimating our bandwidth
4343 by a lot, and skewing our wakeup time towards the start of the
4344 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
4346 o Minor bugfixes (on 0.2.2.x):
4347 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
4348 which were disabled by the circuit build timeout changes in
4349 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
4350 - Make sure we don't warn about missing bandwidth weights when
4351 choosing bridges or other relays not in the consensus. Bugfix on
4352 0.2.2.10-alpha; fixes bug 1805.
4353 - In our logs, do not double-report signatures from unrecognized
4354 authorities both as "from unknown authority" and "not
4355 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
4358 Changes in version 0.2.2.16-alpha - 2010-09-17
4359 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
4360 evident at exit relays), and also continues to resolve all the little
4361 bugs that have been filling up trac lately.
4363 o Major bugfixes (stream-level fairness):
4364 - When receiving a circuit-level SENDME for a blocked circuit, try
4365 to package cells fairly from all the streams that had previously
4366 been blocked on that circuit. Previously, we had started with the
4367 oldest stream, and allowed each stream to potentially exhaust
4368 the circuit's package window. This gave older streams on any
4369 given circuit priority over newer ones. Fixes bug 1937. Detected
4370 originally by Camilo Viecco. This bug was introduced before the
4371 first Tor release, in svn commit r152: it is the new winner of
4372 the longest-lived bug prize.
4373 - When the exit relay got a circuit-level sendme cell, it started
4374 reading on the exit streams, even if had 500 cells queued in the
4375 circuit queue already, so the circuit queue just grew and grew in
4376 some cases. We fix this by not re-enabling reading on receipt of a
4377 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
4378 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
4380 - Newly created streams were allowed to read cells onto circuits,
4381 even if the circuit's cell queue was blocked and waiting to drain.
4382 This created potential unfairness, as older streams would be
4383 blocked, but newer streams would gladly fill the queue completely.
4384 We add code to detect this situation and prevent any stream from
4385 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
4389 - Update to the September 1 2010 Maxmind GeoLite Country database.
4390 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
4391 not. This would lead to a cookie that is still not group readable.
4392 Closes bug 1843. Suggested by katmagic.
4393 - When logging a rate-limited warning, we now mention how many messages
4394 got suppressed since the last warning.
4395 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
4396 do individual connection-level rate limiting of clients. The torrc
4397 config options with the same names trump the consensus params, if
4398 both are present. Replaces the old "bwconnrate" and "bwconnburst"
4399 consensus params which were broken from 0.2.2.7-alpha through
4400 0.2.2.14-alpha. Closes bug 1947.
4401 - When a router changes IP address or port, authorities now launch
4402 a new reachability test for it. Implements ticket 1899.
4403 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
4404 2 no signature, 4 required" messages about consensus signatures
4405 easier to read, and make sure they get logged at the same severity
4406 as the messages explaining which keys are which. Fixes bug 1290.
4407 - Don't warn when we have a consensus that we can't verify because
4408 of missing certificates, unless those certificates are ones
4409 that we have been trying and failing to download. Fixes bug 1145.
4410 - If you configure your bridge with a known identity fingerprint,
4411 and the bridge authority is unreachable (as it is in at least
4412 one country now), fall back to directly requesting the descriptor
4413 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
4415 - When building with --enable-gcc-warnings on OpenBSD, disable
4416 warnings in system headers. This makes --enable-gcc-warnings
4417 pass on OpenBSD 4.8.
4419 o Minor bugfixes (on 0.2.1.x and earlier):
4420 - Authorities will now attempt to download consensuses if their
4421 own efforts to make a live consensus have failed. This change
4422 means authorities that restart will fetch a valid consensus, and
4423 it means authorities that didn't agree with the current consensus
4424 will still fetch and serve it if it has enough signatures. Bugfix
4425 on 0.2.0.9-alpha; fixes bug 1300.
4426 - Ensure DNS requests launched by "RESOLVE" commands from the
4427 controller respect the __LeaveStreamsUnattached setconf options. The
4428 same goes for requests launched via DNSPort or transparent
4429 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
4430 - Allow handshaking OR connections to take a full KeepalivePeriod
4431 seconds to handshake. Previously, we would close them after
4432 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4433 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4435 - Rate-limit "Failed to hand off onionskin" warnings.
4436 - Never relay a cell for a circuit we have already destroyed.
4437 Between marking a circuit as closeable and finally closing it,
4438 it may have been possible for a few queued cells to get relayed,
4439 even though they would have been immediately dropped by the next
4440 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
4441 - Never queue a cell for a circuit that's already been marked
4443 - Never vote for a server as "Running" if we have a descriptor for
4444 it claiming to be hibernating, and that descriptor was published
4445 more recently than our last contact with the server. Bugfix on
4446 0.2.0.3-alpha; fixes bug 911.
4447 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
4450 o Minor bugfixes (on 0.2.2.x):
4451 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
4452 down if a directory fetch fails and you've configured either
4453 bridges or EntryNodes. The intent was to mark the relay as down
4454 _unless_ you're using bridges or EntryNodes, since if you are
4455 then you could quickly run out of entry points.
4456 - Fix the Windows directory-listing code. A bug introduced in
4457 0.2.2.14-alpha could make Windows directory servers forget to load
4458 some of their cached v2 networkstatus files.
4459 - Really allow clients to use relays as bridges. Fixes bug 1776;
4460 bugfix on 0.2.2.15-alpha.
4461 - Demote a warn to info that happens when the CellStatistics option
4462 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
4463 Reported by Moritz Bartl.
4464 - On Windows, build correctly either with or without Unicode support.
4465 This is necessary so that Tor can support fringe platforms like
4466 Windows 98 (which has no Unicode), or Windows CE (which has no
4467 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
4470 - Add a unit test for cross-platform directory-listing code.
4473 Changes in version 0.2.2.15-alpha - 2010-08-18
4474 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
4475 fixes a variety of other bugs that were preventing performance
4476 experiments from moving forward, fixes several bothersome memory leaks,
4477 and generally closes a lot of smaller bugs that have been filling up
4481 - Stop assigning the HSDir flag to relays that disable their
4482 DirPort (and thus will refuse to answer directory requests). This
4483 fix should dramatically improve the reachability of hidden services:
4484 hidden services and hidden service clients pick six HSDir relays
4485 to store and retrieve the hidden service descriptor, and currently
4486 about half of the HSDir relays will refuse to work. Bugfix on
4487 0.2.0.10-alpha; fixes part of bug 1693.
4488 - The PerConnBWRate and Burst config options, along with the
4489 bwconnrate and bwconnburst consensus params, initialized each conn's
4490 token bucket values only when the connection is established. Now we
4491 update them if the config options change, and update them every time
4492 we get a new consensus. Otherwise we can encounter an ugly edge
4493 case where we initialize an OR conn to client-level bandwidth,
4494 but then later the relay joins the consensus and we leave it
4495 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
4496 - Fix a regression that caused Tor to rebind its ports if it receives
4497 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
4500 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
4501 should give us approximately 40-50% more Guard-flagged nodes,
4502 improving the anonymity the Tor network can provide and also
4503 decreasing the dropoff in throughput that relays experience when
4504 they first get the Guard flag.
4505 - Allow enabling or disabling the *Statistics config options while
4509 - Update to the August 1 2010 Maxmind GeoLite Country database.
4510 - Have the controller interface give a more useful message than
4511 "Internal Error" in response to failed GETINFO requests.
4512 - Warn when the same option is provided more than once in a torrc
4513 file, on the command line, or in a single SETCONF statement, and
4514 the option is one that only accepts a single line. Closes bug 1384.
4515 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4516 Patch from mingw-san.
4517 - Add support for the country code "{??}" in torrc options like
4518 ExcludeNodes, to indicate all routers of unknown country. Closes
4520 - Relays report the number of bytes spent on answering directory
4521 requests in extra-info descriptors similar to {read,write}-history.
4522 Implements enhancement 1790.
4524 o Minor bugfixes (on 0.2.1.x and earlier):
4525 - Complain if PublishServerDescriptor is given multiple arguments that
4526 include 0 or 1. This configuration will be rejected in the future.
4527 Bugfix on 0.2.0.1-alpha; closes bug 1107.
4528 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
4529 Bugfix on 0.2.0.13-alpha; closes bug 928.
4530 - Change "Application request when we're believed to be offline."
4531 notice to "Application request when we haven't used client
4532 functionality lately.", to clarify that it's not an error. Bugfix
4533 on 0.0.9.3; fixes bug 1222.
4534 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
4535 would return "551 Internal error" rather than "552 Unrecognized key
4536 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
4537 - Users can't configure a regular relay to be their bridge. It didn't
4538 work because when Tor fetched the bridge descriptor, it found
4539 that it already had it, and didn't realize that the purpose of the
4540 descriptor had changed. Now we replace routers with a purpose other
4541 than bridge with bridge descriptors when fetching them. Bugfix on
4542 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
4543 refetch the descriptor with router purpose 'general', disabling
4545 - Fix a rare bug in rend_fn unit tests: we would fail a test when
4546 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
4547 on 0.2.0.10-alpha; fixes bug 1808.
4548 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
4549 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
4550 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
4551 Servers can start sending this code when enough clients recognize
4552 it. Also update the spec to reflect this new reason. Bugfix on
4553 0.1.0.1-rc; fixes part of bug 1793.
4554 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
4555 when we switch from being a public relay to a bridge. Otherwise
4556 there will still be clients that see the relay in their consensus,
4557 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
4559 - Instead of giving an assertion failure on an internal mismatch
4560 on estimated freelist size, just log a BUG warning and try later.
4561 Mitigates but does not fix bug 1125.
4562 - Fix an assertion failure that could occur in caches or bridge users
4563 when using a very short voting interval on a testing network.
4564 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
4566 o Minor bugfixes (on 0.2.2.x):
4567 - Alter directory authorities to always consider Exit-flagged nodes
4568 as potential Guard nodes in their votes. The actual decision to
4569 use Exits as Guards is done in the consensus bandwidth weights.
4570 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
4571 - When the controller is reporting the purpose of circuits that
4572 didn't finish building before the circuit build timeout, it was
4573 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
4574 - Our libevent version parsing code couldn't handle versions like
4575 1.4.14b-stable and incorrectly warned the user about using an
4576 old and broken version of libevent. Treat 1.4.14b-stable like
4577 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
4579 - Don't use substitution references like $(VAR:MOD) when
4580 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
4581 '$(:x)' to 'x' rather than the empty string. This bites us in
4582 doc/ when configured with --disable-asciidoc. Bugfix on
4583 0.2.2.9-alpha; fixes bug 1773.
4584 - Remove a spurious hidden service server-side log notice about
4585 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
4587 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
4589 - Correctly report written bytes on linked connections. Found while
4590 implementing 1790. Bugfix on 0.2.2.4-alpha.
4591 - Fix three memory leaks: one in circuit_build_times_parse_state(),
4592 one in dirvote_add_signatures_to_pending_consensus(), and one every
4593 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
4594 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
4596 o Code simplifications and refactoring:
4597 - Take a first step towards making or.h smaller by splitting out
4598 function definitions for all source files in src/or/. Leave
4599 structures and defines in or.h for now.
4600 - Remove a bunch of unused function declarations as well as a block of
4601 #if 0'd code from the unit tests. Closes bug 1824.
4602 - New unit tests for exit-port history statistics; refactored exit
4603 statistics code to be more easily tested.
4604 - Remove the old debian/ directory from the main Tor distribution.
4605 The official Tor-for-debian git repository lives at the URL
4606 https://git.torproject.org/debian/tor.git
4609 Changes in version 0.2.2.14-alpha - 2010-07-12
4610 Tor 0.2.2.14-alpha greatly improves client-side handling of
4611 circuit build timeouts, which are used to estimate speed and improve
4612 performance. We also move to a much better GeoIP database, port Tor to
4613 Windows CE, introduce new compile flags that improve code security,
4614 add an eighth v3 directory authority, and address a lot of more
4618 - Tor directory authorities no longer crash when started with a
4619 cached-microdesc-consensus file in their data directory. Bugfix
4620 on 0.2.2.6-alpha; fixes bug 1532.
4621 - Treat an unset $HOME like an empty $HOME rather than triggering an
4622 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
4623 - Ignore negative and large circuit build timeout values that can
4624 happen during a suspend or hibernate. These values caused various
4625 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
4626 - Alter calculation of Pareto distribution parameter 'Xm' for
4627 Circuit Build Timeout learning to use the weighted average of the
4628 top N=3 modes (because we have three entry guards). Considering
4629 multiple modes should improve the timeout calculation in some cases,
4630 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
4632 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
4633 right censored distribution model. This approach improves over the
4634 synthetic timeout generation approach that was producing insanely
4635 high timeout values. Now we calculate build timeouts using truncated
4636 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
4637 - Do not close circuits that are under construction when they reach
4638 the circuit build timeout. Instead, leave them building (but do not
4639 use them) for up until the time corresponding to the 95th percentile
4640 on the Pareto CDF or 60 seconds, whichever is greater. This is done
4641 to provide better data for the new Pareto model. This percentile
4642 can be controlled by the consensus.
4645 - Move to the June 2010 Maxmind GeoLite country db (rather than the
4646 June 2009 ip-to-country GeoIP db) for our statistics that count
4647 how many users relays are seeing from each country. Now we have
4648 more accurate data for many African countries.
4649 - Port Tor to build and run correctly on Windows CE systems, using
4650 the wcecompat library. Contributed by Valerio Lupi.
4651 - New "--enable-gcc-hardening" ./configure flag (off by default)
4652 to turn on gcc compile time hardening options. It ensures
4653 that signed ints have defined behavior (-fwrapv), enables
4654 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
4655 with canaries (-fstack-protector-all), turns on ASLR protection if
4656 supported by the kernel (-fPIE, -pie), and adds additional security
4657 related warnings. Verified to work on Mac OS X and Debian Lenny.
4658 - New "--enable-linker-hardening" ./configure flag (off by default)
4659 to turn on ELF specific hardening features (relro, now). This does
4660 not work with Mac OS X or any other non-ELF binary format.
4662 o New directory authorities:
4663 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
4667 - New config option "WarnUnsafeSocks 0" disables the warning that
4668 occurs whenever Tor receives a socks handshake using a version of
4669 the socks protocol that can only provide an IP address (rather
4670 than a hostname). Setups that do DNS locally over Tor are fine,
4671 and we shouldn't spam the logs in that case.
4672 - Convert the HACKING file to asciidoc, and add a few new sections
4673 to it, explaining how we use Git, how we make changelogs, and
4674 what should go in a patch.
4675 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
4676 event, to give information on the current rate of circuit timeouts
4677 over our stored history.
4678 - Add ability to disable circuit build time learning via consensus
4679 parameter and via a LearnCircuitBuildTimeout config option. Also
4680 automatically disable circuit build time calculation if we are
4681 either a AuthoritativeDirectory, or if we fail to write our state
4682 file. Fixes bug 1296.
4683 - More gracefully handle corrupt state files, removing asserts
4684 in favor of saving a backup and resetting state.
4685 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
4689 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4691 - When a2x fails, mention that the user could disable manpages instead
4692 of trying to fix their asciidoc installation.
4693 - Where available, use Libevent 2.0's periodic timers so that our
4694 once-per-second cleanup code gets called even more closely to
4695 once per second than it would otherwise. Fixes bug 943.
4696 - If you run a bridge that listens on multiple IP addresses, and
4697 some user configures a bridge address that uses a different IP
4698 address than your bridge writes in its router descriptor, and the
4699 user doesn't specify an identity key, their Tor would discard the
4700 descriptor because "it isn't one of our configured bridges", and
4701 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
4702 Bugfix on 0.2.0.3-alpha.
4703 - If OpenSSL fails to make a duplicate of a private or public key, log
4704 an error message and try to exit cleanly. May help with debugging
4705 if bug 1209 ever remanifests.
4706 - Save a couple bytes in memory allocation every time we escape
4707 certain characters in a string. Patch from Florian Zumbiehl.
4708 - Make it explicit that we don't cannibalize one-hop circuits. This
4709 happens in the wild, but doesn't turn out to be a problem because
4710 we fortunately don't use those circuits. Many thanks to outofwords
4711 for the initial analysis and to swissknife who confirmed that
4712 two-hop circuits are actually created.
4713 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
4714 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
4715 - Eliminate a case where a circuit build time warning was displayed
4716 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
4719 Changes in version 0.2.1.26 - 2010-05-02
4720 Tor 0.2.1.26 addresses the recent connection and memory overload
4721 problems we've been seeing on relays, especially relays with their
4722 DirPort open. If your relay has been crashing, or you turned it off
4723 because it used too many resources, give this release a try.
4725 This release also fixes yet another instance of broken OpenSSL libraries
4726 that was causing some relays to drop out of the consensus.
4729 - Teach relays to defend themselves from connection overload. Relays
4730 now close idle circuits early if it looks like they were intended
4731 for directory fetches. Relays are also more aggressive about closing
4732 TLS connections that have no circuits on them. Such circuits are
4733 unlikely to be re-used, and tens of thousands of them were piling
4734 up at the fast relays, causing the relays to run out of sockets
4735 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4736 their directory fetches over TLS).
4737 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4738 that claim to be earlier than 0.9.8m, but which have in reality
4739 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4740 behavior. Possible fix for some cases of bug 1346.
4741 - Directory mirrors were fetching relay descriptors only from v2
4742 directory authorities, rather than v3 authorities like they should.
4743 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4744 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4747 - Finally get rid of the deprecated and now harmful notion of "clique
4748 mode", where directory authorities maintain TLS connections to
4752 - In the util/threads test, no longer free the test_mutex before all
4753 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4754 - The master thread could starve the worker threads quite badly on
4755 certain systems, causing them to run only partially in the allowed
4756 window. This resulted in test failures. Now the master thread sleeps
4757 occasionally for a few microseconds while the two worker-threads
4758 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4761 Changes in version 0.2.2.13-alpha - 2010-04-24
4762 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
4763 problems we've been seeing on relays, especially relays with their
4764 DirPort open. If your relay has been crashing, or you turned it off
4765 because it used too many resources, give this release a try.
4768 - Teach relays to defend themselves from connection overload. Relays
4769 now close idle circuits early if it looks like they were intended
4770 for directory fetches. Relays are also more aggressive about closing
4771 TLS connections that have no circuits on them. Such circuits are
4772 unlikely to be re-used, and tens of thousands of them were piling
4773 up at the fast relays, causing the relays to run out of sockets
4774 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4775 their directory fetches over TLS).
4778 - Finally get rid of the deprecated and now harmful notion of "clique
4779 mode", where directory authorities maintain TLS connections to
4781 - Directory authorities now do an immediate reachability check as soon
4782 as they hear about a new relay. This change should slightly reduce
4783 the time between setting up a relay and getting listed as running
4784 in the consensus. It should also improve the time between setting
4785 up a bridge and seeing use by bridge users.
4786 - Directory authorities no longer launch a TLS connection to every
4787 relay as they startup. Now that we have 2k+ descriptors cached,
4788 the resulting network hiccup is becoming a burden. Besides,
4789 authorities already avoid voting about Running for the first half
4790 hour of their uptime.
4793 Changes in version 0.2.2.12-alpha - 2010-04-20
4794 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
4795 handle and vote on descriptors. It was causing relays to drop out of
4799 - Many relays have been falling out of the consensus lately because
4800 not enough authorities know about their descriptor for them to get
4801 a majority of votes. When we deprecated the v2 directory protocol,
4802 we got rid of the only way that v3 authorities can hear from each
4803 other about other descriptors. Now authorities examine every v3
4804 vote for new descriptors, and fetch them from that authority. Bugfix
4806 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
4807 and a warning in or.h related to bandwidth_weight_rule_t that
4808 prevented clean compile on OS X. Fixes bug 1363; bugfix on
4810 - Fix a segfault on relays when DirReqStatistics is enabled
4811 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
4815 - Demote a confusing TLS warning that relay operators might get when
4816 someone tries to talk to their OrPort. It is neither the operator's
4817 fault nor can they do anything about it. Fixes bug 1364; bugfix
4821 Changes in version 0.2.2.11-alpha - 2010-04-15
4822 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
4823 libraries that was causing some relays to drop out of the consensus.
4826 - Directory mirrors were fetching relay descriptors only from v2
4827 directory authorities, rather than v3 authorities like they should.
4828 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4829 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4830 - Fix a parsing error that made every possible value of
4831 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
4832 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
4833 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
4834 about the option without breaking older ones.
4835 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4836 that claim to be earlier than 0.9.8m, but which have in reality
4837 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4838 behavior. Possible fix for some cases of bug 1346.
4841 - Experiment with a more aggressive approach to preventing clients
4842 from making one-hop exit streams. Exit relays who want to try it
4843 out can set "RefuseUnknownExits 1" in their torrc, and then look
4844 for "Attempt by %s to open a stream" log messages. Let us know
4846 - Add support for statically linking zlib by specifying
4847 --enable-static-zlib, to go with our support for statically linking
4848 openssl and libevent. Resolves bug 1358.
4851 - Fix a segfault that happens whenever a Tor client that is using
4852 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
4854 - When we cleaned up the contrib/tor-exit-notice.html file, we left
4855 out the first line. Fixes bug 1295.
4856 - When building the manpage from a tarball, we required asciidoc, but
4857 the asciidoc -> roff/html conversion was already done for the
4858 tarball. Make 'make' complain only when we need asciidoc (either
4859 because we're compiling directly from git, or because we altered
4860 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
4861 - When none of the directory authorities vote on any params, Tor
4862 segfaulted when trying to make the consensus from the votes. We
4863 didn't trigger the bug in practice, because authorities do include
4864 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
4867 - In the util/threads test, no longer free the test_mutex before all
4868 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4869 - The master thread could starve the worker threads quite badly on
4870 certain systems, causing them to run only partially in the allowed
4871 window. This resulted in test failures. Now the master thread sleeps
4872 occasionally for a few microseconds while the two worker-threads
4873 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4876 Changes in version 0.2.2.10-alpha - 2010-03-07
4877 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
4878 could prevent relays from guessing their IP address correctly. It also
4879 starts the groundwork for another client-side performance boost, since
4880 currently we're not making efficient use of relays that have both the
4881 Guard flag and the Exit flag.
4884 - Fix a regression from our patch for bug 1244 that caused relays
4885 to guess their IP address incorrectly if they didn't set Address
4886 in their torrc and/or their address fails to resolve. Bugfix on
4887 0.2.2.9-alpha; fixes bug 1269.
4889 o Major features (performance):
4890 - Directory authorities now compute consensus weightings that instruct
4891 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
4892 and no flag. Clients that use these weightings will distribute
4893 network load more evenly across these different relay types. The
4894 weightings are in the consensus so we can change them globally in
4895 the future. Extra thanks to "outofwords" for finding some nasty
4896 security bugs in the first implementation of this feature.
4898 o Minor features (performance):
4899 - Always perform router selections using weighted relay bandwidth,
4900 even if we don't need a high capacity circuit at the time. Non-fast
4901 circuits now only differ from fast ones in that they can use relays
4902 not marked with the Fast flag. This "feature" could turn out to
4903 be a horrible bug; we should investigate more before it goes into
4907 - Allow disabling building of the manpages. Skipping the manpage
4908 speeds up the build considerably.
4910 o Minor bugfixes (on 0.2.2.x):
4911 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
4912 Bugfix on 0.2.2.9-alpha.
4913 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
4914 config option. Bugfix on 0.2.2.7-alpha.
4915 - Ship the asciidoc-helper file in the tarball, so that people can
4916 build from source if they want to, and touching the .1.txt files
4917 doesn't break the build. Bugfix on 0.2.2.9-alpha.
4919 o Minor bugfixes (on 0.2.1.x or earlier):
4920 - Fix a dereference-then-NULL-check sequence when publishing
4921 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4923 - Fix another dereference-then-NULL-check sequence. Bugfix on
4924 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4925 - Make sure we treat potentially not NUL-terminated strings correctly.
4926 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4928 o Code simplifications and refactoring:
4929 - Fix some urls in the exit notice file and make it XHTML1.1 strict
4930 compliant. Based on a patch from Christian Kujau.
4931 - Don't use sed in asciidoc-helper anymore.
4932 - Make the build process fail if asciidoc cannot be found and
4933 building with asciidoc isn't disabled.
4936 Changes in version 0.2.2.9-alpha - 2010-02-22
4937 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
4938 location of a directory authority, and cleans up a bunch of small bugs.
4940 o Directory authority changes:
4941 - Change IP address for dannenberg (v3 directory authority), and
4942 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4943 service directory authority) from the list.
4946 - Make Tor work again on the latest OS X: when deciding whether to
4947 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4948 version at run-time, not compile time. We need to do this because
4949 Apple doesn't update its dev-tools headers when it updates its
4950 libraries in a security patch.
4951 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4952 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4953 a memory leak when requesting a hidden service descriptor we've
4954 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4956 - Authorities could be tricked into giving out the Exit flag to relays
4957 that didn't allow exiting to any ports. This bug could screw
4958 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
4959 1238. Bug discovered by Martin Kowalczyk.
4960 - When freeing a session key, zero it out completely. We only zeroed
4961 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4962 patched by ekir. Fixes bug 1254.
4965 - Fix static compilation by listing the openssl libraries in the right
4966 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
4967 - Resume handling .exit hostnames in a special way: originally we
4968 stripped the .exit part and used the requested exit relay. In
4969 0.2.2.1-alpha we stopped treating them in any special way, meaning
4970 if you use a .exit address then Tor will pass it on to the exit
4971 relay. Now we reject the .exit stream outright, since that behavior
4972 might be more expected by the user. Found and diagnosed by Scott
4973 Bennett and Downie on or-talk.
4974 - Don't spam the controller with events when we have no file
4975 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
4976 for log messages was already solved from bug 748.)
4977 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
4979 - Make the DNSPort option work with libevent 2.x. Don't alter the
4980 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
4981 - Emit a GUARD DROPPED controller event for a case we missed.
4982 - Make more fields in the controller protocol case-insensitive, since
4983 control-spec.txt said they were.
4984 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4985 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4986 - Fix a spec conformance issue: the network-status-version token
4987 must be the first token in a v3 consensus or vote. Discovered by
4988 parakeep. Bugfix on 0.2.0.3-alpha.
4990 o Code simplifications and refactoring:
4991 - Generate our manpage and HTML documentation using Asciidoc. This
4992 change should make it easier to maintain the documentation, and
4994 - Remove the --enable-iphone option. According to reports from Marco
4995 Bonetti, Tor builds fine without any special tweaking on recent
4996 iPhone SDK versions.
4997 - Removed some unnecessary files from the source distribution. The
4998 AUTHORS file has now been merged into the people page on the
4999 website. The roadmaps and design doc can now be found in the
5000 projects directory in svn.
5001 - Enabled various circuit build timeout constants to be controlled
5002 by consensus parameters. Also set better defaults for these
5003 parameters based on experimentation on broadband and simulated
5007 - The 'EXTENDCIRCUIT' control port command can now be used with
5008 a circ id of 0 and no path. This feature will cause Tor to build
5009 a new 'fast' general purpose circuit using its own path selection
5011 - Added a BUILDTIMEOUT_SET controller event to describe changes
5012 to the circuit build timeout.
5013 - Future-proof the controller protocol a bit by ignoring keyword
5014 arguments we do not recognize.
5015 - Expand homedirs passed to tor-checkkey. This should silence a
5016 coverity complaint about passing a user-supplied string into
5017 open() without checking it.
5020 Changes in version 0.2.1.25 - 2010-03-16
5021 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
5022 prevent relays from guessing their IP address correctly. It also fixes
5023 several minor potential security bugs.
5026 - Fix a regression from our patch for bug 1244 that caused relays
5027 to guess their IP address incorrectly if they didn't set Address
5028 in their torrc and/or their address fails to resolve. Bugfix on
5029 0.2.1.23; fixes bug 1269.
5030 - When freeing a session key, zero it out completely. We only zeroed
5031 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
5032 patched by ekir. Fixes bug 1254.
5035 - Fix a dereference-then-NULL-check sequence when publishing
5036 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
5038 - Fix another dereference-then-NULL-check sequence. Bugfix on
5039 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
5040 - Make sure we treat potentially not NUL-terminated strings correctly.
5041 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
5045 Changes in version 0.2.1.24 - 2010-02-21
5046 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
5050 - Work correctly out-of-the-box with even more vendor-patched versions
5051 of OpenSSL. In particular, make it so Debian and OS X don't need
5052 customized patches to run/build.
5055 Changes in version 0.2.1.23 - 2010-02-13
5056 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
5057 again on the latest OS X, and updates the location of a directory
5060 o Major bugfixes (performance):
5061 - We were selecting our guards uniformly at random, and then weighting
5062 which of our guards we'd use uniformly at random. This imbalance
5063 meant that Tor clients were severely limited on throughput (and
5064 probably latency too) by the first hop in their circuit. Now we
5065 select guards weighted by currently advertised bandwidth. We also
5066 automatically discard guards picked using the old algorithm. Fixes
5067 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
5070 - Make Tor work again on the latest OS X: when deciding whether to
5071 use strange flags to turn TLS renegotiation on, detect the OpenSSL
5072 version at run-time, not compile time. We need to do this because
5073 Apple doesn't update its dev-tools headers when it updates its
5074 libraries in a security patch.
5075 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
5076 that could happen on 32-bit platforms with 64-bit time_t. Also fix
5077 a memory leak when requesting a hidden service descriptor we've
5078 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
5081 o Directory authority changes:
5082 - Change IP address for dannenberg (v3 directory authority), and
5083 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
5084 service directory authority) from the list.
5087 - Refactor resolve_my_address() to not use gethostbyname() anymore.
5088 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
5091 - Avoid a mad rush at the beginning of each month when each client
5092 rotates half of its guards. Instead we spread the rotation out
5093 throughout the month, but we still avoid leaving a precise timestamp
5094 in the state file about when we first picked the guard. Improves
5095 over the behavior introduced in 0.1.2.17.
5098 Changes in version 0.2.2.8-alpha - 2010-01-26
5099 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
5100 causing bridge relays to disappear. If you're running a bridge,
5104 - Fix a memory corruption bug on bridges that occured during the
5105 inclusion of stats data in extra-info descriptors. Also fix the
5106 interface for geoip_get_bridge_stats* to prevent similar bugs in
5107 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
5108 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
5111 - Ignore OutboundBindAddress when connecting to localhost.
5112 Connections to localhost need to come _from_ localhost, or else
5113 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
5117 Changes in version 0.2.2.7-alpha - 2010-01-19
5118 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
5119 as laying the groundwork for further relay-side performance fixes. It
5120 also starts cleaning up client behavior with respect to the EntryNodes,
5121 ExitNodes, and StrictNodes config options.
5123 This release also rotates two directory authority keys, due to a
5124 security breach of some of the Torproject servers.
5126 o Directory authority changes:
5127 - Rotate keys (both v3 identity and relay identity) for moria1
5130 o Major features (performance):
5131 - We were selecting our guards uniformly at random, and then weighting
5132 which of our guards we'd use uniformly at random. This imbalance
5133 meant that Tor clients were severely limited on throughput (and
5134 probably latency too) by the first hop in their circuit. Now we
5135 select guards weighted by currently advertised bandwidth. We also
5136 automatically discard guards picked using the old algorithm. Fixes
5137 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
5138 - When choosing which cells to relay first, relays can now favor
5139 circuits that have been quiet recently, to provide lower latency
5140 for low-volume circuits. By default, relays enable or disable this
5141 feature based on a setting in the consensus. You can override
5142 this default by using the new "CircuitPriorityHalflife" config
5143 option. Design and code by Ian Goldberg, Can Tang, and Chris
5145 - Add separate per-conn write limiting to go with the per-conn read
5146 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
5147 but never per-conn write limits.
5148 - New consensus params "bwconnrate" and "bwconnburst" to let us
5149 rate-limit client connections as they enter the network. It's
5150 controlled in the consensus so we can turn it on and off for
5151 experiments. It's starting out off. Based on proposal 163.
5153 o Major features (relay selection options):
5154 - Switch to a StrictNodes config option, rather than the previous
5155 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
5156 "StrictExcludeNodes" option.
5157 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
5158 change during a config reload, mark and discard all our origin
5159 circuits. This fix should address edge cases where we change the
5160 config options and but then choose a circuit that we created before
5162 - If EntryNodes or ExitNodes are set, be more willing to use an
5163 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
5165 - Make EntryNodes config option much more aggressive even when
5166 StrictNodes is not set. Before it would prepend your requested
5167 entrynodes to your list of guard nodes, but feel free to use others
5168 after that. Now it chooses only from your EntryNodes if any of
5169 those are available, and only falls back to others if a) they're
5170 all down and b) StrictNodes is not set.
5171 - Now we refresh your entry guards from EntryNodes at each consensus
5172 fetch -- rather than just at startup and then they slowly rot as
5173 the network changes.
5176 - Stop bridge directory authorities from answering dbg-stability.txt
5177 directory queries, which would let people fetch a list of all
5178 bridge identities they track. Bugfix on 0.2.1.6-alpha.
5181 - Log a notice when we get a new control connection. Now it's easier
5182 for security-conscious users to recognize when a local application
5183 is knocking on their controller door. Suggested by bug 1196.
5184 - New config option "CircuitStreamTimeout" to override our internal
5185 timeout schedule for how many seconds until we detach a stream from
5186 a circuit and try a new circuit. If your network is particularly
5187 slow, you might want to set this to a number like 60.
5188 - New controller command "getinfo config-text". It returns the
5189 contents that Tor would write if you send it a SAVECONF command,
5190 so the controller can write the file to disk itself.
5191 - New options for SafeLogging to allow scrubbing only log messages
5192 generated while acting as a relay.
5193 - Ship the bridges spec file in the tarball too.
5194 - Avoid a mad rush at the beginning of each month when each client
5195 rotates half of its guards. Instead we spread the rotation out
5196 throughout the month, but we still avoid leaving a precise timestamp
5197 in the state file about when we first picked the guard. Improves
5198 over the behavior introduced in 0.1.2.17.
5200 o Minor bugfixes (compiling):
5201 - Fix compilation on OS X 10.3, which has a stub mlockall() but
5202 hides it. Bugfix on 0.2.2.6-alpha.
5203 - Fix compilation on Solaris by removing support for the
5204 DisableAllSwap config option. Solaris doesn't have an rlimit for
5205 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
5208 o Minor bugfixes (crashes):
5209 - Do not segfault when writing buffer stats when we haven't observed
5210 a single circuit to report about. Found by Fabian Lanze. Bugfix on
5212 - If we're in the pathological case where there's no exit bandwidth
5213 but there is non-exit bandwidth, or no guard bandwidth but there
5214 is non-guard bandwidth, don't crash during path selection. Bugfix
5216 - Fix an impossible-to-actually-trigger buffer overflow in relay
5217 descriptor generation. Bugfix on 0.1.0.15.
5219 o Minor bugfixes (privacy):
5220 - Fix an instance where a Tor directory mirror might accidentally
5221 log the IP address of a misbehaving Tor client. Bugfix on
5223 - Don't list Windows capabilities in relay descriptors. We never made
5224 use of them, and maybe it's a bad idea to publish them. Bugfix
5227 o Minor bugfixes (other):
5228 - Resolve an edge case in path weighting that could make us misweight
5229 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
5230 - Fix statistics on client numbers by country as seen by bridges that
5231 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
5232 intervals instead of variable 12-to-48-hour intervals.
5233 - After we free an internal connection structure, overwrite it
5234 with a different memory value than we use for overwriting a freed
5235 internal circuit structure. Should help with debugging. Suggested
5237 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
5241 - Remove the HSAuthorityRecordStats option that version 0 hidden
5242 service authorities could have used to track statistics of overall
5243 hidden service usage.
5246 Changes in version 0.2.1.22 - 2010-01-19
5247 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
5248 authorities -- it would tell you its whole history of bridge descriptors
5249 if you make the right directory request. This stable update also
5250 rotates two of the seven v3 directory authority keys and locations.
5252 o Directory authority changes:
5253 - Rotate keys (both v3 identity and relay identity) for moria1
5257 - Stop bridge directory authorities from answering dbg-stability.txt
5258 directory queries, which would let people fetch a list of all
5259 bridge identities they track. Bugfix on 0.2.1.6-alpha.
5262 Changes in version 0.2.1.21 - 2009-12-21
5263 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
5264 library. If you use Tor on Linux / Unix and you're getting SSL
5265 renegotiation errors, upgrading should help. We also recommend an
5266 upgrade if you're an exit relay.
5269 - Work around a security feature in OpenSSL 0.9.8l that prevents our
5270 handshake from working unless we explicitly tell OpenSSL that we
5271 are using SSL renegotiation safely. We are, of course, but OpenSSL
5272 0.9.8l won't work unless we say we are.
5273 - Avoid crashing if the client is trying to upload many bytes and the
5274 circuit gets torn down at the same time, or if the flip side
5275 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
5278 - Do not refuse to learn about authority certs and v2 networkstatus
5279 documents that are older than the latest consensus. This bug might
5280 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
5281 Spotted and fixed by xmux.
5282 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
5283 trigger platform-specific option misparsing case found by Coverity
5285 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
5286 trigger assert. Fixes bug 1173.
5289 Changes in version 0.2.2.6-alpha - 2009-11-19
5290 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
5291 support for the new lower-footprint "microdescriptor" directory design,
5292 future-proofing our consensus format against new hash functions or
5293 other changes, and an Android port. It also makes Tor compatible with
5294 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
5297 - Directory authorities can now create, vote on, and serve multiple
5298 parallel formats of directory data as part of their voting process.
5299 Partially implements Proposal 162: "Publish the consensus in
5301 - Directory authorities can now agree on and publish small summaries
5302 of router information that clients can use in place of regular
5303 server descriptors. This transition will eventually allow clients
5304 to use far less bandwidth for downloading information about the
5305 network. Begins the implementation of Proposal 158: "Clients
5306 download consensus + microdescriptors".
5307 - The directory voting system is now extensible to use multiple hash
5308 algorithms for signatures and resource selection. Newer formats
5309 are signed with SHA256, with a possibility for moving to a better
5310 hash algorithm in the future.
5311 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
5312 current and future memory pages via mlockall(). On supported
5313 platforms (modern Linux and probably BSD but not Windows or OS X),
5314 this should effectively disable any and all attempts to page out
5315 memory. This option requires that you start your Tor as root --
5316 if you use DisableAllSwap, please consider using the User option
5317 to properly reduce the privileges of your Tor.
5318 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
5319 to help Tor build correctly for Android phones.
5322 - Work around a security feature in OpenSSL 0.9.8l that prevents our
5323 handshake from working unless we explicitly tell OpenSSL that we
5324 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
5325 won't work unless we say we are.
5328 - Fix a crash bug when trying to initialize the evdns module in
5329 Libevent 2. Bugfix on 0.2.1.16-rc.
5330 - Stop logging at severity 'warn' when some other Tor client tries
5331 to establish a circuit with us using weak DH keys. It's a protocol
5332 violation, but that doesn't mean ordinary users need to hear about
5333 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
5334 - Do not refuse to learn about authority certs and v2 networkstatus
5335 documents that are older than the latest consensus. This bug might
5336 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
5337 Spotted and fixed by xmux.
5338 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
5339 - If all authorities restart at once right before a consensus vote,
5340 nobody will vote about "Running", and clients will get a consensus
5341 with no usable relays. Instead, authorities refuse to build a
5342 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
5343 - If your relay can't keep up with the number of incoming create
5344 cells, it would log one warning per failure into your logs. Limit
5345 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
5346 - Bridges now use "reject *:*" as their default exit policy. Bugfix
5347 on 0.2.0.3-alpha; fixes bug 1113.
5348 - Fix a memory leak on directory authorities during voting that was
5349 introduced in 0.2.2.1-alpha. Found via valgrind.
5352 Changes in version 0.2.1.20 - 2009-10-15
5353 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
5354 services at once, prepares for more performance improvements, and
5355 fixes a bunch of smaller bugs.
5357 The Windows and OS X bundles also include a more recent Vidalia,
5358 and switch from Privoxy to Polipo.
5360 The OS X installers are now drag and drop. It's best to un-install
5361 Tor/Vidalia and then install this new bundle, rather than upgrade. If
5362 you want to upgrade, you'll need to update the paths for Tor and Polipo
5363 in the Vidalia Settings window.
5366 - Send circuit or stream sendme cells when our window has decreased
5367 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5368 by Karsten when testing the "reduce circuit window" performance
5369 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5370 before the release of Tor 0.0.0. This is the new winner of the
5372 - Fix a remotely triggerable memory leak when a consensus document
5373 contains more than one signature from the same voter. Bugfix on
5375 - Avoid segfault in rare cases when finishing an introduction circuit
5376 as a client and finding out that we don't have an introduction key
5377 for it. Fixes bug 1073. Reported by Aaron Swartz.
5380 - Tor now reads the "circwindow" parameter out of the consensus,
5381 and uses that value for its circuit package window rather than the
5382 default of 1000 cells. Begins the implementation of proposal 168.
5384 o New directory authorities:
5385 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5387 - Move moria1 and tonga to alternate IP addresses.
5390 - Fix a signed/unsigned compile warning in 0.2.1.19.
5391 - Fix possible segmentation fault on directory authorities. Bugfix on
5393 - Fix an extremely rare infinite recursion bug that could occur if
5394 we tried to log a message after shutting down the log subsystem.
5395 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5396 - Fix an obscure bug where hidden services on 64-bit big-endian
5397 systems might mis-read the timestamp in v3 introduce cells, and
5398 refuse to connect back to the client. Discovered by "rotor".
5399 Bugfix on 0.2.1.6-alpha.
5400 - We were triggering a CLOCK_SKEW controller status event whenever
5401 we connect via the v2 connection protocol to any relay that has
5402 a wrong clock. Instead, we should only inform the controller when
5403 it's a trusted authority that claims our clock is wrong. Bugfix
5404 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5405 - We were telling the controller about CHECKING_REACHABILITY and
5406 REACHABILITY_FAILED status events whenever we launch a testing
5407 circuit or notice that one has failed. Instead, only tell the
5408 controller when we want to inform the user of overall success or
5409 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5411 - Don't warn when we're using a circuit that ends with a node
5412 excluded in ExcludeExitNodes, but the circuit is not used to access
5413 the outside world. This should help fix bug 1090. Bugfix on
5415 - Work around a small memory leak in some versions of OpenSSL that
5416 stopped the memory used by the hostname TLS extension from being
5420 - Add a "getinfo status/accepted-server-descriptor" controller
5421 command, which is the recommended way for controllers to learn
5422 whether our server descriptor has been successfully received by at
5423 least on directory authority. Un-recommend good-server-descriptor
5424 getinfo and status events until we have a better design for them.
5427 Changes in version 0.2.2.5-alpha - 2009-10-11
5428 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
5431 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
5433 o Directory authorities:
5434 - Temporarily (just for this release) move dizum to an alternate
5438 Changes in version 0.2.2.4-alpha - 2009-10-10
5439 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
5440 introduces a new unit test framework, shifts directry authority
5441 addresses around to reduce the impact from recent blocking events,
5442 and fixes a few smaller bugs.
5445 - Fix several more asserts in the circuit_build_times code, for
5446 example one that causes Tor to fail to start once we have
5447 accumulated 5000 build times in the state file. Bugfixes on
5448 0.2.2.2-alpha; fixes bug 1108.
5450 o New directory authorities:
5451 - Move moria1 and Tonga to alternate IP addresses.
5454 - Log SSL state transitions at debug level during handshake, and
5455 include SSL states in error messages. This may help debug future
5456 SSL handshake issues.
5457 - Add a new "Handshake" log domain for activities that happen
5458 during the TLS handshake.
5459 - Revert to the "June 3 2009" ip-to-country file. The September one
5460 seems to have removed most US IP addresses.
5461 - Directory authorities now reject Tor relays with versions less than
5462 0.1.2.14. This step cuts out four relays from the current network,
5463 none of which are very big.
5466 - Fix a couple of smaller issues with gathering statistics. Bugfixes
5468 - Fix two memory leaks in the error case of
5469 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
5470 - Don't count one-hop circuits when we're estimating how long it
5471 takes circuits to build on average. Otherwise we'll set our circuit
5472 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
5473 - Directory authorities no longer change their opinion of, or vote on,
5474 whether a router is Running, unless they have themselves been
5475 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
5478 o Code simplifications and refactoring:
5479 - Revise our unit tests to use the "tinytest" framework, so we
5480 can run tests in their own processes, have smarter setup/teardown
5481 code, and so on. The unit test code has moved to its own
5482 subdirectory, and has been split into multiple modules.
5485 Changes in version 0.2.2.3-alpha - 2009-09-23
5486 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
5489 - Fix an overzealous assert in our new circuit build timeout code.
5490 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
5493 - If the networkstatus consensus tells us that we should use a
5494 negative circuit package window, ignore it. Otherwise we'll
5495 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
5498 Changes in version 0.2.2.2-alpha - 2009-09-21
5499 Tor 0.2.2.2-alpha introduces our latest performance improvement for
5500 clients: Tor tracks the average time it takes to build a circuit, and
5501 avoids using circuits that take too long to build. For fast connections,
5502 this feature can cut your expected latency in half. For slow or flaky
5503 connections, it could ruin your Tor experience. Let us know if it does!
5506 - Tor now tracks how long it takes to build client-side circuits
5507 over time, and adapts its timeout to local network performance.
5508 Since a circuit that takes a long time to build will also provide
5509 bad performance, we get significant latency improvements by
5510 discarding the slowest 20% of circuits. Specifically, Tor creates
5511 circuits more aggressively than usual until it has enough data
5512 points for a good timeout estimate. Implements proposal 151.
5513 We are especially looking for reports (good and bad) from users with
5514 both EDGE and broadband connections that can move from broadband
5515 to EDGE and find out if the build-time data in the .tor/state gets
5516 reset without loss of Tor usability. You should also see a notice
5517 log message telling you that Tor has reset its timeout.
5518 - Directory authorities can now vote on arbitary integer values as
5519 part of the consensus process. This is designed to help set
5520 network-wide parameters. Implements proposal 167.
5521 - Tor now reads the "circwindow" parameter out of the consensus,
5522 and uses that value for its circuit package window rather than the
5523 default of 1000 cells. Begins the implementation of proposal 168.
5526 - Fix a remotely triggerable memory leak when a consensus document
5527 contains more than one signature from the same voter. Bugfix on
5531 - Fix an extremely rare infinite recursion bug that could occur if
5532 we tried to log a message after shutting down the log subsystem.
5533 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5534 - Fix parsing for memory or time units given without a space between
5535 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
5536 - A networkstatus vote must contain exactly one signature. Spec
5537 conformance issue. Bugfix on 0.2.0.3-alpha.
5538 - Fix an obscure bug where hidden services on 64-bit big-endian
5539 systems might mis-read the timestamp in v3 introduce cells, and
5540 refuse to connect back to the client. Discovered by "rotor".
5541 Bugfix on 0.2.1.6-alpha.
5542 - We were triggering a CLOCK_SKEW controller status event whenever
5543 we connect via the v2 connection protocol to any relay that has
5544 a wrong clock. Instead, we should only inform the controller when
5545 it's a trusted authority that claims our clock is wrong. Bugfix
5546 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5547 - We were telling the controller about CHECKING_REACHABILITY and
5548 REACHABILITY_FAILED status events whenever we launch a testing
5549 circuit or notice that one has failed. Instead, only tell the
5550 controller when we want to inform the user of overall success or
5551 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5553 - Don't warn when we're using a circuit that ends with a node
5554 excluded in ExcludeExitNodes, but the circuit is not used to access
5555 the outside world. This should help fix bug 1090, but more problems
5556 remain. Bugfix on 0.2.1.6-alpha.
5557 - Work around a small memory leak in some versions of OpenSSL that
5558 stopped the memory used by the hostname TLS extension from being
5560 - Make our 'torify' script more portable; if we have only one of
5561 'torsocks' or 'tsocks' installed, don't complain to the user;
5562 and explain our warning about tsocks better.
5565 - Add a "getinfo status/accepted-server-descriptor" controller
5566 command, which is the recommended way for controllers to learn
5567 whether our server descriptor has been successfully received by at
5568 least on directory authority. Un-recommend good-server-descriptor
5569 getinfo and status events until we have a better design for them.
5570 - Update to the "September 4 2009" ip-to-country file.
5573 Changes in version 0.2.2.1-alpha - 2009-08-26
5574 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
5575 Tor clients to bootstrap on networks where only port 80 is reachable,
5576 makes it more straightforward to support hardware crypto accelerators,
5577 and starts the groundwork for gathering stats safely at relays.
5580 - Start the process of disabling ".exit" address notation, since it
5581 can be used for a variety of esoteric application-level attacks
5582 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
5585 o New directory authorities:
5586 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5590 - New AccelName and AccelDir options add support for dynamic OpenSSL
5591 hardware crypto acceleration engines.
5592 - Tor now supports tunneling all of its outgoing connections over
5593 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
5594 configuration options. Code by Christopher Davis.
5597 - Send circuit or stream sendme cells when our window has decreased
5598 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5599 by Karsten when testing the "reduce circuit window" performance
5600 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5601 before the release of Tor 0.0.0. This is the new winner of the
5604 o New options for gathering stats safely:
5605 - Directory mirrors that set "DirReqStatistics 1" write statistics
5606 about directory requests to disk every 24 hours. As compared to the
5607 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
5608 1) stats are written to disk exactly every 24 hours; 2) estimated
5609 shares of v2 and v3 requests are determined as mean values, not at
5610 the end of a measurement period; 3) unresolved requests are listed
5611 with country code '??'; 4) directories also measure download times.
5612 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
5613 number of exit streams and transferred bytes per port to disk every
5615 - Relays that set "CellStatistics 1" write statistics on how long
5616 cells spend in their circuit queues to disk every 24 hours.
5617 - Entry nodes that set "EntryStatistics 1" write statistics on the
5618 rough number and origins of connecting clients to disk every 24
5620 - Relays that write any of the above statistics to disk and set
5621 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
5622 their extra-info documents.
5625 - New --digests command-line switch to output the digests of the
5626 source files Tor was built with.
5627 - The "torify" script now uses torsocks where available.
5628 - The memarea code now uses a sentinel value at the end of each area
5629 to make sure nothing writes beyond the end of an area. This might
5630 help debug some conceivable causes of bug 930.
5631 - Time and memory units in the configuration file can now be set to
5632 fractional units. For example, "2.5 GB" is now a valid value for
5634 - Certain Tor clients (such as those behind check.torproject.org) may
5635 want to fetch the consensus in an extra early manner. To enable this
5636 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
5637 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
5638 as only certain clients who must have this information sooner should
5640 - Instead of adding the svn revision to the Tor version string, report
5641 the git commit (when we're building from a git checkout).
5644 - If any of the v3 certs we download are unparseable, we should
5645 actually notice the failure so we don't retry indefinitely. Bugfix
5646 on 0.2.0.x; reported by "rotator".
5647 - If the cached cert file is unparseable, warn but don't exit.
5648 - Fix possible segmentation fault on directory authorities. Bugfix on
5650 - When Tor fails to parse a descriptor of any kind, dump it to disk.
5651 Might help diagnosing bug 1051.
5653 o Deprecated and removed features:
5654 - The controller no longer accepts the old obsolete "addr-mappings/"
5655 or "unregistered-servers-" GETINFO values.
5656 - Hidden services no longer publish version 0 descriptors, and clients
5657 do not request or use version 0 descriptors. However, the old hidden
5658 service authorities still accept and serve version 0 descriptors
5659 when contacted by older hidden services/clients.
5660 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
5661 always on; using them is necessary for correct forward-compatible
5663 - Remove support for .noconnect style addresses. Nobody was using
5664 them, and they provided another avenue for detecting Tor users
5665 via application-level web tricks.
5667 o Packaging changes:
5668 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
5669 installer bundles. See
5670 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
5671 for details of what's new in Vidalia 0.2.3.
5672 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
5673 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
5674 configuration file, rather than the old Privoxy.
5675 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
5676 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
5677 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
5678 better compatibility with OS X 10.6, aka Snow Leopard.
5679 - OS X Vidalia Bundle: The multi-package installer is now replaced
5680 by a simple drag and drop to the /Applications folder. This change
5681 occurred with the upgrade to Vidalia 0.2.3.
5684 Changes in version 0.2.1.19 - 2009-07-28
5685 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
5686 services on Tor 0.2.1.3-alpha through 0.2.1.18.
5689 - Make accessing hidden services on 0.2.1.x work right again.
5690 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
5691 part of patch provided by "optimist".
5694 - When a relay/bridge is writing out its identity key fingerprint to
5695 the "fingerprint" file and to its logs, write it without spaces. Now
5696 it will look like the fingerprints in our bridges documentation,
5697 and confuse fewer users.
5700 - Relays no longer publish a new server descriptor if they change
5701 their MaxAdvertisedBandwidth config option but it doesn't end up
5702 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
5703 fixes bug 1026. Patch from Sebastian.
5704 - Avoid leaking memory every time we get a create cell but we have
5705 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
5706 fixes bug 1034. Reported by BarkerJr.
5709 Changes in version 0.2.1.18 - 2009-07-24
5710 Tor 0.2.1.18 lays the foundations for performance improvements,
5711 adds status events to help users diagnose bootstrap problems, adds
5712 optional authentication/authorization for hidden services, fixes a
5713 variety of potential anonymity problems, and includes a huge pile of
5714 other features and bug fixes.
5717 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
5720 Changes in version 0.2.1.17-rc - 2009-07-07
5721 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
5722 candidate for the 0.2.1.x series. It lays the groundwork for further
5723 client performance improvements, and also fixes a big bug with directory
5724 authorities that were causing them to assign Guard and Stable flags
5727 The Windows bundles also finally include the geoip database that we
5728 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
5729 should actually install Torbutton rather than giving you a cryptic
5730 failure message (oops).
5733 - Clients now use the bandwidth values in the consensus, rather than
5734 the bandwidth values in each relay descriptor. This approach opens
5735 the door to more accurate bandwidth estimates once the directory
5736 authorities start doing active measurements. Implements more of
5740 - When Tor clients restart after 1-5 days, they discard all their
5741 cached descriptors as too old, but they still use the cached
5742 consensus document. This approach is good for robustness, but
5743 bad for performance: since they don't know any bandwidths, they
5744 end up choosing at random rather than weighting their choice by
5745 speed. Fixed by the above feature of putting bandwidths in the
5746 consensus. Bugfix on 0.2.0.x.
5747 - Directory authorities were neglecting to mark relays down in their
5748 internal histories if the relays fall off the routerlist without
5749 ever being found unreachable. So there were relays in the histories
5750 that haven't been seen for eight months, and are listed as being
5751 up for eight months. This wreaked havoc on the "median wfu"
5752 and "median mtbf" calculations, in turn making Guard and Stable
5753 flags very wrong, hurting network performance. Fixes bugs 696 and
5754 969. Bugfix on 0.2.0.6-alpha.
5757 - Serve the DirPortFrontPage page even when we have been approaching
5758 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
5759 - The control port would close the connection before flushing long
5760 replies, such as the network consensus, if a QUIT command was issued
5761 before the reply had completed. Now, the control port flushes all
5762 pending replies before closing the connection. Also fixed a spurious
5763 warning when a QUIT command is issued after a malformed or rejected
5764 AUTHENTICATE command, but before the connection was closed. Patch
5765 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
5766 - When we can't find an intro key for a v2 hidden service descriptor,
5767 fall back to the v0 hidden service descriptor and log a bug message.
5768 Workaround for bug 1024.
5769 - Fix a log message that did not respect the SafeLogging option.
5773 - If we're a relay and we change our IP address, be more verbose
5774 about the reason that made us change. Should help track down
5775 further bugs for relays on dynamic IP addresses.
5778 Changes in version 0.2.0.35 - 2009-06-24
5780 - Avoid crashing in the presence of certain malformed descriptors.
5781 Found by lark, and by automated fuzzing.
5782 - Fix an edge case where a malicious exit relay could convince a
5783 controller that the client's DNS question resolves to an internal IP
5784 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5787 - Finally fix the bug where dynamic-IP relays disappear when their
5788 IP address changes: directory mirrors were mistakenly telling
5789 them their old address if they asked via begin_dir, so they
5790 never got an accurate answer about their new address, so they
5791 just vanished after a day. For belt-and-suspenders, relays that
5792 don't set Address in their config now avoid using begin_dir for
5793 all direct connections. Should fix bugs 827, 883, and 900.
5794 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5795 that would occur on some exit nodes when DNS failures and timeouts
5796 occurred in certain patterns. Fix for bug 957.
5799 - When starting with a cache over a few days old, do not leak
5800 memory for the obsolete router descriptors in it. Bugfix on
5801 0.2.0.33; fixes bug 672.
5802 - Hidden service clients didn't use a cached service descriptor that
5803 was older than 15 minutes, but wouldn't fetch a new one either,
5804 because there was already one in the cache. Now, fetch a v2
5805 descriptor unless the same descriptor was added to the cache within
5806 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5809 Changes in version 0.2.1.16-rc - 2009-06-20
5810 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
5811 a bunch of minor bugs.
5814 - Fix an edge case where a malicious exit relay could convince a
5815 controller that the client's DNS question resolves to an internal IP
5816 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5818 o Major performance improvements (on 0.2.0.x):
5819 - Disable and refactor some debugging checks that forced a linear scan
5820 over the whole server-side DNS cache. These accounted for over 50%
5821 of CPU time on a relatively busy exit node's gprof profile. Found
5823 - Disable some debugging checks that appeared in exit node profile
5827 - Update to the "June 3 2009" ip-to-country file.
5828 - Do not have tor-resolve automatically refuse all .onion addresses;
5829 if AutomapHostsOnResolve is set in your torrc, this will work fine.
5831 o Minor bugfixes (on 0.2.0.x):
5832 - Log correct error messages for DNS-related network errors on
5834 - Fix a race condition that could cause crashes or memory corruption
5835 when running as a server with a controller listening for log
5837 - Avoid crashing when we have a policy specified in a DirPolicy or
5838 SocksPolicy or ReachableAddresses option with ports set on it,
5839 and we re-load the policy. May fix bug 996.
5840 - Hidden service clients didn't use a cached service descriptor that
5841 was older than 15 minutes, but wouldn't fetch a new one either,
5842 because there was already one in the cache. Now, fetch a v2
5843 descriptor unless the same descriptor was added to the cache within
5844 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5846 o Minor bugfixes (on 0.2.1.x):
5847 - Don't warn users about low port and hibernation mix when they
5848 provide a *ListenAddress directive to fix that. Bugfix on
5850 - When switching back and forth between bridge mode, do not start
5851 gathering GeoIP data until two hours have passed.
5852 - Do not complain that the user has requested an excluded node as
5853 an exit when the node is not really an exit. This could happen
5854 because the circuit was for testing, or an introduction point.
5858 Changes in version 0.2.1.15-rc - 2009-05-25
5859 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
5860 series. It fixes a major bug on fast exit relays, as well as a variety
5863 o Major bugfixes (on 0.2.0.x):
5864 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5865 that would occur on some exit nodes when DNS failures and timeouts
5866 occurred in certain patterns. Fix for bug 957.
5868 o Minor bugfixes (on 0.2.0.x):
5869 - Actually return -1 in the error case for read_bandwidth_usage().
5870 Harmless bug, since we currently don't care about the return value
5871 anywhere. Bugfix on 0.2.0.9-alpha.
5872 - Provide a more useful log message if bug 977 (related to buffer
5873 freelists) ever reappears, and do not crash right away.
5874 - Fix an assertion failure on 64-bit platforms when we allocated
5875 memory right up to the end of a memarea, then realigned the memory
5876 one step beyond the end. Fixes a possible cause of bug 930.
5877 - Protect the count of open sockets with a mutex, so we can't
5878 corrupt it when two threads are closing or opening sockets at once.
5879 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
5880 - Don't allow a bridge to publish its router descriptor to a
5881 non-bridge directory authority. Fixes part of bug 932.
5882 - When we change to or from being a bridge, reset our counts of
5883 client usage by country. Fixes bug 932.
5884 - Fix a bug that made stream bandwidth get misreported to the
5886 - Stop using malloc_usable_size() to use more area than we had
5887 actually allocated: it was safe, but made valgrind really unhappy.
5888 - Fix a memory leak when v3 directory authorities load their keys
5889 and cert from disk. Bugfix on 0.2.0.1-alpha.
5891 o Minor bugfixes (on 0.2.1.x):
5892 - Fix use of freed memory when deciding to mark a non-addable
5893 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
5896 Changes in version 0.2.1.14-rc - 2009-04-12
5897 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
5898 series. It begins fixing some major performance problems, and also
5899 finally addresses the bug that was causing relays on dynamic IP
5900 addresses to fall out of the directory.
5903 - Clients replace entry guards that were chosen more than a few months
5904 ago. This change should significantly improve client performance,
5905 especially once more people upgrade, since relays that have been
5906 a guard for a long time are currently overloaded.
5908 o Major bugfixes (on 0.2.0):
5909 - Finally fix the bug where dynamic-IP relays disappear when their
5910 IP address changes: directory mirrors were mistakenly telling
5911 them their old address if they asked via begin_dir, so they
5912 never got an accurate answer about their new address, so they
5913 just vanished after a day. For belt-and-suspenders, relays that
5914 don't set Address in their config now avoid using begin_dir for
5915 all direct connections. Should fix bugs 827, 883, and 900.
5916 - Relays were falling out of the networkstatus consensus for
5917 part of a day if they changed their local config but the
5918 authorities discarded their new descriptor as "not sufficiently
5919 different". Now directory authorities accept a descriptor as changed
5920 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
5922 - Avoid crashing in the presence of certain malformed descriptors.
5923 Found by lark, and by automated fuzzing.
5926 - When generating circuit events with verbose nicknames for
5927 controllers, try harder to look up nicknames for routers on a
5928 circuit. (Previously, we would look in the router descriptors we had
5929 for nicknames, but not in the consensus.) Partial fix for bug 941.
5930 - If the bridge config line doesn't specify a port, assume 443.
5931 This makes bridge lines a bit smaller and easier for users to
5933 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
5934 bytes (aka 20KB/s), to match our documentation. Also update
5935 directory authorities so they always assign the Fast flag to relays
5936 with 20KB/s of capacity. Now people running relays won't suddenly
5937 find themselves not seeing any use, if the network gets faster
5939 - Update to the "April 3 2009" ip-to-country file.
5942 - Avoid trying to print raw memory to the logs when we decide to
5943 give up on downloading a given relay descriptor. Bugfix on
5945 - In tor-resolve, when the Tor client to use is specified by
5946 <hostname>:<port>, actually use the specified port rather than
5947 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
5948 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
5949 - When starting with a cache over a few days old, do not leak
5950 memory for the obsolete router descriptors in it. Bugfix on
5952 - Avoid double-free on list of successfully uploaded hidden
5953 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
5954 - Change memarea_strndup() implementation to work even when
5955 duplicating a string at the end of a page. This bug was
5956 harmless for now, but could have meant crashes later. Fix by
5957 lark. Bugfix on 0.2.1.1-alpha.
5958 - Limit uploaded directory documents to be 16M rather than 500K.
5959 The directory authorities were refusing v3 consensus votes from
5960 other authorities, since the votes are now 504K. Fixes bug 959;
5961 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
5962 - Directory authorities should never send a 503 "busy" response to
5963 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
5967 Changes in version 0.2.1.13-alpha - 2009-03-09
5968 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
5969 cleanups. We're finally getting close to a release candidate.
5972 - Correctly update the list of which countries we exclude as
5973 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
5974 lark. Bugfix on 0.2.1.6-alpha.
5976 o Minor bugfixes (on 0.2.0.x and earlier):
5977 - Automatically detect MacOSX versions earlier than 10.4.0, and
5978 disable kqueue from inside Tor when running with these versions.
5979 We previously did this from the startup script, but that was no
5980 help to people who didn't use the startup script. Resolves bug 863.
5981 - When we had picked an exit node for a connection, but marked it as
5982 "optional", and it turned out we had no onion key for the exit,
5983 stop wanting that exit and try again. This situation may not
5984 be possible now, but will probably become feasible with proposal
5985 158. Spotted by rovv. Fixes another case of bug 752.
5986 - Clients no longer cache certificates for authorities they do not
5987 recognize. Bugfix on 0.2.0.9-alpha.
5988 - When we can't transmit a DNS request due to a network error, retry
5989 it after a while, and eventually transmit a failing response to
5990 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
5991 - If the controller claimed responsibility for a stream, but that
5992 stream never finished making its connection, it would live
5993 forever in circuit_wait state. Now we close it after SocksTimeout
5994 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
5995 - Drop begin cells to a hidden service if they come from the middle
5996 of a circuit. Patch from lark.
5997 - When we erroneously receive two EXTEND cells for the same circuit
5998 ID on the same connection, drop the second. Patch from lark.
5999 - Fix a crash that occurs on exit nodes when a nameserver request
6000 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
6001 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
6003 - Do not assume that a stack-allocated character array will be
6004 64-bit aligned on platforms that demand that uint64_t access is
6005 aligned. Possible fix for bug 604.
6006 - Parse dates and IPv4 addresses in a locale- and libc-independent
6007 manner, to avoid platform-dependent behavior on malformed input.
6008 - Build correctly when configured to build outside the main source
6009 path. Patch from Michael Gold.
6010 - We were already rejecting relay begin cells with destination port
6011 of 0. Now also reject extend cells with destination port or address
6012 of 0. Suggested by lark.
6014 o Minor bugfixes (on 0.2.1.x):
6015 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
6016 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
6017 - If we're an exit node, scrub the IP address to which we are exiting
6018 in the logs. Bugfix on 0.2.1.8-alpha.
6021 - On Linux, use the prctl call to re-enable core dumps when the user
6023 - New controller event NEWCONSENSUS that lists the networkstatus
6024 lines for every recommended relay. Now controllers like Torflow
6025 can keep up-to-date on which relays they should be using.
6026 - Update to the "February 26 2009" ip-to-country file.
6029 Changes in version 0.2.0.34 - 2009-02-08
6030 Tor 0.2.0.34 features several more security-related fixes. You should
6031 upgrade, especially if you run an exit relay (remote crash) or a
6032 directory authority (remote infinite loop), or you're on an older
6033 (pre-XP) or not-recently-patched Windows (remote exploit).
6035 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
6036 have many known flaws, and nobody should be using them. You should
6037 upgrade. If you're using a Linux or BSD and its packages are obsolete,
6038 stop using those packages and upgrade anyway.
6041 - Fix an infinite-loop bug on handling corrupt votes under certain
6042 circumstances. Bugfix on 0.2.0.8-alpha.
6043 - Fix a temporary DoS vulnerability that could be performed by
6044 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
6045 - Avoid a potential crash on exit nodes when processing malformed
6046 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
6047 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
6048 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
6051 - Fix compilation on systems where time_t is a 64-bit integer.
6052 Patch from Matthias Drochner.
6053 - Don't consider expiring already-closed client connections. Fixes
6054 bug 893. Bugfix on 0.0.2pre20.
6057 Changes in version 0.2.1.12-alpha - 2009-02-08
6058 Tor 0.2.1.12-alpha features several more security-related fixes. You
6059 should upgrade, especially if you run an exit relay (remote crash) or
6060 a directory authority (remote infinite loop), or you're on an older
6061 (pre-XP) or not-recently-patched Windows (remote exploit). It also
6062 includes a big pile of minor bugfixes and cleanups.
6065 - Fix an infinite-loop bug on handling corrupt votes under certain
6066 circumstances. Bugfix on 0.2.0.8-alpha.
6067 - Fix a temporary DoS vulnerability that could be performed by
6068 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
6069 - Avoid a potential crash on exit nodes when processing malformed
6070 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
6073 - Let controllers actually ask for the "clients_seen" event for
6074 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
6075 reported by Matt Edman.
6076 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
6078 - Fix a bug in address parsing that was preventing bridges or hidden
6079 service targets from being at IPv6 addresses.
6080 - Solve a bug that kept hardware crypto acceleration from getting
6081 enabled when accounting was turned on. Fixes bug 907. Bugfix on
6083 - Remove a bash-ism from configure.in to build properly on non-Linux
6084 platforms. Bugfix on 0.2.1.1-alpha.
6085 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
6086 headers. Bugfix on 0.2.0.10-alpha.
6087 - Don't consider expiring already-closed client connections. Fixes
6088 bug 893. Bugfix on 0.0.2pre20.
6089 - Fix another interesting corner-case of bug 891 spotted by rovv:
6090 Previously, if two hosts had different amounts of clock drift, and
6091 one of them created a new connection with just the wrong timing,
6092 the other might decide to deprecate the new connection erroneously.
6093 Bugfix on 0.1.1.13-alpha.
6094 - Resolve a very rare crash bug that could occur when the user forced
6095 a nameserver reconfiguration during the middle of a nameserver
6096 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
6097 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
6098 Bugfix on 0.2.1.7-alpha.
6099 - If we're using bridges and our network goes away, be more willing
6100 to forgive our bridges and try again when we get an application
6101 request. Bugfix on 0.2.0.x.
6104 - Support platforms where time_t is 64 bits long. (Congratulations,
6105 NetBSD!) Patch from Matthias Drochner.
6106 - Add a 'getinfo status/clients-seen' controller command, in case
6107 controllers want to hear clients_seen events but connect late.
6110 - Disable GCC's strict alias optimization by default, to avoid the
6111 likelihood of its introducing subtle bugs whenever our code violates
6112 the letter of C99's alias rules.
6115 Changes in version 0.2.0.33 - 2009-01-21
6116 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
6117 useful to users. It also finally fixes a bug where a relay or client
6118 that's been off for many days would take a long time to bootstrap.
6120 This update also fixes an important security-related bug reported by
6121 Ilja van Sprundel. You should upgrade. (We'll send out more details
6122 about the bug once people have had some time to upgrade.)
6125 - Fix a heap-corruption bug that may be remotely triggerable on
6126 some platforms. Reported by Ilja van Sprundel.
6129 - When a stream at an exit relay is in state "resolving" or
6130 "connecting" and it receives an "end" relay cell, the exit relay
6131 would silently ignore the end cell and not close the stream. If
6132 the client never closes the circuit, then the exit relay never
6133 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
6135 - When sending CREATED cells back for a given circuit, use a 64-bit
6136 connection ID to find the right connection, rather than an addr:port
6137 combination. Now that we can have multiple OR connections between
6138 the same ORs, it is no longer possible to use addr:port to uniquely
6139 identify a connection.
6140 - Bridge relays that had DirPort set to 0 would stop fetching
6141 descriptors shortly after startup, and then briefly resume
6142 after a new bandwidth test and/or after publishing a new bridge
6143 descriptor. Bridge users that try to bootstrap from them would
6144 get a recent networkstatus but would get descriptors from up to
6145 18 hours earlier, meaning most of the descriptors were obsolete
6146 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
6147 - Prevent bridge relays from serving their 'extrainfo' document
6148 to anybody who asks, now that extrainfo docs include potentially
6149 sensitive aggregated client geoip summaries. Bugfix on
6151 - If the cached networkstatus consensus is more than five days old,
6152 discard it rather than trying to use it. In theory it could be
6153 useful because it lists alternate directory mirrors, but in practice
6154 it just means we spend many minutes trying directory mirrors that
6155 are long gone from the network. Also discard router descriptors as
6156 we load them if they are more than five days old, since the onion
6157 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
6160 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6161 could make gcc generate non-functional binary search code. Bugfix
6163 - Build correctly on platforms without socklen_t.
6164 - Compile without warnings on solaris.
6165 - Avoid potential crash on internal error during signature collection.
6166 Fixes bug 864. Patch from rovv.
6167 - Correct handling of possible malformed authority signing key
6168 certificates with internal signature types. Fixes bug 880.
6169 Bugfix on 0.2.0.3-alpha.
6170 - Fix a hard-to-trigger resource leak when logging credential status.
6172 - When we can't initialize DNS because the network is down, do not
6173 automatically stop Tor from starting. Instead, we retry failed
6174 dns_init() every 10 minutes, and change the exit policy to reject
6175 *:* until one succeeds. Fixes bug 691.
6176 - Use 64 bits instead of 32 bits for connection identifiers used with
6177 the controller protocol, to greatly reduce risk of identifier reuse.
6178 - When we're choosing an exit node for a circuit, and we have
6179 no pending streams, choose a good general exit rather than one that
6180 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
6181 - Fix another case of assuming, when a specific exit is requested,
6182 that we know more than the user about what hosts it allows.
6183 Fixes one case of bug 752. Patch from rovv.
6184 - Clip the MaxCircuitDirtiness config option to a minimum of 10
6185 seconds. Warn the user if lower values are given in the
6186 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
6187 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
6188 user if lower values are given in the configuration. Bugfix on
6189 0.1.1.17-rc. Patch by Sebastian.
6190 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
6191 the cache because we already had a v0 descriptor with the same ID.
6192 Bugfix on 0.2.0.18-alpha.
6193 - Fix a race condition when freeing keys shared between main thread
6194 and CPU workers that could result in a memory leak. Bugfix on
6195 0.1.0.1-rc. Fixes bug 889.
6196 - Send a valid END cell back when a client tries to connect to a
6197 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
6198 840. Patch from rovv.
6199 - Check which hops rendezvous stream cells are associated with to
6200 prevent possible guess-the-streamid injection attacks from
6201 intermediate hops. Fixes another case of bug 446. Based on patch
6203 - If a broken client asks a non-exit router to connect somewhere,
6204 do not even do the DNS lookup before rejecting the connection.
6205 Fixes another case of bug 619. Patch from rovv.
6206 - When a relay gets a create cell it can't decrypt (e.g. because it's
6207 using the wrong onion key), we were dropping it and letting the
6208 client time out. Now actually answer with a destroy cell. Fixes
6209 bug 904. Bugfix on 0.0.2pre8.
6211 o Minor bugfixes (hidden services):
6212 - Do not throw away existing introduction points on SIGHUP. Bugfix on
6213 0.0.6pre1. Patch by Karsten. Fixes bug 874.
6216 - Report the case where all signatures in a detached set are rejected
6217 differently than the case where there is an error handling the
6219 - When we realize that another process has modified our cached
6220 descriptors, print out a more useful error message rather than
6221 triggering an assertion. Fixes bug 885. Patch from Karsten.
6222 - Implement the 0x20 hack to better resist DNS poisoning: set the
6223 case on outgoing DNS requests randomly, and reject responses that do
6224 not match the case correctly. This logic can be disabled with the
6225 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
6226 of servers that do not reliably preserve case in replies. See
6227 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
6229 - Check DNS replies for more matching fields to better resist DNS
6231 - Never use OpenSSL compression: it wastes RAM and CPU trying to
6232 compress cells, which are basically all encrypted, compressed, or
6236 Changes in version 0.2.1.11-alpha - 2009-01-20
6237 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
6238 week it will take a long time to bootstrap again" bug. It also fixes
6239 an important security-related bug reported by Ilja van Sprundel. You
6240 should upgrade. (We'll send out more details about the bug once people
6241 have had some time to upgrade.)
6244 - Fix a heap-corruption bug that may be remotely triggerable on
6245 some platforms. Reported by Ilja van Sprundel.
6248 - Discard router descriptors as we load them if they are more than
6249 five days old. Otherwise if Tor is off for a long time and then
6250 starts with cached descriptors, it will try to use the onion
6251 keys in those obsolete descriptors when building circuits. Bugfix
6252 on 0.2.0.x. Fixes bug 887.
6255 - Try to make sure that the version of Libevent we're running with
6256 is binary-compatible with the one we built with. May address bug
6258 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
6259 for bug 905. Bugfix on 0.2.1.7-alpha.
6260 - Add a new --enable-local-appdata configuration switch to change
6261 the default location of the datadir on win32 from APPDATA to
6262 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
6263 entirely. Patch from coderman.
6266 - Make outbound DNS packets respect the OutboundBindAddress setting.
6267 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
6268 - When our circuit fails at the first hop (e.g. we get a destroy
6269 cell back), avoid using that OR connection anymore, and also
6270 tell all the one-hop directory requests waiting for it that they
6271 should fail. Bugfix on 0.2.1.3-alpha.
6272 - In the torify(1) manpage, mention that tsocks will leak your
6276 Changes in version 0.2.1.10-alpha - 2009-01-06
6277 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
6278 would make the bridge relay not so useful if it had DirPort set to 0,
6279 and one that could let an attacker learn a little bit of information
6280 about the bridge's users), and a bug that would cause your Tor relay
6281 to ignore a circuit create request it can't decrypt (rather than reply
6282 with an error). It also fixes a wide variety of other bugs.
6285 - If the cached networkstatus consensus is more than five days old,
6286 discard it rather than trying to use it. In theory it could
6287 be useful because it lists alternate directory mirrors, but in
6288 practice it just means we spend many minutes trying directory
6289 mirrors that are long gone from the network. Helps bug 887 a bit;
6291 - Bridge relays that had DirPort set to 0 would stop fetching
6292 descriptors shortly after startup, and then briefly resume
6293 after a new bandwidth test and/or after publishing a new bridge
6294 descriptor. Bridge users that try to bootstrap from them would
6295 get a recent networkstatus but would get descriptors from up to
6296 18 hours earlier, meaning most of the descriptors were obsolete
6297 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
6298 - Prevent bridge relays from serving their 'extrainfo' document
6299 to anybody who asks, now that extrainfo docs include potentially
6300 sensitive aggregated client geoip summaries. Bugfix on
6304 - New controller event "clients_seen" to report a geoip-based summary
6305 of which countries we've seen clients from recently. Now controllers
6306 like Vidalia can show bridge operators that they're actually making
6308 - Build correctly against versions of OpenSSL 0.9.8 or later built
6309 without support for deprecated functions.
6310 - Update to the "December 19 2008" ip-to-country file.
6312 o Minor bugfixes (on 0.2.0.x):
6313 - Authorities now vote for the Stable flag for any router whose
6314 weighted MTBF is at least 5 days, regardless of the mean MTBF.
6315 - Do not remove routers as too old if we do not have any consensus
6316 document. Bugfix on 0.2.0.7-alpha.
6317 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
6318 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
6319 - When an exit relay resolves a stream address to a local IP address,
6320 do not just keep retrying that same exit relay over and
6321 over. Instead, just close the stream. Addresses bug 872. Bugfix
6322 on 0.2.0.32. Patch from rovv.
6323 - If a hidden service sends us an END cell, do not consider
6324 retrying the connection; just close it. Patch from rovv.
6325 - When we made bridge authorities stop serving bridge descriptors over
6326 unencrypted links, we also broke DirPort reachability testing for
6327 bridges. So bridges with a non-zero DirPort were printing spurious
6328 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
6329 - When a relay gets a create cell it can't decrypt (e.g. because it's
6330 using the wrong onion key), we were dropping it and letting the
6331 client time out. Now actually answer with a destroy cell. Fixes
6332 bug 904. Bugfix on 0.0.2pre8.
6333 - Squeeze 2-5% out of client performance (according to oprofile) by
6334 improving the implementation of some policy-manipulation functions.
6336 o Minor bugfixes (on 0.2.1.x):
6337 - Make get_interface_address() function work properly again; stop
6338 guessing the wrong parts of our address as our address.
6339 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
6340 send on that circuit. Otherwise we might violate the proposal-110
6341 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
6343 - When we're sending non-EXTEND cells to the first hop in a circuit,
6344 for example to use an encrypted directory connection, we don't need
6345 to use RELAY_EARLY cells: the first hop knows what kind of cell
6346 it is, and nobody else can even see the cell type. Conserving
6347 RELAY_EARLY cells makes it easier to cannibalize circuits like
6349 - Stop logging nameserver addresses in reverse order.
6350 - If we are retrying a directory download slowly over and over, do
6351 not automatically give up after the 254th failure. Bugfix on
6353 - Resume reporting accurate "stream end" reasons to the local control
6354 port. They were lost in the changes for Proposal 148. Bugfix on
6357 o Deprecated and removed features:
6358 - The old "tor --version --version" command, which would print out
6359 the subversion "Id" of most of the source files, is now removed. It
6360 turned out to be less useful than we'd expected, and harder to
6363 o Code simplifications and refactoring:
6364 - Change our header file guard macros to be less likely to conflict
6365 with system headers. Adam Langley noticed that we were conflicting
6366 with log.h on Android.
6367 - Tool-assisted documentation cleanup. Nearly every function or
6368 static variable in Tor should have its own documentation now.
6371 Changes in version 0.2.1.9-alpha - 2008-12-25
6372 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
6374 o New directory authorities:
6375 - gabelmoo (the authority run by Karsten Loesing) now has a new
6379 - Never use a connection with a mismatched address to extend a
6380 circuit, unless that connection is canonical. A canonical
6381 connection is one whose address is authenticated by the router's
6382 identity key, either in a NETINFO cell or in a router descriptor.
6383 - Avoid a possible memory corruption bug when receiving hidden service
6384 descriptors. Bugfix on 0.2.1.6-alpha.
6387 - Fix a logic error that would automatically reject all but the first
6388 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
6389 part of bug 813/868. Bug spotted by coderman.
6390 - When a stream at an exit relay is in state "resolving" or
6391 "connecting" and it receives an "end" relay cell, the exit relay
6392 would silently ignore the end cell and not close the stream. If
6393 the client never closes the circuit, then the exit relay never
6394 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
6396 - When we can't initialize DNS because the network is down, do not
6397 automatically stop Tor from starting. Instead, retry failed
6398 dns_init() every 10 minutes, and change the exit policy to reject
6399 *:* until one succeeds. Fixes bug 691.
6402 - Give a better error message when an overzealous init script says
6403 "sudo -u username tor --user username". Makes Bug 882 easier for
6405 - When a directory authority gives us a new guess for our IP address,
6406 log which authority we used. Hopefully this will help us debug
6407 the recent complaints about bad IP address guesses.
6408 - Detect svn revision properly when we're using git-svn.
6409 - Try not to open more than one descriptor-downloading connection
6410 to an authority at once. This should reduce load on directory
6411 authorities. Fixes bug 366.
6412 - Add cross-certification to newly generated certificates, so that
6413 a signing key is enough information to look up a certificate.
6414 Partial implementation of proposal 157.
6415 - Start serving certificates by <identity digest, signing key digest>
6416 pairs. Partial implementation of proposal 157.
6417 - Clients now never report any stream end reason except 'MISC'.
6418 Implements proposal 148.
6419 - On platforms with a maximum syslog string length, truncate syslog
6420 messages to that length ourselves, rather than relying on the
6421 system to do it for us.
6422 - Optimize out calls to time(NULL) that occur for every IO operation,
6423 or for every cell. On systems where time() is a slow syscall,
6424 this fix will be slightly helpful.
6425 - Exit servers can now answer resolve requests for ip6.arpa addresses.
6426 - When we download a descriptor that we then immediately (as
6427 a directory authority) reject, do not retry downloading it right
6428 away. Should save some bandwidth on authorities. Fix for bug
6429 888. Patch by Sebastian Hahn.
6430 - When a download gets us zero good descriptors, do not notify
6431 Tor that new directory information has arrived.
6432 - Avoid some nasty corner cases in the logic for marking connections
6433 as too old or obsolete or noncanonical for circuits. Partial
6436 o Minor features (controller):
6437 - New CONSENSUS_ARRIVED event to note when a new consensus has
6438 been fetched and validated.
6439 - When we realize that another process has modified our cached
6440 descriptors file, print out a more useful error message rather
6441 than triggering an assertion. Fixes bug 885. Patch from Karsten.
6442 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
6443 controllers to prevent SIGHUP from reloading the
6444 configuration. Fixes bug 856.
6447 - Resume using the correct "REASON=" stream when telling the
6448 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
6449 - When a canonical connection appears later in our internal list
6450 than a noncanonical one for a given OR ID, always use the
6451 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
6453 - Clip the MaxCircuitDirtiness config option to a minimum of 10
6454 seconds. Warn the user if lower values are given in the
6455 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
6456 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
6457 user if lower values are given in the configuration. Bugfix on
6458 0.1.1.17-rc. Patch by Sebastian.
6459 - Fix a race condition when freeing keys shared between main thread
6460 and CPU workers that could result in a memory leak. Bugfix on
6461 0.1.0.1-rc. Fixes bug 889.
6463 o Minor bugfixes (hidden services):
6464 - Do not throw away existing introduction points on SIGHUP (bugfix on
6465 0.0.6pre1); also, do not stall hidden services because we're
6466 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
6467 by John Brooks. Patch by Karsten. Fixes bug 874.
6468 - Fix a memory leak when we decline to add a v2 rendezvous
6469 descriptor to the cache because we already had a v0 descriptor
6470 with the same ID. Bugfix on 0.2.0.18-alpha.
6472 o Deprecated and removed features:
6473 - RedirectExits has been removed. It was deprecated since
6475 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
6476 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
6477 - Cell pools are now always enabled; --disable-cell-pools is ignored.
6479 o Code simplifications and refactoring:
6480 - Rename the confusing or_is_obsolete field to the more appropriate
6481 is_bad_for_new_circs, and move it to or_connection_t where it
6483 - Move edge-only flags from connection_t to edge_connection_t: not
6484 only is this better coding, but on machines of plausible alignment,
6485 it should save 4-8 bytes per connection_t. "Every little bit helps."
6486 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
6487 for consistency; keep old option working for backward compatibility.
6488 - Simplify the code for finding connections to use for a circuit.
6491 Changes in version 0.2.1.8-alpha - 2008-12-08
6492 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
6493 builds better on unusual platforms like Solaris and old OS X, and
6494 fixes a variety of other issues.
6497 - New DirPortFrontPage option that takes an html file and publishes
6498 it as "/" on the DirPort. Now relay operators can provide a
6499 disclaimer without needing to set up a separate webserver. There's
6500 a sample disclaimer in contrib/tor-exit-notice.html.
6503 - When the client is choosing entry guards, now it selects at most
6504 one guard from a given relay family. Otherwise we could end up with
6505 all of our entry points into the network run by the same operator.
6506 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
6509 - Fix a DOS opportunity during the voting signature collection process
6510 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6511 - Fix a possible segfault when establishing an exit connection. Bugfix
6515 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
6517 - Made Tor a little less aggressive about deleting expired
6518 certificates. Partial fix for bug 854.
6519 - Stop doing unaligned memory access that generated bus errors on
6520 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
6521 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
6522 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
6523 - Make USR2 log-level switch take effect immediately. Bugfix on
6525 - If one win32 nameserver fails to get added, continue adding the
6526 rest, and don't automatically fail.
6527 - Use fcntl() for locking when flock() is not available. Should fix
6528 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
6529 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6530 could make gcc generate non-functional binary search code. Bugfix
6532 - Build correctly on platforms without socklen_t.
6533 - Avoid potential crash on internal error during signature collection.
6534 Fixes bug 864. Patch from rovv.
6535 - Do not use C's stdio library for writing to log files. This will
6536 improve logging performance by a minute amount, and will stop
6537 leaking fds when our disk is full. Fixes bug 861.
6538 - Stop erroneous use of O_APPEND in cases where we did not in fact
6539 want to re-seek to the end of a file before every last write().
6540 - Correct handling of possible malformed authority signing key
6541 certificates with internal signature types. Fixes bug 880. Bugfix
6543 - Fix a hard-to-trigger resource leak when logging credential status.
6547 - Directory mirrors no longer fetch the v1 directory or
6548 running-routers files. They are obsolete, and nobody asks for them
6549 anymore. This is the first step to making v1 authorities obsolete.
6551 o Minor features (controller):
6552 - Return circuit purposes in response to GETINFO circuit-status. Fixes
6556 Changes in version 0.2.0.32 - 2008-11-20
6557 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
6558 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6559 a smaller security flaw that might allow an attacker to access local
6560 services, further improves hidden service performance, and fixes a
6561 variety of other issues.
6564 - The "User" and "Group" config options did not clear the
6565 supplementary group entries for the Tor process. The "User" option
6566 is now more robust, and we now set the groups to the specified
6567 user's primary group. The "Group" option is now ignored. For more
6568 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6569 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6570 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
6571 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6572 consistently obeyed: if an exit relay refuses a stream because its
6573 exit policy doesn't allow it, we would remember what IP address
6574 the relay said the destination address resolves to, even if it's
6575 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6578 - Fix a DOS opportunity during the voting signature collection process
6579 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6581 o Major bugfixes (hidden services):
6582 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6583 we were failing the whole hidden service request when the v0
6584 descriptor fetch fails, even if the v2 fetch is still pending and
6585 might succeed. Similarly, if the last v2 fetch fails, we were
6586 failing the whole hidden service request even if a v0 fetch is
6587 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6588 - When extending a circuit to a hidden service directory to upload a
6589 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6590 requests failed, because the router descriptor has not been
6591 downloaded yet. In these cases, do not attempt to upload the
6592 rendezvous descriptor, but wait until the router descriptor is
6593 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
6594 descriptor from a hidden service directory for which the router
6595 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
6599 - Fix several infrequent memory leaks spotted by Coverity.
6600 - When testing for libevent functions, set the LDFLAGS variable
6601 correctly. Found by Riastradh.
6602 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6603 bootstrapping with tunneled directory connections. Bugfix on
6604 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6605 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6606 and we know that server B rejects most-but-not all connections to
6607 port 80, we would previously reject the connection. Now, we assume
6608 the user knows what they were asking for. Fixes bug 752. Bugfix
6609 on 0.0.9rc5. Diagnosed by BarkerJr.
6610 - If we overrun our per-second write limits a little, count this as
6611 having used up our write allocation for the second, and choke
6612 outgoing directory writes. Previously, we had only counted this when
6613 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
6614 Bugfix on 0.2.0.x (??).
6615 - Remove the old v2 directory authority 'lefkada' from the default
6616 list. It has been gone for many months.
6617 - Stop doing unaligned memory access that generated bus errors on
6618 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
6619 - Make USR2 log-level switch take effect immediately. Bugfix on
6622 o Minor bugfixes (controller):
6623 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
6624 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
6627 Changes in version 0.2.1.7-alpha - 2008-11-08
6628 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
6629 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6630 a smaller security flaw that might allow an attacker to access local
6631 services, adds better defense against DNS poisoning attacks on exit
6632 relays, further improves hidden service performance, and fixes a
6633 variety of other issues.
6636 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6637 consistently obeyed: if an exit relay refuses a stream because its
6638 exit policy doesn't allow it, we would remember what IP address
6639 the relay said the destination address resolves to, even if it's
6640 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6641 - The "User" and "Group" config options did not clear the
6642 supplementary group entries for the Tor process. The "User" option
6643 is now more robust, and we now set the groups to the specified
6644 user's primary group. The "Group" option is now ignored. For more
6645 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6646 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6647 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
6648 - Do not use or believe expired v3 authority certificates. Patch
6649 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
6652 - Now NodeFamily and MyFamily config options allow spaces in
6653 identity fingerprints, so it's easier to paste them in.
6654 Suggested by Lucky Green.
6655 - Implement the 0x20 hack to better resist DNS poisoning: set the
6656 case on outgoing DNS requests randomly, and reject responses that do
6657 not match the case correctly. This logic can be disabled with the
6658 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
6659 of servers that do not reliably preserve case in replies. See
6660 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
6662 - Preserve case in replies to DNSPort requests in order to support
6663 the 0x20 hack for resisting DNS poisoning attacks.
6665 o Hidden service performance improvements:
6666 - When the client launches an introduction circuit, retry with a
6667 new circuit after 30 seconds rather than 60 seconds.
6668 - Launch a second client-side introduction circuit in parallel
6669 after a delay of 15 seconds (based on work by Christian Wilms).
6670 - Hidden services start out building five intro circuits rather
6671 than three, and when the first three finish they publish a service
6672 descriptor using those. Now we publish our service descriptor much
6673 faster after restart.
6676 - Minor fix in the warning messages when you're having problems
6677 bootstrapping; also, be more forgiving of bootstrap problems when
6678 we're still making incremental progress on a given bootstrap phase.
6679 - When we're choosing an exit node for a circuit, and we have
6680 no pending streams, choose a good general exit rather than one that
6681 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
6682 - Send a valid END cell back when a client tries to connect to a
6683 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
6684 840. Patch from rovv.
6685 - If a broken client asks a non-exit router to connect somewhere,
6686 do not even do the DNS lookup before rejecting the connection.
6687 Fixes another case of bug 619. Patch from rovv.
6688 - Fix another case of assuming, when a specific exit is requested,
6689 that we know more than the user about what hosts it allows.
6690 Fixes another case of bug 752. Patch from rovv.
6691 - Check which hops rendezvous stream cells are associated with to
6692 prevent possible guess-the-streamid injection attacks from
6693 intermediate hops. Fixes another case of bug 446. Based on patch
6695 - Avoid using a negative right-shift when comparing 32-bit
6696 addresses. Possible fix for bug 845 and bug 811.
6697 - Make the assert_circuit_ok() function work correctly on circuits that
6698 have already been marked for close.
6699 - Fix read-off-the-end-of-string error in unit tests when decoding
6700 introduction points.
6701 - Fix uninitialized size field for memory area allocation: may improve
6702 memory performance during directory parsing.
6703 - Treat duplicate certificate fetches as failures, so that we do
6704 not try to re-fetch an expired certificate over and over and over.
6705 - Do not say we're fetching a certificate when we'll in fact skip it
6706 because of a pending download.
6709 Changes in version 0.2.1.6-alpha - 2008-09-30
6710 Tor 0.2.1.6-alpha further improves performance and robustness of
6711 hidden services, starts work on supporting per-country relay selection,
6712 and fixes a variety of smaller issues.
6715 - Implement proposal 121: make it possible to build hidden services
6716 that only certain clients are allowed to connect to. This is
6717 enforced at several points, so that unauthorized clients are unable
6718 to send INTRODUCE cells to the service, or even (depending on the
6719 type of authentication) to learn introduction points. This feature
6720 raises the bar for certain kinds of active attacks against hidden
6721 services. Code by Karsten Loesing.
6722 - Relays now store and serve v2 hidden service descriptors by default,
6723 i.e., the new default value for HidServDirectoryV2 is 1. This is
6724 the last step in proposal 114, which aims to make hidden service
6725 lookups more reliable.
6726 - Start work to allow node restrictions to include country codes. The
6727 syntax to exclude nodes in a country with country code XX is
6728 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
6729 refinement to decide what config options should take priority if
6730 you ask to both use a particular node and exclude it.
6731 - Allow ExitNodes list to include IP ranges and country codes, just
6732 like the Exclude*Nodes lists. Patch from Robert Hogan.
6735 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
6736 Tor to fail to start if you had it configured to use a bridge
6737 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
6738 - When extending a circuit to a hidden service directory to upload a
6739 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6740 requests failed, because the router descriptor had not been
6741 downloaded yet. In these cases, we now wait until the router
6742 descriptor is downloaded, and then retry. Likewise, clients
6743 now skip over a hidden service directory if they don't yet have
6744 its router descriptor, rather than futilely requesting it and
6745 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
6747 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6748 we were failing the whole hidden service request when the v0
6749 descriptor fetch fails, even if the v2 fetch is still pending and
6750 might succeed. Similarly, if the last v2 fetch fails, we were
6751 failing the whole hidden service request even if a v0 fetch is
6752 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6753 - DNS replies need to have names matching their requests, but
6754 these names should be in the questions section, not necessarily
6755 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
6758 - Update to the "September 1 2008" ip-to-country file.
6759 - Allow ports 465 and 587 in the default exit policy again. We had
6760 rejected them in 0.1.0.15, because back in 2005 they were commonly
6761 misconfigured and ended up as spam targets. We hear they are better
6762 locked down these days.
6763 - Use a lockfile to make sure that two Tor processes are not
6764 simultaneously running with the same datadir.
6765 - Serve the latest v3 networkstatus consensus via the control
6766 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
6767 - Better logging about stability/reliability calculations on directory
6769 - Drop the requirement to have an open dir port for storing and
6770 serving v2 hidden service descriptors.
6771 - Directory authorities now serve a /tor/dbg-stability.txt URL to
6772 help debug WFU and MTBF calculations.
6773 - Implement most of Proposal 152: allow specialized servers to permit
6774 single-hop circuits, and clients to use those servers to build
6775 single-hop circuits when using a specialized controller. Patch
6776 from Josh Albrecht. Resolves feature request 768.
6777 - Add a -p option to tor-resolve for specifying the SOCKS port: some
6778 people find host:port too confusing.
6779 - Make TrackHostExit mappings expire a while after their last use, not
6780 after their creation. Patch from Robert Hogan.
6781 - Provide circuit purposes along with circuit events to the controller.
6784 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
6786 - Fixed some memory leaks -- some quite frequent, some almost
6787 impossible to trigger -- based on results from Coverity.
6788 - When testing for libevent functions, set the LDFLAGS variable
6789 correctly. Found by Riastradh.
6790 - Fix an assertion bug in parsing policy-related options; possible fix
6792 - Catch and report a few more bootstrapping failure cases when Tor
6793 fails to establish a TCP connection. Cleanup on 0.2.1.x.
6794 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6795 bootstrapping with tunneled directory connections. Bugfix on
6796 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6797 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6798 and we know that server B rejects most-but-not all connections to
6799 port 80, we would previously reject the connection. Now, we assume
6800 the user knows what they were asking for. Fixes bug 752. Bugfix
6801 on 0.0.9rc5. Diagnosed by BarkerJr.
6802 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
6803 service directories if they have no advertised dir port. Bugfix
6805 - If we overrun our per-second write limits a little, count this as
6806 having used up our write allocation for the second, and choke
6807 outgoing directory writes. Previously, we had only counted this when
6808 we had met our limits precisely. Fixes bug 824. Patch by rovv.
6809 Bugfix on 0.2.0.x (??).
6810 - Avoid a "0 divided by 0" calculation when calculating router uptime
6811 at directory authorities. Bugfix on 0.2.0.8-alpha.
6812 - Make DNS resolved controller events into "CLOSED", not
6813 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
6815 - Fix a bug where an unreachable relay would establish enough
6816 reachability testing circuits to do a bandwidth test -- if
6817 we already have a connection to the middle hop of the testing
6818 circuit, then it could establish the last hop by using the existing
6819 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
6820 circuits no longer use entry guards in 0.2.1.3-alpha.
6821 - If we have correct permissions on $datadir, we complain to stdout
6822 and fail to start. But dangerous permissions on
6823 $datadir/cached-status/ would cause us to open a log and complain
6824 there. Now complain to stdout and fail to start in both cases. Fixes
6825 bug 820, reported by seeess.
6826 - Remove the old v2 directory authority 'lefkada' from the default
6827 list. It has been gone for many months.
6829 o Code simplifications and refactoring:
6830 - Revise the connection_new functions so that a more typesafe variant
6831 exists. This will work better with Coverity, and let us find any
6832 actual mistakes we're making here.
6833 - Refactor unit testing logic so that dmalloc can be used sensibly
6834 with unit tests to check for memory leaks.
6835 - Move all hidden-service related fields from connection and circuit
6836 structure to substructures: this way they won't eat so much memory.
6839 Changes in version 0.2.0.31 - 2008-09-03
6840 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
6841 a big bug we're seeing where in rare cases traffic from one Tor stream
6842 gets mixed into another stream, and fixes a variety of smaller issues.
6845 - Make sure that two circuits can never exist on the same connection
6846 with the same circuit ID, even if one is marked for close. This
6847 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
6848 - Relays now reject risky extend cells: if the extend cell includes
6849 a digest of all zeroes, or asks to extend back to the relay that
6850 sent the extend cell, tear down the circuit. Ideas suggested
6852 - If not enough of our entry guards are available so we add a new
6853 one, we might use the new one even if it overlapped with the
6854 current circuit's exit relay (or its family). Anonymity bugfix
6855 pointed out by rovv.
6858 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6859 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6860 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6861 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6862 - Pick size of default geoip filename string correctly on windows.
6863 Fixes bug 806. Bugfix on 0.2.0.30.
6864 - Make the autoconf script accept the obsolete --with-ssl-dir
6865 option as an alias for the actually-working --with-openssl-dir
6866 option. Fix the help documentation to recommend --with-openssl-dir.
6867 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6868 - When using the TransPort option on OpenBSD, and using the User
6869 option to change UID and drop privileges, make sure to open
6870 /dev/pf before dropping privileges. Fixes bug 782. Patch from
6871 Christopher Davis. Bugfix on 0.1.2.1-alpha.
6872 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6873 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6874 on the client side when connecting to a hidden service. Bugfix
6875 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6876 - When closing an application-side connection because its circuit is
6877 getting torn down, generate the stream event correctly. Bugfix on
6878 0.1.2.x. Anonymous patch.
6881 Changes in version 0.2.1.5-alpha - 2008-08-31
6882 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
6883 in a lot of the infrastructure for adding authorization to hidden
6884 services, lays the groundwork for having clients read their load
6885 balancing information out of the networkstatus consensus rather than
6886 the individual router descriptors, addresses two potential anonymity
6887 issues, and fixes a variety of smaller issues.
6890 - Convert many internal address representations to optionally hold
6892 - Generate and accept IPv6 addresses in many protocol elements.
6893 - Make resolver code handle nameservers located at ipv6 addresses.
6894 - Begin implementation of proposal 121 ("Client authorization for
6895 hidden services"): configure hidden services with client
6896 authorization, publish descriptors for them, and configure
6897 authorization data for hidden services at clients. The next
6898 step is to actually access hidden services that perform client
6900 - More progress toward proposal 141: Network status consensus
6901 documents and votes now contain bandwidth information for each
6902 router and a summary of that router's exit policy. Eventually this
6903 will be used by clients so that they do not have to download every
6904 known descriptor before building circuits.
6906 o Major bugfixes (on 0.2.0.x and before):
6907 - When sending CREATED cells back for a given circuit, use a 64-bit
6908 connection ID to find the right connection, rather than an addr:port
6909 combination. Now that we can have multiple OR connections between
6910 the same ORs, it is no longer possible to use addr:port to uniquely
6911 identify a connection.
6912 - Relays now reject risky extend cells: if the extend cell includes
6913 a digest of all zeroes, or asks to extend back to the relay that
6914 sent the extend cell, tear down the circuit. Ideas suggested
6916 - If not enough of our entry guards are available so we add a new
6917 one, we might use the new one even if it overlapped with the
6918 current circuit's exit relay (or its family). Anonymity bugfix
6919 pointed out by rovv.
6922 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6923 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6924 - When using the TransPort option on OpenBSD, and using the User
6925 option to change UID and drop privileges, make sure to open /dev/pf
6926 before dropping privileges. Fixes bug 782. Patch from Christopher
6927 Davis. Bugfix on 0.1.2.1-alpha.
6928 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6929 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6930 - Add a missing safe_str() call for a debug log message.
6931 - Use 64 bits instead of 32 bits for connection identifiers used with
6932 the controller protocol, to greatly reduce risk of identifier reuse.
6933 - Make the autoconf script accept the obsolete --with-ssl-dir
6934 option as an alias for the actually-working --with-openssl-dir
6935 option. Fix the help documentation to recommend --with-openssl-dir.
6936 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6939 - Rate-limit too-many-sockets messages: when they happen, they happen
6940 a lot. Resolves bug 748.
6941 - Resist DNS poisoning a little better by making sure that names in
6942 answer sections match.
6943 - Print the SOCKS5 error message string as well as the error code
6944 when a tor-resolve request fails. Patch from Jacob.
6947 Changes in version 0.2.1.4-alpha - 2008-08-04
6948 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
6951 - The address part of exit policies was not correctly written
6952 to router descriptors. This generated router descriptors that failed
6953 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
6955 - Tor triggered a false assert when extending a circuit to a relay
6956 but we already have a connection open to that relay. Noticed by
6957 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
6960 - Fix a hidden service logging bug: in some edge cases, the router
6961 descriptor of a previously picked introduction point becomes
6962 obsolete and we need to give up on it rather than continually
6963 complaining that it has become obsolete. Observed by xiando. Bugfix
6967 - Take out the TestVia config option, since it was a workaround for
6968 a bug that was fixed in Tor 0.1.1.21.
6971 Changes in version 0.2.1.3-alpha - 2008-08-03
6972 Tor 0.2.1.3-alpha implements most of the pieces to prevent
6973 infinite-length circuit attacks (see proposal 110); fixes a bug that
6974 might cause exit relays to corrupt streams they send back; allows
6975 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
6976 ExcludeExitNodes config options; and fixes a big pile of bugs.
6978 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
6979 - Send a bootstrap problem "warn" event on the first problem if the
6980 reason is NO_ROUTE (that is, our network is down).
6983 - Implement most of proposal 110: The first K cells to be sent
6984 along a circuit are marked as special "early" cells; only K "early"
6985 cells will be allowed. Once this code is universal, we can block
6986 certain kinds of DOS attack by requiring that EXTEND commands must
6987 be sent using an "early" cell.
6990 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6991 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6992 on the client side when connecting to a hidden service. Bugfix
6993 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6994 - Ensure that two circuits can never exist on the same connection
6995 with the same circuit ID, even if one is marked for close. This
6996 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
6999 - When relays do their initial bandwidth measurement, don't limit
7000 to just our entry guards for the test circuits. Otherwise we tend
7001 to have multiple test circuits going through a single entry guard,
7002 which makes our bandwidth test less accurate. Fixes part of bug 654;
7003 patch contributed by Josh Albrecht.
7004 - Add an ExcludeExitNodes option so users can list a set of nodes
7005 that should be be excluded from the exit node position, but
7006 allowed elsewhere. Implements proposal 151.
7007 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
7008 ExcludeNodes and ExcludeExitNodes lists.
7009 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
7010 be more efficient. Formerly it was quadratic in the number of
7011 servers; now it should be linear. Fixes bug 509.
7012 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
7013 and n_conn_id_digest fields into a separate structure that's
7014 only needed when the circuit has not yet attached to an n_conn.
7017 - Change the contrib/tor.logrotate script so it makes the new
7018 logs as "_tor:_tor" rather than the default, which is generally
7019 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
7020 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
7021 warnings (occasionally), but it can also cause the compiler to
7022 eliminate error-checking code. Suggested by Peter Gutmann.
7023 - When a hidden service is giving up on an introduction point candidate
7024 that was not included in the last published rendezvous descriptor,
7025 don't reschedule publication of the next descriptor. Fixes bug 763.
7027 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
7028 HiddenServiceExcludeNodes as obsolete: they never worked properly,
7029 and nobody claims to be using them. Fixes bug 754. Bugfix on
7030 0.1.0.1-rc. Patch from Christian Wilms.
7031 - Fix a small alignment and memory-wasting bug on buffer chunks.
7034 o Minor bugfixes (controller):
7035 - When closing an application-side connection because its circuit
7036 is getting torn down, generate the stream event correctly.
7037 Bugfix on 0.1.2.x. Anonymous patch.
7040 - Remove all backward-compatibility code to support relays running
7041 versions of Tor so old that they no longer work at all on the
7045 Changes in version 0.2.0.30 - 2008-07-15
7047 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
7048 warnings (occasionally), but it can also cause the compiler to
7049 eliminate error-checking code. Suggested by Peter Gutmann.
7052 Changes in version 0.2.0.29-rc - 2008-07-08
7053 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
7054 hidden-service performance bugs, and fixes a bunch of smaller bugs.
7057 - If you have more than one bridge but don't know their keys,
7058 you would only launch a request for the descriptor of the first one
7059 on your list. (Tor considered launching requests for the others, but
7060 found that it already had a connection on the way for $0000...0000
7061 so it didn't open another.) Bugfix on 0.2.0.x.
7062 - If you have more than one bridge but don't know their keys, and the
7063 connection to one of the bridges failed, you would cancel all
7064 pending bridge connections. (After all, they all have the same
7065 digest.) Bugfix on 0.2.0.x.
7066 - When a hidden service was trying to establish an introduction point,
7067 and Tor had built circuits preemptively for such purposes, we
7068 were ignoring all the preemptive circuits and launching a new one
7069 instead. Bugfix on 0.2.0.14-alpha.
7070 - When a hidden service was trying to establish an introduction point,
7071 and Tor *did* manage to reuse one of the preemptively built
7072 circuits, it didn't correctly remember which one it used,
7073 so it asked for another one soon after, until there were no
7074 more preemptive circuits, at which point it launched one from
7075 scratch. Bugfix on 0.0.9.x.
7076 - Make directory servers include the X-Your-Address-Is: http header in
7077 their responses even for begin_dir conns. Now clients who only
7078 ever use begin_dir connections still have a way to learn their IP
7079 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
7082 - Fix a macro/CPP interaction that was confusing some compilers:
7083 some GCCs don't like #if/#endif pairs inside macro arguments.
7085 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
7086 Fixes bug 704; fix from Steven Murdoch.
7087 - When opening /dev/null in finish_daemonize(), do not pass the
7088 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
7089 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
7090 - Correctly detect transparent proxy support on Linux hosts that
7091 require in.h to be included before netfilter_ipv4.h. Patch
7093 - Disallow session resumption attempts during the renegotiation
7094 stage of the v2 handshake protocol. Clients should never be trying
7095 session resumption at this point, but apparently some did, in
7096 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
7097 found by Geoff Goodell.
7100 Changes in version 0.2.1.2-alpha - 2008-06-20
7101 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
7102 make it easier to set up your own private Tor network; fixes several
7103 big bugs with using more than one bridge relay; fixes a big bug with
7104 offering hidden services quickly after Tor starts; and uses a better
7105 API for reporting potential bootstrapping problems to the controller.
7108 - New TestingTorNetwork config option to allow adjustment of
7109 previously constant values that, while reasonable, could slow
7110 bootstrapping. Implements proposal 135. Patch from Karsten.
7113 - If you have more than one bridge but don't know their digests,
7114 you would only learn a request for the descriptor of the first one
7115 on your list. (Tor considered launching requests for the others, but
7116 found that it already had a connection on the way for $0000...0000
7117 so it didn't open another.) Bugfix on 0.2.0.x.
7118 - If you have more than one bridge but don't know their digests,
7119 and the connection to one of the bridges failed, you would cancel
7120 all pending bridge connections. (After all, they all have the
7121 same digest.) Bugfix on 0.2.0.x.
7122 - When establishing a hidden service, introduction points that
7123 originate from cannibalized circuits are completely ignored and not
7124 included in rendezvous service descriptors. This might be another
7125 reason for delay in making a hidden service available. Bugfix
7126 from long ago (0.0.9.x?)
7129 - Allow OpenSSL to use dynamic locks if it wants.
7130 - When building a consensus, do not include routers that are down.
7131 This will cut down 30% to 40% on consensus size. Implements
7133 - In directory authorities' approved-routers files, allow
7134 fingerprints with or without space.
7135 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
7136 controller can query our current bootstrap state in case it attaches
7137 partway through and wants to catch up.
7138 - Send an initial "Starting" bootstrap status event, so we have a
7139 state to start out in.
7142 - Asking for a conditional consensus at .../consensus/<fingerprints>
7143 would crash a dirserver if it did not already have a
7144 consensus. Bugfix on 0.2.1.1-alpha.
7145 - Clean up some macro/CPP interactions: some GCC versions don't like
7146 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
7149 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
7150 - Directory authorities shouldn't complain about bootstrapping
7151 problems just because they do a lot of reachability testing and
7152 some of the connection attempts fail.
7153 - Start sending "count" and "recommendation" key/value pairs in
7154 bootstrap problem status events, so the controller can hear about
7155 problems even before Tor decides they're worth reporting for sure.
7156 - If you're using bridges, generate "bootstrap problem" warnings
7157 as soon as you run out of working bridges, rather than waiting
7158 for ten failures -- which will never happen if you have less than
7160 - If we close our OR connection because there's been a circuit
7161 pending on it for too long, we were telling our bootstrap status
7162 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
7165 Changes in version 0.2.1.1-alpha - 2008-06-13
7166 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
7167 were making the Tor process bloat especially on Linux; makes our TLS
7168 handshake blend in better; sends "bootstrap phase" status events to
7169 the controller, so it can keep the user informed of progress (and
7170 problems) fetching directory information and establishing circuits;
7171 and adds a variety of smaller features.
7174 - More work on making our TLS handshake blend in: modify the list
7175 of ciphers advertised by OpenSSL in client mode to even more
7176 closely resemble a common web browser. We cheat a little so that
7177 we can advertise ciphers that the locally installed OpenSSL doesn't
7179 - Start sending "bootstrap phase" status events to the controller,
7180 so it can keep the user informed of progress fetching directory
7181 information and establishing circuits. Also inform the controller
7182 if we think we're stuck at a particular bootstrap phase. Implements
7184 - Resume using OpenSSL's RAND_poll() for better (and more portable)
7185 cross-platform entropy collection again. We used to use it, then
7186 stopped using it because of a bug that could crash systems that
7187 called RAND_poll when they had a lot of fds open. It looks like the
7188 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
7189 at startup, and to call RAND_poll() when we reseed later only if
7190 we have a non-buggy OpenSSL version.
7193 - When we choose to abandon a new entry guard because we think our
7194 older ones might be better, close any circuits pending on that
7195 new entry guard connection. This fix should make us recover much
7196 faster when our network is down and then comes back. Bugfix on
7197 0.1.2.8-beta; found by lodger.
7199 o Memory fixes and improvements:
7200 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
7201 to avoid unused RAM in buffer chunks and memory pools.
7202 - Speed up parsing and cut down on memory fragmentation by using
7203 stack-style allocations for parsing directory objects. Previously,
7204 this accounted for over 40% of allocations from within Tor's code
7205 on a typical directory cache.
7206 - Use a Bloom filter rather than a digest-based set to track which
7207 descriptors we need to keep around when we're cleaning out old
7208 router descriptors. This speeds up the computation significantly,
7209 and may reduce fragmentation.
7210 - Reduce the default smartlist size from 32 to 16; it turns out that
7211 most smartlists hold around 8-12 elements tops.
7212 - Make dumpstats() log the fullness and size of openssl-internal
7214 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
7215 patch to their OpenSSL, turn it on to save memory on servers. This
7216 patch will (with any luck) get included in a mainline distribution
7218 - Never use OpenSSL compression: it wastes RAM and CPU trying to
7219 compress cells, which are basically all encrypted, compressed,
7223 - Stop reloading the router list from disk for no reason when we
7224 run out of reachable directory mirrors. Once upon a time reloading
7225 it would set the 'is_running' flag back to 1 for them. It hasn't
7226 done that for a long time.
7227 - In very rare situations new hidden service descriptors were
7228 published earlier than 30 seconds after the last change to the
7229 service. (We currently think that a hidden service descriptor
7230 that's been stable for 30 seconds is worth publishing.)
7233 - Allow separate log levels to be configured for different logging
7234 domains. For example, this allows one to log all notices, warnings,
7235 or errors, plus all memory management messages of level debug or
7236 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
7237 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
7238 and stop using a warning that had become unfixably verbose under
7240 - New --hush command-line option similar to --quiet. While --quiet
7241 disables all logging to the console on startup, --hush limits the
7242 output to messages of warning and error severity.
7243 - Servers support a new URL scheme for consensus downloads that
7244 allows the client to specify which authorities are trusted.
7245 The server then only sends the consensus if the client will trust
7246 it. Otherwise a 404 error is sent back. Clients use this
7247 new scheme when the server supports it (meaning it's running
7248 0.2.1.1-alpha or later). Implements proposal 134.
7249 - New configure/torrc options (--enable-geoip-stats,
7250 DirRecordUsageByCountry) to record how many IPs we've served
7251 directory info to in each country code, how many status documents
7252 total we've sent to each country code, and what share of the total
7253 directory requests we should expect to see.
7254 - Use the TLS1 hostname extension to more closely resemble browser
7256 - Lots of new unit tests.
7257 - Add a macro to implement the common pattern of iterating through
7258 two parallel lists in lockstep.
7261 Changes in version 0.2.0.28-rc - 2008-06-13
7262 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
7263 performance bug, and fixes a bunch of smaller bugs.
7266 - Fix a bug where, when we were choosing the 'end stream reason' to
7267 put in our relay end cell that we send to the exit relay, Tor
7268 clients on Windows were sometimes sending the wrong 'reason'. The
7269 anonymity problem is that exit relays may be able to guess whether
7270 the client is running Windows, thus helping partition the anonymity
7271 set. Down the road we should stop sending reasons to exit relays,
7272 or otherwise prevent future versions of this bug.
7275 - While setting up a hidden service, some valid introduction circuits
7276 were overlooked and abandoned. This might be the reason for
7277 the long delay in making a hidden service available. Bugfix on
7281 - Update to the "June 9 2008" ip-to-country file.
7282 - Run 'make test' as part of 'make dist', so we stop releasing so
7283 many development snapshots that fail their unit tests.
7286 - When we're checking if we have enough dir info for each relay
7287 to begin establishing circuits, make sure that we actually have
7288 the descriptor listed in the consensus, not just any descriptor.
7290 - Bridge relays no longer print "xx=0" in their extrainfo document
7291 for every single country code in the geoip db. Bugfix on
7293 - Only warn when we fail to load the geoip file if we were planning to
7294 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
7295 - If we change our MaxAdvertisedBandwidth and then reload torrc,
7296 Tor won't realize it should publish a new relay descriptor. Fixes
7297 bug 688, reported by mfr. Bugfix on 0.1.2.x.
7298 - When we haven't had any application requests lately, don't bother
7299 logging that we have expired a bunch of descriptors. Bugfix
7301 - Make relay cells written on a connection count as non-padding when
7302 tracking how long a connection has been in use. Bugfix on
7303 0.2.0.1-alpha. Spotted by lodger.
7304 - Fix unit tests in 0.2.0.27-rc.
7305 - Fix compile on Windows.
7308 Changes in version 0.2.0.27-rc - 2008-06-03
7309 Tor 0.2.0.27-rc adds a few features we left out of the earlier
7310 release candidates. In particular, we now include an IP-to-country
7311 GeoIP database, so controllers can easily look up what country a
7312 given relay is in, and so bridge relays can give us some sanitized
7313 summaries about which countries are making use of bridges. (See proposal
7314 126-geoip-fetching.txt for details.)
7317 - Include an IP-to-country GeoIP file in the tarball, so bridge
7318 relays can report sanitized summaries of the usage they're seeing.
7321 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
7322 Robert Hogan. Fixes the first part of bug 681.
7323 - Make bridge authorities never serve extrainfo docs.
7324 - Add support to detect Libevent versions in the 1.4.x series
7326 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
7327 - Include a new contrib/tor-exit-notice.html file that exit relay
7328 operators can put on their website to help reduce abuse queries.
7331 - When tunneling an encrypted directory connection, and its first
7332 circuit fails, do not leave it unattached and ask the controller
7333 to deal. Fixes the second part of bug 681.
7334 - Make bridge authorities correctly expire old extrainfo documents
7338 Changes in version 0.2.0.26-rc - 2008-05-13
7339 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
7340 in Debian's OpenSSL packages. All users running any 0.2.0.x version
7341 should upgrade, whether they're running Debian or not.
7343 o Major security fixes:
7344 - Use new V3 directory authority keys on the tor26, gabelmoo, and
7345 moria1 V3 directory authorities. The old keys were generated with
7346 a vulnerable version of Debian's OpenSSL package, and must be
7347 considered compromised. Other authorities' keys were not generated
7348 with an affected version of OpenSSL.
7351 - List authority signatures as "unrecognized" based on DirServer
7352 lines, not on cert cache. Bugfix on 0.2.0.x.
7355 - Add a new V3AuthUseLegacyKey option to make it easier for
7356 authorities to change their identity keys if they have to.
7359 Changes in version 0.2.0.25-rc - 2008-04-23
7360 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
7363 - Remember to initialize threading before initializing logging.
7364 Otherwise, many BSD-family implementations will crash hard on
7365 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
7368 - Authorities correctly free policies on bad servers on
7369 exit. Fixes bug 672. Bugfix on 0.2.0.x.
7372 Changes in version 0.2.0.24-rc - 2008-04-22
7373 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
7374 v3 directory authority, makes relays with dynamic IP addresses and no
7375 DirPort notice more quickly when their IP address changes, fixes a few
7376 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
7378 o New directory authorities:
7379 - Take lefkada out of the list of v3 directory authorities, since
7380 it has been down for months.
7381 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
7385 - Detect address changes more quickly on non-directory mirror
7386 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
7388 o Minor features (security):
7389 - Reject requests for reverse-dns lookup of names that are in
7390 a private address space. Patch from lodger.
7391 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
7394 o Minor bugfixes (crashes):
7395 - Avoid a rare assert that can trigger when Tor doesn't have much
7396 directory information yet and it tries to fetch a v2 hidden
7397 service descriptor. Fixes bug 651, reported by nwf.
7398 - Initialize log mutex before initializing dmalloc. Otherwise,
7399 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
7400 - Use recursive pthread mutexes in order to avoid deadlock when
7401 logging debug-level messages to a controller. Bug spotted by nwf,
7402 bugfix on 0.2.0.16-alpha.
7404 o Minor bugfixes (resource management):
7405 - Keep address policies from leaking memory: start their refcount
7406 at 1, not 2. Bugfix on 0.2.0.16-alpha.
7407 - Free authority certificates on exit, so they don't look like memory
7408 leaks. Bugfix on 0.2.0.19-alpha.
7409 - Free static hashtables for policy maps and for TLS connections on
7410 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
7411 - Avoid allocating extra space when computing consensuses on 64-bit
7412 platforms. Bug spotted by aakova.
7414 o Minor bugfixes (misc):
7415 - Do not read the configuration file when we've only been told to
7416 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
7417 based on patch from Sebastian Hahn.
7418 - Exit relays that are used as a client can now reach themselves
7419 using the .exit notation, rather than just launching an infinite
7420 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
7421 - When attempting to open a logfile fails, tell us why.
7422 - Fix a dumb bug that was preventing us from knowing that we should
7423 preemptively build circuits to handle expected directory requests.
7424 Fixes bug 660. Bugfix on 0.1.2.x.
7425 - Warn less verbosely about clock skew from netinfo cells from
7426 untrusted sources. Fixes bug 663.
7427 - Make controller stream events for DNS requests more consistent,
7428 by adding "new stream" events for DNS requests, and removing
7429 spurious "stream closed" events" for cached reverse resolves.
7430 Patch from mwenge. Fixes bug 646.
7431 - Correctly notify one-hop connections when a circuit build has
7432 failed. Possible fix for bug 669. Found by lodger.
7435 Changes in version 0.2.0.23-rc - 2008-03-24
7436 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
7437 makes bootstrapping faster if the first directory mirror you contact
7438 is down. The bundles also include the new Vidalia 0.1.2 release.
7441 - When a tunneled directory request is made to a directory server
7442 that's down, notice after 30 seconds rather than 120 seconds. Also,
7443 fail any begindir streams that are pending on it, so they can
7444 retry elsewhere. This was causing multi-minute delays on bootstrap.
7447 Changes in version 0.2.0.22-rc - 2008-03-18
7448 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
7449 enables encrypted directory connections by default for non-relays, fixes
7450 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
7451 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
7454 - Enable encrypted directory connections by default for non-relays,
7455 so censor tools that block Tor directory connections based on their
7456 plaintext patterns will no longer work. This means Tor works in
7457 certain censored countries by default again.
7460 - Make sure servers always request certificates from clients during
7461 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
7462 - Do not enter a CPU-eating loop when a connection is closed in
7463 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
7464 diagnosed by lodger; bugfix on 0.2.0.20-rc.
7465 - Fix assertion failure that could occur when a blocked circuit
7466 became unblocked, and it had pending client DNS requests. Bugfix
7467 on 0.2.0.1-alpha. Fixes bug 632.
7469 o Minor bugfixes (on 0.1.2.x):
7470 - Generate "STATUS_SERVER" events rather than misspelled
7471 "STATUS_SEVER" events. Caught by mwenge.
7472 - When counting the number of bytes written on a TLS connection,
7473 look at the BIO actually used for writing to the network, not
7474 at the BIO used (sometimes) to buffer data for the network.
7475 Looking at different BIOs could result in write counts on the
7476 order of ULONG_MAX. Fixes bug 614.
7477 - On Windows, correctly detect errors when listing the contents of
7478 a directory. Fix from lodger.
7480 o Minor bugfixes (on 0.2.0.x):
7481 - Downgrade "sslv3 alert handshake failure" message to INFO.
7482 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
7483 left BandwidthRate and BandwidthBurst at the default, we would be
7484 silently limited by those defaults. Now raise them to match the
7485 RelayBandwidth* values.
7486 - Fix the SVK version detection logic to work correctly on a branch.
7487 - Make --enable-openbsd-malloc work correctly on Linux with alpha
7488 CPUs. Fixes bug 625.
7489 - Logging functions now check that the passed severity is sane.
7490 - Use proper log levels in the testsuite call of
7491 get_interface_address6().
7492 - When using a nonstandard malloc, do not use the platform values for
7493 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
7494 - Make the openbsd malloc code use 8k pages on alpha CPUs and
7496 - Detect mismatched page sizes when using --enable-openbsd-malloc.
7497 - Avoid double-marked-for-close warning when certain kinds of invalid
7498 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
7499 for bug 617. Bugfix on 0.2.0.1-alpha.
7500 - Make sure that the "NULL-means-reject *:*" convention is followed by
7501 all the policy manipulation functions, avoiding some possible crash
7502 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
7503 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
7504 actually works, and doesn't warn about every single reverse lookup.
7505 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
7508 - Only log guard node status when guard node status has changed.
7509 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
7510 make "INFO" 75% less verbose.
7513 Changes in version 0.2.0.21-rc - 2008-03-02
7514 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
7515 makes Tor work well with Vidalia again, fixes a rare assert bug,
7516 and fixes a pair of more minor bugs. The bundles also include Vidalia
7517 0.1.0 and Torbutton 1.1.16.
7520 - The control port should declare that it requires password auth
7521 when HashedControlSessionPassword is set too. Patch from Matt Edman;
7522 bugfix on 0.2.0.20-rc. Fixes bug 615.
7523 - Downgrade assert in connection_buckets_decrement() to a log message.
7524 This may help us solve bug 614, and in any case will make its
7525 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
7526 - We were sometimes miscounting the number of bytes read from the
7527 network, causing our rate limiting to not be followed exactly.
7528 Bugfix on 0.2.0.16-alpha. Reported by lodger.
7531 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
7532 OpenSSL versions should have been working fine. Diagnosis and patch
7533 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
7534 Bugfix on 0.2.0.20-rc.
7537 Changes in version 0.2.0.20-rc - 2008-02-24
7538 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
7539 makes more progress towards normalizing Tor's TLS handshake, makes
7540 hidden services work better again, helps relays bootstrap if they don't
7541 know their IP address, adds optional support for linking in openbsd's
7542 allocator or tcmalloc, allows really fast relays to scale past 15000
7543 sockets, and fixes a bunch of minor bugs reported by Veracode.
7546 - Enable the revised TLS handshake based on the one designed by
7547 Steven Murdoch in proposal 124, as revised in proposal 130. It
7548 includes version negotiation for OR connections as described in
7549 proposal 105. The new handshake is meant to be harder for censors
7550 to fingerprint, and it adds the ability to detect certain kinds of
7551 man-in-the-middle traffic analysis attacks. The version negotiation
7552 feature will allow us to improve Tor's link protocol more safely
7554 - Choose which bridge to use proportional to its advertised bandwidth,
7555 rather than uniformly at random. This should speed up Tor for
7556 bridge users. Also do this for people who set StrictEntryNodes.
7557 - When a TrackHostExits-chosen exit fails too many times in a row,
7558 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
7561 - Resolved problems with (re-)fetching hidden service descriptors.
7562 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
7564 - If we only ever used Tor for hidden service lookups or posts, we
7565 would stop building circuits and start refusing connections after
7566 24 hours, since we falsely believed that Tor was dormant. Reported
7567 by nwf; bugfix on 0.1.2.x.
7568 - Servers that don't know their own IP address should go to the
7569 authorities for their first directory fetch, even if their DirPort
7570 is off or if they don't know they're reachable yet. This will help
7571 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
7572 - When counting the number of open sockets, count not only the number
7573 of sockets we have received from the socket() call, but also
7574 the number we've gotten from accept() and socketpair(). This bug
7575 made us fail to count all sockets that we were using for incoming
7576 connections. Bugfix on 0.2.0.x.
7577 - Fix code used to find strings within buffers, when those strings
7578 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
7579 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
7580 - Add a new __HashedControlSessionPassword option for controllers
7581 to use for one-off session password hashes that shouldn't get
7582 saved to disk by SAVECONF --- Vidalia users were accumulating a
7583 pile of HashedControlPassword lines in their torrc files, one for
7584 each time they had restarted Tor and then clicked Save. Make Tor
7585 automatically convert "HashedControlPassword" to this new option but
7586 only when it's given on the command line. Partial fix for bug 586.
7588 o Minor features (performance):
7589 - Tune parameters for cell pool allocation to minimize amount of
7591 - Add OpenBSD malloc code from phk as an optional malloc
7592 replacement on Linux: some glibc libraries do very poorly
7593 with Tor's memory allocation patterns. Pass
7594 --enable-openbsd-malloc to get the replacement malloc code.
7595 - Add a --with-tcmalloc option to the configure script to link
7596 against tcmalloc (if present). Does not yet search for
7597 non-system include paths.
7598 - Stop imposing an arbitrary maximum on the number of file descriptors
7599 used for busy servers. Bug reported by Olaf Selke; patch from
7602 o Minor features (other):
7603 - When SafeLogging is disabled, log addresses along with all TLS
7605 - When building with --enable-gcc-warnings, check for whether Apple's
7606 warning "-Wshorten-64-to-32" is available.
7607 - Add a --passphrase-fd argument to the tor-gencert command for
7610 o Minor bugfixes (memory leaks and code problems):
7611 - We were leaking a file descriptor if Tor started with a zero-length
7612 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
7613 - Detect size overflow in zlib code. Reported by Justin Ferguson and
7615 - We were comparing the raw BridgePassword entry with a base64'ed
7616 version of it, when handling a "/tor/networkstatus-bridges"
7617 directory request. Now compare correctly. Noticed by Veracode.
7618 - Recover from bad tracked-since value in MTBF-history file.
7620 - Alter the code that tries to recover from unhandled write
7621 errors, to not try to flush onto a socket that's given us
7622 unhandled errors. Bugfix on 0.1.2.x.
7623 - Make Unix controlsockets work correctly on OpenBSD. Patch from
7624 tup. Bugfix on 0.2.0.3-alpha.
7626 o Minor bugfixes (other):
7627 - If we have an extra-info document for our server, always make
7628 it available on the control port, even if we haven't gotten
7629 a copy of it from an authority yet. Patch from mwenge.
7630 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
7631 - Directory mirrors no longer include a guess at the client's IP
7632 address if the connection appears to be coming from the same /24
7633 network; it was producing too many wrong guesses.
7634 - Make the new hidden service code respect the SafeLogging setting.
7635 Bugfix on 0.2.0.x. Patch from Karsten.
7636 - When starting as an authority, do not overwrite all certificates
7637 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
7638 - If we're trying to flush the last bytes on a connection (for
7639 example, when answering a directory request), reset the
7640 time-to-give-up timeout every time we manage to write something
7641 on the socket. Bugfix on 0.1.2.x.
7642 - Change the behavior of "getinfo status/good-server-descriptor"
7643 so it doesn't return failure when any authority disappears.
7644 - Even though the man page said that "TrackHostExits ." should
7645 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
7646 - Report TLS "zero return" case as a "clean close" and "IO error"
7647 as a "close". Stop calling closes "unexpected closes": existing
7648 Tors don't use SSL_close(), so having a connection close without
7649 the TLS shutdown handshake is hardly unexpected.
7650 - Send NAMESERVER_STATUS messages for a single failed nameserver
7653 o Code simplifications and refactoring:
7654 - Remove the tor_strpartition function: its logic was confused,
7655 and it was only used for one thing that could be implemented far
7659 Changes in version 0.2.0.19-alpha - 2008-02-09
7660 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
7661 handshake, makes path selection for relays more secure and IP address
7662 guessing more robust, and generally fixes a lot of bugs in preparation
7663 for calling the 0.2.0 branch stable.
7666 - Do not include recognizeable strings in the commonname part of
7667 Tor's x509 certificates.
7670 - If we're a relay, avoid picking ourselves as an introduction point,
7671 a rendezvous point, or as the final hop for internal circuits. Bug
7672 reported by taranis and lodger. Bugfix on 0.1.2.x.
7673 - Patch from "Andrew S. Lists" to catch when we contact a directory
7674 mirror at IP address X and he says we look like we're coming from
7675 IP address X. Bugfix on 0.1.2.x.
7677 o Minor features (security):
7678 - Be more paranoid about overwriting sensitive memory on free(),
7679 as a defensive programming tactic to ensure forward secrecy.
7681 o Minor features (directory authority):
7682 - Actually validate the options passed to AuthDirReject,
7683 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
7684 - Reject router descriptors with out-of-range bandwidthcapacity or
7685 bandwidthburst values.
7687 o Minor features (controller):
7688 - Reject controller commands over 1MB in length. This keeps rogue
7689 processes from running us out of memory.
7691 o Minor features (misc):
7692 - Give more descriptive well-formedness errors for out-of-range
7693 hidden service descriptor/protocol versions.
7694 - Make memory debugging information describe more about history
7695 of cell allocation, so we can help reduce our memory use.
7697 o Deprecated features (controller):
7698 - The status/version/num-versioning and status/version/num-concurring
7699 GETINFO options are no longer useful in the v3 directory protocol:
7700 treat them as deprecated, and warn when they're used.
7703 - When our consensus networkstatus has been expired for a while, stop
7704 being willing to build circuits using it. Fixes bug 401. Bugfix
7706 - Directory caches now fetch certificates from all authorities
7707 listed in a networkstatus consensus, even when they do not
7708 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
7709 - When connecting to a bridge without specifying its key, insert
7710 the connection into the identity-to-connection map as soon as
7711 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
7712 - Detect versions of OS X where malloc_good_size() is present in the
7713 library but never actually declared. Resolves bug 587. Bugfix
7715 - Stop incorrectly truncating zlib responses to directory authority
7716 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
7717 - Stop recommending that every server operator send mail to tor-ops.
7718 Resolves bug 597. Bugfix on 0.1.2.x.
7719 - Don't trigger an assert if we start a directory authority with a
7720 private IP address (like 127.0.0.1).
7721 - Avoid possible failures when generating a directory with routers
7722 with over-long versions strings, or too many flags set. Bugfix
7724 - If an attempt to launch a DNS resolve request over the control
7725 port fails because we have overrun the limit on the number of
7726 connections, tell the controller that the request has failed.
7727 - Avoid using too little bandwidth when our clock skips a few
7728 seconds. Bugfix on 0.1.2.x.
7729 - Fix shell error when warning about missing packages in configure
7730 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
7731 - Do not become confused when receiving a spurious VERSIONS-like
7732 cell from a confused v1 client. Bugfix on 0.2.0.x.
7733 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
7734 introduction points for a hidden service have failed. Patch from
7735 Karsten Loesing. Bugfix on 0.2.0.x.
7737 o Code simplifications and refactoring:
7738 - Remove some needless generality from cpuworker code, for improved
7740 - Stop overloading the circuit_t.onionskin field for both "onionskin
7741 from a CREATE cell that we are waiting for a cpuworker to be
7742 assigned" and "onionskin from an EXTEND cell that we are going to
7743 send to an OR as soon as we are connected". Might help with bug 600.
7744 - Add an in-place version of aes_crypt() so that we can avoid doing a
7745 needless memcpy() call on each cell payload.
7748 Changes in version 0.2.0.18-alpha - 2008-01-25
7749 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
7750 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
7751 that can warn or reject connections to ports generally associated with
7752 vulnerable-plaintext protocols.
7754 o New directory authorities:
7755 - Set up dannenberg (run by CCC) as the sixth v3 directory
7759 - Fix a major memory leak when attempting to use the v2 TLS
7760 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
7761 - We accidentally enabled the under-development v2 TLS handshake
7762 code, which was causing log entries like "TLS error while
7763 renegotiating handshake". Disable it again. Resolves bug 590.
7764 - We were computing the wrong Content-Length: header for directory
7765 responses that need to be compressed on the fly, causing clients
7766 asking for those items to always fail. Bugfix on 0.2.0.x; partially
7770 - Avoid going directly to the directory authorities even if you're a
7771 relay, if you haven't found yourself reachable yet or if you've
7772 decided not to advertise your dirport yet. Addresses bug 556.
7773 - If we've gone 12 hours since our last bandwidth check, and we
7774 estimate we have less than 50KB bandwidth capacity but we could
7775 handle more, do another bandwidth test.
7776 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
7777 Tor can warn and/or refuse connections to ports commonly used with
7778 vulnerable-plaintext protocols. Currently we warn on ports 23,
7779 109, 110, and 143, but we don't reject any.
7782 - When we setconf ClientOnly to 1, close any current OR and Dir
7783 listeners. Reported by mwenge.
7784 - When we get a consensus that's been signed by more people than
7785 we expect, don't log about it; it's not a big deal. Reported
7789 - Don't answer "/tor/networkstatus-bridges" directory requests if
7790 the request isn't encrypted.
7791 - Make "ClientOnly 1" config option disable directory ports too.
7792 - Patches from Karsten Loesing to make v2 hidden services more
7793 robust: work even when there aren't enough HSDir relays available;
7794 retry when a v2 rend desc fetch fails; but don't retry if we
7795 already have a usable v0 rend desc.
7798 Changes in version 0.2.0.17-alpha - 2008-01-17
7799 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
7802 - Make the tor-gencert man page get included correctly in the tarball.
7805 Changes in version 0.2.0.16-alpha - 2008-01-17
7806 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
7807 Loesing, and generally cleans up a lot of features and minor bugs.
7809 o New directory authorities:
7810 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
7813 o Major performance improvements:
7814 - Switch our old ring buffer implementation for one more like that
7815 used by free Unix kernels. The wasted space in a buffer with 1mb
7816 of data will now be more like 8k than 1mb. The new implementation
7817 also avoids realloc();realloc(); patterns that can contribute to
7818 memory fragmentation.
7821 - Configuration files now accept C-style strings as values. This
7822 helps encode characters not allowed in the current configuration
7823 file format, such as newline or #. Addresses bug 557.
7824 - Although we fixed bug 539 (where servers would send HTTP status 503
7825 responses _and_ send a body too), there are still servers out
7826 there that haven't upgraded. Therefore, make clients parse such
7827 bodies when they receive them.
7828 - When we're not serving v2 directory information, there is no reason
7829 to actually keep any around. Remove the obsolete files and directory
7830 on startup if they are very old and we aren't going to serve them.
7832 o Minor performance improvements:
7833 - Reference-count and share copies of address policy entries; only 5%
7834 of them were actually distinct.
7835 - Never walk through the list of logs if we know that no log is
7836 interested in a given message.
7839 - When an authority has not signed a consensus, do not try to
7840 download a nonexistent "certificate with key 00000000". Bugfix
7841 on 0.2.0.x. Fixes bug 569.
7842 - Fix a rare assert error when we're closing one of our threads:
7843 use a mutex to protect the list of logs, so we never write to the
7844 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
7845 bug 575, which is kind of the revenge of bug 222.
7846 - Patch from Karsten Loesing to complain less at both the client
7847 and the relay when a relay used to have the HSDir flag but doesn't
7848 anymore, and we try to upload a hidden service descriptor.
7849 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
7851 - Do not try to download missing certificates until we have tried
7852 to check our fallback consensus. Fixes bug 583.
7853 - Make bridges round reported GeoIP stats info up to the nearest
7854 estimate, not down. Now we can distinguish between "0 people from
7855 this country" and "1 person from this country".
7856 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
7857 - Avoid possible segfault if key generation fails in
7858 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
7859 - Avoid segfault in the case where a badly behaved v2 versioning
7860 directory sends a signed networkstatus with missing client-versions.
7862 - Avoid segfaults on certain complex invocations of
7863 router_get_by_hexdigest(). Bugfix on 0.1.2.
7864 - Correct bad index on array access in parse_http_time(). Bugfix
7866 - Fix possible bug in vote generation when server versions are present
7867 but client versions are not.
7868 - Fix rare bug on REDIRECTSTREAM control command when called with no
7869 port set: it could erroneously report an error when none had
7871 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
7872 compressing large objects and find ourselves with more than 4k
7873 left over. Bugfix on 0.2.0.
7874 - Fix a small memory leak when setting up a hidden service.
7875 - Fix a few memory leaks that could in theory happen under bizarre
7877 - Fix an assert if we post a general-purpose descriptor via the
7878 control port but that descriptor isn't mentioned in our current
7879 network consensus. Bug reported by Jon McLachlan; bugfix on
7882 o Minor features (controller):
7883 - Get NS events working again. Patch from tup.
7884 - The GETCONF command now escapes and quotes configuration values
7885 that don't otherwise fit into the torrc file.
7886 - The SETCONF command now handles quoted values correctly.
7888 o Minor features (directory authorities):
7889 - New configuration options to override default maximum number of
7890 servers allowed on a single IP address. This is important for
7891 running a test network on a single host.
7892 - Actually implement the -s option to tor-gencert.
7893 - Add a manual page for tor-gencert.
7895 o Minor features (bridges):
7896 - Bridge authorities no longer serve bridge descriptors over
7897 unencrypted connections.
7899 o Minor features (other):
7900 - Add hidden services and DNSPorts to the list of things that make
7901 Tor accept that it has running ports. Change starting Tor with no
7902 ports from a fatal error to a warning; we might change it back if
7903 this turns out to confuse anybody. Fixes bug 579.
7906 Changes in version 0.1.2.19 - 2008-01-17
7907 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
7908 exit policy a little bit more conservative so it's safer to run an
7909 exit relay on a home system, and fixes a variety of smaller issues.
7912 - Exit policies now reject connections that are addressed to a
7913 relay's public (external) IP address too, unless
7914 ExitPolicyRejectPrivate is turned off. We do this because too
7915 many relays are running nearby to services that trust them based
7919 - When the clock jumps forward a lot, do not allow the bandwidth
7920 buckets to become negative. Fixes bug 544.
7921 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7922 on every successful resolve. Reported by Mike Perry.
7923 - Purge old entries from the "rephist" database and the hidden
7924 service descriptor database even when DirPort is zero.
7925 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7926 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7927 crashing or mis-answering these requests.
7928 - When we decide to send a 503 response to a request for servers, do
7929 not then also send the server descriptors: this defeats the whole
7930 purpose. Fixes bug 539.
7933 - Changing the ExitPolicyRejectPrivate setting should cause us to
7934 rebuild our server descriptor.
7935 - Fix handling of hex nicknames when answering controller requests for
7936 networkstatus by name, or when deciding whether to warn about
7937 unknown routers in a config option. (Patch from mwenge.)
7938 - Fix a couple of hard-to-trigger autoconf problems that could result
7939 in really weird results on platforms whose sys/types.h files define
7940 nonstandard integer types.
7941 - Don't try to create the datadir when running --verify-config or
7942 --hash-password. Resolves bug 540.
7943 - If we were having problems getting a particular descriptor from the
7944 directory caches, and then we learned about a new descriptor for
7945 that router, we weren't resetting our failure count. Reported
7947 - Although we fixed bug 539 (where servers would send HTTP status 503
7948 responses _and_ send a body too), there are still servers out there
7949 that haven't upgraded. Therefore, make clients parse such bodies
7950 when they receive them.
7951 - Run correctly on systems where rlim_t is larger than unsigned long.
7952 This includes some 64-bit systems.
7953 - Run correctly on platforms (like some versions of OS X 10.5) where
7954 the real limit for number of open files is OPEN_FILES, not rlim_max
7955 from getrlimit(RLIMIT_NOFILES).
7956 - Avoid a spurious free on base64 failure.
7957 - Avoid segfaults on certain complex invocations of
7958 router_get_by_hexdigest().
7959 - Fix rare bug on REDIRECTSTREAM control command when called with no
7960 port set: it could erroneously report an error when none had
7964 Changes in version 0.2.0.15-alpha - 2007-12-25
7965 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
7966 features added in 0.2.0.13-alpha.
7969 - Fix several remotely triggerable asserts based on DirPort requests
7970 for a v2 or v3 networkstatus object before we were prepared. This
7971 was particularly bad for 0.2.0.13 and later bridge relays, who
7972 would never have a v2 networkstatus and would thus always crash
7973 when used. Bugfixes on 0.2.0.x.
7974 - Estimate the v3 networkstatus size more accurately, rather than
7975 estimating it at zero bytes and giving it artificially high priority
7976 compared to other directory requests. Bugfix on 0.2.0.x.
7979 - Fix configure.in logic for cross-compilation.
7980 - When we load a bridge descriptor from the cache, and it was
7981 previously unreachable, mark it as retriable so we won't just
7982 ignore it. Also, try fetching a new copy immediately. Bugfixes
7984 - The bridge GeoIP stats were counting other relays, for example
7985 self-reachability and authority-reachability tests.
7988 - Support compilation to target iPhone; patch from cjacker huang.
7989 To build for iPhone, pass the --enable-iphone option to configure.
7992 Changes in version 0.2.0.14-alpha - 2007-12-23
7994 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
7995 without a datadirectory from a previous Tor install. Reported
7997 - Fix a crash when we fetch a descriptor that turns out to be
7998 unexpected (it used to be in our networkstatus when we started
7999 fetching it, but it isn't in our current networkstatus), and we
8000 aren't using bridges. Bugfix on 0.2.0.x.
8001 - Fix a crash when accessing hidden services: it would work the first
8002 time you use a given introduction point for your service, but
8003 on subsequent requests we'd be using garbage memory. Fixed by
8004 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
8005 - Fix a crash when we load a bridge descriptor from disk but we don't
8006 currently have a Bridge line for it in our torrc. Bugfix on
8010 - If bridge authorities set BridgePassword, they will serve a
8011 snapshot of known bridge routerstatuses from their DirPort to
8012 anybody who knows that password. Unset by default.
8015 - Make the unit tests build again.
8016 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
8017 - Make PublishServerDescriptor default to 1, so the default doesn't
8018 have to change as we invent new directory protocol versions.
8019 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
8020 be included unless sys/time.h is already included. Fixes
8021 bug 553. Bugfix on 0.2.0.x.
8022 - If we receive a general-purpose descriptor and then receive an
8023 identical bridge-purpose descriptor soon after, don't discard
8024 the next one as a duplicate.
8027 - If BridgeRelay is set to 1, then the default for
8028 PublishServerDescriptor is now "bridge" rather than "v2,v3".
8029 - If the user sets RelayBandwidthRate but doesn't set
8030 RelayBandwidthBurst, then make them equal rather than erroring out.
8033 Changes in version 0.2.0.13-alpha - 2007-12-21
8034 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
8035 Goodell, fixes many more bugs, and adds a lot of infrastructure for
8038 o New directory authorities:
8039 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
8043 - Only update guard status (usable / not usable) once we have
8044 enough directory information. This was causing us to always pick
8045 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
8046 causing us to discard all our guards on startup if we hadn't been
8047 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
8048 - Purge old entries from the "rephist" database and the hidden
8049 service descriptor databases even when DirPort is zero. Bugfix
8051 - We were ignoring our RelayBandwidthRate for the first 30 seconds
8052 after opening a circuit -- even a relayed circuit. Bugfix on
8054 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
8055 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
8056 crashing or mis-answering these types of requests.
8057 - Relays were publishing their server descriptor to v1 and v2
8058 directory authorities, but they didn't try publishing to v3-only
8059 authorities. Fix this; and also stop publishing to v1 authorities.
8061 - When we were reading router descriptors from cache, we were ignoring
8062 the annotations -- so for example we were reading in bridge-purpose
8063 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
8064 - When we decided to send a 503 response to a request for servers, we
8065 were then also sending the server descriptors: this defeats the
8066 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
8069 - Bridge relays now behave like clients with respect to time
8070 intervals for downloading new consensus documents -- otherwise they
8071 stand out. Bridge users now wait until the end of the interval,
8072 so their bridge relay will be sure to have a new consensus document.
8073 - Three new config options (AlternateDirAuthority,
8074 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
8075 user selectively replace the default directory authorities by type,
8076 rather than the all-or-nothing replacement that DirServer offers.
8077 - Tor can now be configured to read a GeoIP file from disk in one
8078 of two formats. This can be used by controllers to map IP addresses
8079 to countries. Eventually, it may support exit-by-country.
8080 - When possible, bridge relays remember which countries users
8081 are coming from, and report aggregate information in their
8082 extra-info documents, so that the bridge authorities can learn
8083 where Tor is blocked.
8084 - Bridge directory authorities now do reachability testing on the
8085 bridges they know. They provide router status summaries to the
8086 controller via "getinfo ns/purpose/bridge", and also dump summaries
8087 to a file periodically.
8088 - Stop fetching directory info so aggressively if your DirPort is
8089 on but your ORPort is off; stop fetching v2 dir info entirely.
8090 You can override these choices with the new FetchDirInfoEarly
8094 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
8095 consensus documents when there are too many relays at a single
8096 IP address. Now clear it in v2 network status documents too, and
8097 also clear it in routerinfo_t when the relay is no longer listed
8098 in the relevant networkstatus document.
8099 - Don't crash if we get an unexpected value for the
8100 PublishServerDescriptor config option. Reported by Matt Edman;
8101 bugfix on 0.2.0.9-alpha.
8102 - Our new v2 hidden service descriptor format allows descriptors
8103 that have no introduction points. But Tor crashed when we tried
8104 to build a descriptor with no intro points (and it would have
8105 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
8107 - Fix building with dmalloc 5.5.2 with glibc.
8108 - Reject uploaded descriptors and extrainfo documents if they're
8109 huge. Otherwise we'll cache them all over the network and it'll
8110 clog everything up. Reported by Aljosha Judmayer.
8111 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
8112 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
8113 - When the DANGEROUS_VERSION controller status event told us we're
8114 running an obsolete version, it used the string "OLD" to describe
8115 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
8116 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
8117 - If we can't expand our list of entry guards (e.g. because we're
8118 using bridges or we have StrictEntryNodes set), don't mark relays
8119 down when they fail a directory request. Otherwise we're too quick
8120 to mark all our entry points down. Bugfix on 0.1.2.x.
8121 - Fix handling of hex nicknames when answering controller requests for
8122 networkstatus by name, or when deciding whether to warn about unknown
8123 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
8124 - Fix a couple of hard-to-trigger autoconf problems that could result
8125 in really weird results on platforms whose sys/types.h files define
8126 nonstandard integer types. Bugfix on 0.1.2.x.
8127 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
8128 - Don't crash on name lookup when we have no current consensus. Fixes
8129 bug 538; bugfix on 0.2.0.x.
8130 - Only Tors that want to mirror the v2 directory info should
8131 create the "cached-status" directory in their datadir. (All Tors
8132 used to create it.) Bugfix on 0.2.0.9-alpha.
8133 - Directory authorities should only automatically download Extra Info
8134 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
8137 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
8138 consumers. (We already do this on HUP.)
8139 - Authorities and caches fetch the v2 networkstatus documents
8140 less often, now that v3 is encouraged.
8141 - Add a new config option BridgeRelay that specifies you want to
8142 be a bridge relay. Right now the only difference is that it makes
8143 you answer begin_dir requests, and it makes you cache dir info,
8144 even if your DirPort isn't on.
8145 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
8146 ask about source, timestamp of arrival, purpose, etc. We need
8147 something like this to help Vidalia not do GeoIP lookups on bridge
8149 - Allow multiple HashedControlPassword config lines, to support
8150 multiple controller passwords.
8151 - Authorities now decide whether they're authoritative for a given
8152 router based on the router's purpose.
8153 - New config options AuthDirBadDir and AuthDirListBadDirs for
8154 authorities to mark certain relays as "bad directories" in the
8155 networkstatus documents. Also supports the "!baddir" directive in
8156 the approved-routers file.
8159 Changes in version 0.2.0.12-alpha - 2007-11-16
8160 This twelfth development snapshot fixes some more build problems as
8161 well as a few minor bugs.
8164 - Make it build on OpenBSD again. Patch from tup.
8165 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
8166 package-building for Red Hat, OS X, etc.
8168 o Minor bugfixes (on 0.1.2.x):
8169 - Changing the ExitPolicyRejectPrivate setting should cause us to
8170 rebuild our server descriptor.
8172 o Minor bugfixes (on 0.2.0.x):
8173 - When we're lacking a consensus, don't try to perform rendezvous
8174 operations. Reported by Karsten Loesing.
8175 - Fix a small memory leak whenever we decide against using a
8176 newly picked entry guard. Reported by Mike Perry.
8177 - When authorities detected more than two relays running on the same
8178 IP address, they were clearing all the status flags but forgetting
8179 to clear the "hsdir" flag. So clients were being told that a
8180 given relay was the right choice for a v2 hsdir lookup, yet they
8181 never had its descriptor because it was marked as 'not running'
8183 - If we're trying to fetch a bridge descriptor and there's no way
8184 the bridge authority could help us (for example, we don't know
8185 a digest, or there is no bridge authority), don't be so eager to
8186 fall back to asking the bridge authority.
8187 - If we're using bridges or have strictentrynodes set, and our
8188 chosen exit is in the same family as all our bridges/entry guards,
8189 then be flexible about families.
8192 - When we negotiate a v2 link-layer connection (not yet implemented),
8193 accept RELAY_EARLY cells and turn them into RELAY cells if we've
8194 negotiated a v1 connection for their next step. Initial code for
8198 Changes in version 0.2.0.11-alpha - 2007-11-12
8199 This eleventh development snapshot fixes some build problems with
8200 the previous snapshot. It also includes a more secure-by-default exit
8201 policy for relays, fixes an enormous memory leak for exit relays, and
8202 fixes another bug where servers were falling out of the directory list.
8205 - Exit policies now reject connections that are addressed to a
8206 relay's public (external) IP address too, unless
8207 ExitPolicyRejectPrivate is turned off. We do this because too
8208 many relays are running nearby to services that trust them based
8209 on network address. Bugfix on 0.1.2.x.
8212 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
8213 on every successful resolve. Reported by Mike Perry; bugfix
8215 - On authorities, never downgrade to old router descriptors simply
8216 because they're listed in the consensus. This created a catch-22
8217 where we wouldn't list a new descriptor because there was an
8218 old one in the consensus, and we couldn't get the new one in the
8219 consensus because we wouldn't list it. Possible fix for bug 548.
8220 Also, this might cause bug 543 to appear on authorities; if so,
8221 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
8223 o Packaging fixes on 0.2.0.10-alpha:
8224 - We were including instructions about what to do with the
8225 src/config/fallback-consensus file, but we weren't actually
8226 including it in the tarball. Disable all of that for now.
8229 - Allow people to say PreferTunnelledDirConns rather than
8230 PreferTunneledDirConns, for those alternate-spellers out there.
8233 - Don't reevaluate all the information from our consensus document
8234 just because we've downloaded a v2 networkstatus that we intend
8235 to cache. Fixes bug 545; bugfix on 0.2.0.x.
8238 Changes in version 0.2.0.10-alpha - 2007-11-10
8239 This tenth development snapshot adds a third v3 directory authority
8240 run by Mike Perry, adds most of Karsten Loesing's new hidden service
8241 descriptor format, fixes a bad crash bug and new bridge bugs introduced
8242 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
8243 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
8244 addresses many more minor issues.
8246 o New directory authorities:
8247 - Set up ides (run by Mike Perry) as the third v3 directory authority.
8250 - Allow tunnelled directory connections to ask for an encrypted
8251 "begin_dir" connection or an anonymized "uses a full Tor circuit"
8252 connection independently. Now we can make anonymized begin_dir
8253 connections for (e.g.) more secure hidden service posting and
8255 - More progress on proposal 114: code from Karsten Loesing to
8256 implement new hidden service descriptor format.
8257 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
8258 accommodate the growing number of servers that use the default
8259 and are reaching it.
8260 - Directory authorities use a new formula for selecting which nodes
8261 to advertise as Guards: they must be in the top 7/8 in terms of
8262 how long we have known about them, and above the median of those
8263 nodes in terms of weighted fractional uptime.
8264 - Make "not enough dir info yet" warnings describe *why* Tor feels
8265 it doesn't have enough directory info yet.
8268 - Stop servers from crashing if they set a Family option (or
8269 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
8271 - Make bridge users work again -- the move to v3 directories in
8272 0.2.0.9-alpha had introduced a number of bugs that made bridges
8273 no longer work for clients.
8274 - When the clock jumps forward a lot, do not allow the bandwidth
8275 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
8277 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
8278 - When the consensus lists a router descriptor that we previously were
8279 mirroring, but that we considered non-canonical, reload the
8280 descriptor as canonical. This fixes bug 543 where Tor servers
8281 would start complaining after a few days that they don't have
8282 enough directory information to build a circuit.
8283 - Consider replacing the current consensus when certificates arrive
8284 that make the pending consensus valid. Previously, we were only
8285 considering replacement when the new certs _didn't_ help.
8286 - Fix an assert error on startup if we didn't already have the
8287 consensus and certs cached in our datadirectory: we were caching
8288 the consensus in consensus_waiting_for_certs but then free'ing it
8290 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
8291 Request) if we need more v3 certs but we've already got pending
8292 requests for all of them.
8293 - Correctly back off from failing certificate downloads. Fixes
8295 - Authorities don't vote on the Running flag if they have been running
8296 for less than 30 minutes themselves. Fixes bug 547, where a newly
8297 started authority would vote that everyone was down.
8300 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
8301 it, it had no AES, and it hasn't seen any security patches since
8305 - Clients now hold circuitless TLS connections open for 1.5 times
8306 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
8307 rebuild a new circuit over them within that timeframe. Previously,
8308 they held them open only for KeepalivePeriod (5 minutes).
8309 - Use "If-Modified-Since" to avoid retrieving consensus
8310 networkstatuses that we already have.
8311 - When we have no consensus, check FallbackNetworkstatusFile (defaults
8312 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
8313 we start knowing some directory caches.
8314 - When we receive a consensus from the future, warn about skew.
8315 - Improve skew reporting: try to give the user a better log message
8316 about how skewed they are, and how much this matters.
8317 - When we have a certificate for an authority, believe that
8318 certificate's claims about the authority's IP address.
8319 - New --quiet command-line option to suppress the default console log.
8320 Good in combination with --hash-password.
8321 - Authorities send back an X-Descriptor-Not-New header in response to
8322 an accepted-but-discarded descriptor upload. Partially implements
8324 - Make the log message for "tls error. breaking." more useful.
8325 - Better log messages about certificate downloads, to attempt to
8326 track down the second incarnation of bug 546.
8328 o Minor features (bridges):
8329 - If bridge users set UpdateBridgesFromAuthority, but the digest
8330 they ask for is a 404 from the bridge authority, they now fall
8331 back to trying the bridge directly.
8332 - Bridges now use begin_dir to publish their server descriptor to
8333 the bridge authority, even when they haven't set TunnelDirConns.
8335 o Minor features (controller):
8336 - When reporting clock skew, and we know that the clock is _at least
8337 as skewed_ as some value, but we don't know the actual value,
8338 report the value as a "minimum skew."
8341 - Update linux-tor-prio.sh script to allow QoS based on the uid of
8342 the Tor process. Patch from Marco Bonetti with tweaks from Mike
8346 - Refuse to start if both ORPort and UseBridges are set. Bugfix
8347 on 0.2.0.x, suggested by Matt Edman.
8348 - Don't stop fetching descriptors when FetchUselessDescriptors is
8349 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
8350 reported by tup and ioerror.
8351 - Better log message on vote from unknown authority.
8352 - Don't log "Launching 0 request for 0 router" message.
8354 o Minor bugfixes (memory leaks):
8355 - Stop leaking memory every time we parse a v3 certificate. Bugfix
8357 - Stop leaking memory every time we load a v3 certificate. Bugfix
8358 on 0.2.0.1-alpha. Fixes bug 536.
8359 - Stop leaking a cached networkstatus on exit. Bugfix on
8361 - Stop leaking voter information every time we free a consensus.
8362 Bugfix on 0.2.0.3-alpha.
8363 - Stop leaking signed data every time we check a voter signature.
8364 Bugfix on 0.2.0.3-alpha.
8365 - Stop leaking a signature every time we fail to parse a consensus or
8366 a vote. Bugfix on 0.2.0.3-alpha.
8367 - Stop leaking v2_download_status_map on shutdown. Bugfix on
8369 - Stop leaking conn->nickname every time we make a connection to a
8370 Tor relay without knowing its expected identity digest (e.g. when
8371 using bridges). Bugfix on 0.2.0.3-alpha.
8373 - Minor bugfixes (portability):
8374 - Run correctly on platforms where rlim_t is larger than unsigned
8375 long, and/or where the real limit for number of open files is
8376 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
8377 particular, these may be needed for OS X 10.5.
8380 Changes in version 0.1.2.18 - 2007-10-28
8381 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
8382 hidden service introduction that were causing huge delays, and a big
8383 bug that was causing some servers to disappear from the network status
8384 lists for a few hours each day.
8386 o Major bugfixes (crashes):
8387 - If a connection is shut down abruptly because of something that
8388 happened inside connection_flushed_some(), do not call
8389 connection_finished_flushing(). Should fix bug 451:
8390 "connection_stop_writing: Assertion conn->write_event failed"
8391 Bugfix on 0.1.2.7-alpha.
8392 - Fix possible segfaults in functions called from
8393 rend_process_relay_cell().
8395 o Major bugfixes (hidden services):
8396 - Hidden services were choosing introduction points uniquely by
8397 hexdigest, but when constructing the hidden service descriptor
8398 they merely wrote the (potentially ambiguous) nickname.
8399 - Clients now use the v2 intro format for hidden service
8400 connections: they specify their chosen rendezvous point by identity
8401 digest rather than by (potentially ambiguous) nickname. These
8402 changes could speed up hidden service connections dramatically.
8404 o Major bugfixes (other):
8405 - Stop publishing a new server descriptor just because we get a
8406 HUP signal. This led (in a roundabout way) to some servers getting
8407 dropped from the networkstatus lists for a few hours each day.
8408 - When looking for a circuit to cannibalize, consider family as well
8409 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8410 circuit cannibalization).
8411 - When a router wasn't listed in a new networkstatus, we were leaving
8412 the flags for that router alone -- meaning it remained Named,
8413 Running, etc -- even though absence from the networkstatus means
8414 that it shouldn't be considered to exist at all anymore. Now we
8415 clear all the flags for routers that fall out of the networkstatus
8416 consensus. Fixes bug 529.
8419 - Don't try to access (or alter) the state file when running
8420 --list-fingerprint or --verify-config or --hash-password. Resolves
8422 - When generating information telling us how to extend to a given
8423 router, do not try to include the nickname if it is
8424 absent. Resolves bug 467.
8425 - Fix a user-triggerable segfault in expand_filename(). (There isn't
8426 a way to trigger this remotely.)
8427 - When sending a status event to the controller telling it that an
8428 OR address is reachable, set the port correctly. (Previously we
8429 were reporting the dir port.)
8430 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8431 command. Bugfix on 0.1.2.17.
8432 - When loading bandwidth history, do not believe any information in
8433 the future. Fixes bug 434.
8434 - When loading entry guard information, do not believe any information
8436 - When we have our clock set far in the future and generate an
8437 onion key, then re-set our clock to be correct, we should not stop
8438 the onion key from getting rotated.
8439 - On some platforms, accept() can return a broken address. Detect
8440 this more quietly, and deal accordingly. Fixes bug 483.
8441 - It's not actually an error to find a non-pending entry in the DNS
8442 cache when canceling a pending resolve. Don't log unless stuff
8443 is fishy. Resolves bug 463.
8444 - Don't reset trusted dir server list when we set a configuration
8445 option. Patch from Robert Hogan.
8446 - Don't try to create the datadir when running --verify-config or
8447 --hash-password. Resolves bug 540.
8450 Changes in version 0.2.0.9-alpha - 2007-10-24
8451 This ninth development snapshot switches clients to the new v3 directory
8452 system; allows servers to be listed in the network status even when they
8453 have the same nickname as a registered server; and fixes many other
8454 bugs including a big one that was causing some servers to disappear
8455 from the network status lists for a few hours each day.
8457 o Major features (directory system):
8458 - Clients now download v3 consensus networkstatus documents instead
8459 of v2 networkstatus documents. Clients and caches now base their
8460 opinions about routers on these consensus documents. Clients only
8461 download router descriptors listed in the consensus.
8462 - Authorities now list servers who have the same nickname as
8463 a different named server, but list them with a new flag,
8464 "Unnamed". Now we can list servers that happen to pick the same
8465 nickname as a server that registered two years ago and then
8466 disappeared. Partially implements proposal 122.
8467 - If the consensus lists a router as "Unnamed", the name is assigned
8468 to a different router: do not identify the router by that name.
8469 Partially implements proposal 122.
8470 - Authorities can now come to a consensus on which method to use to
8471 compute the consensus. This gives us forward compatibility.
8474 - Stop publishing a new server descriptor just because we HUP or
8475 when we find our DirPort to be reachable but won't actually publish
8476 it. New descriptors without any real changes are dropped by the
8477 authorities, and can screw up our "publish every 18 hours" schedule.
8479 - When a router wasn't listed in a new networkstatus, we were leaving
8480 the flags for that router alone -- meaning it remained Named,
8481 Running, etc -- even though absence from the networkstatus means
8482 that it shouldn't be considered to exist at all anymore. Now we
8483 clear all the flags for routers that fall out of the networkstatus
8484 consensus. Fixes bug 529; bugfix on 0.1.2.x.
8485 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
8486 extrainfo documents and then discard them immediately for not
8487 matching the latest router. Bugfix on 0.2.0.1-alpha.
8489 o Minor features (v3 directory protocol):
8490 - Allow tor-gencert to generate a new certificate without replacing
8492 - Allow certificates to include an address.
8493 - When we change our directory-cache settings, reschedule all voting
8494 and download operations.
8495 - Reattempt certificate downloads immediately on failure, as long as
8496 we haven't failed a threshold number of times yet.
8497 - Delay retrying consensus downloads while we're downloading
8498 certificates to verify the one we just got. Also, count getting a
8499 consensus that we already have (or one that isn't valid) as a failure,
8500 and count failing to get the certificates after 20 minutes as a
8502 - Build circuits and download descriptors even if our consensus is a
8503 little expired. (This feature will go away once authorities are
8506 o Minor features (router descriptor cache):
8507 - If we find a cached-routers file that's been sitting around for more
8508 than 28 days unmodified, then most likely it's a leftover from
8509 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
8511 - When we (as a cache) download a descriptor because it was listed
8512 in a consensus, remember when the consensus was supposed to expire,
8513 and don't expire the descriptor until then.
8515 o Minor features (performance):
8516 - Call routerlist_remove_old_routers() much less often. This should
8517 speed startup, especially on directory caches.
8518 - Don't try to launch new descriptor downloads quite so often when we
8519 already have enough directory information to build circuits.
8520 - Base64 decoding was actually showing up on our profile when parsing
8521 the initial descriptor file; switch to an in-process all-at-once
8522 implementation that's about 3.5x times faster than calling out to
8525 o Minor features (compilation):
8526 - Detect non-ASCII platforms (if any still exist) and refuse to
8527 build there: some of our code assumes that 'A' is 65 and so on.
8529 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
8530 - Make the "next period" votes into "current period" votes immediately
8531 after publishing the consensus; avoid a heisenbug that made them
8532 stick around indefinitely.
8533 - When we discard a vote as a duplicate, do not report this as
8535 - Treat missing v3 keys or certificates as an error when running as a
8536 v3 directory authority.
8537 - When we're configured to be a v3 authority, but we're only listed
8538 as a non-v3 authority in our DirServer line for ourself, correct
8540 - If an authority doesn't have a qualified hostname, just put
8541 its address in the vote. This fixes the problem where we referred to
8542 "moria on moria:9031."
8543 - Distinguish between detached signatures for the wrong period, and
8544 detached signatures for a divergent vote.
8545 - Fix a small memory leak when computing a consensus.
8546 - When there's no concensus, we were forming a vote every 30
8547 minutes, but writing the "valid-after" line in our vote based
8548 on our configured V3AuthVotingInterval: so unless the intervals
8549 matched up, we immediately rejected our own vote because it didn't
8550 start at the voting interval that caused us to construct a vote.
8552 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
8553 - Delete unverified-consensus when the real consensus is set.
8554 - Consider retrying a consensus networkstatus fetch immediately
8555 after one fails: don't wait 60 seconds to notice.
8556 - When fetching a consensus as a cache, wait until a newer consensus
8557 should exist before trying to replace the current one.
8558 - Use a more forgiving schedule for retrying failed consensus
8559 downloads than for other types.
8561 o Minor bugfixes (other directory issues):
8562 - Correct the implementation of "download votes by digest." Bugfix on
8564 - Authorities no longer send back "400 you're unreachable please fix
8565 it" errors to Tor servers that aren't online all the time. We're
8566 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
8568 o Minor bugfixes (controller):
8569 - Don't reset trusted dir server list when we set a configuration
8570 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
8571 - Respond to INT and TERM SIGNAL commands before we execute the
8572 signal, in case the signal shuts us down. We had a patch in
8573 0.1.2.1-alpha that tried to do this by queueing the response on
8574 the connection's buffer before shutting down, but that really
8575 isn't the same thing at all. Bug located by Matt Edman.
8577 o Minor bugfixes (misc):
8578 - Correctly check for bad options to the "PublishServerDescriptor"
8579 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
8580 - Stop leaking memory on failing case of base32_decode, and make
8581 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
8582 - Don't try to download extrainfo documents when we're trying to
8583 fetch enough directory info to build a circuit: having enough
8584 info should get priority. Bugfix on 0.2.0.x.
8585 - Don't complain that "your server has not managed to confirm that its
8586 ports are reachable" if we haven't been able to build any circuits
8587 yet. Bug found by spending four hours without a v3 consensus. Bugfix
8589 - Detect the reason for failing to mmap a descriptor file we just
8590 wrote, and give a more useful log message. Fixes bug 533. Bugfix
8593 o Code simplifications and refactoring:
8594 - Remove support for the old bw_accounting file: we've been storing
8595 bandwidth accounting information in the state file since
8596 0.1.2.5-alpha. This may result in bandwidth accounting errors
8597 if you try to upgrade from 0.1.1.x or earlier, or if you try to
8598 downgrade to 0.1.1.x or earlier.
8599 - New convenience code to locate a file within the DataDirectory.
8600 - Move non-authority functionality out of dirvote.c.
8601 - Refactor the arguments for router_pick_{directory_|trusteddir}server
8602 so that they all take the same named flags.
8605 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
8606 Unix users an easy way to script their Tor process (e.g. by
8607 adjusting bandwidth based on the time of the day).
8610 Changes in version 0.2.0.8-alpha - 2007-10-12
8611 This eighth development snapshot fixes a crash bug that's been bothering
8612 us since February 2007, lets bridge authorities store a list of bridge
8613 descriptors they've seen, gets v3 directory voting closer to working,
8614 starts caching v3 directory consensus documents on directory mirrors,
8615 and fixes a variety of smaller issues including some minor memory leaks.
8617 o Major features (router descriptor cache):
8618 - Store routers in a file called cached-descriptors instead of in
8619 cached-routers. Initialize cached-descriptors from cached-routers
8620 if the old format is around. The new format allows us to store
8621 annotations along with descriptors.
8622 - Use annotations to record the time we received each descriptor, its
8623 source, and its purpose.
8624 - Disable the SETROUTERPURPOSE controller command: it is now
8626 - Controllers should now specify cache=no or cache=yes when using
8627 the +POSTDESCRIPTOR command.
8628 - Bridge authorities now write bridge descriptors to disk, meaning
8629 we can export them to other programs and begin distributing them
8632 o Major features (directory authorities):
8633 - When a v3 authority is missing votes or signatures, it now tries
8635 - Directory authorities track weighted fractional uptime as well as
8636 weighted mean-time-between failures. WFU is suitable for deciding
8637 whether a node is "usually up", while MTBF is suitable for deciding
8638 whether a node is "likely to stay up." We need both, because
8639 "usually up" is a good requirement for guards, while "likely to
8640 stay up" is a good requirement for long-lived connections.
8642 o Major features (v3 directory system):
8643 - Caches now download v3 network status documents as needed,
8644 and download the descriptors listed in them.
8645 - All hosts now attempt to download and keep fresh v3 authority
8646 certificates, and re-attempt after failures.
8647 - More internal-consistency checks for vote parsing.
8649 o Major bugfixes (crashes):
8650 - If a connection is shut down abruptly because of something that
8651 happened inside connection_flushed_some(), do not call
8652 connection_finished_flushing(). Should fix bug 451. Bugfix on
8655 o Major bugfixes (performance):
8656 - Fix really bad O(n^2) performance when parsing a long list of
8657 routers: Instead of searching the entire list for an "extra-info "
8658 string which usually wasn't there, once for every routerinfo
8659 we read, just scan lines forward until we find one we like.
8661 - When we add data to a write buffer in response to the data on that
8662 write buffer getting low because of a flush, do not consider the
8663 newly added data as a candidate for immediate flushing, but rather
8664 make it wait until the next round of writing. Otherwise, we flush
8665 and refill recursively, and a single greedy TLS connection can
8666 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
8668 o Minor features (v3 authority system):
8669 - Add more ways for tools to download the votes that lead to the
8671 - Send a 503 when low on bandwidth and a vote, consensus, or
8672 certificate is requested.
8673 - If-modified-since is now implemented properly for all kinds of
8674 certificate requests.
8676 o Minor bugfixes (network statuses):
8677 - Tweak the implementation of proposal 109 slightly: allow at most
8678 two Tor servers on the same IP address, except if it's the location
8679 of a directory authority, in which case allow five. Bugfix on
8682 o Minor bugfixes (controller):
8683 - When sending a status event to the controller telling it that an
8684 OR address is reachable, set the port correctly. (Previously we
8685 were reporting the dir port.) Bugfix on 0.1.2.x.
8687 o Minor bugfixes (v3 directory system):
8688 - Fix logic to look up a cert by its signing key digest. Bugfix on
8690 - Only change the reply to a vote to "OK" if it's not already
8691 set. This gets rid of annoying "400 OK" log messages, which may
8692 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
8693 - When we get a valid consensus, recompute the voting schedule.
8694 - Base the valid-after time of a vote on the consensus voting
8695 schedule, not on our preferred schedule.
8696 - Make the return values and messages from signature uploads and
8697 downloads more sensible.
8698 - Fix a memory leak when serving votes and consensus documents, and
8699 another when serving certificates.
8701 o Minor bugfixes (performance):
8702 - Use a slightly simpler string hashing algorithm (copying Python's
8703 instead of Java's) and optimize our digest hashing algorithm to take
8704 advantage of 64-bit platforms and to remove some possibly-costly
8706 - Fix a minor memory leak whenever we parse guards from our state
8707 file. Bugfix on 0.2.0.7-alpha.
8708 - Fix a minor memory leak whenever we write out a file. Bugfix on
8710 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8711 command. Bugfix on 0.2.0.5-alpha.
8713 o Minor bugfixes (portability):
8714 - On some platforms, accept() can return a broken address. Detect
8715 this more quietly, and deal accordingly. Fixes bug 483.
8716 - Stop calling tor_strlower() on uninitialized memory in some cases.
8717 Bugfix in 0.2.0.7-alpha.
8719 o Minor bugfixes (usability):
8720 - Treat some 403 responses from directory servers as INFO rather than
8721 WARN-severity events.
8722 - It's not actually an error to find a non-pending entry in the DNS
8723 cache when canceling a pending resolve. Don't log unless stuff is
8724 fishy. Resolves bug 463.
8726 o Minor bugfixes (anonymity):
8727 - Never report that we've used more bandwidth than we're willing to
8728 relay: it leaks how much non-relay traffic we're using. Resolves
8730 - When looking for a circuit to cannibalize, consider family as well
8731 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8732 circuit cannibalization).
8734 o Code simplifications and refactoring:
8735 - Make a bunch of functions static. Remove some dead code.
8736 - Pull out about a third of the really big routerlist.c; put it in a
8737 new module, networkstatus.c.
8738 - Merge the extra fields in local_routerstatus_t back into
8739 routerstatus_t: we used to need one routerstatus_t for each
8740 authority's opinion, plus a local_routerstatus_t for the locally
8741 computed consensus opinion. To save space, we put the locally
8742 modified fields into local_routerstatus_t, and only the common
8743 stuff into routerstatus_t. But once v3 directories are in use,
8744 clients and caches will no longer need to hold authority opinions;
8745 thus, the rationale for keeping the types separate is now gone.
8746 - Make the code used to reschedule and reattempt downloads more
8748 - Turn all 'Are we a directory server/mirror?' logic into a call to
8750 - Remove the code to generate the oldest (v1) directory format.
8751 The code has been disabled since 0.2.0.5-alpha.
8754 Changes in version 0.2.0.7-alpha - 2007-09-21
8755 This seventh development snapshot makes bridges work again, makes bridge
8756 authorities work for the first time, fixes two huge performance flaws
8757 in hidden services, and fixes a variety of minor issues.
8759 o New directory authorities:
8760 - Set up moria1 and tor26 as the first v3 directory authorities. See
8761 doc/spec/dir-spec.txt for details on the new directory design.
8763 o Major bugfixes (crashes):
8764 - Fix possible segfaults in functions called from
8765 rend_process_relay_cell(). Bugfix on 0.1.2.x.
8767 o Major bugfixes (bridges):
8768 - Fix a bug that made servers send a "404 Not found" in response to
8769 attempts to fetch their server descriptor. This caused Tor servers
8770 to take many minutes to establish reachability for their DirPort,
8771 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
8772 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
8773 users configure that and specify a bridge with an identity
8774 fingerprint, now they will lookup the bridge descriptor at the
8775 default bridge authority via a one-hop tunnel, but once circuits
8776 are established they will switch to a three-hop tunnel for later
8777 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
8779 o Major bugfixes (hidden services):
8780 - Hidden services were choosing introduction points uniquely by
8781 hexdigest, but when constructing the hidden service descriptor
8782 they merely wrote the (potentially ambiguous) nickname.
8783 - Clients now use the v2 intro format for hidden service
8784 connections: they specify their chosen rendezvous point by identity
8785 digest rather than by (potentially ambiguous) nickname. Both
8786 are bugfixes on 0.1.2.x, and they could speed up hidden service
8787 connections dramatically. Thanks to Karsten Loesing.
8789 o Minor features (security):
8790 - As a client, do not believe any server that tells us that an
8791 address maps to an internal address space.
8792 - Make it possible to enable HashedControlPassword and
8793 CookieAuthentication at the same time.
8795 o Minor features (guard nodes):
8796 - Tag every guard node in our state file with the version that
8797 we believe added it, or with our own version if we add it. This way,
8798 if a user temporarily runs an old version of Tor and then switches
8799 back to a new one, she doesn't automatically lose her guards.
8801 o Minor features (speed):
8802 - When implementing AES counter mode, update only the portions of the
8803 counter buffer that need to change, and don't keep separate
8804 network-order and host-order counters when they are the same (i.e.,
8805 on big-endian hosts.)
8807 o Minor features (controller):
8808 - Accept LF instead of CRLF on controller, since some software has a
8809 hard time generating real Internet newlines.
8810 - Add GETINFO values for the server status events
8811 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
8815 - Routers no longer include bandwidth-history lines in their
8816 descriptors; this information is already available in extra-info
8817 documents, and including it in router descriptors took up 60%
8818 (!) of compressed router descriptor downloads. Completes
8819 implementation of proposal 104.
8820 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
8821 and TorControl.py, as they use the old v0 controller protocol,
8822 and are obsoleted by TorFlow anyway.
8823 - Drop support for v1 rendezvous descriptors, since we never used
8824 them anyway, and the code has probably rotted by now. Based on
8825 patch from Karsten Loesing.
8826 - On OSX, stop warning the user that kqueue support in libevent is
8827 "experimental", since it seems to have worked fine for ages.
8830 - When generating information telling us how to extend to a given
8831 router, do not try to include the nickname if it is absent. Fixes
8832 bug 467. Bugfix on 0.2.0.3-alpha.
8833 - Fix a user-triggerable (but not remotely-triggerable) segfault
8834 in expand_filename(). Bugfix on 0.1.2.x.
8835 - Fix a memory leak when freeing incomplete requests from DNSPort.
8836 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
8837 - Don't try to access (or alter) the state file when running
8838 --list-fingerprint or --verify-config or --hash-password. (Resolves
8839 bug 499.) Bugfix on 0.1.2.x.
8840 - Servers used to decline to publish their DirPort if their
8841 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
8842 were below a threshold. Now they only look at BandwidthRate and
8843 RelayBandwidthRate. Bugfix on 0.1.2.x.
8844 - Remove an optimization in the AES counter-mode code that assumed
8845 that the counter never exceeded 2^68. When the counter can be set
8846 arbitrarily as an IV (as it is by Karsten's new hidden services
8847 code), this assumption no longer holds. Bugfix on 0.1.2.x.
8848 - Resume listing "AUTHORITY" flag for authorities in network status.
8849 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
8851 o Code simplifications and refactoring:
8852 - Revamp file-writing logic so we don't need to have the entire
8853 contents of a file in memory at once before we write to disk. Tor,
8855 - Turn "descriptor store" into a full-fledged type.
8856 - Move all NT services code into a separate source file.
8857 - Unify all code that computes medians, percentile elements, etc.
8858 - Get rid of a needless malloc when parsing address policies.
8861 Changes in version 0.1.2.17 - 2007-08-30
8862 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
8863 X bundles. Vidalia 0.0.14 makes authentication required for the
8864 ControlPort in the default configuration, which addresses important
8865 security risks. Everybody who uses Vidalia (or another controller)
8868 In addition, this Tor update fixes major load balancing problems with
8869 path selection, which should speed things up a lot once many people
8872 o Major bugfixes (security):
8873 - We removed support for the old (v0) control protocol. It has been
8874 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
8875 become more of a headache than it's worth.
8877 o Major bugfixes (load balancing):
8878 - When choosing nodes for non-guard positions, weight guards
8879 proportionally less, since they already have enough load. Patch
8881 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8882 will allow fast Tor servers to get more attention.
8883 - When we're upgrading from an old Tor version, forget our current
8884 guards and pick new ones according to the new weightings. These
8885 three load balancing patches could raise effective network capacity
8886 by a factor of four. Thanks to Mike Perry for measurements.
8888 o Major bugfixes (stream expiration):
8889 - Expire not-yet-successful application streams in all cases if
8890 they've been around longer than SocksTimeout. Right now there are
8891 some cases where the stream will live forever, demanding a new
8892 circuit every 15 seconds. Fixes bug 454; reported by lodger.
8894 o Minor features (controller):
8895 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8896 is valid before any authentication has been received. It tells
8897 a controller what kind of authentication is expected, and what
8898 protocol is spoken. Implements proposal 119.
8900 o Minor bugfixes (performance):
8901 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
8902 greatly speeding up loading cached-routers from disk on startup.
8903 - Disable sentinel-based debugging for buffer code: we squashed all
8904 the bugs that this was supposed to detect a long time ago, and now
8905 its only effect is to change our buffer sizes from nice powers of
8906 two (which platform mallocs tend to like) to values slightly over
8907 powers of two (which make some platform mallocs sad).
8909 o Minor bugfixes (misc):
8910 - If exit bandwidth ever exceeds one third of total bandwidth, then
8911 use the correct formula to weight exit nodes when choosing paths.
8912 Based on patch from Mike Perry.
8913 - Choose perfectly fairly among routers when choosing by bandwidth and
8914 weighting by fraction of bandwidth provided by exits. Previously, we
8915 would choose with only approximate fairness, and correct ourselves
8916 if we ran off the end of the list.
8917 - If we require CookieAuthentication but we fail to write the
8918 cookie file, we would warn but not exit, and end up in a state
8919 where no controller could authenticate. Now we exit.
8920 - If we require CookieAuthentication, stop generating a new cookie
8921 every time we change any piece of our config.
8922 - Refuse to start with certain directory authority keys, and
8923 encourage people using them to stop.
8924 - Terminate multi-line control events properly. Original patch
8926 - Fix a minor memory leak when we fail to find enough suitable
8927 servers to choose a circuit.
8928 - Stop leaking part of the descriptor when we run into a particularly
8929 unparseable piece of it.
8932 Changes in version 0.2.0.6-alpha - 2007-08-26
8933 This sixth development snapshot features a new Vidalia version in the
8934 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
8935 the ControlPort in the default configuration, which addresses important
8938 In addition, this snapshot fixes major load balancing problems
8939 with path selection, which should speed things up a lot once many
8940 people have upgraded. The directory authorities also use a new
8941 mean-time-between-failure approach to tracking which servers are stable,
8942 rather than just looking at the most recent uptime.
8944 o New directory authorities:
8945 - Set up Tonga as the default bridge directory authority.
8948 - Directory authorities now track servers by weighted
8949 mean-times-between-failures. When we have 4 or more days of data,
8950 use measured MTBF rather than declared uptime to decide whether
8951 to call a router Stable. Implements proposal 108.
8953 o Major bugfixes (load balancing):
8954 - When choosing nodes for non-guard positions, weight guards
8955 proportionally less, since they already have enough load. Patch
8957 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8958 will allow fast Tor servers to get more attention.
8959 - When we're upgrading from an old Tor version, forget our current
8960 guards and pick new ones according to the new weightings. These
8961 three load balancing patches could raise effective network capacity
8962 by a factor of four. Thanks to Mike Perry for measurements.
8964 o Major bugfixes (descriptor parsing):
8965 - Handle unexpected whitespace better in malformed descriptors. Bug
8966 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
8969 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
8970 GETINFO for Torstat to use until it can switch to using extrainfos.
8971 - Optionally (if built with -DEXPORTMALLINFO) export the output
8972 of mallinfo via http, as tor/mallinfo.txt. Only accessible
8976 - Do not intermix bridge routers with controller-added
8977 routers. (Bugfix on 0.2.0.x)
8978 - Do not fail with an assert when accept() returns an unexpected
8979 address family. Addresses but does not wholly fix bug 483. (Bugfix
8981 - Let directory authorities startup even when they can't generate
8982 a descriptor immediately, e.g. because they don't know their
8984 - Stop putting the authentication cookie in a file called "0"
8985 in your working directory if you don't specify anything for the
8986 new CookieAuthFile option. Reported by Matt Edman.
8987 - Make it possible to read the PROTOCOLINFO response in a way that
8988 conforms to our control-spec. Reported by Matt Edman.
8989 - Fix a minor memory leak when we fail to find enough suitable
8990 servers to choose a circuit. Bugfix on 0.1.2.x.
8991 - Stop leaking part of the descriptor when we run into a particularly
8992 unparseable piece of it. Bugfix on 0.1.2.x.
8993 - Unmap the extrainfo cache file on exit.
8996 Changes in version 0.2.0.5-alpha - 2007-08-19
8997 This fifth development snapshot fixes compilation on Windows again;
8998 fixes an obnoxious client-side bug that slowed things down and put
8999 extra load on the network; gets us closer to using the v3 directory
9000 voting scheme; makes it easier for Tor controllers to use cookie-based
9001 authentication; and fixes a variety of other bugs.
9004 - Version 1 directories are no longer generated in full. Instead,
9005 authorities generate and serve "stub" v1 directories that list
9006 no servers. This will stop Tor versions 0.1.0.x and earlier from
9007 working, but (for security reasons) nobody should be running those
9010 o Major bugfixes (compilation, 0.2.0.x):
9011 - Try to fix Win32 compilation again: improve checking for IPv6 types.
9012 - Try to fix MSVC compilation: build correctly on platforms that do
9013 not define s6_addr16 or s6_addr32.
9014 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
9017 o Major bugfixes (stream expiration):
9018 - Expire not-yet-successful application streams in all cases if
9019 they've been around longer than SocksTimeout. Right now there are
9020 some cases where the stream will live forever, demanding a new
9021 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
9024 o Minor features (directory servers):
9025 - When somebody requests a list of statuses or servers, and we have
9026 none of those, return a 404 rather than an empty 200.
9028 o Minor features (directory voting):
9029 - Store v3 consensus status consensuses on disk, and reload them
9032 o Minor features (security):
9033 - Warn about unsafe ControlPort configurations.
9034 - Refuse to start with certain directory authority keys, and
9035 encourage people using them to stop.
9037 o Minor features (controller):
9038 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
9039 is valid before any authentication has been received. It tells
9040 a controller what kind of authentication is expected, and what
9041 protocol is spoken. Implements proposal 119.
9042 - New config option CookieAuthFile to choose a new location for the
9043 cookie authentication file, and config option
9044 CookieAuthFileGroupReadable to make it group-readable.
9046 o Minor features (unit testing):
9047 - Add command-line arguments to unit-test executable so that we can
9048 invoke any chosen test from the command line rather than having
9049 to run the whole test suite at once; and so that we can turn on
9050 logging for the unit tests.
9052 o Minor bugfixes (on 0.1.2.x):
9053 - If we require CookieAuthentication but we fail to write the
9054 cookie file, we would warn but not exit, and end up in a state
9055 where no controller could authenticate. Now we exit.
9056 - If we require CookieAuthentication, stop generating a new cookie
9057 every time we change any piece of our config.
9058 - When loading bandwidth history, do not believe any information in
9059 the future. Fixes bug 434.
9060 - When loading entry guard information, do not believe any information
9062 - When we have our clock set far in the future and generate an
9063 onion key, then re-set our clock to be correct, we should not stop
9064 the onion key from getting rotated.
9065 - Clean up torrc sample config file.
9066 - Do not automatically run configure from autogen.sh. This
9067 non-standard behavior tended to annoy people who have built other
9070 o Minor bugfixes (on 0.2.0.x):
9071 - Fix a bug with AutomapHostsOnResolve that would always cause
9072 the second request to fail. Bug reported by Kate. Bugfix on
9074 - Fix a bug in ADDRMAP controller replies that would sometimes
9075 try to print a NULL. Patch from tup.
9076 - Read v3 directory authority keys from the right location.
9077 - Numerous bugfixes to directory voting code.
9080 Changes in version 0.1.2.16 - 2007-08-01
9081 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
9082 remote attacker in certain situations to rewrite the user's torrc
9083 configuration file. This can completely compromise anonymity of users
9084 in most configurations, including those running the Vidalia bundles,
9085 TorK, etc. Or worse.
9087 o Major security fixes:
9088 - Close immediately after missing authentication on control port;
9089 do not allow multiple authentication attempts.
9092 Changes in version 0.2.0.4-alpha - 2007-08-01
9093 This fourth development snapshot fixes a critical security vulnerability
9094 for most users, specifically those running Vidalia, TorK, etc. Everybody
9095 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
9097 o Major security fixes:
9098 - Close immediately after missing authentication on control port;
9099 do not allow multiple authentication attempts.
9101 o Major bugfixes (compilation):
9102 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
9105 o Minor features (performance):
9106 - Be even more aggressive about releasing RAM from small
9107 empty buffers. Thanks to our free-list code, this shouldn't be too
9108 performance-intensive.
9109 - Disable sentinel-based debugging for buffer code: we squashed all
9110 the bugs that this was supposed to detect a long time ago, and
9111 now its only effect is to change our buffer sizes from nice
9112 powers of two (which platform mallocs tend to like) to values
9113 slightly over powers of two (which make some platform mallocs sad).
9114 - Log malloc statistics from mallinfo() on platforms where it
9118 Changes in version 0.2.0.3-alpha - 2007-07-29
9119 This third development snapshot introduces new experimental
9120 blocking-resistance features and a preliminary version of the v3
9121 directory voting design, and includes many other smaller features
9125 - The first pieces of our "bridge" design for blocking-resistance
9126 are implemented. People can run bridge directory authorities;
9127 people can run bridges; and people can configure their Tor clients
9128 with a set of bridges to use as the first hop into the Tor network.
9129 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
9131 - Create listener connections before we setuid to the configured
9132 User and Group. Now non-Windows users can choose port values
9133 under 1024, start Tor as root, and have Tor bind those ports
9134 before it changes to another UID. (Windows users could already
9136 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
9137 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
9138 on "vserver" accounts. (Patch from coderman.)
9139 - Be even more aggressive about separating local traffic from relayed
9140 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
9142 o Major features (experimental):
9143 - First cut of code for "v3 dir voting": directory authorities will
9144 vote on a common network status document rather than each publishing
9145 their own opinion. This code needs more testing and more corner-case
9146 handling before it's ready for use.
9149 - Directory authorities now call routers Fast if their bandwidth is
9150 at least 100KB/s, and consider their bandwidth adequate to be a
9151 Guard if it is at least 250KB/s, no matter the medians. This fix
9152 complements proposal 107. [Bugfix on 0.1.2.x]
9153 - Directory authorities now never mark more than 3 servers per IP as
9154 Valid and Running. (Implements proposal 109, by Kevin Bauer and
9156 - Minor change to organizationName and commonName generation
9157 procedures in TLS certificates during Tor handshakes, to invalidate
9158 some earlier censorware approaches. This is not a long-term
9159 solution, but applying it will give us a bit of time to look into
9160 the epidemiology of countermeasures as they spread.
9162 o Major bugfixes (directory):
9163 - Rewrite directory tokenization code to never run off the end of
9164 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
9166 o Minor features (controller):
9167 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
9168 match requests to applications. (Patch from Robert Hogan.)
9169 - Report address and port correctly on connections to DNSPort. (Patch
9171 - Add a RESOLVE command to launch hostname lookups. (Original patch
9173 - Add GETINFO status/enough-dir-info to let controllers tell whether
9174 Tor has downloaded sufficient directory information. (Patch
9176 - You can now use the ControlSocket option to tell Tor to listen for
9177 controller connections on Unix domain sockets on systems that
9178 support them. (Patch from Peter Palfrader.)
9179 - STREAM NEW events are generated for DNSPort requests and for
9180 tunneled directory connections. (Patch from Robert Hogan.)
9181 - New "GETINFO address-mappings/*" command to get address mappings
9182 with expiry information. "addr-mappings/*" is now deprecated.
9185 o Minor features (misc):
9186 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
9188 - The tor-gencert tool for v3 directory authorities now creates all
9189 files as readable to the file creator only, and write-protects
9190 the authority identity key.
9191 - When dumping memory usage, list bytes used in buffer memory
9193 - When running with dmalloc, dump more stats on hup and on exit.
9194 - Directory authorities now fail quickly and (relatively) harmlessly
9195 if they generate a network status document that is somehow
9198 o Traffic load balancing improvements:
9199 - If exit bandwidth ever exceeds one third of total bandwidth, then
9200 use the correct formula to weight exit nodes when choosing paths.
9201 (Based on patch from Mike Perry.)
9202 - Choose perfectly fairly among routers when choosing by bandwidth and
9203 weighting by fraction of bandwidth provided by exits. Previously, we
9204 would choose with only approximate fairness, and correct ourselves
9205 if we ran off the end of the list. [Bugfix on 0.1.2.x]
9207 o Performance improvements:
9208 - Be more aggressive with freeing buffer RAM or putting it on the
9210 - Use Critical Sections rather than Mutexes for synchronizing threads
9211 on win32; Mutexes are heavier-weight, and designed for synchronizing
9214 o Deprecated and removed features:
9215 - RedirectExits is now deprecated.
9216 - Stop allowing address masks that do not correspond to bit prefixes.
9217 We have warned about these for a really long time; now it's time
9218 to reject them. (Patch from croup.)
9220 o Minor bugfixes (directory):
9221 - Fix another crash bug related to extra-info caching. (Bug found by
9222 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
9223 - Directories no longer return a "304 not modified" when they don't
9224 have the networkstatus the client asked for. Also fix a memory
9225 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
9226 - We had accidentally labelled 0.1.2.x directory servers as not
9227 suitable for begin_dir requests, and had labelled no directory
9228 servers as suitable for uploading extra-info documents. [Bugfix
9231 o Minor bugfixes (dns):
9232 - Fix a crash when DNSPort is set more than once. (Patch from Robert
9233 Hogan.) [Bugfix on 0.2.0.2-alpha]
9234 - Add DNSPort connections to the global connection list, so that we
9235 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
9237 - Fix a dangling reference that could lead to a crash when DNSPort is
9238 changed or closed (Patch from Robert Hogan.) [Bugfix on
9241 o Minor bugfixes (controller):
9242 - Provide DNS expiry times in GMT, not in local time. For backward
9243 compatibility, ADDRMAP events only provide GMT expiry in an extended
9244 field. "GETINFO address-mappings" always does the right thing.
9245 - Use CRLF line endings properly in NS events.
9246 - Terminate multi-line control events properly. (Original patch
9247 from tup.) [Bugfix on 0.1.2.x-alpha]
9248 - Do not include spaces in SOURCE_ADDR fields in STREAM
9249 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
9252 Changes in version 0.1.2.15 - 2007-07-17
9253 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
9254 problems, fixes compilation on BSD, and fixes a variety of other
9255 bugs. Everybody should upgrade.
9257 o Major bugfixes (compilation):
9258 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
9260 o Major bugfixes (crashes):
9261 - Try even harder not to dereference the first character after
9262 an mmap(). Reported by lodger.
9263 - Fix a crash bug in directory authorities when we re-number the
9264 routerlist while inserting a new router.
9265 - When the cached-routers file is an even multiple of the page size,
9266 don't run off the end and crash. (Fixes bug 455; based on idea
9268 - Fix eventdns.c behavior on Solaris: It is critical to include
9269 orconfig.h _before_ sys/types.h, so that we can get the expected
9270 definition of _FILE_OFFSET_BITS.
9272 o Major bugfixes (security):
9273 - Fix a possible buffer overrun when using BSD natd support. Bug
9275 - When sending destroy cells from a circuit's origin, don't include
9276 the reason for tearing down the circuit. The spec says we didn't,
9277 and now we actually don't. Reported by lodger.
9278 - Keep streamids from different exits on a circuit separate. This
9279 bug may have allowed other routers on a given circuit to inject
9280 cells into streams. Reported by lodger; fixes bug 446.
9281 - If there's a never-before-connected-to guard node in our list,
9282 never choose any guards past it. This way we don't expand our
9283 guard list unless we need to.
9285 o Minor bugfixes (guard nodes):
9286 - Weight guard selection by bandwidth, so that low-bandwidth nodes
9287 don't get overused as guards.
9289 o Minor bugfixes (directory):
9290 - Correctly count the number of authorities that recommend each
9291 version. Previously, we were under-counting by 1.
9292 - Fix a potential crash bug when we load many server descriptors at
9293 once and some of them make others of them obsolete. Fixes bug 458.
9295 o Minor bugfixes (hidden services):
9296 - Stop tearing down the whole circuit when the user asks for a
9297 connection to a port that the hidden service didn't configure.
9300 o Minor bugfixes (misc):
9301 - On Windows, we were preventing other processes from reading
9302 cached-routers while Tor was running. Reported by janbar.
9303 - Fix a possible (but very unlikely) bug in picking routers by
9304 bandwidth. Add a log message to confirm that it is in fact
9305 unlikely. Patch from lodger.
9306 - Backport a couple of memory leak fixes.
9307 - Backport miscellaneous cosmetic bugfixes.
9310 Changes in version 0.2.0.2-alpha - 2007-06-02
9311 o Major bugfixes on 0.2.0.1-alpha:
9312 - Fix an assertion failure related to servers without extra-info digests.
9313 Resolves bugs 441 and 442.
9315 o Minor features (directory):
9316 - Support "If-Modified-Since" when answering HTTP requests for
9317 directories, running-routers documents, and network-status documents.
9318 (There's no need to support it for router descriptors, since those
9319 are downloaded by descriptor digest.)
9321 o Minor build issues:
9322 - Clear up some MIPSPro compiler warnings.
9323 - When building from a tarball on a machine that happens to have SVK
9324 installed, report the micro-revision as whatever version existed
9325 in the tarball, not as "x".
9328 Changes in version 0.2.0.1-alpha - 2007-06-01
9329 This early development snapshot provides new features for people running
9330 Tor as both a client and a server (check out the new RelayBandwidth
9331 config options); lets Tor run as a DNS proxy; and generally moves us
9332 forward on a lot of fronts.
9334 o Major features, server usability:
9335 - New config options RelayBandwidthRate and RelayBandwidthBurst:
9336 a separate set of token buckets for relayed traffic. Right now
9337 relayed traffic is defined as answers to directory requests, and
9338 OR connections that don't have any local circuits on them.
9340 o Major features, client usability:
9341 - A client-side DNS proxy feature to replace the need for
9342 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
9343 for DNS requests on port 9999, use the Tor network to resolve them
9344 anonymously, and send the reply back like a regular DNS server.
9345 The code still only implements a subset of DNS.
9346 - Make PreferTunneledDirConns and TunnelDirConns work even when
9347 we have no cached directory info. This means Tor clients can now
9348 do all of their connections protected by TLS.
9350 o Major features, performance and efficiency:
9351 - Directory authorities accept and serve "extra info" documents for
9352 routers. These documents contain fields from router descriptors
9353 that aren't usually needed, and that use a lot of excess
9354 bandwidth. Once these fields are removed from router descriptors,
9355 the bandwidth savings should be about 60%. [Partially implements
9357 - Servers upload extra-info documents to any authority that accepts
9358 them. Authorities (and caches that have been configured to download
9359 extra-info documents) download them as needed. [Partially implements
9361 - Change the way that Tor buffers data that it is waiting to write.
9362 Instead of queueing data cells in an enormous ring buffer for each
9363 client->OR or OR->OR connection, we now queue cells on a separate
9364 queue for each circuit. This lets us use less slack memory, and
9365 will eventually let us be smarter about prioritizing different kinds
9367 - Use memory pools to allocate cells with better speed and memory
9368 efficiency, especially on platforms where malloc() is inefficient.
9369 - Stop reading on edge connections when their corresponding circuit
9370 buffers are full; start again as the circuits empty out.
9372 o Major features, other:
9373 - Add an HSAuthorityRecordStats option that hidden service authorities
9374 can use to track statistics of overall hidden service usage without
9375 logging information that would be very useful to an attacker.
9376 - Start work implementing multi-level keys for directory authorities:
9377 Add a standalone tool to generate key certificates. (Proposal 103.)
9380 - Directory authorities now call routers Stable if they have an
9381 uptime of at least 30 days, even if that's not the median uptime
9382 in the network. Implements proposal 107, suggested by Kevin Bauer
9385 o Minor fixes (resource management):
9386 - Count the number of open sockets separately from the number
9387 of active connection_t objects. This will let us avoid underusing
9388 our allocated connection limit.
9389 - We no longer use socket pairs to link an edge connection to an
9390 anonymous directory connection or a DirPort test connection.
9391 Instead, we track the link internally and transfer the data
9392 in-process. This saves two sockets per "linked" connection (at the
9393 client and at the server), and avoids the nasty Windows socketpair()
9395 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
9396 for every single inactive connection_t. Free items from the
9397 4k/16k-buffer free lists when they haven't been used for a while.
9399 o Minor features (build):
9400 - Make autoconf search for libevent, openssl, and zlib consistently.
9401 - Update deprecated macros in configure.in.
9402 - When warning about missing headers, tell the user to let us
9403 know if the compile succeeds anyway, so we can downgrade the
9405 - Include the current subversion revision as part of the version
9406 string: either fetch it directly if we're in an SVN checkout, do
9407 some magic to guess it if we're in an SVK checkout, or use
9408 the last-detected version if we're building from a .tar.gz.
9409 Use this version consistently in log messages.
9411 o Minor features (logging):
9412 - Always prepend "Bug: " to any log message about a bug.
9413 - Put a platform string (e.g. "Linux i686") in the startup log
9414 message, so when people paste just their logs, we know if it's
9415 OpenBSD or Windows or what.
9416 - When logging memory usage, break down memory used in buffers by
9419 o Minor features (directory system):
9420 - New config option V2AuthoritativeDirectory that all directory
9421 authorities should set. This will let future authorities choose
9422 not to serve V2 directory information.
9423 - Directory authorities allow multiple router descriptors and/or extra
9424 info documents to be uploaded in a single go. This will make
9425 implementing proposal 104 simpler.
9427 o Minor features (controller):
9428 - Add a new config option __DisablePredictedCircuits designed for
9429 use by the controller, when we don't want Tor to build any circuits
9431 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
9432 so we can exit from the middle of the circuit.
9433 - Implement "getinfo status/circuit-established".
9434 - Implement "getinfo status/version/..." so a controller can tell
9435 whether the current version is recommended, and whether any versions
9436 are good, and how many authorities agree. (Patch from shibz.)
9438 o Minor features (hidden services):
9439 - Allow multiple HiddenServicePort directives with the same virtual
9440 port; when they occur, the user is sent round-robin to one
9441 of the target ports chosen at random. Partially fixes bug 393 by
9442 adding limited ad-hoc round-robining.
9444 o Minor features (other):
9446 - Add a new AutomapHostsOnResolve option: when it is enabled, any
9447 resolve request for hosts matching a given pattern causes Tor to
9448 generate an internal virtual address mapping for that host. This
9449 allows DNSPort to work sensibly with hidden service users. By
9450 default, .exit and .onion addresses are remapped; the list of
9451 patterns can be reconfigured with AutomapHostsSuffixes.
9452 - Add an "-F" option to tor-resolve to force a resolve for a .onion
9453 address. Thanks to the AutomapHostsOnResolve option, this is no
9454 longer a completely silly thing to do.
9455 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
9456 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
9457 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
9458 minus 1 byte: the actual maximum declared bandwidth.
9461 - Removed support for the old binary "version 0" controller protocol.
9462 This has been deprecated since 0.1.1, and warnings have been issued
9463 since 0.1.2. When we encounter a v0 control message, we now send
9464 back an error and close the connection.
9465 - Remove the old "dns worker" server DNS code: it hasn't been default
9466 since 0.1.2.2-alpha, and all the servers seem to be using the new
9469 o Minor bugfixes (portability):
9470 - Even though Windows is equally happy with / and \ as path separators,
9471 try to use \ consistently on Windows and / consistently on Unix: it
9472 makes the log messages nicer.
9473 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
9474 - Read resolv.conf files correctly on platforms where read() returns
9475 partial results on small file reads.
9477 o Minor bugfixes (directory):
9478 - Correctly enforce that elements of directory objects do not appear
9479 more often than they are allowed to appear.
9480 - When we are reporting the DirServer line we just parsed, we were
9481 logging the second stanza of the key fingerprint, not the first.
9483 o Minor bugfixes (logging):
9484 - When we hit an EOF on a log (probably because we're shutting down),
9485 don't try to remove the log from the list: just mark it as
9486 unusable. (Bulletproofs against bug 222.)
9488 o Minor bugfixes (other):
9489 - In the exitlist script, only consider the most recently published
9490 server descriptor for each server. Also, when the user requests
9491 a list of servers that _reject_ connections to a given address,
9492 explicitly exclude the IPs that also have servers that accept
9493 connections to that address. (Resolves bug 405.)
9494 - Stop allowing hibernating servers to be "stable" or "fast".
9495 - On Windows, we were preventing other processes from reading
9496 cached-routers while Tor was running. (Reported by janbar)
9497 - Make the NodeFamilies config option work. (Reported by
9498 lodger -- it has never actually worked, even though we added it
9500 - Check return values from pthread_mutex functions.
9501 - Don't save non-general-purpose router descriptors to the disk cache,
9502 because we have no way of remembering what their purpose was when
9504 - Add even more asserts to hunt down bug 417.
9505 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
9506 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
9507 Add a log message to confirm that it is in fact unlikely.
9509 o Minor bugfixes (controller):
9510 - Make 'getinfo fingerprint' return a 551 error if we're not a
9511 server, so we match what the control spec claims we do. Reported
9513 - Fix a typo in an error message when extendcircuit fails that
9514 caused us to not follow the \r\n-based delimiter protocol. Reported
9517 o Code simplifications and refactoring:
9518 - Stop passing around circuit_t and crypt_path_t pointers that are
9519 implicit in other procedure arguments.
9520 - Drop the old code to choke directory connections when the
9521 corresponding OR connections got full: thanks to the cell queue
9522 feature, OR conns don't get full any more.
9523 - Make dns_resolve() handle attaching connections to circuits
9524 properly, so the caller doesn't have to.
9525 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
9526 - Keep the connection array as a dynamic smartlist_t, rather than as
9527 a fixed-sized array. This is important, as the number of connections
9528 is becoming increasingly decoupled from the number of sockets.
9531 Changes in version 0.1.2.14 - 2007-05-25
9532 Tor 0.1.2.14 changes the addresses of two directory authorities (this
9533 change especially affects those who serve or use hidden services),
9534 and fixes several other crash- and security-related bugs.
9536 o Directory authority changes:
9537 - Two directory authorities (moria1 and moria2) just moved to new
9538 IP addresses. This change will particularly affect those who serve
9539 or use hidden services.
9541 o Major bugfixes (crashes):
9542 - If a directory server runs out of space in the connection table
9543 as it's processing a begin_dir request, it will free the exit stream
9544 but leave it attached to the circuit, leading to unpredictable
9545 behavior. (Reported by seeess, fixes bug 425.)
9546 - Fix a bug in dirserv_remove_invalid() that would cause authorities
9547 to corrupt memory under some really unlikely scenarios.
9548 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
9549 - Avoid segfaults when reading from mmaped descriptor file. (Reported
9552 o Major bugfixes (security):
9553 - When choosing an entry guard for a circuit, avoid using guards
9554 that are in the same family as the chosen exit -- not just guards
9555 that are exactly the chosen exit. (Reported by lodger.)
9557 o Major bugfixes (resource management):
9558 - If a directory authority is down, skip it when deciding where to get
9559 networkstatus objects or descriptors. Otherwise we keep asking
9560 every 10 seconds forever. Fixes bug 384.
9561 - Count it as a failure if we fetch a valid network-status but we
9562 don't want to keep it. Otherwise we'll keep fetching it and keep
9563 not wanting to keep it. Fixes part of bug 422.
9564 - If all of our dirservers have given us bad or no networkstatuses
9565 lately, then stop hammering them once per minute even when we
9566 think they're failed. Fixes another part of bug 422.
9569 - Actually set the purpose correctly for descriptors inserted with
9571 - When we have k non-v2 authorities in our DirServer config,
9572 we ignored the last k authorities in the list when updating our
9574 - Correctly back-off from requesting router descriptors that we are
9575 having a hard time downloading.
9576 - Read resolv.conf files correctly on platforms where read() returns
9577 partial results on small file reads.
9578 - Don't rebuild the entire router store every time we get 32K of
9579 routers: rebuild it when the journal gets very large, or when
9580 the gaps in the store get very large.
9583 - When routers publish SVN revisions in their router descriptors,
9584 authorities now include those versions correctly in networkstatus
9586 - Warn when using a version of libevent before 1.3b to run a server on
9587 OSX or BSD: these versions interact badly with userspace threads.
9590 Changes in version 0.1.2.13 - 2007-04-24
9591 This release features some major anonymity fixes, such as safer path
9592 selection; better client performance; faster bootstrapping, better
9593 address detection, and better DNS support for servers; write limiting as
9594 well as read limiting to make servers easier to run; and a huge pile of
9595 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
9597 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
9598 of the Freenode IRC network, remembering his patience and vision for
9599 free speech on the Internet.
9602 - Fix a memory leak when we ask for "all" networkstatuses and we
9603 get one we don't recognize.
9604 - Add more asserts to hunt down bug 417.
9605 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
9608 Changes in version 0.1.2.12-rc - 2007-03-16
9610 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
9611 directory information requested inside Tor connections (i.e. via
9612 begin_dir cells). It only triggered when the same connection was
9613 serving other data at the same time. Reported by seeess.
9616 - When creating a circuit via the controller, send a 'launched'
9617 event when we're done, so we follow the spec better.
9620 Changes in version 0.1.2.11-rc - 2007-03-15
9621 o Minor bugfixes (controller), reported by daejees:
9622 - Correct the control spec to match how the code actually responds
9623 to 'getinfo addr-mappings/*'.
9624 - The control spec described a GUARDS event, but the code
9625 implemented a GUARD event. Standardize on GUARD, but let people
9629 Changes in version 0.1.2.10-rc - 2007-03-07
9630 o Major bugfixes (Windows):
9631 - Do not load the NT services library functions (which may not exist)
9632 just to detect if we're a service trying to shut down. Now we run
9633 on Win98 and friends again.
9635 o Minor bugfixes (other):
9636 - Clarify a couple of log messages.
9637 - Fix a misleading socks5 error number.
9640 Changes in version 0.1.2.9-rc - 2007-03-02
9641 o Major bugfixes (Windows):
9642 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
9643 of the usual GCC "%llu". This prevents a bug when saving 64-bit
9644 int configuration values: the high-order 32 bits would get
9645 truncated. In particular, we were being bitten by the default
9646 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
9647 and maybe also bug 397.)
9649 o Minor bugfixes (performance):
9650 - Use OpenSSL's AES implementation on platforms where it's faster.
9651 This could save us as much as 10% CPU usage.
9653 o Minor bugfixes (server):
9654 - Do not rotate onion key immediately after setting it for the first
9657 o Minor bugfixes (directory authorities):
9658 - Stop calling servers that have been hibernating for a long time
9659 "stable". Also, stop letting hibernating or obsolete servers affect
9660 uptime and bandwidth cutoffs.
9661 - Stop listing hibernating servers in the v1 directory.
9663 o Minor bugfixes (hidden services):
9664 - Upload hidden service descriptors slightly less often, to reduce
9665 load on authorities.
9667 o Minor bugfixes (other):
9668 - Fix an assert that could trigger if a controller quickly set then
9669 cleared EntryNodes. Bug found by Udo van den Heuvel.
9670 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
9672 - Fix a potential race condition in the rpm installer. Found by
9674 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
9675 of 2 as indicating that the server is completely bad; it sometimes
9676 means that the server is just bad for the request in question. (may fix
9677 the last of bug 326.)
9678 - Disable encrypted directory connections when we don't have a server
9679 descriptor for the destination. We'll get this working again in
9683 Changes in version 0.1.2.8-beta - 2007-02-26
9684 o Major bugfixes (crashes):
9685 - Stop crashing when the controller asks us to resetconf more than
9686 one config option at once. (Vidalia 0.0.11 does this.)
9687 - Fix a crash that happened on Win98 when we're given command-line
9688 arguments: don't try to load NT service functions from advapi32.dll
9689 except when we need them. (Bug introduced in 0.1.2.7-alpha;
9691 - Fix a longstanding obscure crash bug that could occur when
9692 we run out of DNS worker processes. (Resolves bug 390.)
9694 o Major bugfixes (hidden services):
9695 - Correctly detect whether hidden service descriptor downloads are
9696 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
9698 o Major bugfixes (accounting):
9699 - When we start during an accounting interval before it's time to wake
9700 up, remember to wake up at the correct time. (May fix bug 342.)
9702 o Minor bugfixes (controller):
9703 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
9704 clear the corresponding on_circuit variable, and remember later
9705 that we don't need to send a redundant CLOSED event. Resolves part
9707 - Report events where a resolve succeeded or where we got a socks
9708 protocol error correctly, rather than calling both of them
9710 - Change reported stream target addresses to IP consistently when
9711 we finally get the IP from an exit node.
9712 - Send log messages to the controller even if they happen to be very
9715 o Minor bugfixes (other):
9716 - Display correct results when reporting which versions are
9717 recommended, and how recommended they are. (Resolves bug 383.)
9718 - Improve our estimates for directory bandwidth to be less random:
9719 guess that an unrecognized directory will have the average bandwidth
9720 from all known directories, not that it will have the average
9721 bandwidth from those directories earlier than it on the list.
9722 - If we start a server with ClientOnly 1, then set ClientOnly to 0
9723 and hup, stop triggering an assert based on an empty onion_key.
9724 - On platforms with no working mmap() equivalent, don't warn the
9725 user when cached-routers doesn't exist.
9726 - Warn the user when mmap() [or its equivalent] fails for some reason
9727 other than file-not-found.
9728 - Don't warn the user when cached-routers.new doesn't exist: that's
9729 perfectly fine when starting up for the first time.
9730 - When EntryNodes are configured, rebuild the guard list to contain,
9731 in order: the EntryNodes that were guards before; the rest of the
9732 EntryNodes; the nodes that were guards before.
9733 - Mask out all signals in sub-threads; only the libevent signal
9734 handler should be processing them. This should prevent some crashes
9735 on some machines using pthreads. (Patch from coderman.)
9736 - Fix switched arguments on memset in the implementation of
9737 tor_munmap() for systems with no mmap() call.
9738 - When Tor receives a router descriptor that it asked for, but
9739 no longer wants (because it has received fresh networkstatuses
9740 in the meantime), do not warn the user. Cache the descriptor if
9741 we're a cache; drop it if we aren't.
9742 - Make earlier entry guards _really_ get retried when the network
9744 - On a malformed DNS reply, always give an error to the corresponding
9746 - Build with recent libevents on platforms that do not define the
9747 nonstandard types "u_int8_t" and friends.
9749 o Minor features (controller):
9750 - Warn the user when an application uses the obsolete binary v0
9751 control protocol. We're planning to remove support for it during
9752 the next development series, so it's good to give people some
9754 - Add STREAM_BW events to report per-entry-stream bandwidth
9755 use. (Patch from Robert Hogan.)
9756 - Rate-limit SIGNEWNYM signals in response to controllers that
9757 impolitely generate them for every single stream. (Patch from
9758 mwenge; closes bug 394.)
9759 - Make REMAP stream events have a SOURCE (cache or exit), and
9760 make them generated in every case where we get a successful
9761 connected or resolved cell.
9763 o Minor bugfixes (performance):
9764 - Call router_have_min_dir_info half as often. (This is showing up in
9765 some profiles, but not others.)
9766 - When using GCC, make log_debug never get called at all, and its
9767 arguments never get evaluated, when no debug logs are configured.
9768 (This is showing up in some profiles, but not others.)
9771 - Remove some never-implemented options. Mark PathlenCoinWeight as
9773 - Implement proposal 106: Stop requiring clients to have well-formed
9774 certificates; stop checking nicknames in certificates. (Clients
9775 have certificates so that they can look like Tor servers, but in
9776 the future we might want to allow them to look like regular TLS
9777 clients instead. Nicknames in certificates serve no purpose other
9778 than making our protocol easier to recognize on the wire.)
9779 - Revise messages on handshake failure again to be even more clear about
9780 which are incoming connections and which are outgoing.
9781 - Discard any v1 directory info that's over 1 month old (for
9782 directories) or over 1 week old (for running-routers lists).
9783 - Do not warn when individual nodes in the configuration's EntryNodes,
9784 ExitNodes, etc are down: warn only when all possible nodes
9785 are down. (Fixes bug 348.)
9786 - Always remove expired routers and networkstatus docs before checking
9787 whether we have enough information to build circuits. (Fixes
9789 - Put a lower-bound on MaxAdvertisedBandwidth.
9792 Changes in version 0.1.2.7-alpha - 2007-02-06
9793 o Major bugfixes (rate limiting):
9794 - Servers decline directory requests much more aggressively when
9795 they're low on bandwidth. Otherwise they end up queueing more and
9796 more directory responses, which can't be good for latency.
9797 - But never refuse directory requests from local addresses.
9798 - Fix a memory leak when sending a 503 response for a networkstatus
9800 - Be willing to read or write on local connections (e.g. controller
9801 connections) even when the global rate limiting buckets are empty.
9802 - If our system clock jumps back in time, don't publish a negative
9803 uptime in the descriptor. Also, don't let the global rate limiting
9804 buckets go absurdly negative.
9805 - Flush local controller connection buffers periodically as we're
9806 writing to them, so we avoid queueing 4+ megabytes of data before
9809 o Major bugfixes (NT services):
9810 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
9811 command-line flag so that admins can override the default by saying
9812 "tor --service install --user "SomeUser"". This will not affect
9813 existing installed services. Also, warn the user that the service
9814 will look for its configuration file in the service user's
9815 %appdata% directory. (We can't do the 'hardwire the user's appdata
9816 directory' trick any more, since we may not have read access to that
9819 o Major bugfixes (other):
9820 - Previously, we would cache up to 16 old networkstatus documents
9821 indefinitely, if they came from nontrusted authorities. Now we
9822 discard them if they are more than 10 days old.
9823 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
9825 - Detect and reject malformed DNS responses containing circular
9827 - If exits are rare enough that we're not marking exits as guards,
9828 ignore exit bandwidth when we're deciding the required bandwidth
9830 - When we're handling a directory connection tunneled over Tor,
9831 don't fill up internal memory buffers with all the data we want
9832 to tunnel; instead, only add it if the OR connection that will
9833 eventually receive it has some room for it. (This can lead to
9834 slowdowns in tunneled dir connections; a better solution will have
9837 o Minor bugfixes (dns):
9838 - Add some defensive programming to eventdns.c in an attempt to catch
9839 possible memory-stomping bugs.
9840 - Detect and reject DNS replies containing IPv4 or IPv6 records with
9841 an incorrect number of bytes. (Previously, we would ignore the
9843 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
9844 in the correct order, and doesn't crash.
9845 - Free memory held in recently-completed DNS lookup attempts on exit.
9846 This was not a memory leak, but may have been hiding memory leaks.
9847 - Handle TTL values correctly on reverse DNS lookups.
9848 - Treat failure to parse resolv.conf as an error.
9850 o Minor bugfixes (other):
9851 - Fix crash with "tor --list-fingerprint" (reported by seeess).
9852 - When computing clock skew from directory HTTP headers, consider what
9853 time it was when we finished asking for the directory, not what
9855 - Expire socks connections if they spend too long waiting for the
9856 handshake to finish. Previously we would let them sit around for
9857 days, if the connecting application didn't close them either.
9858 - And if the socks handshake hasn't started, don't send a
9859 "DNS resolve socks failed" handshake reply; just close it.
9860 - Stop using C functions that OpenBSD's linker doesn't like.
9861 - Don't launch requests for descriptors unless we have networkstatuses
9862 from at least half of the authorities. This delays the first
9863 download slightly under pathological circumstances, but can prevent
9864 us from downloading a bunch of descriptors we don't need.
9865 - Do not log IPs with TLS failures for incoming TLS
9866 connections. (Fixes bug 382.)
9867 - If the user asks to use invalid exit nodes, be willing to use
9869 - Stop using the reserved ac_cv namespace in our configure script.
9870 - Call stat() slightly less often; use fstat() when possible.
9871 - Refactor the way we handle pending circuits when an OR connection
9872 completes or fails, in an attempt to fix a rare crash bug.
9873 - Only rewrite a conn's address based on X-Forwarded-For: headers
9874 if it's a parseable public IP address; and stop adding extra quotes
9875 to the resulting address.
9878 - Weight directory requests by advertised bandwidth. Now we can
9879 let servers enable write limiting but still allow most clients to
9880 succeed at their directory requests. (We still ignore weights when
9881 choosing a directory authority; I hope this is a feature.)
9884 - Create a new file ReleaseNotes which was the old ChangeLog. The
9885 new ChangeLog file now includes the summaries for all development
9887 - Check for addresses with invalid characters at the exit as well
9888 as at the client, and warn less verbosely when they fail. You can
9889 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
9890 - Adapt a patch from goodell to let the contrib/exitlist script
9891 take arguments rather than require direct editing.
9892 - Inform the server operator when we decide not to advertise a
9893 DirPort due to AccountingMax enabled or a low BandwidthRate. It
9894 was confusing Zax, so now we're hopefully more helpful.
9895 - Bring us one step closer to being able to establish an encrypted
9896 directory tunnel without knowing a descriptor first. Still not
9897 ready yet. As part of the change, now assume we can use a
9898 create_fast cell if we don't know anything about a router.
9899 - Allow exit nodes to use nameservers running on ports other than 53.
9900 - Servers now cache reverse DNS replies.
9901 - Add an --ignore-missing-torrc command-line option so that we can
9902 get the "use sensible defaults if the configuration file doesn't
9903 exist" behavior even when specifying a torrc location on the command
9906 o Minor features (controller):
9907 - Track reasons for OR connection failure; make these reasons
9908 available via the controller interface. (Patch from Mike Perry.)
9909 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
9910 can learn when clients are sending malformed hostnames to Tor.
9911 - Clean up documentation for controller status events.
9912 - Add a REMAP status to stream events to note that a stream's
9913 address has changed because of a cached address or a MapAddress
9917 Changes in version 0.1.2.6-alpha - 2007-01-09
9919 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
9920 connection handles more than 4 gigs in either direction, we crash.
9921 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
9922 advertised exit node, somebody might try to exit from us when
9923 we're bootstrapping and before we've built our descriptor yet.
9924 Refuse the connection rather than crashing.
9927 - Warn if we (as a server) find that we've resolved an address that we
9928 weren't planning to resolve.
9929 - Warn that using select() on any libevent version before 1.1 will be
9930 unnecessarily slow (even for select()).
9931 - Flush ERR-level controller status events just like we currently
9932 flush ERR-level log events, so that a Tor shutdown doesn't prevent
9933 the controller from learning about current events.
9935 o Minor features (more controller status events):
9936 - Implement EXTERNAL_ADDRESS server status event so controllers can
9937 learn when our address changes.
9938 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
9939 can learn when directories reject our descriptor.
9940 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
9941 can learn when a client application is speaking a non-socks protocol
9943 - Implement DANGEROUS_SOCKS client status event so controllers
9944 can learn when a client application is leaking DNS addresses.
9945 - Implement BUG general status event so controllers can learn when
9946 Tor is unhappy about its internal invariants.
9947 - Implement CLOCK_SKEW general status event so controllers can learn
9948 when Tor thinks the system clock is set incorrectly.
9949 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
9950 server status events so controllers can learn when their descriptors
9951 are accepted by a directory.
9952 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
9953 server status events so controllers can learn about Tor's progress in
9954 deciding whether it's reachable from the outside.
9955 - Implement BAD_LIBEVENT general status event so controllers can learn
9956 when we have a version/method combination in libevent that needs to
9958 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
9959 and DNS_USELESS server status events so controllers can learn
9960 about changes to DNS server status.
9962 o Minor features (directory):
9963 - Authorities no longer recommend exits as guards if this would shift
9964 too much load to the exit nodes.
9967 Changes in version 0.1.2.5-alpha - 2007-01-06
9969 - Enable write limiting as well as read limiting. Now we sacrifice
9970 capacity if we're pushing out lots of directory traffic, rather
9971 than overrunning the user's intended bandwidth limits.
9972 - Include TLS overhead when counting bandwidth usage; previously, we
9973 would count only the bytes sent over TLS, but not the bytes used
9975 - Support running the Tor service with a torrc not in the same
9976 directory as tor.exe and default to using the torrc located in
9977 the %appdata%\Tor\ of the user who installed the service. Patch
9979 - Servers now check for the case when common DNS requests are going to
9980 wildcarded addresses (i.e. all getting the same answer), and change
9981 their exit policy to reject *:* if it's happening.
9982 - Implement BEGIN_DIR cells, so we can connect to the directory
9983 server via TLS to do encrypted directory requests rather than
9984 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
9985 config options if you like.
9987 o Minor features (config and docs):
9988 - Start using the state file to store bandwidth accounting data:
9989 the bw_accounting file is now obsolete. We'll keep generating it
9990 for a while for people who are still using 0.1.2.4-alpha.
9991 - Try to batch changes to the state file so that we do as few
9992 disk writes as possible while still storing important things in
9994 - The state file and the bw_accounting file get saved less often when
9995 the AvoidDiskWrites config option is set.
9996 - Make PIDFile work on Windows (untested).
9997 - Add internal descriptions for a bunch of configuration options:
9998 accessible via controller interface and in comments in saved
10000 - Reject *:563 (NNTPS) in the default exit policy. We already reject
10001 NNTP by default, so this seems like a sensible addition.
10002 - Clients now reject hostnames with invalid characters. This should
10003 avoid some inadvertent info leaks. Add an option
10004 AllowNonRFC953Hostnames to disable this behavior, in case somebody
10005 is running a private network with hosts called @, !, and #.
10006 - Add a maintainer script to tell us which options are missing
10007 documentation: "make check-docs".
10008 - Add a new address-spec.txt document to describe our special-case
10009 addresses: .exit, .onion, and .noconnnect.
10011 o Minor features (DNS):
10012 - Ongoing work on eventdns infrastructure: now it has dns server
10013 and ipv6 support. One day Tor will make use of it.
10014 - Add client-side caching for reverse DNS lookups.
10015 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
10016 - When we change nameservers or IP addresses, reset and re-launch
10017 our tests for DNS hijacking.
10019 o Minor features (directory):
10020 - Authorities now specify server versions in networkstatus. This adds
10021 about 2% to the size of compressed networkstatus docs, and allows
10022 clients to tell which servers support BEGIN_DIR and which don't.
10023 The implementation is forward-compatible with a proposed future
10024 protocol version scheme not tied to Tor versions.
10025 - DirServer configuration lines now have an orport= option so
10026 clients can open encrypted tunnels to the authorities without
10027 having downloaded their descriptors yet. Enabled for moria1,
10028 moria2, tor26, and lefkada now in the default configuration.
10029 - Directory servers are more willing to send a 503 "busy" if they
10030 are near their write limit, especially for v1 directory requests.
10031 Now they can use their limited bandwidth for actual Tor traffic.
10032 - Clients track responses with status 503 from dirservers. After a
10033 dirserver has given us a 503, we try not to use it until an hour has
10034 gone by, or until we have no dirservers that haven't given us a 503.
10035 - When we get a 503 from a directory, and we're not a server, we don't
10036 count the failure against the total number of failures allowed
10037 for the thing we're trying to download.
10038 - Report X-Your-Address-Is correctly from tunneled directory
10039 connections; don't report X-Your-Address-Is when it's an internal
10040 address; and never believe reported remote addresses when they're
10042 - Protect against an unlikely DoS attack on directory servers.
10043 - Add a BadDirectory flag to network status docs so that authorities
10044 can (eventually) tell clients about caches they believe to be
10047 o Minor features (controller):
10048 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
10049 - Reimplement GETINFO so that info/names stays in sync with the
10051 - Implement "GETINFO fingerprint".
10052 - Implement "SETEVENTS GUARD" so controllers can get updates on
10053 entry guard status as it changes.
10055 o Minor features (clean up obsolete pieces):
10056 - Remove some options that have been deprecated since at least
10057 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
10058 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
10059 to set log options.
10060 - We no longer look for identity and onion keys in "identity.key" and
10061 "onion.key" -- these were replaced by secret_id_key and
10062 secret_onion_key in 0.0.8pre1.
10063 - We no longer require unrecognized directory entries to be
10066 o Major bugfixes (security):
10067 - Stop sending the HttpProxyAuthenticator string to directory
10068 servers when directory connections are tunnelled through Tor.
10069 - Clients no longer store bandwidth history in the state file.
10070 - Do not log introduction points for hidden services if SafeLogging
10072 - When generating bandwidth history, round down to the nearest
10073 1k. When storing accounting data, round up to the nearest 1k.
10074 - When we're running as a server, remember when we last rotated onion
10075 keys, so that we will rotate keys once they're a week old even if
10076 we never stay up for a week ourselves.
10078 o Major bugfixes (other):
10079 - Fix a longstanding bug in eventdns that prevented the count of
10080 timed-out resolves from ever being reset. This bug caused us to
10081 give up on a nameserver the third time it timed out, and try it
10082 10 seconds later... and to give up on it every time it timed out
10084 - Take out the '5 second' timeout from the connection retry
10085 schedule. Now the first connect attempt will wait a full 10
10086 seconds before switching to a new circuit. Perhaps this will help
10087 a lot. Based on observations from Mike Perry.
10088 - Fix a bug on the Windows implementation of tor_mmap_file() that
10089 would prevent the cached-routers file from ever loading. Reported
10093 - Fix an assert failure when a directory authority sets
10094 AuthDirRejectUnlisted and then receives a descriptor from an
10095 unlisted router. Reported by seeess.
10096 - Avoid a double-free when parsing malformed DirServer lines.
10097 - Fix a bug when a BSD-style PF socket is first used. Patch from
10099 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
10100 to resolve an address at a given exit node even when they ask for
10102 - Servers no longer ever list themselves in their "family" line,
10103 even if configured to do so. This makes it easier to configure
10104 family lists conveniently.
10105 - When running as a server, don't fall back to 127.0.0.1 when no
10106 nameservers are configured in /etc/resolv.conf; instead, make the
10107 user fix resolv.conf or specify nameservers explicitly. (Resolves
10109 - Stop accepting certain malformed ports in configured exit policies.
10110 - Don't re-write the fingerprint file every restart, unless it has
10112 - Stop warning when a single nameserver fails: only warn when _all_ of
10113 our nameservers have failed. Also, when we only have one nameserver,
10114 raise the threshold for deciding that the nameserver is dead.
10115 - Directory authorities now only decide that routers are reachable
10116 if their identity keys are as expected.
10117 - When the user uses bad syntax in the Log config line, stop
10118 suggesting other bad syntax as a replacement.
10119 - Correctly detect ipv6 DNS capability on OpenBSD.
10121 o Minor bugfixes (controller):
10122 - Report the circuit number correctly in STREAM CLOSED events. Bug
10123 reported by Mike Perry.
10124 - Do not report bizarre values for results of accounting GETINFOs
10125 when the last second's write or read exceeds the allotted bandwidth.
10126 - Report "unrecognized key" rather than an empty string when the
10127 controller tries to fetch a networkstatus that doesn't exist.
10130 Changes in version 0.1.1.26 - 2006-12-14
10131 o Security bugfixes:
10132 - Stop sending the HttpProxyAuthenticator string to directory
10133 servers when directory connections are tunnelled through Tor.
10134 - Clients no longer store bandwidth history in the state file.
10135 - Do not log introduction points for hidden services if SafeLogging
10139 - Fix an assert failure when a directory authority sets
10140 AuthDirRejectUnlisted and then receives a descriptor from an
10141 unlisted router (reported by seeess).
10144 Changes in version 0.1.2.4-alpha - 2006-12-03
10146 - Add support for using natd; this allows FreeBSDs earlier than
10147 5.1.2 to have ipfw send connections through Tor without using
10148 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
10151 - Make all connections to addresses of the form ".noconnect"
10152 immediately get closed. This lets application/controller combos
10153 successfully test whether they're talking to the same Tor by
10154 watching for STREAM events.
10155 - Make cross.sh cross-compilation script work even when autogen.sh
10156 hasn't been run. (Patch from Michael Mohr.)
10157 - Statistics dumped by -USR2 now include a breakdown of public key
10158 operations, for profiling.
10161 - Fix a major leak when directory authorities parse their
10162 approved-routers list, a minor memory leak when we fail to pick
10163 an exit node, and a few rare leaks on errors.
10164 - Handle TransPort connections even when the server sends data before
10165 the client sends data. Previously, the connection would just hang
10166 until the client sent data. (Patch from tup based on patch from
10168 - Avoid assert failure when our cached-routers file is empty on
10172 - Don't log spurious warnings when we see a circuit close reason we
10173 don't recognize; it's probably just from a newer version of Tor.
10174 - Have directory authorities allow larger amounts of drift in uptime
10175 without replacing the server descriptor: previously, a server that
10176 restarted every 30 minutes could have 48 "interesting" descriptors
10178 - Start linking to the Tor specification and Tor reference manual
10179 correctly in the Windows installer.
10180 - Add Vidalia to the OS X uninstaller script, so when we uninstall
10181 Tor/Privoxy we also uninstall Vidalia.
10182 - Resume building on Irix64, and fix a lot of warnings from its
10183 MIPSpro C compiler.
10184 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
10185 when we're running as a client.
10188 Changes in version 0.1.1.25 - 2006-11-04
10190 - When a client asks us to resolve (rather than connect to)
10191 an address, and we have a cached answer, give them the cached
10192 answer. Previously, we would give them no answer at all.
10193 - We were building exactly the wrong circuits when we predict
10194 hidden service requirements, meaning Tor would have to build all
10195 its circuits on demand.
10196 - If none of our live entry guards have a high uptime, but we
10197 require a guard with a high uptime, try adding a new guard before
10198 we give up on the requirement. This patch should make long-lived
10199 connections more stable on average.
10200 - When testing reachability of our DirPort, don't launch new
10201 tests when there's already one in progress -- unreachable
10202 servers were stacking up dozens of testing streams.
10204 o Security bugfixes:
10205 - When the user sends a NEWNYM signal, clear the client-side DNS
10206 cache too. Otherwise we continue to act on previous information.
10209 - Avoid a memory corruption bug when creating a hash table for
10211 - Avoid possibility of controller-triggered crash when misusing
10212 certain commands from a v0 controller on platforms that do not
10213 handle printf("%s",NULL) gracefully.
10214 - Avoid infinite loop on unexpected controller input.
10215 - Don't log spurious warnings when we see a circuit close reason we
10216 don't recognize; it's probably just from a newer version of Tor.
10217 - Add Vidalia to the OS X uninstaller script, so when we uninstall
10218 Tor/Privoxy we also uninstall Vidalia.
10221 Changes in version 0.1.2.3-alpha - 2006-10-29
10223 - Prepare for servers to publish descriptors less often: never
10224 discard a descriptor simply for being too old until either it is
10225 recommended by no authorities, or until we get a better one for
10226 the same router. Make caches consider retaining old recommended
10227 routers for even longer.
10228 - If most authorities set a BadExit flag for a server, clients
10229 don't think of it as a general-purpose exit. Clients only consider
10230 authorities that advertise themselves as listing bad exits.
10231 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
10232 headers for content, so that we can work better in the presence of
10233 caching HTTP proxies.
10234 - Allow authorities to list nodes as bad exits by fingerprint or by
10237 o Minor features, controller:
10238 - Add a REASON field to CIRC events; for backward compatibility, this
10239 field is sent only to controllers that have enabled the extended
10240 event format. Also, add additional reason codes to explain why
10241 a given circuit has been destroyed or truncated. (Patches from
10243 - Add a REMOTE_REASON field to extended CIRC events to tell the
10244 controller about why a remote OR told us to close a circuit.
10245 - Stream events also now have REASON and REMOTE_REASON fields,
10246 working much like those for circuit events.
10247 - There's now a GETINFO ns/... field so that controllers can ask Tor
10248 about the current status of a router.
10249 - A new event type "NS" to inform a controller when our opinion of
10250 a router's status has changed.
10251 - Add a GETINFO events/names and GETINFO features/names so controllers
10252 can tell which events and features are supported.
10253 - A new CLEARDNSCACHE signal to allow controllers to clear the
10254 client-side DNS cache without expiring circuits.
10256 o Security bugfixes:
10257 - When the user sends a NEWNYM signal, clear the client-side DNS
10258 cache too. Otherwise we continue to act on previous information.
10261 - Avoid sending junk to controllers or segfaulting when a controller
10262 uses EVENT_NEW_DESC with verbose nicknames.
10263 - Stop triggering asserts if the controller tries to extend hidden
10264 service circuits (reported by mwenge).
10265 - Avoid infinite loop on unexpected controller input.
10266 - When the controller does a "GETINFO network-status", tell it
10267 about even those routers whose descriptors are very old, and use
10268 long nicknames where appropriate.
10269 - Change NT service functions to be loaded on demand. This lets us
10270 build with MinGW without breaking Tor for Windows 98 users.
10271 - Do DirPort reachability tests less often, since a single test
10272 chews through many circuits before giving up.
10273 - In the hidden service example in torrc.sample, stop recommending
10274 esoteric and discouraged hidden service options.
10275 - When stopping an NT service, wait up to 10 sec for it to actually
10276 stop. Patch from Matt Edman; resolves bug 295.
10277 - Fix handling of verbose nicknames with ORCONN controller events:
10278 make them show up exactly when requested, rather than exactly when
10280 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
10281 printing a duplicate "$" in the keys we send (reported by mwenge).
10282 - Correctly set maximum connection limit on Cygwin. (This time
10284 - Try to detect Windows correctly when cross-compiling.
10285 - Detect the size of the routers file correctly even if it is
10286 corrupted (on systems without mmap) or not page-aligned (on systems
10287 with mmap). This bug was harmless.
10288 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
10289 to open a stream fails; now we do in more cases. This should
10290 make clients able to find a good exit faster in some cases, since
10291 unhandleable requests will now get an error rather than timing out.
10292 - Resolve two memory leaks when rebuilding the on-disk router cache
10293 (reported by fookoowa).
10294 - Clean up minor code warnings suggested by the MIPSpro C compiler,
10295 and reported by some Centos users.
10296 - Controller signals now work on non-Unix platforms that don't define
10297 SIGUSR1 and SIGUSR2 the way we expect.
10298 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
10299 values before failing, and always enables eventdns.
10300 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
10301 Try to fix this in configure.in by checking for most functions
10302 before we check for libevent.
10305 Changes in version 0.1.2.2-alpha - 2006-10-07
10307 - Make our async eventdns library on-by-default for Tor servers,
10308 and plan to deprecate the separate dnsworker threads.
10309 - Add server-side support for "reverse" DNS lookups (using PTR
10310 records so clients can determine the canonical hostname for a given
10311 IPv4 address). Only supported by servers using eventdns; servers
10312 now announce in their descriptors whether they support eventdns.
10313 - Specify and implement client-side SOCKS5 interface for reverse DNS
10314 lookups (see doc/socks-extensions.txt).
10315 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
10316 connect to directory servers through Tor. Previously, clients needed
10317 to find Tor exits to make private connections to directory servers.
10318 - Avoid choosing Exit nodes for entry or middle hops when the
10319 total bandwidth available from non-Exit nodes is much higher than
10320 the total bandwidth available from Exit nodes.
10321 - Workaround for name servers (like Earthlink's) that hijack failing
10322 DNS requests and replace the no-such-server answer with a "helpful"
10323 redirect to an advertising-driven search portal. Also work around
10324 DNS hijackers who "helpfully" decline to hijack known-invalid
10325 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
10326 lets you turn it off.
10327 - Send out a burst of long-range padding cells once we've established
10328 that we're reachable. Spread them over 4 circuits, so hopefully
10329 a few will be fast. This exercises our bandwidth and bootstraps
10330 us into the directory more quickly.
10332 o New/improved config options:
10333 - Add new config option "ResolvConf" to let the server operator
10334 choose an alternate resolve.conf file when using eventdns.
10335 - Add an "EnforceDistinctSubnets" option to control our "exclude
10336 servers on the same /16" behavior. It's still on by default; this
10337 is mostly for people who want to operate private test networks with
10338 all the machines on the same subnet.
10339 - If one of our entry guards is on the ExcludeNodes list, or the
10340 directory authorities don't think it's a good guard, treat it as
10341 if it were unlisted: stop using it as a guard, and throw it off
10342 the guards list if it stays that way for a long time.
10343 - Allow directory authorities to be marked separately as authorities
10344 for the v1 directory protocol, the v2 directory protocol, and
10345 as hidden service directories, to make it easier to retire old
10346 authorities. V1 authorities should set "HSAuthoritativeDir 1"
10347 to continue being hidden service authorities too.
10348 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
10350 o Minor features, controller:
10351 - Fix CIRC controller events so that controllers can learn the
10352 identity digests of non-Named servers used in circuit paths.
10353 - Let controllers ask for more useful identifiers for servers. Instead
10354 of learning identity digests for un-Named servers and nicknames
10355 for Named servers, the new identifiers include digest, nickname,
10356 and indication of Named status. Off by default; see control-spec.txt
10357 for more information.
10358 - Add a "getinfo address" controller command so it can display Tor's
10359 best guess to the user.
10360 - New controller event to alert the controller when our server
10361 descriptor has changed.
10362 - Give more meaningful errors on controller authentication failure.
10364 o Minor features, other:
10365 - When asked to resolve a hostname, don't use non-exit servers unless
10366 requested to do so. This allows servers with broken DNS to be
10367 useful to the network.
10368 - Divide eventdns log messages into warn and info messages.
10369 - Reserve the nickname "Unnamed" for routers that can't pick
10370 a hostname: any router can call itself Unnamed; directory
10371 authorities will never allocate Unnamed to any particular router;
10372 clients won't believe that any router is the canonical Unnamed.
10373 - Only include function names in log messages for info/debug messages.
10374 For notice/warn/err, the content of the message should be clear on
10375 its own, and printing the function name only confuses users.
10376 - Avoid some false positives during reachability testing: don't try
10377 to test via a server that's on the same /24 as us.
10378 - If we fail to build a circuit to an intended enclave, and it's
10379 not mandatory that we use that enclave, stop wanting it.
10380 - When eventdns is enabled, allow multithreaded builds on NetBSD and
10381 OpenBSD. (We had previously disabled threads on these platforms
10382 because they didn't have working thread-safe resolver functions.)
10384 o Major bugfixes, anonymity/security:
10385 - If a client asked for a server by name, and there's a named server
10386 in our network-status but we don't have its descriptor yet, we
10387 could return an unnamed server instead.
10388 - Fix NetBSD bug that could allow someone to force uninitialized RAM
10389 to be sent to a server's DNS resolver. This only affects NetBSD
10390 and other platforms that do not bounds-check tolower().
10391 - Reject (most) attempts to use Tor circuits with length one. (If
10392 many people start using Tor as a one-hop proxy, exit nodes become
10393 a more attractive target for compromise.)
10394 - Just because your DirPort is open doesn't mean people should be
10395 able to remotely teach you about hidden service descriptors. Now
10396 only accept rendezvous posts if you've got HSAuthoritativeDir set.
10398 o Major bugfixes, other:
10399 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
10400 - When a client asks the server to resolve (not connect to)
10401 an address, and it has a cached answer, give them the cached answer.
10402 Previously, the server would give them no answer at all.
10403 - Allow really slow clients to not hang up five minutes into their
10404 directory downloads (suggested by Adam J. Richter).
10405 - We were building exactly the wrong circuits when we anticipated
10406 hidden service requirements, meaning Tor would have to build all
10407 its circuits on demand.
10408 - Avoid crashing when we mmap a router cache file of size 0.
10409 - When testing reachability of our DirPort, don't launch new
10410 tests when there's already one in progress -- unreachable
10411 servers were stacking up dozens of testing streams.
10413 o Minor bugfixes, correctness:
10414 - If we're a directory mirror and we ask for "all" network status
10415 documents, we would discard status documents from authorities
10416 we don't recognize.
10417 - Avoid a memory corruption bug when creating a hash table for
10419 - Avoid controller-triggered crash when misusing certain commands
10420 from a v0 controller on platforms that do not handle
10421 printf("%s",NULL) gracefully.
10422 - Don't crash when a controller sends a third argument to an
10423 "extendcircuit" request.
10424 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10425 response; fix error code when "getinfo dir/status/" fails.
10426 - Avoid crash when telling controller stream-status and a stream
10428 - Patch from Adam Langley to fix assert() in eventdns.c.
10429 - Fix a debug log message in eventdns to say "X resolved to Y"
10430 instead of "X resolved to X".
10431 - Make eventdns give strings for DNS errors, not just error numbers.
10432 - Track unreachable entry guards correctly: don't conflate
10433 'unreachable by us right now' with 'listed as down by the directory
10434 authorities'. With the old code, if a guard was unreachable by
10435 us but listed as running, it would clog our guard list forever.
10436 - Behave correctly in case we ever have a network with more than
10437 2GB/s total advertised capacity.
10438 - Make TrackExitHosts case-insensitive, and fix the behavior of
10439 ".suffix" TrackExitHosts items to avoid matching in the middle of
10441 - Finally fix the openssl warnings from newer gccs that believe that
10442 ignoring a return value is okay, but casting a return value and
10443 then ignoring it is a sign of madness.
10444 - Prevent the contrib/exitlist script from printing the same
10445 result more than once.
10446 - Patch from Steve Hildrey: Generate network status correctly on
10447 non-versioning dirservers.
10448 - Don't listen to the X-Your-Address-Is hint if you did the lookup
10449 via Tor; otherwise you'll think you're the exit node's IP address.
10451 o Minor bugfixes, performance:
10452 - Two small performance improvements on parsing descriptors.
10453 - Major performance improvement on inserting descriptors: change
10454 algorithm from O(n^2) to O(n).
10455 - Make the common memory allocation path faster on machines where
10456 malloc(0) returns a pointer.
10457 - Start remembering X-Your-Address-Is directory hints even if you're
10458 a client, so you can become a server more smoothly.
10459 - Avoid duplicate entries on MyFamily line in server descriptor.
10461 o Packaging, features:
10462 - Remove architecture from OS X builds. The official builds are
10463 now universal binaries.
10464 - The Debian package now uses --verify-config when (re)starting,
10465 to distinguish configuration errors from other errors.
10466 - Update RPMs to require libevent 1.1b.
10468 o Packaging, bugfixes:
10469 - Patches so Tor builds with MinGW on Windows.
10470 - Patches so Tor might run on Cygwin again.
10471 - Resume building on non-gcc compilers and ancient gcc. Resume
10472 building with the -O0 compile flag. Resume building cleanly on
10474 - Run correctly on OS X platforms with case-sensitive filesystems.
10475 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
10476 - Add autoconf checks so Tor can build on Solaris x86 again.
10479 - Documented (and renamed) ServerDNSSearchDomains and
10480 ServerDNSResolvConfFile options.
10481 - Be clearer that the *ListenAddress directives can be repeated
10485 Changes in version 0.1.1.24 - 2006-09-29
10487 - Allow really slow clients to not hang up five minutes into their
10488 directory downloads (suggested by Adam J. Richter).
10489 - Fix major performance regression from 0.1.0.x: instead of checking
10490 whether we have enough directory information every time we want to
10491 do something, only check when the directory information has changed.
10492 This should improve client CPU usage by 25-50%.
10493 - Don't crash if, after a server has been running for a while,
10494 it can't resolve its hostname.
10497 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10498 - Don't crash when the controller receives a third argument to an
10499 "extendcircuit" request.
10500 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10501 response; fix error code when "getinfo dir/status/" fails.
10502 - Fix configure.in to not produce broken configure files with
10503 more recent versions of autoconf. Thanks to Clint for his auto*
10505 - Fix security bug on NetBSD that could allow someone to force
10506 uninitialized RAM to be sent to a server's DNS resolver. This
10507 only affects NetBSD and other platforms that do not bounds-check
10509 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
10510 methods: these are known to be buggy.
10511 - If we're a directory mirror and we ask for "all" network status
10512 documents, we would discard status documents from authorities
10513 we don't recognize.
10516 Changes in version 0.1.2.1-alpha - 2006-08-27
10518 - Add "eventdns" async dns library from Adam Langley, tweaked to
10519 build on OSX and Windows. Only enabled if you pass the
10520 --enable-eventdns argument to configure.
10521 - Allow servers with no hostname or IP address to learn their
10522 IP address by asking the directory authorities. This code only
10523 kicks in when you would normally have exited with a "no address"
10524 error. Nothing's authenticated, so use with care.
10525 - Rather than waiting a fixed amount of time between retrying
10526 application connections, we wait only 5 seconds for the first,
10527 10 seconds for the second, and 15 seconds for each retry after
10528 that. Hopefully this will improve the expected user experience.
10529 - Patch from Tup to add support for transparent AP connections:
10530 this basically bundles the functionality of trans-proxy-tor
10531 into the Tor mainline. Now hosts with compliant pf/netfilter
10532 implementations can redirect TCP connections straight to Tor
10533 without diverting through SOCKS. Needs docs.
10534 - Busy directory servers save lots of memory by spooling server
10535 descriptors, v1 directories, and v2 networkstatus docs to buffers
10536 as needed rather than en masse. Also mmap the cached-routers
10537 files, so we don't need to keep the whole thing in memory too.
10538 - Automatically avoid picking more than one node from the same
10539 /16 network when constructing a circuit.
10540 - Revise and clean up the torrc.sample that we ship with; add
10541 a section for BandwidthRate and BandwidthBurst.
10544 - Split circuit_t into origin_circuit_t and or_circuit_t, and
10545 split connection_t into edge, or, dir, control, and base structs.
10546 These will save quite a bit of memory on busy servers, and they'll
10547 also help us track down bugs in the code and bugs in the spec.
10548 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
10549 or later. Log when we are doing this, so we can diagnose it when
10550 it fails. (Also, recommend libevent 1.1b for kqueue and
10551 win32 methods; deprecate libevent 1.0b harder; make libevent
10552 recommendation system saner.)
10553 - Start being able to build universal binaries on OS X (thanks
10555 - Export the default exit policy via the control port, so controllers
10556 don't need to guess what it is / will be later.
10557 - Add a man page entry for ProtocolWarnings.
10558 - Add TestVia config option to the man page.
10559 - Remove even more protocol-related warnings from Tor server logs,
10560 such as bad TLS handshakes and malformed begin cells.
10561 - Stop fetching descriptors if you're not a dir mirror and you
10562 haven't tried to establish any circuits lately. [This currently
10563 causes some dangerous behavior, because when you start up again
10564 you'll use your ancient server descriptors.]
10565 - New DirPort behavior: if you have your dirport set, you download
10566 descriptors aggressively like a directory mirror, whether or not
10567 your ORPort is set.
10568 - Get rid of the router_retry_connections notion. Now routers
10569 no longer try to rebuild long-term connections to directory
10570 authorities, and directory authorities no longer try to rebuild
10571 long-term connections to all servers. We still don't hang up
10572 connections in these two cases though -- we need to look at it
10573 more carefully to avoid flapping, and we likely need to wait til
10574 0.1.1.x is obsolete.
10575 - Drop compatibility with obsolete Tors that permit create cells
10576 to have the wrong circ_id_type.
10577 - Re-enable per-connection rate limiting. Get rid of the "OP
10578 bandwidth" concept. Lay groundwork for "bandwidth classes" --
10579 separate global buckets that apply depending on what sort of conn
10581 - Start publishing one minute or so after we find our ORPort
10582 to be reachable. This will help reduce the number of descriptors
10583 we have for ourselves floating around, since it's quite likely
10584 other things (e.g. DirPort) will change during that minute too.
10585 - Fork the v1 directory protocol into its own spec document,
10586 and mark dir-spec.txt as the currently correct (v2) spec.
10589 - When we find our DirPort to be reachable, publish a new descriptor
10590 so we'll tell the world (reported by pnx).
10591 - Publish a new descriptor after we hup/reload. This is important
10592 if our config has changed such that we'll want to start advertising
10593 our DirPort now, etc.
10594 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10595 - When we have a state file we cannot parse, tell the user and
10596 move it aside. Now we avoid situations where the user starts
10597 Tor in 1904, Tor writes a state file with that timestamp in it,
10598 the user fixes her clock, and Tor refuses to start.
10599 - Fix configure.in to not produce broken configure files with
10600 more recent versions of autoconf. Thanks to Clint for his auto*
10602 - "tor --verify-config" now exits with -1(255) or 0 depending on
10603 whether the config options are bad or good.
10604 - Resolve bug 321 when using dnsworkers: append a period to every
10605 address we resolve at the exit node, so that we do not accidentally
10606 pick up local addresses, and so that failing searches are retried
10607 in the resolver search domains. (This is already solved for
10608 eventdns.) (This breaks Blossom servers for now.)
10609 - If we are using an exit enclave and we can't connect, e.g. because
10610 its webserver is misconfigured to not listen on localhost, then
10611 back off and try connecting from somewhere else before we fail.
10614 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
10615 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
10616 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
10617 when the IP address is mapped through MapAddress to a hostname.
10618 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
10619 useless IPv6 DNS resolves.
10620 - Patch suggested by Karsten Loesing: respond to SIGNAL command
10621 before we execute the signal, in case the signal shuts us down.
10622 - Clean up AllowInvalidNodes man page entry.
10623 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
10624 - Add more asserts to track down an assert error on a windows Tor
10625 server with connection_add being called with socket == -1.
10626 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
10627 - Fix misleading log messages: an entry guard that is "unlisted",
10628 as well as not known to be "down" (because we've never heard
10629 of it), is not therefore "up".
10630 - Remove code to special-case "-cvs" ending, since it has not
10631 actually mattered since 0.0.9.
10632 - Make our socks5 handling more robust to broken socks clients:
10633 throw out everything waiting on the buffer in between socks
10634 handshake phases, since they can't possibly (so the theory
10635 goes) have predicted what we plan to respond to them.
10638 Changes in version 0.1.1.23 - 2006-07-30
10640 - Fast Tor servers, especially exit nodes, were triggering asserts
10641 due to a bug in handling the list of pending DNS resolves. Some
10642 bugs still remain here; we're hunting them.
10643 - Entry guards could crash clients by sending unexpected input.
10644 - More fixes on reachability testing: if you find yourself reachable,
10645 then don't ever make any client requests (so you stop predicting
10646 circuits), then hup or have your clock jump, then later your IP
10647 changes, you won't think circuits are working, so you won't try to
10648 test reachability, so you won't publish.
10651 - Avoid a crash if the controller does a resetconf firewallports
10652 and then a setconf fascistfirewall=1.
10653 - Avoid an integer underflow when the dir authority decides whether
10654 a router is stable: we might wrongly label it stable, and compute
10655 a slightly wrong median stability, when a descriptor is published
10657 - Fix a place where we might trigger an assert if we can't build our
10658 own server descriptor yet.
10661 Changes in version 0.1.1.22 - 2006-07-05
10663 - Fix a big bug that was causing servers to not find themselves
10664 reachable if they changed IP addresses. Since only 0.1.1.22+
10665 servers can do reachability testing correctly, now we automatically
10666 make sure to test via one of these.
10667 - Fix to allow clients and mirrors to learn directory info from
10668 descriptor downloads that get cut off partway through.
10669 - Directory authorities had a bug in deciding if a newly published
10670 descriptor was novel enough to make everybody want a copy -- a few
10671 servers seem to be publishing new descriptors many times a minute.
10673 - Fix a rare bug that was causing some servers to complain about
10674 "closing wedged cpuworkers" and skip some circuit create requests.
10675 - Make the Exit flag in directory status documents actually work.
10678 Changes in version 0.1.1.21 - 2006-06-10
10679 o Crash and assert fixes from 0.1.1.20:
10680 - Fix a rare crash on Tor servers that have enabled hibernation.
10681 - Fix a seg fault on startup for Tor networks that use only one
10682 directory authority.
10683 - Fix an assert from a race condition that occurs on Tor servers
10684 while exiting, where various threads are trying to log that they're
10685 exiting, and delete the logs, at the same time.
10686 - Make our unit tests pass again on certain obscure platforms.
10689 - Add support for building SUSE RPM packages.
10690 - Speed up initial bootstrapping for clients: if we are making our
10691 first ever connection to any entry guard, then don't mark it down
10693 - When only one Tor server in the network is labelled as a guard,
10694 and we've already picked him, we would cycle endlessly picking him
10695 again, being unhappy about it, etc. Now we specifically exclude
10696 current guards when picking a new guard.
10697 - Servers send create cells more reliably after the TLS connection
10698 is established: we were sometimes forgetting to send half of them
10699 when we had more than one pending.
10700 - If we get a create cell that asks us to extend somewhere, but the
10701 Tor server there doesn't match the expected digest, we now send
10702 a destroy cell back, rather than silently doing nothing.
10703 - Make options->RedirectExit work again.
10704 - Make cookie authentication for the controller work again.
10705 - Stop being picky about unusual characters in the arguments to
10706 mapaddress. It's none of our business.
10707 - Add a new config option "TestVia" that lets you specify preferred
10708 middle hops to use for test circuits. Perhaps this will let me
10709 debug the reachability problems better.
10711 o Log / documentation fixes:
10712 - If we're a server and some peer has a broken TLS certificate, don't
10713 log about it unless ProtocolWarnings is set, i.e., we want to hear
10714 about protocol violations by others.
10715 - Fix spelling of VirtualAddrNetwork in man page.
10716 - Add a better explanation at the top of the autogenerated torrc file
10717 about what happened to our old torrc.
10720 Changes in version 0.1.1.20 - 2006-05-23
10722 - Downgrade a log severity where servers complain that they're
10724 - Avoid a compile warning on FreeBSD.
10725 - Remove string size limit on NEWDESC messages; solve bug 291.
10726 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
10727 more thoroughly when we're running on windows.
10730 Changes in version 0.1.1.19-rc - 2006-05-03
10732 - Regenerate our local descriptor if it's dirty and we try to use
10733 it locally (e.g. if it changes during reachability detection).
10734 - If we setconf our ORPort to 0, we continued to listen on the
10735 old ORPort and receive connections.
10736 - Avoid a second warning about machine/limits.h on Debian
10738 - Be willing to add our own routerinfo into the routerlist.
10739 Now authorities will include themselves in their directories
10740 and network-statuses.
10741 - Stop trying to upload rendezvous descriptors to every
10742 directory authority: only try the v1 authorities.
10743 - Servers no longer complain when they think they're not
10744 registered with the directory authorities. There were too many
10746 - Backport dist-rpm changes so rpms can be built without errors.
10749 - Implement an option, VirtualAddrMask, to set which addresses
10750 get handed out in response to mapaddress requests. This works
10751 around a bug in tsocks where 127.0.0.0/8 is never socksified.
10754 Changes in version 0.1.1.18-rc - 2006-04-10
10756 - Work harder to download live network-statuses from all the
10757 directory authorities we know about. Improve the threshold
10758 decision logic so we're more robust to edge cases.
10759 - When fetching rendezvous descriptors, we were willing to ask
10760 v2 authorities too, which would always return 404.
10763 - Stop listing down or invalid nodes in the v1 directory. This will
10764 reduce its bulk by about 1/3, and reduce load on directory
10766 - When deciding whether a router is Fast or Guard-worthy, consider
10767 his advertised BandwidthRate and not just the BandwidthCapacity.
10768 - No longer ship INSTALL and README files -- they are useless now.
10769 - Force rpmbuild to behave and honor target_cpu.
10770 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
10771 - Start to include translated versions of the tor-doc-*.html
10772 files, along with the screenshots. Still needs more work.
10773 - Start sending back 512 and 451 errors if mapaddress fails,
10774 rather than not sending anything back at all.
10775 - When we fail to bind or listen on an incoming or outgoing
10776 socket, we should close it before failing. otherwise we just
10777 leak it. (thanks to weasel for finding.)
10778 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
10779 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
10780 - Make NoPublish (even though deprecated) work again.
10781 - Fix a minor security flaw where a versioning auth dirserver
10782 could list a recommended version many times in a row to make
10783 clients more convinced that it's recommended.
10784 - Fix crash bug if there are two unregistered servers running
10785 with the same nickname, one of them is down, and you ask for
10786 them by nickname in your EntryNodes or ExitNodes. Also, try
10787 to pick the one that's running rather than an arbitrary one.
10788 - Fix an infinite loop we could hit if we go offline for too long.
10789 - Complain when we hit WSAENOBUFS on recv() or write() too.
10790 Perhaps this will help us hunt the bug.
10791 - If you're not a versioning dirserver, don't put the string
10792 "client-versions \nserver-versions \n" in your network-status.
10793 - Lower the minimum required number of file descriptors to 1000,
10794 so we can have some overhead for Valgrind on Linux, where the
10795 default ulimit -n is 1024.
10798 - Add tor.dizum.com as the fifth authoritative directory server.
10799 - Add a new config option FetchUselessDescriptors, off by default,
10800 for when you plan to run "exitlist" on your client and you want
10801 to know about even the non-running descriptors.
10804 Changes in version 0.1.1.17-rc - 2006-03-28
10806 - Clients and servers since 0.1.1.10-alpha have been expiring
10807 connections whenever they are idle for 5 minutes and they *do*
10808 have circuits on them. Oops. With this new version, clients will
10809 discard their previous entry guard choices and avoid choosing
10810 entry guards running these flawed versions.
10811 - Fix memory leak when uncompressing concatenated zlib streams. This
10812 was causing substantial leaks over time on Tor servers.
10813 - The v1 directory was including servers as much as 48 hours old,
10814 because that's how the new routerlist->routers works. Now only
10815 include them if they're 20 hours old or less.
10818 - Resume building on irix64, netbsd 2.0, etc.
10819 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
10821 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
10822 and it is confusing some users.
10823 - Mirrors stop caching the v1 directory so often.
10824 - Make the max number of old descriptors that a cache will hold
10825 rise with the number of directory authorities, so we can scale.
10826 - Change our win32 uname() hack to be more forgiving about what
10827 win32 versions it thinks it's found.
10830 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
10832 - When the controller's *setconf commands fail, collect an error
10833 message in a string and hand it back to the controller.
10834 - Make the v2 dir's "Fast" flag based on relative capacity, just
10835 like "Stable" is based on median uptime. Name everything in the
10836 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
10837 - Log server fingerprint on startup, so new server operators don't
10838 have to go hunting around their filesystem for it.
10839 - Return a robots.txt on our dirport to discourage google indexing.
10840 - Let the controller ask for GETINFO dir/status/foo so it can ask
10841 directly rather than connecting to the dir port. Only works when
10842 dirport is set for now.
10844 o New config options rather than constants in the code:
10845 - SocksTimeout: How long do we let a socks connection wait
10846 unattached before we fail it?
10847 - CircuitBuildTimeout: Cull non-open circuits that were born
10848 at least this many seconds ago.
10849 - CircuitIdleTimeout: Cull open clean circuits that were born
10850 at least this many seconds ago.
10853 Changes in version 0.1.1.16-rc - 2006-03-18
10854 o Bugfixes on 0.1.1.15-rc:
10855 - Fix assert when the controller asks to attachstream a connect-wait
10856 or resolve-wait stream.
10857 - Now do address rewriting when the controller asks us to attach
10858 to a particular circuit too. This will let Blossom specify
10859 "moria2.exit" without having to learn what moria2's IP address is.
10860 - Make the "tor --verify-config" command-line work again, so people
10861 can automatically check if their torrc will parse.
10862 - Authoritative dirservers no longer require an open connection from
10863 a server to consider him "reachable". We need this change because
10864 when we add new auth dirservers, old servers won't know not to
10866 - Let Tor build on Sun CC again.
10867 - Fix an off-by-one buffer size in dirserv.c that magically never
10868 hit our three authorities but broke sjmurdoch's own tor network.
10869 - If we as a directory mirror don't know of any v1 directory
10870 authorities, then don't try to cache any v1 directories.
10871 - Stop warning about unknown servers in our family when they are
10872 given as hex digests.
10873 - Stop complaining as quickly to the server operator that he
10874 hasn't registered his nickname/key binding.
10875 - Various cleanups so we can add new V2 Auth Dirservers.
10876 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
10877 reflect the updated flags in our v2 dir protocol.
10878 - Resume allowing non-printable characters for exit streams (both
10879 for connecting and for resolving). Now we tolerate applications
10880 that don't follow the RFCs. But continue to block malformed names
10883 o Bugfixes on 0.1.0.x:
10884 - Fix assert bug in close_logs(): when we close and delete logs,
10885 remove them all from the global "logfiles" list.
10886 - Fix minor integer overflow in calculating when we expect to use up
10887 our bandwidth allocation before hibernating.
10888 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
10889 there are multiple SSLs installed with different versions.
10890 - When we try to be a server and Address is not explicitly set and
10891 our hostname resolves to a private IP address, try to use an
10892 interface address if it has a public address. Now Windows machines
10893 that think of themselves as localhost can work by default.
10896 - Let the controller ask for GETINFO dir/server/foo so it can ask
10897 directly rather than connecting to the dir port.
10898 - Let the controller tell us about certain router descriptors
10899 that it doesn't want Tor to use in circuits. Implement
10900 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
10901 - New config option SafeSocks to reject all application connections
10902 using unsafe socks protocols. Defaults to off.
10905 Changes in version 0.1.1.15-rc - 2006-03-11
10906 o Bugfixes and cleanups:
10907 - When we're printing strings from the network, don't try to print
10908 non-printable characters. This protects us against shell escape
10909 sequence exploits, and also against attacks to fool humans into
10910 misreading their logs.
10911 - Fix a bug where Tor would fail to establish any connections if you
10912 left it off for 24 hours and then started it: we were happy with
10913 the obsolete network statuses, but they all referred to router
10914 descriptors that were too old to fetch, so we ended up with no
10915 valid router descriptors.
10916 - Fix a seg fault in the controller's "getinfo orconn-status"
10917 command while listing status on incoming handshaking connections.
10918 Introduce a status name "NEW" for these connections.
10919 - If we get a linelist or linelist_s config option from the torrc
10920 (e.g. ExitPolicy) and it has no value, warn and skip rather than
10921 silently resetting it to its default.
10922 - Don't abandon entry guards until they've been down or gone for
10924 - Cleaner and quieter log messages.
10927 - New controller signal NEWNYM that makes new application requests
10928 use clean circuits.
10929 - Add a new circuit purpose 'controller' to let the controller ask
10930 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
10931 controller command to let you specify the purpose if you're
10932 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
10933 command to let you change a circuit's purpose after it's been
10935 - Accept "private:*" in routerdesc exit policies; not generated yet
10936 because older Tors do not understand it.
10937 - Add BSD-style contributed startup script "rc.subr" from Peter
10941 Changes in version 0.1.1.14-alpha - 2006-02-20
10942 o Bugfixes on 0.1.1.x:
10943 - Don't die if we ask for a stdout or stderr log (even implicitly)
10944 and we're set to RunAsDaemon -- just warn.
10945 - We still had a few bugs in the OR connection rotation code that
10946 caused directory servers to slowly aggregate connections to other
10947 fast Tor servers. This time for sure!
10948 - Make log entries on Win32 include the name of the function again.
10949 - We were treating a pair of exit policies if they were equal even
10950 if one said accept and the other said reject -- causing us to
10951 not always publish a new descriptor since we thought nothing
10953 - Retry pending server downloads as well as pending networkstatus
10954 downloads when we unexpectedly get a socks request.
10955 - We were ignoring the IS_FAST flag in the directory status,
10956 meaning we were willing to pick trivial-bandwidth nodes for "fast"
10958 - If the controller's SAVECONF command fails (e.g. due to file
10959 permissions), let the controller know that it failed.
10962 - If we're trying to be a Tor server and running Windows 95/98/ME
10963 as a server, explain that we'll likely crash.
10964 - When we're a server, a client asks for an old-style directory,
10965 and our write bucket is empty, don't give it to him. This way
10966 small servers can continue to serve the directory *sometimes*,
10967 without getting overloaded.
10968 - Compress exit policies even more -- look for duplicate lines
10970 - Clients now honor the "guard" flag in the router status when
10971 picking entry guards, rather than looking at is_fast or is_stable.
10972 - Retain unrecognized lines in $DATADIR/state file, so that we can
10973 be forward-compatible.
10974 - Generate 18.0.0.0/8 address policy format in descs when we can;
10975 warn when the mask is not reducible to a bit-prefix.
10976 - Let the user set ControlListenAddress in the torrc. This can be
10977 dangerous, but there are some cases (like a secured LAN) where it
10979 - Split ReachableAddresses into ReachableDirAddresses and
10980 ReachableORAddresses, so we can restrict Dir conns to port 80
10981 and OR conns to port 443.
10982 - Now we can target arch and OS in rpm builds (contributed by
10983 Phobos). Also make the resulting dist-rpm filename match the
10985 - New config options to help controllers: FetchServerDescriptors
10986 and FetchHidServDescriptors for whether to fetch server
10987 info and hidserv info or let the controller do it, and
10988 PublishServerDescriptor and PublishHidServDescriptors.
10989 - Also let the controller set the __AllDirActionsPrivate config
10990 option if you want all directory fetches/publishes to happen via
10991 Tor (it assumes your controller bootstraps your circuits).
10994 Changes in version 0.1.0.17 - 2006-02-17
10995 o Crash bugfixes on 0.1.0.x:
10996 - When servers with a non-zero DirPort came out of hibernation,
10997 sometimes they would trigger an assert.
10999 o Other important bugfixes:
11000 - On platforms that don't have getrlimit (like Windows), we were
11001 artificially constraining ourselves to a max of 1024
11002 connections. Now just assume that we can handle as many as 15000
11003 connections. Hopefully this won't cause other problems.
11005 o Backported features:
11006 - When we're a server, a client asks for an old-style directory,
11007 and our write bucket is empty, don't give it to him. This way
11008 small servers can continue to serve the directory *sometimes*,
11009 without getting overloaded.
11010 - Whenever you get a 503 in response to a directory fetch, try
11011 once more. This will become important once servers start sending
11012 503's whenever they feel busy.
11013 - Fetch a new directory every 120 minutes, not every 40 minutes.
11014 Now that we have hundreds of thousands of users running the old
11015 directory algorithm, it's starting to hurt a lot.
11016 - Bump up the period for forcing a hidden service descriptor upload
11017 from 20 minutes to 1 hour.
11020 Changes in version 0.1.1.13-alpha - 2006-02-09
11021 o Crashes in 0.1.1.x:
11022 - When you tried to setconf ORPort via the controller, Tor would
11023 crash. So people using TorCP to become a server were sad.
11024 - Solve (I hope) the stack-smashing bug that we were seeing on fast
11025 servers. The problem appears to be something do with OpenSSL's
11026 random number generation, or how we call it, or something. Let me
11027 know if the crashes continue.
11028 - Turn crypto hardware acceleration off by default, until we find
11029 somebody smart who can test it for us. (It appears to produce
11030 seg faults in at least some cases.)
11031 - Fix a rare assert error when we've tried all intro points for
11032 a hidden service and we try fetching the service descriptor again:
11033 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
11036 - Fix a major load balance bug: we were round-robining in 16 KB
11037 chunks, and servers with bandwidthrate of 20 KB, while downloading
11038 a 600 KB directory, would starve their other connections. Now we
11039 try to be a bit more fair.
11040 - Dir authorities and mirrors were never expiring the newest
11041 descriptor for each server, causing memory and directory bloat.
11042 - Fix memory-bloating and connection-bloating bug on servers: We
11043 were never closing any connection that had ever had a circuit on
11044 it, because we were checking conn->n_circuits == 0, yet we had a
11045 bug that let it go negative.
11046 - Make Tor work using squid as your http proxy again -- squid
11047 returns an error if you ask for a URL that's too long, and it uses
11048 a really generic error message. Plus, many people are behind a
11049 transparent squid so they don't even realize it.
11050 - On platforms that don't have getrlimit (like Windows), we were
11051 artificially constraining ourselves to a max of 1024
11052 connections. Now just assume that we can handle as many as 15000
11053 connections. Hopefully this won't cause other problems.
11054 - Add a new config option ExitPolicyRejectPrivate which defaults to
11055 1. This means all exit policies will begin with rejecting private
11056 addresses, unless the server operator explicitly turns it off.
11059 - Clients no longer download descriptors for non-running
11061 - Before we add new directory authorities, we should make it
11062 clear that only v1 authorities should receive/publish hidden
11063 service descriptors.
11066 - As soon as we've fetched some more directory info, immediately
11067 try to download more server descriptors. This way we don't have
11068 a 10 second pause during initial bootstrapping.
11069 - Remove even more loud log messages that the server operator can't
11071 - When we're running an obsolete or un-recommended version, make
11072 the log message more clear about what the problem is and what
11073 versions *are* still recommended.
11074 - Provide a more useful warn message when our onion queue gets full:
11075 the CPU is too slow or the exit policy is too liberal.
11076 - Don't warn when we receive a 503 from a dirserver/cache -- this
11077 will pave the way for them being able to refuse if they're busy.
11078 - When we fail to bind a listener, try to provide a more useful
11079 log message: e.g., "Is Tor already running?"
11080 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
11081 Goldberg can prove things about our handshake protocol more
11083 - MaxConn has been obsolete for a while now. Document the ConnLimit
11084 config option, which is a *minimum* number of file descriptors
11085 that must be available else Tor refuses to start.
11086 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
11087 if you log to syslog and want something other than LOG_DAEMON.
11088 - Make dirservers generate a separate "guard" flag to mean,
11089 "would make a good entry guard". Make clients parse it and vote
11090 on it. Not used by clients yet.
11091 - Implement --with-libevent-dir option to ./configure. Also, improve
11092 search techniques to find libevent, and use those for openssl too.
11093 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
11094 - Only start testing reachability once we've established a
11095 circuit. This will make startup on dirservers less noisy.
11096 - Don't try to upload hidden service descriptors until we have
11097 established a circuit.
11098 - Fix the controller's "attachstream 0" command to treat conn like
11099 it just connected, doing address remapping, handling .exit and
11100 .onion idioms, and so on. Now we're more uniform in making sure
11101 that the controller hears about new and closing connections.
11104 Changes in version 0.1.1.12-alpha - 2006-01-11
11105 o Bugfixes on 0.1.1.x:
11106 - The fix to close duplicate server connections was closing all
11107 Tor client connections if they didn't establish a circuit
11108 quickly enough. Oops.
11109 - Fix minor memory issue (double-free) that happened on exit.
11111 o Bugfixes on 0.1.0.x:
11112 - Tor didn't warn when it failed to open a log file.
11115 Changes in version 0.1.1.11-alpha - 2006-01-10
11116 o Crashes in 0.1.1.x:
11117 - Include all the assert/crash fixes from 0.1.0.16.
11118 - If you start Tor and then quit very quickly, there were some
11119 races that tried to free things that weren't allocated yet.
11120 - Fix a rare memory stomp if you're running hidden services.
11121 - Fix segfault when specifying DirServer in config without nickname.
11122 - Fix a seg fault when you finish connecting to a server but at
11123 that moment you dump his server descriptor.
11124 - Extendcircuit and Attachstream controller commands would
11125 assert/crash if you don't give them enough arguments.
11126 - Fix an assert error when we're out of space in the connection_list
11127 and we try to post a hidden service descriptor (reported by weasel).
11128 - If you specify a relative torrc path and you set RunAsDaemon in
11129 your torrc, then it chdir()'s to the new directory. If you HUP,
11130 it tries to load the new torrc location, fails, and exits.
11131 The fix: no longer allow a relative path to torrc using -f.
11134 - Implement "entry guards": automatically choose a handful of entry
11135 nodes and stick with them for all circuits. Only pick new guards
11136 when the ones you have are unsuitable, and if the old guards
11137 become suitable again, switch back. This will increase security
11138 dramatically against certain end-point attacks. The EntryNodes
11139 config option now provides some hints about which entry guards you
11140 want to use most; and StrictEntryNodes means to only use those.
11141 - New directory logic: download by descriptor digest, not by
11142 fingerprint. Caches try to download all listed digests from
11143 authorities; clients try to download "best" digests from caches.
11144 This avoids partitioning and isolating attacks better.
11145 - Make the "stable" router flag in network-status be the median of
11146 the uptimes of running valid servers, and make clients pay
11147 attention to the network-status flags. Thus the cutoff adapts
11148 to the stability of the network as a whole, making IRC, IM, etc
11149 connections more reliable.
11152 - Tor servers with dynamic IP addresses were needing to wait 18
11153 hours before they could start doing reachability testing using
11154 the new IP address and ports. This is because they were using
11155 the internal descriptor to learn what to test, yet they were only
11156 rebuilding the descriptor once they decided they were reachable.
11157 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
11158 to download certain server descriptors, throw them away, and then
11159 fetch them again after 30 minutes. Now mirrors throw away these
11160 server descriptors so clients can't get them.
11161 - We were leaving duplicate connections to other ORs open for a week,
11162 rather than closing them once we detect a duplicate. This only
11163 really affected authdirservers, but it affected them a lot.
11164 - Spread the authdirservers' reachability testing over the entire
11165 testing interval, so we don't try to do 500 TLS's at once every
11169 - If the network is down, and we try to connect to a conn because
11170 we have a circuit in mind, and we timeout (30 seconds) because the
11171 network never answers, we were expiring the circuit, but we weren't
11172 obsoleting the connection or telling the entry_guards functions.
11173 - Some Tor servers process billions of cells per day. These statistics
11174 need to be uint64_t's.
11175 - Check for integer overflows in more places, when adding elements
11176 to smartlists. This could possibly prevent a buffer overflow
11177 on malicious huge inputs. I don't see any, but I haven't looked
11179 - ReachableAddresses kept growing new "reject *:*" lines on every
11181 - When you "setconf log" via the controller, it should remove all
11182 logs. We were automatically adding back in a "log notice stdout".
11183 - Newly bootstrapped Tor networks couldn't establish hidden service
11184 circuits until they had nodes with high uptime. Be more tolerant.
11185 - We were marking servers down when they could not answer every piece
11186 of the directory request we sent them. This was far too harsh.
11187 - Fix the torify (tsocks) config file to not use Tor for localhost
11189 - Directory authorities now go to the proper authority when asking for
11190 a networkstatus, even when they want a compressed one.
11191 - Fix a harmless bug that was causing Tor servers to log
11192 "Got an end because of misc error, but we're not an AP. Closing."
11193 - Authorities were treating their own descriptor changes as cosmetic,
11194 meaning the descriptor available in the network-status and the
11195 descriptor that clients downloaded were different.
11196 - The OS X installer was adding a symlink for tor_resolve but
11197 the binary was called tor-resolve (reported by Thomas Hardly).
11198 - Workaround a problem with some http proxies where they refuse GET
11199 requests that specify "Content-Length: 0" (reported by Adrian).
11200 - Fix wrong log message when you add a "HiddenServiceNodes" config
11201 line without any HiddenServiceDir line (reported by Chris Thomas).
11204 - Write the TorVersion into the state file so we have a prayer of
11205 keeping forward and backward compatibility.
11206 - Revive the FascistFirewall config option rather than eliminating it:
11207 now it's a synonym for ReachableAddresses *:80,*:443.
11208 - Clients choose directory servers from the network status lists,
11209 not from their internal list of router descriptors. Now they can
11210 go to caches directly rather than needing to go to authorities
11212 - Directory authorities ignore router descriptors that have only
11213 cosmetic differences: do this for 0.1.0.x servers now too.
11214 - Add a new flag to network-status indicating whether the server
11215 can answer v2 directory requests too.
11216 - Authdirs now stop whining so loudly about bad descriptors that
11217 they fetch from other dirservers. So when there's a log complaint,
11218 it's for sure from a freshly uploaded descriptor.
11219 - Reduce memory requirements in our structs by changing the order
11221 - There used to be two ways to specify your listening ports in a
11222 server descriptor: on the "router" line and with a separate "ports"
11223 line. Remove support for the "ports" line.
11224 - New config option "AuthDirRejectUnlisted" for auth dirservers as
11225 a panic button: if we get flooded with unusable servers we can
11226 revert to only listing servers in the approved-routers file.
11227 - Auth dir servers can now mark a fingerprint as "!reject" or
11228 "!invalid" in the approved-routers file (as its nickname), to
11229 refuse descriptors outright or include them but marked as invalid.
11230 - Servers store bandwidth history across restarts/crashes.
11231 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
11232 get a better idea of why their circuits failed. Not used yet.
11233 - Directory mirrors now cache up to 16 unrecognized network-status
11234 docs. Now we can add new authdirservers and they'll be cached too.
11235 - When picking a random directory, prefer non-authorities if any
11237 - New controller option "getinfo desc/all-recent" to fetch the
11238 latest server descriptor for every router that Tor knows about.
11241 Changes in version 0.1.0.16 - 2006-01-02
11242 o Crash bugfixes on 0.1.0.x:
11243 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
11244 corrupting the heap, losing FDs, or crashing when we need to resize
11245 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
11246 - It turns out sparc64 platforms crash on unaligned memory access
11247 too -- so detect and avoid this.
11248 - Handle truncated compressed data correctly (by detecting it and
11250 - Fix possible-but-unlikely free(NULL) in control.c.
11251 - When we were closing connections, there was a rare case that
11252 stomped on memory, triggering seg faults and asserts.
11253 - Avoid potential infinite recursion when building a descriptor. (We
11254 don't know that it ever happened, but better to fix it anyway.)
11255 - We were neglecting to unlink marked circuits from soon-to-close OR
11256 connections, which caused some rare scribbling on freed memory.
11257 - Fix a memory stomping race bug when closing the joining point of two
11258 rendezvous circuits.
11259 - Fix an assert in time parsing found by Steven Murdoch.
11261 o Other bugfixes on 0.1.0.x:
11262 - When we're doing reachability testing, provide more useful log
11263 messages so the operator knows what to expect.
11264 - Do not check whether DirPort is reachable when we are suppressing
11265 advertising it because of hibernation.
11266 - When building with -static or on Solaris, we sometimes needed -ldl.
11267 - When we're deciding whether a stream has enough circuits around
11268 that can handle it, count the freshly dirty ones and not the ones
11269 that are so dirty they won't be able to handle it.
11270 - When we're expiring old circuits, we had a logic error that caused
11271 us to close new rendezvous circuits rather than old ones.
11272 - Give a more helpful log message when you try to change ORPort via
11273 the controller: you should upgrade Tor if you want that to work.
11274 - We were failing to parse Tor versions that start with "Tor ".
11275 - Tolerate faulty streams better: when a stream fails for reason
11276 exitpolicy, stop assuming that the router is lying about his exit
11277 policy. When a stream fails for reason misc, allow it to retry just
11278 as if it was resolvefailed. When a stream has failed three times,
11279 reset its failure count so we can try again and get all three tries.
11282 Changes in version 0.1.1.10-alpha - 2005-12-11
11283 o Correctness bugfixes on 0.1.0.x:
11284 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
11285 corrupting the heap, losing FDs, or crashing when we need to resize
11286 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
11287 - Stop doing the complex voodoo overkill checking for insecure
11288 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
11289 - When we were closing connections, there was a rare case that
11290 stomped on memory, triggering seg faults and asserts.
11291 - We were neglecting to unlink marked circuits from soon-to-close OR
11292 connections, which caused some rare scribbling on freed memory.
11293 - When we're deciding whether a stream has enough circuits around
11294 that can handle it, count the freshly dirty ones and not the ones
11295 that are so dirty they won't be able to handle it.
11296 - Recover better from TCP connections to Tor servers that are
11297 broken but don't tell you (it happens!); and rotate TLS
11298 connections once a week.
11299 - When we're expiring old circuits, we had a logic error that caused
11300 us to close new rendezvous circuits rather than old ones.
11301 - Fix a scary-looking but apparently harmless bug where circuits
11302 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
11303 servers, and never switch to state CIRCUIT_STATE_OPEN.
11304 - When building with -static or on Solaris, we sometimes needed to
11306 - Give a useful message when people run Tor as the wrong user,
11307 rather than telling them to start chowning random directories.
11308 - We were failing to inform the controller about new .onion streams.
11310 o Security bugfixes on 0.1.0.x:
11311 - Refuse server descriptors if the fingerprint line doesn't match
11312 the included identity key. Tor doesn't care, but other apps (and
11313 humans) might actually be trusting the fingerprint line.
11314 - We used to kill the circuit when we receive a relay command we
11315 don't recognize. Now we just drop it.
11316 - Start obeying our firewall options more rigorously:
11317 . If we can't get to a dirserver directly, try going via Tor.
11318 . Don't ever try to connect (as a client) to a place our
11319 firewall options forbid.
11320 . If we specify a proxy and also firewall options, obey the
11321 firewall options even when we're using the proxy: some proxies
11322 can only proxy to certain destinations.
11323 - Fix a bug found by Lasse Overlier: when we were making internal
11324 circuits (intended to be cannibalized later for rendezvous and
11325 introduction circuits), we were picking them so that they had
11326 useful exit nodes. There was no need for this, and it actually
11327 aids some statistical attacks.
11328 - Start treating internal circuits and exit circuits separately.
11329 It's important to keep them separate because internal circuits
11330 have their last hops picked like middle hops, rather than like
11331 exit hops. So exiting on them will break the user's expectations.
11333 o Bugfixes on 0.1.1.x:
11334 - Take out the mis-feature where we tried to detect IP address
11335 flapping for people with DynDNS, and chose not to upload a new
11336 server descriptor sometimes.
11337 - Try to be compatible with OpenSSL 0.9.6 again.
11338 - Log fix: when the controller is logging about .onion addresses,
11339 sometimes it didn't include the ".onion" part of the address.
11340 - Don't try to modify options->DirServers internally -- if the
11341 user didn't specify any, just add the default ones directly to
11342 the trusted dirserver list. This fixes a bug where people running
11343 controllers would use SETCONF on some totally unrelated config
11344 option, and Tor would start yelling at them about changing their
11346 - Let the controller's redirectstream command specify a port, in
11347 case the controller wants to change that too.
11348 - When we requested a pile of server descriptors, we sometimes
11349 accidentally launched a duplicate request for the first one.
11350 - Bugfix for trackhostexits: write down the fingerprint of the
11351 chosen exit, not its nickname, because the chosen exit might not
11353 - When parsing foo.exit, if foo is unknown, and we are leaving
11354 circuits unattached, set the chosen_exit field and leave the
11355 address empty. This matters because controllers got confused
11357 - Directory authorities no longer try to download server
11358 descriptors that they know they will reject.
11360 o Features and updates:
11361 - Replace balanced trees with hash tables: this should make stuff
11362 significantly faster.
11363 - Resume using the AES counter-mode implementation that we ship,
11364 rather than OpenSSL's. Ours is significantly faster.
11365 - Many other CPU and memory improvements.
11366 - Add a new config option FastFirstHopPK (on by default) so clients
11367 do a trivial crypto handshake for their first hop, since TLS has
11368 already taken care of confidentiality and authentication.
11369 - Add a new config option TestSocks so people can see if their
11370 applications are using socks4, socks4a, socks5-with-ip, or
11371 socks5-with-hostname. This way they don't have to keep mucking
11372 with tcpdump and wondering if something got cached somewhere.
11373 - Warn when listening on a public address for socks. I suspect a
11374 lot of people are setting themselves up as open socks proxies,
11375 and they have no idea that jerks on the Internet are using them,
11376 since they simply proxy the traffic into the Tor network.
11377 - Add "private:*" as an alias in configuration for policies. Now
11378 you can simplify your exit policy rather than needing to list
11379 every single internal or nonroutable network space.
11380 - Add a new controller event type that allows controllers to get
11381 all server descriptors that were uploaded to a router in its role
11382 as authoritative dirserver.
11383 - Start shipping socks-extensions.txt, tor-doc-unix.html,
11384 tor-doc-server.html, and stylesheet.css in the tarball.
11385 - Stop shipping tor-doc.html in the tarball.
11388 Changes in version 0.1.1.9-alpha - 2005-11-15
11389 o Usability improvements:
11390 - Start calling it FooListenAddress rather than FooBindAddress,
11391 since few of our users know what it means to bind an address
11393 - Reduce clutter in server logs. We're going to try to make
11394 them actually usable now. New config option ProtocolWarnings that
11395 lets you hear about how _other Tors_ are breaking the protocol. Off
11397 - Divide log messages into logging domains. Once we put some sort
11398 of interface on this, it will let people looking at more verbose
11399 log levels specify the topics they want to hear more about.
11400 - Make directory servers return better http 404 error messages
11401 instead of a generic "Servers unavailable".
11402 - Check for even more Windows version flags when writing the platform
11403 string in server descriptors, and note any we don't recognize.
11404 - Clean up more of the OpenSSL memory when exiting, so we can detect
11405 memory leaks better.
11406 - Make directory authorities be non-versioning, non-naming by
11407 default. Now we can add new directory servers without requiring
11408 their operators to pay close attention.
11409 - When logging via syslog, include the pid whenever we provide
11410 a log entry. Suggested by Todd Fries.
11412 o Performance improvements:
11413 - Directory servers now silently throw away new descriptors that
11414 haven't changed much if the timestamps are similar. We do this to
11415 tolerate older Tor servers that upload a new descriptor every 15
11416 minutes. (It seemed like a good idea at the time.)
11417 - Inline bottleneck smartlist functions; use fast versions by default.
11418 - Add a "Map from digest to void*" abstraction digestmap_t so we
11419 can do less hex encoding/decoding. Use it in router_get_by_digest()
11420 to resolve a performance bottleneck.
11421 - Allow tor_gzip_uncompress to extract as much as possible from
11422 truncated compressed data. Try to extract as many
11423 descriptors as possible from truncated http responses (when
11424 DIR_PURPOSE_FETCH_ROUTERDESC).
11425 - Make circ->onionskin a pointer, not a static array. moria2 was using
11426 125000 circuit_t's after it had been up for a few weeks, which
11427 translates to 20+ megs of wasted space.
11428 - The private half of our EDH handshake keys are now chosen out
11429 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
11431 o Security improvements:
11432 - Start making directory caches retain old routerinfos, so soon
11433 clients can start asking by digest of descriptor rather than by
11434 fingerprint of server.
11435 - Add half our entropy from RAND_poll in OpenSSL. This knows how
11436 to use egd (if present), openbsd weirdness (if present), vms/os2
11437 weirdness (if we ever port there), and more in the future.
11439 o Bugfixes on 0.1.0.x:
11440 - Do round-robin writes of at most 16 kB per write. This might be
11441 more fair on loaded Tor servers, and it might resolve our Windows
11442 crash bug. It might also slow things down.
11443 - Our TLS handshakes were generating a single public/private
11444 keypair for the TLS context, rather than making a new one for
11445 each new connections. Oops. (But we were still rotating them
11446 periodically, so it's not so bad.)
11447 - When we were cannibalizing a circuit with a particular exit
11448 node in mind, we weren't checking to see if that exit node was
11449 already present earlier in the circuit. Oops.
11450 - When a Tor server's IP changes (e.g. from a dyndns address),
11451 upload a new descriptor so clients will learn too.
11452 - Really busy servers were keeping enough circuits open on stable
11453 connections that they were wrapping around the circuit_id
11454 space. (It's only two bytes.) This exposed a bug where we would
11455 feel free to reuse a circuit_id even if it still exists but has
11456 been marked for close. Try to fix this bug. Some bug remains.
11457 - If we would close a stream early (e.g. it asks for a .exit that
11458 we know would refuse it) but the LeaveStreamsUnattached config
11459 option is set by the controller, then don't close it.
11461 o Bugfixes on 0.1.1.8-alpha:
11462 - Fix a big pile of memory leaks, some of them serious.
11463 - Do not try to download a routerdesc if we would immediately reject
11465 - Resume inserting a newline between all router descriptors when
11466 generating (old style) signed directories, since our spec says
11468 - When providing content-type application/octet-stream for
11469 server descriptors using .z, we were leaving out the
11470 content-encoding header. Oops. (Everything tolerated this just
11471 fine, but that doesn't mean we need to be part of the problem.)
11472 - Fix a potential seg fault in getconf and getinfo using version 1
11473 of the controller protocol.
11474 - Avoid crash: do not check whether DirPort is reachable when we
11475 are suppressing it because of hibernation.
11476 - Make --hash-password not crash on exit.
11479 Changes in version 0.1.1.8-alpha - 2005-10-07
11480 o New features (major):
11481 - Clients don't download or use the directory anymore. Now they
11482 download and use network-statuses from the trusted dirservers,
11483 and fetch individual server descriptors as needed from mirrors.
11484 See dir-spec.txt for all the gory details.
11485 - Be more conservative about whether to advertise our DirPort.
11486 The main change is to not advertise if we're running at capacity
11487 and either a) we could hibernate or b) our capacity is low and
11488 we're using a default DirPort.
11489 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
11491 o New features (minor):
11492 - Try to be smart about when to retry network-status and
11493 server-descriptor fetches. Still needs some tuning.
11494 - Stop parsing, storing, or using running-routers output (but
11495 mirrors still cache and serve it).
11496 - Consider a threshold of versioning dirservers (dirservers who have
11497 an opinion about which Tor versions are still recommended) before
11498 deciding whether to warn the user that he's obsolete.
11499 - Dirservers can now reject/invalidate by key and IP, with the
11500 config options "AuthDirInvalid" and "AuthDirReject". This is
11501 useful since currently we automatically list servers as running
11502 and usable even if we know they're jerks.
11503 - Provide dire warnings to any users who set DirServer; move it out
11504 of torrc.sample and into torrc.complete.
11505 - Add MyFamily to torrc.sample in the server section.
11506 - Add nicknames to the DirServer line, so we can refer to them
11507 without requiring all our users to memorize their IP addresses.
11508 - When we get an EOF or a timeout on a directory connection, note
11509 how many bytes of serverdesc we are dropping. This will help
11510 us determine whether it is smart to parse incomplete serverdesc
11512 - Add a new function to "change pseudonyms" -- that is, to stop
11513 using any currently-dirty circuits for new streams, so we don't
11514 link new actions to old actions. Currently it's only called on
11515 HUP (or SIGNAL RELOAD).
11516 - On sighup, if UseHelperNodes changed to 1, use new circuits.
11517 - Start using RAND_bytes rather than RAND_pseudo_bytes from
11518 OpenSSL. Also, reseed our entropy every hour, not just at
11519 startup. And entropy in 512-bit chunks, not 160-bit chunks.
11521 o Fixes on 0.1.1.7-alpha:
11522 - Nobody ever implemented EVENT_ADDRMAP for control protocol
11523 version 0, so don't let version 0 controllers ask for it.
11524 - If you requested something with too many newlines via the
11525 v1 controller protocol, you could crash tor.
11526 - Fix a number of memory leaks, including some pretty serious ones.
11527 - Re-enable DirPort testing again, so Tor servers will be willing
11528 to advertise their DirPort if it's reachable.
11529 - On TLS handshake, only check the other router's nickname against
11530 its expected nickname if is_named is set.
11532 o Fixes forward-ported from 0.1.0.15:
11533 - Don't crash when we don't have any spare file descriptors and we
11534 try to spawn a dns or cpu worker.
11535 - Make the numbers in read-history and write-history into uint64s,
11536 so they don't overflow and publish negatives in the descriptor.
11538 o Fixes on 0.1.0.x:
11539 - For the OS X package's modified privoxy config file, comment
11540 out the "logfile" line so we don't log everything passed
11542 - We were whining about using socks4 or socks5-with-local-lookup
11543 even when it's an IP in the "virtual" range we designed exactly
11545 - We were leaking some memory every time the client changes IPs.
11546 - Never call free() on tor_malloc()d memory. This will help us
11547 use dmalloc to detect memory leaks.
11548 - Check for named servers when looking them up by nickname;
11549 warn when we'recalling a non-named server by its nickname;
11550 don't warn twice about the same name.
11551 - Try to list MyFamily elements by key, not by nickname, and warn
11552 if we've not heard of the server.
11553 - Make windows platform detection (uname equivalent) smarter.
11554 - It turns out sparc64 doesn't like unaligned access either.
11557 Changes in version 0.1.0.15 - 2005-09-23
11558 o Bugfixes on 0.1.0.x:
11559 - Reject ports 465 and 587 (spam targets) in default exit policy.
11560 - Don't crash when we don't have any spare file descriptors and we
11561 try to spawn a dns or cpu worker.
11562 - Get rid of IgnoreVersion undocumented config option, and make us
11563 only warn, never exit, when we're running an obsolete version.
11564 - Don't try to print a null string when your server finds itself to
11565 be unreachable and the Address config option is empty.
11566 - Make the numbers in read-history and write-history into uint64s,
11567 so they don't overflow and publish negatives in the descriptor.
11568 - Fix a minor memory leak in smartlist_string_remove().
11569 - We were only allowing ourselves to upload a server descriptor at
11570 most every 20 minutes, even if it changed earlier than that.
11571 - Clean up log entries that pointed to old URLs.
11574 Changes in version 0.1.1.7-alpha - 2005-09-14
11575 o Fixes on 0.1.1.6-alpha:
11576 - Exit servers were crashing when people asked them to make a
11577 connection to an address not in their exit policy.
11578 - Looking up a non-existent stream for a v1 control connection would
11580 - Fix a seg fault if we ask a dirserver for a descriptor by
11581 fingerprint but he doesn't know about him.
11582 - SETCONF was appending items to linelists, not clearing them.
11583 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
11584 out and refuse the setconf if it would fail.
11585 - Downgrade the dirserver log messages when whining about
11589 - Add Peter Palfrader's check-tor script to tor/contrib/
11590 It lets you easily check whether a given server (referenced by
11591 nickname) is reachable by you.
11592 - Numerous changes to move towards client-side v2 directories. Not
11595 o Fixes on 0.1.0.x:
11596 - If the user gave tor an odd number of command-line arguments,
11597 we were silently ignoring the last one. Now we complain and fail.
11598 [This wins the oldest-bug prize -- this bug has been present since
11599 November 2002, as released in Tor 0.0.0.]
11600 - Do not use unaligned memory access on alpha, mips, or mipsel.
11601 It *works*, but is very slow, so we treat them as if it doesn't.
11602 - Retry directory requests if we fail to get an answer we like
11603 from a given dirserver (we were retrying before, but only if
11604 we fail to connect).
11605 - When writing the RecommendedVersions line, sort them first.
11606 - When the client asked for a rendezvous port that the hidden
11607 service didn't want to provide, we were sending an IP address
11608 back along with the end cell. Fortunately, it was zero. But stop
11610 - Correct "your server is reachable" log entries to indicate that
11611 it was self-testing that told us so.
11614 Changes in version 0.1.1.6-alpha - 2005-09-09
11615 o Fixes on 0.1.1.5-alpha:
11616 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
11617 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
11618 - Fix bug with tor_memmem finding a match at the end of the string.
11619 - Make unit tests run without segfaulting.
11620 - Resolve some solaris x86 compile warnings.
11621 - Handle duplicate lines in approved-routers files without warning.
11622 - Fix bug where as soon as a server refused any requests due to his
11623 exit policy (e.g. when we ask for localhost and he tells us that's
11624 127.0.0.1 and he won't do it), we decided he wasn't obeying his
11625 exit policy using him for any exits.
11626 - Only do openssl hardware accelerator stuff if openssl version is
11629 o New controller features/fixes:
11630 - Add a "RESETCONF" command so you can set config options like
11631 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
11632 a config option in the torrc with no value, then it clears it
11633 entirely (rather than setting it to its default).
11634 - Add a "GETINFO config-file" to tell us where torrc is.
11635 - Avoid sending blank lines when GETINFO replies should be empty.
11636 - Add a QUIT command for the controller (for using it manually).
11637 - Fix a bug in SAVECONF that was adding default dirservers and
11638 other redundant entries to the torrc file.
11640 o Start on the new directory design:
11641 - Generate, publish, cache, serve new network-status format.
11642 - Publish individual descriptors (by fingerprint, by "all", and by
11644 - Publish client and server recommended versions separately.
11645 - Allow tor_gzip_uncompress() to handle multiple concatenated
11646 compressed strings. Serve compressed groups of router
11647 descriptors. The compression logic here could be more
11649 - Distinguish v1 authorities (all currently trusted directories)
11650 from v2 authorities (all trusted directories).
11651 - Change DirServers config line to note which dirs are v1 authorities.
11652 - Add configuration option "V1AuthoritativeDirectory 1" which
11653 moria1, moria2, and tor26 should set.
11654 - Remove option when getting directory cache to see whether they
11655 support running-routers; they all do now. Replace it with one
11656 to see whether caches support v2 stuff.
11659 - Dirservers now do their own external reachability testing of each
11660 Tor server, and only list them as running if they've been found to
11661 be reachable. We also send back warnings to the server's logs if
11662 it uploads a descriptor that we already believe is unreachable.
11663 - Implement exit enclaves: if we know an IP address for the
11664 destination, and there's a running Tor server at that address
11665 which allows exit to the destination, then extend the circuit to
11666 that exit first. This provides end-to-end encryption and end-to-end
11667 authentication. Also, if the user wants a .exit address or enclave,
11668 use 4 hops rather than 3, and cannibalize a general circ for it
11670 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
11671 controller. Also, rotate dns and cpu workers if the controller
11672 changes options that will affect them; and initialize the dns
11673 worker cache tree whether or not we start out as a server.
11674 - Only upload a new server descriptor when options change, 18
11675 hours have passed, uptime is reset, or bandwidth changes a lot.
11676 - Check [X-]Forwarded-For headers in HTTP requests when generating
11677 log messages. This lets people run dirservers (and caches) behind
11678 Apache but still know which IP addresses are causing warnings.
11680 o Config option changes:
11681 - Replace (Fascist)Firewall* config options with a new
11682 ReachableAddresses option that understands address policies.
11683 For example, "ReachableAddresses *:80,*:443"
11684 - Get rid of IgnoreVersion undocumented config option, and make us
11685 only warn, never exit, when we're running an obsolete version.
11686 - Make MonthlyAccountingStart config option truly obsolete now.
11688 o Fixes on 0.1.0.x:
11689 - Reject ports 465 and 587 in the default exit policy, since
11690 people have started using them for spam too.
11691 - It turns out we couldn't bootstrap a network since we added
11692 reachability detection in 0.1.0.1-rc. Good thing the Tor network
11693 has never gone down. Add an AssumeReachable config option to let
11694 servers and dirservers bootstrap. When we're trying to build a
11695 high-uptime or high-bandwidth circuit but there aren't enough
11696 suitable servers, try being less picky rather than simply failing.
11697 - Our logic to decide if the OR we connected to was the right guy
11698 was brittle and maybe open to a mitm for unverified routers.
11699 - We weren't cannibalizing circuits correctly for
11700 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
11701 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
11702 build those from scratch. This should make hidden services faster.
11703 - Predict required circuits better, with an eye toward making hidden
11704 services faster on the service end.
11705 - Retry streams if the exit node sends back a 'misc' failure. This
11706 should result in fewer random failures. Also, after failing
11707 from resolve failed or misc, reset the num failures, so we give
11708 it a fair shake next time we try.
11709 - Clean up the rendezvous warn log msgs, and downgrade some to info.
11710 - Reduce severity on logs about dns worker spawning and culling.
11711 - When we're shutting down and we do something like try to post a
11712 server descriptor or rendezvous descriptor, don't complain that
11713 we seem to be unreachable. Of course we are, we're shutting down.
11714 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
11715 We don't use them yet, but maybe one day our DNS resolver will be
11716 able to discover them.
11717 - Make ContactInfo mandatory for authoritative directory servers.
11718 - Require server descriptors to list IPv4 addresses -- hostnames
11719 are no longer allowed. This also fixes some potential security
11720 problems with people providing hostnames as their address and then
11721 preferentially resolving them to partition users.
11722 - Change log line for unreachability to explicitly suggest /etc/hosts
11723 as the culprit. Also make it clearer what IP address and ports we're
11724 testing for reachability.
11725 - Put quotes around user-supplied strings when logging so users are
11726 more likely to realize if they add bad characters (like quotes)
11728 - Let auth dir servers start without specifying an Address config
11730 - Make unit tests (and other invocations that aren't the real Tor)
11731 run without launching listeners, creating subdirectories, and so on.
11734 Changes in version 0.1.1.5-alpha - 2005-08-08
11735 o Bugfixes included in 0.1.0.14.
11737 o Bugfixes on 0.1.0.x:
11738 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
11739 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
11740 it would silently using ignore the 6668.
11743 Changes in version 0.1.0.14 - 2005-08-08
11744 o Bugfixes on 0.1.0.x:
11745 - Fix the other half of the bug with crypto handshakes
11747 - Fix an assert trigger if you send a 'signal term' via the
11748 controller when it's listening for 'event info' messages.
11751 Changes in version 0.1.1.4-alpha - 2005-08-04
11752 o Bugfixes included in 0.1.0.13.
11755 - Improve tor_gettimeofday() granularity on windows.
11756 - Make clients regenerate their keys when their IP address changes.
11757 - Implement some more GETINFO goodness: expose helper nodes, config
11758 options, getinfo keys.
11761 Changes in version 0.1.0.13 - 2005-08-04
11762 o Bugfixes on 0.1.0.x:
11763 - Fix a critical bug in the security of our crypto handshakes.
11764 - Fix a size_t underflow in smartlist_join_strings2() that made
11765 it do bad things when you hand it an empty smartlist.
11766 - Fix Windows installer to ship Tor license (thanks to Aphex for
11767 pointing out this oversight) and put a link to the doc directory
11769 - Explicitly set no-unaligned-access for sparc: it turns out the
11770 new gcc's let you compile broken code, but that doesn't make it
11774 Changes in version 0.1.1.3-alpha - 2005-07-23
11775 o Bugfixes on 0.1.1.2-alpha:
11776 - Fix a bug in handling the controller's "post descriptor"
11778 - Fix several bugs in handling the controller's "extend circuit"
11780 - Fix a bug in handling the controller's "stream status" event.
11781 - Fix an assert failure if we have a controller listening for
11782 circuit events and we go offline.
11783 - Re-allow hidden service descriptors to publish 0 intro points.
11784 - Fix a crash when generating your hidden service descriptor if
11785 you don't have enough intro points already.
11787 o New features on 0.1.1.2-alpha:
11788 - New controller function "getinfo accounting", to ask how
11789 many bytes we've used in this time period.
11790 - Experimental support for helper nodes: a lot of the risk from
11791 a small static adversary comes because users pick new random
11792 nodes every time they rebuild a circuit. Now users will try to
11793 stick to the same small set of entry nodes if they can. Not
11794 enabled by default yet.
11796 o Bugfixes on 0.1.0.12:
11797 - If you're an auth dir server, always publish your dirport,
11798 even if you haven't yet found yourself to be reachable.
11799 - Fix a size_t underflow in smartlist_join_strings2() that made
11800 it do bad things when you hand it an empty smartlist.
11803 Changes in version 0.1.0.12 - 2005-07-18
11804 o New directory servers:
11805 - tor26 has changed IP address.
11807 o Bugfixes on 0.1.0.x:
11808 - Fix a possible double-free in tor_gzip_uncompress().
11809 - When --disable-threads is set, do not search for or link against
11810 pthreads libraries.
11811 - Don't trigger an assert if an authoritative directory server
11812 claims its dirport is 0.
11813 - Fix bug with removing Tor as an NT service: some people were
11814 getting "The service did not return an error." Thanks to Matt
11818 Changes in version 0.1.1.2-alpha - 2005-07-15
11819 o New directory servers:
11820 - tor26 has changed IP address.
11822 o Bugfixes on 0.1.0.x, crashes/leaks:
11823 - Port the servers-not-obeying-their-exit-policies fix from
11825 - Fix an fd leak in start_daemon().
11826 - On Windows, you can't always reopen a port right after you've
11827 closed it. So change retry_listeners() to only close and re-open
11828 ports that have changed.
11829 - Fix a possible double-free in tor_gzip_uncompress().
11831 o Bugfixes on 0.1.0.x, usability:
11832 - When tor_socketpair() fails in Windows, give a reasonable
11833 Windows-style errno back.
11834 - Let people type "tor --install" as well as "tor -install" when
11836 want to make it an NT service.
11837 - NT service patch from Matt Edman to improve error messages.
11838 - When the controller asks for a config option with an abbreviated
11839 name, give the full name in our response.
11840 - Correct the man page entry on TrackHostExitsExpire.
11841 - Looks like we were never delivering deflated (i.e. compressed)
11842 running-routers lists, even when asked. Oops.
11843 - When --disable-threads is set, do not search for or link against
11844 pthreads libraries.
11846 o Bugfixes on 0.1.1.x:
11847 - Fix a seg fault with autodetecting which controller version is
11851 - New hidden service descriptor format: put a version in it, and
11852 let people specify introduction/rendezvous points that aren't
11853 in "the directory" (which is subjective anyway).
11854 - Allow the DEBUG controller event to work again. Mark certain log
11855 entries as "don't tell this to controllers", so we avoid cycles.
11858 Changes in version 0.1.0.11 - 2005-06-30
11859 o Bugfixes on 0.1.0.x:
11860 - Fix major security bug: servers were disregarding their
11861 exit policies if clients behaved unexpectedly.
11862 - Make OS X init script check for missing argument, so we don't
11863 confuse users who invoke it incorrectly.
11864 - Fix a seg fault in "tor --hash-password foo".
11865 - The MAPADDRESS control command was broken.
11868 Changes in version 0.1.1.1-alpha - 2005-06-29
11870 - Make OS X init script check for missing argument, so we don't
11871 confuse users who invoke it incorrectly.
11872 - Fix a seg fault in "tor --hash-password foo".
11873 - Fix a possible way to DoS dirservers.
11874 - When we complain that your exit policy implicitly allows local or
11875 private address spaces, name them explicitly so operators can
11877 - Make the log message less scary when all the dirservers are
11878 temporarily unreachable.
11879 - We were printing the number of idle dns workers incorrectly when
11883 - Revised controller protocol (version 1) that uses ascii rather
11884 than binary. Add supporting libraries in python and java so you
11885 can use the controller from your applications without caring how
11886 our protocol works.
11887 - Spiffy new support for crypto hardware accelerators. Can somebody
11891 Changes in version 0.0.9.10 - 2005-06-16
11892 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
11893 - Refuse relay cells that claim to have a length larger than the
11894 maximum allowed. This prevents a potential attack that could read
11895 arbitrary memory (e.g. keys) from an exit server's process
11899 Changes in version 0.1.0.10 - 2005-06-14
11900 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
11901 libevent before 1.1a.
11904 Changes in version 0.1.0.9-rc - 2005-06-09
11906 - Reset buf->highwater every time buf_shrink() is called, not just on
11907 a successful shrink. This was causing significant memory bloat.
11908 - Fix buffer overflow when checking hashed passwords.
11909 - Security fix: if seeding the RNG on Win32 fails, quit.
11910 - Allow seeding the RNG on Win32 even when you're not running as
11912 - Disable threading on Solaris too. Something is wonky with it,
11913 cpuworkers, and reentrant libs.
11914 - Reenable the part of the code that tries to flush as soon as an
11915 OR outbuf has a full TLS record available. Perhaps this will make
11916 OR outbufs not grow as huge except in rare cases, thus saving lots
11917 of CPU time plus memory.
11918 - Reject malformed .onion addresses rather then passing them on as
11919 normal web requests.
11920 - Adapt patch from Adam Langley: fix possible memory leak in
11921 tor_lookup_hostname().
11922 - Initialize libevent later in the startup process, so the logs are
11923 already established by the time we start logging libevent warns.
11924 - Use correct errno on win32 if libevent fails.
11925 - Check and warn about known-bad/slow libevent versions.
11926 - Pay more attention to the ClientOnly config option.
11927 - Have torctl.in/tor.sh.in check for location of su binary (needed
11929 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
11930 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
11931 HttpProxyAuthenticator
11932 - Stop warning about sigpipes in the logs. We're going to
11933 pretend that getting these occassionally is normal and fine.
11934 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
11936 installer screens; and don't put stuff into StartupItems unless
11937 the user asks you to.
11938 - Require servers that use the default dirservers to have public IP
11939 addresses. We have too many servers that are configured with private
11940 IPs and their admins never notice the log entries complaining that
11941 their descriptors are being rejected.
11942 - Add OSX uninstall instructions. An actual uninstall script will
11946 Changes in version 0.1.0.8-rc - 2005-05-23
11948 - It turns out that kqueue on OS X 10.3.9 was causing kernel
11949 panics. Disable kqueue on all OS X Tors.
11950 - Fix RPM: remove duplicate line accidentally added to the rpm
11952 - Disable threads on openbsd too, since its gethostaddr is not
11954 - Tolerate libevent 0.8 since it still works, even though it's
11956 - Enable building on Red Hat 9.0 again.
11957 - Allow the middle hop of the testing circuit to be running any
11958 version, now that most of them have the bugfix to let them connect
11959 to unknown servers. This will allow reachability testing to work
11960 even when 0.0.9.7-0.0.9.9 become obsolete.
11961 - Handle relay cells with rh.length too large. This prevents
11962 a potential attack that could read arbitrary memory (maybe even
11963 keys) from the exit server's process.
11964 - We screwed up the dirport reachability testing when we don't yet
11965 have a cached version of the directory. Hopefully now fixed.
11966 - Clean up router_load_single_router() (used by the controller),
11967 so it doesn't seg fault on error.
11968 - Fix a minor memory leak when somebody establishes an introduction
11969 point at your Tor server.
11970 - If a socks connection ends because read fails, don't warn that
11971 you're not sending a socks reply back.
11974 - Add HttpProxyAuthenticator config option too, that works like
11975 the HttpsProxyAuthenticator config option.
11976 - Encode hashed controller passwords in hex instead of base64,
11977 to make it easier to write controllers.
11980 Changes in version 0.1.0.7-rc - 2005-05-17
11982 - Fix a bug in the OS X package installer that prevented it from
11983 installing on Tiger.
11984 - Fix a script bug in the OS X package installer that made it
11985 complain during installation.
11986 - Find libevent even if it's hiding in /usr/local/ and your
11987 CFLAGS and LDFLAGS don't tell you to look there.
11988 - Be able to link with libevent as a shared library (the default
11989 after 1.0d), even if it's hiding in /usr/local/lib and even
11990 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
11991 assuming you're running gcc. Otherwise fail and give a useful
11993 - Fix a bug in the RPM packager: set home directory for _tor to
11994 something more reasonable when first installing.
11995 - Free a minor amount of memory that is still reachable on exit.
11998 Changes in version 0.1.0.6-rc - 2005-05-14
12000 - Implement --disable-threads configure option. Disable threads on
12001 netbsd by default, because it appears to have no reentrant resolver
12003 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
12004 release (1.1) detects and disables kqueue if it's broken.
12005 - Append default exit policy before checking for implicit internal
12006 addresses. Now we don't log a bunch of complaints on startup
12007 when using the default exit policy.
12008 - Some people were putting "Address " in their torrc, and they had
12009 a buggy resolver that resolved " " to 0.0.0.0. Oops.
12010 - If DataDir is ~/.tor, and that expands to /.tor, then default to
12011 LOCALSTATEDIR/tor instead.
12012 - Fix fragmented-message bug in TorControl.py.
12013 - Resolve a minor bug which would prevent unreachable dirports
12014 from getting suppressed in the published descriptor.
12015 - When the controller gave us a new descriptor, we weren't resolving
12016 it immediately, so Tor would think its address was 0.0.0.0 until
12017 we fetched a new directory.
12018 - Fix an uppercase/lowercase case error in suppressing a bogus
12019 libevent warning on some Linuxes.
12022 - Begin scrubbing sensitive strings from logs by default. Turn off
12023 the config option SafeLogging if you need to do debugging.
12024 - Switch to a new buffer management algorithm, which tries to avoid
12025 reallocing and copying quite as much. In first tests it looks like
12026 it uses *more* memory on average, but less cpu.
12027 - First cut at support for "create-fast" cells. Clients can use
12028 these when extending to their first hop, since the TLS already
12029 provides forward secrecy and authentication. Not enabled on
12031 - When dirservers refuse a router descriptor, we now log its
12032 contactinfo, platform, and the poster's IP address.
12033 - Call tor_free_all instead of connections_free_all after forking, to
12034 save memory on systems that need to fork.
12035 - Whine at you if you're a server and you don't set your contactinfo.
12036 - Implement --verify-config command-line option to check if your torrc
12037 is valid without actually launching Tor.
12038 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
12039 rather than just rejecting it.
12042 Changes in version 0.1.0.5-rc - 2005-04-27
12044 - Stop trying to print a null pointer if an OR conn fails because
12045 we didn't like its cert.
12047 - Switch our internal buffers implementation to use a ring buffer,
12048 to hopefully improve performance for fast servers a lot.
12049 - Add HttpsProxyAuthenticator support (basic auth only), based
12050 on patch from Adam Langley.
12051 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
12052 the fast servers that have been joining lately.
12053 - Give hidden service accesses extra time on the first attempt,
12054 since 60 seconds is often only barely enough. This might improve
12056 - Improve performance for dirservers: stop re-parsing the whole
12057 directory every time you regenerate it.
12058 - Add more debugging info to help us find the weird dns freebsd
12059 pthreads bug; cleaner debug messages to help track future issues.
12062 Changes in version 0.0.9.9 - 2005-04-23
12063 o Bugfixes on 0.0.9.x:
12064 - If unofficial Tor clients connect and send weird TLS certs, our
12065 Tor server triggers an assert. This release contains a minimal
12066 backport from the broader fix that we put into 0.1.0.4-rc.
12069 Changes in version 0.1.0.4-rc - 2005-04-23
12071 - If unofficial Tor clients connect and send weird TLS certs, our
12072 Tor server triggers an assert. Stop asserting, and start handling
12073 TLS errors better in other situations too.
12074 - When the controller asks us to tell it about all the debug-level
12075 logs, it turns out we were generating debug-level logs while
12076 telling it about them, which turns into a bad loop. Now keep
12077 track of whether you're sending a debug log to the controller,
12078 and don't log when you are.
12079 - Fix the "postdescriptor" feature of the controller interface: on
12080 non-complete success, only say "done" once.
12082 - Clients are now willing to load balance over up to 2mB, not 1mB,
12083 of advertised bandwidth capacity.
12084 - Add a NoPublish config option, so you can be a server (e.g. for
12085 testing running Tor servers in other Tor networks) without
12086 publishing your descriptor to the primary dirservers.
12089 Changes in version 0.1.0.3-rc - 2005-04-08
12090 o Improvements on 0.1.0.2-rc:
12091 - Client now retries when streams end early for 'hibernating' or
12092 'resource limit' reasons, rather than failing them.
12093 - More automated handling for dirserver operators:
12094 - Automatically approve nodes running 0.1.0.2-rc or later,
12095 now that the the reachability detection stuff is working.
12096 - Now we allow two unverified servers with the same nickname
12097 but different keys. But if a nickname is verified, only that
12098 nickname+key are allowed.
12099 - If you're an authdirserver connecting to an address:port,
12100 and it's not the OR you were expecting, forget about that
12101 descriptor. If he *was* the one you were expecting, then forget
12102 about all other descriptors for that address:port.
12103 - Allow servers to publish descriptors from 12 hours in the future.
12104 Corollary: only whine about clock skew from the dirserver if
12105 he's a trusted dirserver (since now even verified servers could
12106 have quite wrong clocks).
12107 - Adjust maximum skew and age for rendezvous descriptors: let skew
12108 be 48 hours rather than 90 minutes.
12109 - Efficiency improvements:
12110 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
12111 it much faster to look up a circuit for each relay cell.
12112 - Remove most calls to assert_all_pending_dns_resolves_ok(),
12113 since they're eating our cpu on exit nodes.
12114 - Stop wasting time doing a case insensitive comparison for every
12115 dns name every time we do any lookup. Canonicalize the names to
12116 lowercase and be done with it.
12117 - Start sending 'truncated' cells back rather than destroy cells,
12118 if the circuit closes in front of you. This means we won't have
12119 to abandon partially built circuits.
12120 - Only warn once per nickname from add_nickname_list_to_smartlist
12121 per failure, so an entrynode or exitnode choice that's down won't
12123 - Put a note in the torrc about abuse potential with the default
12125 - Revise control spec and implementation to allow all log messages to
12126 be sent to controller with their severities intact (suggested by
12127 Matt Edman). Update TorControl to handle new log event types.
12128 - Provide better explanation messages when controller's POSTDESCRIPTOR
12130 - Stop putting nodename in the Platform string in server descriptors.
12131 It doesn't actually help, and it is confusing/upsetting some people.
12133 o Bugfixes on 0.1.0.2-rc:
12134 - We were printing the host mask wrong in exit policies in server
12135 descriptors. This isn't a critical bug though, since we were still
12136 obeying the exit policy internally.
12137 - Fix Tor when compiled with libevent but without pthreads: move
12138 connection_unregister() from _connection_free() to
12140 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
12141 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
12142 when we look through the connection array, we'll find any of the
12143 cpu/dnsworkers. This is no good.
12145 o Bugfixes on 0.0.9.8:
12146 - Fix possible bug on threading platforms (e.g. win32) which was
12147 leaking a file descriptor whenever a cpuworker or dnsworker died.
12148 - When using preferred entry or exit nodes, ignore whether the
12149 circuit wants uptime or capacity. They asked for the nodes, they
12151 - chdir() to your datadirectory at the *end* of the daemonize process,
12152 not the beginning. This was a problem because the first time you
12153 run tor, if your datadir isn't there, and you have runasdaemon set
12154 to 1, it will try to chdir to it before it tries to create it. Oops.
12155 - Handle changed router status correctly when dirserver reloads
12156 fingerprint file. We used to be dropping all unverified descriptors
12157 right then. The bug was hidden because we would immediately
12158 fetch a directory from another dirserver, which would include the
12159 descriptors we just dropped.
12160 - When we're connecting to an OR and he's got a different nickname/key
12161 than we were expecting, only complain loudly if we're an OP or a
12162 dirserver. Complaining loudly to the OR admins just confuses them.
12163 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
12164 artificially capped at 500kB.
12167 Changes in version 0.0.9.8 - 2005-04-07
12168 o Bugfixes on 0.0.9.x:
12169 - We have a bug that I haven't found yet. Sometimes, very rarely,
12170 cpuworkers get stuck in the 'busy' state, even though the cpuworker
12171 thinks of itself as idle. This meant that no new circuits ever got
12172 established. Here's a workaround to kill any cpuworker that's been
12173 busy for more than 100 seconds.
12176 Changes in version 0.1.0.2-rc - 2005-04-01
12177 o Bugfixes on 0.1.0.1-rc:
12178 - Fixes on reachability detection:
12179 - Don't check for reachability while hibernating.
12180 - If ORPort is reachable but DirPort isn't, still publish the
12181 descriptor, but zero out DirPort until it's found reachable.
12182 - When building testing circs for ORPort testing, use only
12183 high-bandwidth nodes, so fewer circuits fail.
12184 - Complain about unreachable ORPort separately from unreachable
12185 DirPort, so the user knows what's going on.
12186 - Make sure we only conclude ORPort reachability if we didn't
12187 initiate the conn. Otherwise we could falsely conclude that
12188 we're reachable just because we connected to the guy earlier
12189 and he used that same pipe to extend to us.
12190 - Authdirservers shouldn't do ORPort reachability detection,
12191 since they're in clique mode, so it will be rare to find a
12192 server not already connected to them.
12193 - When building testing circuits, always pick middle hops running
12194 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
12195 bug. (This is a kludge; it will go away when 0.0.9.x becomes
12197 - When we decide we're reachable, actually publish our descriptor
12199 - Fix bug in redirectstream in the controller.
12200 - Fix the state descriptor strings so logs don't claim edge streams
12201 are in a different state than they actually are.
12202 - Use recent libevent features when possible (this only really affects
12203 win32 and osx right now, because the new libevent with these
12204 features hasn't been released yet). Add code to suppress spurious
12206 - Prevent possible segfault in connection_close_unattached_ap().
12207 - Fix newlines on torrc in win32.
12208 - Improve error msgs when tor-resolve fails.
12210 o Improvements on 0.0.9.x:
12211 - New experimental script tor/contrib/ExerciseServer.py (needs more
12212 work) that uses the controller interface to build circuits and
12213 fetch pages over them. This will help us bootstrap servers that
12214 have lots of capacity but haven't noticed it yet.
12215 - New experimental script tor/contrib/PathDemo.py (needs more work)
12216 that uses the controller interface to let you choose whole paths
12218 "<hostname>.<path,separated by dots>.<length of path>.path"
12219 - When we've connected to an OR and handshaked but didn't like
12220 the result, we were closing the conn without sending destroy
12221 cells back for pending circuits. Now send those destroys.
12224 Changes in version 0.0.9.7 - 2005-04-01
12225 o Bugfixes on 0.0.9.x:
12226 - Fix another race crash bug (thanks to Glenn Fink for reporting).
12227 - Compare identity to identity, not to nickname, when extending to
12228 a router not already in the directory. This was preventing us from
12229 extending to unknown routers. Oops.
12230 - Make sure to create OS X Tor user in <500 range, so we aren't
12231 creating actual system users.
12232 - Note where connection-that-hasn't-sent-end was marked, and fix
12233 a few really loud instances of this harmless bug (it's fixed more
12237 Changes in version 0.1.0.1-rc - 2005-03-28
12239 - Add reachability testing. Your Tor server will automatically try
12240 to see if its ORPort and DirPort are reachable from the outside,
12241 and it won't upload its descriptor until it decides they are.
12242 - Handle unavailable hidden services better. Handle slow or busy
12243 hidden services better.
12244 - Add support for CONNECTing through https proxies, with "HttpsProxy"
12246 - New exit policy: accept most low-numbered ports, rather than
12247 rejecting most low-numbered ports.
12248 - More Tor controller support (still experimental). See
12249 http://tor.eff.org/doc/control-spec.txt for all the new features,
12250 including signals to emulate unix signals from any platform;
12251 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
12252 closestream; closecircuit; etc.
12253 - Make nt services work and start on startup on win32 (based on
12254 patch by Matt Edman).
12255 - Add a new AddressMap config directive to rewrite incoming socks
12256 addresses. This lets you, for example, declare an implicit
12257 required exit node for certain sites.
12258 - Add a new TrackHostExits config directive to trigger addressmaps
12259 for certain incoming socks addresses -- for sites that break when
12260 your exit keeps changing (based on patch by Mike Perry).
12261 - Redo the client-side dns cache so it's just an addressmap too.
12262 - Notice when our IP changes, and reset stats/uptime/reachability.
12263 - When an application is using socks5, give him the whole variety of
12264 potential socks5 responses (connect refused, host unreachable, etc),
12265 rather than just "success" or "failure".
12266 - A more sane version numbering system. See
12267 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
12268 - New contributed script "exitlist": a simple python script to
12269 parse directories and find Tor nodes that exit to listed
12271 - New contributed script "privoxy-tor-toggle" to toggle whether
12272 Privoxy uses Tor. Seems to be configured for Debian by default.
12273 - Report HTTP reasons to client when getting a response from directory
12274 servers -- so you can actually know what went wrong.
12275 - New config option MaxAdvertisedBandwidth which lets you advertise
12276 a low bandwidthrate (to not attract as many circuits) while still
12277 allowing a higher bandwidthrate in reality.
12279 o Robustness/stability fixes:
12280 - Make Tor use Niels Provos's libevent instead of its current
12281 poll-but-sometimes-select mess. This will let us use faster async
12282 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
12284 - pthread support now too. This was forced because when we forked,
12285 we ended up wasting a lot of duplicate ram over time. Also switch
12286 to foo_r versions of some library calls to allow reentry and
12288 - Better handling for heterogeneous / unreliable nodes:
12289 - Annotate circuits w/ whether they aim to contain high uptime nodes
12290 and/or high capacity nodes. When building circuits, choose
12292 - This means that every single node in an intro rend circuit,
12293 not just the last one, will have a minimum uptime.
12294 - New config option LongLivedPorts to indicate application streams
12295 that will want high uptime circuits.
12296 - Servers reset uptime when a dir fetch entirely fails. This
12297 hopefully reflects stability of the server's network connectivity.
12298 - If somebody starts his tor server in Jan 2004 and then fixes his
12299 clock, don't make his published uptime be a year.
12300 - Reset published uptime when you wake up from hibernation.
12301 - Introduce a notion of 'internal' circs, which are chosen without
12302 regard to the exit policy of the last hop. Intro and rendezvous
12303 circs must be internal circs, to avoid leaking information. Resolve
12304 and connect streams can use internal circs if they want.
12305 - New circuit pooling algorithm: make sure to have enough circs around
12306 to satisfy any predicted ports, and also make sure to have 2 internal
12307 circs around if we've required internal circs lately (and with high
12308 uptime if we've seen that lately too).
12309 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
12310 which describes how often we retry making new circuits if current
12311 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
12312 how long we're willing to make use of an already-dirty circuit.
12313 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
12314 circ as necessary, if there are any completed ones lying around
12315 when we try to launch one.
12316 - Make hidden services try to establish a rendezvous for 30 seconds,
12317 rather than for n (where n=3) attempts to build a circuit.
12318 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
12319 "ShutdownWaitLength".
12320 - Try to be more zealous about calling connection_edge_end when
12321 things go bad with edge conns in connection.c.
12322 - Revise tor-spec to add more/better stream end reasons.
12323 - Revise all calls to connection_edge_end to avoid sending "misc",
12324 and to take errno into account where possible.
12327 - Fix a race condition that can trigger an assert, when we have a
12328 pending create cell and an OR connection fails right then.
12329 - Fix several double-mark-for-close bugs, e.g. where we were finding
12330 a conn for a cell even if that conn is already marked for close.
12331 - Make sequence of log messages when starting on win32 with no config
12332 file more reasonable.
12333 - When choosing an exit node for a new non-internal circ, don't take
12334 into account whether it'll be useful for any pending x.onion
12335 addresses -- it won't.
12336 - Turn addr_policy_compare from a tristate to a quadstate; this should
12337 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
12338 for google.com" problem.
12339 - Make "platform" string in descriptor more accurate for Win32 servers,
12340 so it's not just "unknown platform".
12341 - Fix an edge case in parsing config options (thanks weasel).
12342 If they say "--" on the commandline, it's not an option.
12343 - Reject odd-looking addresses at the client (e.g. addresses that
12344 contain a colon), rather than having the server drop them because
12346 - tor-resolve requests were ignoring .exit if there was a working circuit
12347 they could use instead.
12348 - REUSEADDR on normal platforms means you can rebind to the port
12349 right after somebody else has let it go. But REUSEADDR on win32
12350 means to let you bind to the port _even when somebody else
12351 already has it bound_! So, don't do that on Win32.
12352 - Change version parsing logic: a version is "obsolete" if it is not
12353 recommended and (1) there is a newer recommended version in the
12354 same series, or (2) there are no recommended versions in the same
12355 series, but there are some recommended versions in a newer series.
12356 A version is "new" if it is newer than any recommended version in
12358 - Stop most cases of hanging up on a socks connection without sending
12362 - Require BandwidthRate to be at least 20kB/s for servers.
12363 - When a dirserver causes you to give a warn, mention which dirserver
12365 - New config option DirAllowPrivateAddresses for authdirservers.
12366 Now by default they refuse router descriptors that have non-IP or
12367 private-IP addresses.
12368 - Stop publishing socksport in the directory, since it's not
12369 actually meant to be public. For compatibility, publish a 0 there
12371 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
12372 smart" value, that is low for servers and high for clients.
12373 - If our clock jumps forward by 100 seconds or more, assume something
12374 has gone wrong with our network and abandon all not-yet-used circs.
12375 - Warn when exit policy implicitly allows local addresses.
12376 - If we get an incredibly skewed timestamp from a dirserver mirror
12377 that isn't a verified OR, don't warn -- it's probably him that's
12379 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
12380 cookies to disk and doesn't log each web request to disk. (Thanks
12381 to Brett Carrington for pointing this out.)
12382 - When a client asks us for a dir mirror and we don't have one,
12383 launch an attempt to get a fresh one.
12384 - If we're hibernating and we get a SIGINT, exit immediately.
12385 - Add --with-dmalloc ./configure option, to track memory leaks.
12386 - And try to free all memory on closing, so we can detect what
12388 - Cache local dns resolves correctly even when they're .exit
12390 - Give a better warning when some other server advertises an
12391 ORPort that is actually an apache running ssl.
12392 - Add "opt hibernating 1" to server descriptor to make it clearer
12393 whether the server is hibernating.
12396 Changes in version 0.0.9.6 - 2005-03-24
12397 o Bugfixes on 0.0.9.x (crashes and asserts):
12398 - Add new end stream reasons to maintainance branch. Fix bug where
12399 reason (8) could trigger an assert. Prevent bug from recurring.
12400 - Apparently win32 stat wants paths to not end with a slash.
12401 - Fix assert triggers in assert_cpath_layer_ok(), where we were
12402 blowing away the circuit that conn->cpath_layer points to, then
12403 checking to see if the circ is well-formed. Backport check to make
12404 sure we dont use the cpath on a closed connection.
12405 - Prevent circuit_resume_edge_reading_helper() from trying to package
12406 inbufs for marked-for-close streams.
12407 - Don't crash on hup if your options->address has become unresolvable.
12408 - Some systems (like OS X) sometimes accept() a connection and tell
12409 you the remote host is 0.0.0.0:0. If this happens, due to some
12410 other mis-features, we get confused; so refuse the conn for now.
12412 o Bugfixes on 0.0.9.x (other):
12413 - Fix harmless but scary "Unrecognized content encoding" warn message.
12414 - Add new stream error reason: TORPROTOCOL reason means "you are not
12415 speaking a version of Tor I understand; say bye-bye to your stream."
12416 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
12417 into the future, now that we are more tolerant of skew. This
12418 resolves a bug where a Tor server would refuse to cache a directory
12419 because all the directories it gets are too far in the future;
12420 yet the Tor server never logs any complaints about clock skew.
12421 - Mac packaging magic: make man pages useable, and do not overwrite
12422 existing torrc files.
12423 - Make OS X log happily to /var/log/tor/tor.log
12426 Changes in version 0.0.9.5 - 2005-02-22
12427 o Bugfixes on 0.0.9.x:
12428 - Fix an assert race at exit nodes when resolve requests fail.
12429 - Stop picking unverified dir mirrors--it only leads to misery.
12430 - Patch from Matt Edman to make NT services work better. Service
12431 support is still not compiled into the executable by default.
12432 - Patch from Dmitri Bely so the Tor service runs better under
12433 the win32 SYSTEM account.
12434 - Make tor-resolve actually work (?) on Win32.
12435 - Fix a sign bug when getrlimit claims to have 4+ billion
12436 file descriptors available.
12437 - Stop refusing to start when bandwidthburst == bandwidthrate.
12438 - When create cells have been on the onion queue more than five
12439 seconds, just send back a destroy and take them off the list.
12442 Changes in version 0.0.9.4 - 2005-02-03
12443 o Bugfixes on 0.0.9:
12444 - Fix an assert bug that took down most of our servers: when
12445 a server claims to have 1 GB of bandwidthburst, don't
12447 - Don't crash as badly if we have spawned the max allowed number
12448 of dnsworkers, or we're out of file descriptors.
12449 - Block more file-sharing ports in the default exit policy.
12450 - MaxConn is now automatically set to the hard limit of max
12451 file descriptors we're allowed (ulimit -n), minus a few for
12453 - Give a clearer message when servers need to raise their
12454 ulimit -n when they start running out of file descriptors.
12455 - SGI Compatibility patches from Jan Schaumann.
12456 - Tolerate a corrupt cached directory better.
12457 - When a dirserver hasn't approved your server, list which one.
12458 - Go into soft hibernation after 95% of the bandwidth is used,
12459 not 99%. This is especially important for daily hibernators who
12460 have a small accounting max. Hopefully it will result in fewer
12461 cut connections when the hard hibernation starts.
12462 - Load-balance better when using servers that claim more than
12463 800kB/s of capacity.
12464 - Make NT services work (experimental, only used if compiled in).
12467 Changes in version 0.0.9.3 - 2005-01-21
12468 o Bugfixes on 0.0.9:
12469 - Backport the cpu use fixes from main branch, so busy servers won't
12470 need as much processor time.
12471 - Work better when we go offline and then come back, or when we
12472 run Tor at boot before the network is up. We do this by
12473 optimistically trying to fetch a new directory whenever an
12474 application request comes in and we think we're offline -- the
12475 human is hopefully a good measure of when the network is back.
12476 - Backport some minimal hidserv bugfixes: keep rend circuits open as
12477 long as you keep using them; actually publish hidserv descriptors
12478 shortly after they change, rather than waiting 20-40 minutes.
12479 - Enable Mac startup script by default.
12480 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
12481 - When you update AllowUnverifiedNodes or FirewallPorts via the
12482 controller's setconf feature, we were always appending, never
12484 - When you update HiddenServiceDir via setconf, it was screwing up
12485 the order of reading the lines, making it fail.
12486 - Do not rewrite a cached directory back to the cache; otherwise we
12487 will think it is recent and not fetch a newer one on startup.
12488 - Workaround for webservers that lie about Content-Encoding: Tor
12489 now tries to autodetect compressed directories and compression
12490 itself. This lets us Proxypass dir fetches through apache.
12493 Changes in version 0.0.9.2 - 2005-01-04
12494 o Bugfixes on 0.0.9 (crashes and asserts):
12495 - Fix an assert on startup when the disk is full and you're logging
12497 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
12498 style address, then we'd crash.
12499 - Fix an assert trigger when the running-routers string we get from
12500 a dirserver is broken.
12501 - Make worker threads start and run on win32. Now win32 servers
12503 - Bandaid (not actually fix, but now it doesn't crash) an assert
12504 where the dns worker dies mysteriously and the main Tor process
12505 doesn't remember anything about the address it was resolving.
12507 o Bugfixes on 0.0.9 (Win32):
12508 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
12509 name out of the warning/assert messages.
12510 - Fix a superficial "unhandled error on read" bug on win32.
12511 - The win32 installer no longer requires a click-through for our
12512 license, since our Free Software license grants rights but does not
12514 - Win32: When connecting to a dirserver fails, try another one
12515 immediately. (This was already working for non-win32 Tors.)
12516 - Stop trying to parse $HOME on win32 when hunting for default
12518 - Make tor-resolve.c work on win32 by calling network_init().
12520 o Bugfixes on 0.0.9 (other):
12521 - Make 0.0.9.x build on Solaris again.
12522 - Due to a fencepost error, we were blowing away the \n when reporting
12523 confvalue items in the controller. So asking for multiple config
12524 values at once couldn't work.
12525 - When listing circuits that are pending on an opening OR connection,
12526 if we're an OR we were listing circuits that *end* at us as
12527 being pending on every listener, dns/cpu worker, etc. Stop that.
12528 - Dirservers were failing to create 'running-routers' or 'directory'
12529 strings if we had more than some threshold of routers. Fix them so
12530 they can handle any number of routers.
12531 - Fix a superficial "Duplicate mark for close" bug.
12532 - Stop checking for clock skew for OR connections, even for servers.
12533 - Fix a fencepost error that was chopping off the last letter of any
12534 nickname that is the maximum allowed nickname length.
12535 - Update URLs in log messages so they point to the new website.
12536 - Fix a potential problem in mangling server private keys while
12537 writing to disk (not triggered yet, as far as we know).
12538 - Include the licenses for other free software we include in Tor,
12539 now that we're shipping binary distributions more regularly.
12542 Changes in version 0.0.9.1 - 2004-12-15
12543 o Bugfixes on 0.0.9:
12544 - Make hibernation actually work.
12545 - Make HashedControlPassword config option work.
12546 - When we're reporting event circuit status to a controller,
12547 don't use the stream status code.
12550 Changes in version 0.0.9 - 2004-12-12
12552 - Clean up manpage and torrc.sample file.
12553 - Clean up severities and text of log warnings.
12555 - Make servers trigger an assert when they enter hibernation.
12558 Changes in version 0.0.9rc7 - 2004-12-08
12559 o Bugfixes on 0.0.9rc:
12560 - Fix a stack-trashing crash when an exit node begins hibernating.
12561 - Avoid looking at unallocated memory while considering which
12562 ports we need to build circuits to cover.
12563 - Stop a sigpipe: when an 'end' cell races with eof from the app,
12564 we shouldn't hold-open-until-flush if the eof arrived first.
12565 - Fix a bug with init_cookie_authentication() in the controller.
12566 - When recommending new-format log lines, if the upper bound is
12567 LOG_ERR, leave it implicit.
12569 o Bugfixes on 0.0.8.1:
12570 - Fix a whole slew of memory leaks.
12571 - Fix isspace() and friends so they still make Solaris happy
12572 but also so they don't trigger asserts on win32.
12573 - Fix parse_iso_time on platforms without strptime (eg win32).
12574 - win32: tolerate extra "readable" events better.
12575 - win32: when being multithreaded, leave parent fdarray open.
12576 - Make unit tests work on win32.
12579 Changes in version 0.0.9rc6 - 2004-12-06
12580 o Bugfixes on 0.0.9pre:
12581 - Clean up some more integer underflow opportunities (not exploitable
12583 - While hibernating, hup should not regrow our listeners.
12584 - Send an end to the streams we close when we hibernate, rather
12585 than just chopping them off.
12586 - React to eof immediately on non-open edge connections.
12588 o Bugfixes on 0.0.8.1:
12589 - Calculate timeout for waiting for a connected cell from the time
12590 we sent the begin cell, not from the time the stream started. If
12591 it took a long time to establish the circuit, we would time out
12592 right after sending the begin cell.
12593 - Fix router_compare_addr_to_addr_policy: it was not treating a port
12594 of * as always matching, so we were picking reject *:* nodes as
12595 exit nodes too. Oops.
12598 - New circuit building strategy: keep a list of ports that we've
12599 used in the past 6 hours, and always try to have 2 circuits open
12600 or on the way that will handle each such port. Seed us with port
12601 80 so web users won't complain that Tor is "slow to start up".
12602 - Make kill -USR1 dump more useful stats about circuits.
12603 - When warning about retrying or giving up, print the address, so
12604 the user knows which one it's talking about.
12605 - If you haven't used a clean circuit in an hour, throw it away,
12606 just to be on the safe side. (This means after 6 hours a totally
12607 unused Tor client will have no circuits open.)
12610 Changes in version 0.0.9rc5 - 2004-12-01
12611 o Bugfixes on 0.0.8.1:
12612 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
12613 - Let resolve conns retry/expire also, rather than sticking around
12615 - If we are using select, make sure we stay within FD_SETSIZE.
12617 o Bugfixes on 0.0.9pre:
12618 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
12619 but doesn't seem to be currently; thanks to Ilja van Sprundel for
12621 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
12622 instead. Impose minima and maxima for all *Period options; impose
12623 even tighter maxima for fetching if we are a caching dirserver.
12624 Clip rather than rejecting.
12625 - Fetch cached running-routers from servers that serve it (that is,
12626 authdirservers and servers running 0.0.9rc5-cvs or later.)
12629 - Accept *:706 (silc) in default exit policy.
12630 - Implement new versioning format for post 0.1.
12631 - Support "foo.nickname.exit" addresses, to let Alice request the
12632 address "foo" as viewed by exit node "nickname". Based on a patch
12634 - Make tor --version --version dump the cvs Id of every file.
12637 Changes in version 0.0.9rc4 - 2004-11-28
12638 o Bugfixes on 0.0.8.1:
12639 - Make windows sockets actually non-blocking (oops), and handle
12640 win32 socket errors better.
12642 o Bugfixes on 0.0.9rc1:
12643 - Actually catch the -USR2 signal.
12646 Changes in version 0.0.9rc3 - 2004-11-25
12647 o Bugfixes on 0.0.8.1:
12648 - Flush the log file descriptor after we print "Tor opening log file",
12649 so we don't see those messages days later.
12651 o Bugfixes on 0.0.9rc1:
12652 - Make tor-resolve work again.
12653 - Avoid infinite loop in tor-resolve if tor hangs up on it.
12654 - Fix an assert trigger for clients/servers handling resolves.
12657 Changes in version 0.0.9rc2 - 2004-11-24
12658 o Bugfixes on 0.0.9rc1:
12659 - I broke socks5 support while fixing the eof bug.
12660 - Allow unitless bandwidths and intervals; they default to bytes
12662 - New servers don't start out hibernating; they are active until
12663 they run out of bytes, so they have a better estimate of how
12664 long it takes, and so their operators can know they're working.
12667 Changes in version 0.0.9rc1 - 2004-11-23
12668 o Bugfixes on 0.0.8.1:
12669 - Finally fix a bug that's been plaguing us for a year:
12670 With high load, circuit package window was reaching 0. Whenever
12671 we got a circuit-level sendme, we were reading a lot on each
12672 socket, but only writing out a bit. So we would eventually reach
12673 eof. This would be noticed and acted on even when there were still
12674 bytes sitting in the inbuf.
12675 - When poll() is interrupted, we shouldn't believe the revents values.
12677 o Bugfixes on 0.0.9pre6:
12678 - Fix hibernate bug that caused pre6 to be broken.
12679 - Don't keep rephist info for routers that haven't had activity for
12680 24 hours. (This matters now that clients have keys, since we track
12682 - Never call close_temp_logs while validating log options.
12683 - Fix backslash-escaping on tor.sh.in and torctl.in.
12686 - Implement weekly/monthly/daily accounting: now you specify your
12687 hibernation properties by
12688 AccountingMax N bytes|KB|MB|GB|TB
12689 AccountingStart day|week|month [day] HH:MM
12690 Defaults to "month 1 0:00".
12691 - Let bandwidth and interval config options be specified as 5 bytes,
12692 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
12693 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
12694 get back to normal.)
12695 - If your requested entry or exit node has advertised bandwidth 0,
12697 - Be more greedy about filling up relay cells -- we try reading again
12698 once we've processed the stuff we read, in case enough has arrived
12699 to fill the last cell completely.
12700 - Apply NT service patch from Osamu Fujino. Still needs more work.
12703 Changes in version 0.0.9pre6 - 2004-11-15
12704 o Bugfixes on 0.0.8.1:
12705 - Fix assert failure on malformed socks4a requests.
12706 - Use identity comparison, not nickname comparison, to choose which
12707 half of circuit-ID-space each side gets to use. This is needed
12708 because sometimes we think of a router as a nickname, and sometimes
12709 as a hex ID, and we can't predict what the other side will do.
12710 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
12711 write() call will fail and we handle it there.
12712 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
12713 and smartlist_len, which are two major profiling offenders.
12715 o Bugfixes on 0.0.9pre5:
12716 - Fix a bug in read_all that was corrupting config files on windows.
12717 - When we're raising the max number of open file descriptors to
12718 'unlimited', don't log that we just raised it to '-1'.
12719 - Include event code with events, as required by control-spec.txt.
12720 - Don't give a fingerprint when clients do --list-fingerprint:
12721 it's misleading, because it will never be the same again.
12722 - Stop using strlcpy in tor_strndup, since it was slowing us
12724 - Remove warn on startup about missing cached-directory file.
12725 - Make kill -USR1 work again.
12726 - Hibernate if we start tor during the "wait for wakeup-time" phase
12727 of an accounting interval. Log our hibernation plans better.
12728 - Authoritative dirservers now also cache their directory, so they
12729 have it on start-up.
12732 - Fetch running-routers; cache running-routers; compress
12733 running-routers; serve compressed running-routers.z
12734 - Add NSI installer script contributed by J Doe.
12735 - Commit VC6 and VC7 workspace/project files.
12736 - Commit a tor.spec for making RPM files, with help from jbash.
12737 - Add contrib/torctl.in contributed by Glenn Fink.
12738 - Implement the control-spec's SAVECONF command, to write your
12739 configuration to torrc.
12740 - Get cookie authentication for the controller closer to working.
12741 - Include control-spec.txt in the tarball.
12742 - When set_conf changes our server descriptor, upload a new copy.
12743 But don't upload it too often if there are frequent changes.
12744 - Document authentication config in man page, and document signals
12746 - Clean up confusing parts of man page and torrc.sample.
12747 - Make expand_filename handle ~ and ~username.
12748 - Use autoconf to enable largefile support where necessary. Use
12749 ftello where available, since ftell can fail at 2GB.
12750 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
12751 log more informatively.
12752 - Give a slightly more useful output for "tor -h".
12753 - Refuse application socks connections to port 0.
12754 - Check clock skew for verified servers, but allow unverified
12755 servers and clients to have any clock skew.
12756 - Break DirFetchPostPeriod into:
12757 - DirFetchPeriod for fetching full directory,
12758 - StatusFetchPeriod for fetching running-routers,
12759 - DirPostPeriod for posting server descriptor,
12760 - RendPostPeriod for posting hidden service descriptors.
12761 - Make sure the hidden service descriptors are at a random offset
12762 from each other, to hinder linkability.
12765 Changes in version 0.0.9pre5 - 2004-11-09
12766 o Bugfixes on 0.0.9pre4:
12767 - Fix a seg fault in unit tests (doesn't affect main program).
12768 - Fix an assert bug where a hidden service provider would fail if
12769 the first hop of his rendezvous circuit was down.
12770 - Hidden service operators now correctly handle version 1 style
12771 INTRODUCE1 cells (nobody generates them still, so not a critical
12773 - If do_hup fails, actually notice.
12774 - Handle more errnos from accept() without closing the listener.
12775 Some OpenBSD machines were closing their listeners because
12776 they ran out of file descriptors.
12777 - Send resolve cells to exit routers that are running a new
12778 enough version of the resolve code to work right.
12779 - Better handling of winsock includes on non-MSV win32 compilers.
12780 - Some people had wrapped their tor client/server in a script
12781 that would restart it whenever it died. This did not play well
12782 with our "shut down if your version is obsolete" code. Now people
12783 don't fetch a new directory if their local cached version is
12785 - Make our autogen.sh work on ksh as well as bash.
12788 - Hibernation: New config option "AccountingMaxKB" lets you
12789 set how many KBytes per month you want to allow your server to
12790 consume. Rather than spreading those bytes out evenly over the
12791 month, we instead hibernate for some of the month and pop up
12792 at a deterministic time, work until the bytes are consumed, then
12793 hibernate again. Config option "MonthlyAccountingStart" lets you
12794 specify which day of the month your billing cycle starts on.
12795 - Control interface: a separate program can now talk to your
12796 client/server over a socket, and get/set config options, receive
12797 notifications of circuits and streams starting/finishing/dying,
12798 bandwidth used, etc. The next step is to get some GUIs working.
12799 Let us know if you want to help out. See doc/control-spec.txt .
12800 - Ship a contrib/tor-control.py as an example script to interact
12801 with the control port.
12802 - "tor --hash-password zzyxz" will output a salted password for
12803 use in authenticating to the control interface.
12804 - New log format in config:
12805 "Log minsev[-maxsev] stdout|stderr|syslog" or
12806 "Log minsev[-maxsev] file /var/foo"
12809 - DirPolicy config option, to let people reject incoming addresses
12810 from their dirserver.
12811 - "tor --list-fingerprint" will list your identity key fingerprint
12813 - Add "pass" target for RedirectExit, to make it easier to break
12814 out of a sequence of RedirectExit rules.
12815 - Clients now generate a TLS cert too, in preparation for having
12816 them act more like real nodes.
12817 - Ship src/win32/ in the tarball, so people can use it to build.
12818 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
12820 - New "router-status" line in directory, to better bind each verified
12821 nickname to its identity key.
12822 - Deprecate unofficial config option abbreviations, and abbreviations
12823 not on the command line.
12824 - Add a pure-C tor-resolve implementation.
12825 - Use getrlimit and friends to ensure we can reach MaxConn (currently
12826 1024) file descriptors.
12828 o Code security improvements, inspired by Ilja:
12829 - Replace sprintf with snprintf. (I think they were all safe, but
12831 - Replace strcpy/strncpy with strlcpy in more places.
12832 - Avoid strcat; use snprintf or strlcat instead.
12833 - snprintf wrapper with consistent (though not C99) overflow behavior.
12836 Changes in version 0.0.9pre4 - 2004-10-17
12837 o Bugfixes on 0.0.9pre3:
12838 - If the server doesn't specify an exit policy, use the real default
12839 exit policy, not reject *:*.
12840 - Ignore fascistfirewall when uploading/downloading hidden service
12841 descriptors, since we go through Tor for those; and when using
12842 an HttpProxy, since we assume it can reach them all.
12843 - When looking for an authoritative dirserver, use only the ones
12844 configured at boot. Don't bother looking in the directory.
12845 - The rest of the fix for get_default_conf_file() on older win32.
12846 - Make 'Routerfile' config option obsolete.
12849 - New 'MyFamily nick1,...' config option for a server to
12850 specify other servers that shouldn't be used in the same circuit
12851 with it. Only believed if nick1 also specifies us.
12852 - New 'NodeFamily nick1,nick2,...' config option for a client to
12853 specify nodes that it doesn't want to use in the same circuit.
12854 - New 'Redirectexit pattern address:port' config option for a
12855 server to redirect exit connections, e.g. to a local squid.
12858 Changes in version 0.0.9pre3 - 2004-10-13
12859 o Bugfixes on 0.0.8.1:
12860 - Better torrc example lines for dirbindaddress and orbindaddress.
12861 - Improved bounds checking on parsed ints (e.g. config options and
12862 the ones we find in directories.)
12863 - Better handling of size_t vs int, so we're more robust on 64
12865 - Fix the rest of the bug where a newly started OR would appear
12866 as unverified even after we've added his fingerprint and hupped
12868 - Fix a bug from 0.0.7: when read() failed on a stream, we would
12869 close it without sending back an end. So 'connection refused'
12870 would simply be ignored and the user would get no response.
12872 o Bugfixes on 0.0.9pre2:
12873 - Serving the cached-on-disk directory to people is bad. We now
12874 provide no directory until we've fetched a fresh one.
12875 - Workaround for bug on windows where cached-directories get crlf
12877 - Make get_default_conf_file() work on older windows too.
12878 - If we write a *:* exit policy line in the descriptor, don't write
12879 any more exit policy lines.
12882 - Use only 0.0.9pre1 and later servers for resolve cells.
12883 - Make the dirservers file obsolete.
12884 - Include a dir-signing-key token in directories to tell the
12885 parsing entity which key is being used to sign.
12886 - Remove the built-in bulky default dirservers string.
12887 - New config option "Dirserver %s:%d [fingerprint]", which can be
12888 repeated as many times as needed. If no dirservers specified,
12889 default to moria1,moria2,tor26.
12890 - Make moria2 advertise a dirport of 80, so people behind firewalls
12891 will be able to get a directory.
12892 - Http proxy support
12893 - Dirservers translate requests for http://%s:%d/x to /x
12894 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
12895 be routed through this host.
12896 - Clients ask for /tor/x rather than /x for new enough dirservers.
12897 This way we can one day coexist peacefully with apache.
12898 - Clients specify a "Host: %s%d" http header, to be compatible
12899 with more proxies, and so running squid on an exit node can work.
12902 Changes in version 0.0.8.1 - 2004-10-13
12904 - Fix a seg fault that can be triggered remotely for Tor
12905 clients/servers with an open dirport.
12906 - Fix a rare assert trigger, where routerinfos for entries in
12907 our cpath would expire while we're building the path.
12908 - Fix a bug in OutboundBindAddress so it (hopefully) works.
12909 - Fix a rare seg fault for people running hidden services on
12910 intermittent connections.
12911 - Fix a bug in parsing opt keywords with objects.
12912 - Fix a stale pointer assert bug when a stream detaches and
12914 - Fix a string format vulnerability (probably not exploitable)
12915 in reporting stats locally.
12916 - Fix an assert trigger: sometimes launching circuits can fail
12917 immediately, e.g. because too many circuits have failed recently.
12918 - Fix a compile warning on 64 bit platforms.
12921 Changes in version 0.0.9pre2 - 2004-10-03
12923 - Make fetching a cached directory work for 64-bit platforms too.
12924 - Make zlib.h a required header, not an optional header.
12927 Changes in version 0.0.9pre1 - 2004-10-01
12929 - Stop using separate defaults for no-config-file and
12930 empty-config-file. Now you have to explicitly turn off SocksPort,
12931 if you don't want it open.
12932 - Fix a bug in OutboundBindAddress so it (hopefully) works.
12933 - Improve man page to mention more of the 0.0.8 features.
12934 - Fix a rare seg fault for people running hidden services on
12935 intermittent connections.
12936 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
12938 - Fix more dns related bugs: send back resolve_failed and end cells
12939 more reliably when the resolve fails, rather than closing the
12940 circuit and then trying to send the cell. Also attach dummy resolve
12941 connections to a circuit *before* calling dns_resolve(), to fix
12942 a bug where cached answers would never be sent in RESOLVED cells.
12943 - When we run out of disk space, or other log writing error, don't
12944 crash. Just stop logging to that log and continue.
12945 - We were starting to daemonize before we opened our logs, so if
12946 there were any problems opening logs, we would complain to stderr,
12947 which wouldn't work, and then mysteriously exit.
12948 - Fix a rare bug where sometimes a verified OR would connect to us
12949 before he'd uploaded his descriptor, which would cause us to
12950 assign conn->nickname as though he's unverified. Now we look through
12951 the fingerprint list to see if he's there.
12952 - Fix a rare assert trigger, where routerinfos for entries in
12953 our cpath would expire while we're building the path.
12956 - Clients can ask dirservers for /dir.z to get a compressed version
12957 of the directory. Only works for servers running 0.0.9, of course.
12958 - Make clients cache directories and use them to seed their router
12959 lists at startup. This means clients have a datadir again.
12960 - Configuration infrastructure support for warning on obsolete
12962 - Respond to content-encoding headers by trying to uncompress as
12964 - Reply with a deflated directory when a client asks for "dir.z".
12965 We could use allow-encodings instead, but allow-encodings isn't
12966 specified in HTTP 1.0.
12967 - Raise the max dns workers from 50 to 100.
12968 - Discourage people from setting their dirfetchpostperiod more often
12969 than once per minute.
12970 - Protect dirservers from overzealous descriptor uploading -- wait
12971 10 seconds after directory gets dirty, before regenerating.
12974 Changes in version 0.0.8 - 2004-08-25
12975 o Port it to SunOS 5.9 / Athena
12978 Changes in version 0.0.8rc2 - 2004-08-20
12979 o Make it compile on cygwin again.
12980 o When picking unverified routers, skip those with low uptime and/or
12981 low bandwidth, depending on what properties you care about.
12984 Changes in version 0.0.8rc1 - 2004-08-18
12985 o Changes from 0.0.7.3:
12987 - Fix assert triggers: if the other side returns an address 0.0.0.0,
12988 don't put it into the client dns cache.
12989 - If a begin failed due to exit policy, but we believe the IP address
12990 should have been allowed, switch that router to exitpolicy reject *:*
12991 until we get our next directory.
12993 - Clients choose nodes proportional to advertised bandwidth.
12994 - Avoid using nodes with low uptime as introduction points.
12995 - Handle servers with dynamic IP addresses: don't replace
12996 options->Address with the resolved one at startup, and
12997 detect our address right before we make a routerinfo each time.
12998 - 'FascistFirewall' option to pick dirservers and ORs on specific
12999 ports; plus 'FirewallPorts' config option to tell FascistFirewall
13000 which ports are open. (Defaults to 80,443)
13001 - Be more aggressive about trying to make circuits when the network
13002 has changed (e.g. when you unsuspend your laptop).
13003 - Check for time skew on http headers; report date in response to
13005 - If the entrynode config line has only one node, don't pick it as
13007 - Add strict{entry|exit}nodes config options. If set to 1, then
13008 we refuse to build circuits that don't include the specified entry
13010 - OutboundBindAddress config option, to bind to a specific
13011 IP address for outgoing connect()s.
13012 - End truncated log entries (e.g. directories) with "[truncated]".
13014 o Patches to 0.0.8preX:
13016 - Patches to compile and run on win32 again (maybe)?
13017 - Fix crash when looking for ~/.torrc with no $HOME set.
13018 - Fix a race bug in the unit tests.
13019 - Handle verified/unverified name collisions better when new
13020 routerinfo's arrive in a directory.
13021 - Sometimes routers were getting entered into the stats before
13022 we'd assigned their identity_digest. Oops.
13023 - Only pick and establish intro points after we've gotten a
13026 - AllowUnverifiedNodes config option to let circuits choose no-name
13027 routers in entry,middle,exit,introduction,rendezvous positions.
13028 Allow middle and rendezvous positions by default.
13029 - Add a man page for tor-resolve.
13032 Changes in version 0.0.7.3 - 2004-08-12
13033 o Stop dnsworkers from triggering an assert failure when you
13034 ask them to resolve the host "".
13037 Changes in version 0.0.8pre3 - 2004-08-09
13038 o Changes from 0.0.7.2:
13039 - Allow multiple ORs with same nickname in routerlist -- now when
13040 people give us one identity key for a nickname, then later
13041 another, we don't constantly complain until the first expires.
13042 - Remember used bandwidth (both in and out), and publish 15-minute
13043 snapshots for the past day into our descriptor.
13044 - You can now fetch $DIRURL/running-routers to get just the
13045 running-routers line, not the whole descriptor list. (But
13046 clients don't use this yet.)
13047 - When people mistakenly use Tor as an http proxy, point them
13048 at the tor-doc.html rather than the INSTALL.
13049 - Remove our mostly unused -- and broken -- hex_encode()
13050 function. Use base16_encode() instead. (Thanks to Timo Lindfors
13051 for pointing out this bug.)
13052 - Rotate onion keys every 12 hours, not every 2 hours, so we have
13053 fewer problems with people using the wrong key.
13054 - Change the default exit policy to reject the default edonkey,
13055 kazaa, gnutella ports.
13056 - Add replace_file() to util.[ch] to handle win32's rename().
13058 o Changes from 0.0.8preX:
13059 - Fix two bugs in saving onion keys to disk when rotating, so
13060 hopefully we'll get fewer people using old onion keys.
13061 - Fix an assert error that was making SocksPolicy not work.
13062 - Be willing to expire routers that have an open dirport -- it's
13063 just the authoritative dirservers we want to not forget.
13064 - Reject tor-resolve requests for .onion addresses early, so we
13065 don't build a whole rendezvous circuit and then fail.
13066 - When you're warning a server that he's unverified, don't cry
13067 wolf unpredictably.
13068 - Fix a race condition: don't try to extend onto a connection
13069 that's still handshaking.
13070 - For servers in clique mode, require the conn to be open before
13071 you'll choose it for your path.
13072 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
13073 end relay cell, etc.
13074 - Measure bandwidth capacity over the last 24 hours, not just 12
13075 - Bugfix: authoritative dirservers were making and signing a new
13076 directory for each client, rather than reusing the cached one.
13079 Changes in version 0.0.8pre2 - 2004-08-04
13080 o Changes from 0.0.7.2:
13082 - Check directory signature _before_ you decide whether you're
13083 you're running an obsolete version and should exit.
13084 - Check directory signature _before_ you parse the running-routers
13085 list to decide who's running or verified.
13086 - Bugfixes and features:
13087 - Check return value of fclose while writing to disk, so we don't
13088 end up with broken files when servers run out of disk space.
13089 - Log a warning if the user uses an unsafe socks variant, so people
13090 are more likely to learn about privoxy or socat.
13091 - Dirservers now include RFC1123-style dates in the HTTP headers,
13092 which one day we will use to better detect clock skew.
13094 o Changes from 0.0.8pre1:
13095 - Make it compile without warnings again on win32.
13096 - Log a warning if you're running an unverified server, to let you
13097 know you might want to get it verified.
13098 - Only pick a default nickname if you plan to be a server.
13101 Changes in version 0.0.8pre1 - 2004-07-23
13103 - Made our unit tests compile again on OpenBSD 3.5, and tor
13104 itself compile again on OpenBSD on a sparc64.
13105 - We were neglecting milliseconds when logging on win32, so
13106 everything appeared to happen at the beginning of each second.
13108 o Protocol changes:
13109 - 'Extend' relay cell payloads now include the digest of the
13110 intended next hop's identity key. Now we can verify that we're
13111 extending to the right router, and also extend to routers we
13112 hadn't heard of before.
13115 - Tor nodes can now act as relays (with an advertised ORPort)
13116 without being manually verified by the dirserver operators.
13117 - Uploaded descriptors of unverified routers are now accepted
13118 by the dirservers, and included in the directory.
13119 - Verified routers are listed by nickname in the running-routers
13120 list; unverified routers are listed as "$<fingerprint>".
13121 - We now use hash-of-identity-key in most places rather than
13122 nickname or addr:port, for improved security/flexibility.
13123 - To avoid Sybil attacks, paths still use only verified servers.
13124 But now we have a chance to play around with hybrid approaches.
13125 - Nodes track bandwidth usage to estimate capacity (not used yet).
13126 - ClientOnly option for nodes that never want to become servers.
13127 - Directory caching.
13128 - "AuthoritativeDir 1" option for the official dirservers.
13129 - Now other nodes (clients and servers) will cache the latest
13130 directory they've pulled down.
13131 - They can enable their DirPort to serve it to others.
13132 - Clients will pull down a directory from any node with an open
13133 DirPort, and check the signature/timestamp correctly.
13134 - Authoritative dirservers now fetch directories from other
13135 authdirservers, to stay better synced.
13136 - Running-routers list tells who's down also, along with noting
13137 if they're verified (listed by nickname) or unverified (listed
13139 - Allow dirservers to serve running-router list separately.
13140 This isn't used yet.
13141 - ORs connect-on-demand to other ORs
13142 - If you get an extend cell to an OR you're not connected to,
13143 connect, handshake, and forward the create cell.
13144 - The authoritative dirservers stay connected to everybody,
13145 and everybody stays connected to 0.0.7 servers, but otherwise
13146 clients/servers expire unused connections after 5 minutes.
13147 - When servers get a sigint, they delay 30 seconds (refusing new
13148 connections) then exit. A second sigint causes immediate exit.
13149 - File and name management:
13150 - Look for .torrc if no CONFDIR "torrc" is found.
13151 - If no datadir is defined, then choose, make, and secure ~/.tor
13153 - If torrc not found, exitpolicy reject *:*.
13154 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
13155 - If no nickname is defined, derive default from hostname.
13156 - Rename secret key files, e.g. identity.key -> secret_id_key,
13157 to discourage people from mailing their identity key to tor-ops.
13158 - Refuse to build a circuit before the directory has arrived --
13159 it won't work anyway, since you won't know the right onion keys
13161 - Try other dirservers immediately if the one you try is down. This
13162 should tolerate down dirservers better now.
13163 - Parse tor version numbers so we can do an is-newer-than check
13164 rather than an is-in-the-list check.
13165 - New socks command 'resolve', to let us shim gethostbyname()
13167 - A 'tor_resolve' script to access the socks resolve functionality.
13168 - A new socks-extensions.txt doc file to describe our
13169 interpretation and extensions to the socks protocols.
13170 - Add a ContactInfo option, which gets published in descriptor.
13171 - Publish OR uptime in descriptor (and thus in directory) too.
13172 - Write tor version at the top of each log file
13173 - New docs in the tarball:
13175 - Document that you should proxy your SSL traffic too.
13178 Changes in version 0.0.7.2 - 2004-07-07
13179 o A better fix for the 0.0.0.0 problem, that will hopefully
13180 eliminate the remaining related assertion failures.
13183 Changes in version 0.0.7.1 - 2004-07-04
13184 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
13185 since internally we use 0.0.0.0 to signify "not yet resolved".
13188 Changes in version 0.0.7 - 2004-06-07
13189 o Updated the man page to reflect the new features.
13192 Changes in version 0.0.7rc2 - 2004-06-06
13193 o Changes from 0.0.7rc1:
13194 - Make it build on Win32 again.
13195 o Changes from 0.0.6.2:
13196 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
13200 Changes in version 0.0.7rc1 - 2004-06-02
13202 - On sighup, we were adding another log without removing the first
13203 one. So log messages would get duplicated n times for n sighups.
13204 - Several cases of using a connection after we'd freed it. The
13205 problem was that connections that are pending resolve are in both
13206 the pending_resolve tree, and also the circuit's resolving_streams
13207 list. When you want to remove one, you must remove it from both.
13208 - Fix a double-mark-for-close where an end cell arrived for a
13209 resolving stream, and then the resolve failed.
13210 - Check directory signatures based on name of signer, not on whom
13211 we got the directory from. This will let us cache directories more
13214 - Crank up some of our constants to handle more users.
13217 Changes in version 0.0.7pre1 - 2004-06-02
13218 o Fixes for crashes and other obnoxious bugs:
13219 - Fix an epipe bug: sometimes when directory connections failed
13220 to connect, we would give them a chance to flush before closing
13222 - When we detached from a circuit because of resolvefailed, we
13223 would immediately try the same circuit twice more, and then
13224 give up on the resolve thinking we'd tried three different
13226 - Limit the number of intro circuits we'll attempt to build for a
13227 hidden service per 15-minute period.
13228 - Check recommended-software string *early*, before actually parsing
13229 the directory. Thus we can detect an obsolete version and exit,
13230 even if the new directory format doesn't parse.
13231 o Fixes for security bugs:
13232 - Remember which nodes are dirservers when you startup, and if a
13233 random OR enables his dirport, don't automatically assume he's
13234 a trusted dirserver.
13236 - Directory connections were asking the wrong poll socket to
13237 start writing, and not asking themselves to start writing.
13238 - When we detached from a circuit because we sent a begin but
13239 didn't get a connected, we would use it again the first time;
13240 but after that we would correctly switch to a different one.
13241 - Stop warning when the first onion decrypt attempt fails; they
13242 will sometimes legitimately fail now that we rotate keys.
13243 - Override unaligned-access-ok check when $host_cpu is ia64 or
13244 arm. Apparently they allow it but the kernel whines.
13245 - Dirservers try to reconnect periodically too, in case connections
13247 - Fix some memory leaks in directory servers.
13248 - Allow backslash in Win32 filenames.
13249 - Made Tor build complain-free on FreeBSD, hopefully without
13250 breaking other BSD builds. We'll see.
13252 - Doxygen markup on all functions and global variables.
13253 - Make directory functions update routerlist, not replace it. So
13254 now directory disagreements are not so critical a problem.
13255 - Remove the upper limit on number of descriptors in a dirserver's
13256 directory (not that we were anywhere close).
13257 - Allow multiple logfiles at different severity ranges.
13258 - Allow *BindAddress to specify ":port" rather than setting *Port
13259 separately. Allow multiple instances of each BindAddress config
13260 option, so you can bind to multiple interfaces if you want.
13261 - Allow multiple exit policy lines, which are processed in order.
13262 Now we don't need that huge line with all the commas in it.
13263 - Enable accept/reject policies on SOCKS connections, so you can bind
13264 to 0.0.0.0 but still control who can use your OP.
13267 Changes in version 0.0.6.2 - 2004-05-16
13268 o Our integrity-checking digest was checking only the most recent cell,
13269 not the previous cells like we'd thought.
13270 Thanks to Stefan Mark for finding the flaw!
13273 Changes in version 0.0.6.1 - 2004-05-06
13274 o Fix two bugs in our AES counter-mode implementation (this affected
13275 onion-level stream encryption, but not TLS-level). It turns
13276 out we were doing something much more akin to a 16-character
13277 polyalphabetic cipher. Oops.
13278 Thanks to Stefan Mark for finding the flaw!
13279 o Retire moria3 as a directory server, and add tor26 as a directory
13283 Changes in version 0.0.6 - 2004-05-02
13284 [version bump only]
13287 Changes in version 0.0.6rc4 - 2004-05-01
13288 o Update the built-in dirservers list to use the new directory format
13289 o Fix a rare seg fault: if a node offering a hidden service attempts
13290 to build a circuit to Alice's rendezvous point and fails before it
13291 reaches the last hop, it retries with a different circuit, but
13293 o Handle windows socket errors correctly.
13296 Changes in version 0.0.6rc3 - 2004-04-28
13297 o Don't expire non-general excess circuits (if we had enough
13298 circuits open, we were expiring rendezvous circuits -- even
13299 when they had a stream attached. oops.)
13300 o Fetch randomness from /dev/urandom better (not via fopen/fread)
13301 o Better debugging for tls errors
13302 o Some versions of openssl have an SSL_pending function that erroneously
13303 returns bytes when there is a non-application record pending.
13304 o Set Content-Type on the directory and hidserv descriptor.
13305 o Remove IVs from cipher code, since AES-ctr has none.
13306 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
13307 o We were using an array of length zero in a few places.
13308 o win32's gethostbyname can't resolve an IP to an IP.
13309 o win32's close can't close a socket.
13312 Changes in version 0.0.6rc2 - 2004-04-26
13313 o Fix a bug where we were closing tls connections intermittently.
13314 It turns out openssl keeps its errors around -- so if an error
13315 happens, and you don't ask about it, and then another openssl
13316 operation happens and succeeds, and you ask if there was an error,
13317 it tells you about the first error. Fun fun.
13318 o Fix a bug that's been lurking since 27 may 03 (!)
13319 When passing back a destroy cell, we would use the wrong circ id.
13320 'Mostly harmless', but still worth fixing.
13321 o Since we don't support truncateds much, don't bother sending them;
13322 just close the circ.
13323 o check for <machine/limits.h> so we build on NetBSD again (I hope).
13324 o don't crash if a conn that sent a begin has suddenly lost its circuit
13325 (this was quite rare).
13328 Changes in version 0.0.6rc1 - 2004-04-25
13329 o We now rotate link (tls context) keys and onion keys.
13330 o CREATE cells now include oaep padding, so you can tell
13331 if you decrypted them correctly.
13332 o Add bandwidthburst to server descriptor.
13333 o Directories now say which dirserver signed them.
13334 o Use a tor_assert macro that logs failed assertions too.
13337 Changes in version 0.0.6pre5 - 2004-04-18
13338 o changes from 0.0.6pre4:
13339 - make tor build on broken freebsd 5.2 installs
13340 - fix a failed assert when you try an intro point, get a nack, and try
13341 a second one and it works.
13342 - when alice uses a port that the hidden service doesn't accept,
13343 it now sends back an end cell (denied by exit policy). otherwise
13344 alice would just have to wait to time out.
13345 - fix another rare bug: when we had tried all the intro
13346 points for a hidden service, we fetched the descriptor
13347 again, but we left our introcirc thinking it had already
13348 sent an intro, so it kept waiting for a response...
13349 - bugfix: when you sleep your hidden-service laptop, as soon
13350 as it wakes up it tries to upload a service descriptor, but
13351 socketpair fails for some reason (localhost not up yet?).
13352 now we simply give up on that upload, and we'll try again later.
13353 i'd still like to find the bug though.
13354 - if an intro circ waiting for an ack dies before getting one, then
13356 - we were reusing stale service descriptors and refetching usable
13360 Changes in version 0.0.6pre4 - 2004-04-14
13361 o changes from 0.0.6pre3:
13362 - when bob fails to connect to the rendezvous point, and his
13363 circ didn't fail because of the rendezvous point itself, then
13364 he retries a couple of times
13365 - we expire introduction and rendezvous circs more thoroughly
13366 (sometimes they were hanging around forever)
13367 - we expire unattached rendezvous streams that have been around
13368 too long (they were sticking around forever).
13369 - fix a measly fencepost error that was crashing everybody with
13373 Changes in version 0.0.6pre3 - 2004-04-14
13374 o changes from 0.0.6pre2:
13375 - make hup work again
13376 - fix some memory leaks for dirservers
13377 - allow more skew in rendezvous descriptor timestamps, to help
13378 handle people like blanu who don't know what time it is
13379 - normal circs are 3 hops, but some rend/intro circs are 4, if
13380 the initiator doesn't get to choose the last hop
13381 - send acks for introductions, so alice can know whether to try
13383 - bob publishes intro points more correctly
13384 o changes from 0.0.5:
13385 - fix an assert trigger that's been plaguing us since the days
13386 of 0.0.2prexx (thanks weasel!)
13387 - retry stream correctly when we fail to connect because of
13388 exit-policy-reject (should try another) or can't-resolve-address
13389 (also should try another, because dns on random internet servers
13391 - when we hup a dirserver and we've *removed* a server from the
13392 approved-routers list, now we remove that server from the
13393 in-memory directories too
13396 Changes in version 0.0.6pre2 - 2004-04-08
13397 o We fixed our base32 implementation. Now it works on all architectures.
13400 Changes in version 0.0.6pre1 - 2004-04-08
13402 - Hidden services and rendezvous points are implemented. Go to
13403 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
13404 hidden services. (This only works via a socks4a proxy such as
13405 Privoxy, and currently it's quite slow.)
13408 Changes in version 0.0.5 - 2004-03-30
13409 [version bump only]
13412 Changes in version 0.0.5rc3 - 2004-03-29
13413 o Install torrc as torrc.sample -- we no longer clobber your
13415 o Re-enable recommendedversion checking (we broke it in rc2, oops)
13416 o Add in a 'notice' log level for things the operator should hear
13417 but that aren't warnings
13420 Changes in version 0.0.5rc2 - 2004-03-29
13421 o Hold socks connection open until reply is flushed (if possible)
13422 o Make exit nodes resolve IPs to IPs immediately, rather than asking
13423 the dns farm to do it.
13424 o Fix c99 aliasing warnings in rephist.c
13425 o Don't include server descriptors that are older than 24 hours in the
13427 o Give socks 'reject' replies their whole 15s to attempt to flush,
13428 rather than seeing the 60s timeout and assuming the flush had failed.
13429 o Clean automake droppings from the cvs repository
13432 Changes in version 0.0.5rc1 - 2004-03-28
13433 o Fix mangled-state bug in directory fetching (was causing sigpipes).
13434 o Only build circuits after we've fetched the directory: clients were
13435 using only the directory servers before they'd fetched a directory.
13436 This also means longer startup time; so it goes.
13437 o Fix an assert trigger where an OP would fail to handshake, and we'd
13438 expect it to have a nickname.
13439 o Work around a tsocks bug: do a socks reject when AP connection dies
13440 early, else tsocks goes into an infinite loop.
13443 Changes in version 0.0.4 - 2004-03-26
13444 o When connecting to a dirserver or OR and the network is down,
13448 Changes in version 0.0.3 - 2004-03-26
13449 o Warn and fail if server chose a nickname with illegal characters
13450 o Port to Solaris and Sparc:
13451 - include missing header fcntl.h
13452 - have autoconf find -lsocket -lnsl automatically
13453 - deal with hardware word alignment
13454 - make uname() work (solaris has a different return convention)
13455 - switch from using signal() to sigaction()
13456 o Preliminary work on reputation system:
13457 - Keep statistics on success/fail of connect attempts; they're published
13458 by kill -USR1 currently.
13459 - Add a RunTesting option to try to learn link state by creating test
13460 circuits, even when SocksPort is off.
13461 - Remove unused open circuits when there are too many.
13464 Changes in version 0.0.2 - 2004-03-19
13465 - Include strlcpy and strlcat for safer string ops
13466 - define INADDR_NONE so we compile (but still not run) on solaris
13469 Changes in version 0.0.2pre27 - 2004-03-14
13471 - Allow internal tor networks (we were rejecting internal IPs,
13472 now we allow them if they're set explicitly).
13473 - And fix a few endian issues.
13476 Changes in version 0.0.2pre26 - 2004-03-14
13478 - If a stream times out after 15s without a connected cell, don't
13479 try that circuit again: try a new one.
13480 - Retry streams at most 4 times. Then give up.
13481 - When a dirserver gets a descriptor from an unknown router, it
13482 logs its fingerprint (so the dirserver operator can choose to
13483 accept it even without mail from the server operator).
13484 - Inform unapproved servers when we reject their descriptors.
13485 - Make tor build on Windows again. It works as a client, who knows
13487 - Clearer instructions in the torrc for how to set up a server.
13488 - Be more efficient about reading fd's when our global token bucket
13489 (used for rate limiting) becomes empty.
13491 - Stop asserting that computers always go forward in time. It's
13493 - When we sent a cell (e.g. destroy) and then marked an OR connection
13494 expired, we might close it before finishing a flush if the other
13495 side isn't reading right then.
13496 - Don't allow dirservers to start if they haven't defined
13497 RecommendedVersions
13498 - We were caching transient dns failures. Oops.
13499 - Prevent servers from publishing an internal IP as their address.
13500 - Address a strcat vulnerability in circuit.c
13503 Changes in version 0.0.2pre25 - 2004-03-04
13505 - Put the OR's IP in its router descriptor, not its fqdn. That way
13506 we'll stop being stalled by gethostbyname for nodes with flaky dns,
13509 - If the user typed in an address that didn't resolve, the server
13513 Changes in version 0.0.2pre24 - 2004-03-03
13515 - Fix an assertion failure in dns.c, where we were trying to dequeue
13516 a pending dns resolve even if it wasn't pending
13517 - Fix a spurious socks5 warning about still trying to write after the
13518 connection is finished.
13519 - Hold certain marked_for_close connections open until they're finished
13520 flushing, rather than losing bytes by closing them too early.
13521 - Correctly report the reason for ending a stream
13522 - Remove some duplicate calls to connection_mark_for_close
13523 - Put switch_id and start_daemon earlier in the boot sequence, so it
13524 will actually try to chdir() to options.DataDirectory
13525 - Make 'make test' exit(1) if a test fails; fix some unit tests
13526 - Make tor fail when you use a config option it doesn't know about,
13527 rather than warn and continue.
13528 - Make --version work
13529 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
13532 Changes in version 0.0.2pre23 - 2004-02-29
13534 - Print a statement when the first circ is finished, so the user
13535 knows it's working.
13536 - If a relay cell is unrecognized at the end of the circuit,
13537 send back a destroy. (So attacks to mutate cells are more
13539 - New config option 'excludenodes' to avoid certain nodes for circuits.
13540 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
13541 so you can collect coredumps there.
13543 - Fix a bug in tls flushing where sometimes data got wedged and
13544 didn't flush until more data got sent. Hopefully this bug was
13545 a big factor in the random delays we were seeing.
13546 - Make 'connected' cells include the resolved IP, so the client
13547 dns cache actually gets populated.
13548 - Disallow changing from ORPort=0 to ORPort>0 on hup.
13549 - When we time-out on a stream and detach from the circuit, send an
13550 end cell down it first.
13551 - Only warn about an unknown router (in exitnodes, entrynodes,
13552 excludenodes) after we've fetched a directory.
13555 Changes in version 0.0.2pre22 - 2004-02-26
13557 - Servers publish less revealing uname information in descriptors.
13558 - More memory tracking and assertions, to crash more usefully when
13560 - If the default torrc isn't there, just use some default defaults.
13561 Plus provide an internal dirservers file if they don't have one.
13562 - When the user tries to use Tor as an http proxy, give them an http
13563 501 failure explaining that we're a socks proxy.
13564 - Dump a new router.desc on hup, to help confused people who change
13565 their exit policies and then wonder why router.desc doesn't reflect
13567 - Clean up the generic tor.sh init script that we ship with.
13569 - If the exit stream is pending on the resolve, and a destroy arrives,
13570 then the stream wasn't getting removed from the pending list. I
13571 think this was the one causing recent server crashes.
13572 - Use a more robust poll on OSX 10.3, since their poll is flaky.
13573 - When it couldn't resolve any dirservers, it was useless from then on.
13574 Now it reloads the RouterFile (or default dirservers) if it has no
13576 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
13577 many users don't even *have* a /usr/local/sbin/.
13580 Changes in version 0.0.2pre21 - 2004-02-18
13582 - There's a ChangeLog file that actually reflects the changelog.
13583 - There's a 'torify' wrapper script, with an accompanying
13584 tor-tsocks.conf, that simplifies the process of using tsocks for
13585 tor. It even has a man page.
13586 - The tor binary gets installed to sbin rather than bin now.
13587 - Retry streams where the connected cell hasn't arrived in 15 seconds
13588 - Clean up exit policy handling -- get the default out of the torrc,
13589 so we can update it without forcing each server operator to fix
13591 - Allow imaps and pop3s in default exit policy
13593 - Prevent picking middleman nodes as the last node in the circuit
13596 Changes in version 0.0.2pre20 - 2004-01-30
13598 - We now have a deb package, and it's in debian unstable. Go to
13599 it, apt-getters. :)
13600 - I've split the TotalBandwidth option into BandwidthRate (how many
13601 bytes per second you want to allow, long-term) and
13602 BandwidthBurst (how many bytes you will allow at once before the cap
13603 kicks in). This better token bucket approach lets you, say, set
13604 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
13605 performance while not exceeding your monthly bandwidth quota.
13606 - Push out a tls record's worth of data once you've got it, rather
13607 than waiting until you've read everything waiting to be read. This
13608 may improve performance by pipelining better. We'll see.
13609 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
13610 from failed circuits (if they haven't been connected yet) and attach
13612 - Expire old streams that haven't managed to connect. Some day we'll
13613 have them reattach to new circuits instead.
13616 - Fix several memory leaks that were causing servers to become bloated
13618 - Fix a few very rare assert triggers. A few more remain.
13619 - Setuid to User _before_ complaining about running as root.
13622 Changes in version 0.0.2pre19 - 2004-01-07
13624 - Fix deadlock condition in dns farm. We were telling a child to die by
13625 closing the parent's file descriptor to him. But newer children were
13626 inheriting the open file descriptor from the parent, and since they
13627 weren't closing it, the socket never closed, so the child never read
13628 eof, so he never knew to exit. Similarly, dns workers were holding
13629 open other sockets, leading to all sorts of chaos.
13630 - New cleaner daemon() code for forking and backgrounding.
13631 - If you log to a file, it now prints an entry at the top of the
13632 logfile so you know it's working.
13633 - The onionskin challenge length was 30 bytes longer than necessary.
13634 - Started to patch up the spec so it's not quite so out of date.
13637 Changes in version 0.0.2pre18 - 2004-01-02
13639 - Fix endian issues with the 'integrity' field in the relay header.
13640 - Fix a potential bug where connections in state
13641 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
13644 Changes in version 0.0.2pre17 - 2003-12-30
13646 - Made --debuglogfile (or any second log file, actually) work.
13647 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
13648 adversary could force us into an infinite loop.
13651 - Each onionskin handshake now includes a hash of the computed key,
13652 to prove the server's identity and help perfect forward secrecy.
13653 - Changed cell size from 256 to 512 bytes (working toward compatibility
13655 - Changed cell length to 2 bytes, and moved it to the relay header.
13656 - Implemented end-to-end integrity checking for the payloads of
13658 - Separated streamid from 'recognized' (otherwise circuits will get
13659 messed up when we try to have streams exit from the middle). We
13660 use the integrity-checking to confirm that a cell is addressed to
13662 - Randomize the initial circid and streamid values, so an adversary who
13663 breaks into a node can't learn how many circuits or streams have
13667 Changes in version 0.0.2pre16 - 2003-12-14
13669 - Fixed a bug that made HUP trigger an assert
13670 - Fixed a bug where a circuit that immediately failed wasn't being
13671 counted as a failed circuit in counting retries.
13674 - Now we close the circuit when we get a truncated cell: otherwise we're
13675 open to an anonymity attack where a bad node in the path truncates
13676 the circuit and then we open streams at him.
13677 - Add port ranges to exit policies
13678 - Add a conservative default exit policy
13679 - Warn if you're running tor as root
13680 - on HUP, retry OR connections and close/rebind listeners
13681 - options.EntryNodes: try these nodes first when picking the first node
13682 - options.ExitNodes: if your best choices happen to include any of
13683 your preferred exit nodes, you choose among just those preferred
13685 - options.ExcludedNodes: nodes that are never picked in path building
13688 Changes in version 0.0.2pre15 - 2003-12-03
13689 o Robustness and bugfixes:
13690 - Sometimes clients would cache incorrect DNS resolves, which would
13691 really screw things up.
13692 - An OP that goes offline would slowly leak all its sockets and stop
13694 - A wide variety of bugfixes in exit node selection, exit policy
13695 handling, and processing pending streams when a new circuit is
13697 - Pick nodes for a path only from those the directory says are up
13698 - Choose randomly from all running dirservers, not always the first one
13699 - Increase allowed http header size for directory fetch.
13700 - Stop writing to stderr (if we're daemonized it will be closed).
13701 - Enable -g always, so cores will be more useful to me.
13702 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
13705 - Wrote a man page. It lists commonly used options.
13708 - Change default loglevel to warn.
13709 - Make PidFile default to null rather than littering in your CWD.
13710 - OnionRouter config option is now obsolete. Instead it just checks
13712 - Moved to a single unified torrc file for both clients and servers.
13715 Changes in version 0.0.2pre14 - 2003-11-29
13716 o Robustness and bugfixes:
13717 - Force the admin to make the DataDirectory himself
13718 - to get ownership/permissions right
13719 - so clients no longer make a DataDirectory and then never use it
13720 - fix bug where a client who was offline for 45 minutes would never
13721 pull down a directory again
13722 - fix (or at least hide really well) the dns assert bug that was
13723 causing server crashes
13724 - warnings and improved robustness wrt clockskew for certs
13725 - use the native daemon(3) to daemonize, when available
13726 - exit if bind() fails
13727 - exit if neither socksport nor orport is defined
13728 - include our own tor_timegm (Win32 doesn't have its own)
13729 - bugfix for win32 with lots of connections
13730 - fix minor bias in PRNG
13731 - make dirserver more robust to corrupt cached directory
13734 - Wrote the design document (woo)
13736 o Circuit building and exit policies:
13737 - Circuits no longer try to use nodes that the directory has told them
13739 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
13740 bitcounts (18.0.0.0/8).
13741 - Make AP connections standby for a circuit if no suitable circuit
13742 exists, rather than failing
13743 - Circuits choose exit node based on addr/port, exit policies, and
13744 which AP connections are standing by
13745 - Bump min pathlen from 2 to 3
13746 - Relay end cells have a payload to describe why the stream ended.
13747 - If the stream failed because of exit policy, try again with a new
13749 - Clients have a dns cache to remember resolved addresses.
13750 - Notice more quickly when we have no working circuits
13753 - APPort is now called SocksPort
13754 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
13756 - RecommendedVersions is now a config variable rather than
13757 hardcoded (for dirservers)
13758 - Reloads config on HUP
13759 - Usage info on -h or --help
13760 - If you set User and Group config vars, it'll setu/gid to them.
13763 Changes in version 0.0.2pre13 - 2003-10-19
13764 o General stability:
13765 - SSL_write no longer fails when it returns WANTWRITE and the number
13766 of bytes in the buf has changed by the next SSL_write call.
13767 - Fix segfault fetching directory when network is down
13768 - Fix a variety of minor memory leaks
13769 - Dirservers reload the fingerprints file on HUP, so I don't have
13770 to take down the network when I approve a new router
13771 - Default server config file has explicit Address line to specify fqdn
13774 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
13775 - Make listener connections not ever alloc bufs
13777 o Autoconf improvements:
13778 - don't clobber an external CFLAGS in ./configure
13779 - Make install now works
13780 - create var/lib/tor on make install
13781 - autocreate a tor.sh initscript to help distribs
13782 - autocreate the torrc and sample-server-torrc with correct paths
13784 o Log files and Daemonizing now work:
13785 - If --DebugLogFile is specified, log to it at -l debug
13786 - If --LogFile is specified, use it instead of commandline
13787 - If --RunAsDaemon is set, tor forks and backgrounds on startup