1 Changes in version 0.2.4.3-alpha - 2012-09-??
3 - Fix an assertion failure in tor_timegm() that could be triggered
4 by a badly formatted directory object. Bug found by fuzzing with
5 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
8 - Fix a possible crash bug when checking for deactivated circuits
9 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
10 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
11 - Allow routers to detect that their own DirPorts are running. When
12 we removed support for versions_supports_begindir, we also
13 accidentally removed the mechanism we used to self-test our
14 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
15 bugfix on 0.2.4.2-alpha.
18 - Switch to a completely time-invariant approach for picking nodes
19 weighted by bandwidth. Our old approach would run through the
20 part of the loop after it had made its choice slightly slower
21 than it ran through the part of the loop before it had made its
22 choice. Addresses ticket 6538.
25 - Correct file sizes when reading binary files on Cygwin, to avoid
26 a bug where Tor would fail to read its state file. Fixes bug 6844;
27 bugfix on 0.1.2.7-alpha.
28 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
29 with large values. This situation was untriggered, but nevertheless
30 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
31 - Reject consensus votes with more than 64 known-flags. We aren't even
32 close to that limit yet, and our code doesn't handle it correctly.
33 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
34 - Avoid undefined behaviour when parsing the list of supported
35 rendezvous/introduction protocols in a hidden service descriptor.
36 Previously, Tor would have confused (as-yet-unused) protocol version
37 numbers greater than 32 with lower ones on many platforms. Fixes
38 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
39 - Fix building with older versions of GCC (2.95, for one) that don't
40 like preprocessor directives inside macro arguments. Found by
41 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
42 - Switch weighted node selection rule from using a list of doubles
43 to using a list of int64_t. This change should make the process
44 slightly easier to debug and maintain. Needed to finish ticket 6538.
46 o Code simplification and refactoring:
47 - Move the generic "config" code into a new file, and have "config.c"
48 hold only torrc- and state-related code. Resolves ticket 6823.
49 - Move the core of our "choose a weighted element at random" logic
50 into its own function, and give it unit tests. Now the logic is
51 testable, and a little less fragile too.
53 o Documentation fixes:
54 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
58 Changes in version 0.2.3.22-rc - 2012-09-11
59 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
63 - Fix an assertion failure in tor_timegm() that could be triggered
64 by a badly formatted directory object. Bug found by fuzzing with
65 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
68 - Avoid segfault when starting up having run with an extremely old
69 version of Tor and parsing its state file. Fixes bug 6801; bugfix
73 Changes in version 0.2.2.39 - 2012-09-11
74 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
78 - Fix an assertion failure in tor_timegm() that could be triggered
79 by a badly formatted directory object. Bug found by fuzzing with
80 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
81 - Do not crash when comparing an address with port value 0 to an
82 address policy. This bug could have been used to cause a remote
83 assertion failure by or against directory authorities, or to
84 allow some applications to crash clients. Fixes bug 6690; bugfix
88 Changes in version 0.2.4.2-alpha - 2012-09-10
89 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
90 raises the default rate limiting even more, and makes the bootstrapping
91 log messages less noisy.
94 - Automatically forward the TCP ports of pluggable transport
95 proxies using tor-fw-helper if PortForwarding is enabled. Implements
99 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
100 to 1GB/1GB. The previous defaults were intended to be "basically
101 infinite", but it turns out they're now limiting our 100mbit+
102 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
103 last time we raised it).
106 - Detect when we're running with a version of OpenSSL other than the
107 one we compiled with. This has occasionally given people hard-to-
109 - Log fewer lines at level "notice" about our OpenSSL and Libevent
110 versions and capabilities when everything is going right. Resolves
112 - Directory authorities no long accept descriptors for any version of
113 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
114 These versions are insecure, unsupported, or both. Implements
118 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
119 to start with a triple-underscore so the controller won't touch it.
120 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
121 - Avoid segfault when starting up having run with an extremely old
122 version of Tor and parsing its state file. Fixes bug 6801; bugfix
124 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
125 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
126 - Don't follow the NULL pointer if microdescriptor generation fails.
127 (This does not appear to be triggerable, but it's best to be safe.)
128 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
129 - Fix mis-declared dependencies on src/common/crypto.c and
130 src/or/tor_main.c that could break out-of-tree builds under some
131 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
132 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
133 6778; bugfix on 0.2.4.1-alpha.
134 - Fix a harmless (in this case) build warning for implicitly
135 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
138 - Now that all versions before 0.2.2.x are disallowed, we no longer
139 need to work around their missing features. Thus we can remove a
140 bunch of compatibility code.
143 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
144 TCP ports to forward. In the past it only accepted two ports:
145 the ORPort and the DirPort.
148 Changes in version 0.2.4.1-alpha - 2012-09-05
149 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
150 bridgedb; lets relays use IPv6 addresses and directory authorities
151 advertise them; and switches to a cleaner build interface.
153 This is the first alpha release in a new series, so expect there to
154 be bugs. Users who would rather test out a more stable branch should
155 stay with 0.2.3.x for now.
157 o Major features (bridges):
158 - Bridges now report the pluggable transports they support to the
159 bridge authority, so it can pass the supported transports on to
160 bridgedb and/or eventually do reachability testing. Implements
163 o Major features (IPv6):
164 - Bridge authorities now accept IPv6 bridge addresses and include
165 them in network status documents. Implements ticket 5534.
166 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
167 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
168 to happen. Implements ticket 5535.
169 - All kind of relays, not just bridges, can now advertise an IPv6
170 OR port. Implements ticket 6362.
171 - Directory authorities vote on IPv6 OR ports using the new consensus
172 method 14. Implements ticket 6363.
174 o Major features (build):
175 - Switch to a nonrecursive Makefile structure. Now instead of each
176 Makefile.am invoking other Makefile.am's, there is a master
177 Makefile.am that includes the others. This change makes our build
178 process slightly more maintainable, and improves parallelism for
179 building with make -j. Original patch by Stewart Smith; various
180 fixes by Jim Meyering.
181 - Where available, we now use automake's "silent" make rules by
182 default, so that warnings are easier to spot. You can get the old
183 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
185 o Minor features (code security and spec conformance):
186 - Clear keys and key-derived material left on the stack in
187 rendservice.c and rendclient.c. Check return value of
188 crypto_pk_write_private_key_to_string() in end_service_load_keys().
189 These fixes should make us more forward-secure against cold-boot
190 attacks and the like. Fixes bug 2385.
191 - Reject EXTEND cells sent to nonexistent streams. According to the
192 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
193 we were only checking for stream IDs that were currently in use.
194 Found while hunting for more instances of bug 6271. Bugfix on
195 0.0.2pre8, which introduced incremental circuit construction.
197 o Minor features (streamlining);
198 - No longer include the "opt" prefix when generating routerinfos
199 or v2 directories: it has been needless since Tor 0.1.2. Closes
201 - Remove some now-needless code that tried to aggressively flush
202 OR connections as data was added to them. Since 0.2.0.1-alpha, our
203 cell queue logic has saved us from the failure mode that this code
204 was supposed to prevent. Removing this code will limit the number
205 of baroque control flow paths through Tor's network logic. Reported
206 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
208 o Minor features (controller):
209 - Add a "GETINFO signal/names" control port command. Implements
211 - Provide default values for all options via "GETINFO config/defaults".
212 Implements ticket 4971.
214 o Minor features (IPv6):
215 - New config option "AuthDirHasIPv6Connectivity 1" that directory
216 authorities should set if they have IPv6 connectivity and want to
217 do reachability tests for IPv6 relays. Implements feature 5974.
218 - A relay with an IPv6 OR port now sends that address in NETINFO
219 cells (in addition to its other address). Implements ticket 6364.
221 o Minor features (log messages):
222 - Omit the first heartbeat log message, because it never has anything
223 useful to say, and it clutters up the bootstrapping messages.
224 Resolves ticket 6758.
225 - Don't log about reloading the microdescriptor cache at startup. Our
226 bootstrap warnings are supposed to tell the user when there's a
227 problem, and our bootstrap notices say when there isn't. Resolves
228 ticket 6759; bugfix on 0.2.2.6-alpha.
229 - Don't log "I learned some more directory information" when we're
230 reading cached directory information. Reserve it for when new
231 directory information arrives in response to a fetch. Resolves
233 - Prevent rounding error in path bias counts when scaling
234 them down, and use the correct scale factor default. Also demote
235 some path bias related log messages down a level and make others
236 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
237 - We no longer warn so much when generating manpages from their
240 o Code simplifications and refactoring:
241 - Enhance our internal sscanf replacement so that we can eliminate
242 the last remaining uses of the system sscanf. (Though those uses
243 of sscanf were safe, sscanf itself is generally error prone, so
244 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
246 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
247 - Move last_reachable and testing_since from routerinfo_t to node_t.
248 Implements ticket 5529.
249 - Add replaycache_t structure, functions and unit tests, then refactor
250 rend_service_introduce() to be more clear to read, improve, debug,
251 and test. Resolves bug 6177.
252 - Finally remove support for malloc_good_size and malloc_usable_size.
253 We had hoped that these functions would let us eke a little more
254 memory out of our malloc implementation. Unfortunately, the only
255 implementations that provided these functions are also ones that
256 are already efficient about not overallocation: they never got us
257 more than 7 or so bytes per allocation. Removing them saves us a
258 little code complexity and a nontrivial amount of build complexity.
261 - Tor maintainers now require Automake version 1.9 or later to build
262 Tor from the Git repository. (Automake is not required when building
263 from a source distribution.)
266 Changes in version 0.2.3.21-rc - 2012-09-05
267 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
268 series. It fixes a trio of potential security bugs, fixes a bug where
269 we were leaving some of the fast relays out of the microdescriptor
270 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
271 and cleans up other smaller issues.
273 o Major bugfixes (security):
274 - Tear down the circuit if we get an unexpected SENDME cell. Clients
275 could use this trick to make their circuits receive cells faster
276 than our flow control would have allowed, or to gum up the network,
277 or possibly to do targeted memory denial-of-service attacks on
278 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
279 from July 2002, before the release of Tor 0.0.0. We had committed
280 this patch previously, but we had to revert it because of bug 6271.
281 Now that 6271 is fixed, this patch appears to work.
282 - Reject any attempt to extend to an internal address. Without
283 this fix, a router could be used to probe addresses on an internal
284 network to see whether they were accepting connections. Fixes bug
285 6710; bugfix on 0.0.8pre1.
286 - Do not crash when comparing an address with port value 0 to an
287 address policy. This bug could have been used to cause a remote
288 assertion failure by or against directory authorities, or to
289 allow some applications to crash clients. Fixes bug 6690; bugfix
293 - Remove the upper bound on microdescriptor length. We were hitting
294 the limit for routers with complex exit policies or family
295 declarations, causing clients to not use them. Fixes the first
296 piece of bug 6404; fix on 0.2.2.6-alpha.
297 - Detect "ORPort 0" as meaning, uniformly, that we're not running
298 as a relay. Previously, some of our code would treat the presence
299 of any ORPort line as meaning that we should act like a relay,
300 even though our new listener code would correctly not open any
301 ORPorts for ORPort 0. Similar bugs in other Port options are also
302 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
305 - Avoid a pair of double-free and use-after-mark bugs that can
306 occur with certain timings in canceled and re-received DNS
307 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
308 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
309 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
310 - Allow one-hop directory fetching circuits the full "circuit build
311 timeout" period, rather than just half of it, before failing them
312 and marking the relay down. This fix should help reduce cases where
313 clients declare relays (or worse, bridges) unreachable because
314 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
315 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
317 - Authorities no longer include any router in their microdescriptor
318 consensuses for which they couldn't generate or agree on a
319 microdescriptor. Fixes the second piece of bug 6404; fix on
321 - Detect and reject attempts to specify both "FooPort" and
322 "FooPort 0" in the same configuration domain. (It's still okay
323 to have a FooPort in your configuration file, and use "FooPort 0"
324 on the command line to disable it.) Fixes the second half of bug
325 6507; bugfix on 0.2.3.3-alpha.
326 - Make wildcarded addresses (that is, ones beginning with "*.") work
327 when provided via the controller's MapAddress command. Previously,
328 they were accepted, but we never actually noticed that they were
329 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
330 - Avoid crashing on a malformed state file where EntryGuardPathBias
331 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
332 - Add a (probably redundant) memory clear between iterations of
333 the router status voting loop, to prevent future coding errors
334 where data might leak between iterations of the loop. Resolves
337 o Minor bugfixes (log messages):
338 - Downgrade "set buildtimeout to low value" messages to "info"
339 severity; they were never an actual problem, there was never
340 anything reasonable to do about them, and they tended to spam logs
341 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
342 - Downgrade path-bias warning messages to "info". We'll try to get
343 them working better in 0.2.4. Add internal circuit construction
344 state to protect against the noisy warn message "Unexpectedly high
345 circuit_successes". Also add some additional rate-limited notice
346 messages to help determine the root cause of the warn. Fixes bug
347 6475. Bugfix against 0.2.3.17-beta.
348 - Move log message when unable to find a microdesc in a routerstatus
349 entry to parse time. Previously we'd spam this warning every time
350 we tried to figure out which microdescriptors to download. Fixes
351 the third piece of bug 6404; fix on 0.2.3.18-rc.
354 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
355 change when the authority is deciding whether to accept a newly
356 uploaded descriptor. Implements ticket 6423.
357 - Add missing documentation for consensus and microdesc files.
358 Resolves ticket 6732.
361 Changes in version 0.2.2.38 - 2012-08-12
362 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
363 attack that could in theory leak path information.
366 - Avoid an uninitialized memory read when reading a vote or consensus
367 document that has an unrecognized flavor name. This read could
368 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
369 - Try to leak less information about what relays a client is
370 choosing to a side-channel attacker. Previously, a Tor client would
371 stop iterating through the list of available relays as soon as it
372 had chosen one, thus finishing a little earlier when it picked
373 a router earlier in the list. If an attacker can recover this
374 timing information (nontrivial but not proven to be impossible),
375 they could learn some coarse-grained information about which relays
376 a client was picking (middle nodes in particular are likelier to
377 be affected than exits). The timing attack might be mitigated by
378 other factors (see bug 6537 for some discussion), but it's best
379 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
382 Changes in version 0.2.3.20-rc - 2012-08-05
383 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
384 series. It fixes a pair of code security bugs and a potential anonymity
385 issue, updates our RPM spec files, and cleans up other smaller issues.
388 - Avoid read-from-freed-memory and double-free bugs that could occur
389 when a DNS request fails while launching it. Fixes bug 6480;
390 bugfix on 0.2.0.1-alpha.
391 - Avoid an uninitialized memory read when reading a vote or consensus
392 document that has an unrecognized flavor name. This read could
393 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
394 - Try to leak less information about what relays a client is
395 choosing to a side-channel attacker. Previously, a Tor client would
396 stop iterating through the list of available relays as soon as it
397 had chosen one, thus finishing a little earlier when it picked
398 a router earlier in the list. If an attacker can recover this
399 timing information (nontrivial but not proven to be impossible),
400 they could learn some coarse-grained information about which relays
401 a client was picking (middle nodes in particular are likelier to
402 be affected than exits). The timing attack might be mitigated by
403 other factors (see bug 6537 for some discussion), but it's best
404 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
407 - Try to make the warning when giving an obsolete SOCKSListenAddress
408 a little more useful.
409 - Terminate active server managed proxies if Tor stops being a
410 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
411 - Provide a better error message about possible OSX Asciidoc failure
412 reasons. Fixes bug 6436.
413 - Warn when Tor is configured to use accounting in a way that can
414 link a hidden service to some other hidden service or public
415 address. Resolves ticket 6490.
418 - Check return value of fputs() when writing authority certificate
419 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
420 - Ignore ServerTransportPlugin lines when Tor is not configured as
421 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
422 - When disabling guards for having too high a proportion of failed
423 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
427 - Update our default RPM spec files to work with mock and rpmbuild
428 on RHEL/Fedora. They have an updated set of dependencies and
429 conflicts, a fix for an ancient typo when creating the "_tor"
430 user, and better instructions. Thanks to Ondrej Mikle for the
431 patch series. Fixes bug 6043.
434 - Make it possible to set the TestingTorNetwork configuration
435 option using AlternateDirAuthority and AlternateBridgeAuthority
436 as an alternative to setting DirServer. Addresses ticket 6377.
439 - Clarify the documentation for the Alternate*Authority options.
441 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
443 o Code simplification and refactoring:
444 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
445 10 lines. Also, don't nest them. Doing so in the past has
446 led to hard-to-debug code. The new style is to use the
447 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
450 Changes in version 0.2.3.19-rc - 2012-07-06
451 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
452 series. It fixes the compile on Windows, reverts to a GeoIP database
453 that isn't as broken, and fixes a flow control bug that has been around
454 since the beginning of Tor.
457 - Fix a bug handling SENDME cells on nonexistent streams that could
458 result in bizarre window values. Report and patch contributed
459 pseudonymously. Fixes part of bug 6271. This bug was introduced
460 before the first Tor release, in svn commit r152.
461 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
462 June 2012 database, Maxmind marked many Tor relays as country "A1",
463 which will cause risky behavior for clients that set EntryNodes
464 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
465 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
466 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
469 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
470 bugfix on 0.2.1.10-alpha.
473 Changes in version 0.2.3.18-rc - 2012-06-28
474 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
475 series. It fixes a few smaller bugs, but generally appears stable.
476 Please test it and let us know whether it is!
479 - Allow wildcarded mapaddress targets to be specified on the
480 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
481 - Make our linker option detection code more robust against linkers
482 such as on FreeBSD 8, where a bad combination of options completes
483 successfully but makes an unrunnable binary. Fixes bug 6173;
484 bugfix on 0.2.3.17-beta.
486 o Minor bugfixes (on 0.2.2.x and earlier):
487 - Avoid a false positive in the util/threads unit test by increasing
488 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
489 - Replace "Sending publish request" log messages with "Launching
490 upload", so that they no longer confusingly imply that we're
491 sending something to a directory we might not even be connected
492 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
493 - Make sure to set *socket_error in all error cases in
494 connection_connect(), so it can't produce a warning about
495 errno being zero from errno_to_orconn_end_reason(). Bugfix on
496 0.2.1.1-alpha; resolves ticket 6028.
497 - Downgrade "Got a certificate, but we already have it" log messages
498 from warning to info, except when we're a dirauth. Fixes bug 5238;
499 bugfix on 0.2.1.7-alpha.
500 - When checking for requested signatures on the latest consensus
501 before serving it to a client, make sure to check the right
502 consensus flavor. Bugfix on 0.2.2.6-alpha.
503 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
504 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
506 o Minor bugfixes (on 0.2.3.x):
507 - Make format_helper_exit_status() avoid unnecessary space padding
508 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
510 - Downgrade a message about cleaning the microdescriptor cache to
511 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
512 - Log a BUG message at severity INFO if we have a networkstatus with
513 a missing entry for some microdescriptor. Continues on a patch
515 - Improve the log message when a managed proxy fails to launch. Fixes
516 bug 5099; bugfix on 0.2.3.6-alpha.
517 - Don't do DNS lookups when parsing corrupted managed proxy protocol
518 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
519 - When formatting wildcarded address mappings for the controller,
520 be sure to include "*." as appropriate. Partially fixes bug 6244;
521 bugfix on 0.2.3.9-alpha.
522 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
523 Bugfix on 0.2.3.13-alpha.
524 - Stop logging messages about running with circuit timeout learning
525 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
526 - Disable a spurious warning about reading on a marked and flushing
527 connection. We shouldn't be doing that, but apparently we
528 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
529 - Fix a bug that stopped AllowDotExit from working on addresses
530 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
533 o Code simplification, refactoring, unit tests:
534 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
535 Libevent's notion of cached time when possible.
536 - Remove duplicate code for invoking getrlimit() from control.c.
537 - Add a unit test for the environment_variable_names_equal function.
540 - Document the --defaults-torrc option, and the new (in 0.2.3)
541 semantics for overriding, extending, and clearing lists of
542 options. Closes bug 4748.
545 Changes in version 0.2.3.17-beta - 2012-06-15
546 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
547 gets our TLS handshake back on track for being able to blend in with
548 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
549 with Vidalia, and otherwise continues to get us closer to a release
553 - Enable gcc and ld hardening by default. Resolves ticket 5210.
554 - Update TLS cipher list to match Firefox 8 and later. Resolves
556 - Implement the client side of proposal 198: remove support for
557 clients falsely claiming to support standard ciphersuites that
558 they can actually provide. As of modern OpenSSL versions, it's not
559 necessary to fake any standard ciphersuite, and doing so prevents
560 us from using better ciphersuites in the future, since servers
561 can't know whether an advertised ciphersuite is really supported or
562 not. Some hosts -- notably, ones with very old versions of OpenSSL
563 or where OpenSSL has been built with ECC disabled -- will stand
564 out because of this change; TBB users should not be affected.
567 - Change the default value for DynamicDHGroups (introduced in
568 0.2.3.9-alpha) to 0. This feature can make Tor relays less
569 identifiable by their use of the mod_ssl DH group, but at
570 the cost of some usability (#4721) and bridge tracing (#6087)
571 regressions. Resolves ticket 5598.
572 - Send a CRLF at the end of each STATUS_* control protocol event. This
573 bug tickled a bug in Vidalia which would make it freeze. Fixes
574 bug 6094; bugfix on 0.2.3.16-alpha.
577 - Disable writing on marked-for-close connections when they are
578 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
579 bug 5263; bugfix on 0.0.2pre13, where we first added a special
580 case for flushing marked connections.
581 - Detect SSL handshake even when the initial attempt to write the
582 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
583 - Change the AllowDotExit rules so they should actually work.
584 We now enforce AllowDotExit only immediately after receiving an
585 address via SOCKS or DNSPort: other sources are free to provide
586 .exit addresses after the resolution occurs. Fixes bug 3940;
587 bugfix on 0.2.2.1-alpha.
588 - Fix a (harmless) integer overflow in cell statistics reported by
589 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
590 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
591 right places and never depends on the consensus parameters or
592 computes adaptive timeouts when it is disabled. Fixes bug 5049;
593 bugfix on 0.2.2.14-alpha.
594 - When building Tor on Windows with -DUNICODE (not default), ensure
595 that error messages, filenames, and DNS server names are always
596 NUL-terminated when we convert them to a single-byte encoding.
597 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
598 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
599 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
600 - Fix an edge case where TestingTorNetwork is set but the authorities
601 and relays all have an uptime of zero, where the private Tor network
602 could briefly lack support for hidden services. Fixes bug 3886;
603 bugfix on 0.2.2.18-alpha.
604 - Correct the manpage's descriptions for the default values of
605 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
607 - Fix the documentation for the --hush and --quiet command line
608 options, which changed their behavior back in 0.2.3.3-alpha.
609 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
613 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
614 more information to it, so that we can track it down in case it
615 returns again. Mitigates bug 5235.
616 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
617 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
618 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
619 - Warn the user when HTTPProxy, but no other proxy type, is
620 configured. This can cause surprising behavior: it doesn't send
621 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
622 directory traffic only. Resolves ticket 4663.
623 - Issue a notice if a guard completes less than 40% of your circuits.
624 Threshold is configurable by torrc option PathBiasNoticeRate and
625 consensus parameter pb_noticepct. There is additional, off-by-
626 default code to disable guards which fail too many circuits.
627 Addresses ticket 5458.
628 - Update to the June 6 2012 Maxmind GeoLite Country database.
630 o Code simplifications and refactoring:
631 - Remove validate_pluggable_transports_config(): its warning
632 message is now handled by connection_or_connect().
635 Changes in version 0.2.2.37 - 2012-06-06
636 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
637 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
641 - Work around a bug in OpenSSL that broke renegotiation with TLS
642 1.1 and TLS 1.2. Without this workaround, all attempts to speak
643 the v2 Tor connection protocol when both sides were using OpenSSL
644 1.0.1 would fail. Resolves ticket 6033.
645 - When waiting for a client to renegotiate, don't allow it to add
646 any bytes to the input buffer. This fixes a potential DoS issue.
647 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
648 - Fix an edge case where if we fetch or publish a hidden service
649 descriptor, we might build a 4-hop circuit and then use that circuit
650 for exiting afterwards -- even if the new last hop doesn't obey our
651 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
654 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
655 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
658 - Tell GCC and Clang to check for any errors in format strings passed
659 to the tor_v*(print|scan)f functions.
662 Changes in version 0.2.3.16-alpha - 2012-06-05
663 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
664 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
665 currently). It also fixes a variety of smaller bugs and other cleanups
666 that get us closer to a release candidate.
668 o Major bugfixes (general):
669 - Work around a bug in OpenSSL that broke renegotiation with TLS
670 1.1 and TLS 1.2. Without this workaround, all attempts to speak
671 the v2 Tor connection protocol when both sides were using OpenSSL
672 1.0.1 would fail. Resolves ticket 6033.
673 - When waiting for a client to renegotiate, don't allow it to add
674 any bytes to the input buffer. This fixes a potential DoS issue.
675 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
676 - Pass correct OR address to managed proxies (like obfsproxy),
677 even when ORListenAddress is used. Fixes bug 4865; bugfix on
679 - The advertised platform of a router now includes only its operating
680 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
681 service pack level (for Windows) or its CPU architecture (for Unix).
682 We also no longer include the "git-XYZ" tag in the version. Resolves
685 o Major bugfixes (clients):
686 - If we are unable to find any exit that supports our predicted ports,
687 stop calling them predicted, so that we don't loop and build
688 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
689 which introduced predicted ports.
690 - Fix an edge case where if we fetch or publish a hidden service
691 descriptor, we might build a 4-hop circuit and then use that circuit
692 for exiting afterwards -- even if the new last hop doesn't obey our
693 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
694 - Check at each new consensus whether our entry guards were picked
695 long enough ago that we should rotate them. Previously, we only
696 did this check at startup, which could lead to us holding a guard
697 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
698 - When fetching a bridge descriptor from a bridge authority,
699 always do so anonymously, whether we have been able to open
700 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
701 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
702 but we'll need to wait for bug 6010 before it's actually usable.
704 o Major bugfixes (directory authorities):
705 - When computing weight parameters, behave more robustly in the
706 presence of a bad bwweightscale value. Previously, the authorities
707 would crash if they agreed on a sufficiently broken weight_scale
708 value: now, they use a reasonable default and carry on. Partial
709 fix for 5786; bugfix on 0.2.2.17-alpha.
710 - Check more thoroughly to prevent a rogue authority from
711 double-voting on any consensus directory parameter. Previously,
712 authorities would crash in this case if the total number of
713 votes for any parameter exceeded the number of active voters,
714 but would let it pass otherwise. Partial fix for bug 5786; bugfix
718 - Rate-limit log messages when asked to connect anonymously to
719 a private address. When these hit, they tended to hit fast and
720 often. Also, don't bother trying to connect to addresses that we
721 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
722 reply makes us think we have been lied to, even when the address the
723 client tried to connect to was "localhost." Resolves ticket 2822.
724 - Allow packagers to insert an extra string in server descriptor
725 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
726 Resolves the rest of ticket 2988.
727 - Raise the threshold of server descriptors needed (75%) and exit
728 server descriptors needed (50%) before we will declare ourselves
729 bootstrapped. This will make clients start building circuits a
730 little later, but makes the initially constructed circuits less
731 skewed and less in conflict with further directory fetches. Fixes
733 - Close any connection that sends unrecognized junk before the
734 handshake. Solves an issue noted in bug 4369.
735 - Improve log messages about managed transports. Resolves ticket 5070.
736 - Tag a bridge's descriptor as "never to be sent unencrypted".
737 This shouldn't matter, since bridges don't open non-anonymous
738 connections to the bridge authority and don't allow unencrypted
739 directory connections from clients, but we might as well make
740 sure. Closes bug 5139.
741 - Expose our view of whether we have gone dormant to the controller,
742 via a new "GETINFO dormant" value. Torbutton and other controllers
743 can use this to avoid doing periodic requests through Tor while
744 it's dormant (bug 4718). Fixes bug 5954.
745 - Tell GCC and Clang to check for any errors in format strings passed
746 to the tor_v*(print|scan)f functions.
747 - Update to the May 1 2012 Maxmind GeoLite Country database.
749 o Minor bugfixes (already included in 0.2.2.36):
750 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
751 Fixes bug 5346; bugfix on 0.0.8pre3.
752 - Correct parsing of certain date types in parse_http_time().
753 Without this patch, If-Modified-Since would behave
754 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
755 Esteban Manchado Velázques.
756 - Make our number-parsing functions always treat too-large values
757 as an error, even when those values exceed the width of the
758 underlying type. Previously, if the caller provided these
759 functions with minima or maxima set to the extreme values of the
760 underlying integer type, these functions would return those
761 values on overflow rather than treating overflow as an error.
762 Fixes part of bug 5786; bugfix on 0.0.9.
763 - If we hit the error case where routerlist_insert() replaces an
764 existing (old) server descriptor, make sure to remove that
765 server descriptor from the old_routers list. Fix related to bug
766 1776. Bugfix on 0.2.2.18-alpha.
767 - Clarify the behavior of MaxCircuitDirtiness with hidden service
768 circuits. Fixes issue 5259.
770 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
771 - Prevent a null-pointer dereference when receiving a data cell
772 for a nonexistent stream when the circuit in question has an
773 empty deliver window. We don't believe this is triggerable,
774 since we don't currently allow deliver windows to become empty,
775 but the logic is tricky enough that it's better to make the code
776 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
777 - Fix a memory leak when trying to launch a DNS request when the
778 network is disabled or the nameservers are unconfigurable. Fixes
779 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
780 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
781 - Don't hold a Windows file handle open for every file mapping;
782 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
784 - Avoid O(n^2) performance characteristics when parsing a large
785 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
786 - Format more doubles with %f, not %lf. Patch from grarpamp to make
787 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
789 - Make our replacement implementation of strtok_r() compatible with
790 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
791 bugfix on 0.2.2.1-alpha.
792 - Fix a NULL-pointer dereference on a badly formed
793 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
794 bugfix on 0.2.2.9-alpha.
795 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
796 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
797 - Defensively refactor rend_mid_rendezvous() so that protocol
798 violations and length checks happen in the beginning. Fixes
800 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
801 that IPv6 stuff will compile on MSVC, and compilation issues
802 will be easier to track down. Fixes bug 5861.
804 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
805 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
806 resource exhaustion, so that clients can adjust their load to
807 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
808 started using END_STREAM_REASON_RESOURCELIMIT.
809 - Don't check for whether the address we're using for outbound
810 connections has changed until after the outbound connection has
811 completed. On Windows, getsockname() doesn't succeed until the
812 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
813 - If the configuration tries to set MyFamily on a bridge, refuse to
814 do so, and warn about the security implications. Fixes bug 4657;
815 bugfix on 0.2.0.3-alpha.
816 - If the client fails to set a reasonable set of ciphersuites
817 during its v2 handshake renegotiation, allow the renegotiation to
818 continue nevertheless (i.e. send all the required certificates).
819 Fixes bug 4591; bugfix on 0.2.0.20-rc.
820 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
821 option is set to 0 (which Vidalia version 0.2.16 now does when
822 a SAVECONF attempt fails), perform other actions that SIGHUP
823 usually causes (like reopening the logs). Fixes bug 5095; bugfix
825 - If we fail to write a microdescriptor to the disk cache, do not
826 continue replacing the old microdescriptor file. Fixes bug 2954;
827 bugfix on 0.2.2.6-alpha.
828 - Exit nodes don't need to fetch certificates for authorities that
829 they don't recognize; only directory authorities, bridges,
830 and caches need to do that. Fixes part of bug 2297; bugfix on
832 - Correctly handle checking the permissions on the parent
833 directory of a control socket in the root directory. Bug found
834 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
836 - When told to add a bridge with the same digest as a preexisting
837 bridge but a different addr:port, change the addr:port as
838 requested. Previously we would not notice the change. Fixes half
839 of bug 5603; fix on 0.2.2.26-beta.
840 - End AUTHCHALLENGE error messages (in the control protocol) with
841 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
843 o Minor bugfixes (on 0.2.3.x):
844 - Turn an assertion (that the number of handshakes received as a
845 server is not < 1) into a warning. Fixes bug 4873; bugfix on
847 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
848 we had reversed them when the answer was cached.) Fixes bug
849 5723; bugfix on 0.2.3.1-alpha.
850 - Work correctly on Linux systems with accept4 support advertised in
851 their headers, but without accept4 support in the kernel. Fix
852 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
853 - When told to add a bridge with the same addr:port as a preexisting
854 bridge but a different transport, change the transport as
855 requested. Previously we would not notice the change. Fixes half
856 of bug 5603; fix on 0.2.3.2-alpha.
857 - Avoid a "double-reply" warning when replying to a SOCKS request
858 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
859 bugfix on 0.2.3.4-alpha.
860 - Fix a bug where a bridge authority crashes if it has seen no
861 directory requests when it's time to write statistics to disk.
862 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
864 - Don't try to open non-control listeners when DisableNetwork is set.
865 Previously, we'd open all listeners, then immediately close them.
866 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
867 - Don't abort the managed proxy protocol if the managed proxy
868 sends us an unrecognized line; ignore it instead. Fixes bug
869 5910; bugfix on 0.2.3.9-alpha.
870 - Fix a compile warning in crypto.c when compiling with clang 3.1.
871 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
872 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
873 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
874 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
875 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
876 - Resolve numerous small warnings and build issues with MSVC. Resolves
879 o Documentation fixes:
880 - Improve the manual's documentation for the NT Service command-line
881 options. Addresses ticket 3964.
882 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
883 - Document the changes to the ORPort and DirPort options, and the
884 fact that {OR/Dir}ListenAddress is now unnecessary (and
885 therefore deprecated). Resolves ticket 5597.
888 - Remove the torrc.bridge file: we don't use it for anything, and
889 it had become badly desynchronized from torrc.sample. Resolves
893 Changes in version 0.2.2.36 - 2012-05-24
894 Tor 0.2.2.36 updates the addresses for two of the eight directory
895 authorities, fixes some potential anonymity and security issues,
896 and fixes several crash bugs.
898 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
899 known flaws, and nobody should be using them. You should upgrade. If
900 you're using a Linux or BSD and its packages are obsolete, stop using
901 those packages and upgrade anyway.
903 o Directory authority changes:
904 - Change IP address for maatuska (v3 directory authority).
905 - Change IP address for ides (v3 directory authority), and rename
909 - When building or running with any version of OpenSSL earlier
910 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
911 versions have a bug (CVE-2011-4576) in which their block cipher
912 padding includes uninitialized data, potentially leaking sensitive
913 information to any peer with whom they make a SSLv3 connection. Tor
914 does not use SSL v3 by default, but a hostile client or server
915 could force an SSLv3 connection in order to gain information that
916 they shouldn't have been able to get. The best solution here is to
917 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
918 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
919 to make sure that the bug can't happen.
920 - Never use a bridge or a controller-supplied node as an exit, even
921 if its exit policy allows it. Found by wanoskarnet. Fixes bug
922 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
923 and 0.2.0.3-alpha (for bridge-purpose descriptors).
924 - Only build circuits if we have a sufficient threshold of the total
925 descriptors that are marked in the consensus with the "Exit"
926 flag. This mitigates an attack proposed by wanoskarnet, in which
927 all of a client's bridges collude to restrict the exit nodes that
928 the client knows about. Fixes bug 5343.
929 - Provide controllers with a safer way to implement the cookie
930 authentication mechanism. With the old method, if another locally
931 running program could convince a controller that it was the Tor
932 process, then that program could trick the controller into telling
933 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
934 authentication method uses a challenge-response approach to prevent
935 this attack. Fixes bug 5185; implements proposal 193.
938 - Avoid logging uninitialized data when unable to decode a hidden
939 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
940 - Avoid a client-side assertion failure when receiving an INTRODUCE2
941 cell on a general purpose circuit. Fixes bug 5644; bugfix on
943 - Fix builds when the path to sed, openssl, or sha1sum contains
944 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
946 - Correct our replacements for the timeradd() and timersub() functions
947 on platforms that lack them (for example, Windows). The timersub()
948 function is used when expiring circuits, while timeradd() is
949 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
950 bugfix on 0.2.2.24-alpha.
951 - Fix the SOCKET_OK test that we use to tell when socket
952 creation fails so that it works on Win64. Fixes part of bug 4533;
953 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
956 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
957 Fixes bug 5346; bugfix on 0.0.8pre3.
958 - Make our number-parsing functions always treat too-large values
959 as an error, even when those values exceed the width of the
960 underlying type. Previously, if the caller provided these
961 functions with minima or maxima set to the extreme values of the
962 underlying integer type, these functions would return those
963 values on overflow rather than treating overflow as an error.
964 Fixes part of bug 5786; bugfix on 0.0.9.
965 - Older Linux kernels erroneously respond to strange nmap behavior
966 by having accept() return successfully with a zero-length
967 socket. When this happens, just close the connection. Previously,
968 we would try harder to learn the remote address: but there was
969 no such remote address to learn, and our method for trying to
970 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
971 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
972 - Correct parsing of certain date types in parse_http_time().
973 Without this patch, If-Modified-Since would behave
974 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
975 Esteban Manchado Velázques.
976 - Change the BridgePassword feature (part of the "bridge community"
977 design, which is not yet implemented) to use a time-independent
978 comparison. The old behavior might have allowed an adversary
979 to use timing to guess the BridgePassword value. Fixes bug 5543;
980 bugfix on 0.2.0.14-alpha.
981 - Detect and reject certain misformed escape sequences in
982 configuration values. Previously, these values would cause us
983 to crash if received in a torrc file or over an authenticated
984 control port. Bug found by Esteban Manchado Velázquez, and
985 independently by Robert Connolly from Matta Consulting who further
986 noted that it allows a post-authentication heap overflow. Patch
987 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
988 bugfix on 0.2.0.16-alpha.
989 - Fix a compile warning when using the --enable-openbsd-malloc
990 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
991 - During configure, detect when we're building with clang version
992 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
993 CFLAGS. clang doesn't support them yet.
994 - When sending an HTTP/1.1 proxy request, include a Host header.
995 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
996 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
997 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
998 - If we hit the error case where routerlist_insert() replaces an
999 existing (old) server descriptor, make sure to remove that
1000 server descriptor from the old_routers list. Fix related to bug
1001 1776. Bugfix on 0.2.2.18-alpha.
1003 o Minor bugfixes (documentation and log messages):
1004 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
1005 Fixes bug 4856; bugfix on Tor 0.0.6.
1006 - Update "ClientOnly" man page entry to explain that there isn't
1007 really any point to messing with it. Resolves ticket 5005.
1008 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
1009 directory authority option (introduced in Tor 0.2.2.34).
1010 - Downgrade the "We're missing a certificate" message from notice
1011 to info: people kept mistaking it for a real problem, whereas it
1012 is seldom the problem even when we are failing to bootstrap. Fixes
1013 bug 5067; bugfix on 0.2.0.10-alpha.
1014 - Correctly spell "connect" in a log message on failure to create a
1015 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
1016 - Clarify the behavior of MaxCircuitDirtiness with hidden service
1017 circuits. Fixes issue 5259.
1020 - Directory authorities now reject versions of Tor older than
1021 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
1022 inclusive. These versions accounted for only a small fraction of
1023 the Tor network, and have numerous known security issues. Resolves
1025 - Update to the May 1 2012 Maxmind GeoLite Country database.
1028 - When sending or relaying a RELAY_EARLY cell, we used to convert
1029 it to a RELAY cell if the connection was using the v1 link
1030 protocol. This was a workaround for older versions of Tor, which
1031 didn't handle RELAY_EARLY cells properly. Now that all supported
1032 versions can handle RELAY_EARLY cells, and now that we're enforcing
1033 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
1034 remove this workaround. Addresses bug 4786.
1037 Changes in version 0.2.3.15-alpha - 2012-04-30
1038 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
1039 the development branch build on Windows again.
1041 o Minor bugfixes (on 0.2.2.x and earlier):
1042 - Make sure that there are no unhandled pending TLS errors before
1043 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
1044 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
1045 Bugfix on 0.1.0.5-rc; fixes bug 4528.
1046 - Fix an assert that directory authorities could trigger on sighup
1047 during some configuration state transitions. We now don't treat
1048 it as a fatal error when the new descriptor we just generated in
1049 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
1050 - After we pick a directory mirror, we would refuse to use it if
1051 it's in our ExcludeExitNodes list, resulting in mysterious failures
1052 to bootstrap for people who just wanted to avoid exiting from
1053 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
1054 - When building with --enable-static-tor on OpenBSD, do not
1055 erroneously attempt to link -lrt. Fixes bug 5103.
1057 o Minor bugfixes (on 0.2.3.x):
1058 - When Tor is built with kernel headers from a recent (last few
1059 years) Linux kernel, do not fail to run on older (pre-2.6.28
1060 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
1061 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
1063 - Fix compilation with miniupnpc version 1.6; patch from
1064 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
1065 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
1066 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
1067 - Fix compilation on platforms without unistd.h, or where environ
1068 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
1071 - Directory authorities are now a little more lenient at accepting
1072 older router descriptors, or newer router descriptors that don't
1073 make big changes. This should help ameliorate past and future
1074 issues where routers think they have uploaded valid descriptors,
1075 but the authorities don't think so. Fix for ticket 2479.
1076 - Make the code that clients use to detect an address change be
1077 IPv6-aware, so that it won't fill clients' logs with error
1078 messages when trying to get the IPv4 address of an IPv6
1079 connection. Implements ticket 5537.
1082 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
1083 authorities needed to use it for a while to keep the network working
1084 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
1085 that was six months ago. As of now, it should no longer be needed
1089 Changes in version 0.2.3.14-alpha - 2012-04-23
1090 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
1091 candidate. It also dramatically speeds up AES: fast relays should
1092 consider switching to the newer OpenSSL library.
1094 o Directory authority changes:
1095 - Change IP address for ides (v3 directory authority), and rename
1099 - Avoid logging uninitialized data when unable to decode a hidden
1100 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
1101 - Avoid a client-side assertion failure when receiving an INTRODUCE2
1102 cell on a general purpose circuit. Fixes bug 5644; bugfix on
1104 - If authorities are unable to get a v2 consensus document from other
1105 directory authorities, they no longer fall back to fetching
1106 them from regular directory caches. Fixes bug 5635; bugfix on
1107 0.2.2.26-beta, where routers stopped downloading v2 consensus
1109 - When we start a Tor client with a normal consensus already cached,
1110 be willing to download a microdescriptor consensus. Fixes bug 4011;
1111 fix on 0.2.3.1-alpha.
1113 o Major features (performance):
1114 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
1115 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
1116 vectorized AES implementations as appropriate. These can be much,
1117 much faster than other AES implementations.
1119 o Minor bugfixes (0.2.2.x and earlier):
1120 - Don't launch more than 10 service-side introduction-point circuits
1121 for a hidden service in five minutes. Previously, we would consider
1122 launching more introduction-point circuits if at least one second
1123 had passed without any introduction-point circuits failing. Fixes
1124 bug 4607; bugfix on 0.0.7pre1.
1125 - Change the BridgePassword feature (part of the "bridge community"
1126 design, which is not yet implemented) to use a time-independent
1127 comparison. The old behavior might have allowed an adversary
1128 to use timing to guess the BridgePassword value. Fixes bug 5543;
1129 bugfix on 0.2.0.14-alpha.
1130 - Enforce correct return behavior of tor_vsscanf() when the '%%'
1131 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
1132 - When sending an HTTP/1.1 proxy request, include a Host header.
1133 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
1134 - Don't log that we have "decided to publish new relay descriptor"
1135 unless we are actually publishing a descriptor. Fixes bug 3942;
1136 bugfix on 0.2.2.28-beta.
1138 o Minor bugfixes (0.2.3.x):
1139 - Fix a bug where a bridge authority crashes (on a failed assert)
1140 if it has seen no directory requests when it's time to write
1141 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
1142 - Fix bug stomping on ORPort option NoListen and ignoring option
1143 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
1144 - In the testsuite, provide a large enough buffer in the tor_sscanf
1145 unit test. Otherwise we'd overrun that buffer and crash during
1146 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
1148 - Make sure we create the keys directory if it doesn't exist and we're
1149 about to store the dynamic Diffie-Hellman parameters. Fixes bug
1150 5572; bugfix on 0.2.3.13-alpha.
1151 - Fix a small memory leak when trying to decode incorrect base16
1152 authenticator during SAFECOOKIE authentication. Found by
1153 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
1156 - Add more information to a log statement that might help track down
1157 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
1158 non-IP address" messages (or any Bug messages, for that matter!),
1159 please let us know about it.
1160 - Relays now understand an IPv6 address when they get one from a
1161 directory server. Resolves ticket 4875.
1162 - Resolve IPv6 addresses in bridge and entry statistics to country
1163 code "??" which means we at least count them. Resolves ticket 5053;
1164 improves on 0.2.3.9-alpha.
1165 - Update to the April 3 2012 Maxmind GeoLite Country database.
1166 - Begin a doc/state-contents.txt file to explain the contents of
1167 the Tor state file. Fixes bug 2987.
1169 o Default torrc changes:
1170 - Stop listing "socksport 9050" in torrc.sample. We open a socks
1171 port on 9050 by default anyway, so this should not change anything
1173 - Stop mentioning the deprecated *ListenAddress options in
1174 torrc.sample. Fixes bug 5438.
1175 - Document unit of bandwidth related options in sample torrc.
1179 - The "torify" script no longer supports the "tsocks" socksifier
1180 tool, since tsocks doesn't support DNS and UDP right for Tor.
1181 Everyone should be using torsocks instead. Fixes bugs 3530 and
1182 5180. Based on a patch by "ugh".
1185 - Change the symmetric cipher interface so that creating and
1186 initializing a stream cipher are no longer separate functions.
1187 - Remove all internal support for unpadded RSA. We never used it, and
1188 it would be a bad idea to start.
1191 Changes in version 0.2.3.13-alpha - 2012-03-26
1192 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
1193 in managed pluggable transports, as well as providing other cleanups
1194 that get us closer to a release candidate.
1196 o Directory authority changes:
1197 - Change IP address for maatuska (v3 directory authority).
1200 - Provide controllers with a safer way to implement the cookie
1201 authentication mechanism. With the old method, if another locally
1202 running program could convince a controller that it was the Tor
1203 process, then that program could trick the controller into telling
1204 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
1205 authentication method uses a challenge-response approach to prevent
1206 this attack. Fixes bug 5185, implements proposal 193.
1207 - Never use a bridge or a controller-supplied node as an exit, even
1208 if its exit policy allows it. Found by wanoskarnet. Fixes bug
1209 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
1210 and 0.2.0.3-alpha (for bridge-purpose descriptors).
1211 - Only build circuits if we have a sufficient threshold of the total
1212 descriptors that are marked in the consensus with the "Exit"
1213 flag. This mitigates an attack proposed by wanoskarnet, in which
1214 all of a client's bridges collude to restrict the exit nodes that
1215 the client knows about. Fixes bug 5343.
1217 o Major bugfixes (on Tor 0.2.3.x):
1218 - Avoid an assert when managed proxies like obfsproxy are configured,
1219 and we receive HUP signals or setconf attempts too rapidly. This
1220 situation happens most commonly when Vidalia tries to attach to
1221 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
1222 bugfix on 0.2.3.6-alpha.
1223 - Fix a relay-side pluggable transports bug where managed proxies were
1224 unreachable from the Internet, because Tor asked them to bind on
1225 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
1226 - Stop discarding command-line arguments when TestingTorNetwork
1227 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
1228 0.2.3.9-alpha, where task 4552 added support for two layers of
1230 - Resume allowing the unit tests to run in gdb. This was accidentally
1231 made impossible when the DisableDebuggerAttachment option was
1232 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
1233 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
1234 0.2.3.11-alpha. Reported by Anthony G. Basile.
1236 o Minor bugfixes (on 0.2.2.x and earlier):
1237 - Ensure we don't cannibalize circuits that are longer than three hops
1238 already, so we don't end up making circuits with 5 or more
1239 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
1240 0.1.0.1-rc which introduced cannibalization.
1241 - Detect and reject certain misformed escape sequences in
1242 configuration values. Previously, these values would cause us
1243 to crash if received in a torrc file or over an authenticated
1244 control port. Bug found by Esteban Manchado Velázquez, and
1245 independently by Robert Connolly from Matta Consulting who further
1246 noted that it allows a post-authentication heap overflow. Patch
1247 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
1248 bugfix on 0.2.0.16-alpha.
1249 - Fix a compile warning when using the --enable-openbsd-malloc
1250 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
1251 - Directory caches no longer refuse to clean out descriptors because
1252 of missing v2 networkstatus documents, unless they're configured
1253 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
1254 0.2.2.26-beta. Patch by Daniel Bryg.
1255 - Update to the latest version of the tinytest unit testing framework.
1256 This includes a couple of bugfixes that can be relevant for
1257 running forked unit tests on Windows, and removes all reserved
1260 o Minor bugfixes (on 0.2.3.x):
1261 - On a failed pipe() call, don't leak file descriptors. Fixes bug
1262 4296; bugfix on 0.2.3.1-alpha.
1263 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
1264 until after we have received a CERTS cell. Fixes bug 4361; bugfix
1265 on 0.2.3.6-alpha. Patch by "frosty".
1266 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
1267 option, so that the IP stack doesn't decide to use it for IPv4
1268 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
1269 - Ensure that variables set in Tor's environment cannot override
1270 environment variables that Tor passes to a managed
1271 pluggable-transport proxy. Previously, Tor would pass every
1272 variable in its environment to managed proxies along with the new
1273 ones, in such a way that on many operating systems, the inherited
1274 environment variables would override those which Tor tried to
1275 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
1276 bugfix on 0.2.3.9-alpha for Windows.
1279 - A wide variety of new unit tests by Esteban Manchado Velázquez.
1280 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
1281 - Update to the March 6 2012 Maxmind GeoLite Country database.
1284 Changes in version 0.2.3.12-alpha - 2012-02-13
1285 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
1286 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
1287 when Tor is configured to use a pluggable transport like obfsproxy.
1290 - Fix builds when the path to sed, openssl, or sha1sum contains
1291 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
1293 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
1294 connections. This change should allow busy exit relays to stop
1295 running out of available sockets as quickly. Fixes bug 4950;
1296 bugfix on 0.2.2.26-beta.
1297 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
1298 would ask the bridge for microdescriptors, which are only supported
1299 in 0.2.3.x, and then fail to bootstrap when it didn't get the
1300 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
1301 - Properly set up obfsproxy's environment when in managed mode. The
1302 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
1303 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
1304 5076 and 5082; bugfix on 0.2.3.6-alpha.
1307 - Use the dead_strip option when building Tor on OS X. This reduces
1308 binary size by almost 19% when linking openssl and libevent
1309 statically, which we do for Tor Browser Bundle.
1310 - Fix broken URLs in the sample torrc file, and tell readers about
1311 the OutboundBindAddress, ExitPolicyRejectPrivate, and
1312 PublishServerDescriptor options. Addresses bug 4652.
1313 - Update to the February 7 2012 Maxmind GeoLite Country database.
1316 - Downgrade the "We're missing a certificate" message from notice
1317 to info: people kept mistaking it for a real problem, whereas it
1318 is seldom the problem even when we are failing to bootstrap. Fixes
1319 bug 5067; bugfix on 0.2.0.10-alpha.
1320 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
1321 managed pluggable transport server proxy's environment.
1322 Previously, we would put it there, even though Tor doesn't
1323 implement an 'extended server port' yet, and even though Tor
1324 almost certainly isn't listening at that address. For now, we set
1325 it to an empty string to avoid crashing older obfsproxies. Bugfix
1327 - Log the heartbeat message every HeartbeatPeriod seconds, not every
1328 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
1329 0.2.3.1-alpha. Bug reported by Scott Bennett.
1330 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
1331 bugfix on 0.2.3.11-alpha.
1332 - Update "ClientOnly" man page entry to explain that there isn't
1333 really any point to messing with it. Resolves ticket 5005.
1334 - Use the correct CVE number for CVE-2011-4576 in our comments and
1335 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
1338 o Code simplifications and refactoring:
1339 - Use the _WIN32 macro throughout our code to detect Windows.
1340 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
1344 Changes in version 0.2.3.11-alpha - 2012-01-22
1345 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
1346 the last step of the plan to limit maximum circuit length, includes
1347 a wide variety of hidden service performance and correctness fixes,
1348 works around an OpenSSL security flaw if your distro is too stubborn
1349 to upgrade, and fixes a bunch of smaller issues.
1352 - Now that Tor 0.2.0.x is completely deprecated, enable the final
1353 part of "Proposal 110: Avoiding infinite length circuits" by
1354 refusing all circuit-extend requests that do not use a relay_early
1355 cell. This change helps Tor resist a class of denial-of-service
1356 attacks by limiting the maximum circuit length.
1357 - Adjust the number of introduction points that a hidden service
1358 will try to maintain based on how long its introduction points
1359 remain in use and how many introductions they handle. Fixes
1361 - Try to use system facilities for enumerating local interface
1362 addresses, before falling back to our old approach (which was
1363 binding a UDP socket, and calling getsockname() on it). That
1364 approach was scaring OS X users whose draconian firewall
1365 software warned about binding to UDP sockets, regardless of
1366 whether packets were sent. Now we try to use getifaddrs(),
1367 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
1368 system supports. Resolves ticket 1827.
1370 o Major security workaround:
1371 - When building or running with any version of OpenSSL earlier
1372 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
1373 versions have a bug (CVE-2011-4576) in which their block cipher
1374 padding includes uninitialized data, potentially leaking sensitive
1375 information to any peer with whom they make a SSLv3 connection. Tor
1376 does not use SSL v3 by default, but a hostile client or server
1377 could force an SSLv3 connection in order to gain information that
1378 they shouldn't have been able to get. The best solution here is to
1379 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
1380 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
1381 to make sure that the bug can't happen.
1384 - Fix the SOCKET_OK test that we use to tell when socket
1385 creation fails so that it works on Win64. Fixes part of bug 4533;
1386 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
1387 - Correct our replacements for the timeradd() and timersub() functions
1388 on platforms that lack them (for example, Windows). The timersub()
1389 function is used when expiring circuits, while timeradd() is
1390 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
1391 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
1392 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
1393 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
1394 bug at runtime, not compile time, because some distributions hack
1395 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
1396 on 0.2.3.9-alpha. Found by Pascal.
1398 o Minor features (controller):
1399 - Use absolute path names when reporting the torrc filename in the
1400 control protocol, so a controller can more easily find the torrc
1401 file. Resolves bug 1101.
1402 - Extend the control protocol to report flags that control a circuit's
1403 path selection in CIRC events and in replies to 'GETINFO
1404 circuit-status'. Implements part of ticket 2411.
1405 - Extend the control protocol to report the hidden service address
1406 and current state of a hidden-service-related circuit in CIRC
1407 events and in replies to 'GETINFO circuit-status'. Implements part
1409 - When reporting the path to the cookie file to the controller,
1410 give an absolute path. Resolves ticket 4881.
1411 - Allow controllers to request an event notification whenever a
1412 circuit is cannibalized or its purpose is changed. Implements
1413 part of ticket 3457.
1414 - Include the creation time of a circuit in CIRC and CIRC2
1415 control-port events and the list produced by the 'GETINFO
1416 circuit-status' control-port command.
1418 o Minor features (directory authorities):
1419 - Directory authorities now reject versions of Tor older than
1420 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
1421 inclusive. These versions accounted for only a small fraction of
1422 the Tor network, and have numerous known security issues. Resolves
1424 - Authority operators can now vote for all relays in a given
1425 set of countries to be BadDir/BadExit/Invalid/Rejected.
1426 - Provide two consensus parameters (FastFlagMinThreshold and
1427 FastFlagMaxThreshold) to control the range of allowable bandwidths
1428 for the Fast directory flag. These allow authorities to run
1429 experiments on appropriate requirements for being a "Fast" node.
1430 The AuthDirFastGuarantee config value still applies. Implements
1432 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
1433 directory authority option (introduced in Tor 0.2.2.34).
1435 o Minor features (other):
1436 - Don't disable the DirPort when we cannot exceed our AccountingMax
1437 limit during this interval because the effective bandwidthrate is
1438 low enough. This is useful in a situation where AccountMax is only
1439 used as an additional safeguard or to provide statistics.
1440 - Prepend an informative header to generated dynamic_dh_params files.
1441 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
1442 EntryNodes will have no effect. Resolves issue 2571.
1443 - Log more useful messages when we fail to disable debugger
1445 - Log which authority we're missing votes from when we go to fetch
1446 them from the other auths.
1447 - Log (at debug level) whenever a circuit's purpose is changed.
1448 - Add missing documentation for the MaxClientCircuitsPending,
1449 UseMicrodescriptors, UserspaceIOCPBuffers, and
1450 _UseFilteringSSLBufferevents options, all introduced during
1452 - Update to the January 3 2012 Maxmind GeoLite Country database.
1454 o Minor bugfixes (hidden services):
1455 - Don't close hidden service client circuits which have almost
1456 finished connecting to their destination when they reach
1457 the normal circuit-build timeout. Previously, we would close
1458 introduction circuits which are waiting for an acknowledgement
1459 from the introduction point, and rendezvous circuits which have
1460 been specified in an INTRODUCE1 cell sent to a hidden service,
1461 after the normal CBT. Now, we mark them as 'timed out', and launch
1462 another rendezvous attempt in parallel. This behavior change can
1463 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
1464 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
1465 - Don't close hidden-service-side rendezvous circuits when they
1466 reach the normal circuit-build timeout. This behaviour change can
1467 be disabled using the new
1468 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
1469 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
1470 - Make sure we never mark the wrong rendezvous circuit as having
1471 had its introduction cell acknowleged by the introduction-point
1472 relay. Previously, when we received an INTRODUCE_ACK cell on a
1473 client-side hidden-service introduction circuit, we might have
1474 marked a rendezvous circuit other than the one we specified in
1475 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
1476 a warning message and interfered with the hidden service
1477 connection-establishment process. Fixes bug 4759; bugfix on
1478 0.2.3.3-alpha, when we added the stream-isolation feature which
1479 might cause Tor to open multiple rendezvous circuits for the same
1481 - Don't trigger an assertion failure when we mark a new client-side
1482 hidden-service introduction circuit for close during the process
1483 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
1486 o Minor bugfixes (log messages):
1487 - Correctly spell "connect" in a log message on failure to create a
1488 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
1490 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
1491 Fixes bug 4856; bugfix on Tor 0.0.6.
1492 - Fix the log message describing how we work around discovering
1493 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
1494 4837; bugfix on 0.2.2.9-alpha.
1495 - When logging about a disallowed .exit name, do not also call it
1496 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
1498 o Minor bugfixes (build fixes):
1499 - During configure, detect when we're building with clang version
1500 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
1501 CFLAGS. clang doesn't support them yet.
1502 - During configure, search for library containing cos function as
1503 libm lives in libcore on some platforms (BeOS/Haiku). Linking
1504 against libm was hard-coded before. Fixes the first part of bug
1505 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
1507 - Detect attempts to build Tor on (as yet hypothetical) versions
1508 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
1509 fix for bug 4533. Bugfix on 0.2.2.28-beta.
1510 - Preprocessor directives should not be put inside the arguments
1511 of a macro. This would break compilation with GCC releases prior
1512 to version 3.3. We would never recommend such an old GCC version,
1513 but it is apparently required for binary compatibility on some
1514 platforms (namely, certain builds of Haiku). Fixes the other part
1515 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
1518 o Minor bugfixes (other):
1519 - Older Linux kernels erroneously respond to strange nmap behavior
1520 by having accept() return successfully with a zero-length
1521 socket. When this happens, just close the connection. Previously,
1522 we would try harder to learn the remote address: but there was
1523 no such remote address to learn, and our method for trying to
1524 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
1525 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
1526 - Fix null-pointer access that could occur if TLS allocation failed.
1527 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
1528 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
1529 accidentally been reverted.
1530 - Fix our implementation of crypto_random_hostname() so it can't
1531 overflow on ridiculously large inputs. (No Tor version has ever
1532 provided this kind of bad inputs, but let's be correct in depth.)
1533 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
1534 - Find more places in the code that should have been testing for
1535 invalid sockets using the SOCKET_OK macro. Required for a fix
1536 for bug 4533. Bugfix on 0.2.2.28-beta.
1537 - Fix an assertion failure when, while running with bufferevents, a
1538 connection finishes connecting after it is marked for close, but
1539 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
1540 - test_util_spawn_background_ok() hardcoded the expected value
1541 for ENOENT to 2. This isn't portable as error numbers are
1542 platform specific, and particularly the hurd has ENOENT at
1543 0x40000002. Construct expected string at runtime, using the correct
1544 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
1545 - Reject attempts to disable DisableDebuggerAttachment while Tor is
1546 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
1547 - Use an appropriate-width type for sockets in tor-fw-helper on
1548 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
1551 - When sending or relaying a RELAY_EARLY cell, we used to convert
1552 it to a RELAY cell if the connection was using the v1 link
1553 protocol. This was a workaround for older versions of Tor, which
1554 didn't handle RELAY_EARLY cells properly. Now that all supported
1555 versions can handle RELAY_EARLY cells, and now that we're enforcing
1556 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
1557 remove this workaround. Addresses bug 4786.
1559 o Code simplifications and refactoring:
1560 - Use OpenSSL's built-in SSL_state_string_long() instead of our
1561 own homebrewed ssl_state_to_string() replacement. Patch from
1562 Emile Snyder. Fixes bug 4653.
1563 - Use macros to indicate OpenSSL versions, so we don't need to worry
1564 about accidental hexadecimal bit shifts.
1565 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
1567 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
1568 - Use the smartlist_add_asprintf() alias more consistently.
1569 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
1570 invalid value, rather than just -1.
1571 - Rename a handful of old identifiers, mostly related to crypto
1572 structures and crypto functions. By convention, our "create an
1573 object" functions are called "type_new()", our "free an object"
1574 functions are called "type_free()", and our types indicate that
1575 they are types only with a final "_t". But a handful of older
1576 types and functions broke these rules, with function names like
1577 "type_create" or "subsystem_op_type", or with type names like
1581 Changes in version 0.2.3.10-alpha - 2011-12-16
1582 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
1583 Tor's buffers code. Absolutely everybody should upgrade.
1585 The bug relied on an incorrect calculation when making data continuous
1586 in one of our IO buffers, if the first chunk of the buffer was
1587 misaligned by just the wrong amount. The miscalculation would allow an
1588 attacker to overflow a piece of heap-allocated memory. To mount this
1589 attack, the attacker would need to either open a SOCKS connection to
1590 Tor's SocksPort (usually restricted to localhost), or target a Tor
1591 instance configured to make its connections through a SOCKS proxy
1592 (which Tor does not do by default).
1594 Good security practice requires that all heap-overflow bugs should be
1595 presumed to be exploitable until proven otherwise, so we are treating
1596 this as a potential code execution attack. Please upgrade immediately!
1597 This bug does not affect bufferevents-based builds of Tor. Special
1598 thanks to "Vektor" for reporting this issue to us!
1600 This release also contains a few minor bugfixes for issues discovered
1604 - Fix a heap overflow bug that could occur when trying to pull
1605 data into the first chunk of a buffer, when that chunk had
1606 already had some data drained from it. Fixes CVE-2011-2778;
1607 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1610 - If we can't attach streams to a rendezvous circuit when we
1611 finish connecting to a hidden service, clear the rendezvous
1612 circuit's stream-isolation state and try to attach streams
1613 again. Previously, we cleared rendezvous circuits' isolation
1614 state either too early (if they were freshly built) or not at all
1615 (if they had been built earlier and were cannibalized). Bugfix on
1616 0.2.3.3-alpha; fixes bug 4655.
1617 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
1618 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
1619 - Fix an assertion failure when a relay with accounting enabled
1620 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
1623 - Update to the December 6 2011 Maxmind GeoLite Country database.
1626 Changes in version 0.2.2.35 - 2011-12-16
1627 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
1628 buffers code. Absolutely everybody should upgrade.
1630 The bug relied on an incorrect calculation when making data continuous
1631 in one of our IO buffers, if the first chunk of the buffer was
1632 misaligned by just the wrong amount. The miscalculation would allow an
1633 attacker to overflow a piece of heap-allocated memory. To mount this
1634 attack, the attacker would need to either open a SOCKS connection to
1635 Tor's SocksPort (usually restricted to localhost), or target a Tor
1636 instance configured to make its connections through a SOCKS proxy
1637 (which Tor does not do by default).
1639 Good security practice requires that all heap-overflow bugs should be
1640 presumed to be exploitable until proven otherwise, so we are treating
1641 this as a potential code execution attack. Please upgrade immediately!
1642 This bug does not affect bufferevents-based builds of Tor. Special
1643 thanks to "Vektor" for reporting this issue to us!
1645 Tor 0.2.2.35 also fixes several bugs in previous versions, including
1646 crash bugs for unusual configurations, and a long-term bug that
1647 would prevent Tor from starting on Windows machines with draconian
1650 With this release, we remind everyone that 0.2.0.x has reached its
1651 formal end-of-life. Those Tor versions have many known flaws, and
1652 nobody should be using them. You should upgrade -- ideally to the
1653 0.2.2.x series. If you're using a Linux or BSD and its packages are
1654 obsolete, stop using those packages and upgrade anyway.
1656 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
1657 longer receive support after some time in early 2012.
1660 - Fix a heap overflow bug that could occur when trying to pull
1661 data into the first chunk of a buffer, when that chunk had
1662 already had some data drained from it. Fixes CVE-2011-2778;
1663 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1664 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1665 that it doesn't attempt to allocate a socketpair. This could cause
1666 some problems on Windows systems with overzealous firewalls. Fix for
1667 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1669 - If we mark an OR connection for close based on a cell we process,
1670 don't process any further cells on it. We already avoid further
1671 reads on marked-for-close connections, but now we also discard the
1672 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1673 which was the first version where we might mark a connection for
1674 close based on processing a cell on it.
1675 - Correctly sanity-check that we don't underflow on a memory
1676 allocation (and then assert) for hidden service introduction
1677 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1678 bugfix on 0.2.1.5-alpha.
1679 - Fix a memory leak when we check whether a hidden service
1680 descriptor has any usable introduction points left. Fixes bug
1681 4424. Bugfix on 0.2.2.25-alpha.
1682 - Don't crash when we're running as a relay and don't have a GeoIP
1683 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
1684 we've had in the 0.2.3.x branch already.
1685 - When running as a client, do not print a misleading (and plain
1686 wrong) log message that we're collecting "directory request"
1687 statistics: clients don't collect statistics. Also don't create a
1688 useless (because empty) stats file in the stats/ directory. Fixes
1689 bug 4353; bugfix on 0.2.2.34.
1692 - Detect failure to initialize Libevent. This fix provides better
1693 detection for future instances of bug 4457.
1694 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1695 function. This was eating up hideously large amounts of time on some
1696 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1697 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1698 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1700 - Don't warn about unused log_mutex in log.c when building with
1701 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1702 0.1.0.6-rc which introduced --disable-threads.
1703 - When configuring, starting, or stopping an NT service, stop
1704 immediately after the service configuration attempt has succeeded
1705 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1706 - When sending a NETINFO cell, include the original address
1707 received for the other side, not its canonical address. Found
1708 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1709 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
1710 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1711 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1712 occurred when a client tried to fetch a descriptor for a bridge
1713 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1714 - Backport fixes for a pair of compilation warnings on Windows.
1715 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
1716 - If we had ever tried to call tor_addr_to_str on an address of
1717 unknown type, we would have done a strdup on an uninitialized
1718 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1719 Reported by "troll_un".
1720 - Correctly detect and handle transient lookup failures from
1721 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1722 Reported by "troll_un".
1723 - Fix null-pointer access that could occur if TLS allocation failed.
1724 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1725 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1726 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1729 - Add two new config options for directory authorities:
1730 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
1731 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
1732 that is always sufficient to satisfy the bandwidth requirement for
1733 the Guard flag. Now it will be easier for researchers to simulate
1734 Tor networks with different values. Resolves ticket 4484.
1735 - When Tor ignores a hidden service specified in its configuration,
1736 include the hidden service's directory in the warning message.
1737 Previously, we would only tell the user that some hidden service
1738 was ignored. Bugfix on 0.0.6; fixes bug 4426.
1739 - Update to the December 6 2011 Maxmind GeoLite Country database.
1741 o Packaging changes:
1742 - Make it easier to automate expert package builds on Windows,
1743 by removing an absolute path from makensis.exe command.
1746 Changes in version 0.2.1.32 - 2011-12-16
1747 Tor 0.2.1.32 backports important security and privacy fixes for
1748 oldstable. This release is intended only for package maintainers and
1749 others who cannot use the 0.2.2 stable series. All others should be
1750 using Tor 0.2.2.x or newer.
1752 The Tor 0.2.1.x series will reach formal end-of-life some time in
1753 early 2012; we will stop releasing patches for it then.
1755 o Major bugfixes (also included in 0.2.2.x):
1756 - Correctly sanity-check that we don't underflow on a memory
1757 allocation (and then assert) for hidden service introduction
1758 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1759 bugfix on 0.2.1.5-alpha.
1760 - Fix a heap overflow bug that could occur when trying to pull
1761 data into the first chunk of a buffer, when that chunk had
1762 already had some data drained from it. Fixes CVE-2011-2778;
1763 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1766 - Update to the December 6 2011 Maxmind GeoLite Country database.
1769 Changes in version 0.2.3.9-alpha - 2011-12-08
1770 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
1771 a "DisableNetwork" security feature that bundles can use to avoid
1772 touching the network until bridges are configured, moves forward on
1773 the pluggable transport design, fixes a flaw in the hidden service
1774 design that unnecessarily prevented clients with wrong clocks from
1775 reaching hidden services, and fixes a wide variety of other issues.
1778 - Clients can now connect to private bridges over IPv6. Bridges
1779 still need at least one IPv4 address in order to connect to
1780 other relays. Note that we don't yet handle the case where the
1781 user has two bridge lines for the same bridge (one IPv4, one
1782 IPv6). Implements parts of proposal 186.
1783 - New "DisableNetwork" config option to prevent Tor from launching any
1784 connections or accepting any connections except on a control port.
1785 Bundles and controllers can set this option before letting Tor talk
1786 to the rest of the network, for example to prevent any connections
1787 to a non-bridge address. Packages like Orbot can also use this
1788 option to instruct Tor to save power when the network is off.
1789 - Clients and bridges can now be configured to use a separate
1790 "transport" proxy. This approach makes the censorship arms race
1791 easier by allowing bridges to use protocol obfuscation plugins. It
1792 implements the "managed proxy" part of proposal 180 (ticket 3472).
1793 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
1794 implementation. It makes AES_CTR about 7% faster than our old one
1795 (which was about 10% faster than the one OpenSSL used to provide).
1796 Resolves ticket 4526.
1797 - Add a "tor2web mode" for clients that want to connect to hidden
1798 services non-anonymously (and possibly more quickly). As a safety
1799 measure to try to keep users from turning this on without knowing
1800 what they are doing, tor2web mode must be explicitly enabled at
1801 compile time, and a copy of Tor compiled to run in tor2web mode
1802 cannot be used as a normal Tor client. Implements feature 2553.
1803 - Add experimental support for running on Windows with IOCP and no
1804 kernel-space socket buffers. This feature is controlled by a new
1805 "UserspaceIOCPBuffers" config option (off by default), which has
1806 no effect unless Tor has been built with support for bufferevents,
1807 is running on Windows, and has enabled IOCP. This may, in the long
1808 run, help solve or mitigate bug 98.
1809 - Use a more secure consensus parameter voting algorithm. Now at
1810 least three directory authorities or a majority of them must
1811 vote on a given parameter before it will be included in the
1812 consensus. Implements proposal 178.
1815 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
1816 They used to check that the timestamp was within 30 minutes
1817 of their system clock, so they could cap the size of their
1818 replay-detection cache, but that approach unnecessarily refused
1819 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
1820 the v3 intro-point protocol (the first one which sent a timestamp
1821 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
1822 - Only use the EVP interface when AES acceleration is enabled,
1823 to avoid a 5-7% performance regression. Resolves issue 4525;
1824 bugfix on 0.2.3.8-alpha.
1826 o Privacy/anonymity features (bridge detection):
1827 - Make bridge SSL certificates a bit more stealthy by using random
1828 serial numbers, in the same fashion as OpenSSL when generating
1829 self-signed certificates. Implements ticket 4584.
1830 - Introduce a new config option "DynamicDHGroups", enabled by
1831 default, which provides each bridge with a unique prime DH modulus
1832 to be used during SSL handshakes. This option attempts to help
1833 against censors who might use the Apache DH modulus as a static
1834 identifier for bridges. Addresses ticket 4548.
1836 o Minor features (new/different config options):
1837 - New configuration option "DisableDebuggerAttachment" (on by default)
1838 to prevent basic debugging attachment attempts by other processes.
1839 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
1840 - Allow MapAddress directives to specify matches against super-domains,
1841 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
1842 Implements issue 933.
1843 - Slightly change behavior of "list" options (that is, config
1844 options that can appear more than once) when they appear both in
1845 torrc and on the command line. Previously, the command-line options
1846 would be appended to the ones from torrc. Now, the command-line
1847 options override the torrc options entirely. This new behavior
1848 allows the user to override list options (like exit policies and
1849 ports to listen on) from the command line, rather than simply
1850 appending to the list.
1851 - You can get the old (appending) command-line behavior for "list"
1852 options by prefixing the option name with a "+".
1853 - You can remove all the values for a "list" option from the command
1854 line without adding any new ones by prefixing the option name
1856 - Add experimental support for a "defaults" torrc file to be parsed
1857 before the regular torrc. Torrc options override the defaults file's
1858 options in the same way that the command line overrides the torrc.
1859 The SAVECONF controller command saves only those options which
1860 differ between the current configuration and the defaults file. HUP
1861 reloads both files. (Note: This is an experimental feature; its
1862 behavior will probably be refined in future 0.2.3.x-alpha versions
1863 to better meet packagers' needs.) Implements task 4552.
1866 - Try to make the introductory warning message that Tor prints on
1867 startup more useful for actually finding help and information.
1868 Resolves ticket 2474.
1869 - Running "make version" now displays the version of Tor that
1870 we're about to build. Idea from katmagic; resolves issue 4400.
1871 - Expire old or over-used hidden service introduction points.
1872 Required by fix for bug 3460.
1873 - Move the replay-detection cache for the RSA-encrypted parts of
1874 INTRODUCE2 cells to the introduction point data structures.
1875 Previously, we would use one replay-detection cache per hidden
1876 service. Required by fix for bug 3460.
1877 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
1878 public key replay-detection cache from 60 minutes to 5 minutes. This
1879 replay-detection cache is now used only to detect multiple
1880 INTRODUCE2 cells specifying the same rendezvous point, so we can
1881 avoid launching multiple simultaneous attempts to connect to it.
1883 o Minor bugfixes (on Tor 0.2.2.x and earlier):
1884 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1885 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1887 - Fix a minor formatting issue in one of tor-gencert's error messages.
1889 - Prevent a false positive from the check-spaces script, by disabling
1890 the "whitespace between function name and (" check for functions
1892 - Fix a log message suggesting that people contact a non-existent
1893 email address. Fixes bug 3448.
1894 - Fix null-pointer access that could occur if TLS allocation failed.
1895 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1896 - Report a real bootstrap problem to the controller on router
1897 identity mismatch. Previously we just said "foo", which probably
1898 made a lot of sense at the time. Fixes bug 4169; bugfix on
1900 - If we had ever tried to call tor_addr_to_str() on an address of
1901 unknown type, we would have done a strdup() on an uninitialized
1902 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1903 Reported by "troll_un".
1904 - Correctly detect and handle transient lookup failures from
1905 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1906 Reported by "troll_un".
1907 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1908 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1909 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
1910 bug 4532; found by "troll_un".
1912 o Minor bugfixes (on Tor 0.2.3.x):
1913 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
1915 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
1916 circuit for use as a hidden service client's rendezvous point.
1917 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
1918 with help from wanoskarnet.
1919 - Restore behavior of overriding SocksPort, ORPort, and similar
1920 options from the command line. Bugfix on 0.2.3.3-alpha.
1923 - Properly handle the case where the build-tree is not the same
1924 as the source tree when generating src/common/common_sha1.i,
1925 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
1926 bugfix on 0.2.0.1-alpha.
1928 o Code simplifications, cleanups, and refactorings:
1929 - Remove the pure attribute from all functions that used it
1930 previously. In many cases we assigned it incorrectly, because the
1931 functions might assert or call impure functions, and we don't have
1932 evidence that keeping the pure attribute is worthwhile. Implements
1933 changes suggested in ticket 4421.
1934 - Remove some dead code spotted by coverity. Fixes cid 432.
1935 Bugfix on 0.2.3.1-alpha, closes bug 4637.
1938 Changes in version 0.2.3.8-alpha - 2011-11-22
1939 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
1940 socketpair-related bug that has been bothering Windows users. It adds
1941 support to serve microdescriptors to controllers, so Vidalia's network
1942 map can resume listing relays (once Vidalia implements its side),
1943 and adds better support for hardware AES acceleration. Finally, it
1944 starts the process of adjusting the bandwidth cutoff for getting the
1945 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
1946 that tiny relays harm performance more than they help network capacity.
1949 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1950 that it doesn't attempt to allocate a socketpair. This could cause
1951 some problems on Windows systems with overzealous firewalls. Fix for
1952 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1954 - Correctly sanity-check that we don't underflow on a memory
1955 allocation (and then assert) for hidden service introduction
1956 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1957 bugfix on 0.2.1.5-alpha.
1958 - Remove the artificially low cutoff of 20KB to guarantee the Fast
1959 flag. In the past few years the average relay speed has picked
1960 up, and while the "top 7/8 of the network get the Fast flag" and
1961 "all relays with 20KB or more of capacity get the Fast flag" rules
1962 used to have the same result, now the top 7/8 of the network has
1963 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
1964 - Fix a rare assertion failure when checking whether a v0 hidden
1965 service descriptor has any usable introduction points left, and
1966 we don't have enough information to build a circuit to the first
1967 intro point named in the descriptor. The HS client code in
1968 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
1969 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
1970 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
1971 - Make bridge authorities not crash when they are asked for their own
1972 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
1973 - When running as a client, do not print a misleading (and plain
1974 wrong) log message that we're collecting "directory request"
1975 statistics: clients don't collect statistics. Also don't create a
1976 useless (because empty) stats file in the stats/ directory. Fixes
1977 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
1980 - Allow Tor controllers like Vidalia to obtain the microdescriptor
1981 for a relay by identity digest or nickname. Previously,
1982 microdescriptors were only available by their own digests, so a
1983 controller would have to ask for and parse the whole microdescriptor
1984 consensus in order to look up a single relay's microdesc. Fixes
1985 bug 3832; bugfix on 0.2.3.1-alpha.
1986 - Use OpenSSL's EVP interface for AES encryption, so that all AES
1987 operations can use hardware acceleration (if present). Resolves
1990 o Minor bugfixes (on 0.2.2.x and earlier):
1991 - Detect failure to initialize Libevent. This fix provides better
1992 detection for future instances of bug 4457.
1993 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1994 function. This was eating up hideously large amounts of time on some
1995 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1996 - Don't warn about unused log_mutex in log.c when building with
1997 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1998 0.1.0.6-rc which introduced --disable-threads.
1999 - Allow manual 'authenticate' commands to the controller interface
2000 from netcat (nc) as well as telnet. We were rejecting them because
2001 they didn't come with the expected whitespace at the end of the
2002 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
2003 - Fix some (not actually triggerable) buffer size checks in usage of
2004 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
2006 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
2007 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
2008 - When configuring, starting, or stopping an NT service, stop
2009 immediately after the service configuration attempt has succeeded
2010 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
2011 - When sending a NETINFO cell, include the original address
2012 received for the other side, not its canonical address. Found
2013 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
2014 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
2015 can pick them up when the tests aren't disabled. Bugfix on
2016 0.2.2.4-alpha which introduced tinytest.
2017 - Fix a memory leak when we check whether a hidden service
2018 descriptor has any usable introduction points left. Fixes bug
2019 4424. Bugfix on 0.2.2.25-alpha.
2020 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
2021 occurred when a client tried to fetch a descriptor for a bridge
2022 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
2024 o Minor bugfixes (on 0.2.3.x):
2025 - Make util unit tests build correctly with MSVC. Bugfix on
2026 0.2.3.3-alpha. Patch by Gisle Vanem.
2027 - Successfully detect AUTH_CHALLENGE cells with no recognized
2028 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
2030 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
2031 it should still send a NETINFO cell to allow the connection to
2032 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
2034 - Log less loudly when we get an invalid authentication certificate
2035 from a source other than a directory authority: it's not unusual
2036 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
2038 - Tolerate servers with more clock skew in their authentication
2039 certificates than previously. Fixes bug 4371; bugfix on
2041 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
2042 on 0.2.3.4-alpha and 0.2.3.6-alpha.
2045 - Add two new config options for directory authorities:
2046 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
2047 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
2048 that is always sufficient to satisfy the bandwidth requirement for
2049 the Guard flag. Now it will be easier for researchers to simulate
2050 Tor networks with different values. Resolves ticket 4484.
2051 - When Tor ignores a hidden service specified in its configuration,
2052 include the hidden service's directory in the warning message.
2053 Previously, we would only tell the user that some hidden service
2054 was ignored. Bugfix on 0.0.6; fixes bug 4426.
2055 - When we fail to initialize Libevent, retry with IOCP disabled so we
2056 don't need to turn on multi-threading support in Libevent, which in
2057 turn requires a working socketpair(). This is a workaround for bug
2058 4457, which affects Libevent versions from 2.0.1-alpha through
2060 - Detect when we try to build on a platform that doesn't define
2061 AF_UNSPEC to 0. We don't work there, so refuse to compile.
2062 - Update to the November 1 2011 Maxmind GeoLite Country database.
2064 o Packaging changes:
2065 - Make it easier to automate expert package builds on Windows,
2066 by removing an absolute path from makensis.exe command.
2068 o Code simplifications and refactoring:
2069 - Remove some redundant #include directives throughout the code.
2070 Patch from Andrea Gelmini.
2071 - Unconditionally use OpenSSL's AES implementation instead of our
2072 old built-in one. OpenSSL's AES has been better for a while, and
2073 relatively few servers should still be on any version of OpenSSL
2074 that doesn't have good optimized assembly AES.
2075 - Use the name "CERTS" consistently to refer to the new cell type;
2076 we were calling it CERT in some places and CERTS in others.
2079 - Numerous new unit tests for functions in util.c and address.c by
2081 - The long-disabled benchmark tests are now split into their own
2082 ./src/test/bench binary.
2083 - The benchmark tests can now use more accurate timers than
2084 gettimeofday() when such timers are available.
2087 Changes in version 0.2.3.7-alpha - 2011-10-30
2088 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
2089 the new v3 handshake. It also resolves yet another bridge address
2093 - If we mark an OR connection for close based on a cell we process,
2094 don't process any further cells on it. We already avoid further
2095 reads on marked-for-close connections, but now we also discard the
2096 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
2097 which was the first version where we might mark a connection for
2098 close based on processing a cell on it.
2099 - Fix a double-free bug that would occur when we received an invalid
2100 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
2101 bugfix on 0.2.3.6-alpha.
2102 - Bridges no longer include their address in NETINFO cells on outgoing
2103 OR connections, to allow them to blend in better with clients.
2104 Removes another avenue for enumerating bridges. Reported by
2105 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
2106 cells were introduced.
2109 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
2110 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
2113 Changes in version 0.2.3.6-alpha - 2011-10-26
2114 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
2115 anonymity vulnerability where an attacker can deanonymize Tor
2116 users. Everybody should upgrade.
2118 This release also features support for a new v3 connection handshake
2119 protocol, and fixes to make hidden service connections more robust.
2122 - Implement a new handshake protocol (v3) for authenticating Tors to
2123 each other over TLS. It should be more resistant to fingerprinting
2124 than previous protocols, and should require less TLS hacking for
2125 future Tor implementations. Implements proposal 176.
2126 - Allow variable-length padding cells to disguise the length of
2127 Tor's TLS records. Implements part of proposal 184.
2129 o Privacy/anonymity fixes (clients):
2130 - Clients and bridges no longer send TLS certificate chains on
2131 outgoing OR connections. Previously, each client or bridge would
2132 use the same cert chain for all outgoing OR connections until
2133 its IP address changes, which allowed any relay that the client
2134 or bridge contacted to determine which entry guards it is using.
2135 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2136 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2137 no longer considers that connection as suitable for satisfying a
2138 circuit EXTEND request. Now relays can protect clients from the
2139 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2140 - Directory authorities no longer assign the Guard flag to relays
2141 that haven't upgraded to the above "refuse EXTEND requests
2142 to client connections" fix. Now directory authorities can
2143 protect clients from the CVE-2011-2768 issue even if neither
2144 the clients nor the relays have upgraded yet. There's a new
2145 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
2146 to let us transition smoothly, else tomorrow there would be no
2149 o Major bugfixes (hidden services):
2150 - Improve hidden service robustness: when an attempt to connect to
2151 a hidden service ends, be willing to refetch its hidden service
2152 descriptors from each of the HSDir relays responsible for them
2153 immediately. Previously, we would not consider refetching the
2154 service's descriptors from each HSDir for 15 minutes after the last
2155 fetch, which was inconvenient if the hidden service was not running
2156 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
2157 - When one of a hidden service's introduction points appears to be
2158 unreachable, stop trying it. Previously, we would keep trying
2159 to build circuits to the introduction point until we lost the
2160 descriptor, usually because the user gave up and restarted Tor.
2161 Partly fixes bug 3825.
2162 - Don't launch a useless circuit after failing to use one of a
2163 hidden service's introduction points. Previously, we would
2164 launch a new introduction circuit, but not set the hidden service
2165 which that circuit was intended to connect to, so it would never
2166 actually be used. A different piece of code would then create a
2167 new introduction circuit correctly. Bug reported by katmagic and
2168 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
2170 o Major bugfixes (other):
2171 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2172 that they initiated. Relays could distinguish incoming bridge
2173 connections from client connections, creating another avenue for
2174 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2175 Found by "frosty_un".
2176 - Don't update the AccountingSoftLimitHitAt state file entry whenever
2177 tor gets started. This prevents a wrong average bandwidth
2178 estimate, which would cause relays to always start a new accounting
2179 interval at the earliest possible moment. Fixes bug 2003; bugfix
2180 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
2181 immensely in tracking this bug down.
2182 - Fix a crash bug when changing node restrictions while a DNS lookup
2183 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
2186 o Minor bugfixes (on 0.2.2.x and earlier):
2187 - When a hidden service turns an extra service-side introduction
2188 circuit into a general-purpose circuit, free the rend_data and
2189 intro_key fields first, so we won't leak memory if the circuit
2190 is cannibalized for use as another service-side introduction
2191 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
2192 - Rephrase the log message emitted if the TestSocks check is
2193 successful. Patch from Fabian Keil; fixes bug 4094.
2194 - Bridges now skip DNS self-tests, to act a little more stealthily.
2195 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
2196 bridges. Patch by "warms0x".
2197 - Remove a confusing dollar sign from the example fingerprint in the
2198 man page, and also make the example fingerprint a valid one. Fixes
2199 bug 4309; bugfix on 0.2.1.3-alpha.
2200 - Fix internal bug-checking logic that was supposed to catch
2201 failures in digest generation so that it will fail more robustly
2202 if we ask for a nonexistent algorithm. Found by Coverity Scan.
2203 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
2204 - Report any failure in init_keys() calls launched because our
2205 IP address has changed. Spotted by Coverity Scan. Bugfix on
2206 0.1.1.4-alpha; fixes CID 484.
2208 o Minor bugfixes (on 0.2.3.x):
2209 - Fix a bug in configure.in that kept it from building a configure
2210 script with autoconf versions earlier than 2.61. Fixes bug 2430;
2211 bugfix on 0.2.3.1-alpha.
2212 - Don't warn users that they are exposing a client port to the
2213 Internet if they have specified an RFC1918 address. Previously,
2214 we would warn if the user had specified any non-loopback
2215 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
2216 - Fix memory leaks in the failing cases of the new SocksPort and
2217 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
2218 fixes coverity CIDs 485, 486, and 487.
2221 - When a hidden service's introduction point times out, consider
2222 trying it again during the next attempt to connect to the
2223 HS. Previously, we would not try it again unless a newly fetched
2224 descriptor contained it. Required by fixes for bugs 1297 and 3825.
2225 - The next version of Windows will be called Windows 8, and it has
2226 a major version of 6, minor version of 2. Correctly identify that
2227 version instead of calling it "Very recent version". Resolves
2228 ticket 4153; reported by funkstar.
2229 - The Bridge Authority now writes statistics on how many bridge
2230 descriptors it gave out in total, and how many unique descriptors
2231 it gave out. It also lists how often the most and least commonly
2232 fetched descriptors were given out, as well as the median and
2233 25th/75th percentile. Implements tickets 4200 and 4294.
2234 - Update to the October 4 2011 Maxmind GeoLite Country database.
2236 o Code simplifications and refactoring:
2237 - Remove some old code to remember statistics about which descriptors
2238 we've served as a directory mirror. The feature wasn't used and
2239 is outdated now that microdescriptors are around.
2240 - Rename Tor functions that turn strings into addresses, so that
2241 "parse" indicates that no hostname resolution occurs, and
2242 "lookup" indicates that hostname resolution may occur. This
2243 should help prevent mistakes in the future. Fixes bug 3512.
2246 Changes in version 0.2.2.34 - 2011-10-26
2247 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
2248 can deanonymize Tor users. Everybody should upgrade.
2250 The attack relies on four components: 1) Clients reuse their TLS cert
2251 when talking to different relays, so relays can recognize a user by
2252 the identity key in her cert. 2) An attacker who knows the client's
2253 identity key can probe each guard relay to see if that identity key
2254 is connected to that guard relay right now. 3) A variety of active
2255 attacks in the literature (starting from "Low-Cost Traffic Analysis
2256 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
2257 discover the guard relays that a Tor user visiting the website is using.
2258 4) Clients typically pick three guards at random, so the set of guards
2259 for a given user could well be a unique fingerprint for her. This
2260 release fixes components #1 and #2, which is enough to block the attack;
2261 the other two remain as open research problems. Special thanks to
2262 "frosty_un" for reporting the issue to us!
2264 Clients should upgrade so they are no longer recognizable by the TLS
2265 certs they present. Relays should upgrade so they no longer allow a
2266 remote attacker to probe them to test whether unpatched clients are
2267 currently connected to them.
2269 This release also fixes several vulnerabilities that allow an attacker
2270 to enumerate bridge relays. Some bridge enumeration attacks still
2271 remain; see for example proposal 188.
2273 o Privacy/anonymity fixes (clients):
2274 - Clients and bridges no longer send TLS certificate chains on
2275 outgoing OR connections. Previously, each client or bridge would
2276 use the same cert chain for all outgoing OR connections until
2277 its IP address changes, which allowed any relay that the client
2278 or bridge contacted to determine which entry guards it is using.
2279 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2280 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2281 no longer considers that connection as suitable for satisfying a
2282 circuit EXTEND request. Now relays can protect clients from the
2283 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2284 - Directory authorities no longer assign the Guard flag to relays
2285 that haven't upgraded to the above "refuse EXTEND requests
2286 to client connections" fix. Now directory authorities can
2287 protect clients from the CVE-2011-2768 issue even if neither
2288 the clients nor the relays have upgraded yet. There's a new
2289 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
2290 to let us transition smoothly, else tomorrow there would be no
2293 o Privacy/anonymity fixes (bridge enumeration):
2294 - Bridge relays now do their directory fetches inside Tor TLS
2295 connections, like all the other clients do, rather than connecting
2296 directly to the DirPort like public relays do. Removes another
2297 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
2298 - Bridges relays now build circuits for themselves in a more similar
2299 way to how clients build them. Removes another avenue for
2300 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
2301 when bridges were introduced.
2302 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2303 that they initiated. Relays could distinguish incoming bridge
2304 connections from client connections, creating another avenue for
2305 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2306 Found by "frosty_un".
2309 - Fix a crash bug when changing node restrictions while a DNS lookup
2310 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
2312 - Don't launch a useless circuit after failing to use one of a
2313 hidden service's introduction points. Previously, we would
2314 launch a new introduction circuit, but not set the hidden service
2315 which that circuit was intended to connect to, so it would never
2316 actually be used. A different piece of code would then create a
2317 new introduction circuit correctly. Bug reported by katmagic and
2318 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
2321 - Change an integer overflow check in the OpenBSD_Malloc code so
2322 that GCC is less likely to eliminate it as impossible. Patch
2323 from Mansour Moufid. Fixes bug 4059.
2324 - When a hidden service turns an extra service-side introduction
2325 circuit into a general-purpose circuit, free the rend_data and
2326 intro_key fields first, so we won't leak memory if the circuit
2327 is cannibalized for use as another service-side introduction
2328 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
2329 - Bridges now skip DNS self-tests, to act a little more stealthily.
2330 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
2331 bridges. Patch by "warms0x".
2332 - Fix internal bug-checking logic that was supposed to catch
2333 failures in digest generation so that it will fail more robustly
2334 if we ask for a nonexistent algorithm. Found by Coverity Scan.
2335 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
2336 - Report any failure in init_keys() calls launched because our
2337 IP address has changed. Spotted by Coverity Scan. Bugfix on
2338 0.1.1.4-alpha; fixes CID 484.
2340 o Minor bugfixes (log messages and documentation):
2341 - Remove a confusing dollar sign from the example fingerprint in the
2342 man page, and also make the example fingerprint a valid one. Fixes
2343 bug 4309; bugfix on 0.2.1.3-alpha.
2344 - The next version of Windows will be called Windows 8, and it has
2345 a major version of 6, minor version of 2. Correctly identify that
2346 version instead of calling it "Very recent version". Resolves
2347 ticket 4153; reported by funkstar.
2348 - Downgrade log messages about circuit timeout calibration from
2349 "notice" to "info": they don't require or suggest any human
2350 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
2351 bugfix on 0.2.2.14-alpha.
2354 - Turn on directory request statistics by default and include them in
2355 extra-info descriptors. Don't break if we have no GeoIP database.
2356 Backported from 0.2.3.1-alpha; implements ticket 3951.
2357 - Update to the October 4 2011 Maxmind GeoLite Country database.
2360 Changes in version 0.2.1.31 - 2011-10-26
2361 Tor 0.2.1.31 backports important security and privacy fixes for
2362 oldstable. This release is intended only for package maintainers and
2363 others who cannot use the 0.2.2 stable series. All others should be
2364 using Tor 0.2.2.x or newer.
2366 o Security fixes (also included in 0.2.2.x):
2367 - Replace all potentially sensitive memory comparison operations
2368 with versions whose runtime does not depend on the data being
2369 compared. This will help resist a class of attacks where an
2370 adversary can use variations in timing information to learn
2371 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2372 implementation by Robert Ransom based partially on code by DJB.)
2373 - Fix an assert in parsing router descriptors containing IPv6
2374 addresses. This one took down the directory authorities when
2375 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
2377 o Privacy/anonymity fixes (also included in 0.2.2.x):
2378 - Clients and bridges no longer send TLS certificate chains on
2379 outgoing OR connections. Previously, each client or bridge would
2380 use the same cert chain for all outgoing OR connections until
2381 its IP address changes, which allowed any relay that the client
2382 or bridge contacted to determine which entry guards it is using.
2383 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2384 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2385 no longer considers that connection as suitable for satisfying a
2386 circuit EXTEND request. Now relays can protect clients from the
2387 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2388 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2389 that they initiated. Relays could distinguish incoming bridge
2390 connections from client connections, creating another avenue for
2391 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2392 Found by "frosty_un".
2393 - When receiving a hidden service descriptor, check that it is for
2394 the hidden service we wanted. Previously, Tor would store any
2395 hidden service descriptors that a directory gave it, whether it
2396 wanted them or not. This wouldn't have let an attacker impersonate
2397 a hidden service, but it did let directories pre-seed a client
2398 with descriptors that it didn't want. Bugfix on 0.0.6.
2399 - Avoid linkability based on cached hidden service descriptors: forget
2400 all hidden service descriptors cached as a client when processing a
2401 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
2402 - Make the bridge directory authority refuse to answer directory
2403 requests for "all" descriptors. It used to include bridge
2404 descriptors in its answer, which was a major information leak.
2405 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
2406 - Don't attach new streams to old rendezvous circuits after SIGNAL
2407 NEWNYM. Previously, we would keep using an existing rendezvous
2408 circuit if it remained open (i.e. if it were kept open by a
2409 long-lived stream, or if a new stream were attached to it before
2410 Tor could notice that it was old and no longer in use). Bugfix on
2411 0.1.1.15-rc; fixes bug 3375.
2413 o Minor bugfixes (also included in 0.2.2.x):
2414 - When we restart our relay, we might get a successful connection
2415 from the outside before we've started our reachability tests,
2416 triggering a warning: "ORPort found reachable, but I have no
2417 routerinfo yet. Failing to inform controller of success." This
2418 bug was harmless unless Tor is running under a controller
2419 like Vidalia, in which case the controller would never get a
2420 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
2422 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
2423 enabled. Fixes bug 1526.
2424 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2425 anything since 0.2.1.16-rc.
2426 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
2427 None of the cases where we did this before were wrong, but by making
2428 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
2429 - Fix a rare crash bug that could occur when a client was configured
2430 with a large number of bridges. Fixes bug 2629; bugfix on
2431 0.2.1.2-alpha. Bugfix by trac user "shitlei".
2432 - Correct the warning displayed when a rendezvous descriptor exceeds
2433 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
2435 - Fix an uncommon assertion failure when running with DNSPort under
2436 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
2437 - When warning about missing zlib development packages during compile,
2438 give the correct package names. Bugfix on 0.2.0.1-alpha.
2439 - Require that introduction point keys and onion keys have public
2440 exponent 65537. Bugfix on 0.2.0.10-alpha.
2441 - Do not crash when our configuration file becomes unreadable, for
2442 example due to a permissions change, between when we start up
2443 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2445 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2447 - Always NUL-terminate the sun_path field of a sockaddr_un before
2448 passing it to the kernel. (Not a security issue: kernels are
2449 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2450 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2451 - Don't stack-allocate the list of supplementary GIDs when we're
2452 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2453 could take up to 256K, which is way too much stack. Found by
2454 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2456 o Minor bugfixes (only in 0.2.1.x):
2457 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
2458 rely on them. Bugfix on 0.2.1.30.
2459 - Use git revisions instead of svn revisions when generating our
2460 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
2462 o Minor features (also included in 0.2.2.x):
2463 - Adjust the expiration time on our SSL session certificates to
2464 better match SSL certs seen in the wild. Resolves ticket 4014.
2465 - Allow nameservers with IPv6 address. Resolves bug 2574.
2466 - Update to the October 4 2011 Maxmind GeoLite Country database.
2469 Changes in version 0.2.3.5-alpha - 2011-09-28
2470 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
2471 bridge relays; fixes an assertion error that many users started hitting
2472 today; and adds the ability to refill token buckets more often than
2473 once per second, allowing significant performance improvements.
2476 - Bridge relays now do their directory fetches inside Tor TLS
2477 connections, like all the other clients do, rather than connecting
2478 directly to the DirPort like public relays do. Removes another
2479 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
2480 - Bridges relays now build circuits for themselves in a more similar
2481 way to how clients build them. Removes another avenue for
2482 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
2483 when bridges were introduced.
2486 - Fix an "Assertion md->held_by_node == 1 failed" error that could
2487 occur when the same microdescriptor was referenced by two node_t
2488 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
2490 o Major features (networking):
2491 - Add a new TokenBucketRefillInterval option to refill token buckets
2492 more frequently than once per second. This should improve network
2493 performance, alleviate queueing problems, and make traffic less
2494 bursty. Implements proposal 183; closes ticket 3630. Design by
2495 Florian Tschorsch and Björn Scheuermann; implementation by
2499 - Change an integer overflow check in the OpenBSD_Malloc code so
2500 that GCC is less likely to eliminate it as impossible. Patch
2501 from Mansour Moufid. Fixes bug 4059.
2503 o Minor bugfixes (usability):
2504 - Downgrade log messages about circuit timeout calibration from
2505 "notice" to "info": they don't require or suggest any human
2506 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
2507 bugfix on 0.2.2.14-alpha.
2509 o Minor features (diagnostics):
2510 - When the system call to create a listener socket fails, log the
2511 error message explaining why. This may help diagnose bug 4027.
2514 Changes in version 0.2.3.4-alpha - 2011-09-13
2515 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
2516 tweak to Tor's TLS handshake that makes relays and bridges that run
2517 this new version reachable from Iran again. It also fixes a few new
2518 bugs in 0.2.3.x, and teaches relays to recognize when they're not
2519 listed in the network consensus and republish.
2521 o Major bugfixes (also part of 0.2.2.33):
2522 - Avoid an assertion failure when reloading a configuration with
2523 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2524 3923; bugfix on 0.2.2.25-alpha.
2526 o Minor features (security, also part of 0.2.2.33):
2527 - Check for replays of the public-key encrypted portion of an
2528 INTRODUCE1 cell, in addition to the current check for replays of
2529 the g^x value. This prevents a possible class of active attacks
2530 by an attacker who controls both an introduction point and a
2531 rendezvous point, and who uses the malleability of AES-CTR to
2532 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2533 that these attacks is infeasible (requiring the attacker to send
2534 on the order of zettabytes of altered cells in a short interval),
2535 but we'd rather block them off in case there are any classes of
2536 this attack that we missed. Reported by Willem Pinckaers.
2538 o Minor features (also part of 0.2.2.33):
2539 - Adjust the expiration time on our SSL session certificates to
2540 better match SSL certs seen in the wild. Resolves ticket 4014.
2541 - Change the default required uptime for a relay to be accepted as
2542 a HSDir (hidden service directory) from 24 hours to 25 hours.
2543 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2544 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2545 authorities to abstain from voting on assignment of the HSDir
2546 consensus flag. Related to bug 2649.
2547 - Update to the September 6 2011 Maxmind GeoLite Country database.
2549 o Minor bugfixes (also part of 0.2.2.33):
2550 - Demote the 'replay detected' log message emitted when a hidden
2551 service receives the same Diffie-Hellman public key in two different
2552 INTRODUCE2 cells to info level. A normal Tor client can cause that
2553 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2554 fixes part of bug 2442.
2555 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2556 level. There is nothing that a hidden service's operator can do
2557 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2559 - Clarify a log message specifying the characters permitted in
2560 HiddenServiceAuthorizeClient client names. Previously, the log
2561 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2562 given the impression that every ASCII character between "+" and "_"
2563 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2565 o Build fixes (also part of 0.2.2.33):
2566 - Clean up some code issues that prevented Tor from building on older
2567 BSDs. Fixes bug 3894; reported by "grarpamp".
2568 - Search for a platform-specific version of "ar" when cross-compiling.
2569 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2572 - Fix a bug where the SocksPort option (for example) would get
2573 ignored and replaced by the default if a SocksListenAddress
2574 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
2578 - Relays now try regenerating and uploading their descriptor more
2579 frequently if they are not listed in the consensus, or if the
2580 version of their descriptor listed in the consensus is too
2581 old. This fix should prevent situations where a server declines
2582 to re-publish itself because it has done so too recently, even
2583 though the authorities decided not to list its recent-enough
2584 descriptor. Fix for bug 3327.
2587 - Relays now include a reason for regenerating their descriptors
2588 in an HTTP header when uploading to the authorities. This will
2589 make it easier to debug descriptor-upload issues in the future.
2590 - When starting as root and then changing our UID via the User
2591 control option, and we have a ControlSocket configured, make sure
2592 that the ControlSocket is owned by the same account that Tor will
2593 run under. Implements ticket 3421; fix by Jérémy Bobbio.
2596 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
2597 utility function used in the control-port code). This shouldn't
2598 ever happen unless Tor is completely out of memory, but if it did
2599 happen and Tor somehow recovered from it, Tor could have sent a log
2600 message to a control port in the middle of a reply to a controller
2601 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
2602 - Make 'FetchUselessDescriptors' cause all descriptor types and
2603 all consensus types (including microdescriptors) to get fetched.
2604 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
2607 - Make a new "entry connection" struct as an internal subtype of "edge
2608 connection", to simplify the code and make exit connections smaller.
2611 Changes in version 0.2.2.33 - 2011-09-13
2612 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
2613 TLS handshake that makes relays and bridges that run this new version
2614 reachable from Iran again.
2617 - Avoid an assertion failure when reloading a configuration with
2618 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2619 3923; bugfix on 0.2.2.25-alpha.
2621 o Minor features (security):
2622 - Check for replays of the public-key encrypted portion of an
2623 INTRODUCE1 cell, in addition to the current check for replays of
2624 the g^x value. This prevents a possible class of active attacks
2625 by an attacker who controls both an introduction point and a
2626 rendezvous point, and who uses the malleability of AES-CTR to
2627 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2628 that these attacks are infeasible (requiring the attacker to send
2629 on the order of zettabytes of altered cells in a short interval),
2630 but we'd rather block them off in case there are any classes of
2631 this attack that we missed. Reported by Willem Pinckaers.
2634 - Adjust the expiration time on our SSL session certificates to
2635 better match SSL certs seen in the wild. Resolves ticket 4014.
2636 - Change the default required uptime for a relay to be accepted as
2637 a HSDir (hidden service directory) from 24 hours to 25 hours.
2638 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2639 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2640 authorities to abstain from voting on assignment of the HSDir
2641 consensus flag. Related to bug 2649.
2642 - Update to the September 6 2011 Maxmind GeoLite Country database.
2644 o Minor bugfixes (documentation and log messages):
2645 - Correct the man page to explain that HashedControlPassword and
2646 CookieAuthentication can both be set, in which case either method
2647 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2648 when we decided to allow these config options to both be set. Issue
2650 - Demote the 'replay detected' log message emitted when a hidden
2651 service receives the same Diffie-Hellman public key in two different
2652 INTRODUCE2 cells to info level. A normal Tor client can cause that
2653 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2654 fixes part of bug 2442.
2655 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2656 level. There is nothing that a hidden service's operator can do
2657 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2659 - Clarify a log message specifying the characters permitted in
2660 HiddenServiceAuthorizeClient client names. Previously, the log
2661 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2662 given the impression that every ASCII character between "+" and "_"
2663 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2666 - Provide a substitute implementation of lround() for MSVC, which
2667 apparently lacks it. Patch from Gisle Vanem.
2668 - Clean up some code issues that prevented Tor from building on older
2669 BSDs. Fixes bug 3894; reported by "grarpamp".
2670 - Search for a platform-specific version of "ar" when cross-compiling.
2671 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2674 Changes in version 0.2.3.3-alpha - 2011-09-01
2675 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
2676 security, and provides client-side support for the microdescriptor
2677 and optimistic data features introduced earlier in the 0.2.3.x
2678 series. It also includes numerous critical bugfixes in the (optional)
2679 bufferevent-based networking backend.
2681 o Major features (stream isolation):
2682 - You can now configure Tor so that streams from different
2683 applications are isolated on different circuits, to prevent an
2684 attacker who sees your streams as they leave an exit node from
2685 linking your sessions to one another. To do this, choose some way
2686 to distinguish the applications: have them connect to different
2687 SocksPorts, or have one of them use SOCKS4 while the other uses
2688 SOCKS5, or have them pass different authentication strings to the
2689 SOCKS proxy. Then, use the new SocksPort syntax to configure the
2690 degree of isolation you need. This implements Proposal 171.
2691 - There's a new syntax for specifying multiple client ports (such as
2692 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
2693 multiple *Port entries with full addr:port syntax on each.
2694 The old *ListenAddress format is still supported, but you can't
2695 mix it with the new *Port syntax.
2697 o Major features (other):
2698 - Enable microdescriptor fetching by default for clients. This allows
2699 clients to download a much smaller amount of directory information.
2700 To disable it (and go back to the old-style consensus and
2701 descriptors), set "UseMicrodescriptors 0" in your torrc file.
2702 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
2703 "PortForwarding" config option), now supports Windows.
2704 - When using an exit relay running 0.2.3.x, clients can now
2705 "optimistically" send data before the exit relay reports that
2706 the stream has opened. This saves a round trip when starting
2707 connections where the client speaks first (such as web browsing).
2708 This behavior is controlled by a consensus parameter (currently
2709 disabled). To turn it on or off manually, use the "OptimisticData"
2710 torrc option. Implements proposal 181; code by Ian Goldberg.
2712 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
2713 - When using IOCP on Windows, we need to enable Libevent windows
2715 - The IOCP backend now works even when the user has not specified
2716 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
2717 Fixes part of bug 3752.
2718 - Correctly record the bytes we've read and written when using
2719 bufferevents, so that we can include them in our bandwidth history
2720 and advertised bandwidth. Fixes bug 3803.
2721 - Apply rate-limiting only at the bottom of a chain of filtering
2722 bufferevents. This prevents us from filling up internal read
2723 buffers and violating rate-limits when filtering bufferevents
2724 are enabled. Fixes part of bug 3804.
2725 - Add high-watermarks to the output buffers for filtered
2726 bufferevents. This prevents us from filling up internal write
2727 buffers and wasting CPU cycles when filtering bufferevents are
2728 enabled. Fixes part of bug 3804.
2729 - Correctly notice when data has been written from a bufferevent
2730 without flushing it completely. Fixes bug 3805.
2731 - Fix a bug where server-side tunneled bufferevent-based directory
2732 streams would get closed prematurely. Fixes bug 3814.
2733 - Fix a use-after-free error with per-connection rate-limiting
2734 buckets. Fixes bug 3888.
2736 o Major bugfixes (also part of 0.2.2.31-rc):
2737 - If we're configured to write our ControlPorts to disk, only write
2738 them after switching UID and creating the data directory. This way,
2739 we don't fail when starting up with a nonexistent DataDirectory
2740 and a ControlPortWriteToFile setting based on that directory. Fixes
2741 bug 3747; bugfix on Tor 0.2.2.26-beta.
2744 - Added a new CONF_CHANGED event so that controllers can be notified
2745 of any configuration changes made by other controllers, or by the
2746 user. Implements ticket 1692.
2747 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
2748 leak when using bufferevents, and lets Libevent worry about how to
2749 best copy data out of a buffer.
2750 - Replace files in stats/ rather than appending to them. Now that we
2751 include statistics in extra-info descriptors, it makes no sense to
2752 keep old statistics forever. Implements ticket 2930.
2754 o Minor features (build compatibility):
2755 - Limited, experimental support for building with nmake and MSVC.
2756 - Provide a substitute implementation of lround() for MSVC, which
2757 apparently lacks it. Patch from Gisle Vanem.
2759 o Minor features (also part of 0.2.2.31-rc):
2760 - Update to the August 2 2011 Maxmind GeoLite Country database.
2762 o Minor bugfixes (on 0.2.3.x-alpha):
2763 - Fix a spurious warning when parsing SOCKS requests with
2764 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
2765 - Get rid of a harmless warning that could happen on relays running
2766 with bufferevents. The warning was caused by someone doing an http
2767 request to a relay's orport. Also don't warn for a few related
2768 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
2770 o Minor bugfixes (on 2.2.x and earlier):
2771 - Correct the man page to explain that HashedControlPassword and
2772 CookieAuthentication can both be set, in which case either method
2773 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2774 when we decided to allow these config options to both be set. Issue
2776 - The "--quiet" and "--hush" options now apply not only to Tor's
2777 behavior before logs are configured, but also to Tor's behavior in
2778 the absense of configured logs. Fixes bug 3550; bugfix on
2781 o Minor bugfixes (also part of 0.2.2.31-rc):
2782 - Write several files in text mode, on OSes that distinguish text
2783 mode from binary mode (namely, Windows). These files are:
2784 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2785 that collect those statistics; 'client_keys' and 'hostname' for
2786 hidden services that use authentication; and (in the tor-gencert
2787 utility) newly generated identity and signing keys. Previously,
2788 we wouldn't specify text mode or binary mode, leading to an
2789 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2790 the DirRecordUsageByCountry option which would have triggered
2791 the assertion failure was added), although this assertion failure
2792 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2793 - Selectively disable deprecation warnings on OS X because Lion
2794 started deprecating the shipped copy of openssl. Fixes bug 3643.
2795 - Remove an extra pair of quotation marks around the error
2796 message in control-port STATUS_GENERAL BUG events. Bugfix on
2797 0.1.2.6-alpha; fixes bug 3732.
2798 - When unable to format an address as a string, report its value
2799 as "???" rather than reusing the last formatted address. Bugfix
2802 o Code simplifications and refactoring:
2803 - Rewrite the listener-selection logic so that parsing which ports
2804 we want to listen on is now separate from binding to the ports
2808 - Building Tor with bufferevent support now requires Libevent
2809 2.0.13-stable or later. Previous versions of Libevent had bugs in
2810 SSL-related bufferevents and related issues that would make Tor
2811 work badly with bufferevents. Requiring 2.0.13-stable also allows
2812 Tor with bufferevents to take advantage of Libevent APIs
2813 introduced after 2.0.8-rc.
2816 Changes in version 0.2.2.32 - 2011-08-27
2817 The Tor 0.2.2 release series is dedicated to the memory of Andreas
2818 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
2819 a founder of the PETS community, a leader in our field, a mentor,
2820 and a friend. He left us with these words: "I had the possibility
2821 to contribute to this world that is not as it should be. I hope I
2822 could help in some areas to make the world a better place, and that
2823 I could also encourage other people to be engaged in improving the
2824 world. Please, stay engaged. This world needs you, your love, your
2825 initiative -- now I cannot be part of that anymore."
2827 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
2828 ready. More than two years in the making, this release features improved
2829 client performance and hidden service reliability, better compatibility
2830 for Android, correct behavior for bridges that listen on more than
2831 one address, more extensible and flexible directory object handling,
2832 better reporting of network statistics, improved code security, and
2833 many many other features and bugfixes.
2836 Changes in version 0.2.2.31-rc - 2011-08-17
2837 Tor 0.2.2.31-rc is the second and hopefully final release candidate
2838 for the Tor 0.2.2.x series.
2841 - Remove an extra pair of quotation marks around the error
2842 message in control-port STATUS_GENERAL BUG events. Bugfix on
2843 0.1.2.6-alpha; fixes bug 3732.
2844 - If we're configured to write our ControlPorts to disk, only write
2845 them after switching UID and creating the data directory. This way,
2846 we don't fail when starting up with a nonexistent DataDirectory
2847 and a ControlPortWriteToFile setting based on that directory. Fixes
2848 bug 3747; bugfix on Tor 0.2.2.26-beta.
2851 - Update to the August 2 2011 Maxmind GeoLite Country database.
2854 - Allow GETINFO fingerprint to return a fingerprint even when
2855 we have not yet built a router descriptor. Fixes bug 3577;
2856 bugfix on 0.2.0.1-alpha.
2857 - Write several files in text mode, on OSes that distinguish text
2858 mode from binary mode (namely, Windows). These files are:
2859 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2860 that collect those statistics; 'client_keys' and 'hostname' for
2861 hidden services that use authentication; and (in the tor-gencert
2862 utility) newly generated identity and signing keys. Previously,
2863 we wouldn't specify text mode or binary mode, leading to an
2864 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2865 the DirRecordUsageByCountry option which would have triggered
2866 the assertion failure was added), although this assertion failure
2867 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2868 - Selectively disable deprecation warnings on OS X because Lion
2869 started deprecating the shipped copy of openssl. Fixes bug 3643.
2870 - When unable to format an address as a string, report its value
2871 as "???" rather than reusing the last formatted address. Bugfix
2875 Changes in version 0.2.3.2-alpha - 2011-07-18
2876 Tor 0.2.3.2-alpha introduces two new experimental features:
2877 microdescriptors and pluggable transports. It also continues cleaning
2878 up a variety of recently introduced features.
2881 - Clients can now use microdescriptors instead of regular descriptors
2882 to build circuits. Microdescriptors are authority-generated
2883 summaries of regular descriptors' contents, designed to change
2884 very rarely (see proposal 158 for details). This feature is
2885 designed to save bandwidth, especially for clients on slow internet
2886 connections. It's off by default for now, since nearly no caches
2887 support it, but it will be on-by-default for clients in a future
2888 version. You can use the UseMicrodescriptors option to turn it on.
2889 - Tor clients using bridges can now be configured to use a separate
2890 'transport' proxy for each bridge. This approach helps to resist
2891 censorship by allowing bridges to use protocol obfuscation
2892 plugins. It implements part of proposal 180. Implements ticket 2841.
2893 - While we're trying to bootstrap, record how many TLS connections
2894 fail in each state, and report which states saw the most failures
2895 in response to any bootstrap failures. This feature may speed up
2896 diagnosis of censorship events. Implements ticket 3116.
2898 o Major bugfixes (on 0.2.3.1-alpha):
2899 - When configuring a large set of nodes in EntryNodes (as with
2900 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
2901 random subset to be guards, and choose them in random
2902 order. Fixes bug 2798.
2903 - Tor could crash when remembering a consensus in a non-used consensus
2904 flavor without having a current consensus set. Fixes bug 3361.
2905 - Comparing an unknown address to a microdescriptor's shortened exit
2906 policy would always give a "rejected" result. Fixes bug 3599.
2907 - Using microdescriptors as a client no longer prevents Tor from
2908 uploading and downloading hidden service descriptors. Fixes
2912 - Allow nameservers with IPv6 address. Resolves bug 2574.
2913 - Accept attempts to include a password authenticator in the
2914 handshake, as supported by SOCKS5. This handles SOCKS clients that
2915 don't know how to omit a password when authenticating. Resolves
2917 - When configuring a large set of nodes in EntryNodes, and there are
2918 enough of them listed as Guard so that we don't need to consider
2919 the non-guard entries, prefer the ones listed with the Guard flag.
2920 - Check for and recover from inconsistency in the microdescriptor
2921 cache. This will make it harder for us to accidentally free a
2922 microdescriptor without removing it from the appropriate data
2923 structures. Fixes issue 3135; issue noted by "wanoskarnet".
2924 - Log SSL state transitions at log level DEBUG, log domain
2925 HANDSHAKE. This can be useful for debugging censorship events.
2926 Implements ticket 3264.
2927 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
2928 implements ticket 3439.
2930 o Minor bugfixes (on 0.2.3.1-alpha):
2931 - Do not free all general-purpose regular descriptors just
2932 because microdescriptor use is enabled. Fixes bug 3113.
2933 - Correctly link libevent_openssl when --enable-static-libevent
2934 is passed to configure. Fixes bug 3118.
2935 - Bridges should not complain during their heartbeat log messages that
2936 they are unlisted in the consensus: that's more or less the point
2937 of being a bridge. Fixes bug 3183.
2938 - Report a SIGNAL event to controllers when acting on a delayed
2939 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
2940 event to the controller if we acted on a SIGNAL NEWNYM command
2941 immediately, and otherwise not report a SIGNAL event for the
2942 command at all. Fixes bug 3349.
2943 - Fix a crash when handling the SIGNAL controller command or
2944 reporting ERR-level status events with bufferevents enabled. Found
2945 by Robert Ransom. Fixes bug 3367.
2946 - Always ship the tor-fw-helper manpage in our release tarballs.
2947 Fixes bug 3389. Reported by Stephen Walker.
2948 - Fix a class of double-mark-for-close bugs when bufferevents
2949 are enabled. Fixes bug 3403.
2950 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
2951 - Add SIGNAL to the list returned by the 'GETINFO events/names'
2952 control-port command. Fixes part of bug 3465.
2953 - Prevent using negative indices during unit test runs when read_all()
2954 fails. Spotted by coverity.
2955 - Fix a rare memory leak when checking the nodelist without it being
2956 present. Found by coverity.
2957 - Only try to download a microdescriptor-flavored consensus from
2958 a directory cache that provides them.
2960 o Minor bugfixes (on 0.2.2.x and earlier):
2961 - Assert that hidden-service-related operations are not performed
2962 using single-hop circuits. Previously, Tor would assert that
2963 client-side streams are not attached to single-hop circuits,
2964 but not that other sensitive operations on the client and service
2965 side are not performed using single-hop circuits. Fixes bug 3332;
2967 - Don't publish a new relay descriptor when we reload our onion key,
2968 unless the onion key has actually changed. Fixes bug 3263 and
2969 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
2970 - Allow GETINFO fingerprint to return a fingerprint even when
2971 we have not yet built a router descriptor. Fixes bug 3577;
2972 bugfix on 0.2.0.1-alpha.
2973 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
2974 on 0.2.2.4-alpha; fixes bug 3427.
2976 o Code simplification and refactoring:
2977 - Use tor_sscanf() in place of scanf() in more places through the
2978 code. This makes us a little more locale-independent, and
2979 should help shut up code-analysis tools that can't tell
2980 a safe sscanf string from a dangerous one.
2981 - Use tt_assert(), not tor_assert(), for checking for test failures.
2982 This makes the unit tests more able to go on in the event that
2984 - Split connection_about_to_close() into separate functions for each
2988 - On Windows, we now define the _WIN32_WINNT macros only if they
2989 are not already defined. This lets the person building Tor decide,
2990 if they want, to require a later version of Windows.
2993 Changes in version 0.2.2.30-rc - 2011-07-07
2994 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
2995 series. It fixes a few smaller bugs, but generally appears stable.
2996 Please test it and let us know whether it is!
2999 - Send a SUCCEEDED stream event to the controller when a reverse
3000 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
3001 discovered by katmagic.
3002 - Always NUL-terminate the sun_path field of a sockaddr_un before
3003 passing it to the kernel. (Not a security issue: kernels are
3004 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3005 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3006 - Don't stack-allocate the list of supplementary GIDs when we're
3007 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3008 could take up to 256K, which is way too much stack. Found by
3009 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3010 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
3011 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
3012 fixes part of bug 3465.
3013 - Fix a memory leak when receiving a descriptor for a hidden
3014 service we didn't ask for. Found by Coverity; CID #30. Bugfix
3018 - Update to the July 1 2011 Maxmind GeoLite Country database.
3021 Changes in version 0.2.2.29-beta - 2011-06-20
3022 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
3023 have bridge lines in their torrc but don't want to use them; gets
3024 us closer to having the control socket feature working on Debian;
3025 and fixes a variety of smaller bugs.
3028 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
3029 When we changed the default behavior to "use bridges if any
3030 are listed in the torrc", we surprised users who had bridges
3031 in their torrc files but who didn't actually want to use them.
3032 Partial resolution for bug 3354.
3035 - Don't attach new streams to old rendezvous circuits after SIGNAL
3036 NEWNYM. Previously, we would keep using an existing rendezvous
3037 circuit if it remained open (i.e. if it were kept open by a
3038 long-lived stream, or if a new stream were attached to it before
3039 Tor could notice that it was old and no longer in use). Bugfix on
3040 0.1.1.15-rc; fixes bug 3375.
3043 - Fix a bug when using ControlSocketsGroupWritable with User. The
3044 directory's group would be checked against the current group, not
3045 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
3046 bugfix on 0.2.2.26-beta.
3047 - Make connection_printf_to_buf()'s behaviour sane. Its callers
3048 expect it to emit a CRLF iff the format string ends with CRLF;
3049 it actually emitted a CRLF iff (a) the format string ended with
3050 CRLF or (b) the resulting string was over 1023 characters long or
3051 (c) the format string did not end with CRLF *and* the resulting
3052 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
3053 fixes part of bug 3407.
3054 - Make send_control_event_impl()'s behaviour sane. Its callers
3055 expect it to always emit a CRLF at the end of the string; it
3056 might have emitted extra control characters as well. Bugfix on
3057 0.1.1.9-alpha; fixes another part of bug 3407.
3058 - Make crypto_rand_int() check the value of its input correctly.
3059 Previously, it accepted values up to UINT_MAX, but could return a
3060 negative number if given a value above INT_MAX+1. Found by George
3061 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
3062 - Avoid a segfault when reading a malformed circuit build state
3063 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
3065 - When asked about a DNS record type we don't support via a
3066 client DNSPort, reply with NOTIMPL rather than an empty
3067 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
3068 - Fix a rare memory leak during stats writing. Found by coverity.
3071 - Update to the June 1 2011 Maxmind GeoLite Country database.
3073 o Code simplifications and refactoring:
3074 - Remove some dead code as indicated by coverity.
3075 - Remove a few dead assignments during router parsing. Found by
3077 - Add some forgotten return value checks during unit tests. Found
3079 - Don't use 1-bit wide signed bit fields. Found by coverity.
3082 Changes in version 0.2.2.28-beta - 2011-06-04
3083 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
3084 fixed a big bug in whether relays stay in the consensus consistently,
3085 we moved closer to handling bridges and hidden services correctly,
3086 and we started the process of better handling the dreaded "my Vidalia
3087 died, and now my Tor demands a password when I try to reconnect to it"
3091 - Don't decide to make a new descriptor when receiving a HUP signal.
3092 This bug has caused a lot of 0.2.2.x relays to disappear from the
3093 consensus periodically. Fixes the most common case of triggering
3094 bug 1810; bugfix on 0.2.2.7-alpha.
3095 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
3096 - Don't try to build descriptors if "ORPort auto" is set and we
3097 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
3099 - Resolve a crash that occurred when setting BridgeRelay to 1 with
3100 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
3101 - Apply circuit timeouts to opened hidden-service-related circuits
3102 based on the correct start time. Previously, we would apply the
3103 circuit build timeout based on time since the circuit's creation;
3104 it was supposed to be applied based on time since the circuit
3105 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
3106 - Use the same circuit timeout for client-side introduction
3107 circuits as for other four-hop circuits, rather than the timeout
3108 for single-hop directory-fetch circuits; the shorter timeout may
3109 have been appropriate with the static circuit build timeout in
3110 0.2.1.x and earlier, but caused many hidden service access attempts
3111 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
3112 on 0.2.2.2-alpha; fixes another part of bug 1297.
3113 - In ticket 2511 we fixed a case where you could use an unconfigured
3114 bridge if you had configured it as a bridge the last time you ran
3115 Tor. Now fix another edge case: if you had configured it as a bridge
3116 but then switched to a different bridge via the controller, you
3117 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
3121 - Add an __OwningControllerProcess configuration option and a
3122 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
3123 that when it exits, Tor will shut down. Implements feature 3049.
3124 - If "UseBridges 1" is set and no bridges are configured, Tor will
3125 now refuse to build any circuits until some bridges are set.
3126 If "UseBridges auto" is set, Tor will use bridges if they are
3127 configured and we are not running as a server, but otherwise will
3128 make circuits as usual. The new default is "auto". Patch by anonym,
3129 so the Tails LiveCD can stop automatically revealing you as a Tor
3133 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3134 - Remove a trailing asterisk from "exit-policy/default" in the
3135 output of the control port command "GETINFO info/names". Bugfix
3137 - Use a wide type to hold sockets when built for 64-bit Windows builds.
3139 - Warn when the user configures two HiddenServiceDir lines that point
3140 to the same directory. Bugfix on 0.0.6 (the version introducing
3141 HiddenServiceDir); fixes bug 3289.
3142 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
3143 part of bug 2748; bugfix on 0.2.0.10-alpha.
3144 - Log malformed requests for rendezvous descriptors as protocol
3145 warnings, not warnings. Also, use a more informative log message
3146 in case someone sees it at log level warning without prior
3147 info-level messages. Fixes the other part of bug 2748; bugfix
3149 - Clear the table recording the time of the last request for each
3150 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
3151 Previously, we would clear our HS descriptor cache on SIGNAL
3152 NEWNYM, but if we had previously retrieved a descriptor (or tried
3153 to) from every directory responsible for it, we would refuse to
3154 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
3156 - Fix a log message that said "bits" while displaying a value in
3157 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
3159 - When checking for 1024-bit keys, check for 1024 bits, not 128
3160 bytes. This allows Tor to correctly discard keys of length 1017
3161 through 1023. Bugfix on 0.0.9pre5.
3164 - Relays now log the reason for publishing a new relay descriptor,
3165 so we have a better chance of hunting down instances of bug 1810.
3166 Resolves ticket 3252.
3167 - Revise most log messages that refer to nodes by nickname to
3168 instead use the "$key=nickname at address" format. This should be
3169 more useful, especially since nicknames are less and less likely
3170 to be unique. Resolves ticket 3045.
3171 - Log (at info level) when purging pieces of hidden-service-client
3172 state because of SIGNAL NEWNYM.
3175 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3176 anything since 0.2.1.16-rc.
3179 Changes in version 0.2.2.27-beta - 2011-05-18
3180 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
3181 release, and also adds a few more general bugfixes.
3184 - Fix a crash bug when changing bridges in a running Tor process.
3185 Fixes bug 3213; bugfix on 0.2.2.26-beta.
3186 - When the controller configures a new bridge, don't wait 10 to 60
3187 seconds before trying to fetch its descriptor. Bugfix on
3188 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
3191 - Require that onion keys have exponent 65537 in microdescriptors too.
3192 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
3193 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
3194 Changed the limit to 512 characters by removing base64 newlines.
3195 Fixes bug 2752. Fix by Michael Yakubovich.
3196 - When a client starts or stops using bridges, never use a circuit
3197 that was built before the configuration change. This behavior could
3198 put at risk a user who uses bridges to ensure that her traffic
3199 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
3203 Changes in version 0.2.2.26-beta - 2011-05-17
3204 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
3205 also introduces a new "socksport auto" approach that should make it
3206 easier to run multiple Tors on the same system, and does a lot of
3207 cleanup to get us closer to a release candidate.
3209 o Security/privacy fixes:
3210 - Replace all potentially sensitive memory comparison operations
3211 with versions whose runtime does not depend on the data being
3212 compared. This will help resist a class of attacks where an
3213 adversary can use variations in timing information to learn
3214 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3215 implementation by Robert Ransom based partially on code by DJB.)
3216 - When receiving a hidden service descriptor, check that it is for
3217 the hidden service we wanted. Previously, Tor would store any
3218 hidden service descriptors that a directory gave it, whether it
3219 wanted them or not. This wouldn't have let an attacker impersonate
3220 a hidden service, but it did let directories pre-seed a client
3221 with descriptors that it didn't want. Bugfix on 0.0.6.
3222 - On SIGHUP, do not clear out all TrackHostExits mappings, client
3223 DNS cache entries, and virtual address mappings: that's what
3224 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
3227 - The options SocksPort, ControlPort, and so on now all accept a
3228 value "auto" that opens a socket on an OS-selected port. A
3229 new ControlPortWriteToFile option tells Tor to write its
3230 actual control port or ports to a chosen file. If the option
3231 ControlPortFileGroupReadable is set, the file is created as
3232 group-readable. Now users can run two Tor clients on the same
3233 system without needing to manually mess with parameters. Resolves
3234 part of ticket 3076.
3235 - Set SO_REUSEADDR on all sockets, not just listeners. This should
3236 help busy exit nodes avoid running out of useable ports just
3237 because all the ports have been used in the near past. Resolves
3241 - New "GETINFO net/listeners/(type)" controller command to return
3242 a list of addresses and ports that are bound for listeners for a
3243 given connection type. This is useful when the user has configured
3244 "SocksPort auto" and the controller needs to know which port got
3245 chosen. Resolves another part of ticket 3076.
3246 - Add a new ControlSocketsGroupWritable configuration option: when
3247 it is turned on, ControlSockets are group-writeable by the default
3248 group of the current user. Patch by Jérémy Bobbio; implements
3250 - Tor now refuses to create a ControlSocket in a directory that is
3251 world-readable (or group-readable if ControlSocketsGroupWritable
3252 is 0). This is necessary because some operating systems do not
3253 enforce permissions on an AF_UNIX sockets. Permissions on the
3254 directory holding the socket, however, seems to work everywhere.
3255 - Rate-limit a warning about failures to download v2 networkstatus
3256 documents. Resolves part of bug 1352.
3257 - Backport code from 0.2.3.x that allows directory authorities to
3258 clean their microdescriptor caches. Needed to resolve bug 2230.
3259 - When an HTTPS proxy reports "403 Forbidden", we now explain
3260 what it means rather than calling it an unexpected status code.
3261 Closes bug 2503. Patch from Michael Yakubovich.
3262 - Update to the May 1 2011 Maxmind GeoLite Country database.
3265 - Authorities now clean their microdesc cache periodically and when
3266 reading from disk initially, not only when adding new descriptors.
3267 This prevents a bug where we could lose microdescriptors. Bugfix
3268 on 0.2.2.6-alpha. Fixes bug 2230.
3269 - Do not crash when our configuration file becomes unreadable, for
3270 example due to a permissions change, between when we start up
3271 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3273 - Avoid a bug that would keep us from replacing a microdescriptor
3274 cache on Windows. (We would try to replace the file while still
3275 holding it open. That's fine on Unix, but Windows doesn't let us
3276 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
3277 - Add missing explanations for the authority-related torrc options
3278 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
3279 man page. Resolves issue 2379.
3280 - As an authority, do not upload our own vote or signature set to
3281 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
3282 it would get flagged as a duplicate. Resolves bug 3026.
3283 - Accept hidden service descriptors if we think we might be a hidden
3284 service directory, regardless of what our consensus says. This
3285 helps robustness, since clients and hidden services can sometimes
3286 have a more up-to-date view of the network consensus than we do,
3287 and if they think that the directory authorities list us a HSDir,
3288 we might actually be one. Related to bug 2732; bugfix on
3290 - When a controller changes TrackHostExits, remove mappings for
3291 hosts that should no longer have their exits tracked. Bugfix on
3293 - When a controller changes VirtualAddrNetwork, remove any mappings
3294 for hosts that were automapped to the old network. Bugfix on
3296 - When a controller changes one of the AutomapHosts* options, remove
3297 any mappings for hosts that should no longer be automapped. Bugfix
3299 - Do not reset the bridge descriptor download status every time we
3300 re-parse our configuration or get a configuration change. Fixes
3301 bug 3019; bugfix on 0.2.0.3-alpha.
3303 o Minor bugfixes (code cleanup):
3304 - When loading the microdesc journal, remember its current size.
3305 In 0.2.2, this helps prevent the microdesc journal from growing
3306 without limit on authorities (who are the only ones to use it in
3307 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
3308 Fix posted by "cypherpunks."
3309 - The microdesc journal is supposed to get rebuilt only if it is
3310 at least _half_ the length of the store, not _twice_ the length
3311 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
3312 - Fix a potential null-pointer dereference while computing a
3313 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
3315 - Avoid a possible null-pointer dereference when rebuilding the mdesc
3316 cache without actually having any descriptors to cache. Bugfix on
3317 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
3318 - If we fail to compute the identity digest of a v3 legacy keypair,
3319 warn, and don't use a buffer-full of junk instead. Bugfix on
3320 0.2.1.1-alpha; fixes bug 3106.
3321 - Resolve an untriggerable issue in smartlist_string_num_isin(),
3322 where if the function had ever in the future been used to check
3323 for the presence of a too-large number, it would have given an
3324 incorrect result. (Fortunately, we only used it for 16-bit
3325 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
3326 - Require that introduction point keys and onion handshake keys
3327 have a public exponent of 65537. Starts to fix bug 3207; bugfix
3331 - Caches no longer download and serve v2 networkstatus documents
3332 unless FetchV2Networkstatus flag is set: these documents haven't
3333 haven't been used by clients or relays since 0.2.0.x. Resolves
3337 Changes in version 0.2.3.1-alpha - 2011-05-05
3338 Tor 0.2.3.1-alpha adds some new experimental features, including support
3339 for an improved network IO backend, IOCP networking on Windows,
3340 microdescriptor caching, "fast-start" support for streams, and automatic
3341 home router configuration. There are also numerous internal improvements
3342 to try to make the code easier for developers to work with.
3344 This is the first alpha release in a new series, so expect there to be
3345 bugs. Users who would rather test out a more stable branch should
3346 stay with 0.2.2.x for now.
3349 - Tor can now optionally build with the "bufferevents" buffered IO
3350 backend provided by Libevent 2. To use this feature, make sure you
3351 have the latest possible version of Libevent, and pass the
3352 --enable-bufferevents flag to configure when building Tor from
3353 source. This feature will make our networking code more flexible,
3354 let us stack layers on each other, and let us use more efficient
3355 zero-copy transports where available.
3356 - As an experimental feature, Tor can use IOCP for networking on Windows.
3357 Once this code is tuned and optimized, it promises much better
3358 performance than the select-based backend we've used in the past. To
3359 try this feature, you must build Tor with Libevent 2, configure Tor
3360 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
3361 your torrc. There are known bugs here: only try this if you can help
3362 debug it as it breaks.
3363 - The EntryNodes option can now include country codes like {de} or IP
3364 addresses or network masks. Previously we had disallowed these options
3365 because we didn't have an efficient way to keep the list up to
3366 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
3367 - Exit nodes now accept and queue data on not-yet-connected streams.
3368 Previously, the client wasn't allowed to send data until the stream was
3369 connected, which slowed down all connections. This change will enable
3370 clients to perform a "fast-start" on streams and send data without
3371 having to wait for a confirmation that the stream has opened. (Patch
3372 from Ian Goldberg; implements the server side of Proposal 174.)
3373 - Tor now has initial support for automatic port mapping on the many
3374 home routers that support NAT-PMP or UPnP. (Not yet supported on
3375 Windows). To build the support code, you'll need to have libnatpnp
3376 library and/or the libminiupnpc library, and you'll need to enable the
3377 feature specifically by passing "--enable-upnp" and/or
3378 "--enable-natpnp" to configure. To turn it on, use the new
3379 PortForwarding option.
3380 - Caches now download, cache, and serve multiple "flavors" of the
3381 consensus, including a flavor that describes microdescriptors.
3382 - Caches now download, cache, and serve microdescriptors -- small
3383 summaries of router descriptors that are authenticated by all of the
3384 directory authorities. Once enough caches are running this code,
3385 clients will be able to save significant amounts of directory bandwidth
3386 by downloading microdescriptors instead of router descriptors.
3389 - Make logging resolution configurable with a new LogTimeGranularity
3390 option, and change the default from 1 millisecond to 1 second.
3391 Implements enhancement 1668.
3392 - We log which torrc file we're using on startup. Implements ticket
3394 - Ordinarily, Tor does not count traffic from private addresses (like
3395 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
3396 There is now a new option, CountPrivateBandwidth, to disable this
3397 behavior. Patch from Daniel Cagara.
3398 - New --enable-static-tor configure option for building Tor as
3399 statically as possible. Idea, general hackery and thoughts from
3400 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
3402 - If you set the NumCPUs option to 0, Tor will now try to detect how
3403 many CPUs you have. This is the new default behavior.
3404 - Turn on directory request statistics by default and include them in
3405 extra-info descriptors. Don't break if we have no GeoIP database.
3406 - Relays that set "ConnDirectionStatistics 1" write statistics on the
3407 bidirectional use of connections to disk every 24 hours.
3408 - Add a GeoIP file digest to the extra-info descriptor. Implements
3410 - The NodeFamily option -- which let you declare that you want to
3411 consider nodes to be part of a family whether they list themselves
3412 that way or not -- now allows IP address ranges and country codes.
3413 - Add a new 'Heartbeat' log message type to periodically log a message
3414 describing Tor's status at level Notice. This feature is meant for
3415 operators who log at notice, and want to make sure that their Tor
3416 server is still working. Implementation by George Kadianakis.
3418 o Minor bugfixes (on 0.2.2.25-alpha):
3419 - When loading the microdesc journal, remember its current size.
3420 In 0.2.2, this helps prevent the microdesc journal from growing
3421 without limit on authorities (who are the only ones to use it in
3422 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
3423 Fix posted by "cypherpunks."
3424 - The microdesc journal is supposed to get rebuilt only if it is
3425 at least _half_ the length of the store, not _twice_ the length
3426 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
3427 - If as an authority we fail to compute the identity digest of a v3
3428 legacy keypair, warn, and don't use a buffer-full of junk instead.
3429 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
3430 - Authorities now clean their microdesc cache periodically and when
3431 reading from disk initially, not only when adding new descriptors.
3432 This prevents a bug where we could lose microdescriptors. Bugfix
3435 o Minor features (controller):
3436 - Add a new SIGNAL event to the controller interface so that
3437 controllers can be notified when Tor handles a signal. Resolves
3438 issue 1955. Patch by John Brooks.
3439 - Add a new GETINFO option to get total bytes read and written. Patch
3440 from pipe, revised by atagar. Resolves ticket 2345.
3441 - Implement some GETINFO controller fields to provide information about
3442 the Tor process's pid, euid, username, and resource limits.
3445 - Our build system requires automake 1.6 or later to create the
3446 Makefile.in files. Previously, you could have used 1.4.
3447 This only affects developers and people building Tor from git;
3448 people who build Tor from the source distribution without changing
3449 the Makefile.am files should be fine.
3450 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
3451 so on. This is more robust against some of the failure modes
3452 associated with running the autotools pieces on their own.
3454 o Minor packaging issues:
3455 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
3456 already created. Patch from Andreas Stieger. Fixes bug 2573.
3458 o Code simplifications and refactoring:
3459 - A major revision to our internal node-selecting and listing logic.
3460 Tor already had at least two major ways to look at the question of
3461 "which Tor servers do we know about": a list of router descriptors,
3462 and a list of entries in the current consensus. With
3463 microdescriptors, we're adding a third. Having so many systems
3464 without an abstraction layer over them was hurting the codebase.
3465 Now, we have a new "node_t" abstraction that presents a consistent
3466 interface to a client's view of a Tor node, and holds (nearly) all
3467 of the mutable state formerly in routerinfo_t and routerstatus_t.
3468 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
3469 no longer link against Libevent: they never used it, but
3470 our library structure used to force them to link it.
3473 - Remove some old code to work around even older versions of Tor that
3474 used forked processes to handle DNS requests. Such versions of Tor
3475 are no longer in use as servers.
3477 o Documentation fixes:
3478 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
3479 - Add missing documentation for the authority-related torrc options
3480 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
3484 Changes in version 0.2.2.25-alpha - 2011-04-29
3485 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
3486 robust, routers no longer overreport their bandwidth, Win7 should crash
3487 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
3488 now prevents hidden service-related activity from being linkable. It
3489 provides more information to Vidalia so you can see if your bridge is
3490 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
3491 StrictNodes configuration options to make them more reliable, more
3492 understandable, and more regularly applied. If you use those options,
3493 please see the revised documentation for them in the manual page.
3496 - Relays were publishing grossly inflated bandwidth values because
3497 they were writing their state files wrong--now they write the
3498 correct value. Also, resume reading bandwidth history from the
3499 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
3500 - Improve hidden service robustness: When we find that we have
3501 extended a hidden service's introduction circuit to a relay not
3502 listed as an introduction point in the HS descriptor we currently
3503 have, retry with an introduction point from the current
3504 descriptor. Previously we would just give up. Fixes bugs 1024 and
3505 1930; bugfix on 0.2.0.10-alpha.
3506 - Clients now stop trying to use an exit node associated with a given
3507 destination by TrackHostExits if they fail to reach that exit node.
3508 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
3509 - Fix crash bug on platforms where gmtime and localtime can return
3510 NULL. Windows 7 users were running into this one. Fixes part of bug
3511 2077. Bugfix on all versions of Tor. Found by boboper.
3513 o Security and stability fixes:
3514 - Don't double-free a parsable, but invalid, microdescriptor, even if
3515 it is followed in the blob we're parsing by an unparsable
3516 microdescriptor. Fixes an issue reported in a comment on bug 2954.
3517 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
3518 - If the Nickname configuration option isn't given, Tor would pick a
3519 nickname based on the local hostname as the nickname for a relay.
3520 Because nicknames are not very important in today's Tor and the
3521 "Unnamed" nickname has been implemented, this is now problematic
3522 behavior: It leaks information about the hostname without being
3523 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
3524 introduced the Unnamed nickname. Reported by tagnaq.
3525 - Fix an uncommon assertion failure when running with DNSPort under
3526 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3527 - Avoid linkability based on cached hidden service descriptors: forget
3528 all hidden service descriptors cached as a client when processing a
3529 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3532 - Export GeoIP information on bridge usage to controllers even if we
3533 have not yet been running for 24 hours. Now Vidalia bridge operators
3534 can get more accurate and immediate feedback about their
3535 contributions to the network.
3537 o Major features and bugfixes (node selection):
3538 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
3539 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
3540 options. Previously, we had been ambiguous in describing what
3541 counted as an "exit" node, and what operations exactly "StrictNodes
3542 0" would permit. This created confusion when people saw nodes built
3543 through unexpected circuits, and made it hard to tell real bugs from
3544 surprises. Now the intended behavior is:
3545 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
3546 a node that delivers user traffic outside the Tor network.
3547 . "Entry", in the context of EntryNodes, means a node used as the
3548 first hop of a multihop circuit. It doesn't include direct
3549 connections to directory servers.
3550 . "ExcludeNodes" applies to all nodes.
3551 . "StrictNodes" changes the behavior of ExcludeNodes only. When
3552 StrictNodes is set, Tor should avoid all nodes listed in
3553 ExcludeNodes, even when it will make user requests fail. When
3554 StrictNodes is *not* set, then Tor should follow ExcludeNodes
3555 whenever it can, except when it must use an excluded node to
3556 perform self-tests, connect to a hidden service, provide a
3557 hidden service, fulfill a .exit request, upload directory
3558 information, or fetch directory information.
3559 Collectively, the changes to implement the behavior fix bug 1090.
3560 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
3561 a node is listed in both, it's treated as excluded.
3562 - ExcludeNodes now applies to directory nodes -- as a preference if
3563 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
3564 Don't exclude all the directory authorities and set StrictNodes to 1
3565 unless you really want your Tor to break.
3566 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
3567 - ExcludeExitNodes now overrides .exit requests.
3568 - We don't use bridges listed in ExcludeNodes.
3569 - When StrictNodes is 1:
3570 . We now apply ExcludeNodes to hidden service introduction points
3571 and to rendezvous points selected by hidden service users. This
3572 can make your hidden service less reliable: use it with caution!
3573 . If we have used ExcludeNodes on ourself, do not try relay
3574 reachability self-tests.
3575 . If we have excluded all the directory authorities, we will not
3576 even try to upload our descriptor if we're a relay.
3577 . Do not honor .exit requests to an excluded node.
3578 - Remove a misfeature that caused us to ignore the Fast/Stable flags
3579 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
3580 - When the set of permitted nodes changes, we now remove any mappings
3581 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
3583 - We never cannibalize a circuit that had excluded nodes on it, even
3584 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
3585 - Revert a change where we would be laxer about attaching streams to
3586 circuits than when building the circuits. This was meant to prevent
3587 a set of bugs where streams were never attachable, but our improved
3588 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
3589 - Keep track of how many times we launch a new circuit to handle a
3590 given stream. Too many launches could indicate an inconsistency
3591 between our "launch a circuit to handle this stream" logic and our
3592 "attach this stream to one of the available circuits" logic.
3593 - Improve log messages related to excluded nodes.
3596 - Fix a spurious warning when moving from a short month to a long
3597 month on relays with month-based BandwidthAccounting. Bugfix on
3598 0.2.2.17-alpha; fixes bug 3020.
3599 - When a client finds that an origin circuit has run out of 16-bit
3600 stream IDs, we now mark it as unusable for new streams. Previously,
3601 we would try to close the entire circuit. Bugfix on 0.0.6.
3602 - Add a forgotten cast that caused a compile warning on OS X 10.6.
3603 Bugfix on 0.2.2.24-alpha.
3604 - Be more careful about reporting the correct error from a failed
3605 connect() system call. Under some circumstances, it was possible to
3606 look at an incorrect value for errno when sending the end reason.
3607 Bugfix on 0.1.0.1-rc.
3608 - Correctly handle an "impossible" overflow cases in connection byte
3609 counting, where we write or read more than 4GB on an edge connection
3610 in a single second. Bugfix on 0.1.2.8-beta.
3611 - Correct the warning displayed when a rendezvous descriptor exceeds
3612 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3614 - Clients and hidden services now use HSDir-flagged relays for hidden
3615 service descriptor downloads and uploads even if the relays have no
3616 DirPort set and the client has disabled TunnelDirConns. This will
3617 eventually allow us to give the HSDir flag to relays with no
3618 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
3619 - Downgrade "no current certificates known for authority" message from
3620 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
3621 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
3622 2917. Bugfix on 0.1.1.1-alpha.
3623 - Only limit the lengths of single HS descriptors, even when multiple
3624 HS descriptors are published to an HSDir relay in a single POST
3625 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
3626 - Write the current time into the LastWritten line in our state file,
3627 rather than the time from the previous write attempt. Also, stop
3628 trying to use a time of -1 in our log statements. Fixes bug 3039;
3629 bugfix on 0.2.2.14-alpha.
3630 - Be more consistent in our treatment of file system paths. "~" should
3631 get expanded to the user's home directory in the Log config option.
3632 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
3633 feature for the -f and --DataDirectory options.
3636 - Make sure every relay writes a state file at least every 12 hours.
3637 Previously, a relay could go for weeks without writing its state
3638 file, and on a crash could lose its bandwidth history, capacity
3639 estimates, client country statistics, and so on. Addresses bug 3012.
3640 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
3641 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
3642 clients are already deprecated because of security bugs.
3643 - Don't allow v0 hidden service authorities to act as clients.
3644 Required by fix for bug 3000.
3645 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
3646 by fix for bug 3000.
3647 - Ensure that no empty [dirreq-](read|write)-history lines are added
3648 to an extrainfo document. Implements ticket 2497.
3650 o Code simplification and refactoring:
3651 - Remove workaround code to handle directory responses from servers
3652 that had bug 539 (they would send HTTP status 503 responses _and_
3653 send a body too). Since only server versions before
3654 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
3655 keep the workaround in place.
3656 - Remove the old 'fuzzy time' logic. It was supposed to be used for
3657 handling calculations where we have a known amount of clock skew and
3658 an allowed amount of unknown skew. But we only used it in three
3659 places, and we never adjusted the known/unknown skew values. This is
3660 still something we might want to do someday, but if we do, we'll
3661 want to do it differently.
3662 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3663 None of the cases where we did this before were wrong, but by making
3664 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3665 - Use GetTempDir to find the proper temporary directory location on
3666 Windows when generating temporary files for the unit tests. Patch by
3670 Changes in version 0.2.2.24-alpha - 2011-04-08
3671 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
3672 prevented Tor clients from effectively using "multihomed" bridges,
3673 that is, bridges that listen on multiple ports or IP addresses so users
3674 can continue to use some of their addresses even if others get blocked.
3677 - Fix a bug where bridge users who configure the non-canonical
3678 address of a bridge automatically switch to its canonical
3679 address. If a bridge listens at more than one address, it should be
3680 able to advertise those addresses independently and any non-blocked
3681 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
3683 - If you configured Tor to use bridge A, and then quit and
3684 configured Tor to use bridge B instead, it would happily continue
3685 to use bridge A if it's still reachable. While this behavior is
3686 a feature if your goal is connectivity, in some scenarios it's a
3687 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
3688 - Directory authorities now use data collected from their own
3689 uptime observations when choosing whether to assign the HSDir flag
3690 to relays, instead of trusting the uptime value the relay reports in
3691 its descriptor. This change helps prevent an attack where a small
3692 set of nodes with frequently-changing identity keys can blackhole
3693 a hidden service. (Only authorities need upgrade; others will be
3694 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
3697 - When we restart our relay, we might get a successful connection
3698 from the outside before we've started our reachability tests,
3699 triggering a warning: "ORPort found reachable, but I have no
3700 routerinfo yet. Failing to inform controller of success." This
3701 bug was harmless unless Tor is running under a controller
3702 like Vidalia, in which case the controller would never get a
3703 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3705 - Make directory authorities more accurate at recording when
3706 relays that have failed several reachability tests became
3707 unreachable, so we can provide more accuracy at assigning Stable,
3708 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
3709 - Fix an issue that prevented static linking of libevent on
3710 some platforms (notably Linux). Fixes bug 2698; bugfix on
3711 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
3712 the --with-static-libevent configure option).
3713 - We now ask the other side of a stream (the client or the exit)
3714 for more data on that stream when the amount of queued data on
3715 that stream dips low enough. Previously, we wouldn't ask the
3716 other side for more data until either it sent us more data (which
3717 it wasn't supposed to do if it had exhausted its window!) or we
3718 had completely flushed all our queued data. This flow control fix
3719 should improve throughput. Fixes bug 2756; bugfix on the earliest
3720 released versions of Tor (svn commit r152).
3721 - Avoid a double-mark-for-free warning when failing to attach a
3722 transparent proxy connection. (We thought we had fixed this in
3723 0.2.2.23-alpha, but it turns out our fix was checking the wrong
3724 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
3725 bug) and 0.2.2.23-alpha (the incorrect fix).
3726 - When warning about missing zlib development packages during compile,
3727 give the correct package names. Bugfix on 0.2.0.1-alpha.
3730 - Directory authorities now log the source of a rejected POSTed v3
3732 - Make compilation with clang possible when using
3733 --enable-gcc-warnings by removing two warning options that clang
3734 hasn't implemented yet and by fixing a few warnings. Implements
3736 - When expiring circuits, use microsecond timers rather than
3737 one-second timers. This can avoid an unpleasant situation where a
3738 circuit is launched near the end of one second and expired right
3739 near the beginning of the next, and prevent fluctuations in circuit
3741 - Use computed circuit-build timeouts to decide when to launch
3742 parallel introduction circuits for hidden services. (Previously,
3743 we would retry after 15 seconds.)
3744 - Update to the April 1 2011 Maxmind GeoLite Country database.
3747 - Create the /var/run/tor directory on startup on OpenSUSE if it is
3748 not already created. Patch from Andreas Stieger. Fixes bug 2573.
3750 o Documentation changes:
3751 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
3752 - Resolve all doxygen warnings except those for missing documentation.
3754 - Add doxygen documentation for more functions, fields, and types.
3757 Changes in version 0.2.2.23-alpha - 2011-03-08
3758 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
3759 they restart they don't lose their bandwidth capacity estimate. This
3760 release also fixes a diverse set of user-facing bugs, ranging from
3761 relays overrunning their rate limiting to clients falsely warning about
3762 clock skew to bridge descriptor leaks by our bridge directory authority.
3765 - Stop sending a CLOCK_SKEW controller status event whenever
3766 we fetch directory information from a relay that has a wrong clock.
3767 Instead, only inform the controller when it's a trusted authority
3768 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3769 the rest of bug 1074.
3770 - Fix an assert in parsing router descriptors containing IPv6
3771 addresses. This one took down the directory authorities when
3772 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3773 - Make the bridge directory authority refuse to answer directory
3774 requests for "all" descriptors. It used to include bridge
3775 descriptors in its answer, which was a major information leak.
3776 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3777 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3778 Tor would ignore their RelayBandwidthBurst setting,
3779 potentially using more bandwidth than expected. Bugfix on
3780 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3781 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3782 hidserv" in her torrc. The 'hidserv' argument never controlled
3783 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3786 - Relays now save observed peak bandwidth throughput rates to their
3787 state file (along with total usage, which was already saved)
3788 so that they can determine their correct estimated bandwidth on
3789 restart. Resolves bug 1863, where Tor relays would reset their
3790 estimated bandwidth to 0 after restarting.
3791 - Directory authorities now take changes in router IP address and
3792 ORPort into account when determining router stability. Previously,
3793 if a router changed its IP or ORPort, the authorities would not
3794 treat it as having any downtime for the purposes of stability
3795 calculation, whereas clients would experience downtime since the
3796 change could take a while to propagate to them. Resolves issue 1035.
3797 - Enable Address Space Layout Randomization (ASLR) and Data Execution
3798 Prevention (DEP) by default on Windows to make it harder for
3799 attackers to exploit vulnerabilities. Patch from John Brooks.
3801 o Minor bugfixes (on 0.2.1.x and earlier):
3802 - Fix a rare crash bug that could occur when a client was configured
3803 with a large number of bridges. Fixes bug 2629; bugfix on
3804 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3805 - Avoid a double mark-for-free warning when failing to attach a
3806 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
3808 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
3809 found by "cypherpunks". This bug was introduced before the first
3810 Tor release, in svn commit r110.
3811 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
3812 don't mention them in the manpage. Fixes bug 2450; issue
3813 spotted by keb and G-Lo.
3814 - Fix a bug in bandwidth history state parsing that could have been
3815 triggered if a future version of Tor ever changed the timing
3816 granularity at which bandwidth history is measured. Bugfix on
3818 - When a relay decides that its DNS is too broken for it to serve
3819 as an exit server, it advertised itself as a non-exit, but
3820 continued to act as an exit. This could create accidental
3821 partitioning opportunities for users. Instead, if a relay is
3822 going to advertise reject *:* as its exit policy, it should
3823 really act with exit policy "reject *:*". Fixes bug 2366.
3824 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
3825 - In the special case where you configure a public exit relay as your
3826 bridge, Tor would be willing to use that exit relay as the last
3827 hop in your circuit as well. Now we fail that circuit instead.
3828 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
3829 - Fix a bug with our locking implementation on Windows that couldn't
3830 correctly detect when a file was already locked. Fixes bug 2504,
3831 bugfix on 0.2.1.6-alpha.
3832 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
3833 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
3835 - Set target port in get_interface_address6() correctly. Bugfix
3836 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
3837 - Directory authorities are now more robust to hops back in time
3838 when calculating router stability. Previously, if a run of uptime
3839 or downtime appeared to be negative, the calculation could give
3840 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
3842 - Fix an assert that got triggered when using the TestingTorNetwork
3843 configuration option and then issuing a GETINFO config-text control
3844 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
3846 o Minor bugfixes (on 0.2.2.x):
3847 - Clients should not weight BadExit nodes as Exits in their node
3848 selection. Similarly, directory authorities should not count BadExit
3849 bandwidth as Exit bandwidth when computing bandwidth-weights.
3850 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
3851 - Correctly clear our dir_read/dir_write history when there is an
3852 error parsing any bw history value from the state file. Bugfix on
3854 - Resolve a bug in verifying signatures of directory objects
3855 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
3856 Fixes bug 2409. Found by "piebeer".
3857 - Bridge authorities no longer crash on SIGHUP when they try to
3858 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
3862 - Log less aggressively about circuit timeout changes, and improve
3863 some other circuit timeout messages. Resolves bug 2004.
3864 - Log a little more clearly about the times at which we're no longer
3865 accepting new connections. Resolves bug 2181.
3866 - Reject attempts at the client side to open connections to private
3867 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
3868 a randomly chosen exit node. Attempts to do so are always
3869 ill-defined, generally prevented by exit policies, and usually
3870 in error. This will also help to detect loops in transparent
3871 proxy configurations. You can disable this feature by setting
3872 "ClientRejectInternalAddresses 0" in your torrc.
3873 - Always treat failure to allocate an RSA key as an unrecoverable
3875 - Update to the March 1 2011 Maxmind GeoLite Country database.
3877 o Minor features (log subsystem):
3878 - Add documentation for configuring logging at different severities in
3879 different log domains. We've had this feature since 0.2.1.1-alpha,
3880 but for some reason it never made it into the manpage. Fixes
3882 - Make it simpler to specify "All log domains except for A and B".
3883 Previously you needed to say "[*,~A,~B]". Now you can just say
3885 - Add a "LogMessageDomains 1" option to include the domains of log
3886 messages along with the messages. Without this, there's no way
3887 to use log domains without reading the source or doing a lot
3890 o Packaging changes:
3891 - Stop shipping the Tor specs files and development proposal documents
3892 in the tarball. They are now in a separate git repository at
3893 git://git.torproject.org/torspec.git
3896 Changes in version 0.2.1.30 - 2011-02-23
3897 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
3898 change is a slight tweak to Tor's TLS handshake that makes relays
3899 and bridges that run this new version reachable from Iran again.
3900 We don't expect this tweak will win the arms race long-term, but it
3901 buys us time until we roll out a better solution.
3904 - Stop sending a CLOCK_SKEW controller status event whenever
3905 we fetch directory information from a relay that has a wrong clock.
3906 Instead, only inform the controller when it's a trusted authority
3907 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3908 the rest of bug 1074.
3909 - Fix a bounds-checking error that could allow an attacker to
3910 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3912 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3913 Tor would ignore their RelayBandwidthBurst setting,
3914 potentially using more bandwidth than expected. Bugfix on
3915 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3916 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3917 hidserv" in her torrc. The 'hidserv' argument never controlled
3918 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3921 - Adjust our TLS Diffie-Hellman parameters to match those used by
3923 - Update to the February 1 2011 Maxmind GeoLite Country database.
3926 - Check for and reject overly long directory certificates and
3927 directory tokens before they have a chance to hit any assertions.
3928 Bugfix on 0.2.1.28. Found by "doorss".
3929 - Bring the logic that gathers routerinfos and assesses the
3930 acceptability of circuits into line. This prevents a Tor OP from
3931 getting locked in a cycle of choosing its local OR as an exit for a
3932 path (due to a .exit request) and then rejecting the circuit because
3933 its OR is not listed yet. It also prevents Tor clients from using an
3934 OR running in the same instance as an exit (due to a .exit request)
3935 if the OR does not meet the same requirements expected of an OR
3936 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
3938 o Packaging changes:
3939 - Stop shipping the Tor specs files and development proposal documents
3940 in the tarball. They are now in a separate git repository at
3941 git://git.torproject.org/torspec.git
3942 - Do not include Git version tags as though they are SVN tags when
3943 generating a tarball from inside a repository that has switched
3944 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3947 Changes in version 0.2.2.22-alpha - 2011-01-25
3948 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
3949 main other change is a slight tweak to Tor's TLS handshake that makes
3950 relays and bridges that run this new version reachable from Iran again.
3951 We don't expect this tweak will win the arms race long-term, but it
3952 will buy us a bit more time until we roll out a better solution.
3955 - Fix a bounds-checking error that could allow an attacker to
3956 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3958 - Don't assert when changing from bridge to relay or vice versa
3959 via the controller. The assert happened because we didn't properly
3960 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
3961 bug 2433. Reported by bastik.
3964 - Adjust our TLS Diffie-Hellman parameters to match those used by
3966 - Provide a log message stating which geoip file we're parsing
3967 instead of just stating that we're parsing the geoip file.
3968 Implements ticket 2432.
3971 - Check for and reject overly long directory certificates and
3972 directory tokens before they have a chance to hit any assertions.
3973 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
3976 Changes in version 0.2.2.21-alpha - 2011-01-15
3977 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
3978 continues our recent code security audit work. The main fix resolves
3979 a remote heap overflow vulnerability that can allow remote code
3980 execution (CVE-2011-0427). Other fixes address a variety of assert
3981 and crash bugs, most of which we think are hard to exploit remotely.
3983 o Major bugfixes (security), also included in 0.2.1.29:
3984 - Fix a heap overflow bug where an adversary could cause heap
3985 corruption. This bug probably allows remote code execution
3986 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3988 - Prevent a denial-of-service attack by disallowing any
3989 zlib-compressed data whose compression factor is implausibly
3990 high. Fixes part of bug 2324; reported by "doorss".
3991 - Zero out a few more keys in memory before freeing them. Fixes
3992 bug 2384 and part of bug 2385. These key instances found by
3993 "cypherpunks", based on Andrew Case's report about being able
3994 to find sensitive data in Tor's memory space if you have enough
3995 permissions. Bugfix on 0.0.2pre9.
3997 o Major bugfixes (crashes), also included in 0.2.1.29:
3998 - Prevent calls to Libevent from inside Libevent log handlers.
3999 This had potential to cause a nasty set of crashes, especially
4000 if running Libevent with debug logging enabled, and running
4001 Tor with a controller watching for low-severity log messages.
4002 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
4003 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
4004 underflow errors there too. Fixes the other part of bug 2324.
4005 - Fix a bug where we would assert if we ever had a
4006 cached-descriptors.new file (or another file read directly into
4007 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
4008 on 0.2.1.25. Found by doorss.
4009 - Fix some potential asserts and parsing issues with grossly
4010 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
4013 o Minor bugfixes (other), also included in 0.2.1.29:
4014 - Fix a bug with handling misformed replies to reverse DNS lookup
4015 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
4016 bug reported by doorss.
4017 - Fix compilation on mingw when a pthreads compatibility library
4018 has been installed. (We don't want to use it, so we shouldn't
4019 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
4020 - Fix a bug where we would declare that we had run out of virtual
4021 addresses when the address space was only half-exhausted. Bugfix
4023 - Correctly handle the case where AutomapHostsOnResolve is set but
4024 no virtual addresses are available. Fixes bug 2328; bugfix on
4025 0.1.2.1-alpha. Bug found by doorss.
4026 - Correctly handle wrapping around when we run out of virtual
4027 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
4029 o Minor features, also included in 0.2.1.29:
4030 - Update to the January 1 2011 Maxmind GeoLite Country database.
4031 - Introduce output size checks on all of our decryption functions.
4033 o Build changes, also included in 0.2.1.29:
4034 - Tor does not build packages correctly with Automake 1.6 and earlier;
4035 added a check to Makefile.am to make sure that we're building with
4036 Automake 1.7 or later.
4037 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
4038 because we built it with a too-old version of automake. Thus that
4039 release broke ./configure --enable-openbsd-malloc, which is popular
4040 among really fast exit relays on Linux.
4042 o Major bugfixes, new in 0.2.2.21-alpha:
4043 - Prevent crash/heap corruption when the cbtnummodes consensus
4044 parameter is set to 0 or large values. Fixes bug 2317; bugfix
4047 o Major features, new in 0.2.2.21-alpha:
4048 - Introduce minimum/maximum values that clients will believe
4049 from the consensus. Now we'll have a better chance to avoid crashes
4050 or worse when a consensus param has a weird value.
4052 o Minor features, new in 0.2.2.21-alpha:
4053 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
4054 used on bridges, and it makes bridge scanning somewhat easier.
4055 - If writing the state file to disk fails, wait up to an hour before
4056 retrying again, rather than trying again each second. Fixes bug
4057 2346; bugfix on Tor 0.1.1.3-alpha.
4058 - Make Libevent log messages get delivered to controllers later,
4059 and not from inside the Libevent log handler. This prevents unsafe
4060 reentrant Libevent calls while still letting the log messages
4062 - Detect platforms that brokenly use a signed size_t, and refuse to
4063 build there. Found and analyzed by doorss and rransom.
4064 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
4067 o Minor bugfixes, new in 0.2.2.21-alpha:
4068 - Handle SOCKS messages longer than 128 bytes long correctly, rather
4069 than waiting forever for them to finish. Fixes bug 2330; bugfix
4070 on 0.2.0.16-alpha. Found by doorss.
4071 - Add assertions to check for overflow in arguments to
4072 base32_encode() and base32_decode(); fix a signed-unsigned
4073 comparison there too. These bugs are not actually reachable in Tor,
4074 but it's good to prevent future errors too. Found by doorss.
4075 - Correctly detect failures to create DNS requests when using Libevent
4076 versions before v2. (Before Libevent 2, we used our own evdns
4077 implementation. Its return values for Libevent's evdns_resolve_*()
4078 functions are not consistent with those from Libevent.) Fixes bug
4079 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
4081 o Documentation, new in 0.2.2.21-alpha:
4082 - Document the default socks host and port (127.0.0.1:9050) for
4086 Changes in version 0.2.1.29 - 2011-01-15
4087 Tor 0.2.1.29 continues our recent code security audit work. The main
4088 fix resolves a remote heap overflow vulnerability that can allow remote
4089 code execution. Other fixes address a variety of assert and crash bugs,
4090 most of which we think are hard to exploit remotely.
4092 o Major bugfixes (security):
4093 - Fix a heap overflow bug where an adversary could cause heap
4094 corruption. This bug probably allows remote code execution
4095 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
4097 - Prevent a denial-of-service attack by disallowing any
4098 zlib-compressed data whose compression factor is implausibly
4099 high. Fixes part of bug 2324; reported by "doorss".
4100 - Zero out a few more keys in memory before freeing them. Fixes
4101 bug 2384 and part of bug 2385. These key instances found by
4102 "cypherpunks", based on Andrew Case's report about being able
4103 to find sensitive data in Tor's memory space if you have enough
4104 permissions. Bugfix on 0.0.2pre9.
4106 o Major bugfixes (crashes):
4107 - Prevent calls to Libevent from inside Libevent log handlers.
4108 This had potential to cause a nasty set of crashes, especially
4109 if running Libevent with debug logging enabled, and running
4110 Tor with a controller watching for low-severity log messages.
4111 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
4112 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
4113 underflow errors there too. Fixes the other part of bug 2324.
4114 - Fix a bug where we would assert if we ever had a
4115 cached-descriptors.new file (or another file read directly into
4116 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
4117 on 0.2.1.25. Found by doorss.
4118 - Fix some potential asserts and parsing issues with grossly
4119 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
4122 o Minor bugfixes (other):
4123 - Fix a bug with handling misformed replies to reverse DNS lookup
4124 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
4125 bug reported by doorss.
4126 - Fix compilation on mingw when a pthreads compatibility library
4127 has been installed. (We don't want to use it, so we shouldn't
4128 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
4129 - Fix a bug where we would declare that we had run out of virtual
4130 addresses when the address space was only half-exhausted. Bugfix
4132 - Correctly handle the case where AutomapHostsOnResolve is set but
4133 no virtual addresses are available. Fixes bug 2328; bugfix on
4134 0.1.2.1-alpha. Bug found by doorss.
4135 - Correctly handle wrapping around to when we run out of virtual
4136 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
4137 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
4138 because we built it with a too-old version of automake. Thus that
4139 release broke ./configure --enable-openbsd-malloc, which is popular
4140 among really fast exit relays on Linux.
4143 - Update to the January 1 2011 Maxmind GeoLite Country database.
4144 - Introduce output size checks on all of our decryption functions.
4147 - Tor does not build packages correctly with Automake 1.6 and earlier;
4148 added a check to Makefile.am to make sure that we're building with
4149 Automake 1.7 or later.
4152 Changes in version 0.2.2.20-alpha - 2010-12-17
4153 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
4154 exploitable bugs. We also fix a variety of other significant bugs,
4155 change the IP address for one of our directory authorities, and update
4156 the minimum version that Tor relays must run to join the network.
4159 - Fix a remotely exploitable bug that could be used to crash instances
4160 of Tor remotely by overflowing on the heap. Remote-code execution
4161 hasn't been confirmed, but can't be ruled out. Everyone should
4162 upgrade. Bugfix on the 0.1.1 series and later.
4163 - Fix a bug that could break accounting on 64-bit systems with large
4164 time_t values, making them hibernate for impossibly long intervals.
4165 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
4166 - Fix a logic error in directory_fetches_from_authorities() that
4167 would cause all _non_-exits refusing single-hop-like circuits
4168 to fetch from authorities, when we wanted to have _exits_ fetch
4169 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
4171 - Fix a stream fairness bug that would cause newer streams on a given
4172 circuit to get preference when reading bytes from the origin or
4173 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
4174 introduced before the first Tor release, in svn revision r152.
4176 o Directory authority changes:
4177 - Change IP address and ports for gabelmoo (v3 directory authority).
4180 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
4181 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
4182 - Fix an off-by-one error in calculating some controller command
4183 argument lengths. Fortunately, this mistake is harmless since
4184 the controller code does redundant NUL termination too. Found by
4185 boboper. Bugfix on 0.1.1.1-alpha.
4186 - Do not dereference NULL if a bridge fails to build its
4187 extra-info descriptor. Found by an anonymous commenter on
4188 Trac. Bugfix on 0.2.2.19-alpha.
4191 - Update to the December 1 2010 Maxmind GeoLite Country database.
4192 - Directory authorities now reject relays running any versions of
4193 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
4194 known bugs that keep RELAY_EARLY cells from working on rendezvous
4195 circuits. Followup to fix for bug 2081.
4196 - Directory authorities now reject relays running any version of Tor
4197 older than 0.2.0.26-rc. That version is the earliest that fetches
4198 current directory information correctly. Fixes bug 2156.
4199 - Report only the top 10 ports in exit-port stats in order not to
4200 exceed the maximum extra-info descriptor length of 50 KB. Implements
4204 Changes in version 0.2.1.28 - 2010-12-17
4205 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
4206 exploitable bugs. We also took this opportunity to change the IP address
4207 for one of our directory authorities, and to update the geoip database
4211 - Fix a remotely exploitable bug that could be used to crash instances
4212 of Tor remotely by overflowing on the heap. Remote-code execution
4213 hasn't been confirmed, but can't be ruled out. Everyone should
4214 upgrade. Bugfix on the 0.1.1 series and later.
4216 o Directory authority changes:
4217 - Change IP address and ports for gabelmoo (v3 directory authority).
4220 - Update to the December 1 2010 Maxmind GeoLite Country database.
4223 Changes in version 0.2.1.27 - 2010-11-23
4224 Yet another OpenSSL security patch broke its compatibility with Tor:
4225 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
4226 also took this opportunity to fix several crash bugs, integrate a new
4227 directory authority, and update the bundled GeoIP database.
4230 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
4231 No longer set the tlsext_host_name extension on server SSL objects;
4232 but continue to set it on client SSL objects. Our goal in setting
4233 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
4234 bugfix on 0.2.1.1-alpha.
4235 - Do not log messages to the controller while shrinking buffer
4236 freelists. Doing so would sometimes make the controller connection
4237 try to allocate a buffer chunk, which would mess up the internals
4238 of the freelist and cause an assertion failure. Fixes bug 1125;
4239 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
4240 - Learn our external IP address when we're a relay or bridge, even if
4241 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
4242 where we introduced bridge relays that don't need to publish to
4243 be useful. Fixes bug 2050.
4244 - Do even more to reject (and not just ignore) annotations on
4245 router descriptors received anywhere but from the cache. Previously
4246 we would ignore such annotations at first, but cache them to disk
4247 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
4248 - When you're using bridges and your network goes away and your
4249 bridges get marked as down, recover when you attempt a new socks
4250 connection (if the network is back), rather than waiting up to an
4251 hour to try fetching new descriptors for your bridges. Bugfix on
4252 0.2.0.3-alpha; fixes bug 1981.
4255 - Move to the November 2010 Maxmind GeoLite country db (rather
4256 than the June 2009 ip-to-country GeoIP db) for our statistics that
4257 count how many users relays are seeing from each country. Now we'll
4258 have more accurate data, especially for many African countries.
4260 o New directory authorities:
4261 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
4265 - Fix an assertion failure that could occur in directory caches or
4266 bridge users when using a very short voting interval on a testing
4267 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
4269 - Enforce multiplicity rules when parsing annotations. Bugfix on
4270 0.2.0.8-alpha. Found by piebeer.
4271 - Allow handshaking OR connections to take a full KeepalivePeriod
4272 seconds to handshake. Previously, we would close them after
4273 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4274 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4276 - When building with --enable-gcc-warnings on OpenBSD, disable
4277 warnings in system headers. This makes --enable-gcc-warnings
4278 pass on OpenBSD 4.8.
4281 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
4282 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
4283 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
4284 Servers can start sending this code when enough clients recognize
4285 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
4286 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4287 Patch from mingw-san.
4290 - Remove the old debian/ directory from the main Tor distribution.
4291 The official Tor-for-debian git repository lives at the URL
4292 https://git.torproject.org/debian/tor.git
4293 - Stop shipping the old doc/website/ directory in the tarball. We
4294 changed the website format in late 2010, and what we shipped in
4295 0.2.1.26 really wasn't that useful anyway.
4298 Changes in version 0.2.2.19-alpha - 2010-11-22
4299 Yet another OpenSSL security patch broke its compatibility with Tor:
4300 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
4303 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
4304 No longer set the tlsext_host_name extension on server SSL objects;
4305 but continue to set it on client SSL objects. Our goal in setting
4306 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
4307 bugfix on 0.2.1.1-alpha.
4310 - Try harder not to exceed the maximum length of 50 KB when writing
4311 statistics to extra-info descriptors. This bug was triggered by very
4312 fast relays reporting exit-port, entry, and dirreq statistics.
4313 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
4314 - Publish a router descriptor even if generating an extra-info
4315 descriptor fails. Previously we would not publish a router
4316 descriptor without an extra-info descriptor; this can cause fast
4317 exit relays collecting exit-port statistics to drop from the
4318 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
4321 Changes in version 0.2.2.18-alpha - 2010-11-16
4322 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
4323 us lately, makes unpublished bridge relays able to detect their IP
4324 address, and fixes a wide variety of other bugs to get us much closer
4325 to a stable release.
4328 - Do even more to reject (and not just ignore) annotations on
4329 router descriptors received anywhere but from the cache. Previously
4330 we would ignore such annotations at first, but cache them to disk
4331 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
4332 - Do not log messages to the controller while shrinking buffer
4333 freelists. Doing so would sometimes make the controller connection
4334 try to allocate a buffer chunk, which would mess up the internals
4335 of the freelist and cause an assertion failure. Fixes bug 1125;
4336 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
4337 - Learn our external IP address when we're a relay or bridge, even if
4338 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
4339 where we introduced bridge relays that don't need to publish to
4340 be useful. Fixes bug 2050.
4341 - Maintain separate TLS contexts and certificates for incoming and
4342 outgoing connections in bridge relays. Previously we would use the
4343 same TLS contexts and certs for incoming and outgoing connections.
4344 Bugfix on 0.2.0.3-alpha; addresses bug 988.
4345 - Maintain separate identity keys for incoming and outgoing TLS
4346 contexts in bridge relays. Previously we would use the same
4347 identity keys for incoming and outgoing TLS contexts. Bugfix on
4348 0.2.0.3-alpha; addresses the other half of bug 988.
4349 - Avoid an assertion failure when we as an authority receive a
4350 duplicate upload of a router descriptor that we already have,
4351 but which we previously considered an obsolete descriptor.
4352 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
4353 - Avoid a crash bug triggered by looking at a dangling pointer while
4354 setting the network status consensus. Found by Robert Ransom.
4355 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
4356 - Fix a logic error where servers that _didn't_ act as exits would
4357 try to keep their server lists more aggressively up to date than
4358 exits, when it was supposed to be the other way around. Bugfix
4361 o Minor bugfixes (on Tor 0.2.1.x and earlier):
4362 - When we're trying to guess whether we know our IP address as
4363 a relay, we would log various ways that we failed to guess
4364 our address, but never log that we ended up guessing it
4365 successfully. Now add a log line to help confused and anxious
4366 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
4367 - Bring the logic that gathers routerinfos and assesses the
4368 acceptability of circuits into line. This prevents a Tor OP from
4369 getting locked in a cycle of choosing its local OR as an exit for a
4370 path (due to a .exit request) and then rejecting the circuit because
4371 its OR is not listed yet. It also prevents Tor clients from using an
4372 OR running in the same instance as an exit (due to a .exit request)
4373 if the OR does not meet the same requirements expected of an OR
4374 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
4375 - Correctly describe errors that occur when generating a TLS object.
4376 Previously we would attribute them to a failure while generating a
4377 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
4379 - Enforce multiplicity rules when parsing annotations. Bugfix on
4380 0.2.0.8-alpha. Found by piebeer.
4381 - Fix warnings that newer versions of autoconf produced during
4382 ./autogen.sh. These warnings appear to be harmless in our case,
4383 but they were extremely verbose. Fixes bug 2020.
4385 o Minor bugfixes (on Tor 0.2.2.x):
4386 - Enable protection of small arrays whenever we build with gcc
4387 hardening features, not only when also building with warnings
4388 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
4391 - Make hidden services work better in private Tor networks by not
4392 requiring any uptime to join the hidden service descriptor
4393 DHT. Implements ticket 2088.
4394 - Rate-limit the "your application is giving Tor only an IP address"
4395 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
4396 - When AllowSingleHopExits is set, print a warning to explain to the
4397 relay operator why most clients are avoiding her relay.
4398 - Update to the November 1 2010 Maxmind GeoLite Country database.
4400 o Code simplifications and refactoring:
4401 - When we fixed bug 1038 we had to put in a restriction not to send
4402 RELAY_EARLY cells on rend circuits. This was necessary as long
4403 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
4404 active. Now remove this obsolete check. Resolves bug 2081.
4405 - Some options used different conventions for uppercasing of acronyms
4406 when comparing manpage and source. Fix those in favor of the
4407 manpage, as it makes sense to capitalize acronyms.
4408 - Remove the torrc.complete file. It hasn't been kept up to date
4409 and users will have better luck checking out the manpage.
4410 - Remove the obsolete "NoPublish" option; it has been flagged
4411 as obsolete and has produced a warning since 0.1.1.18-rc.
4412 - Remove everything related to building the expert bundle for OS X.
4413 It has confused many users, doesn't work right on OS X 10.6,
4414 and is hard to get rid of once installed. Resolves bug 1274.
4417 Changes in version 0.2.2.17-alpha - 2010-09-30
4418 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
4419 to use one-hop circuits (which can put the exit relays at higher risk,
4420 plus unbalance the network); fixes a big bug in bandwidth accounting
4421 for relays that want to limit their monthly bandwidth use; fixes a
4422 big pile of bugs in how clients tolerate temporary network failure;
4423 and makes our adaptive circuit build timeout feature (which improves
4424 client performance if your network is fast while not breaking things
4425 if your network is slow) better handle bad networks.
4428 - Exit relays now try harder to block exit attempts from unknown
4429 relays, to make it harder for people to use them as one-hop proxies
4430 a la tortunnel. Controlled by the refuseunknownexits consensus
4431 parameter (currently enabled), or you can override it on your
4432 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
4434 o Major bugfixes (0.2.1.x and earlier):
4435 - Fix a bug in bandwidth accounting that could make us use twice
4436 the intended bandwidth when our interval start changes due to
4437 daylight saving time. Now we tolerate skew in stored vs computed
4438 interval starts: if the start of the period changes by no more than
4439 50% of the period's duration, we remember bytes that we transferred
4440 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
4441 - Always search the Windows system directory for system DLLs, and
4442 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
4443 - When you're using bridges and your network goes away and your
4444 bridges get marked as down, recover when you attempt a new socks
4445 connection (if the network is back), rather than waiting up to an
4446 hour to try fetching new descriptors for your bridges. Bugfix on
4447 0.2.0.3-alpha; fixes bug 1981.
4449 o Major bugfixes (on 0.2.2.x):
4450 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
4452 - Fix a segfault that could happen when operating a bridge relay with
4453 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
4454 - The consensus bandwidth-weights (used by clients to choose fast
4455 relays) entered an unexpected edge case in September where
4456 Exits were much scarcer than Guards, resulting in bad weight
4457 recommendations. Now we compute them using new constraints that
4458 should succeed in all cases. Also alter directory authorities to
4459 not include the bandwidth-weights line if they fail to produce
4460 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
4461 - When weighting bridges during path selection, we used to trust
4462 the bandwidths they provided in their descriptor, only capping them
4463 at 10MB/s. This turned out to be problematic for two reasons:
4464 Bridges could claim to handle a lot more traffic then they
4465 actually would, thus making more clients pick them and have a
4466 pretty effective DoS attack. The other issue is that new bridges
4467 that might not have a good estimate for their bw capacity yet
4468 would not get used at all unless no other bridges are available
4469 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
4471 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
4472 - Ignore cannibalized circuits when recording circuit build times.
4473 This should provide for a minor performance improvement for hidden
4474 service users using 0.2.2.14-alpha, and should remove two spurious
4475 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
4476 - Simplify the logic that causes us to decide if the network is
4477 unavailable for purposes of recording circuit build times. If we
4478 receive no cells whatsoever for the entire duration of a circuit's
4479 full measured lifetime, the network is probably down. Also ignore
4480 one-hop directory fetching circuit timeouts when calculating our
4481 circuit build times. These changes should hopefully reduce the
4482 cases where we see ridiculous circuit build timeouts for people
4483 with spotty wireless connections. Fixes part of bug 1772; bugfix
4485 - Prevent the circuit build timeout from becoming larger than
4486 the maximum build time we have ever seen. Also, prevent the time
4487 period for measurement circuits from becoming larger than twice that
4488 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
4491 - When we run out of directory information such that we can't build
4492 circuits, but then get enough that we can build circuits, log when
4493 we actually construct a circuit, so the user has a better chance of
4494 knowing what's going on. Fixes bug 1362.
4495 - Be more generous with how much bandwidth we'd use up (with
4496 accounting enabled) before entering "soft hibernation". Previously,
4497 we'd refuse new connections and circuits once we'd used up 95% of
4498 our allotment. Now, we use up 95% of our allotment, AND make sure
4499 that we have no more than 500MB (or 3 hours of expected traffic,
4500 whichever is lower) remaining before we enter soft hibernation.
4501 - If we've configured EntryNodes and our network goes away and/or all
4502 our entrynodes get marked down, optimistically retry them all when
4503 a new socks application request appears. Fixes bug 1882.
4504 - Add some more defensive programming for architectures that can't
4505 handle unaligned integer accesses. We don't know of any actual bugs
4506 right now, but that's the best time to fix them. Fixes bug 1943.
4507 - Support line continuations in the torrc config file. If a line
4508 ends with a single backslash character, the newline is ignored, and
4509 the configuration value is treated as continuing on the next line.
4512 o Minor bugfixes (on 0.2.1.x and earlier):
4513 - For bandwidth accounting, calculate our expected bandwidth rate
4514 based on the time during which we were active and not in
4515 soft-hibernation during the last interval. Previously, we were
4516 also considering the time spent in soft-hibernation. If this
4517 was a long time, we would wind up underestimating our bandwidth
4518 by a lot, and skewing our wakeup time towards the start of the
4519 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
4521 o Minor bugfixes (on 0.2.2.x):
4522 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
4523 which were disabled by the circuit build timeout changes in
4524 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
4525 - Make sure we don't warn about missing bandwidth weights when
4526 choosing bridges or other relays not in the consensus. Bugfix on
4527 0.2.2.10-alpha; fixes bug 1805.
4528 - In our logs, do not double-report signatures from unrecognized
4529 authorities both as "from unknown authority" and "not
4530 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
4533 Changes in version 0.2.2.16-alpha - 2010-09-17
4534 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
4535 evident at exit relays), and also continues to resolve all the little
4536 bugs that have been filling up trac lately.
4538 o Major bugfixes (stream-level fairness):
4539 - When receiving a circuit-level SENDME for a blocked circuit, try
4540 to package cells fairly from all the streams that had previously
4541 been blocked on that circuit. Previously, we had started with the
4542 oldest stream, and allowed each stream to potentially exhaust
4543 the circuit's package window. This gave older streams on any
4544 given circuit priority over newer ones. Fixes bug 1937. Detected
4545 originally by Camilo Viecco. This bug was introduced before the
4546 first Tor release, in svn commit r152: it is the new winner of
4547 the longest-lived bug prize.
4548 - When the exit relay got a circuit-level sendme cell, it started
4549 reading on the exit streams, even if had 500 cells queued in the
4550 circuit queue already, so the circuit queue just grew and grew in
4551 some cases. We fix this by not re-enabling reading on receipt of a
4552 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
4553 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
4555 - Newly created streams were allowed to read cells onto circuits,
4556 even if the circuit's cell queue was blocked and waiting to drain.
4557 This created potential unfairness, as older streams would be
4558 blocked, but newer streams would gladly fill the queue completely.
4559 We add code to detect this situation and prevent any stream from
4560 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
4564 - Update to the September 1 2010 Maxmind GeoLite Country database.
4565 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
4566 not. This would lead to a cookie that is still not group readable.
4567 Closes bug 1843. Suggested by katmagic.
4568 - When logging a rate-limited warning, we now mention how many messages
4569 got suppressed since the last warning.
4570 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
4571 do individual connection-level rate limiting of clients. The torrc
4572 config options with the same names trump the consensus params, if
4573 both are present. Replaces the old "bwconnrate" and "bwconnburst"
4574 consensus params which were broken from 0.2.2.7-alpha through
4575 0.2.2.14-alpha. Closes bug 1947.
4576 - When a router changes IP address or port, authorities now launch
4577 a new reachability test for it. Implements ticket 1899.
4578 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
4579 2 no signature, 4 required" messages about consensus signatures
4580 easier to read, and make sure they get logged at the same severity
4581 as the messages explaining which keys are which. Fixes bug 1290.
4582 - Don't warn when we have a consensus that we can't verify because
4583 of missing certificates, unless those certificates are ones
4584 that we have been trying and failing to download. Fixes bug 1145.
4585 - If you configure your bridge with a known identity fingerprint,
4586 and the bridge authority is unreachable (as it is in at least
4587 one country now), fall back to directly requesting the descriptor
4588 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
4590 - When building with --enable-gcc-warnings on OpenBSD, disable
4591 warnings in system headers. This makes --enable-gcc-warnings
4592 pass on OpenBSD 4.8.
4594 o Minor bugfixes (on 0.2.1.x and earlier):
4595 - Authorities will now attempt to download consensuses if their
4596 own efforts to make a live consensus have failed. This change
4597 means authorities that restart will fetch a valid consensus, and
4598 it means authorities that didn't agree with the current consensus
4599 will still fetch and serve it if it has enough signatures. Bugfix
4600 on 0.2.0.9-alpha; fixes bug 1300.
4601 - Ensure DNS requests launched by "RESOLVE" commands from the
4602 controller respect the __LeaveStreamsUnattached setconf options. The
4603 same goes for requests launched via DNSPort or transparent
4604 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
4605 - Allow handshaking OR connections to take a full KeepalivePeriod
4606 seconds to handshake. Previously, we would close them after
4607 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4608 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4610 - Rate-limit "Failed to hand off onionskin" warnings.
4611 - Never relay a cell for a circuit we have already destroyed.
4612 Between marking a circuit as closeable and finally closing it,
4613 it may have been possible for a few queued cells to get relayed,
4614 even though they would have been immediately dropped by the next
4615 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
4616 - Never queue a cell for a circuit that's already been marked
4618 - Never vote for a server as "Running" if we have a descriptor for
4619 it claiming to be hibernating, and that descriptor was published
4620 more recently than our last contact with the server. Bugfix on
4621 0.2.0.3-alpha; fixes bug 911.
4622 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
4625 o Minor bugfixes (on 0.2.2.x):
4626 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
4627 down if a directory fetch fails and you've configured either
4628 bridges or EntryNodes. The intent was to mark the relay as down
4629 _unless_ you're using bridges or EntryNodes, since if you are
4630 then you could quickly run out of entry points.
4631 - Fix the Windows directory-listing code. A bug introduced in
4632 0.2.2.14-alpha could make Windows directory servers forget to load
4633 some of their cached v2 networkstatus files.
4634 - Really allow clients to use relays as bridges. Fixes bug 1776;
4635 bugfix on 0.2.2.15-alpha.
4636 - Demote a warn to info that happens when the CellStatistics option
4637 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
4638 Reported by Moritz Bartl.
4639 - On Windows, build correctly either with or without Unicode support.
4640 This is necessary so that Tor can support fringe platforms like
4641 Windows 98 (which has no Unicode), or Windows CE (which has no
4642 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
4645 - Add a unit test for cross-platform directory-listing code.
4648 Changes in version 0.2.2.15-alpha - 2010-08-18
4649 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
4650 fixes a variety of other bugs that were preventing performance
4651 experiments from moving forward, fixes several bothersome memory leaks,
4652 and generally closes a lot of smaller bugs that have been filling up
4656 - Stop assigning the HSDir flag to relays that disable their
4657 DirPort (and thus will refuse to answer directory requests). This
4658 fix should dramatically improve the reachability of hidden services:
4659 hidden services and hidden service clients pick six HSDir relays
4660 to store and retrieve the hidden service descriptor, and currently
4661 about half of the HSDir relays will refuse to work. Bugfix on
4662 0.2.0.10-alpha; fixes part of bug 1693.
4663 - The PerConnBWRate and Burst config options, along with the
4664 bwconnrate and bwconnburst consensus params, initialized each conn's
4665 token bucket values only when the connection is established. Now we
4666 update them if the config options change, and update them every time
4667 we get a new consensus. Otherwise we can encounter an ugly edge
4668 case where we initialize an OR conn to client-level bandwidth,
4669 but then later the relay joins the consensus and we leave it
4670 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
4671 - Fix a regression that caused Tor to rebind its ports if it receives
4672 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
4675 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
4676 should give us approximately 40-50% more Guard-flagged nodes,
4677 improving the anonymity the Tor network can provide and also
4678 decreasing the dropoff in throughput that relays experience when
4679 they first get the Guard flag.
4680 - Allow enabling or disabling the *Statistics config options while
4684 - Update to the August 1 2010 Maxmind GeoLite Country database.
4685 - Have the controller interface give a more useful message than
4686 "Internal Error" in response to failed GETINFO requests.
4687 - Warn when the same option is provided more than once in a torrc
4688 file, on the command line, or in a single SETCONF statement, and
4689 the option is one that only accepts a single line. Closes bug 1384.
4690 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4691 Patch from mingw-san.
4692 - Add support for the country code "{??}" in torrc options like
4693 ExcludeNodes, to indicate all routers of unknown country. Closes
4695 - Relays report the number of bytes spent on answering directory
4696 requests in extra-info descriptors similar to {read,write}-history.
4697 Implements enhancement 1790.
4699 o Minor bugfixes (on 0.2.1.x and earlier):
4700 - Complain if PublishServerDescriptor is given multiple arguments that
4701 include 0 or 1. This configuration will be rejected in the future.
4702 Bugfix on 0.2.0.1-alpha; closes bug 1107.
4703 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
4704 Bugfix on 0.2.0.13-alpha; closes bug 928.
4705 - Change "Application request when we're believed to be offline."
4706 notice to "Application request when we haven't used client
4707 functionality lately.", to clarify that it's not an error. Bugfix
4708 on 0.0.9.3; fixes bug 1222.
4709 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
4710 would return "551 Internal error" rather than "552 Unrecognized key
4711 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
4712 - Users can't configure a regular relay to be their bridge. It didn't
4713 work because when Tor fetched the bridge descriptor, it found
4714 that it already had it, and didn't realize that the purpose of the
4715 descriptor had changed. Now we replace routers with a purpose other
4716 than bridge with bridge descriptors when fetching them. Bugfix on
4717 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
4718 refetch the descriptor with router purpose 'general', disabling
4720 - Fix a rare bug in rend_fn unit tests: we would fail a test when
4721 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
4722 on 0.2.0.10-alpha; fixes bug 1808.
4723 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
4724 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
4725 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
4726 Servers can start sending this code when enough clients recognize
4727 it. Also update the spec to reflect this new reason. Bugfix on
4728 0.1.0.1-rc; fixes part of bug 1793.
4729 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
4730 when we switch from being a public relay to a bridge. Otherwise
4731 there will still be clients that see the relay in their consensus,
4732 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
4734 - Instead of giving an assertion failure on an internal mismatch
4735 on estimated freelist size, just log a BUG warning and try later.
4736 Mitigates but does not fix bug 1125.
4737 - Fix an assertion failure that could occur in caches or bridge users
4738 when using a very short voting interval on a testing network.
4739 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
4741 o Minor bugfixes (on 0.2.2.x):
4742 - Alter directory authorities to always consider Exit-flagged nodes
4743 as potential Guard nodes in their votes. The actual decision to
4744 use Exits as Guards is done in the consensus bandwidth weights.
4745 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
4746 - When the controller is reporting the purpose of circuits that
4747 didn't finish building before the circuit build timeout, it was
4748 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
4749 - Our libevent version parsing code couldn't handle versions like
4750 1.4.14b-stable and incorrectly warned the user about using an
4751 old and broken version of libevent. Treat 1.4.14b-stable like
4752 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
4754 - Don't use substitution references like $(VAR:MOD) when
4755 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
4756 '$(:x)' to 'x' rather than the empty string. This bites us in
4757 doc/ when configured with --disable-asciidoc. Bugfix on
4758 0.2.2.9-alpha; fixes bug 1773.
4759 - Remove a spurious hidden service server-side log notice about
4760 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
4762 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
4764 - Correctly report written bytes on linked connections. Found while
4765 implementing 1790. Bugfix on 0.2.2.4-alpha.
4766 - Fix three memory leaks: one in circuit_build_times_parse_state(),
4767 one in dirvote_add_signatures_to_pending_consensus(), and one every
4768 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
4769 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
4771 o Code simplifications and refactoring:
4772 - Take a first step towards making or.h smaller by splitting out
4773 function definitions for all source files in src/or/. Leave
4774 structures and defines in or.h for now.
4775 - Remove a bunch of unused function declarations as well as a block of
4776 #if 0'd code from the unit tests. Closes bug 1824.
4777 - New unit tests for exit-port history statistics; refactored exit
4778 statistics code to be more easily tested.
4779 - Remove the old debian/ directory from the main Tor distribution.
4780 The official Tor-for-debian git repository lives at the URL
4781 https://git.torproject.org/debian/tor.git
4784 Changes in version 0.2.2.14-alpha - 2010-07-12
4785 Tor 0.2.2.14-alpha greatly improves client-side handling of
4786 circuit build timeouts, which are used to estimate speed and improve
4787 performance. We also move to a much better GeoIP database, port Tor to
4788 Windows CE, introduce new compile flags that improve code security,
4789 add an eighth v3 directory authority, and address a lot of more
4793 - Tor directory authorities no longer crash when started with a
4794 cached-microdesc-consensus file in their data directory. Bugfix
4795 on 0.2.2.6-alpha; fixes bug 1532.
4796 - Treat an unset $HOME like an empty $HOME rather than triggering an
4797 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
4798 - Ignore negative and large circuit build timeout values that can
4799 happen during a suspend or hibernate. These values caused various
4800 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
4801 - Alter calculation of Pareto distribution parameter 'Xm' for
4802 Circuit Build Timeout learning to use the weighted average of the
4803 top N=3 modes (because we have three entry guards). Considering
4804 multiple modes should improve the timeout calculation in some cases,
4805 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
4807 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
4808 right censored distribution model. This approach improves over the
4809 synthetic timeout generation approach that was producing insanely
4810 high timeout values. Now we calculate build timeouts using truncated
4811 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
4812 - Do not close circuits that are under construction when they reach
4813 the circuit build timeout. Instead, leave them building (but do not
4814 use them) for up until the time corresponding to the 95th percentile
4815 on the Pareto CDF or 60 seconds, whichever is greater. This is done
4816 to provide better data for the new Pareto model. This percentile
4817 can be controlled by the consensus.
4820 - Move to the June 2010 Maxmind GeoLite country db (rather than the
4821 June 2009 ip-to-country GeoIP db) for our statistics that count
4822 how many users relays are seeing from each country. Now we have
4823 more accurate data for many African countries.
4824 - Port Tor to build and run correctly on Windows CE systems, using
4825 the wcecompat library. Contributed by Valerio Lupi.
4826 - New "--enable-gcc-hardening" ./configure flag (off by default)
4827 to turn on gcc compile time hardening options. It ensures
4828 that signed ints have defined behavior (-fwrapv), enables
4829 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
4830 with canaries (-fstack-protector-all), turns on ASLR protection if
4831 supported by the kernel (-fPIE, -pie), and adds additional security
4832 related warnings. Verified to work on Mac OS X and Debian Lenny.
4833 - New "--enable-linker-hardening" ./configure flag (off by default)
4834 to turn on ELF specific hardening features (relro, now). This does
4835 not work with Mac OS X or any other non-ELF binary format.
4837 o New directory authorities:
4838 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
4842 - New config option "WarnUnsafeSocks 0" disables the warning that
4843 occurs whenever Tor receives a socks handshake using a version of
4844 the socks protocol that can only provide an IP address (rather
4845 than a hostname). Setups that do DNS locally over Tor are fine,
4846 and we shouldn't spam the logs in that case.
4847 - Convert the HACKING file to asciidoc, and add a few new sections
4848 to it, explaining how we use Git, how we make changelogs, and
4849 what should go in a patch.
4850 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
4851 event, to give information on the current rate of circuit timeouts
4852 over our stored history.
4853 - Add ability to disable circuit build time learning via consensus
4854 parameter and via a LearnCircuitBuildTimeout config option. Also
4855 automatically disable circuit build time calculation if we are
4856 either a AuthoritativeDirectory, or if we fail to write our state
4857 file. Fixes bug 1296.
4858 - More gracefully handle corrupt state files, removing asserts
4859 in favor of saving a backup and resetting state.
4860 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
4864 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4866 - When a2x fails, mention that the user could disable manpages instead
4867 of trying to fix their asciidoc installation.
4868 - Where available, use Libevent 2.0's periodic timers so that our
4869 once-per-second cleanup code gets called even more closely to
4870 once per second than it would otherwise. Fixes bug 943.
4871 - If you run a bridge that listens on multiple IP addresses, and
4872 some user configures a bridge address that uses a different IP
4873 address than your bridge writes in its router descriptor, and the
4874 user doesn't specify an identity key, their Tor would discard the
4875 descriptor because "it isn't one of our configured bridges", and
4876 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
4877 Bugfix on 0.2.0.3-alpha.
4878 - If OpenSSL fails to make a duplicate of a private or public key, log
4879 an error message and try to exit cleanly. May help with debugging
4880 if bug 1209 ever remanifests.
4881 - Save a couple bytes in memory allocation every time we escape
4882 certain characters in a string. Patch from Florian Zumbiehl.
4883 - Make it explicit that we don't cannibalize one-hop circuits. This
4884 happens in the wild, but doesn't turn out to be a problem because
4885 we fortunately don't use those circuits. Many thanks to outofwords
4886 for the initial analysis and to swissknife who confirmed that
4887 two-hop circuits are actually created.
4888 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
4889 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
4890 - Eliminate a case where a circuit build time warning was displayed
4891 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
4894 Changes in version 0.2.1.26 - 2010-05-02
4895 Tor 0.2.1.26 addresses the recent connection and memory overload
4896 problems we've been seeing on relays, especially relays with their
4897 DirPort open. If your relay has been crashing, or you turned it off
4898 because it used too many resources, give this release a try.
4900 This release also fixes yet another instance of broken OpenSSL libraries
4901 that was causing some relays to drop out of the consensus.
4904 - Teach relays to defend themselves from connection overload. Relays
4905 now close idle circuits early if it looks like they were intended
4906 for directory fetches. Relays are also more aggressive about closing
4907 TLS connections that have no circuits on them. Such circuits are
4908 unlikely to be re-used, and tens of thousands of them were piling
4909 up at the fast relays, causing the relays to run out of sockets
4910 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4911 their directory fetches over TLS).
4912 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4913 that claim to be earlier than 0.9.8m, but which have in reality
4914 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4915 behavior. Possible fix for some cases of bug 1346.
4916 - Directory mirrors were fetching relay descriptors only from v2
4917 directory authorities, rather than v3 authorities like they should.
4918 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4919 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4922 - Finally get rid of the deprecated and now harmful notion of "clique
4923 mode", where directory authorities maintain TLS connections to
4927 - In the util/threads test, no longer free the test_mutex before all
4928 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4929 - The master thread could starve the worker threads quite badly on
4930 certain systems, causing them to run only partially in the allowed
4931 window. This resulted in test failures. Now the master thread sleeps
4932 occasionally for a few microseconds while the two worker-threads
4933 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4936 Changes in version 0.2.2.13-alpha - 2010-04-24
4937 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
4938 problems we've been seeing on relays, especially relays with their
4939 DirPort open. If your relay has been crashing, or you turned it off
4940 because it used too many resources, give this release a try.
4943 - Teach relays to defend themselves from connection overload. Relays
4944 now close idle circuits early if it looks like they were intended
4945 for directory fetches. Relays are also more aggressive about closing
4946 TLS connections that have no circuits on them. Such circuits are
4947 unlikely to be re-used, and tens of thousands of them were piling
4948 up at the fast relays, causing the relays to run out of sockets
4949 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4950 their directory fetches over TLS).
4953 - Finally get rid of the deprecated and now harmful notion of "clique
4954 mode", where directory authorities maintain TLS connections to
4956 - Directory authorities now do an immediate reachability check as soon
4957 as they hear about a new relay. This change should slightly reduce
4958 the time between setting up a relay and getting listed as running
4959 in the consensus. It should also improve the time between setting
4960 up a bridge and seeing use by bridge users.
4961 - Directory authorities no longer launch a TLS connection to every
4962 relay as they startup. Now that we have 2k+ descriptors cached,
4963 the resulting network hiccup is becoming a burden. Besides,
4964 authorities already avoid voting about Running for the first half
4965 hour of their uptime.
4968 Changes in version 0.2.2.12-alpha - 2010-04-20
4969 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
4970 handle and vote on descriptors. It was causing relays to drop out of
4974 - Many relays have been falling out of the consensus lately because
4975 not enough authorities know about their descriptor for them to get
4976 a majority of votes. When we deprecated the v2 directory protocol,
4977 we got rid of the only way that v3 authorities can hear from each
4978 other about other descriptors. Now authorities examine every v3
4979 vote for new descriptors, and fetch them from that authority. Bugfix
4981 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
4982 and a warning in or.h related to bandwidth_weight_rule_t that
4983 prevented clean compile on OS X. Fixes bug 1363; bugfix on
4985 - Fix a segfault on relays when DirReqStatistics is enabled
4986 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
4990 - Demote a confusing TLS warning that relay operators might get when
4991 someone tries to talk to their OrPort. It is neither the operator's
4992 fault nor can they do anything about it. Fixes bug 1364; bugfix
4996 Changes in version 0.2.2.11-alpha - 2010-04-15
4997 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
4998 libraries that was causing some relays to drop out of the consensus.
5001 - Directory mirrors were fetching relay descriptors only from v2
5002 directory authorities, rather than v3 authorities like they should.
5003 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
5004 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
5005 - Fix a parsing error that made every possible value of
5006 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
5007 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
5008 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
5009 about the option without breaking older ones.
5010 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
5011 that claim to be earlier than 0.9.8m, but which have in reality
5012 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
5013 behavior. Possible fix for some cases of bug 1346.
5016 - Experiment with a more aggressive approach to preventing clients
5017 from making one-hop exit streams. Exit relays who want to try it
5018 out can set "RefuseUnknownExits 1" in their torrc, and then look
5019 for "Attempt by %s to open a stream" log messages. Let us know
5021 - Add support for statically linking zlib by specifying
5022 --enable-static-zlib, to go with our support for statically linking
5023 openssl and libevent. Resolves bug 1358.
5026 - Fix a segfault that happens whenever a Tor client that is using
5027 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
5029 - When we cleaned up the contrib/tor-exit-notice.html file, we left
5030 out the first line. Fixes bug 1295.
5031 - When building the manpage from a tarball, we required asciidoc, but
5032 the asciidoc -> roff/html conversion was already done for the
5033 tarball. Make 'make' complain only when we need asciidoc (either
5034 because we're compiling directly from git, or because we altered
5035 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
5036 - When none of the directory authorities vote on any params, Tor
5037 segfaulted when trying to make the consensus from the votes. We
5038 didn't trigger the bug in practice, because authorities do include
5039 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
5042 - In the util/threads test, no longer free the test_mutex before all
5043 worker threads have finished. Bugfix on 0.2.1.6-alpha.
5044 - The master thread could starve the worker threads quite badly on
5045 certain systems, causing them to run only partially in the allowed
5046 window. This resulted in test failures. Now the master thread sleeps
5047 occasionally for a few microseconds while the two worker-threads
5048 compete for the mutex. Bugfix on 0.2.0.1-alpha.
5051 Changes in version 0.2.2.10-alpha - 2010-03-07
5052 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
5053 could prevent relays from guessing their IP address correctly. It also
5054 starts the groundwork for another client-side performance boost, since
5055 currently we're not making efficient use of relays that have both the
5056 Guard flag and the Exit flag.
5059 - Fix a regression from our patch for bug 1244 that caused relays
5060 to guess their IP address incorrectly if they didn't set Address
5061 in their torrc and/or their address fails to resolve. Bugfix on
5062 0.2.2.9-alpha; fixes bug 1269.
5064 o Major features (performance):
5065 - Directory authorities now compute consensus weightings that instruct
5066 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
5067 and no flag. Clients that use these weightings will distribute
5068 network load more evenly across these different relay types. The
5069 weightings are in the consensus so we can change them globally in
5070 the future. Extra thanks to "outofwords" for finding some nasty
5071 security bugs in the first implementation of this feature.
5073 o Minor features (performance):
5074 - Always perform router selections using weighted relay bandwidth,
5075 even if we don't need a high capacity circuit at the time. Non-fast
5076 circuits now only differ from fast ones in that they can use relays
5077 not marked with the Fast flag. This "feature" could turn out to
5078 be a horrible bug; we should investigate more before it goes into
5082 - Allow disabling building of the manpages. Skipping the manpage
5083 speeds up the build considerably.
5085 o Minor bugfixes (on 0.2.2.x):
5086 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
5087 Bugfix on 0.2.2.9-alpha.
5088 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
5089 config option. Bugfix on 0.2.2.7-alpha.
5090 - Ship the asciidoc-helper file in the tarball, so that people can
5091 build from source if they want to, and touching the .1.txt files
5092 doesn't break the build. Bugfix on 0.2.2.9-alpha.
5094 o Minor bugfixes (on 0.2.1.x or earlier):
5095 - Fix a dereference-then-NULL-check sequence when publishing
5096 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
5098 - Fix another dereference-then-NULL-check sequence. Bugfix on
5099 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
5100 - Make sure we treat potentially not NUL-terminated strings correctly.
5101 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
5103 o Code simplifications and refactoring:
5104 - Fix some urls in the exit notice file and make it XHTML1.1 strict
5105 compliant. Based on a patch from Christian Kujau.
5106 - Don't use sed in asciidoc-helper anymore.
5107 - Make the build process fail if asciidoc cannot be found and
5108 building with asciidoc isn't disabled.
5111 Changes in version 0.2.2.9-alpha - 2010-02-22
5112 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
5113 location of a directory authority, and cleans up a bunch of small bugs.
5115 o Directory authority changes:
5116 - Change IP address for dannenberg (v3 directory authority), and
5117 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
5118 service directory authority) from the list.
5121 - Make Tor work again on the latest OS X: when deciding whether to
5122 use strange flags to turn TLS renegotiation on, detect the OpenSSL
5123 version at run-time, not compile time. We need to do this because
5124 Apple doesn't update its dev-tools headers when it updates its
5125 libraries in a security patch.
5126 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
5127 that could happen on 32-bit platforms with 64-bit time_t. Also fix
5128 a memory leak when requesting a hidden service descriptor we've
5129 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
5131 - Authorities could be tricked into giving out the Exit flag to relays
5132 that didn't allow exiting to any ports. This bug could screw
5133 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
5134 1238. Bug discovered by Martin Kowalczyk.
5135 - When freeing a session key, zero it out completely. We only zeroed
5136 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
5137 patched by ekir. Fixes bug 1254.
5140 - Fix static compilation by listing the openssl libraries in the right
5141 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
5142 - Resume handling .exit hostnames in a special way: originally we
5143 stripped the .exit part and used the requested exit relay. In
5144 0.2.2.1-alpha we stopped treating them in any special way, meaning
5145 if you use a .exit address then Tor will pass it on to the exit
5146 relay. Now we reject the .exit stream outright, since that behavior
5147 might be more expected by the user. Found and diagnosed by Scott
5148 Bennett and Downie on or-talk.
5149 - Don't spam the controller with events when we have no file
5150 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
5151 for log messages was already solved from bug 748.)
5152 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
5154 - Make the DNSPort option work with libevent 2.x. Don't alter the
5155 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
5156 - Emit a GUARD DROPPED controller event for a case we missed.
5157 - Make more fields in the controller protocol case-insensitive, since
5158 control-spec.txt said they were.
5159 - Refactor resolve_my_address() to not use gethostbyname() anymore.
5160 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
5161 - Fix a spec conformance issue: the network-status-version token
5162 must be the first token in a v3 consensus or vote. Discovered by
5163 parakeep. Bugfix on 0.2.0.3-alpha.
5165 o Code simplifications and refactoring:
5166 - Generate our manpage and HTML documentation using Asciidoc. This
5167 change should make it easier to maintain the documentation, and
5169 - Remove the --enable-iphone option. According to reports from Marco
5170 Bonetti, Tor builds fine without any special tweaking on recent
5171 iPhone SDK versions.
5172 - Removed some unnecessary files from the source distribution. The
5173 AUTHORS file has now been merged into the people page on the
5174 website. The roadmaps and design doc can now be found in the
5175 projects directory in svn.
5176 - Enabled various circuit build timeout constants to be controlled
5177 by consensus parameters. Also set better defaults for these
5178 parameters based on experimentation on broadband and simulated
5182 - The 'EXTENDCIRCUIT' control port command can now be used with
5183 a circ id of 0 and no path. This feature will cause Tor to build
5184 a new 'fast' general purpose circuit using its own path selection
5186 - Added a BUILDTIMEOUT_SET controller event to describe changes
5187 to the circuit build timeout.
5188 - Future-proof the controller protocol a bit by ignoring keyword
5189 arguments we do not recognize.
5190 - Expand homedirs passed to tor-checkkey. This should silence a
5191 coverity complaint about passing a user-supplied string into
5192 open() without checking it.
5195 Changes in version 0.2.1.25 - 2010-03-16
5196 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
5197 prevent relays from guessing their IP address correctly. It also fixes
5198 several minor potential security bugs.
5201 - Fix a regression from our patch for bug 1244 that caused relays
5202 to guess their IP address incorrectly if they didn't set Address
5203 in their torrc and/or their address fails to resolve. Bugfix on
5204 0.2.1.23; fixes bug 1269.
5205 - When freeing a session key, zero it out completely. We only zeroed
5206 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
5207 patched by ekir. Fixes bug 1254.
5210 - Fix a dereference-then-NULL-check sequence when publishing
5211 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
5213 - Fix another dereference-then-NULL-check sequence. Bugfix on
5214 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
5215 - Make sure we treat potentially not NUL-terminated strings correctly.
5216 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
5220 Changes in version 0.2.1.24 - 2010-02-21
5221 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
5225 - Work correctly out-of-the-box with even more vendor-patched versions
5226 of OpenSSL. In particular, make it so Debian and OS X don't need
5227 customized patches to run/build.
5230 Changes in version 0.2.1.23 - 2010-02-13
5231 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
5232 again on the latest OS X, and updates the location of a directory
5235 o Major bugfixes (performance):
5236 - We were selecting our guards uniformly at random, and then weighting
5237 which of our guards we'd use uniformly at random. This imbalance
5238 meant that Tor clients were severely limited on throughput (and
5239 probably latency too) by the first hop in their circuit. Now we
5240 select guards weighted by currently advertised bandwidth. We also
5241 automatically discard guards picked using the old algorithm. Fixes
5242 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
5245 - Make Tor work again on the latest OS X: when deciding whether to
5246 use strange flags to turn TLS renegotiation on, detect the OpenSSL
5247 version at run-time, not compile time. We need to do this because
5248 Apple doesn't update its dev-tools headers when it updates its
5249 libraries in a security patch.
5250 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
5251 that could happen on 32-bit platforms with 64-bit time_t. Also fix
5252 a memory leak when requesting a hidden service descriptor we've
5253 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
5256 o Directory authority changes:
5257 - Change IP address for dannenberg (v3 directory authority), and
5258 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
5259 service directory authority) from the list.
5262 - Refactor resolve_my_address() to not use gethostbyname() anymore.
5263 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
5266 - Avoid a mad rush at the beginning of each month when each client
5267 rotates half of its guards. Instead we spread the rotation out
5268 throughout the month, but we still avoid leaving a precise timestamp
5269 in the state file about when we first picked the guard. Improves
5270 over the behavior introduced in 0.1.2.17.
5273 Changes in version 0.2.2.8-alpha - 2010-01-26
5274 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
5275 causing bridge relays to disappear. If you're running a bridge,
5279 - Fix a memory corruption bug on bridges that occured during the
5280 inclusion of stats data in extra-info descriptors. Also fix the
5281 interface for geoip_get_bridge_stats* to prevent similar bugs in
5282 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
5283 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
5286 - Ignore OutboundBindAddress when connecting to localhost.
5287 Connections to localhost need to come _from_ localhost, or else
5288 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
5292 Changes in version 0.2.2.7-alpha - 2010-01-19
5293 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
5294 as laying the groundwork for further relay-side performance fixes. It
5295 also starts cleaning up client behavior with respect to the EntryNodes,
5296 ExitNodes, and StrictNodes config options.
5298 This release also rotates two directory authority keys, due to a
5299 security breach of some of the Torproject servers.
5301 o Directory authority changes:
5302 - Rotate keys (both v3 identity and relay identity) for moria1
5305 o Major features (performance):
5306 - We were selecting our guards uniformly at random, and then weighting
5307 which of our guards we'd use uniformly at random. This imbalance
5308 meant that Tor clients were severely limited on throughput (and
5309 probably latency too) by the first hop in their circuit. Now we
5310 select guards weighted by currently advertised bandwidth. We also
5311 automatically discard guards picked using the old algorithm. Fixes
5312 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
5313 - When choosing which cells to relay first, relays can now favor
5314 circuits that have been quiet recently, to provide lower latency
5315 for low-volume circuits. By default, relays enable or disable this
5316 feature based on a setting in the consensus. You can override
5317 this default by using the new "CircuitPriorityHalflife" config
5318 option. Design and code by Ian Goldberg, Can Tang, and Chris
5320 - Add separate per-conn write limiting to go with the per-conn read
5321 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
5322 but never per-conn write limits.
5323 - New consensus params "bwconnrate" and "bwconnburst" to let us
5324 rate-limit client connections as they enter the network. It's
5325 controlled in the consensus so we can turn it on and off for
5326 experiments. It's starting out off. Based on proposal 163.
5328 o Major features (relay selection options):
5329 - Switch to a StrictNodes config option, rather than the previous
5330 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
5331 "StrictExcludeNodes" option.
5332 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
5333 change during a config reload, mark and discard all our origin
5334 circuits. This fix should address edge cases where we change the
5335 config options and but then choose a circuit that we created before
5337 - If EntryNodes or ExitNodes are set, be more willing to use an
5338 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
5340 - Make EntryNodes config option much more aggressive even when
5341 StrictNodes is not set. Before it would prepend your requested
5342 entrynodes to your list of guard nodes, but feel free to use others
5343 after that. Now it chooses only from your EntryNodes if any of
5344 those are available, and only falls back to others if a) they're
5345 all down and b) StrictNodes is not set.
5346 - Now we refresh your entry guards from EntryNodes at each consensus
5347 fetch -- rather than just at startup and then they slowly rot as
5348 the network changes.
5351 - Stop bridge directory authorities from answering dbg-stability.txt
5352 directory queries, which would let people fetch a list of all
5353 bridge identities they track. Bugfix on 0.2.1.6-alpha.
5356 - Log a notice when we get a new control connection. Now it's easier
5357 for security-conscious users to recognize when a local application
5358 is knocking on their controller door. Suggested by bug 1196.
5359 - New config option "CircuitStreamTimeout" to override our internal
5360 timeout schedule for how many seconds until we detach a stream from
5361 a circuit and try a new circuit. If your network is particularly
5362 slow, you might want to set this to a number like 60.
5363 - New controller command "getinfo config-text". It returns the
5364 contents that Tor would write if you send it a SAVECONF command,
5365 so the controller can write the file to disk itself.
5366 - New options for SafeLogging to allow scrubbing only log messages
5367 generated while acting as a relay.
5368 - Ship the bridges spec file in the tarball too.
5369 - Avoid a mad rush at the beginning of each month when each client
5370 rotates half of its guards. Instead we spread the rotation out
5371 throughout the month, but we still avoid leaving a precise timestamp
5372 in the state file about when we first picked the guard. Improves
5373 over the behavior introduced in 0.1.2.17.
5375 o Minor bugfixes (compiling):
5376 - Fix compilation on OS X 10.3, which has a stub mlockall() but
5377 hides it. Bugfix on 0.2.2.6-alpha.
5378 - Fix compilation on Solaris by removing support for the
5379 DisableAllSwap config option. Solaris doesn't have an rlimit for
5380 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
5383 o Minor bugfixes (crashes):
5384 - Do not segfault when writing buffer stats when we haven't observed
5385 a single circuit to report about. Found by Fabian Lanze. Bugfix on
5387 - If we're in the pathological case where there's no exit bandwidth
5388 but there is non-exit bandwidth, or no guard bandwidth but there
5389 is non-guard bandwidth, don't crash during path selection. Bugfix
5391 - Fix an impossible-to-actually-trigger buffer overflow in relay
5392 descriptor generation. Bugfix on 0.1.0.15.
5394 o Minor bugfixes (privacy):
5395 - Fix an instance where a Tor directory mirror might accidentally
5396 log the IP address of a misbehaving Tor client. Bugfix on
5398 - Don't list Windows capabilities in relay descriptors. We never made
5399 use of them, and maybe it's a bad idea to publish them. Bugfix
5402 o Minor bugfixes (other):
5403 - Resolve an edge case in path weighting that could make us misweight
5404 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
5405 - Fix statistics on client numbers by country as seen by bridges that
5406 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
5407 intervals instead of variable 12-to-48-hour intervals.
5408 - After we free an internal connection structure, overwrite it
5409 with a different memory value than we use for overwriting a freed
5410 internal circuit structure. Should help with debugging. Suggested
5412 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
5416 - Remove the HSAuthorityRecordStats option that version 0 hidden
5417 service authorities could have used to track statistics of overall
5418 hidden service usage.
5421 Changes in version 0.2.1.22 - 2010-01-19
5422 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
5423 authorities -- it would tell you its whole history of bridge descriptors
5424 if you make the right directory request. This stable update also
5425 rotates two of the seven v3 directory authority keys and locations.
5427 o Directory authority changes:
5428 - Rotate keys (both v3 identity and relay identity) for moria1
5432 - Stop bridge directory authorities from answering dbg-stability.txt
5433 directory queries, which would let people fetch a list of all
5434 bridge identities they track. Bugfix on 0.2.1.6-alpha.
5437 Changes in version 0.2.1.21 - 2009-12-21
5438 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
5439 library. If you use Tor on Linux / Unix and you're getting SSL
5440 renegotiation errors, upgrading should help. We also recommend an
5441 upgrade if you're an exit relay.
5444 - Work around a security feature in OpenSSL 0.9.8l that prevents our
5445 handshake from working unless we explicitly tell OpenSSL that we
5446 are using SSL renegotiation safely. We are, of course, but OpenSSL
5447 0.9.8l won't work unless we say we are.
5448 - Avoid crashing if the client is trying to upload many bytes and the
5449 circuit gets torn down at the same time, or if the flip side
5450 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
5453 - Do not refuse to learn about authority certs and v2 networkstatus
5454 documents that are older than the latest consensus. This bug might
5455 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
5456 Spotted and fixed by xmux.
5457 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
5458 trigger platform-specific option misparsing case found by Coverity
5460 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
5461 trigger assert. Fixes bug 1173.
5464 Changes in version 0.2.2.6-alpha - 2009-11-19
5465 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
5466 support for the new lower-footprint "microdescriptor" directory design,
5467 future-proofing our consensus format against new hash functions or
5468 other changes, and an Android port. It also makes Tor compatible with
5469 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
5472 - Directory authorities can now create, vote on, and serve multiple
5473 parallel formats of directory data as part of their voting process.
5474 Partially implements Proposal 162: "Publish the consensus in
5476 - Directory authorities can now agree on and publish small summaries
5477 of router information that clients can use in place of regular
5478 server descriptors. This transition will eventually allow clients
5479 to use far less bandwidth for downloading information about the
5480 network. Begins the implementation of Proposal 158: "Clients
5481 download consensus + microdescriptors".
5482 - The directory voting system is now extensible to use multiple hash
5483 algorithms for signatures and resource selection. Newer formats
5484 are signed with SHA256, with a possibility for moving to a better
5485 hash algorithm in the future.
5486 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
5487 current and future memory pages via mlockall(). On supported
5488 platforms (modern Linux and probably BSD but not Windows or OS X),
5489 this should effectively disable any and all attempts to page out
5490 memory. This option requires that you start your Tor as root --
5491 if you use DisableAllSwap, please consider using the User option
5492 to properly reduce the privileges of your Tor.
5493 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
5494 to help Tor build correctly for Android phones.
5497 - Work around a security feature in OpenSSL 0.9.8l that prevents our
5498 handshake from working unless we explicitly tell OpenSSL that we
5499 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
5500 won't work unless we say we are.
5503 - Fix a crash bug when trying to initialize the evdns module in
5504 Libevent 2. Bugfix on 0.2.1.16-rc.
5505 - Stop logging at severity 'warn' when some other Tor client tries
5506 to establish a circuit with us using weak DH keys. It's a protocol
5507 violation, but that doesn't mean ordinary users need to hear about
5508 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
5509 - Do not refuse to learn about authority certs and v2 networkstatus
5510 documents that are older than the latest consensus. This bug might
5511 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
5512 Spotted and fixed by xmux.
5513 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
5514 - If all authorities restart at once right before a consensus vote,
5515 nobody will vote about "Running", and clients will get a consensus
5516 with no usable relays. Instead, authorities refuse to build a
5517 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
5518 - If your relay can't keep up with the number of incoming create
5519 cells, it would log one warning per failure into your logs. Limit
5520 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
5521 - Bridges now use "reject *:*" as their default exit policy. Bugfix
5522 on 0.2.0.3-alpha; fixes bug 1113.
5523 - Fix a memory leak on directory authorities during voting that was
5524 introduced in 0.2.2.1-alpha. Found via valgrind.
5527 Changes in version 0.2.1.20 - 2009-10-15
5528 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
5529 services at once, prepares for more performance improvements, and
5530 fixes a bunch of smaller bugs.
5532 The Windows and OS X bundles also include a more recent Vidalia,
5533 and switch from Privoxy to Polipo.
5535 The OS X installers are now drag and drop. It's best to un-install
5536 Tor/Vidalia and then install this new bundle, rather than upgrade. If
5537 you want to upgrade, you'll need to update the paths for Tor and Polipo
5538 in the Vidalia Settings window.
5541 - Send circuit or stream sendme cells when our window has decreased
5542 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5543 by Karsten when testing the "reduce circuit window" performance
5544 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5545 before the release of Tor 0.0.0. This is the new winner of the
5547 - Fix a remotely triggerable memory leak when a consensus document
5548 contains more than one signature from the same voter. Bugfix on
5550 - Avoid segfault in rare cases when finishing an introduction circuit
5551 as a client and finding out that we don't have an introduction key
5552 for it. Fixes bug 1073. Reported by Aaron Swartz.
5555 - Tor now reads the "circwindow" parameter out of the consensus,
5556 and uses that value for its circuit package window rather than the
5557 default of 1000 cells. Begins the implementation of proposal 168.
5559 o New directory authorities:
5560 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5562 - Move moria1 and tonga to alternate IP addresses.
5565 - Fix a signed/unsigned compile warning in 0.2.1.19.
5566 - Fix possible segmentation fault on directory authorities. Bugfix on
5568 - Fix an extremely rare infinite recursion bug that could occur if
5569 we tried to log a message after shutting down the log subsystem.
5570 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5571 - Fix an obscure bug where hidden services on 64-bit big-endian
5572 systems might mis-read the timestamp in v3 introduce cells, and
5573 refuse to connect back to the client. Discovered by "rotor".
5574 Bugfix on 0.2.1.6-alpha.
5575 - We were triggering a CLOCK_SKEW controller status event whenever
5576 we connect via the v2 connection protocol to any relay that has
5577 a wrong clock. Instead, we should only inform the controller when
5578 it's a trusted authority that claims our clock is wrong. Bugfix
5579 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5580 - We were telling the controller about CHECKING_REACHABILITY and
5581 REACHABILITY_FAILED status events whenever we launch a testing
5582 circuit or notice that one has failed. Instead, only tell the
5583 controller when we want to inform the user of overall success or
5584 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5586 - Don't warn when we're using a circuit that ends with a node
5587 excluded in ExcludeExitNodes, but the circuit is not used to access
5588 the outside world. This should help fix bug 1090. Bugfix on
5590 - Work around a small memory leak in some versions of OpenSSL that
5591 stopped the memory used by the hostname TLS extension from being
5595 - Add a "getinfo status/accepted-server-descriptor" controller
5596 command, which is the recommended way for controllers to learn
5597 whether our server descriptor has been successfully received by at
5598 least on directory authority. Un-recommend good-server-descriptor
5599 getinfo and status events until we have a better design for them.
5602 Changes in version 0.2.2.5-alpha - 2009-10-11
5603 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
5606 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
5608 o Directory authorities:
5609 - Temporarily (just for this release) move dizum to an alternate
5613 Changes in version 0.2.2.4-alpha - 2009-10-10
5614 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
5615 introduces a new unit test framework, shifts directry authority
5616 addresses around to reduce the impact from recent blocking events,
5617 and fixes a few smaller bugs.
5620 - Fix several more asserts in the circuit_build_times code, for
5621 example one that causes Tor to fail to start once we have
5622 accumulated 5000 build times in the state file. Bugfixes on
5623 0.2.2.2-alpha; fixes bug 1108.
5625 o New directory authorities:
5626 - Move moria1 and Tonga to alternate IP addresses.
5629 - Log SSL state transitions at debug level during handshake, and
5630 include SSL states in error messages. This may help debug future
5631 SSL handshake issues.
5632 - Add a new "Handshake" log domain for activities that happen
5633 during the TLS handshake.
5634 - Revert to the "June 3 2009" ip-to-country file. The September one
5635 seems to have removed most US IP addresses.
5636 - Directory authorities now reject Tor relays with versions less than
5637 0.1.2.14. This step cuts out four relays from the current network,
5638 none of which are very big.
5641 - Fix a couple of smaller issues with gathering statistics. Bugfixes
5643 - Fix two memory leaks in the error case of
5644 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
5645 - Don't count one-hop circuits when we're estimating how long it
5646 takes circuits to build on average. Otherwise we'll set our circuit
5647 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
5648 - Directory authorities no longer change their opinion of, or vote on,
5649 whether a router is Running, unless they have themselves been
5650 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
5653 o Code simplifications and refactoring:
5654 - Revise our unit tests to use the "tinytest" framework, so we
5655 can run tests in their own processes, have smarter setup/teardown
5656 code, and so on. The unit test code has moved to its own
5657 subdirectory, and has been split into multiple modules.
5660 Changes in version 0.2.2.3-alpha - 2009-09-23
5661 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
5664 - Fix an overzealous assert in our new circuit build timeout code.
5665 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
5668 - If the networkstatus consensus tells us that we should use a
5669 negative circuit package window, ignore it. Otherwise we'll
5670 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
5673 Changes in version 0.2.2.2-alpha - 2009-09-21
5674 Tor 0.2.2.2-alpha introduces our latest performance improvement for
5675 clients: Tor tracks the average time it takes to build a circuit, and
5676 avoids using circuits that take too long to build. For fast connections,
5677 this feature can cut your expected latency in half. For slow or flaky
5678 connections, it could ruin your Tor experience. Let us know if it does!
5681 - Tor now tracks how long it takes to build client-side circuits
5682 over time, and adapts its timeout to local network performance.
5683 Since a circuit that takes a long time to build will also provide
5684 bad performance, we get significant latency improvements by
5685 discarding the slowest 20% of circuits. Specifically, Tor creates
5686 circuits more aggressively than usual until it has enough data
5687 points for a good timeout estimate. Implements proposal 151.
5688 We are especially looking for reports (good and bad) from users with
5689 both EDGE and broadband connections that can move from broadband
5690 to EDGE and find out if the build-time data in the .tor/state gets
5691 reset without loss of Tor usability. You should also see a notice
5692 log message telling you that Tor has reset its timeout.
5693 - Directory authorities can now vote on arbitary integer values as
5694 part of the consensus process. This is designed to help set
5695 network-wide parameters. Implements proposal 167.
5696 - Tor now reads the "circwindow" parameter out of the consensus,
5697 and uses that value for its circuit package window rather than the
5698 default of 1000 cells. Begins the implementation of proposal 168.
5701 - Fix a remotely triggerable memory leak when a consensus document
5702 contains more than one signature from the same voter. Bugfix on
5706 - Fix an extremely rare infinite recursion bug that could occur if
5707 we tried to log a message after shutting down the log subsystem.
5708 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5709 - Fix parsing for memory or time units given without a space between
5710 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
5711 - A networkstatus vote must contain exactly one signature. Spec
5712 conformance issue. Bugfix on 0.2.0.3-alpha.
5713 - Fix an obscure bug where hidden services on 64-bit big-endian
5714 systems might mis-read the timestamp in v3 introduce cells, and
5715 refuse to connect back to the client. Discovered by "rotor".
5716 Bugfix on 0.2.1.6-alpha.
5717 - We were triggering a CLOCK_SKEW controller status event whenever
5718 we connect via the v2 connection protocol to any relay that has
5719 a wrong clock. Instead, we should only inform the controller when
5720 it's a trusted authority that claims our clock is wrong. Bugfix
5721 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5722 - We were telling the controller about CHECKING_REACHABILITY and
5723 REACHABILITY_FAILED status events whenever we launch a testing
5724 circuit or notice that one has failed. Instead, only tell the
5725 controller when we want to inform the user of overall success or
5726 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5728 - Don't warn when we're using a circuit that ends with a node
5729 excluded in ExcludeExitNodes, but the circuit is not used to access
5730 the outside world. This should help fix bug 1090, but more problems
5731 remain. Bugfix on 0.2.1.6-alpha.
5732 - Work around a small memory leak in some versions of OpenSSL that
5733 stopped the memory used by the hostname TLS extension from being
5735 - Make our 'torify' script more portable; if we have only one of
5736 'torsocks' or 'tsocks' installed, don't complain to the user;
5737 and explain our warning about tsocks better.
5740 - Add a "getinfo status/accepted-server-descriptor" controller
5741 command, which is the recommended way for controllers to learn
5742 whether our server descriptor has been successfully received by at
5743 least on directory authority. Un-recommend good-server-descriptor
5744 getinfo and status events until we have a better design for them.
5745 - Update to the "September 4 2009" ip-to-country file.
5748 Changes in version 0.2.2.1-alpha - 2009-08-26
5749 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
5750 Tor clients to bootstrap on networks where only port 80 is reachable,
5751 makes it more straightforward to support hardware crypto accelerators,
5752 and starts the groundwork for gathering stats safely at relays.
5755 - Start the process of disabling ".exit" address notation, since it
5756 can be used for a variety of esoteric application-level attacks
5757 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
5760 o New directory authorities:
5761 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5765 - New AccelName and AccelDir options add support for dynamic OpenSSL
5766 hardware crypto acceleration engines.
5767 - Tor now supports tunneling all of its outgoing connections over
5768 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
5769 configuration options. Code by Christopher Davis.
5772 - Send circuit or stream sendme cells when our window has decreased
5773 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5774 by Karsten when testing the "reduce circuit window" performance
5775 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5776 before the release of Tor 0.0.0. This is the new winner of the
5779 o New options for gathering stats safely:
5780 - Directory mirrors that set "DirReqStatistics 1" write statistics
5781 about directory requests to disk every 24 hours. As compared to the
5782 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
5783 1) stats are written to disk exactly every 24 hours; 2) estimated
5784 shares of v2 and v3 requests are determined as mean values, not at
5785 the end of a measurement period; 3) unresolved requests are listed
5786 with country code '??'; 4) directories also measure download times.
5787 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
5788 number of exit streams and transferred bytes per port to disk every
5790 - Relays that set "CellStatistics 1" write statistics on how long
5791 cells spend in their circuit queues to disk every 24 hours.
5792 - Entry nodes that set "EntryStatistics 1" write statistics on the
5793 rough number and origins of connecting clients to disk every 24
5795 - Relays that write any of the above statistics to disk and set
5796 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
5797 their extra-info documents.
5800 - New --digests command-line switch to output the digests of the
5801 source files Tor was built with.
5802 - The "torify" script now uses torsocks where available.
5803 - The memarea code now uses a sentinel value at the end of each area
5804 to make sure nothing writes beyond the end of an area. This might
5805 help debug some conceivable causes of bug 930.
5806 - Time and memory units in the configuration file can now be set to
5807 fractional units. For example, "2.5 GB" is now a valid value for
5809 - Certain Tor clients (such as those behind check.torproject.org) may
5810 want to fetch the consensus in an extra early manner. To enable this
5811 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
5812 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
5813 as only certain clients who must have this information sooner should
5815 - Instead of adding the svn revision to the Tor version string, report
5816 the git commit (when we're building from a git checkout).
5819 - If any of the v3 certs we download are unparseable, we should
5820 actually notice the failure so we don't retry indefinitely. Bugfix
5821 on 0.2.0.x; reported by "rotator".
5822 - If the cached cert file is unparseable, warn but don't exit.
5823 - Fix possible segmentation fault on directory authorities. Bugfix on
5825 - When Tor fails to parse a descriptor of any kind, dump it to disk.
5826 Might help diagnosing bug 1051.
5828 o Deprecated and removed features:
5829 - The controller no longer accepts the old obsolete "addr-mappings/"
5830 or "unregistered-servers-" GETINFO values.
5831 - Hidden services no longer publish version 0 descriptors, and clients
5832 do not request or use version 0 descriptors. However, the old hidden
5833 service authorities still accept and serve version 0 descriptors
5834 when contacted by older hidden services/clients.
5835 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
5836 always on; using them is necessary for correct forward-compatible
5838 - Remove support for .noconnect style addresses. Nobody was using
5839 them, and they provided another avenue for detecting Tor users
5840 via application-level web tricks.
5842 o Packaging changes:
5843 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
5844 installer bundles. See
5845 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
5846 for details of what's new in Vidalia 0.2.3.
5847 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
5848 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
5849 configuration file, rather than the old Privoxy.
5850 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
5851 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
5852 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
5853 better compatibility with OS X 10.6, aka Snow Leopard.
5854 - OS X Vidalia Bundle: The multi-package installer is now replaced
5855 by a simple drag and drop to the /Applications folder. This change
5856 occurred with the upgrade to Vidalia 0.2.3.
5859 Changes in version 0.2.1.19 - 2009-07-28
5860 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
5861 services on Tor 0.2.1.3-alpha through 0.2.1.18.
5864 - Make accessing hidden services on 0.2.1.x work right again.
5865 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
5866 part of patch provided by "optimist".
5869 - When a relay/bridge is writing out its identity key fingerprint to
5870 the "fingerprint" file and to its logs, write it without spaces. Now
5871 it will look like the fingerprints in our bridges documentation,
5872 and confuse fewer users.
5875 - Relays no longer publish a new server descriptor if they change
5876 their MaxAdvertisedBandwidth config option but it doesn't end up
5877 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
5878 fixes bug 1026. Patch from Sebastian.
5879 - Avoid leaking memory every time we get a create cell but we have
5880 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
5881 fixes bug 1034. Reported by BarkerJr.
5884 Changes in version 0.2.1.18 - 2009-07-24
5885 Tor 0.2.1.18 lays the foundations for performance improvements,
5886 adds status events to help users diagnose bootstrap problems, adds
5887 optional authentication/authorization for hidden services, fixes a
5888 variety of potential anonymity problems, and includes a huge pile of
5889 other features and bug fixes.
5892 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
5895 Changes in version 0.2.1.17-rc - 2009-07-07
5896 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
5897 candidate for the 0.2.1.x series. It lays the groundwork for further
5898 client performance improvements, and also fixes a big bug with directory
5899 authorities that were causing them to assign Guard and Stable flags
5902 The Windows bundles also finally include the geoip database that we
5903 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
5904 should actually install Torbutton rather than giving you a cryptic
5905 failure message (oops).
5908 - Clients now use the bandwidth values in the consensus, rather than
5909 the bandwidth values in each relay descriptor. This approach opens
5910 the door to more accurate bandwidth estimates once the directory
5911 authorities start doing active measurements. Implements more of
5915 - When Tor clients restart after 1-5 days, they discard all their
5916 cached descriptors as too old, but they still use the cached
5917 consensus document. This approach is good for robustness, but
5918 bad for performance: since they don't know any bandwidths, they
5919 end up choosing at random rather than weighting their choice by
5920 speed. Fixed by the above feature of putting bandwidths in the
5921 consensus. Bugfix on 0.2.0.x.
5922 - Directory authorities were neglecting to mark relays down in their
5923 internal histories if the relays fall off the routerlist without
5924 ever being found unreachable. So there were relays in the histories
5925 that haven't been seen for eight months, and are listed as being
5926 up for eight months. This wreaked havoc on the "median wfu"
5927 and "median mtbf" calculations, in turn making Guard and Stable
5928 flags very wrong, hurting network performance. Fixes bugs 696 and
5929 969. Bugfix on 0.2.0.6-alpha.
5932 - Serve the DirPortFrontPage page even when we have been approaching
5933 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
5934 - The control port would close the connection before flushing long
5935 replies, such as the network consensus, if a QUIT command was issued
5936 before the reply had completed. Now, the control port flushes all
5937 pending replies before closing the connection. Also fixed a spurious
5938 warning when a QUIT command is issued after a malformed or rejected
5939 AUTHENTICATE command, but before the connection was closed. Patch
5940 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
5941 - When we can't find an intro key for a v2 hidden service descriptor,
5942 fall back to the v0 hidden service descriptor and log a bug message.
5943 Workaround for bug 1024.
5944 - Fix a log message that did not respect the SafeLogging option.
5948 - If we're a relay and we change our IP address, be more verbose
5949 about the reason that made us change. Should help track down
5950 further bugs for relays on dynamic IP addresses.
5953 Changes in version 0.2.0.35 - 2009-06-24
5955 - Avoid crashing in the presence of certain malformed descriptors.
5956 Found by lark, and by automated fuzzing.
5957 - Fix an edge case where a malicious exit relay could convince a
5958 controller that the client's DNS question resolves to an internal IP
5959 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5962 - Finally fix the bug where dynamic-IP relays disappear when their
5963 IP address changes: directory mirrors were mistakenly telling
5964 them their old address if they asked via begin_dir, so they
5965 never got an accurate answer about their new address, so they
5966 just vanished after a day. For belt-and-suspenders, relays that
5967 don't set Address in their config now avoid using begin_dir for
5968 all direct connections. Should fix bugs 827, 883, and 900.
5969 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5970 that would occur on some exit nodes when DNS failures and timeouts
5971 occurred in certain patterns. Fix for bug 957.
5974 - When starting with a cache over a few days old, do not leak
5975 memory for the obsolete router descriptors in it. Bugfix on
5976 0.2.0.33; fixes bug 672.
5977 - Hidden service clients didn't use a cached service descriptor that
5978 was older than 15 minutes, but wouldn't fetch a new one either,
5979 because there was already one in the cache. Now, fetch a v2
5980 descriptor unless the same descriptor was added to the cache within
5981 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5984 Changes in version 0.2.1.16-rc - 2009-06-20
5985 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
5986 a bunch of minor bugs.
5989 - Fix an edge case where a malicious exit relay could convince a
5990 controller that the client's DNS question resolves to an internal IP
5991 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5993 o Major performance improvements (on 0.2.0.x):
5994 - Disable and refactor some debugging checks that forced a linear scan
5995 over the whole server-side DNS cache. These accounted for over 50%
5996 of CPU time on a relatively busy exit node's gprof profile. Found
5998 - Disable some debugging checks that appeared in exit node profile
6002 - Update to the "June 3 2009" ip-to-country file.
6003 - Do not have tor-resolve automatically refuse all .onion addresses;
6004 if AutomapHostsOnResolve is set in your torrc, this will work fine.
6006 o Minor bugfixes (on 0.2.0.x):
6007 - Log correct error messages for DNS-related network errors on
6009 - Fix a race condition that could cause crashes or memory corruption
6010 when running as a server with a controller listening for log
6012 - Avoid crashing when we have a policy specified in a DirPolicy or
6013 SocksPolicy or ReachableAddresses option with ports set on it,
6014 and we re-load the policy. May fix bug 996.
6015 - Hidden service clients didn't use a cached service descriptor that
6016 was older than 15 minutes, but wouldn't fetch a new one either,
6017 because there was already one in the cache. Now, fetch a v2
6018 descriptor unless the same descriptor was added to the cache within
6019 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
6021 o Minor bugfixes (on 0.2.1.x):
6022 - Don't warn users about low port and hibernation mix when they
6023 provide a *ListenAddress directive to fix that. Bugfix on
6025 - When switching back and forth between bridge mode, do not start
6026 gathering GeoIP data until two hours have passed.
6027 - Do not complain that the user has requested an excluded node as
6028 an exit when the node is not really an exit. This could happen
6029 because the circuit was for testing, or an introduction point.
6033 Changes in version 0.2.1.15-rc - 2009-05-25
6034 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
6035 series. It fixes a major bug on fast exit relays, as well as a variety
6038 o Major bugfixes (on 0.2.0.x):
6039 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
6040 that would occur on some exit nodes when DNS failures and timeouts
6041 occurred in certain patterns. Fix for bug 957.
6043 o Minor bugfixes (on 0.2.0.x):
6044 - Actually return -1 in the error case for read_bandwidth_usage().
6045 Harmless bug, since we currently don't care about the return value
6046 anywhere. Bugfix on 0.2.0.9-alpha.
6047 - Provide a more useful log message if bug 977 (related to buffer
6048 freelists) ever reappears, and do not crash right away.
6049 - Fix an assertion failure on 64-bit platforms when we allocated
6050 memory right up to the end of a memarea, then realigned the memory
6051 one step beyond the end. Fixes a possible cause of bug 930.
6052 - Protect the count of open sockets with a mutex, so we can't
6053 corrupt it when two threads are closing or opening sockets at once.
6054 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
6055 - Don't allow a bridge to publish its router descriptor to a
6056 non-bridge directory authority. Fixes part of bug 932.
6057 - When we change to or from being a bridge, reset our counts of
6058 client usage by country. Fixes bug 932.
6059 - Fix a bug that made stream bandwidth get misreported to the
6061 - Stop using malloc_usable_size() to use more area than we had
6062 actually allocated: it was safe, but made valgrind really unhappy.
6063 - Fix a memory leak when v3 directory authorities load their keys
6064 and cert from disk. Bugfix on 0.2.0.1-alpha.
6066 o Minor bugfixes (on 0.2.1.x):
6067 - Fix use of freed memory when deciding to mark a non-addable
6068 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
6071 Changes in version 0.2.1.14-rc - 2009-04-12
6072 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
6073 series. It begins fixing some major performance problems, and also
6074 finally addresses the bug that was causing relays on dynamic IP
6075 addresses to fall out of the directory.
6078 - Clients replace entry guards that were chosen more than a few months
6079 ago. This change should significantly improve client performance,
6080 especially once more people upgrade, since relays that have been
6081 a guard for a long time are currently overloaded.
6083 o Major bugfixes (on 0.2.0):
6084 - Finally fix the bug where dynamic-IP relays disappear when their
6085 IP address changes: directory mirrors were mistakenly telling
6086 them their old address if they asked via begin_dir, so they
6087 never got an accurate answer about their new address, so they
6088 just vanished after a day. For belt-and-suspenders, relays that
6089 don't set Address in their config now avoid using begin_dir for
6090 all direct connections. Should fix bugs 827, 883, and 900.
6091 - Relays were falling out of the networkstatus consensus for
6092 part of a day if they changed their local config but the
6093 authorities discarded their new descriptor as "not sufficiently
6094 different". Now directory authorities accept a descriptor as changed
6095 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
6097 - Avoid crashing in the presence of certain malformed descriptors.
6098 Found by lark, and by automated fuzzing.
6101 - When generating circuit events with verbose nicknames for
6102 controllers, try harder to look up nicknames for routers on a
6103 circuit. (Previously, we would look in the router descriptors we had
6104 for nicknames, but not in the consensus.) Partial fix for bug 941.
6105 - If the bridge config line doesn't specify a port, assume 443.
6106 This makes bridge lines a bit smaller and easier for users to
6108 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
6109 bytes (aka 20KB/s), to match our documentation. Also update
6110 directory authorities so they always assign the Fast flag to relays
6111 with 20KB/s of capacity. Now people running relays won't suddenly
6112 find themselves not seeing any use, if the network gets faster
6114 - Update to the "April 3 2009" ip-to-country file.
6117 - Avoid trying to print raw memory to the logs when we decide to
6118 give up on downloading a given relay descriptor. Bugfix on
6120 - In tor-resolve, when the Tor client to use is specified by
6121 <hostname>:<port>, actually use the specified port rather than
6122 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
6123 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
6124 - When starting with a cache over a few days old, do not leak
6125 memory for the obsolete router descriptors in it. Bugfix on
6127 - Avoid double-free on list of successfully uploaded hidden
6128 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
6129 - Change memarea_strndup() implementation to work even when
6130 duplicating a string at the end of a page. This bug was
6131 harmless for now, but could have meant crashes later. Fix by
6132 lark. Bugfix on 0.2.1.1-alpha.
6133 - Limit uploaded directory documents to be 16M rather than 500K.
6134 The directory authorities were refusing v3 consensus votes from
6135 other authorities, since the votes are now 504K. Fixes bug 959;
6136 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
6137 - Directory authorities should never send a 503 "busy" response to
6138 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
6142 Changes in version 0.2.1.13-alpha - 2009-03-09
6143 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
6144 cleanups. We're finally getting close to a release candidate.
6147 - Correctly update the list of which countries we exclude as
6148 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
6149 lark. Bugfix on 0.2.1.6-alpha.
6151 o Minor bugfixes (on 0.2.0.x and earlier):
6152 - Automatically detect MacOSX versions earlier than 10.4.0, and
6153 disable kqueue from inside Tor when running with these versions.
6154 We previously did this from the startup script, but that was no
6155 help to people who didn't use the startup script. Resolves bug 863.
6156 - When we had picked an exit node for a connection, but marked it as
6157 "optional", and it turned out we had no onion key for the exit,
6158 stop wanting that exit and try again. This situation may not
6159 be possible now, but will probably become feasible with proposal
6160 158. Spotted by rovv. Fixes another case of bug 752.
6161 - Clients no longer cache certificates for authorities they do not
6162 recognize. Bugfix on 0.2.0.9-alpha.
6163 - When we can't transmit a DNS request due to a network error, retry
6164 it after a while, and eventually transmit a failing response to
6165 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
6166 - If the controller claimed responsibility for a stream, but that
6167 stream never finished making its connection, it would live
6168 forever in circuit_wait state. Now we close it after SocksTimeout
6169 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
6170 - Drop begin cells to a hidden service if they come from the middle
6171 of a circuit. Patch from lark.
6172 - When we erroneously receive two EXTEND cells for the same circuit
6173 ID on the same connection, drop the second. Patch from lark.
6174 - Fix a crash that occurs on exit nodes when a nameserver request
6175 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
6176 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
6178 - Do not assume that a stack-allocated character array will be
6179 64-bit aligned on platforms that demand that uint64_t access is
6180 aligned. Possible fix for bug 604.
6181 - Parse dates and IPv4 addresses in a locale- and libc-independent
6182 manner, to avoid platform-dependent behavior on malformed input.
6183 - Build correctly when configured to build outside the main source
6184 path. Patch from Michael Gold.
6185 - We were already rejecting relay begin cells with destination port
6186 of 0. Now also reject extend cells with destination port or address
6187 of 0. Suggested by lark.
6189 o Minor bugfixes (on 0.2.1.x):
6190 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
6191 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
6192 - If we're an exit node, scrub the IP address to which we are exiting
6193 in the logs. Bugfix on 0.2.1.8-alpha.
6196 - On Linux, use the prctl call to re-enable core dumps when the user
6198 - New controller event NEWCONSENSUS that lists the networkstatus
6199 lines for every recommended relay. Now controllers like Torflow
6200 can keep up-to-date on which relays they should be using.
6201 - Update to the "February 26 2009" ip-to-country file.
6204 Changes in version 0.2.0.34 - 2009-02-08
6205 Tor 0.2.0.34 features several more security-related fixes. You should
6206 upgrade, especially if you run an exit relay (remote crash) or a
6207 directory authority (remote infinite loop), or you're on an older
6208 (pre-XP) or not-recently-patched Windows (remote exploit).
6210 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
6211 have many known flaws, and nobody should be using them. You should
6212 upgrade. If you're using a Linux or BSD and its packages are obsolete,
6213 stop using those packages and upgrade anyway.
6216 - Fix an infinite-loop bug on handling corrupt votes under certain
6217 circumstances. Bugfix on 0.2.0.8-alpha.
6218 - Fix a temporary DoS vulnerability that could be performed by
6219 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
6220 - Avoid a potential crash on exit nodes when processing malformed
6221 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
6222 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
6223 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
6226 - Fix compilation on systems where time_t is a 64-bit integer.
6227 Patch from Matthias Drochner.
6228 - Don't consider expiring already-closed client connections. Fixes
6229 bug 893. Bugfix on 0.0.2pre20.
6232 Changes in version 0.2.1.12-alpha - 2009-02-08
6233 Tor 0.2.1.12-alpha features several more security-related fixes. You
6234 should upgrade, especially if you run an exit relay (remote crash) or
6235 a directory authority (remote infinite loop), or you're on an older
6236 (pre-XP) or not-recently-patched Windows (remote exploit). It also
6237 includes a big pile of minor bugfixes and cleanups.
6240 - Fix an infinite-loop bug on handling corrupt votes under certain
6241 circumstances. Bugfix on 0.2.0.8-alpha.
6242 - Fix a temporary DoS vulnerability that could be performed by
6243 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
6244 - Avoid a potential crash on exit nodes when processing malformed
6245 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
6248 - Let controllers actually ask for the "clients_seen" event for
6249 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
6250 reported by Matt Edman.
6251 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
6253 - Fix a bug in address parsing that was preventing bridges or hidden
6254 service targets from being at IPv6 addresses.
6255 - Solve a bug that kept hardware crypto acceleration from getting
6256 enabled when accounting was turned on. Fixes bug 907. Bugfix on
6258 - Remove a bash-ism from configure.in to build properly on non-Linux
6259 platforms. Bugfix on 0.2.1.1-alpha.
6260 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
6261 headers. Bugfix on 0.2.0.10-alpha.
6262 - Don't consider expiring already-closed client connections. Fixes
6263 bug 893. Bugfix on 0.0.2pre20.
6264 - Fix another interesting corner-case of bug 891 spotted by rovv:
6265 Previously, if two hosts had different amounts of clock drift, and
6266 one of them created a new connection with just the wrong timing,
6267 the other might decide to deprecate the new connection erroneously.
6268 Bugfix on 0.1.1.13-alpha.
6269 - Resolve a very rare crash bug that could occur when the user forced
6270 a nameserver reconfiguration during the middle of a nameserver
6271 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
6272 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
6273 Bugfix on 0.2.1.7-alpha.
6274 - If we're using bridges and our network goes away, be more willing
6275 to forgive our bridges and try again when we get an application
6276 request. Bugfix on 0.2.0.x.
6279 - Support platforms where time_t is 64 bits long. (Congratulations,
6280 NetBSD!) Patch from Matthias Drochner.
6281 - Add a 'getinfo status/clients-seen' controller command, in case
6282 controllers want to hear clients_seen events but connect late.
6285 - Disable GCC's strict alias optimization by default, to avoid the
6286 likelihood of its introducing subtle bugs whenever our code violates
6287 the letter of C99's alias rules.
6290 Changes in version 0.2.0.33 - 2009-01-21
6291 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
6292 useful to users. It also finally fixes a bug where a relay or client
6293 that's been off for many days would take a long time to bootstrap.
6295 This update also fixes an important security-related bug reported by
6296 Ilja van Sprundel. You should upgrade. (We'll send out more details
6297 about the bug once people have had some time to upgrade.)
6300 - Fix a heap-corruption bug that may be remotely triggerable on
6301 some platforms. Reported by Ilja van Sprundel.
6304 - When a stream at an exit relay is in state "resolving" or
6305 "connecting" and it receives an "end" relay cell, the exit relay
6306 would silently ignore the end cell and not close the stream. If
6307 the client never closes the circuit, then the exit relay never
6308 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
6310 - When sending CREATED cells back for a given circuit, use a 64-bit
6311 connection ID to find the right connection, rather than an addr:port
6312 combination. Now that we can have multiple OR connections between
6313 the same ORs, it is no longer possible to use addr:port to uniquely
6314 identify a connection.
6315 - Bridge relays that had DirPort set to 0 would stop fetching
6316 descriptors shortly after startup, and then briefly resume
6317 after a new bandwidth test and/or after publishing a new bridge
6318 descriptor. Bridge users that try to bootstrap from them would
6319 get a recent networkstatus but would get descriptors from up to
6320 18 hours earlier, meaning most of the descriptors were obsolete
6321 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
6322 - Prevent bridge relays from serving their 'extrainfo' document
6323 to anybody who asks, now that extrainfo docs include potentially
6324 sensitive aggregated client geoip summaries. Bugfix on
6326 - If the cached networkstatus consensus is more than five days old,
6327 discard it rather than trying to use it. In theory it could be
6328 useful because it lists alternate directory mirrors, but in practice
6329 it just means we spend many minutes trying directory mirrors that
6330 are long gone from the network. Also discard router descriptors as
6331 we load them if they are more than five days old, since the onion
6332 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
6335 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6336 could make gcc generate non-functional binary search code. Bugfix
6338 - Build correctly on platforms without socklen_t.
6339 - Compile without warnings on solaris.
6340 - Avoid potential crash on internal error during signature collection.
6341 Fixes bug 864. Patch from rovv.
6342 - Correct handling of possible malformed authority signing key
6343 certificates with internal signature types. Fixes bug 880.
6344 Bugfix on 0.2.0.3-alpha.
6345 - Fix a hard-to-trigger resource leak when logging credential status.
6347 - When we can't initialize DNS because the network is down, do not
6348 automatically stop Tor from starting. Instead, we retry failed
6349 dns_init() every 10 minutes, and change the exit policy to reject
6350 *:* until one succeeds. Fixes bug 691.
6351 - Use 64 bits instead of 32 bits for connection identifiers used with
6352 the controller protocol, to greatly reduce risk of identifier reuse.
6353 - When we're choosing an exit node for a circuit, and we have
6354 no pending streams, choose a good general exit rather than one that
6355 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
6356 - Fix another case of assuming, when a specific exit is requested,
6357 that we know more than the user about what hosts it allows.
6358 Fixes one case of bug 752. Patch from rovv.
6359 - Clip the MaxCircuitDirtiness config option to a minimum of 10
6360 seconds. Warn the user if lower values are given in the
6361 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
6362 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
6363 user if lower values are given in the configuration. Bugfix on
6364 0.1.1.17-rc. Patch by Sebastian.
6365 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
6366 the cache because we already had a v0 descriptor with the same ID.
6367 Bugfix on 0.2.0.18-alpha.
6368 - Fix a race condition when freeing keys shared between main thread
6369 and CPU workers that could result in a memory leak. Bugfix on
6370 0.1.0.1-rc. Fixes bug 889.
6371 - Send a valid END cell back when a client tries to connect to a
6372 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
6373 840. Patch from rovv.
6374 - Check which hops rendezvous stream cells are associated with to
6375 prevent possible guess-the-streamid injection attacks from
6376 intermediate hops. Fixes another case of bug 446. Based on patch
6378 - If a broken client asks a non-exit router to connect somewhere,
6379 do not even do the DNS lookup before rejecting the connection.
6380 Fixes another case of bug 619. Patch from rovv.
6381 - When a relay gets a create cell it can't decrypt (e.g. because it's
6382 using the wrong onion key), we were dropping it and letting the
6383 client time out. Now actually answer with a destroy cell. Fixes
6384 bug 904. Bugfix on 0.0.2pre8.
6386 o Minor bugfixes (hidden services):
6387 - Do not throw away existing introduction points on SIGHUP. Bugfix on
6388 0.0.6pre1. Patch by Karsten. Fixes bug 874.
6391 - Report the case where all signatures in a detached set are rejected
6392 differently than the case where there is an error handling the
6394 - When we realize that another process has modified our cached
6395 descriptors, print out a more useful error message rather than
6396 triggering an assertion. Fixes bug 885. Patch from Karsten.
6397 - Implement the 0x20 hack to better resist DNS poisoning: set the
6398 case on outgoing DNS requests randomly, and reject responses that do
6399 not match the case correctly. This logic can be disabled with the
6400 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
6401 of servers that do not reliably preserve case in replies. See
6402 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
6404 - Check DNS replies for more matching fields to better resist DNS
6406 - Never use OpenSSL compression: it wastes RAM and CPU trying to
6407 compress cells, which are basically all encrypted, compressed, or
6411 Changes in version 0.2.1.11-alpha - 2009-01-20
6412 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
6413 week it will take a long time to bootstrap again" bug. It also fixes
6414 an important security-related bug reported by Ilja van Sprundel. You
6415 should upgrade. (We'll send out more details about the bug once people
6416 have had some time to upgrade.)
6419 - Fix a heap-corruption bug that may be remotely triggerable on
6420 some platforms. Reported by Ilja van Sprundel.
6423 - Discard router descriptors as we load them if they are more than
6424 five days old. Otherwise if Tor is off for a long time and then
6425 starts with cached descriptors, it will try to use the onion
6426 keys in those obsolete descriptors when building circuits. Bugfix
6427 on 0.2.0.x. Fixes bug 887.
6430 - Try to make sure that the version of Libevent we're running with
6431 is binary-compatible with the one we built with. May address bug
6433 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
6434 for bug 905. Bugfix on 0.2.1.7-alpha.
6435 - Add a new --enable-local-appdata configuration switch to change
6436 the default location of the datadir on win32 from APPDATA to
6437 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
6438 entirely. Patch from coderman.
6441 - Make outbound DNS packets respect the OutboundBindAddress setting.
6442 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
6443 - When our circuit fails at the first hop (e.g. we get a destroy
6444 cell back), avoid using that OR connection anymore, and also
6445 tell all the one-hop directory requests waiting for it that they
6446 should fail. Bugfix on 0.2.1.3-alpha.
6447 - In the torify(1) manpage, mention that tsocks will leak your
6451 Changes in version 0.2.1.10-alpha - 2009-01-06
6452 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
6453 would make the bridge relay not so useful if it had DirPort set to 0,
6454 and one that could let an attacker learn a little bit of information
6455 about the bridge's users), and a bug that would cause your Tor relay
6456 to ignore a circuit create request it can't decrypt (rather than reply
6457 with an error). It also fixes a wide variety of other bugs.
6460 - If the cached networkstatus consensus is more than five days old,
6461 discard it rather than trying to use it. In theory it could
6462 be useful because it lists alternate directory mirrors, but in
6463 practice it just means we spend many minutes trying directory
6464 mirrors that are long gone from the network. Helps bug 887 a bit;
6466 - Bridge relays that had DirPort set to 0 would stop fetching
6467 descriptors shortly after startup, and then briefly resume
6468 after a new bandwidth test and/or after publishing a new bridge
6469 descriptor. Bridge users that try to bootstrap from them would
6470 get a recent networkstatus but would get descriptors from up to
6471 18 hours earlier, meaning most of the descriptors were obsolete
6472 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
6473 - Prevent bridge relays from serving their 'extrainfo' document
6474 to anybody who asks, now that extrainfo docs include potentially
6475 sensitive aggregated client geoip summaries. Bugfix on
6479 - New controller event "clients_seen" to report a geoip-based summary
6480 of which countries we've seen clients from recently. Now controllers
6481 like Vidalia can show bridge operators that they're actually making
6483 - Build correctly against versions of OpenSSL 0.9.8 or later built
6484 without support for deprecated functions.
6485 - Update to the "December 19 2008" ip-to-country file.
6487 o Minor bugfixes (on 0.2.0.x):
6488 - Authorities now vote for the Stable flag for any router whose
6489 weighted MTBF is at least 5 days, regardless of the mean MTBF.
6490 - Do not remove routers as too old if we do not have any consensus
6491 document. Bugfix on 0.2.0.7-alpha.
6492 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
6493 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
6494 - When an exit relay resolves a stream address to a local IP address,
6495 do not just keep retrying that same exit relay over and
6496 over. Instead, just close the stream. Addresses bug 872. Bugfix
6497 on 0.2.0.32. Patch from rovv.
6498 - If a hidden service sends us an END cell, do not consider
6499 retrying the connection; just close it. Patch from rovv.
6500 - When we made bridge authorities stop serving bridge descriptors over
6501 unencrypted links, we also broke DirPort reachability testing for
6502 bridges. So bridges with a non-zero DirPort were printing spurious
6503 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
6504 - When a relay gets a create cell it can't decrypt (e.g. because it's
6505 using the wrong onion key), we were dropping it and letting the
6506 client time out. Now actually answer with a destroy cell. Fixes
6507 bug 904. Bugfix on 0.0.2pre8.
6508 - Squeeze 2-5% out of client performance (according to oprofile) by
6509 improving the implementation of some policy-manipulation functions.
6511 o Minor bugfixes (on 0.2.1.x):
6512 - Make get_interface_address() function work properly again; stop
6513 guessing the wrong parts of our address as our address.
6514 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
6515 send on that circuit. Otherwise we might violate the proposal-110
6516 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
6518 - When we're sending non-EXTEND cells to the first hop in a circuit,
6519 for example to use an encrypted directory connection, we don't need
6520 to use RELAY_EARLY cells: the first hop knows what kind of cell
6521 it is, and nobody else can even see the cell type. Conserving
6522 RELAY_EARLY cells makes it easier to cannibalize circuits like
6524 - Stop logging nameserver addresses in reverse order.
6525 - If we are retrying a directory download slowly over and over, do
6526 not automatically give up after the 254th failure. Bugfix on
6528 - Resume reporting accurate "stream end" reasons to the local control
6529 port. They were lost in the changes for Proposal 148. Bugfix on
6532 o Deprecated and removed features:
6533 - The old "tor --version --version" command, which would print out
6534 the subversion "Id" of most of the source files, is now removed. It
6535 turned out to be less useful than we'd expected, and harder to
6538 o Code simplifications and refactoring:
6539 - Change our header file guard macros to be less likely to conflict
6540 with system headers. Adam Langley noticed that we were conflicting
6541 with log.h on Android.
6542 - Tool-assisted documentation cleanup. Nearly every function or
6543 static variable in Tor should have its own documentation now.
6546 Changes in version 0.2.1.9-alpha - 2008-12-25
6547 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
6549 o New directory authorities:
6550 - gabelmoo (the authority run by Karsten Loesing) now has a new
6554 - Never use a connection with a mismatched address to extend a
6555 circuit, unless that connection is canonical. A canonical
6556 connection is one whose address is authenticated by the router's
6557 identity key, either in a NETINFO cell or in a router descriptor.
6558 - Avoid a possible memory corruption bug when receiving hidden service
6559 descriptors. Bugfix on 0.2.1.6-alpha.
6562 - Fix a logic error that would automatically reject all but the first
6563 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
6564 part of bug 813/868. Bug spotted by coderman.
6565 - When a stream at an exit relay is in state "resolving" or
6566 "connecting" and it receives an "end" relay cell, the exit relay
6567 would silently ignore the end cell and not close the stream. If
6568 the client never closes the circuit, then the exit relay never
6569 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
6571 - When we can't initialize DNS because the network is down, do not
6572 automatically stop Tor from starting. Instead, retry failed
6573 dns_init() every 10 minutes, and change the exit policy to reject
6574 *:* until one succeeds. Fixes bug 691.
6577 - Give a better error message when an overzealous init script says
6578 "sudo -u username tor --user username". Makes Bug 882 easier for
6580 - When a directory authority gives us a new guess for our IP address,
6581 log which authority we used. Hopefully this will help us debug
6582 the recent complaints about bad IP address guesses.
6583 - Detect svn revision properly when we're using git-svn.
6584 - Try not to open more than one descriptor-downloading connection
6585 to an authority at once. This should reduce load on directory
6586 authorities. Fixes bug 366.
6587 - Add cross-certification to newly generated certificates, so that
6588 a signing key is enough information to look up a certificate.
6589 Partial implementation of proposal 157.
6590 - Start serving certificates by <identity digest, signing key digest>
6591 pairs. Partial implementation of proposal 157.
6592 - Clients now never report any stream end reason except 'MISC'.
6593 Implements proposal 148.
6594 - On platforms with a maximum syslog string length, truncate syslog
6595 messages to that length ourselves, rather than relying on the
6596 system to do it for us.
6597 - Optimize out calls to time(NULL) that occur for every IO operation,
6598 or for every cell. On systems where time() is a slow syscall,
6599 this fix will be slightly helpful.
6600 - Exit servers can now answer resolve requests for ip6.arpa addresses.
6601 - When we download a descriptor that we then immediately (as
6602 a directory authority) reject, do not retry downloading it right
6603 away. Should save some bandwidth on authorities. Fix for bug
6604 888. Patch by Sebastian Hahn.
6605 - When a download gets us zero good descriptors, do not notify
6606 Tor that new directory information has arrived.
6607 - Avoid some nasty corner cases in the logic for marking connections
6608 as too old or obsolete or noncanonical for circuits. Partial
6611 o Minor features (controller):
6612 - New CONSENSUS_ARRIVED event to note when a new consensus has
6613 been fetched and validated.
6614 - When we realize that another process has modified our cached
6615 descriptors file, print out a more useful error message rather
6616 than triggering an assertion. Fixes bug 885. Patch from Karsten.
6617 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
6618 controllers to prevent SIGHUP from reloading the
6619 configuration. Fixes bug 856.
6622 - Resume using the correct "REASON=" stream when telling the
6623 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
6624 - When a canonical connection appears later in our internal list
6625 than a noncanonical one for a given OR ID, always use the
6626 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
6628 - Clip the MaxCircuitDirtiness config option to a minimum of 10
6629 seconds. Warn the user if lower values are given in the
6630 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
6631 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
6632 user if lower values are given in the configuration. Bugfix on
6633 0.1.1.17-rc. Patch by Sebastian.
6634 - Fix a race condition when freeing keys shared between main thread
6635 and CPU workers that could result in a memory leak. Bugfix on
6636 0.1.0.1-rc. Fixes bug 889.
6638 o Minor bugfixes (hidden services):
6639 - Do not throw away existing introduction points on SIGHUP (bugfix on
6640 0.0.6pre1); also, do not stall hidden services because we're
6641 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
6642 by John Brooks. Patch by Karsten. Fixes bug 874.
6643 - Fix a memory leak when we decline to add a v2 rendezvous
6644 descriptor to the cache because we already had a v0 descriptor
6645 with the same ID. Bugfix on 0.2.0.18-alpha.
6647 o Deprecated and removed features:
6648 - RedirectExits has been removed. It was deprecated since
6650 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
6651 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
6652 - Cell pools are now always enabled; --disable-cell-pools is ignored.
6654 o Code simplifications and refactoring:
6655 - Rename the confusing or_is_obsolete field to the more appropriate
6656 is_bad_for_new_circs, and move it to or_connection_t where it
6658 - Move edge-only flags from connection_t to edge_connection_t: not
6659 only is this better coding, but on machines of plausible alignment,
6660 it should save 4-8 bytes per connection_t. "Every little bit helps."
6661 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
6662 for consistency; keep old option working for backward compatibility.
6663 - Simplify the code for finding connections to use for a circuit.
6666 Changes in version 0.2.1.8-alpha - 2008-12-08
6667 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
6668 builds better on unusual platforms like Solaris and old OS X, and
6669 fixes a variety of other issues.
6672 - New DirPortFrontPage option that takes an html file and publishes
6673 it as "/" on the DirPort. Now relay operators can provide a
6674 disclaimer without needing to set up a separate webserver. There's
6675 a sample disclaimer in contrib/tor-exit-notice.html.
6678 - When the client is choosing entry guards, now it selects at most
6679 one guard from a given relay family. Otherwise we could end up with
6680 all of our entry points into the network run by the same operator.
6681 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
6684 - Fix a DOS opportunity during the voting signature collection process
6685 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6686 - Fix a possible segfault when establishing an exit connection. Bugfix
6690 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
6692 - Made Tor a little less aggressive about deleting expired
6693 certificates. Partial fix for bug 854.
6694 - Stop doing unaligned memory access that generated bus errors on
6695 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
6696 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
6697 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
6698 - Make USR2 log-level switch take effect immediately. Bugfix on
6700 - If one win32 nameserver fails to get added, continue adding the
6701 rest, and don't automatically fail.
6702 - Use fcntl() for locking when flock() is not available. Should fix
6703 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
6704 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6705 could make gcc generate non-functional binary search code. Bugfix
6707 - Build correctly on platforms without socklen_t.
6708 - Avoid potential crash on internal error during signature collection.
6709 Fixes bug 864. Patch from rovv.
6710 - Do not use C's stdio library for writing to log files. This will
6711 improve logging performance by a minute amount, and will stop
6712 leaking fds when our disk is full. Fixes bug 861.
6713 - Stop erroneous use of O_APPEND in cases where we did not in fact
6714 want to re-seek to the end of a file before every last write().
6715 - Correct handling of possible malformed authority signing key
6716 certificates with internal signature types. Fixes bug 880. Bugfix
6718 - Fix a hard-to-trigger resource leak when logging credential status.
6722 - Directory mirrors no longer fetch the v1 directory or
6723 running-routers files. They are obsolete, and nobody asks for them
6724 anymore. This is the first step to making v1 authorities obsolete.
6726 o Minor features (controller):
6727 - Return circuit purposes in response to GETINFO circuit-status. Fixes
6731 Changes in version 0.2.0.32 - 2008-11-20
6732 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
6733 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6734 a smaller security flaw that might allow an attacker to access local
6735 services, further improves hidden service performance, and fixes a
6736 variety of other issues.
6739 - The "User" and "Group" config options did not clear the
6740 supplementary group entries for the Tor process. The "User" option
6741 is now more robust, and we now set the groups to the specified
6742 user's primary group. The "Group" option is now ignored. For more
6743 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6744 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6745 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
6746 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6747 consistently obeyed: if an exit relay refuses a stream because its
6748 exit policy doesn't allow it, we would remember what IP address
6749 the relay said the destination address resolves to, even if it's
6750 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6753 - Fix a DOS opportunity during the voting signature collection process
6754 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6756 o Major bugfixes (hidden services):
6757 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6758 we were failing the whole hidden service request when the v0
6759 descriptor fetch fails, even if the v2 fetch is still pending and
6760 might succeed. Similarly, if the last v2 fetch fails, we were
6761 failing the whole hidden service request even if a v0 fetch is
6762 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6763 - When extending a circuit to a hidden service directory to upload a
6764 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6765 requests failed, because the router descriptor has not been
6766 downloaded yet. In these cases, do not attempt to upload the
6767 rendezvous descriptor, but wait until the router descriptor is
6768 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
6769 descriptor from a hidden service directory for which the router
6770 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
6774 - Fix several infrequent memory leaks spotted by Coverity.
6775 - When testing for libevent functions, set the LDFLAGS variable
6776 correctly. Found by Riastradh.
6777 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6778 bootstrapping with tunneled directory connections. Bugfix on
6779 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6780 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6781 and we know that server B rejects most-but-not all connections to
6782 port 80, we would previously reject the connection. Now, we assume
6783 the user knows what they were asking for. Fixes bug 752. Bugfix
6784 on 0.0.9rc5. Diagnosed by BarkerJr.
6785 - If we overrun our per-second write limits a little, count this as
6786 having used up our write allocation for the second, and choke
6787 outgoing directory writes. Previously, we had only counted this when
6788 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
6789 Bugfix on 0.2.0.x (??).
6790 - Remove the old v2 directory authority 'lefkada' from the default
6791 list. It has been gone for many months.
6792 - Stop doing unaligned memory access that generated bus errors on
6793 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
6794 - Make USR2 log-level switch take effect immediately. Bugfix on
6797 o Minor bugfixes (controller):
6798 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
6799 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
6802 Changes in version 0.2.1.7-alpha - 2008-11-08
6803 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
6804 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6805 a smaller security flaw that might allow an attacker to access local
6806 services, adds better defense against DNS poisoning attacks on exit
6807 relays, further improves hidden service performance, and fixes a
6808 variety of other issues.
6811 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6812 consistently obeyed: if an exit relay refuses a stream because its
6813 exit policy doesn't allow it, we would remember what IP address
6814 the relay said the destination address resolves to, even if it's
6815 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6816 - The "User" and "Group" config options did not clear the
6817 supplementary group entries for the Tor process. The "User" option
6818 is now more robust, and we now set the groups to the specified
6819 user's primary group. The "Group" option is now ignored. For more
6820 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6821 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6822 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
6823 - Do not use or believe expired v3 authority certificates. Patch
6824 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
6827 - Now NodeFamily and MyFamily config options allow spaces in
6828 identity fingerprints, so it's easier to paste them in.
6829 Suggested by Lucky Green.
6830 - Implement the 0x20 hack to better resist DNS poisoning: set the
6831 case on outgoing DNS requests randomly, and reject responses that do
6832 not match the case correctly. This logic can be disabled with the
6833 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
6834 of servers that do not reliably preserve case in replies. See
6835 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
6837 - Preserve case in replies to DNSPort requests in order to support
6838 the 0x20 hack for resisting DNS poisoning attacks.
6840 o Hidden service performance improvements:
6841 - When the client launches an introduction circuit, retry with a
6842 new circuit after 30 seconds rather than 60 seconds.
6843 - Launch a second client-side introduction circuit in parallel
6844 after a delay of 15 seconds (based on work by Christian Wilms).
6845 - Hidden services start out building five intro circuits rather
6846 than three, and when the first three finish they publish a service
6847 descriptor using those. Now we publish our service descriptor much
6848 faster after restart.
6851 - Minor fix in the warning messages when you're having problems
6852 bootstrapping; also, be more forgiving of bootstrap problems when
6853 we're still making incremental progress on a given bootstrap phase.
6854 - When we're choosing an exit node for a circuit, and we have
6855 no pending streams, choose a good general exit rather than one that
6856 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
6857 - Send a valid END cell back when a client tries to connect to a
6858 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
6859 840. Patch from rovv.
6860 - If a broken client asks a non-exit router to connect somewhere,
6861 do not even do the DNS lookup before rejecting the connection.
6862 Fixes another case of bug 619. Patch from rovv.
6863 - Fix another case of assuming, when a specific exit is requested,
6864 that we know more than the user about what hosts it allows.
6865 Fixes another case of bug 752. Patch from rovv.
6866 - Check which hops rendezvous stream cells are associated with to
6867 prevent possible guess-the-streamid injection attacks from
6868 intermediate hops. Fixes another case of bug 446. Based on patch
6870 - Avoid using a negative right-shift when comparing 32-bit
6871 addresses. Possible fix for bug 845 and bug 811.
6872 - Make the assert_circuit_ok() function work correctly on circuits that
6873 have already been marked for close.
6874 - Fix read-off-the-end-of-string error in unit tests when decoding
6875 introduction points.
6876 - Fix uninitialized size field for memory area allocation: may improve
6877 memory performance during directory parsing.
6878 - Treat duplicate certificate fetches as failures, so that we do
6879 not try to re-fetch an expired certificate over and over and over.
6880 - Do not say we're fetching a certificate when we'll in fact skip it
6881 because of a pending download.
6884 Changes in version 0.2.1.6-alpha - 2008-09-30
6885 Tor 0.2.1.6-alpha further improves performance and robustness of
6886 hidden services, starts work on supporting per-country relay selection,
6887 and fixes a variety of smaller issues.
6890 - Implement proposal 121: make it possible to build hidden services
6891 that only certain clients are allowed to connect to. This is
6892 enforced at several points, so that unauthorized clients are unable
6893 to send INTRODUCE cells to the service, or even (depending on the
6894 type of authentication) to learn introduction points. This feature
6895 raises the bar for certain kinds of active attacks against hidden
6896 services. Code by Karsten Loesing.
6897 - Relays now store and serve v2 hidden service descriptors by default,
6898 i.e., the new default value for HidServDirectoryV2 is 1. This is
6899 the last step in proposal 114, which aims to make hidden service
6900 lookups more reliable.
6901 - Start work to allow node restrictions to include country codes. The
6902 syntax to exclude nodes in a country with country code XX is
6903 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
6904 refinement to decide what config options should take priority if
6905 you ask to both use a particular node and exclude it.
6906 - Allow ExitNodes list to include IP ranges and country codes, just
6907 like the Exclude*Nodes lists. Patch from Robert Hogan.
6910 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
6911 Tor to fail to start if you had it configured to use a bridge
6912 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
6913 - When extending a circuit to a hidden service directory to upload a
6914 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6915 requests failed, because the router descriptor had not been
6916 downloaded yet. In these cases, we now wait until the router
6917 descriptor is downloaded, and then retry. Likewise, clients
6918 now skip over a hidden service directory if they don't yet have
6919 its router descriptor, rather than futilely requesting it and
6920 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
6922 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6923 we were failing the whole hidden service request when the v0
6924 descriptor fetch fails, even if the v2 fetch is still pending and
6925 might succeed. Similarly, if the last v2 fetch fails, we were
6926 failing the whole hidden service request even if a v0 fetch is
6927 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6928 - DNS replies need to have names matching their requests, but
6929 these names should be in the questions section, not necessarily
6930 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
6933 - Update to the "September 1 2008" ip-to-country file.
6934 - Allow ports 465 and 587 in the default exit policy again. We had
6935 rejected them in 0.1.0.15, because back in 2005 they were commonly
6936 misconfigured and ended up as spam targets. We hear they are better
6937 locked down these days.
6938 - Use a lockfile to make sure that two Tor processes are not
6939 simultaneously running with the same datadir.
6940 - Serve the latest v3 networkstatus consensus via the control
6941 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
6942 - Better logging about stability/reliability calculations on directory
6944 - Drop the requirement to have an open dir port for storing and
6945 serving v2 hidden service descriptors.
6946 - Directory authorities now serve a /tor/dbg-stability.txt URL to
6947 help debug WFU and MTBF calculations.
6948 - Implement most of Proposal 152: allow specialized servers to permit
6949 single-hop circuits, and clients to use those servers to build
6950 single-hop circuits when using a specialized controller. Patch
6951 from Josh Albrecht. Resolves feature request 768.
6952 - Add a -p option to tor-resolve for specifying the SOCKS port: some
6953 people find host:port too confusing.
6954 - Make TrackHostExit mappings expire a while after their last use, not
6955 after their creation. Patch from Robert Hogan.
6956 - Provide circuit purposes along with circuit events to the controller.
6959 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
6961 - Fixed some memory leaks -- some quite frequent, some almost
6962 impossible to trigger -- based on results from Coverity.
6963 - When testing for libevent functions, set the LDFLAGS variable
6964 correctly. Found by Riastradh.
6965 - Fix an assertion bug in parsing policy-related options; possible fix
6967 - Catch and report a few more bootstrapping failure cases when Tor
6968 fails to establish a TCP connection. Cleanup on 0.2.1.x.
6969 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6970 bootstrapping with tunneled directory connections. Bugfix on
6971 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6972 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6973 and we know that server B rejects most-but-not all connections to
6974 port 80, we would previously reject the connection. Now, we assume
6975 the user knows what they were asking for. Fixes bug 752. Bugfix
6976 on 0.0.9rc5. Diagnosed by BarkerJr.
6977 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
6978 service directories if they have no advertised dir port. Bugfix
6980 - If we overrun our per-second write limits a little, count this as
6981 having used up our write allocation for the second, and choke
6982 outgoing directory writes. Previously, we had only counted this when
6983 we had met our limits precisely. Fixes bug 824. Patch by rovv.
6984 Bugfix on 0.2.0.x (??).
6985 - Avoid a "0 divided by 0" calculation when calculating router uptime
6986 at directory authorities. Bugfix on 0.2.0.8-alpha.
6987 - Make DNS resolved controller events into "CLOSED", not
6988 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
6990 - Fix a bug where an unreachable relay would establish enough
6991 reachability testing circuits to do a bandwidth test -- if
6992 we already have a connection to the middle hop of the testing
6993 circuit, then it could establish the last hop by using the existing
6994 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
6995 circuits no longer use entry guards in 0.2.1.3-alpha.
6996 - If we have correct permissions on $datadir, we complain to stdout
6997 and fail to start. But dangerous permissions on
6998 $datadir/cached-status/ would cause us to open a log and complain
6999 there. Now complain to stdout and fail to start in both cases. Fixes
7000 bug 820, reported by seeess.
7001 - Remove the old v2 directory authority 'lefkada' from the default
7002 list. It has been gone for many months.
7004 o Code simplifications and refactoring:
7005 - Revise the connection_new functions so that a more typesafe variant
7006 exists. This will work better with Coverity, and let us find any
7007 actual mistakes we're making here.
7008 - Refactor unit testing logic so that dmalloc can be used sensibly
7009 with unit tests to check for memory leaks.
7010 - Move all hidden-service related fields from connection and circuit
7011 structure to substructures: this way they won't eat so much memory.
7014 Changes in version 0.2.0.31 - 2008-09-03
7015 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
7016 a big bug we're seeing where in rare cases traffic from one Tor stream
7017 gets mixed into another stream, and fixes a variety of smaller issues.
7020 - Make sure that two circuits can never exist on the same connection
7021 with the same circuit ID, even if one is marked for close. This
7022 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
7023 - Relays now reject risky extend cells: if the extend cell includes
7024 a digest of all zeroes, or asks to extend back to the relay that
7025 sent the extend cell, tear down the circuit. Ideas suggested
7027 - If not enough of our entry guards are available so we add a new
7028 one, we might use the new one even if it overlapped with the
7029 current circuit's exit relay (or its family). Anonymity bugfix
7030 pointed out by rovv.
7033 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
7034 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
7035 - Correctly detect the presence of the linux/netfilter_ipv4.h header
7036 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
7037 - Pick size of default geoip filename string correctly on windows.
7038 Fixes bug 806. Bugfix on 0.2.0.30.
7039 - Make the autoconf script accept the obsolete --with-ssl-dir
7040 option as an alias for the actually-working --with-openssl-dir
7041 option. Fix the help documentation to recommend --with-openssl-dir.
7042 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
7043 - When using the TransPort option on OpenBSD, and using the User
7044 option to change UID and drop privileges, make sure to open
7045 /dev/pf before dropping privileges. Fixes bug 782. Patch from
7046 Christopher Davis. Bugfix on 0.1.2.1-alpha.
7047 - Try to attach connections immediately upon receiving a RENDEZVOUS2
7048 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
7049 on the client side when connecting to a hidden service. Bugfix
7050 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
7051 - When closing an application-side connection because its circuit is
7052 getting torn down, generate the stream event correctly. Bugfix on
7053 0.1.2.x. Anonymous patch.
7056 Changes in version 0.2.1.5-alpha - 2008-08-31
7057 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
7058 in a lot of the infrastructure for adding authorization to hidden
7059 services, lays the groundwork for having clients read their load
7060 balancing information out of the networkstatus consensus rather than
7061 the individual router descriptors, addresses two potential anonymity
7062 issues, and fixes a variety of smaller issues.
7065 - Convert many internal address representations to optionally hold
7067 - Generate and accept IPv6 addresses in many protocol elements.
7068 - Make resolver code handle nameservers located at ipv6 addresses.
7069 - Begin implementation of proposal 121 ("Client authorization for
7070 hidden services"): configure hidden services with client
7071 authorization, publish descriptors for them, and configure
7072 authorization data for hidden services at clients. The next
7073 step is to actually access hidden services that perform client
7075 - More progress toward proposal 141: Network status consensus
7076 documents and votes now contain bandwidth information for each
7077 router and a summary of that router's exit policy. Eventually this
7078 will be used by clients so that they do not have to download every
7079 known descriptor before building circuits.
7081 o Major bugfixes (on 0.2.0.x and before):
7082 - When sending CREATED cells back for a given circuit, use a 64-bit
7083 connection ID to find the right connection, rather than an addr:port
7084 combination. Now that we can have multiple OR connections between
7085 the same ORs, it is no longer possible to use addr:port to uniquely
7086 identify a connection.
7087 - Relays now reject risky extend cells: if the extend cell includes
7088 a digest of all zeroes, or asks to extend back to the relay that
7089 sent the extend cell, tear down the circuit. Ideas suggested
7091 - If not enough of our entry guards are available so we add a new
7092 one, we might use the new one even if it overlapped with the
7093 current circuit's exit relay (or its family). Anonymity bugfix
7094 pointed out by rovv.
7097 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
7098 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
7099 - When using the TransPort option on OpenBSD, and using the User
7100 option to change UID and drop privileges, make sure to open /dev/pf
7101 before dropping privileges. Fixes bug 782. Patch from Christopher
7102 Davis. Bugfix on 0.1.2.1-alpha.
7103 - Correctly detect the presence of the linux/netfilter_ipv4.h header
7104 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
7105 - Add a missing safe_str() call for a debug log message.
7106 - Use 64 bits instead of 32 bits for connection identifiers used with
7107 the controller protocol, to greatly reduce risk of identifier reuse.
7108 - Make the autoconf script accept the obsolete --with-ssl-dir
7109 option as an alias for the actually-working --with-openssl-dir
7110 option. Fix the help documentation to recommend --with-openssl-dir.
7111 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
7114 - Rate-limit too-many-sockets messages: when they happen, they happen
7115 a lot. Resolves bug 748.
7116 - Resist DNS poisoning a little better by making sure that names in
7117 answer sections match.
7118 - Print the SOCKS5 error message string as well as the error code
7119 when a tor-resolve request fails. Patch from Jacob.
7122 Changes in version 0.2.1.4-alpha - 2008-08-04
7123 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
7126 - The address part of exit policies was not correctly written
7127 to router descriptors. This generated router descriptors that failed
7128 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
7130 - Tor triggered a false assert when extending a circuit to a relay
7131 but we already have a connection open to that relay. Noticed by
7132 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
7135 - Fix a hidden service logging bug: in some edge cases, the router
7136 descriptor of a previously picked introduction point becomes
7137 obsolete and we need to give up on it rather than continually
7138 complaining that it has become obsolete. Observed by xiando. Bugfix
7142 - Take out the TestVia config option, since it was a workaround for
7143 a bug that was fixed in Tor 0.1.1.21.
7146 Changes in version 0.2.1.3-alpha - 2008-08-03
7147 Tor 0.2.1.3-alpha implements most of the pieces to prevent
7148 infinite-length circuit attacks (see proposal 110); fixes a bug that
7149 might cause exit relays to corrupt streams they send back; allows
7150 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
7151 ExcludeExitNodes config options; and fixes a big pile of bugs.
7153 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
7154 - Send a bootstrap problem "warn" event on the first problem if the
7155 reason is NO_ROUTE (that is, our network is down).
7158 - Implement most of proposal 110: The first K cells to be sent
7159 along a circuit are marked as special "early" cells; only K "early"
7160 cells will be allowed. Once this code is universal, we can block
7161 certain kinds of DOS attack by requiring that EXTEND commands must
7162 be sent using an "early" cell.
7165 - Try to attach connections immediately upon receiving a RENDEZVOUS2
7166 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
7167 on the client side when connecting to a hidden service. Bugfix
7168 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
7169 - Ensure that two circuits can never exist on the same connection
7170 with the same circuit ID, even if one is marked for close. This
7171 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
7174 - When relays do their initial bandwidth measurement, don't limit
7175 to just our entry guards for the test circuits. Otherwise we tend
7176 to have multiple test circuits going through a single entry guard,
7177 which makes our bandwidth test less accurate. Fixes part of bug 654;
7178 patch contributed by Josh Albrecht.
7179 - Add an ExcludeExitNodes option so users can list a set of nodes
7180 that should be be excluded from the exit node position, but
7181 allowed elsewhere. Implements proposal 151.
7182 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
7183 ExcludeNodes and ExcludeExitNodes lists.
7184 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
7185 be more efficient. Formerly it was quadratic in the number of
7186 servers; now it should be linear. Fixes bug 509.
7187 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
7188 and n_conn_id_digest fields into a separate structure that's
7189 only needed when the circuit has not yet attached to an n_conn.
7192 - Change the contrib/tor.logrotate script so it makes the new
7193 logs as "_tor:_tor" rather than the default, which is generally
7194 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
7195 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
7196 warnings (occasionally), but it can also cause the compiler to
7197 eliminate error-checking code. Suggested by Peter Gutmann.
7198 - When a hidden service is giving up on an introduction point candidate
7199 that was not included in the last published rendezvous descriptor,
7200 don't reschedule publication of the next descriptor. Fixes bug 763.
7202 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
7203 HiddenServiceExcludeNodes as obsolete: they never worked properly,
7204 and nobody claims to be using them. Fixes bug 754. Bugfix on
7205 0.1.0.1-rc. Patch from Christian Wilms.
7206 - Fix a small alignment and memory-wasting bug on buffer chunks.
7209 o Minor bugfixes (controller):
7210 - When closing an application-side connection because its circuit
7211 is getting torn down, generate the stream event correctly.
7212 Bugfix on 0.1.2.x. Anonymous patch.
7215 - Remove all backward-compatibility code to support relays running
7216 versions of Tor so old that they no longer work at all on the
7220 Changes in version 0.2.0.30 - 2008-07-15
7222 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
7223 warnings (occasionally), but it can also cause the compiler to
7224 eliminate error-checking code. Suggested by Peter Gutmann.
7227 Changes in version 0.2.0.29-rc - 2008-07-08
7228 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
7229 hidden-service performance bugs, and fixes a bunch of smaller bugs.
7232 - If you have more than one bridge but don't know their keys,
7233 you would only launch a request for the descriptor of the first one
7234 on your list. (Tor considered launching requests for the others, but
7235 found that it already had a connection on the way for $0000...0000
7236 so it didn't open another.) Bugfix on 0.2.0.x.
7237 - If you have more than one bridge but don't know their keys, and the
7238 connection to one of the bridges failed, you would cancel all
7239 pending bridge connections. (After all, they all have the same
7240 digest.) Bugfix on 0.2.0.x.
7241 - When a hidden service was trying to establish an introduction point,
7242 and Tor had built circuits preemptively for such purposes, we
7243 were ignoring all the preemptive circuits and launching a new one
7244 instead. Bugfix on 0.2.0.14-alpha.
7245 - When a hidden service was trying to establish an introduction point,
7246 and Tor *did* manage to reuse one of the preemptively built
7247 circuits, it didn't correctly remember which one it used,
7248 so it asked for another one soon after, until there were no
7249 more preemptive circuits, at which point it launched one from
7250 scratch. Bugfix on 0.0.9.x.
7251 - Make directory servers include the X-Your-Address-Is: http header in
7252 their responses even for begin_dir conns. Now clients who only
7253 ever use begin_dir connections still have a way to learn their IP
7254 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
7257 - Fix a macro/CPP interaction that was confusing some compilers:
7258 some GCCs don't like #if/#endif pairs inside macro arguments.
7260 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
7261 Fixes bug 704; fix from Steven Murdoch.
7262 - When opening /dev/null in finish_daemonize(), do not pass the
7263 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
7264 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
7265 - Correctly detect transparent proxy support on Linux hosts that
7266 require in.h to be included before netfilter_ipv4.h. Patch
7268 - Disallow session resumption attempts during the renegotiation
7269 stage of the v2 handshake protocol. Clients should never be trying
7270 session resumption at this point, but apparently some did, in
7271 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
7272 found by Geoff Goodell.
7275 Changes in version 0.2.1.2-alpha - 2008-06-20
7276 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
7277 make it easier to set up your own private Tor network; fixes several
7278 big bugs with using more than one bridge relay; fixes a big bug with
7279 offering hidden services quickly after Tor starts; and uses a better
7280 API for reporting potential bootstrapping problems to the controller.
7283 - New TestingTorNetwork config option to allow adjustment of
7284 previously constant values that, while reasonable, could slow
7285 bootstrapping. Implements proposal 135. Patch from Karsten.
7288 - If you have more than one bridge but don't know their digests,
7289 you would only learn a request for the descriptor of the first one
7290 on your list. (Tor considered launching requests for the others, but
7291 found that it already had a connection on the way for $0000...0000
7292 so it didn't open another.) Bugfix on 0.2.0.x.
7293 - If you have more than one bridge but don't know their digests,
7294 and the connection to one of the bridges failed, you would cancel
7295 all pending bridge connections. (After all, they all have the
7296 same digest.) Bugfix on 0.2.0.x.
7297 - When establishing a hidden service, introduction points that
7298 originate from cannibalized circuits are completely ignored and not
7299 included in rendezvous service descriptors. This might be another
7300 reason for delay in making a hidden service available. Bugfix
7301 from long ago (0.0.9.x?)
7304 - Allow OpenSSL to use dynamic locks if it wants.
7305 - When building a consensus, do not include routers that are down.
7306 This will cut down 30% to 40% on consensus size. Implements
7308 - In directory authorities' approved-routers files, allow
7309 fingerprints with or without space.
7310 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
7311 controller can query our current bootstrap state in case it attaches
7312 partway through and wants to catch up.
7313 - Send an initial "Starting" bootstrap status event, so we have a
7314 state to start out in.
7317 - Asking for a conditional consensus at .../consensus/<fingerprints>
7318 would crash a dirserver if it did not already have a
7319 consensus. Bugfix on 0.2.1.1-alpha.
7320 - Clean up some macro/CPP interactions: some GCC versions don't like
7321 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
7324 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
7325 - Directory authorities shouldn't complain about bootstrapping
7326 problems just because they do a lot of reachability testing and
7327 some of the connection attempts fail.
7328 - Start sending "count" and "recommendation" key/value pairs in
7329 bootstrap problem status events, so the controller can hear about
7330 problems even before Tor decides they're worth reporting for sure.
7331 - If you're using bridges, generate "bootstrap problem" warnings
7332 as soon as you run out of working bridges, rather than waiting
7333 for ten failures -- which will never happen if you have less than
7335 - If we close our OR connection because there's been a circuit
7336 pending on it for too long, we were telling our bootstrap status
7337 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
7340 Changes in version 0.2.1.1-alpha - 2008-06-13
7341 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
7342 were making the Tor process bloat especially on Linux; makes our TLS
7343 handshake blend in better; sends "bootstrap phase" status events to
7344 the controller, so it can keep the user informed of progress (and
7345 problems) fetching directory information and establishing circuits;
7346 and adds a variety of smaller features.
7349 - More work on making our TLS handshake blend in: modify the list
7350 of ciphers advertised by OpenSSL in client mode to even more
7351 closely resemble a common web browser. We cheat a little so that
7352 we can advertise ciphers that the locally installed OpenSSL doesn't
7354 - Start sending "bootstrap phase" status events to the controller,
7355 so it can keep the user informed of progress fetching directory
7356 information and establishing circuits. Also inform the controller
7357 if we think we're stuck at a particular bootstrap phase. Implements
7359 - Resume using OpenSSL's RAND_poll() for better (and more portable)
7360 cross-platform entropy collection again. We used to use it, then
7361 stopped using it because of a bug that could crash systems that
7362 called RAND_poll when they had a lot of fds open. It looks like the
7363 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
7364 at startup, and to call RAND_poll() when we reseed later only if
7365 we have a non-buggy OpenSSL version.
7368 - When we choose to abandon a new entry guard because we think our
7369 older ones might be better, close any circuits pending on that
7370 new entry guard connection. This fix should make us recover much
7371 faster when our network is down and then comes back. Bugfix on
7372 0.1.2.8-beta; found by lodger.
7374 o Memory fixes and improvements:
7375 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
7376 to avoid unused RAM in buffer chunks and memory pools.
7377 - Speed up parsing and cut down on memory fragmentation by using
7378 stack-style allocations for parsing directory objects. Previously,
7379 this accounted for over 40% of allocations from within Tor's code
7380 on a typical directory cache.
7381 - Use a Bloom filter rather than a digest-based set to track which
7382 descriptors we need to keep around when we're cleaning out old
7383 router descriptors. This speeds up the computation significantly,
7384 and may reduce fragmentation.
7385 - Reduce the default smartlist size from 32 to 16; it turns out that
7386 most smartlists hold around 8-12 elements tops.
7387 - Make dumpstats() log the fullness and size of openssl-internal
7389 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
7390 patch to their OpenSSL, turn it on to save memory on servers. This
7391 patch will (with any luck) get included in a mainline distribution
7393 - Never use OpenSSL compression: it wastes RAM and CPU trying to
7394 compress cells, which are basically all encrypted, compressed,
7398 - Stop reloading the router list from disk for no reason when we
7399 run out of reachable directory mirrors. Once upon a time reloading
7400 it would set the 'is_running' flag back to 1 for them. It hasn't
7401 done that for a long time.
7402 - In very rare situations new hidden service descriptors were
7403 published earlier than 30 seconds after the last change to the
7404 service. (We currently think that a hidden service descriptor
7405 that's been stable for 30 seconds is worth publishing.)
7408 - Allow separate log levels to be configured for different logging
7409 domains. For example, this allows one to log all notices, warnings,
7410 or errors, plus all memory management messages of level debug or
7411 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
7412 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
7413 and stop using a warning that had become unfixably verbose under
7415 - New --hush command-line option similar to --quiet. While --quiet
7416 disables all logging to the console on startup, --hush limits the
7417 output to messages of warning and error severity.
7418 - Servers support a new URL scheme for consensus downloads that
7419 allows the client to specify which authorities are trusted.
7420 The server then only sends the consensus if the client will trust
7421 it. Otherwise a 404 error is sent back. Clients use this
7422 new scheme when the server supports it (meaning it's running
7423 0.2.1.1-alpha or later). Implements proposal 134.
7424 - New configure/torrc options (--enable-geoip-stats,
7425 DirRecordUsageByCountry) to record how many IPs we've served
7426 directory info to in each country code, how many status documents
7427 total we've sent to each country code, and what share of the total
7428 directory requests we should expect to see.
7429 - Use the TLS1 hostname extension to more closely resemble browser
7431 - Lots of new unit tests.
7432 - Add a macro to implement the common pattern of iterating through
7433 two parallel lists in lockstep.
7436 Changes in version 0.2.0.28-rc - 2008-06-13
7437 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
7438 performance bug, and fixes a bunch of smaller bugs.
7441 - Fix a bug where, when we were choosing the 'end stream reason' to
7442 put in our relay end cell that we send to the exit relay, Tor
7443 clients on Windows were sometimes sending the wrong 'reason'. The
7444 anonymity problem is that exit relays may be able to guess whether
7445 the client is running Windows, thus helping partition the anonymity
7446 set. Down the road we should stop sending reasons to exit relays,
7447 or otherwise prevent future versions of this bug.
7450 - While setting up a hidden service, some valid introduction circuits
7451 were overlooked and abandoned. This might be the reason for
7452 the long delay in making a hidden service available. Bugfix on
7456 - Update to the "June 9 2008" ip-to-country file.
7457 - Run 'make test' as part of 'make dist', so we stop releasing so
7458 many development snapshots that fail their unit tests.
7461 - When we're checking if we have enough dir info for each relay
7462 to begin establishing circuits, make sure that we actually have
7463 the descriptor listed in the consensus, not just any descriptor.
7465 - Bridge relays no longer print "xx=0" in their extrainfo document
7466 for every single country code in the geoip db. Bugfix on
7468 - Only warn when we fail to load the geoip file if we were planning to
7469 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
7470 - If we change our MaxAdvertisedBandwidth and then reload torrc,
7471 Tor won't realize it should publish a new relay descriptor. Fixes
7472 bug 688, reported by mfr. Bugfix on 0.1.2.x.
7473 - When we haven't had any application requests lately, don't bother
7474 logging that we have expired a bunch of descriptors. Bugfix
7476 - Make relay cells written on a connection count as non-padding when
7477 tracking how long a connection has been in use. Bugfix on
7478 0.2.0.1-alpha. Spotted by lodger.
7479 - Fix unit tests in 0.2.0.27-rc.
7480 - Fix compile on Windows.
7483 Changes in version 0.2.0.27-rc - 2008-06-03
7484 Tor 0.2.0.27-rc adds a few features we left out of the earlier
7485 release candidates. In particular, we now include an IP-to-country
7486 GeoIP database, so controllers can easily look up what country a
7487 given relay is in, and so bridge relays can give us some sanitized
7488 summaries about which countries are making use of bridges. (See proposal
7489 126-geoip-fetching.txt for details.)
7492 - Include an IP-to-country GeoIP file in the tarball, so bridge
7493 relays can report sanitized summaries of the usage they're seeing.
7496 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
7497 Robert Hogan. Fixes the first part of bug 681.
7498 - Make bridge authorities never serve extrainfo docs.
7499 - Add support to detect Libevent versions in the 1.4.x series
7501 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
7502 - Include a new contrib/tor-exit-notice.html file that exit relay
7503 operators can put on their website to help reduce abuse queries.
7506 - When tunneling an encrypted directory connection, and its first
7507 circuit fails, do not leave it unattached and ask the controller
7508 to deal. Fixes the second part of bug 681.
7509 - Make bridge authorities correctly expire old extrainfo documents
7513 Changes in version 0.2.0.26-rc - 2008-05-13
7514 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
7515 in Debian's OpenSSL packages. All users running any 0.2.0.x version
7516 should upgrade, whether they're running Debian or not.
7518 o Major security fixes:
7519 - Use new V3 directory authority keys on the tor26, gabelmoo, and
7520 moria1 V3 directory authorities. The old keys were generated with
7521 a vulnerable version of Debian's OpenSSL package, and must be
7522 considered compromised. Other authorities' keys were not generated
7523 with an affected version of OpenSSL.
7526 - List authority signatures as "unrecognized" based on DirServer
7527 lines, not on cert cache. Bugfix on 0.2.0.x.
7530 - Add a new V3AuthUseLegacyKey option to make it easier for
7531 authorities to change their identity keys if they have to.
7534 Changes in version 0.2.0.25-rc - 2008-04-23
7535 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
7538 - Remember to initialize threading before initializing logging.
7539 Otherwise, many BSD-family implementations will crash hard on
7540 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
7543 - Authorities correctly free policies on bad servers on
7544 exit. Fixes bug 672. Bugfix on 0.2.0.x.
7547 Changes in version 0.2.0.24-rc - 2008-04-22
7548 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
7549 v3 directory authority, makes relays with dynamic IP addresses and no
7550 DirPort notice more quickly when their IP address changes, fixes a few
7551 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
7553 o New directory authorities:
7554 - Take lefkada out of the list of v3 directory authorities, since
7555 it has been down for months.
7556 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
7560 - Detect address changes more quickly on non-directory mirror
7561 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
7563 o Minor features (security):
7564 - Reject requests for reverse-dns lookup of names that are in
7565 a private address space. Patch from lodger.
7566 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
7569 o Minor bugfixes (crashes):
7570 - Avoid a rare assert that can trigger when Tor doesn't have much
7571 directory information yet and it tries to fetch a v2 hidden
7572 service descriptor. Fixes bug 651, reported by nwf.
7573 - Initialize log mutex before initializing dmalloc. Otherwise,
7574 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
7575 - Use recursive pthread mutexes in order to avoid deadlock when
7576 logging debug-level messages to a controller. Bug spotted by nwf,
7577 bugfix on 0.2.0.16-alpha.
7579 o Minor bugfixes (resource management):
7580 - Keep address policies from leaking memory: start their refcount
7581 at 1, not 2. Bugfix on 0.2.0.16-alpha.
7582 - Free authority certificates on exit, so they don't look like memory
7583 leaks. Bugfix on 0.2.0.19-alpha.
7584 - Free static hashtables for policy maps and for TLS connections on
7585 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
7586 - Avoid allocating extra space when computing consensuses on 64-bit
7587 platforms. Bug spotted by aakova.
7589 o Minor bugfixes (misc):
7590 - Do not read the configuration file when we've only been told to
7591 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
7592 based on patch from Sebastian Hahn.
7593 - Exit relays that are used as a client can now reach themselves
7594 using the .exit notation, rather than just launching an infinite
7595 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
7596 - When attempting to open a logfile fails, tell us why.
7597 - Fix a dumb bug that was preventing us from knowing that we should
7598 preemptively build circuits to handle expected directory requests.
7599 Fixes bug 660. Bugfix on 0.1.2.x.
7600 - Warn less verbosely about clock skew from netinfo cells from
7601 untrusted sources. Fixes bug 663.
7602 - Make controller stream events for DNS requests more consistent,
7603 by adding "new stream" events for DNS requests, and removing
7604 spurious "stream closed" events" for cached reverse resolves.
7605 Patch from mwenge. Fixes bug 646.
7606 - Correctly notify one-hop connections when a circuit build has
7607 failed. Possible fix for bug 669. Found by lodger.
7610 Changes in version 0.2.0.23-rc - 2008-03-24
7611 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
7612 makes bootstrapping faster if the first directory mirror you contact
7613 is down. The bundles also include the new Vidalia 0.1.2 release.
7616 - When a tunneled directory request is made to a directory server
7617 that's down, notice after 30 seconds rather than 120 seconds. Also,
7618 fail any begindir streams that are pending on it, so they can
7619 retry elsewhere. This was causing multi-minute delays on bootstrap.
7622 Changes in version 0.2.0.22-rc - 2008-03-18
7623 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
7624 enables encrypted directory connections by default for non-relays, fixes
7625 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
7626 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
7629 - Enable encrypted directory connections by default for non-relays,
7630 so censor tools that block Tor directory connections based on their
7631 plaintext patterns will no longer work. This means Tor works in
7632 certain censored countries by default again.
7635 - Make sure servers always request certificates from clients during
7636 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
7637 - Do not enter a CPU-eating loop when a connection is closed in
7638 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
7639 diagnosed by lodger; bugfix on 0.2.0.20-rc.
7640 - Fix assertion failure that could occur when a blocked circuit
7641 became unblocked, and it had pending client DNS requests. Bugfix
7642 on 0.2.0.1-alpha. Fixes bug 632.
7644 o Minor bugfixes (on 0.1.2.x):
7645 - Generate "STATUS_SERVER" events rather than misspelled
7646 "STATUS_SEVER" events. Caught by mwenge.
7647 - When counting the number of bytes written on a TLS connection,
7648 look at the BIO actually used for writing to the network, not
7649 at the BIO used (sometimes) to buffer data for the network.
7650 Looking at different BIOs could result in write counts on the
7651 order of ULONG_MAX. Fixes bug 614.
7652 - On Windows, correctly detect errors when listing the contents of
7653 a directory. Fix from lodger.
7655 o Minor bugfixes (on 0.2.0.x):
7656 - Downgrade "sslv3 alert handshake failure" message to INFO.
7657 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
7658 left BandwidthRate and BandwidthBurst at the default, we would be
7659 silently limited by those defaults. Now raise them to match the
7660 RelayBandwidth* values.
7661 - Fix the SVK version detection logic to work correctly on a branch.
7662 - Make --enable-openbsd-malloc work correctly on Linux with alpha
7663 CPUs. Fixes bug 625.
7664 - Logging functions now check that the passed severity is sane.
7665 - Use proper log levels in the testsuite call of
7666 get_interface_address6().
7667 - When using a nonstandard malloc, do not use the platform values for
7668 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
7669 - Make the openbsd malloc code use 8k pages on alpha CPUs and
7671 - Detect mismatched page sizes when using --enable-openbsd-malloc.
7672 - Avoid double-marked-for-close warning when certain kinds of invalid
7673 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
7674 for bug 617. Bugfix on 0.2.0.1-alpha.
7675 - Make sure that the "NULL-means-reject *:*" convention is followed by
7676 all the policy manipulation functions, avoiding some possible crash
7677 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
7678 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
7679 actually works, and doesn't warn about every single reverse lookup.
7680 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
7683 - Only log guard node status when guard node status has changed.
7684 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
7685 make "INFO" 75% less verbose.
7688 Changes in version 0.2.0.21-rc - 2008-03-02
7689 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
7690 makes Tor work well with Vidalia again, fixes a rare assert bug,
7691 and fixes a pair of more minor bugs. The bundles also include Vidalia
7692 0.1.0 and Torbutton 1.1.16.
7695 - The control port should declare that it requires password auth
7696 when HashedControlSessionPassword is set too. Patch from Matt Edman;
7697 bugfix on 0.2.0.20-rc. Fixes bug 615.
7698 - Downgrade assert in connection_buckets_decrement() to a log message.
7699 This may help us solve bug 614, and in any case will make its
7700 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
7701 - We were sometimes miscounting the number of bytes read from the
7702 network, causing our rate limiting to not be followed exactly.
7703 Bugfix on 0.2.0.16-alpha. Reported by lodger.
7706 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
7707 OpenSSL versions should have been working fine. Diagnosis and patch
7708 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
7709 Bugfix on 0.2.0.20-rc.
7712 Changes in version 0.2.0.20-rc - 2008-02-24
7713 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
7714 makes more progress towards normalizing Tor's TLS handshake, makes
7715 hidden services work better again, helps relays bootstrap if they don't
7716 know their IP address, adds optional support for linking in openbsd's
7717 allocator or tcmalloc, allows really fast relays to scale past 15000
7718 sockets, and fixes a bunch of minor bugs reported by Veracode.
7721 - Enable the revised TLS handshake based on the one designed by
7722 Steven Murdoch in proposal 124, as revised in proposal 130. It
7723 includes version negotiation for OR connections as described in
7724 proposal 105. The new handshake is meant to be harder for censors
7725 to fingerprint, and it adds the ability to detect certain kinds of
7726 man-in-the-middle traffic analysis attacks. The version negotiation
7727 feature will allow us to improve Tor's link protocol more safely
7729 - Choose which bridge to use proportional to its advertised bandwidth,
7730 rather than uniformly at random. This should speed up Tor for
7731 bridge users. Also do this for people who set StrictEntryNodes.
7732 - When a TrackHostExits-chosen exit fails too many times in a row,
7733 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
7736 - Resolved problems with (re-)fetching hidden service descriptors.
7737 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
7739 - If we only ever used Tor for hidden service lookups or posts, we
7740 would stop building circuits and start refusing connections after
7741 24 hours, since we falsely believed that Tor was dormant. Reported
7742 by nwf; bugfix on 0.1.2.x.
7743 - Servers that don't know their own IP address should go to the
7744 authorities for their first directory fetch, even if their DirPort
7745 is off or if they don't know they're reachable yet. This will help
7746 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
7747 - When counting the number of open sockets, count not only the number
7748 of sockets we have received from the socket() call, but also
7749 the number we've gotten from accept() and socketpair(). This bug
7750 made us fail to count all sockets that we were using for incoming
7751 connections. Bugfix on 0.2.0.x.
7752 - Fix code used to find strings within buffers, when those strings
7753 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
7754 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
7755 - Add a new __HashedControlSessionPassword option for controllers
7756 to use for one-off session password hashes that shouldn't get
7757 saved to disk by SAVECONF --- Vidalia users were accumulating a
7758 pile of HashedControlPassword lines in their torrc files, one for
7759 each time they had restarted Tor and then clicked Save. Make Tor
7760 automatically convert "HashedControlPassword" to this new option but
7761 only when it's given on the command line. Partial fix for bug 586.
7763 o Minor features (performance):
7764 - Tune parameters for cell pool allocation to minimize amount of
7766 - Add OpenBSD malloc code from phk as an optional malloc
7767 replacement on Linux: some glibc libraries do very poorly
7768 with Tor's memory allocation patterns. Pass
7769 --enable-openbsd-malloc to get the replacement malloc code.
7770 - Add a --with-tcmalloc option to the configure script to link
7771 against tcmalloc (if present). Does not yet search for
7772 non-system include paths.
7773 - Stop imposing an arbitrary maximum on the number of file descriptors
7774 used for busy servers. Bug reported by Olaf Selke; patch from
7777 o Minor features (other):
7778 - When SafeLogging is disabled, log addresses along with all TLS
7780 - When building with --enable-gcc-warnings, check for whether Apple's
7781 warning "-Wshorten-64-to-32" is available.
7782 - Add a --passphrase-fd argument to the tor-gencert command for
7785 o Minor bugfixes (memory leaks and code problems):
7786 - We were leaking a file descriptor if Tor started with a zero-length
7787 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
7788 - Detect size overflow in zlib code. Reported by Justin Ferguson and
7790 - We were comparing the raw BridgePassword entry with a base64'ed
7791 version of it, when handling a "/tor/networkstatus-bridges"
7792 directory request. Now compare correctly. Noticed by Veracode.
7793 - Recover from bad tracked-since value in MTBF-history file.
7795 - Alter the code that tries to recover from unhandled write
7796 errors, to not try to flush onto a socket that's given us
7797 unhandled errors. Bugfix on 0.1.2.x.
7798 - Make Unix controlsockets work correctly on OpenBSD. Patch from
7799 tup. Bugfix on 0.2.0.3-alpha.
7801 o Minor bugfixes (other):
7802 - If we have an extra-info document for our server, always make
7803 it available on the control port, even if we haven't gotten
7804 a copy of it from an authority yet. Patch from mwenge.
7805 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
7806 - Directory mirrors no longer include a guess at the client's IP
7807 address if the connection appears to be coming from the same /24
7808 network; it was producing too many wrong guesses.
7809 - Make the new hidden service code respect the SafeLogging setting.
7810 Bugfix on 0.2.0.x. Patch from Karsten.
7811 - When starting as an authority, do not overwrite all certificates
7812 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
7813 - If we're trying to flush the last bytes on a connection (for
7814 example, when answering a directory request), reset the
7815 time-to-give-up timeout every time we manage to write something
7816 on the socket. Bugfix on 0.1.2.x.
7817 - Change the behavior of "getinfo status/good-server-descriptor"
7818 so it doesn't return failure when any authority disappears.
7819 - Even though the man page said that "TrackHostExits ." should
7820 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
7821 - Report TLS "zero return" case as a "clean close" and "IO error"
7822 as a "close". Stop calling closes "unexpected closes": existing
7823 Tors don't use SSL_close(), so having a connection close without
7824 the TLS shutdown handshake is hardly unexpected.
7825 - Send NAMESERVER_STATUS messages for a single failed nameserver
7828 o Code simplifications and refactoring:
7829 - Remove the tor_strpartition function: its logic was confused,
7830 and it was only used for one thing that could be implemented far
7834 Changes in version 0.2.0.19-alpha - 2008-02-09
7835 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
7836 handshake, makes path selection for relays more secure and IP address
7837 guessing more robust, and generally fixes a lot of bugs in preparation
7838 for calling the 0.2.0 branch stable.
7841 - Do not include recognizeable strings in the commonname part of
7842 Tor's x509 certificates.
7845 - If we're a relay, avoid picking ourselves as an introduction point,
7846 a rendezvous point, or as the final hop for internal circuits. Bug
7847 reported by taranis and lodger. Bugfix on 0.1.2.x.
7848 - Patch from "Andrew S. Lists" to catch when we contact a directory
7849 mirror at IP address X and he says we look like we're coming from
7850 IP address X. Bugfix on 0.1.2.x.
7852 o Minor features (security):
7853 - Be more paranoid about overwriting sensitive memory on free(),
7854 as a defensive programming tactic to ensure forward secrecy.
7856 o Minor features (directory authority):
7857 - Actually validate the options passed to AuthDirReject,
7858 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
7859 - Reject router descriptors with out-of-range bandwidthcapacity or
7860 bandwidthburst values.
7862 o Minor features (controller):
7863 - Reject controller commands over 1MB in length. This keeps rogue
7864 processes from running us out of memory.
7866 o Minor features (misc):
7867 - Give more descriptive well-formedness errors for out-of-range
7868 hidden service descriptor/protocol versions.
7869 - Make memory debugging information describe more about history
7870 of cell allocation, so we can help reduce our memory use.
7872 o Deprecated features (controller):
7873 - The status/version/num-versioning and status/version/num-concurring
7874 GETINFO options are no longer useful in the v3 directory protocol:
7875 treat them as deprecated, and warn when they're used.
7878 - When our consensus networkstatus has been expired for a while, stop
7879 being willing to build circuits using it. Fixes bug 401. Bugfix
7881 - Directory caches now fetch certificates from all authorities
7882 listed in a networkstatus consensus, even when they do not
7883 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
7884 - When connecting to a bridge without specifying its key, insert
7885 the connection into the identity-to-connection map as soon as
7886 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
7887 - Detect versions of OS X where malloc_good_size() is present in the
7888 library but never actually declared. Resolves bug 587. Bugfix
7890 - Stop incorrectly truncating zlib responses to directory authority
7891 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
7892 - Stop recommending that every server operator send mail to tor-ops.
7893 Resolves bug 597. Bugfix on 0.1.2.x.
7894 - Don't trigger an assert if we start a directory authority with a
7895 private IP address (like 127.0.0.1).
7896 - Avoid possible failures when generating a directory with routers
7897 with over-long versions strings, or too many flags set. Bugfix
7899 - If an attempt to launch a DNS resolve request over the control
7900 port fails because we have overrun the limit on the number of
7901 connections, tell the controller that the request has failed.
7902 - Avoid using too little bandwidth when our clock skips a few
7903 seconds. Bugfix on 0.1.2.x.
7904 - Fix shell error when warning about missing packages in configure
7905 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
7906 - Do not become confused when receiving a spurious VERSIONS-like
7907 cell from a confused v1 client. Bugfix on 0.2.0.x.
7908 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
7909 introduction points for a hidden service have failed. Patch from
7910 Karsten Loesing. Bugfix on 0.2.0.x.
7912 o Code simplifications and refactoring:
7913 - Remove some needless generality from cpuworker code, for improved
7915 - Stop overloading the circuit_t.onionskin field for both "onionskin
7916 from a CREATE cell that we are waiting for a cpuworker to be
7917 assigned" and "onionskin from an EXTEND cell that we are going to
7918 send to an OR as soon as we are connected". Might help with bug 600.
7919 - Add an in-place version of aes_crypt() so that we can avoid doing a
7920 needless memcpy() call on each cell payload.
7923 Changes in version 0.2.0.18-alpha - 2008-01-25
7924 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
7925 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
7926 that can warn or reject connections to ports generally associated with
7927 vulnerable-plaintext protocols.
7929 o New directory authorities:
7930 - Set up dannenberg (run by CCC) as the sixth v3 directory
7934 - Fix a major memory leak when attempting to use the v2 TLS
7935 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
7936 - We accidentally enabled the under-development v2 TLS handshake
7937 code, which was causing log entries like "TLS error while
7938 renegotiating handshake". Disable it again. Resolves bug 590.
7939 - We were computing the wrong Content-Length: header for directory
7940 responses that need to be compressed on the fly, causing clients
7941 asking for those items to always fail. Bugfix on 0.2.0.x; partially
7945 - Avoid going directly to the directory authorities even if you're a
7946 relay, if you haven't found yourself reachable yet or if you've
7947 decided not to advertise your dirport yet. Addresses bug 556.
7948 - If we've gone 12 hours since our last bandwidth check, and we
7949 estimate we have less than 50KB bandwidth capacity but we could
7950 handle more, do another bandwidth test.
7951 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
7952 Tor can warn and/or refuse connections to ports commonly used with
7953 vulnerable-plaintext protocols. Currently we warn on ports 23,
7954 109, 110, and 143, but we don't reject any.
7957 - When we setconf ClientOnly to 1, close any current OR and Dir
7958 listeners. Reported by mwenge.
7959 - When we get a consensus that's been signed by more people than
7960 we expect, don't log about it; it's not a big deal. Reported
7964 - Don't answer "/tor/networkstatus-bridges" directory requests if
7965 the request isn't encrypted.
7966 - Make "ClientOnly 1" config option disable directory ports too.
7967 - Patches from Karsten Loesing to make v2 hidden services more
7968 robust: work even when there aren't enough HSDir relays available;
7969 retry when a v2 rend desc fetch fails; but don't retry if we
7970 already have a usable v0 rend desc.
7973 Changes in version 0.2.0.17-alpha - 2008-01-17
7974 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
7977 - Make the tor-gencert man page get included correctly in the tarball.
7980 Changes in version 0.2.0.16-alpha - 2008-01-17
7981 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
7982 Loesing, and generally cleans up a lot of features and minor bugs.
7984 o New directory authorities:
7985 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
7988 o Major performance improvements:
7989 - Switch our old ring buffer implementation for one more like that
7990 used by free Unix kernels. The wasted space in a buffer with 1mb
7991 of data will now be more like 8k than 1mb. The new implementation
7992 also avoids realloc();realloc(); patterns that can contribute to
7993 memory fragmentation.
7996 - Configuration files now accept C-style strings as values. This
7997 helps encode characters not allowed in the current configuration
7998 file format, such as newline or #. Addresses bug 557.
7999 - Although we fixed bug 539 (where servers would send HTTP status 503
8000 responses _and_ send a body too), there are still servers out
8001 there that haven't upgraded. Therefore, make clients parse such
8002 bodies when they receive them.
8003 - When we're not serving v2 directory information, there is no reason
8004 to actually keep any around. Remove the obsolete files and directory
8005 on startup if they are very old and we aren't going to serve them.
8007 o Minor performance improvements:
8008 - Reference-count and share copies of address policy entries; only 5%
8009 of them were actually distinct.
8010 - Never walk through the list of logs if we know that no log is
8011 interested in a given message.
8014 - When an authority has not signed a consensus, do not try to
8015 download a nonexistent "certificate with key 00000000". Bugfix
8016 on 0.2.0.x. Fixes bug 569.
8017 - Fix a rare assert error when we're closing one of our threads:
8018 use a mutex to protect the list of logs, so we never write to the
8019 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
8020 bug 575, which is kind of the revenge of bug 222.
8021 - Patch from Karsten Loesing to complain less at both the client
8022 and the relay when a relay used to have the HSDir flag but doesn't
8023 anymore, and we try to upload a hidden service descriptor.
8024 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
8026 - Do not try to download missing certificates until we have tried
8027 to check our fallback consensus. Fixes bug 583.
8028 - Make bridges round reported GeoIP stats info up to the nearest
8029 estimate, not down. Now we can distinguish between "0 people from
8030 this country" and "1 person from this country".
8031 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
8032 - Avoid possible segfault if key generation fails in
8033 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
8034 - Avoid segfault in the case where a badly behaved v2 versioning
8035 directory sends a signed networkstatus with missing client-versions.
8037 - Avoid segfaults on certain complex invocations of
8038 router_get_by_hexdigest(). Bugfix on 0.1.2.
8039 - Correct bad index on array access in parse_http_time(). Bugfix
8041 - Fix possible bug in vote generation when server versions are present
8042 but client versions are not.
8043 - Fix rare bug on REDIRECTSTREAM control command when called with no
8044 port set: it could erroneously report an error when none had
8046 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
8047 compressing large objects and find ourselves with more than 4k
8048 left over. Bugfix on 0.2.0.
8049 - Fix a small memory leak when setting up a hidden service.
8050 - Fix a few memory leaks that could in theory happen under bizarre
8052 - Fix an assert if we post a general-purpose descriptor via the
8053 control port but that descriptor isn't mentioned in our current
8054 network consensus. Bug reported by Jon McLachlan; bugfix on
8057 o Minor features (controller):
8058 - Get NS events working again. Patch from tup.
8059 - The GETCONF command now escapes and quotes configuration values
8060 that don't otherwise fit into the torrc file.
8061 - The SETCONF command now handles quoted values correctly.
8063 o Minor features (directory authorities):
8064 - New configuration options to override default maximum number of
8065 servers allowed on a single IP address. This is important for
8066 running a test network on a single host.
8067 - Actually implement the -s option to tor-gencert.
8068 - Add a manual page for tor-gencert.
8070 o Minor features (bridges):
8071 - Bridge authorities no longer serve bridge descriptors over
8072 unencrypted connections.
8074 o Minor features (other):
8075 - Add hidden services and DNSPorts to the list of things that make
8076 Tor accept that it has running ports. Change starting Tor with no
8077 ports from a fatal error to a warning; we might change it back if
8078 this turns out to confuse anybody. Fixes bug 579.
8081 Changes in version 0.1.2.19 - 2008-01-17
8082 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
8083 exit policy a little bit more conservative so it's safer to run an
8084 exit relay on a home system, and fixes a variety of smaller issues.
8087 - Exit policies now reject connections that are addressed to a
8088 relay's public (external) IP address too, unless
8089 ExitPolicyRejectPrivate is turned off. We do this because too
8090 many relays are running nearby to services that trust them based
8094 - When the clock jumps forward a lot, do not allow the bandwidth
8095 buckets to become negative. Fixes bug 544.
8096 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
8097 on every successful resolve. Reported by Mike Perry.
8098 - Purge old entries from the "rephist" database and the hidden
8099 service descriptor database even when DirPort is zero.
8100 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
8101 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
8102 crashing or mis-answering these requests.
8103 - When we decide to send a 503 response to a request for servers, do
8104 not then also send the server descriptors: this defeats the whole
8105 purpose. Fixes bug 539.
8108 - Changing the ExitPolicyRejectPrivate setting should cause us to
8109 rebuild our server descriptor.
8110 - Fix handling of hex nicknames when answering controller requests for
8111 networkstatus by name, or when deciding whether to warn about
8112 unknown routers in a config option. (Patch from mwenge.)
8113 - Fix a couple of hard-to-trigger autoconf problems that could result
8114 in really weird results on platforms whose sys/types.h files define
8115 nonstandard integer types.
8116 - Don't try to create the datadir when running --verify-config or
8117 --hash-password. Resolves bug 540.
8118 - If we were having problems getting a particular descriptor from the
8119 directory caches, and then we learned about a new descriptor for
8120 that router, we weren't resetting our failure count. Reported
8122 - Although we fixed bug 539 (where servers would send HTTP status 503
8123 responses _and_ send a body too), there are still servers out there
8124 that haven't upgraded. Therefore, make clients parse such bodies
8125 when they receive them.
8126 - Run correctly on systems where rlim_t is larger than unsigned long.
8127 This includes some 64-bit systems.
8128 - Run correctly on platforms (like some versions of OS X 10.5) where
8129 the real limit for number of open files is OPEN_FILES, not rlim_max
8130 from getrlimit(RLIMIT_NOFILES).
8131 - Avoid a spurious free on base64 failure.
8132 - Avoid segfaults on certain complex invocations of
8133 router_get_by_hexdigest().
8134 - Fix rare bug on REDIRECTSTREAM control command when called with no
8135 port set: it could erroneously report an error when none had
8139 Changes in version 0.2.0.15-alpha - 2007-12-25
8140 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
8141 features added in 0.2.0.13-alpha.
8144 - Fix several remotely triggerable asserts based on DirPort requests
8145 for a v2 or v3 networkstatus object before we were prepared. This
8146 was particularly bad for 0.2.0.13 and later bridge relays, who
8147 would never have a v2 networkstatus and would thus always crash
8148 when used. Bugfixes on 0.2.0.x.
8149 - Estimate the v3 networkstatus size more accurately, rather than
8150 estimating it at zero bytes and giving it artificially high priority
8151 compared to other directory requests. Bugfix on 0.2.0.x.
8154 - Fix configure.in logic for cross-compilation.
8155 - When we load a bridge descriptor from the cache, and it was
8156 previously unreachable, mark it as retriable so we won't just
8157 ignore it. Also, try fetching a new copy immediately. Bugfixes
8159 - The bridge GeoIP stats were counting other relays, for example
8160 self-reachability and authority-reachability tests.
8163 - Support compilation to target iPhone; patch from cjacker huang.
8164 To build for iPhone, pass the --enable-iphone option to configure.
8167 Changes in version 0.2.0.14-alpha - 2007-12-23
8169 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
8170 without a datadirectory from a previous Tor install. Reported
8172 - Fix a crash when we fetch a descriptor that turns out to be
8173 unexpected (it used to be in our networkstatus when we started
8174 fetching it, but it isn't in our current networkstatus), and we
8175 aren't using bridges. Bugfix on 0.2.0.x.
8176 - Fix a crash when accessing hidden services: it would work the first
8177 time you use a given introduction point for your service, but
8178 on subsequent requests we'd be using garbage memory. Fixed by
8179 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
8180 - Fix a crash when we load a bridge descriptor from disk but we don't
8181 currently have a Bridge line for it in our torrc. Bugfix on
8185 - If bridge authorities set BridgePassword, they will serve a
8186 snapshot of known bridge routerstatuses from their DirPort to
8187 anybody who knows that password. Unset by default.
8190 - Make the unit tests build again.
8191 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
8192 - Make PublishServerDescriptor default to 1, so the default doesn't
8193 have to change as we invent new directory protocol versions.
8194 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
8195 be included unless sys/time.h is already included. Fixes
8196 bug 553. Bugfix on 0.2.0.x.
8197 - If we receive a general-purpose descriptor and then receive an
8198 identical bridge-purpose descriptor soon after, don't discard
8199 the next one as a duplicate.
8202 - If BridgeRelay is set to 1, then the default for
8203 PublishServerDescriptor is now "bridge" rather than "v2,v3".
8204 - If the user sets RelayBandwidthRate but doesn't set
8205 RelayBandwidthBurst, then make them equal rather than erroring out.
8208 Changes in version 0.2.0.13-alpha - 2007-12-21
8209 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
8210 Goodell, fixes many more bugs, and adds a lot of infrastructure for
8213 o New directory authorities:
8214 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
8218 - Only update guard status (usable / not usable) once we have
8219 enough directory information. This was causing us to always pick
8220 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
8221 causing us to discard all our guards on startup if we hadn't been
8222 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
8223 - Purge old entries from the "rephist" database and the hidden
8224 service descriptor databases even when DirPort is zero. Bugfix
8226 - We were ignoring our RelayBandwidthRate for the first 30 seconds
8227 after opening a circuit -- even a relayed circuit. Bugfix on
8229 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
8230 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
8231 crashing or mis-answering these types of requests.
8232 - Relays were publishing their server descriptor to v1 and v2
8233 directory authorities, but they didn't try publishing to v3-only
8234 authorities. Fix this; and also stop publishing to v1 authorities.
8236 - When we were reading router descriptors from cache, we were ignoring
8237 the annotations -- so for example we were reading in bridge-purpose
8238 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
8239 - When we decided to send a 503 response to a request for servers, we
8240 were then also sending the server descriptors: this defeats the
8241 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
8244 - Bridge relays now behave like clients with respect to time
8245 intervals for downloading new consensus documents -- otherwise they
8246 stand out. Bridge users now wait until the end of the interval,
8247 so their bridge relay will be sure to have a new consensus document.
8248 - Three new config options (AlternateDirAuthority,
8249 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
8250 user selectively replace the default directory authorities by type,
8251 rather than the all-or-nothing replacement that DirServer offers.
8252 - Tor can now be configured to read a GeoIP file from disk in one
8253 of two formats. This can be used by controllers to map IP addresses
8254 to countries. Eventually, it may support exit-by-country.
8255 - When possible, bridge relays remember which countries users
8256 are coming from, and report aggregate information in their
8257 extra-info documents, so that the bridge authorities can learn
8258 where Tor is blocked.
8259 - Bridge directory authorities now do reachability testing on the
8260 bridges they know. They provide router status summaries to the
8261 controller via "getinfo ns/purpose/bridge", and also dump summaries
8262 to a file periodically.
8263 - Stop fetching directory info so aggressively if your DirPort is
8264 on but your ORPort is off; stop fetching v2 dir info entirely.
8265 You can override these choices with the new FetchDirInfoEarly
8269 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
8270 consensus documents when there are too many relays at a single
8271 IP address. Now clear it in v2 network status documents too, and
8272 also clear it in routerinfo_t when the relay is no longer listed
8273 in the relevant networkstatus document.
8274 - Don't crash if we get an unexpected value for the
8275 PublishServerDescriptor config option. Reported by Matt Edman;
8276 bugfix on 0.2.0.9-alpha.
8277 - Our new v2 hidden service descriptor format allows descriptors
8278 that have no introduction points. But Tor crashed when we tried
8279 to build a descriptor with no intro points (and it would have
8280 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
8282 - Fix building with dmalloc 5.5.2 with glibc.
8283 - Reject uploaded descriptors and extrainfo documents if they're
8284 huge. Otherwise we'll cache them all over the network and it'll
8285 clog everything up. Reported by Aljosha Judmayer.
8286 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
8287 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
8288 - When the DANGEROUS_VERSION controller status event told us we're
8289 running an obsolete version, it used the string "OLD" to describe
8290 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
8291 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
8292 - If we can't expand our list of entry guards (e.g. because we're
8293 using bridges or we have StrictEntryNodes set), don't mark relays
8294 down when they fail a directory request. Otherwise we're too quick
8295 to mark all our entry points down. Bugfix on 0.1.2.x.
8296 - Fix handling of hex nicknames when answering controller requests for
8297 networkstatus by name, or when deciding whether to warn about unknown
8298 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
8299 - Fix a couple of hard-to-trigger autoconf problems that could result
8300 in really weird results on platforms whose sys/types.h files define
8301 nonstandard integer types. Bugfix on 0.1.2.x.
8302 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
8303 - Don't crash on name lookup when we have no current consensus. Fixes
8304 bug 538; bugfix on 0.2.0.x.
8305 - Only Tors that want to mirror the v2 directory info should
8306 create the "cached-status" directory in their datadir. (All Tors
8307 used to create it.) Bugfix on 0.2.0.9-alpha.
8308 - Directory authorities should only automatically download Extra Info
8309 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
8312 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
8313 consumers. (We already do this on HUP.)
8314 - Authorities and caches fetch the v2 networkstatus documents
8315 less often, now that v3 is encouraged.
8316 - Add a new config option BridgeRelay that specifies you want to
8317 be a bridge relay. Right now the only difference is that it makes
8318 you answer begin_dir requests, and it makes you cache dir info,
8319 even if your DirPort isn't on.
8320 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
8321 ask about source, timestamp of arrival, purpose, etc. We need
8322 something like this to help Vidalia not do GeoIP lookups on bridge
8324 - Allow multiple HashedControlPassword config lines, to support
8325 multiple controller passwords.
8326 - Authorities now decide whether they're authoritative for a given
8327 router based on the router's purpose.
8328 - New config options AuthDirBadDir and AuthDirListBadDirs for
8329 authorities to mark certain relays as "bad directories" in the
8330 networkstatus documents. Also supports the "!baddir" directive in
8331 the approved-routers file.
8334 Changes in version 0.2.0.12-alpha - 2007-11-16
8335 This twelfth development snapshot fixes some more build problems as
8336 well as a few minor bugs.
8339 - Make it build on OpenBSD again. Patch from tup.
8340 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
8341 package-building for Red Hat, OS X, etc.
8343 o Minor bugfixes (on 0.1.2.x):
8344 - Changing the ExitPolicyRejectPrivate setting should cause us to
8345 rebuild our server descriptor.
8347 o Minor bugfixes (on 0.2.0.x):
8348 - When we're lacking a consensus, don't try to perform rendezvous
8349 operations. Reported by Karsten Loesing.
8350 - Fix a small memory leak whenever we decide against using a
8351 newly picked entry guard. Reported by Mike Perry.
8352 - When authorities detected more than two relays running on the same
8353 IP address, they were clearing all the status flags but forgetting
8354 to clear the "hsdir" flag. So clients were being told that a
8355 given relay was the right choice for a v2 hsdir lookup, yet they
8356 never had its descriptor because it was marked as 'not running'
8358 - If we're trying to fetch a bridge descriptor and there's no way
8359 the bridge authority could help us (for example, we don't know
8360 a digest, or there is no bridge authority), don't be so eager to
8361 fall back to asking the bridge authority.
8362 - If we're using bridges or have strictentrynodes set, and our
8363 chosen exit is in the same family as all our bridges/entry guards,
8364 then be flexible about families.
8367 - When we negotiate a v2 link-layer connection (not yet implemented),
8368 accept RELAY_EARLY cells and turn them into RELAY cells if we've
8369 negotiated a v1 connection for their next step. Initial code for
8373 Changes in version 0.2.0.11-alpha - 2007-11-12
8374 This eleventh development snapshot fixes some build problems with
8375 the previous snapshot. It also includes a more secure-by-default exit
8376 policy for relays, fixes an enormous memory leak for exit relays, and
8377 fixes another bug where servers were falling out of the directory list.
8380 - Exit policies now reject connections that are addressed to a
8381 relay's public (external) IP address too, unless
8382 ExitPolicyRejectPrivate is turned off. We do this because too
8383 many relays are running nearby to services that trust them based
8384 on network address. Bugfix on 0.1.2.x.
8387 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
8388 on every successful resolve. Reported by Mike Perry; bugfix
8390 - On authorities, never downgrade to old router descriptors simply
8391 because they're listed in the consensus. This created a catch-22
8392 where we wouldn't list a new descriptor because there was an
8393 old one in the consensus, and we couldn't get the new one in the
8394 consensus because we wouldn't list it. Possible fix for bug 548.
8395 Also, this might cause bug 543 to appear on authorities; if so,
8396 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
8398 o Packaging fixes on 0.2.0.10-alpha:
8399 - We were including instructions about what to do with the
8400 src/config/fallback-consensus file, but we weren't actually
8401 including it in the tarball. Disable all of that for now.
8404 - Allow people to say PreferTunnelledDirConns rather than
8405 PreferTunneledDirConns, for those alternate-spellers out there.
8408 - Don't reevaluate all the information from our consensus document
8409 just because we've downloaded a v2 networkstatus that we intend
8410 to cache. Fixes bug 545; bugfix on 0.2.0.x.
8413 Changes in version 0.2.0.10-alpha - 2007-11-10
8414 This tenth development snapshot adds a third v3 directory authority
8415 run by Mike Perry, adds most of Karsten Loesing's new hidden service
8416 descriptor format, fixes a bad crash bug and new bridge bugs introduced
8417 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
8418 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
8419 addresses many more minor issues.
8421 o New directory authorities:
8422 - Set up ides (run by Mike Perry) as the third v3 directory authority.
8425 - Allow tunnelled directory connections to ask for an encrypted
8426 "begin_dir" connection or an anonymized "uses a full Tor circuit"
8427 connection independently. Now we can make anonymized begin_dir
8428 connections for (e.g.) more secure hidden service posting and
8430 - More progress on proposal 114: code from Karsten Loesing to
8431 implement new hidden service descriptor format.
8432 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
8433 accommodate the growing number of servers that use the default
8434 and are reaching it.
8435 - Directory authorities use a new formula for selecting which nodes
8436 to advertise as Guards: they must be in the top 7/8 in terms of
8437 how long we have known about them, and above the median of those
8438 nodes in terms of weighted fractional uptime.
8439 - Make "not enough dir info yet" warnings describe *why* Tor feels
8440 it doesn't have enough directory info yet.
8443 - Stop servers from crashing if they set a Family option (or
8444 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
8446 - Make bridge users work again -- the move to v3 directories in
8447 0.2.0.9-alpha had introduced a number of bugs that made bridges
8448 no longer work for clients.
8449 - When the clock jumps forward a lot, do not allow the bandwidth
8450 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
8452 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
8453 - When the consensus lists a router descriptor that we previously were
8454 mirroring, but that we considered non-canonical, reload the
8455 descriptor as canonical. This fixes bug 543 where Tor servers
8456 would start complaining after a few days that they don't have
8457 enough directory information to build a circuit.
8458 - Consider replacing the current consensus when certificates arrive
8459 that make the pending consensus valid. Previously, we were only
8460 considering replacement when the new certs _didn't_ help.
8461 - Fix an assert error on startup if we didn't already have the
8462 consensus and certs cached in our datadirectory: we were caching
8463 the consensus in consensus_waiting_for_certs but then free'ing it
8465 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
8466 Request) if we need more v3 certs but we've already got pending
8467 requests for all of them.
8468 - Correctly back off from failing certificate downloads. Fixes
8470 - Authorities don't vote on the Running flag if they have been running
8471 for less than 30 minutes themselves. Fixes bug 547, where a newly
8472 started authority would vote that everyone was down.
8475 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
8476 it, it had no AES, and it hasn't seen any security patches since
8480 - Clients now hold circuitless TLS connections open for 1.5 times
8481 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
8482 rebuild a new circuit over them within that timeframe. Previously,
8483 they held them open only for KeepalivePeriod (5 minutes).
8484 - Use "If-Modified-Since" to avoid retrieving consensus
8485 networkstatuses that we already have.
8486 - When we have no consensus, check FallbackNetworkstatusFile (defaults
8487 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
8488 we start knowing some directory caches.
8489 - When we receive a consensus from the future, warn about skew.
8490 - Improve skew reporting: try to give the user a better log message
8491 about how skewed they are, and how much this matters.
8492 - When we have a certificate for an authority, believe that
8493 certificate's claims about the authority's IP address.
8494 - New --quiet command-line option to suppress the default console log.
8495 Good in combination with --hash-password.
8496 - Authorities send back an X-Descriptor-Not-New header in response to
8497 an accepted-but-discarded descriptor upload. Partially implements
8499 - Make the log message for "tls error. breaking." more useful.
8500 - Better log messages about certificate downloads, to attempt to
8501 track down the second incarnation of bug 546.
8503 o Minor features (bridges):
8504 - If bridge users set UpdateBridgesFromAuthority, but the digest
8505 they ask for is a 404 from the bridge authority, they now fall
8506 back to trying the bridge directly.
8507 - Bridges now use begin_dir to publish their server descriptor to
8508 the bridge authority, even when they haven't set TunnelDirConns.
8510 o Minor features (controller):
8511 - When reporting clock skew, and we know that the clock is _at least
8512 as skewed_ as some value, but we don't know the actual value,
8513 report the value as a "minimum skew."
8516 - Update linux-tor-prio.sh script to allow QoS based on the uid of
8517 the Tor process. Patch from Marco Bonetti with tweaks from Mike
8521 - Refuse to start if both ORPort and UseBridges are set. Bugfix
8522 on 0.2.0.x, suggested by Matt Edman.
8523 - Don't stop fetching descriptors when FetchUselessDescriptors is
8524 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
8525 reported by tup and ioerror.
8526 - Better log message on vote from unknown authority.
8527 - Don't log "Launching 0 request for 0 router" message.
8529 o Minor bugfixes (memory leaks):
8530 - Stop leaking memory every time we parse a v3 certificate. Bugfix
8532 - Stop leaking memory every time we load a v3 certificate. Bugfix
8533 on 0.2.0.1-alpha. Fixes bug 536.
8534 - Stop leaking a cached networkstatus on exit. Bugfix on
8536 - Stop leaking voter information every time we free a consensus.
8537 Bugfix on 0.2.0.3-alpha.
8538 - Stop leaking signed data every time we check a voter signature.
8539 Bugfix on 0.2.0.3-alpha.
8540 - Stop leaking a signature every time we fail to parse a consensus or
8541 a vote. Bugfix on 0.2.0.3-alpha.
8542 - Stop leaking v2_download_status_map on shutdown. Bugfix on
8544 - Stop leaking conn->nickname every time we make a connection to a
8545 Tor relay without knowing its expected identity digest (e.g. when
8546 using bridges). Bugfix on 0.2.0.3-alpha.
8548 - Minor bugfixes (portability):
8549 - Run correctly on platforms where rlim_t is larger than unsigned
8550 long, and/or where the real limit for number of open files is
8551 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
8552 particular, these may be needed for OS X 10.5.
8555 Changes in version 0.1.2.18 - 2007-10-28
8556 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
8557 hidden service introduction that were causing huge delays, and a big
8558 bug that was causing some servers to disappear from the network status
8559 lists for a few hours each day.
8561 o Major bugfixes (crashes):
8562 - If a connection is shut down abruptly because of something that
8563 happened inside connection_flushed_some(), do not call
8564 connection_finished_flushing(). Should fix bug 451:
8565 "connection_stop_writing: Assertion conn->write_event failed"
8566 Bugfix on 0.1.2.7-alpha.
8567 - Fix possible segfaults in functions called from
8568 rend_process_relay_cell().
8570 o Major bugfixes (hidden services):
8571 - Hidden services were choosing introduction points uniquely by
8572 hexdigest, but when constructing the hidden service descriptor
8573 they merely wrote the (potentially ambiguous) nickname.
8574 - Clients now use the v2 intro format for hidden service
8575 connections: they specify their chosen rendezvous point by identity
8576 digest rather than by (potentially ambiguous) nickname. These
8577 changes could speed up hidden service connections dramatically.
8579 o Major bugfixes (other):
8580 - Stop publishing a new server descriptor just because we get a
8581 HUP signal. This led (in a roundabout way) to some servers getting
8582 dropped from the networkstatus lists for a few hours each day.
8583 - When looking for a circuit to cannibalize, consider family as well
8584 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8585 circuit cannibalization).
8586 - When a router wasn't listed in a new networkstatus, we were leaving
8587 the flags for that router alone -- meaning it remained Named,
8588 Running, etc -- even though absence from the networkstatus means
8589 that it shouldn't be considered to exist at all anymore. Now we
8590 clear all the flags for routers that fall out of the networkstatus
8591 consensus. Fixes bug 529.
8594 - Don't try to access (or alter) the state file when running
8595 --list-fingerprint or --verify-config or --hash-password. Resolves
8597 - When generating information telling us how to extend to a given
8598 router, do not try to include the nickname if it is
8599 absent. Resolves bug 467.
8600 - Fix a user-triggerable segfault in expand_filename(). (There isn't
8601 a way to trigger this remotely.)
8602 - When sending a status event to the controller telling it that an
8603 OR address is reachable, set the port correctly. (Previously we
8604 were reporting the dir port.)
8605 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8606 command. Bugfix on 0.1.2.17.
8607 - When loading bandwidth history, do not believe any information in
8608 the future. Fixes bug 434.
8609 - When loading entry guard information, do not believe any information
8611 - When we have our clock set far in the future and generate an
8612 onion key, then re-set our clock to be correct, we should not stop
8613 the onion key from getting rotated.
8614 - On some platforms, accept() can return a broken address. Detect
8615 this more quietly, and deal accordingly. Fixes bug 483.
8616 - It's not actually an error to find a non-pending entry in the DNS
8617 cache when canceling a pending resolve. Don't log unless stuff
8618 is fishy. Resolves bug 463.
8619 - Don't reset trusted dir server list when we set a configuration
8620 option. Patch from Robert Hogan.
8621 - Don't try to create the datadir when running --verify-config or
8622 --hash-password. Resolves bug 540.
8625 Changes in version 0.2.0.9-alpha - 2007-10-24
8626 This ninth development snapshot switches clients to the new v3 directory
8627 system; allows servers to be listed in the network status even when they
8628 have the same nickname as a registered server; and fixes many other
8629 bugs including a big one that was causing some servers to disappear
8630 from the network status lists for a few hours each day.
8632 o Major features (directory system):
8633 - Clients now download v3 consensus networkstatus documents instead
8634 of v2 networkstatus documents. Clients and caches now base their
8635 opinions about routers on these consensus documents. Clients only
8636 download router descriptors listed in the consensus.
8637 - Authorities now list servers who have the same nickname as
8638 a different named server, but list them with a new flag,
8639 "Unnamed". Now we can list servers that happen to pick the same
8640 nickname as a server that registered two years ago and then
8641 disappeared. Partially implements proposal 122.
8642 - If the consensus lists a router as "Unnamed", the name is assigned
8643 to a different router: do not identify the router by that name.
8644 Partially implements proposal 122.
8645 - Authorities can now come to a consensus on which method to use to
8646 compute the consensus. This gives us forward compatibility.
8649 - Stop publishing a new server descriptor just because we HUP or
8650 when we find our DirPort to be reachable but won't actually publish
8651 it. New descriptors without any real changes are dropped by the
8652 authorities, and can screw up our "publish every 18 hours" schedule.
8654 - When a router wasn't listed in a new networkstatus, we were leaving
8655 the flags for that router alone -- meaning it remained Named,
8656 Running, etc -- even though absence from the networkstatus means
8657 that it shouldn't be considered to exist at all anymore. Now we
8658 clear all the flags for routers that fall out of the networkstatus
8659 consensus. Fixes bug 529; bugfix on 0.1.2.x.
8660 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
8661 extrainfo documents and then discard them immediately for not
8662 matching the latest router. Bugfix on 0.2.0.1-alpha.
8664 o Minor features (v3 directory protocol):
8665 - Allow tor-gencert to generate a new certificate without replacing
8667 - Allow certificates to include an address.
8668 - When we change our directory-cache settings, reschedule all voting
8669 and download operations.
8670 - Reattempt certificate downloads immediately on failure, as long as
8671 we haven't failed a threshold number of times yet.
8672 - Delay retrying consensus downloads while we're downloading
8673 certificates to verify the one we just got. Also, count getting a
8674 consensus that we already have (or one that isn't valid) as a failure,
8675 and count failing to get the certificates after 20 minutes as a
8677 - Build circuits and download descriptors even if our consensus is a
8678 little expired. (This feature will go away once authorities are
8681 o Minor features (router descriptor cache):
8682 - If we find a cached-routers file that's been sitting around for more
8683 than 28 days unmodified, then most likely it's a leftover from
8684 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
8686 - When we (as a cache) download a descriptor because it was listed
8687 in a consensus, remember when the consensus was supposed to expire,
8688 and don't expire the descriptor until then.
8690 o Minor features (performance):
8691 - Call routerlist_remove_old_routers() much less often. This should
8692 speed startup, especially on directory caches.
8693 - Don't try to launch new descriptor downloads quite so often when we
8694 already have enough directory information to build circuits.
8695 - Base64 decoding was actually showing up on our profile when parsing
8696 the initial descriptor file; switch to an in-process all-at-once
8697 implementation that's about 3.5x times faster than calling out to
8700 o Minor features (compilation):
8701 - Detect non-ASCII platforms (if any still exist) and refuse to
8702 build there: some of our code assumes that 'A' is 65 and so on.
8704 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
8705 - Make the "next period" votes into "current period" votes immediately
8706 after publishing the consensus; avoid a heisenbug that made them
8707 stick around indefinitely.
8708 - When we discard a vote as a duplicate, do not report this as
8710 - Treat missing v3 keys or certificates as an error when running as a
8711 v3 directory authority.
8712 - When we're configured to be a v3 authority, but we're only listed
8713 as a non-v3 authority in our DirServer line for ourself, correct
8715 - If an authority doesn't have a qualified hostname, just put
8716 its address in the vote. This fixes the problem where we referred to
8717 "moria on moria:9031."
8718 - Distinguish between detached signatures for the wrong period, and
8719 detached signatures for a divergent vote.
8720 - Fix a small memory leak when computing a consensus.
8721 - When there's no concensus, we were forming a vote every 30
8722 minutes, but writing the "valid-after" line in our vote based
8723 on our configured V3AuthVotingInterval: so unless the intervals
8724 matched up, we immediately rejected our own vote because it didn't
8725 start at the voting interval that caused us to construct a vote.
8727 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
8728 - Delete unverified-consensus when the real consensus is set.
8729 - Consider retrying a consensus networkstatus fetch immediately
8730 after one fails: don't wait 60 seconds to notice.
8731 - When fetching a consensus as a cache, wait until a newer consensus
8732 should exist before trying to replace the current one.
8733 - Use a more forgiving schedule for retrying failed consensus
8734 downloads than for other types.
8736 o Minor bugfixes (other directory issues):
8737 - Correct the implementation of "download votes by digest." Bugfix on
8739 - Authorities no longer send back "400 you're unreachable please fix
8740 it" errors to Tor servers that aren't online all the time. We're
8741 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
8743 o Minor bugfixes (controller):
8744 - Don't reset trusted dir server list when we set a configuration
8745 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
8746 - Respond to INT and TERM SIGNAL commands before we execute the
8747 signal, in case the signal shuts us down. We had a patch in
8748 0.1.2.1-alpha that tried to do this by queueing the response on
8749 the connection's buffer before shutting down, but that really
8750 isn't the same thing at all. Bug located by Matt Edman.
8752 o Minor bugfixes (misc):
8753 - Correctly check for bad options to the "PublishServerDescriptor"
8754 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
8755 - Stop leaking memory on failing case of base32_decode, and make
8756 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
8757 - Don't try to download extrainfo documents when we're trying to
8758 fetch enough directory info to build a circuit: having enough
8759 info should get priority. Bugfix on 0.2.0.x.
8760 - Don't complain that "your server has not managed to confirm that its
8761 ports are reachable" if we haven't been able to build any circuits
8762 yet. Bug found by spending four hours without a v3 consensus. Bugfix
8764 - Detect the reason for failing to mmap a descriptor file we just
8765 wrote, and give a more useful log message. Fixes bug 533. Bugfix
8768 o Code simplifications and refactoring:
8769 - Remove support for the old bw_accounting file: we've been storing
8770 bandwidth accounting information in the state file since
8771 0.1.2.5-alpha. This may result in bandwidth accounting errors
8772 if you try to upgrade from 0.1.1.x or earlier, or if you try to
8773 downgrade to 0.1.1.x or earlier.
8774 - New convenience code to locate a file within the DataDirectory.
8775 - Move non-authority functionality out of dirvote.c.
8776 - Refactor the arguments for router_pick_{directory_|trusteddir}server
8777 so that they all take the same named flags.
8780 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
8781 Unix users an easy way to script their Tor process (e.g. by
8782 adjusting bandwidth based on the time of the day).
8785 Changes in version 0.2.0.8-alpha - 2007-10-12
8786 This eighth development snapshot fixes a crash bug that's been bothering
8787 us since February 2007, lets bridge authorities store a list of bridge
8788 descriptors they've seen, gets v3 directory voting closer to working,
8789 starts caching v3 directory consensus documents on directory mirrors,
8790 and fixes a variety of smaller issues including some minor memory leaks.
8792 o Major features (router descriptor cache):
8793 - Store routers in a file called cached-descriptors instead of in
8794 cached-routers. Initialize cached-descriptors from cached-routers
8795 if the old format is around. The new format allows us to store
8796 annotations along with descriptors.
8797 - Use annotations to record the time we received each descriptor, its
8798 source, and its purpose.
8799 - Disable the SETROUTERPURPOSE controller command: it is now
8801 - Controllers should now specify cache=no or cache=yes when using
8802 the +POSTDESCRIPTOR command.
8803 - Bridge authorities now write bridge descriptors to disk, meaning
8804 we can export them to other programs and begin distributing them
8807 o Major features (directory authorities):
8808 - When a v3 authority is missing votes or signatures, it now tries
8810 - Directory authorities track weighted fractional uptime as well as
8811 weighted mean-time-between failures. WFU is suitable for deciding
8812 whether a node is "usually up", while MTBF is suitable for deciding
8813 whether a node is "likely to stay up." We need both, because
8814 "usually up" is a good requirement for guards, while "likely to
8815 stay up" is a good requirement for long-lived connections.
8817 o Major features (v3 directory system):
8818 - Caches now download v3 network status documents as needed,
8819 and download the descriptors listed in them.
8820 - All hosts now attempt to download and keep fresh v3 authority
8821 certificates, and re-attempt after failures.
8822 - More internal-consistency checks for vote parsing.
8824 o Major bugfixes (crashes):
8825 - If a connection is shut down abruptly because of something that
8826 happened inside connection_flushed_some(), do not call
8827 connection_finished_flushing(). Should fix bug 451. Bugfix on
8830 o Major bugfixes (performance):
8831 - Fix really bad O(n^2) performance when parsing a long list of
8832 routers: Instead of searching the entire list for an "extra-info "
8833 string which usually wasn't there, once for every routerinfo
8834 we read, just scan lines forward until we find one we like.
8836 - When we add data to a write buffer in response to the data on that
8837 write buffer getting low because of a flush, do not consider the
8838 newly added data as a candidate for immediate flushing, but rather
8839 make it wait until the next round of writing. Otherwise, we flush
8840 and refill recursively, and a single greedy TLS connection can
8841 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
8843 o Minor features (v3 authority system):
8844 - Add more ways for tools to download the votes that lead to the
8846 - Send a 503 when low on bandwidth and a vote, consensus, or
8847 certificate is requested.
8848 - If-modified-since is now implemented properly for all kinds of
8849 certificate requests.
8851 o Minor bugfixes (network statuses):
8852 - Tweak the implementation of proposal 109 slightly: allow at most
8853 two Tor servers on the same IP address, except if it's the location
8854 of a directory authority, in which case allow five. Bugfix on
8857 o Minor bugfixes (controller):
8858 - When sending a status event to the controller telling it that an
8859 OR address is reachable, set the port correctly. (Previously we
8860 were reporting the dir port.) Bugfix on 0.1.2.x.
8862 o Minor bugfixes (v3 directory system):
8863 - Fix logic to look up a cert by its signing key digest. Bugfix on
8865 - Only change the reply to a vote to "OK" if it's not already
8866 set. This gets rid of annoying "400 OK" log messages, which may
8867 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
8868 - When we get a valid consensus, recompute the voting schedule.
8869 - Base the valid-after time of a vote on the consensus voting
8870 schedule, not on our preferred schedule.
8871 - Make the return values and messages from signature uploads and
8872 downloads more sensible.
8873 - Fix a memory leak when serving votes and consensus documents, and
8874 another when serving certificates.
8876 o Minor bugfixes (performance):
8877 - Use a slightly simpler string hashing algorithm (copying Python's
8878 instead of Java's) and optimize our digest hashing algorithm to take
8879 advantage of 64-bit platforms and to remove some possibly-costly
8881 - Fix a minor memory leak whenever we parse guards from our state
8882 file. Bugfix on 0.2.0.7-alpha.
8883 - Fix a minor memory leak whenever we write out a file. Bugfix on
8885 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8886 command. Bugfix on 0.2.0.5-alpha.
8888 o Minor bugfixes (portability):
8889 - On some platforms, accept() can return a broken address. Detect
8890 this more quietly, and deal accordingly. Fixes bug 483.
8891 - Stop calling tor_strlower() on uninitialized memory in some cases.
8892 Bugfix in 0.2.0.7-alpha.
8894 o Minor bugfixes (usability):
8895 - Treat some 403 responses from directory servers as INFO rather than
8896 WARN-severity events.
8897 - It's not actually an error to find a non-pending entry in the DNS
8898 cache when canceling a pending resolve. Don't log unless stuff is
8899 fishy. Resolves bug 463.
8901 o Minor bugfixes (anonymity):
8902 - Never report that we've used more bandwidth than we're willing to
8903 relay: it leaks how much non-relay traffic we're using. Resolves
8905 - When looking for a circuit to cannibalize, consider family as well
8906 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8907 circuit cannibalization).
8909 o Code simplifications and refactoring:
8910 - Make a bunch of functions static. Remove some dead code.
8911 - Pull out about a third of the really big routerlist.c; put it in a
8912 new module, networkstatus.c.
8913 - Merge the extra fields in local_routerstatus_t back into
8914 routerstatus_t: we used to need one routerstatus_t for each
8915 authority's opinion, plus a local_routerstatus_t for the locally
8916 computed consensus opinion. To save space, we put the locally
8917 modified fields into local_routerstatus_t, and only the common
8918 stuff into routerstatus_t. But once v3 directories are in use,
8919 clients and caches will no longer need to hold authority opinions;
8920 thus, the rationale for keeping the types separate is now gone.
8921 - Make the code used to reschedule and reattempt downloads more
8923 - Turn all 'Are we a directory server/mirror?' logic into a call to
8925 - Remove the code to generate the oldest (v1) directory format.
8926 The code has been disabled since 0.2.0.5-alpha.
8929 Changes in version 0.2.0.7-alpha - 2007-09-21
8930 This seventh development snapshot makes bridges work again, makes bridge
8931 authorities work for the first time, fixes two huge performance flaws
8932 in hidden services, and fixes a variety of minor issues.
8934 o New directory authorities:
8935 - Set up moria1 and tor26 as the first v3 directory authorities. See
8936 doc/spec/dir-spec.txt for details on the new directory design.
8938 o Major bugfixes (crashes):
8939 - Fix possible segfaults in functions called from
8940 rend_process_relay_cell(). Bugfix on 0.1.2.x.
8942 o Major bugfixes (bridges):
8943 - Fix a bug that made servers send a "404 Not found" in response to
8944 attempts to fetch their server descriptor. This caused Tor servers
8945 to take many minutes to establish reachability for their DirPort,
8946 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
8947 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
8948 users configure that and specify a bridge with an identity
8949 fingerprint, now they will lookup the bridge descriptor at the
8950 default bridge authority via a one-hop tunnel, but once circuits
8951 are established they will switch to a three-hop tunnel for later
8952 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
8954 o Major bugfixes (hidden services):
8955 - Hidden services were choosing introduction points uniquely by
8956 hexdigest, but when constructing the hidden service descriptor
8957 they merely wrote the (potentially ambiguous) nickname.
8958 - Clients now use the v2 intro format for hidden service
8959 connections: they specify their chosen rendezvous point by identity
8960 digest rather than by (potentially ambiguous) nickname. Both
8961 are bugfixes on 0.1.2.x, and they could speed up hidden service
8962 connections dramatically. Thanks to Karsten Loesing.
8964 o Minor features (security):
8965 - As a client, do not believe any server that tells us that an
8966 address maps to an internal address space.
8967 - Make it possible to enable HashedControlPassword and
8968 CookieAuthentication at the same time.
8970 o Minor features (guard nodes):
8971 - Tag every guard node in our state file with the version that
8972 we believe added it, or with our own version if we add it. This way,
8973 if a user temporarily runs an old version of Tor and then switches
8974 back to a new one, she doesn't automatically lose her guards.
8976 o Minor features (speed):
8977 - When implementing AES counter mode, update only the portions of the
8978 counter buffer that need to change, and don't keep separate
8979 network-order and host-order counters when they are the same (i.e.,
8980 on big-endian hosts.)
8982 o Minor features (controller):
8983 - Accept LF instead of CRLF on controller, since some software has a
8984 hard time generating real Internet newlines.
8985 - Add GETINFO values for the server status events
8986 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
8990 - Routers no longer include bandwidth-history lines in their
8991 descriptors; this information is already available in extra-info
8992 documents, and including it in router descriptors took up 60%
8993 (!) of compressed router descriptor downloads. Completes
8994 implementation of proposal 104.
8995 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
8996 and TorControl.py, as they use the old v0 controller protocol,
8997 and are obsoleted by TorFlow anyway.
8998 - Drop support for v1 rendezvous descriptors, since we never used
8999 them anyway, and the code has probably rotted by now. Based on
9000 patch from Karsten Loesing.
9001 - On OSX, stop warning the user that kqueue support in libevent is
9002 "experimental", since it seems to have worked fine for ages.
9005 - When generating information telling us how to extend to a given
9006 router, do not try to include the nickname if it is absent. Fixes
9007 bug 467. Bugfix on 0.2.0.3-alpha.
9008 - Fix a user-triggerable (but not remotely-triggerable) segfault
9009 in expand_filename(). Bugfix on 0.1.2.x.
9010 - Fix a memory leak when freeing incomplete requests from DNSPort.
9011 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
9012 - Don't try to access (or alter) the state file when running
9013 --list-fingerprint or --verify-config or --hash-password. (Resolves
9014 bug 499.) Bugfix on 0.1.2.x.
9015 - Servers used to decline to publish their DirPort if their
9016 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
9017 were below a threshold. Now they only look at BandwidthRate and
9018 RelayBandwidthRate. Bugfix on 0.1.2.x.
9019 - Remove an optimization in the AES counter-mode code that assumed
9020 that the counter never exceeded 2^68. When the counter can be set
9021 arbitrarily as an IV (as it is by Karsten's new hidden services
9022 code), this assumption no longer holds. Bugfix on 0.1.2.x.
9023 - Resume listing "AUTHORITY" flag for authorities in network status.
9024 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
9026 o Code simplifications and refactoring:
9027 - Revamp file-writing logic so we don't need to have the entire
9028 contents of a file in memory at once before we write to disk. Tor,
9030 - Turn "descriptor store" into a full-fledged type.
9031 - Move all NT services code into a separate source file.
9032 - Unify all code that computes medians, percentile elements, etc.
9033 - Get rid of a needless malloc when parsing address policies.
9036 Changes in version 0.1.2.17 - 2007-08-30
9037 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
9038 X bundles. Vidalia 0.0.14 makes authentication required for the
9039 ControlPort in the default configuration, which addresses important
9040 security risks. Everybody who uses Vidalia (or another controller)
9043 In addition, this Tor update fixes major load balancing problems with
9044 path selection, which should speed things up a lot once many people
9047 o Major bugfixes (security):
9048 - We removed support for the old (v0) control protocol. It has been
9049 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
9050 become more of a headache than it's worth.
9052 o Major bugfixes (load balancing):
9053 - When choosing nodes for non-guard positions, weight guards
9054 proportionally less, since they already have enough load. Patch
9056 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
9057 will allow fast Tor servers to get more attention.
9058 - When we're upgrading from an old Tor version, forget our current
9059 guards and pick new ones according to the new weightings. These
9060 three load balancing patches could raise effective network capacity
9061 by a factor of four. Thanks to Mike Perry for measurements.
9063 o Major bugfixes (stream expiration):
9064 - Expire not-yet-successful application streams in all cases if
9065 they've been around longer than SocksTimeout. Right now there are
9066 some cases where the stream will live forever, demanding a new
9067 circuit every 15 seconds. Fixes bug 454; reported by lodger.
9069 o Minor features (controller):
9070 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
9071 is valid before any authentication has been received. It tells
9072 a controller what kind of authentication is expected, and what
9073 protocol is spoken. Implements proposal 119.
9075 o Minor bugfixes (performance):
9076 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
9077 greatly speeding up loading cached-routers from disk on startup.
9078 - Disable sentinel-based debugging for buffer code: we squashed all
9079 the bugs that this was supposed to detect a long time ago, and now
9080 its only effect is to change our buffer sizes from nice powers of
9081 two (which platform mallocs tend to like) to values slightly over
9082 powers of two (which make some platform mallocs sad).
9084 o Minor bugfixes (misc):
9085 - If exit bandwidth ever exceeds one third of total bandwidth, then
9086 use the correct formula to weight exit nodes when choosing paths.
9087 Based on patch from Mike Perry.
9088 - Choose perfectly fairly among routers when choosing by bandwidth and
9089 weighting by fraction of bandwidth provided by exits. Previously, we
9090 would choose with only approximate fairness, and correct ourselves
9091 if we ran off the end of the list.
9092 - If we require CookieAuthentication but we fail to write the
9093 cookie file, we would warn but not exit, and end up in a state
9094 where no controller could authenticate. Now we exit.
9095 - If we require CookieAuthentication, stop generating a new cookie
9096 every time we change any piece of our config.
9097 - Refuse to start with certain directory authority keys, and
9098 encourage people using them to stop.
9099 - Terminate multi-line control events properly. Original patch
9101 - Fix a minor memory leak when we fail to find enough suitable
9102 servers to choose a circuit.
9103 - Stop leaking part of the descriptor when we run into a particularly
9104 unparseable piece of it.
9107 Changes in version 0.2.0.6-alpha - 2007-08-26
9108 This sixth development snapshot features a new Vidalia version in the
9109 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
9110 the ControlPort in the default configuration, which addresses important
9113 In addition, this snapshot fixes major load balancing problems
9114 with path selection, which should speed things up a lot once many
9115 people have upgraded. The directory authorities also use a new
9116 mean-time-between-failure approach to tracking which servers are stable,
9117 rather than just looking at the most recent uptime.
9119 o New directory authorities:
9120 - Set up Tonga as the default bridge directory authority.
9123 - Directory authorities now track servers by weighted
9124 mean-times-between-failures. When we have 4 or more days of data,
9125 use measured MTBF rather than declared uptime to decide whether
9126 to call a router Stable. Implements proposal 108.
9128 o Major bugfixes (load balancing):
9129 - When choosing nodes for non-guard positions, weight guards
9130 proportionally less, since they already have enough load. Patch
9132 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
9133 will allow fast Tor servers to get more attention.
9134 - When we're upgrading from an old Tor version, forget our current
9135 guards and pick new ones according to the new weightings. These
9136 three load balancing patches could raise effective network capacity
9137 by a factor of four. Thanks to Mike Perry for measurements.
9139 o Major bugfixes (descriptor parsing):
9140 - Handle unexpected whitespace better in malformed descriptors. Bug
9141 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
9144 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
9145 GETINFO for Torstat to use until it can switch to using extrainfos.
9146 - Optionally (if built with -DEXPORTMALLINFO) export the output
9147 of mallinfo via http, as tor/mallinfo.txt. Only accessible
9151 - Do not intermix bridge routers with controller-added
9152 routers. (Bugfix on 0.2.0.x)
9153 - Do not fail with an assert when accept() returns an unexpected
9154 address family. Addresses but does not wholly fix bug 483. (Bugfix
9156 - Let directory authorities startup even when they can't generate
9157 a descriptor immediately, e.g. because they don't know their
9159 - Stop putting the authentication cookie in a file called "0"
9160 in your working directory if you don't specify anything for the
9161 new CookieAuthFile option. Reported by Matt Edman.
9162 - Make it possible to read the PROTOCOLINFO response in a way that
9163 conforms to our control-spec. Reported by Matt Edman.
9164 - Fix a minor memory leak when we fail to find enough suitable
9165 servers to choose a circuit. Bugfix on 0.1.2.x.
9166 - Stop leaking part of the descriptor when we run into a particularly
9167 unparseable piece of it. Bugfix on 0.1.2.x.
9168 - Unmap the extrainfo cache file on exit.
9171 Changes in version 0.2.0.5-alpha - 2007-08-19
9172 This fifth development snapshot fixes compilation on Windows again;
9173 fixes an obnoxious client-side bug that slowed things down and put
9174 extra load on the network; gets us closer to using the v3 directory
9175 voting scheme; makes it easier for Tor controllers to use cookie-based
9176 authentication; and fixes a variety of other bugs.
9179 - Version 1 directories are no longer generated in full. Instead,
9180 authorities generate and serve "stub" v1 directories that list
9181 no servers. This will stop Tor versions 0.1.0.x and earlier from
9182 working, but (for security reasons) nobody should be running those
9185 o Major bugfixes (compilation, 0.2.0.x):
9186 - Try to fix Win32 compilation again: improve checking for IPv6 types.
9187 - Try to fix MSVC compilation: build correctly on platforms that do
9188 not define s6_addr16 or s6_addr32.
9189 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
9192 o Major bugfixes (stream expiration):
9193 - Expire not-yet-successful application streams in all cases if
9194 they've been around longer than SocksTimeout. Right now there are
9195 some cases where the stream will live forever, demanding a new
9196 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
9199 o Minor features (directory servers):
9200 - When somebody requests a list of statuses or servers, and we have
9201 none of those, return a 404 rather than an empty 200.
9203 o Minor features (directory voting):
9204 - Store v3 consensus status consensuses on disk, and reload them
9207 o Minor features (security):
9208 - Warn about unsafe ControlPort configurations.
9209 - Refuse to start with certain directory authority keys, and
9210 encourage people using them to stop.
9212 o Minor features (controller):
9213 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
9214 is valid before any authentication has been received. It tells
9215 a controller what kind of authentication is expected, and what
9216 protocol is spoken. Implements proposal 119.
9217 - New config option CookieAuthFile to choose a new location for the
9218 cookie authentication file, and config option
9219 CookieAuthFileGroupReadable to make it group-readable.
9221 o Minor features (unit testing):
9222 - Add command-line arguments to unit-test executable so that we can
9223 invoke any chosen test from the command line rather than having
9224 to run the whole test suite at once; and so that we can turn on
9225 logging for the unit tests.
9227 o Minor bugfixes (on 0.1.2.x):
9228 - If we require CookieAuthentication but we fail to write the
9229 cookie file, we would warn but not exit, and end up in a state
9230 where no controller could authenticate. Now we exit.
9231 - If we require CookieAuthentication, stop generating a new cookie
9232 every time we change any piece of our config.
9233 - When loading bandwidth history, do not believe any information in
9234 the future. Fixes bug 434.
9235 - When loading entry guard information, do not believe any information
9237 - When we have our clock set far in the future and generate an
9238 onion key, then re-set our clock to be correct, we should not stop
9239 the onion key from getting rotated.
9240 - Clean up torrc sample config file.
9241 - Do not automatically run configure from autogen.sh. This
9242 non-standard behavior tended to annoy people who have built other
9245 o Minor bugfixes (on 0.2.0.x):
9246 - Fix a bug with AutomapHostsOnResolve that would always cause
9247 the second request to fail. Bug reported by Kate. Bugfix on
9249 - Fix a bug in ADDRMAP controller replies that would sometimes
9250 try to print a NULL. Patch from tup.
9251 - Read v3 directory authority keys from the right location.
9252 - Numerous bugfixes to directory voting code.
9255 Changes in version 0.1.2.16 - 2007-08-01
9256 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
9257 remote attacker in certain situations to rewrite the user's torrc
9258 configuration file. This can completely compromise anonymity of users
9259 in most configurations, including those running the Vidalia bundles,
9260 TorK, etc. Or worse.
9262 o Major security fixes:
9263 - Close immediately after missing authentication on control port;
9264 do not allow multiple authentication attempts.
9267 Changes in version 0.2.0.4-alpha - 2007-08-01
9268 This fourth development snapshot fixes a critical security vulnerability
9269 for most users, specifically those running Vidalia, TorK, etc. Everybody
9270 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
9272 o Major security fixes:
9273 - Close immediately after missing authentication on control port;
9274 do not allow multiple authentication attempts.
9276 o Major bugfixes (compilation):
9277 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
9280 o Minor features (performance):
9281 - Be even more aggressive about releasing RAM from small
9282 empty buffers. Thanks to our free-list code, this shouldn't be too
9283 performance-intensive.
9284 - Disable sentinel-based debugging for buffer code: we squashed all
9285 the bugs that this was supposed to detect a long time ago, and
9286 now its only effect is to change our buffer sizes from nice
9287 powers of two (which platform mallocs tend to like) to values
9288 slightly over powers of two (which make some platform mallocs sad).
9289 - Log malloc statistics from mallinfo() on platforms where it
9293 Changes in version 0.2.0.3-alpha - 2007-07-29
9294 This third development snapshot introduces new experimental
9295 blocking-resistance features and a preliminary version of the v3
9296 directory voting design, and includes many other smaller features
9300 - The first pieces of our "bridge" design for blocking-resistance
9301 are implemented. People can run bridge directory authorities;
9302 people can run bridges; and people can configure their Tor clients
9303 with a set of bridges to use as the first hop into the Tor network.
9304 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
9306 - Create listener connections before we setuid to the configured
9307 User and Group. Now non-Windows users can choose port values
9308 under 1024, start Tor as root, and have Tor bind those ports
9309 before it changes to another UID. (Windows users could already
9311 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
9312 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
9313 on "vserver" accounts. (Patch from coderman.)
9314 - Be even more aggressive about separating local traffic from relayed
9315 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
9317 o Major features (experimental):
9318 - First cut of code for "v3 dir voting": directory authorities will
9319 vote on a common network status document rather than each publishing
9320 their own opinion. This code needs more testing and more corner-case
9321 handling before it's ready for use.
9324 - Directory authorities now call routers Fast if their bandwidth is
9325 at least 100KB/s, and consider their bandwidth adequate to be a
9326 Guard if it is at least 250KB/s, no matter the medians. This fix
9327 complements proposal 107. [Bugfix on 0.1.2.x]
9328 - Directory authorities now never mark more than 3 servers per IP as
9329 Valid and Running. (Implements proposal 109, by Kevin Bauer and
9331 - Minor change to organizationName and commonName generation
9332 procedures in TLS certificates during Tor handshakes, to invalidate
9333 some earlier censorware approaches. This is not a long-term
9334 solution, but applying it will give us a bit of time to look into
9335 the epidemiology of countermeasures as they spread.
9337 o Major bugfixes (directory):
9338 - Rewrite directory tokenization code to never run off the end of
9339 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
9341 o Minor features (controller):
9342 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
9343 match requests to applications. (Patch from Robert Hogan.)
9344 - Report address and port correctly on connections to DNSPort. (Patch
9346 - Add a RESOLVE command to launch hostname lookups. (Original patch
9348 - Add GETINFO status/enough-dir-info to let controllers tell whether
9349 Tor has downloaded sufficient directory information. (Patch
9351 - You can now use the ControlSocket option to tell Tor to listen for
9352 controller connections on Unix domain sockets on systems that
9353 support them. (Patch from Peter Palfrader.)
9354 - STREAM NEW events are generated for DNSPort requests and for
9355 tunneled directory connections. (Patch from Robert Hogan.)
9356 - New "GETINFO address-mappings/*" command to get address mappings
9357 with expiry information. "addr-mappings/*" is now deprecated.
9360 o Minor features (misc):
9361 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
9363 - The tor-gencert tool for v3 directory authorities now creates all
9364 files as readable to the file creator only, and write-protects
9365 the authority identity key.
9366 - When dumping memory usage, list bytes used in buffer memory
9368 - When running with dmalloc, dump more stats on hup and on exit.
9369 - Directory authorities now fail quickly and (relatively) harmlessly
9370 if they generate a network status document that is somehow
9373 o Traffic load balancing improvements:
9374 - If exit bandwidth ever exceeds one third of total bandwidth, then
9375 use the correct formula to weight exit nodes when choosing paths.
9376 (Based on patch from Mike Perry.)
9377 - Choose perfectly fairly among routers when choosing by bandwidth and
9378 weighting by fraction of bandwidth provided by exits. Previously, we
9379 would choose with only approximate fairness, and correct ourselves
9380 if we ran off the end of the list. [Bugfix on 0.1.2.x]
9382 o Performance improvements:
9383 - Be more aggressive with freeing buffer RAM or putting it on the
9385 - Use Critical Sections rather than Mutexes for synchronizing threads
9386 on win32; Mutexes are heavier-weight, and designed for synchronizing
9389 o Deprecated and removed features:
9390 - RedirectExits is now deprecated.
9391 - Stop allowing address masks that do not correspond to bit prefixes.
9392 We have warned about these for a really long time; now it's time
9393 to reject them. (Patch from croup.)
9395 o Minor bugfixes (directory):
9396 - Fix another crash bug related to extra-info caching. (Bug found by
9397 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
9398 - Directories no longer return a "304 not modified" when they don't
9399 have the networkstatus the client asked for. Also fix a memory
9400 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
9401 - We had accidentally labelled 0.1.2.x directory servers as not
9402 suitable for begin_dir requests, and had labelled no directory
9403 servers as suitable for uploading extra-info documents. [Bugfix
9406 o Minor bugfixes (dns):
9407 - Fix a crash when DNSPort is set more than once. (Patch from Robert
9408 Hogan.) [Bugfix on 0.2.0.2-alpha]
9409 - Add DNSPort connections to the global connection list, so that we
9410 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
9412 - Fix a dangling reference that could lead to a crash when DNSPort is
9413 changed or closed (Patch from Robert Hogan.) [Bugfix on
9416 o Minor bugfixes (controller):
9417 - Provide DNS expiry times in GMT, not in local time. For backward
9418 compatibility, ADDRMAP events only provide GMT expiry in an extended
9419 field. "GETINFO address-mappings" always does the right thing.
9420 - Use CRLF line endings properly in NS events.
9421 - Terminate multi-line control events properly. (Original patch
9422 from tup.) [Bugfix on 0.1.2.x-alpha]
9423 - Do not include spaces in SOURCE_ADDR fields in STREAM
9424 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
9427 Changes in version 0.1.2.15 - 2007-07-17
9428 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
9429 problems, fixes compilation on BSD, and fixes a variety of other
9430 bugs. Everybody should upgrade.
9432 o Major bugfixes (compilation):
9433 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
9435 o Major bugfixes (crashes):
9436 - Try even harder not to dereference the first character after
9437 an mmap(). Reported by lodger.
9438 - Fix a crash bug in directory authorities when we re-number the
9439 routerlist while inserting a new router.
9440 - When the cached-routers file is an even multiple of the page size,
9441 don't run off the end and crash. (Fixes bug 455; based on idea
9443 - Fix eventdns.c behavior on Solaris: It is critical to include
9444 orconfig.h _before_ sys/types.h, so that we can get the expected
9445 definition of _FILE_OFFSET_BITS.
9447 o Major bugfixes (security):
9448 - Fix a possible buffer overrun when using BSD natd support. Bug
9450 - When sending destroy cells from a circuit's origin, don't include
9451 the reason for tearing down the circuit. The spec says we didn't,
9452 and now we actually don't. Reported by lodger.
9453 - Keep streamids from different exits on a circuit separate. This
9454 bug may have allowed other routers on a given circuit to inject
9455 cells into streams. Reported by lodger; fixes bug 446.
9456 - If there's a never-before-connected-to guard node in our list,
9457 never choose any guards past it. This way we don't expand our
9458 guard list unless we need to.
9460 o Minor bugfixes (guard nodes):
9461 - Weight guard selection by bandwidth, so that low-bandwidth nodes
9462 don't get overused as guards.
9464 o Minor bugfixes (directory):
9465 - Correctly count the number of authorities that recommend each
9466 version. Previously, we were under-counting by 1.
9467 - Fix a potential crash bug when we load many server descriptors at
9468 once and some of them make others of them obsolete. Fixes bug 458.
9470 o Minor bugfixes (hidden services):
9471 - Stop tearing down the whole circuit when the user asks for a
9472 connection to a port that the hidden service didn't configure.
9475 o Minor bugfixes (misc):
9476 - On Windows, we were preventing other processes from reading
9477 cached-routers while Tor was running. Reported by janbar.
9478 - Fix a possible (but very unlikely) bug in picking routers by
9479 bandwidth. Add a log message to confirm that it is in fact
9480 unlikely. Patch from lodger.
9481 - Backport a couple of memory leak fixes.
9482 - Backport miscellaneous cosmetic bugfixes.
9485 Changes in version 0.2.0.2-alpha - 2007-06-02
9486 o Major bugfixes on 0.2.0.1-alpha:
9487 - Fix an assertion failure related to servers without extra-info digests.
9488 Resolves bugs 441 and 442.
9490 o Minor features (directory):
9491 - Support "If-Modified-Since" when answering HTTP requests for
9492 directories, running-routers documents, and network-status documents.
9493 (There's no need to support it for router descriptors, since those
9494 are downloaded by descriptor digest.)
9496 o Minor build issues:
9497 - Clear up some MIPSPro compiler warnings.
9498 - When building from a tarball on a machine that happens to have SVK
9499 installed, report the micro-revision as whatever version existed
9500 in the tarball, not as "x".
9503 Changes in version 0.2.0.1-alpha - 2007-06-01
9504 This early development snapshot provides new features for people running
9505 Tor as both a client and a server (check out the new RelayBandwidth
9506 config options); lets Tor run as a DNS proxy; and generally moves us
9507 forward on a lot of fronts.
9509 o Major features, server usability:
9510 - New config options RelayBandwidthRate and RelayBandwidthBurst:
9511 a separate set of token buckets for relayed traffic. Right now
9512 relayed traffic is defined as answers to directory requests, and
9513 OR connections that don't have any local circuits on them.
9515 o Major features, client usability:
9516 - A client-side DNS proxy feature to replace the need for
9517 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
9518 for DNS requests on port 9999, use the Tor network to resolve them
9519 anonymously, and send the reply back like a regular DNS server.
9520 The code still only implements a subset of DNS.
9521 - Make PreferTunneledDirConns and TunnelDirConns work even when
9522 we have no cached directory info. This means Tor clients can now
9523 do all of their connections protected by TLS.
9525 o Major features, performance and efficiency:
9526 - Directory authorities accept and serve "extra info" documents for
9527 routers. These documents contain fields from router descriptors
9528 that aren't usually needed, and that use a lot of excess
9529 bandwidth. Once these fields are removed from router descriptors,
9530 the bandwidth savings should be about 60%. [Partially implements
9532 - Servers upload extra-info documents to any authority that accepts
9533 them. Authorities (and caches that have been configured to download
9534 extra-info documents) download them as needed. [Partially implements
9536 - Change the way that Tor buffers data that it is waiting to write.
9537 Instead of queueing data cells in an enormous ring buffer for each
9538 client->OR or OR->OR connection, we now queue cells on a separate
9539 queue for each circuit. This lets us use less slack memory, and
9540 will eventually let us be smarter about prioritizing different kinds
9542 - Use memory pools to allocate cells with better speed and memory
9543 efficiency, especially on platforms where malloc() is inefficient.
9544 - Stop reading on edge connections when their corresponding circuit
9545 buffers are full; start again as the circuits empty out.
9547 o Major features, other:
9548 - Add an HSAuthorityRecordStats option that hidden service authorities
9549 can use to track statistics of overall hidden service usage without
9550 logging information that would be very useful to an attacker.
9551 - Start work implementing multi-level keys for directory authorities:
9552 Add a standalone tool to generate key certificates. (Proposal 103.)
9555 - Directory authorities now call routers Stable if they have an
9556 uptime of at least 30 days, even if that's not the median uptime
9557 in the network. Implements proposal 107, suggested by Kevin Bauer
9560 o Minor fixes (resource management):
9561 - Count the number of open sockets separately from the number
9562 of active connection_t objects. This will let us avoid underusing
9563 our allocated connection limit.
9564 - We no longer use socket pairs to link an edge connection to an
9565 anonymous directory connection or a DirPort test connection.
9566 Instead, we track the link internally and transfer the data
9567 in-process. This saves two sockets per "linked" connection (at the
9568 client and at the server), and avoids the nasty Windows socketpair()
9570 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
9571 for every single inactive connection_t. Free items from the
9572 4k/16k-buffer free lists when they haven't been used for a while.
9574 o Minor features (build):
9575 - Make autoconf search for libevent, openssl, and zlib consistently.
9576 - Update deprecated macros in configure.in.
9577 - When warning about missing headers, tell the user to let us
9578 know if the compile succeeds anyway, so we can downgrade the
9580 - Include the current subversion revision as part of the version
9581 string: either fetch it directly if we're in an SVN checkout, do
9582 some magic to guess it if we're in an SVK checkout, or use
9583 the last-detected version if we're building from a .tar.gz.
9584 Use this version consistently in log messages.
9586 o Minor features (logging):
9587 - Always prepend "Bug: " to any log message about a bug.
9588 - Put a platform string (e.g. "Linux i686") in the startup log
9589 message, so when people paste just their logs, we know if it's
9590 OpenBSD or Windows or what.
9591 - When logging memory usage, break down memory used in buffers by
9594 o Minor features (directory system):
9595 - New config option V2AuthoritativeDirectory that all directory
9596 authorities should set. This will let future authorities choose
9597 not to serve V2 directory information.
9598 - Directory authorities allow multiple router descriptors and/or extra
9599 info documents to be uploaded in a single go. This will make
9600 implementing proposal 104 simpler.
9602 o Minor features (controller):
9603 - Add a new config option __DisablePredictedCircuits designed for
9604 use by the controller, when we don't want Tor to build any circuits
9606 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
9607 so we can exit from the middle of the circuit.
9608 - Implement "getinfo status/circuit-established".
9609 - Implement "getinfo status/version/..." so a controller can tell
9610 whether the current version is recommended, and whether any versions
9611 are good, and how many authorities agree. (Patch from shibz.)
9613 o Minor features (hidden services):
9614 - Allow multiple HiddenServicePort directives with the same virtual
9615 port; when they occur, the user is sent round-robin to one
9616 of the target ports chosen at random. Partially fixes bug 393 by
9617 adding limited ad-hoc round-robining.
9619 o Minor features (other):
9621 - Add a new AutomapHostsOnResolve option: when it is enabled, any
9622 resolve request for hosts matching a given pattern causes Tor to
9623 generate an internal virtual address mapping for that host. This
9624 allows DNSPort to work sensibly with hidden service users. By
9625 default, .exit and .onion addresses are remapped; the list of
9626 patterns can be reconfigured with AutomapHostsSuffixes.
9627 - Add an "-F" option to tor-resolve to force a resolve for a .onion
9628 address. Thanks to the AutomapHostsOnResolve option, this is no
9629 longer a completely silly thing to do.
9630 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
9631 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
9632 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
9633 minus 1 byte: the actual maximum declared bandwidth.
9636 - Removed support for the old binary "version 0" controller protocol.
9637 This has been deprecated since 0.1.1, and warnings have been issued
9638 since 0.1.2. When we encounter a v0 control message, we now send
9639 back an error and close the connection.
9640 - Remove the old "dns worker" server DNS code: it hasn't been default
9641 since 0.1.2.2-alpha, and all the servers seem to be using the new
9644 o Minor bugfixes (portability):
9645 - Even though Windows is equally happy with / and \ as path separators,
9646 try to use \ consistently on Windows and / consistently on Unix: it
9647 makes the log messages nicer.
9648 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
9649 - Read resolv.conf files correctly on platforms where read() returns
9650 partial results on small file reads.
9652 o Minor bugfixes (directory):
9653 - Correctly enforce that elements of directory objects do not appear
9654 more often than they are allowed to appear.
9655 - When we are reporting the DirServer line we just parsed, we were
9656 logging the second stanza of the key fingerprint, not the first.
9658 o Minor bugfixes (logging):
9659 - When we hit an EOF on a log (probably because we're shutting down),
9660 don't try to remove the log from the list: just mark it as
9661 unusable. (Bulletproofs against bug 222.)
9663 o Minor bugfixes (other):
9664 - In the exitlist script, only consider the most recently published
9665 server descriptor for each server. Also, when the user requests
9666 a list of servers that _reject_ connections to a given address,
9667 explicitly exclude the IPs that also have servers that accept
9668 connections to that address. (Resolves bug 405.)
9669 - Stop allowing hibernating servers to be "stable" or "fast".
9670 - On Windows, we were preventing other processes from reading
9671 cached-routers while Tor was running. (Reported by janbar)
9672 - Make the NodeFamilies config option work. (Reported by
9673 lodger -- it has never actually worked, even though we added it
9675 - Check return values from pthread_mutex functions.
9676 - Don't save non-general-purpose router descriptors to the disk cache,
9677 because we have no way of remembering what their purpose was when
9679 - Add even more asserts to hunt down bug 417.
9680 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
9681 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
9682 Add a log message to confirm that it is in fact unlikely.
9684 o Minor bugfixes (controller):
9685 - Make 'getinfo fingerprint' return a 551 error if we're not a
9686 server, so we match what the control spec claims we do. Reported
9688 - Fix a typo in an error message when extendcircuit fails that
9689 caused us to not follow the \r\n-based delimiter protocol. Reported
9692 o Code simplifications and refactoring:
9693 - Stop passing around circuit_t and crypt_path_t pointers that are
9694 implicit in other procedure arguments.
9695 - Drop the old code to choke directory connections when the
9696 corresponding OR connections got full: thanks to the cell queue
9697 feature, OR conns don't get full any more.
9698 - Make dns_resolve() handle attaching connections to circuits
9699 properly, so the caller doesn't have to.
9700 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
9701 - Keep the connection array as a dynamic smartlist_t, rather than as
9702 a fixed-sized array. This is important, as the number of connections
9703 is becoming increasingly decoupled from the number of sockets.
9706 Changes in version 0.1.2.14 - 2007-05-25
9707 Tor 0.1.2.14 changes the addresses of two directory authorities (this
9708 change especially affects those who serve or use hidden services),
9709 and fixes several other crash- and security-related bugs.
9711 o Directory authority changes:
9712 - Two directory authorities (moria1 and moria2) just moved to new
9713 IP addresses. This change will particularly affect those who serve
9714 or use hidden services.
9716 o Major bugfixes (crashes):
9717 - If a directory server runs out of space in the connection table
9718 as it's processing a begin_dir request, it will free the exit stream
9719 but leave it attached to the circuit, leading to unpredictable
9720 behavior. (Reported by seeess, fixes bug 425.)
9721 - Fix a bug in dirserv_remove_invalid() that would cause authorities
9722 to corrupt memory under some really unlikely scenarios.
9723 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
9724 - Avoid segfaults when reading from mmaped descriptor file. (Reported
9727 o Major bugfixes (security):
9728 - When choosing an entry guard for a circuit, avoid using guards
9729 that are in the same family as the chosen exit -- not just guards
9730 that are exactly the chosen exit. (Reported by lodger.)
9732 o Major bugfixes (resource management):
9733 - If a directory authority is down, skip it when deciding where to get
9734 networkstatus objects or descriptors. Otherwise we keep asking
9735 every 10 seconds forever. Fixes bug 384.
9736 - Count it as a failure if we fetch a valid network-status but we
9737 don't want to keep it. Otherwise we'll keep fetching it and keep
9738 not wanting to keep it. Fixes part of bug 422.
9739 - If all of our dirservers have given us bad or no networkstatuses
9740 lately, then stop hammering them once per minute even when we
9741 think they're failed. Fixes another part of bug 422.
9744 - Actually set the purpose correctly for descriptors inserted with
9746 - When we have k non-v2 authorities in our DirServer config,
9747 we ignored the last k authorities in the list when updating our
9749 - Correctly back-off from requesting router descriptors that we are
9750 having a hard time downloading.
9751 - Read resolv.conf files correctly on platforms where read() returns
9752 partial results on small file reads.
9753 - Don't rebuild the entire router store every time we get 32K of
9754 routers: rebuild it when the journal gets very large, or when
9755 the gaps in the store get very large.
9758 - When routers publish SVN revisions in their router descriptors,
9759 authorities now include those versions correctly in networkstatus
9761 - Warn when using a version of libevent before 1.3b to run a server on
9762 OSX or BSD: these versions interact badly with userspace threads.
9765 Changes in version 0.1.2.13 - 2007-04-24
9766 This release features some major anonymity fixes, such as safer path
9767 selection; better client performance; faster bootstrapping, better
9768 address detection, and better DNS support for servers; write limiting as
9769 well as read limiting to make servers easier to run; and a huge pile of
9770 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
9772 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
9773 of the Freenode IRC network, remembering his patience and vision for
9774 free speech on the Internet.
9777 - Fix a memory leak when we ask for "all" networkstatuses and we
9778 get one we don't recognize.
9779 - Add more asserts to hunt down bug 417.
9780 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
9783 Changes in version 0.1.2.12-rc - 2007-03-16
9785 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
9786 directory information requested inside Tor connections (i.e. via
9787 begin_dir cells). It only triggered when the same connection was
9788 serving other data at the same time. Reported by seeess.
9791 - When creating a circuit via the controller, send a 'launched'
9792 event when we're done, so we follow the spec better.
9795 Changes in version 0.1.2.11-rc - 2007-03-15
9796 o Minor bugfixes (controller), reported by daejees:
9797 - Correct the control spec to match how the code actually responds
9798 to 'getinfo addr-mappings/*'.
9799 - The control spec described a GUARDS event, but the code
9800 implemented a GUARD event. Standardize on GUARD, but let people
9804 Changes in version 0.1.2.10-rc - 2007-03-07
9805 o Major bugfixes (Windows):
9806 - Do not load the NT services library functions (which may not exist)
9807 just to detect if we're a service trying to shut down. Now we run
9808 on Win98 and friends again.
9810 o Minor bugfixes (other):
9811 - Clarify a couple of log messages.
9812 - Fix a misleading socks5 error number.
9815 Changes in version 0.1.2.9-rc - 2007-03-02
9816 o Major bugfixes (Windows):
9817 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
9818 of the usual GCC "%llu". This prevents a bug when saving 64-bit
9819 int configuration values: the high-order 32 bits would get
9820 truncated. In particular, we were being bitten by the default
9821 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
9822 and maybe also bug 397.)
9824 o Minor bugfixes (performance):
9825 - Use OpenSSL's AES implementation on platforms where it's faster.
9826 This could save us as much as 10% CPU usage.
9828 o Minor bugfixes (server):
9829 - Do not rotate onion key immediately after setting it for the first
9832 o Minor bugfixes (directory authorities):
9833 - Stop calling servers that have been hibernating for a long time
9834 "stable". Also, stop letting hibernating or obsolete servers affect
9835 uptime and bandwidth cutoffs.
9836 - Stop listing hibernating servers in the v1 directory.
9838 o Minor bugfixes (hidden services):
9839 - Upload hidden service descriptors slightly less often, to reduce
9840 load on authorities.
9842 o Minor bugfixes (other):
9843 - Fix an assert that could trigger if a controller quickly set then
9844 cleared EntryNodes. Bug found by Udo van den Heuvel.
9845 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
9847 - Fix a potential race condition in the rpm installer. Found by
9849 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
9850 of 2 as indicating that the server is completely bad; it sometimes
9851 means that the server is just bad for the request in question. (may fix
9852 the last of bug 326.)
9853 - Disable encrypted directory connections when we don't have a server
9854 descriptor for the destination. We'll get this working again in
9858 Changes in version 0.1.2.8-beta - 2007-02-26
9859 o Major bugfixes (crashes):
9860 - Stop crashing when the controller asks us to resetconf more than
9861 one config option at once. (Vidalia 0.0.11 does this.)
9862 - Fix a crash that happened on Win98 when we're given command-line
9863 arguments: don't try to load NT service functions from advapi32.dll
9864 except when we need them. (Bug introduced in 0.1.2.7-alpha;
9866 - Fix a longstanding obscure crash bug that could occur when
9867 we run out of DNS worker processes. (Resolves bug 390.)
9869 o Major bugfixes (hidden services):
9870 - Correctly detect whether hidden service descriptor downloads are
9871 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
9873 o Major bugfixes (accounting):
9874 - When we start during an accounting interval before it's time to wake
9875 up, remember to wake up at the correct time. (May fix bug 342.)
9877 o Minor bugfixes (controller):
9878 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
9879 clear the corresponding on_circuit variable, and remember later
9880 that we don't need to send a redundant CLOSED event. Resolves part
9882 - Report events where a resolve succeeded or where we got a socks
9883 protocol error correctly, rather than calling both of them
9885 - Change reported stream target addresses to IP consistently when
9886 we finally get the IP from an exit node.
9887 - Send log messages to the controller even if they happen to be very
9890 o Minor bugfixes (other):
9891 - Display correct results when reporting which versions are
9892 recommended, and how recommended they are. (Resolves bug 383.)
9893 - Improve our estimates for directory bandwidth to be less random:
9894 guess that an unrecognized directory will have the average bandwidth
9895 from all known directories, not that it will have the average
9896 bandwidth from those directories earlier than it on the list.
9897 - If we start a server with ClientOnly 1, then set ClientOnly to 0
9898 and hup, stop triggering an assert based on an empty onion_key.
9899 - On platforms with no working mmap() equivalent, don't warn the
9900 user when cached-routers doesn't exist.
9901 - Warn the user when mmap() [or its equivalent] fails for some reason
9902 other than file-not-found.
9903 - Don't warn the user when cached-routers.new doesn't exist: that's
9904 perfectly fine when starting up for the first time.
9905 - When EntryNodes are configured, rebuild the guard list to contain,
9906 in order: the EntryNodes that were guards before; the rest of the
9907 EntryNodes; the nodes that were guards before.
9908 - Mask out all signals in sub-threads; only the libevent signal
9909 handler should be processing them. This should prevent some crashes
9910 on some machines using pthreads. (Patch from coderman.)
9911 - Fix switched arguments on memset in the implementation of
9912 tor_munmap() for systems with no mmap() call.
9913 - When Tor receives a router descriptor that it asked for, but
9914 no longer wants (because it has received fresh networkstatuses
9915 in the meantime), do not warn the user. Cache the descriptor if
9916 we're a cache; drop it if we aren't.
9917 - Make earlier entry guards _really_ get retried when the network
9919 - On a malformed DNS reply, always give an error to the corresponding
9921 - Build with recent libevents on platforms that do not define the
9922 nonstandard types "u_int8_t" and friends.
9924 o Minor features (controller):
9925 - Warn the user when an application uses the obsolete binary v0
9926 control protocol. We're planning to remove support for it during
9927 the next development series, so it's good to give people some
9929 - Add STREAM_BW events to report per-entry-stream bandwidth
9930 use. (Patch from Robert Hogan.)
9931 - Rate-limit SIGNEWNYM signals in response to controllers that
9932 impolitely generate them for every single stream. (Patch from
9933 mwenge; closes bug 394.)
9934 - Make REMAP stream events have a SOURCE (cache or exit), and
9935 make them generated in every case where we get a successful
9936 connected or resolved cell.
9938 o Minor bugfixes (performance):
9939 - Call router_have_min_dir_info half as often. (This is showing up in
9940 some profiles, but not others.)
9941 - When using GCC, make log_debug never get called at all, and its
9942 arguments never get evaluated, when no debug logs are configured.
9943 (This is showing up in some profiles, but not others.)
9946 - Remove some never-implemented options. Mark PathlenCoinWeight as
9948 - Implement proposal 106: Stop requiring clients to have well-formed
9949 certificates; stop checking nicknames in certificates. (Clients
9950 have certificates so that they can look like Tor servers, but in
9951 the future we might want to allow them to look like regular TLS
9952 clients instead. Nicknames in certificates serve no purpose other
9953 than making our protocol easier to recognize on the wire.)
9954 - Revise messages on handshake failure again to be even more clear about
9955 which are incoming connections and which are outgoing.
9956 - Discard any v1 directory info that's over 1 month old (for
9957 directories) or over 1 week old (for running-routers lists).
9958 - Do not warn when individual nodes in the configuration's EntryNodes,
9959 ExitNodes, etc are down: warn only when all possible nodes
9960 are down. (Fixes bug 348.)
9961 - Always remove expired routers and networkstatus docs before checking
9962 whether we have enough information to build circuits. (Fixes
9964 - Put a lower-bound on MaxAdvertisedBandwidth.
9967 Changes in version 0.1.2.7-alpha - 2007-02-06
9968 o Major bugfixes (rate limiting):
9969 - Servers decline directory requests much more aggressively when
9970 they're low on bandwidth. Otherwise they end up queueing more and
9971 more directory responses, which can't be good for latency.
9972 - But never refuse directory requests from local addresses.
9973 - Fix a memory leak when sending a 503 response for a networkstatus
9975 - Be willing to read or write on local connections (e.g. controller
9976 connections) even when the global rate limiting buckets are empty.
9977 - If our system clock jumps back in time, don't publish a negative
9978 uptime in the descriptor. Also, don't let the global rate limiting
9979 buckets go absurdly negative.
9980 - Flush local controller connection buffers periodically as we're
9981 writing to them, so we avoid queueing 4+ megabytes of data before
9984 o Major bugfixes (NT services):
9985 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
9986 command-line flag so that admins can override the default by saying
9987 "tor --service install --user "SomeUser"". This will not affect
9988 existing installed services. Also, warn the user that the service
9989 will look for its configuration file in the service user's
9990 %appdata% directory. (We can't do the 'hardwire the user's appdata
9991 directory' trick any more, since we may not have read access to that
9994 o Major bugfixes (other):
9995 - Previously, we would cache up to 16 old networkstatus documents
9996 indefinitely, if they came from nontrusted authorities. Now we
9997 discard them if they are more than 10 days old.
9998 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
10000 - Detect and reject malformed DNS responses containing circular
10002 - If exits are rare enough that we're not marking exits as guards,
10003 ignore exit bandwidth when we're deciding the required bandwidth
10005 - When we're handling a directory connection tunneled over Tor,
10006 don't fill up internal memory buffers with all the data we want
10007 to tunnel; instead, only add it if the OR connection that will
10008 eventually receive it has some room for it. (This can lead to
10009 slowdowns in tunneled dir connections; a better solution will have
10010 to wait for 0.2.0.)
10012 o Minor bugfixes (dns):
10013 - Add some defensive programming to eventdns.c in an attempt to catch
10014 possible memory-stomping bugs.
10015 - Detect and reject DNS replies containing IPv4 or IPv6 records with
10016 an incorrect number of bytes. (Previously, we would ignore the
10018 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
10019 in the correct order, and doesn't crash.
10020 - Free memory held in recently-completed DNS lookup attempts on exit.
10021 This was not a memory leak, but may have been hiding memory leaks.
10022 - Handle TTL values correctly on reverse DNS lookups.
10023 - Treat failure to parse resolv.conf as an error.
10025 o Minor bugfixes (other):
10026 - Fix crash with "tor --list-fingerprint" (reported by seeess).
10027 - When computing clock skew from directory HTTP headers, consider what
10028 time it was when we finished asking for the directory, not what
10030 - Expire socks connections if they spend too long waiting for the
10031 handshake to finish. Previously we would let them sit around for
10032 days, if the connecting application didn't close them either.
10033 - And if the socks handshake hasn't started, don't send a
10034 "DNS resolve socks failed" handshake reply; just close it.
10035 - Stop using C functions that OpenBSD's linker doesn't like.
10036 - Don't launch requests for descriptors unless we have networkstatuses
10037 from at least half of the authorities. This delays the first
10038 download slightly under pathological circumstances, but can prevent
10039 us from downloading a bunch of descriptors we don't need.
10040 - Do not log IPs with TLS failures for incoming TLS
10041 connections. (Fixes bug 382.)
10042 - If the user asks to use invalid exit nodes, be willing to use
10044 - Stop using the reserved ac_cv namespace in our configure script.
10045 - Call stat() slightly less often; use fstat() when possible.
10046 - Refactor the way we handle pending circuits when an OR connection
10047 completes or fails, in an attempt to fix a rare crash bug.
10048 - Only rewrite a conn's address based on X-Forwarded-For: headers
10049 if it's a parseable public IP address; and stop adding extra quotes
10050 to the resulting address.
10053 - Weight directory requests by advertised bandwidth. Now we can
10054 let servers enable write limiting but still allow most clients to
10055 succeed at their directory requests. (We still ignore weights when
10056 choosing a directory authority; I hope this is a feature.)
10059 - Create a new file ReleaseNotes which was the old ChangeLog. The
10060 new ChangeLog file now includes the summaries for all development
10062 - Check for addresses with invalid characters at the exit as well
10063 as at the client, and warn less verbosely when they fail. You can
10064 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
10065 - Adapt a patch from goodell to let the contrib/exitlist script
10066 take arguments rather than require direct editing.
10067 - Inform the server operator when we decide not to advertise a
10068 DirPort due to AccountingMax enabled or a low BandwidthRate. It
10069 was confusing Zax, so now we're hopefully more helpful.
10070 - Bring us one step closer to being able to establish an encrypted
10071 directory tunnel without knowing a descriptor first. Still not
10072 ready yet. As part of the change, now assume we can use a
10073 create_fast cell if we don't know anything about a router.
10074 - Allow exit nodes to use nameservers running on ports other than 53.
10075 - Servers now cache reverse DNS replies.
10076 - Add an --ignore-missing-torrc command-line option so that we can
10077 get the "use sensible defaults if the configuration file doesn't
10078 exist" behavior even when specifying a torrc location on the command
10081 o Minor features (controller):
10082 - Track reasons for OR connection failure; make these reasons
10083 available via the controller interface. (Patch from Mike Perry.)
10084 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
10085 can learn when clients are sending malformed hostnames to Tor.
10086 - Clean up documentation for controller status events.
10087 - Add a REMAP status to stream events to note that a stream's
10088 address has changed because of a cached address or a MapAddress
10092 Changes in version 0.1.2.6-alpha - 2007-01-09
10094 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
10095 connection handles more than 4 gigs in either direction, we crash.
10096 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
10097 advertised exit node, somebody might try to exit from us when
10098 we're bootstrapping and before we've built our descriptor yet.
10099 Refuse the connection rather than crashing.
10102 - Warn if we (as a server) find that we've resolved an address that we
10103 weren't planning to resolve.
10104 - Warn that using select() on any libevent version before 1.1 will be
10105 unnecessarily slow (even for select()).
10106 - Flush ERR-level controller status events just like we currently
10107 flush ERR-level log events, so that a Tor shutdown doesn't prevent
10108 the controller from learning about current events.
10110 o Minor features (more controller status events):
10111 - Implement EXTERNAL_ADDRESS server status event so controllers can
10112 learn when our address changes.
10113 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
10114 can learn when directories reject our descriptor.
10115 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
10116 can learn when a client application is speaking a non-socks protocol
10118 - Implement DANGEROUS_SOCKS client status event so controllers
10119 can learn when a client application is leaking DNS addresses.
10120 - Implement BUG general status event so controllers can learn when
10121 Tor is unhappy about its internal invariants.
10122 - Implement CLOCK_SKEW general status event so controllers can learn
10123 when Tor thinks the system clock is set incorrectly.
10124 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
10125 server status events so controllers can learn when their descriptors
10126 are accepted by a directory.
10127 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
10128 server status events so controllers can learn about Tor's progress in
10129 deciding whether it's reachable from the outside.
10130 - Implement BAD_LIBEVENT general status event so controllers can learn
10131 when we have a version/method combination in libevent that needs to
10133 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
10134 and DNS_USELESS server status events so controllers can learn
10135 about changes to DNS server status.
10137 o Minor features (directory):
10138 - Authorities no longer recommend exits as guards if this would shift
10139 too much load to the exit nodes.
10142 Changes in version 0.1.2.5-alpha - 2007-01-06
10144 - Enable write limiting as well as read limiting. Now we sacrifice
10145 capacity if we're pushing out lots of directory traffic, rather
10146 than overrunning the user's intended bandwidth limits.
10147 - Include TLS overhead when counting bandwidth usage; previously, we
10148 would count only the bytes sent over TLS, but not the bytes used
10150 - Support running the Tor service with a torrc not in the same
10151 directory as tor.exe and default to using the torrc located in
10152 the %appdata%\Tor\ of the user who installed the service. Patch
10154 - Servers now check for the case when common DNS requests are going to
10155 wildcarded addresses (i.e. all getting the same answer), and change
10156 their exit policy to reject *:* if it's happening.
10157 - Implement BEGIN_DIR cells, so we can connect to the directory
10158 server via TLS to do encrypted directory requests rather than
10159 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
10160 config options if you like.
10162 o Minor features (config and docs):
10163 - Start using the state file to store bandwidth accounting data:
10164 the bw_accounting file is now obsolete. We'll keep generating it
10165 for a while for people who are still using 0.1.2.4-alpha.
10166 - Try to batch changes to the state file so that we do as few
10167 disk writes as possible while still storing important things in
10169 - The state file and the bw_accounting file get saved less often when
10170 the AvoidDiskWrites config option is set.
10171 - Make PIDFile work on Windows (untested).
10172 - Add internal descriptions for a bunch of configuration options:
10173 accessible via controller interface and in comments in saved
10175 - Reject *:563 (NNTPS) in the default exit policy. We already reject
10176 NNTP by default, so this seems like a sensible addition.
10177 - Clients now reject hostnames with invalid characters. This should
10178 avoid some inadvertent info leaks. Add an option
10179 AllowNonRFC953Hostnames to disable this behavior, in case somebody
10180 is running a private network with hosts called @, !, and #.
10181 - Add a maintainer script to tell us which options are missing
10182 documentation: "make check-docs".
10183 - Add a new address-spec.txt document to describe our special-case
10184 addresses: .exit, .onion, and .noconnnect.
10186 o Minor features (DNS):
10187 - Ongoing work on eventdns infrastructure: now it has dns server
10188 and ipv6 support. One day Tor will make use of it.
10189 - Add client-side caching for reverse DNS lookups.
10190 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
10191 - When we change nameservers or IP addresses, reset and re-launch
10192 our tests for DNS hijacking.
10194 o Minor features (directory):
10195 - Authorities now specify server versions in networkstatus. This adds
10196 about 2% to the size of compressed networkstatus docs, and allows
10197 clients to tell which servers support BEGIN_DIR and which don't.
10198 The implementation is forward-compatible with a proposed future
10199 protocol version scheme not tied to Tor versions.
10200 - DirServer configuration lines now have an orport= option so
10201 clients can open encrypted tunnels to the authorities without
10202 having downloaded their descriptors yet. Enabled for moria1,
10203 moria2, tor26, and lefkada now in the default configuration.
10204 - Directory servers are more willing to send a 503 "busy" if they
10205 are near their write limit, especially for v1 directory requests.
10206 Now they can use their limited bandwidth for actual Tor traffic.
10207 - Clients track responses with status 503 from dirservers. After a
10208 dirserver has given us a 503, we try not to use it until an hour has
10209 gone by, or until we have no dirservers that haven't given us a 503.
10210 - When we get a 503 from a directory, and we're not a server, we don't
10211 count the failure against the total number of failures allowed
10212 for the thing we're trying to download.
10213 - Report X-Your-Address-Is correctly from tunneled directory
10214 connections; don't report X-Your-Address-Is when it's an internal
10215 address; and never believe reported remote addresses when they're
10217 - Protect against an unlikely DoS attack on directory servers.
10218 - Add a BadDirectory flag to network status docs so that authorities
10219 can (eventually) tell clients about caches they believe to be
10222 o Minor features (controller):
10223 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
10224 - Reimplement GETINFO so that info/names stays in sync with the
10226 - Implement "GETINFO fingerprint".
10227 - Implement "SETEVENTS GUARD" so controllers can get updates on
10228 entry guard status as it changes.
10230 o Minor features (clean up obsolete pieces):
10231 - Remove some options that have been deprecated since at least
10232 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
10233 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
10234 to set log options.
10235 - We no longer look for identity and onion keys in "identity.key" and
10236 "onion.key" -- these were replaced by secret_id_key and
10237 secret_onion_key in 0.0.8pre1.
10238 - We no longer require unrecognized directory entries to be
10241 o Major bugfixes (security):
10242 - Stop sending the HttpProxyAuthenticator string to directory
10243 servers when directory connections are tunnelled through Tor.
10244 - Clients no longer store bandwidth history in the state file.
10245 - Do not log introduction points for hidden services if SafeLogging
10247 - When generating bandwidth history, round down to the nearest
10248 1k. When storing accounting data, round up to the nearest 1k.
10249 - When we're running as a server, remember when we last rotated onion
10250 keys, so that we will rotate keys once they're a week old even if
10251 we never stay up for a week ourselves.
10253 o Major bugfixes (other):
10254 - Fix a longstanding bug in eventdns that prevented the count of
10255 timed-out resolves from ever being reset. This bug caused us to
10256 give up on a nameserver the third time it timed out, and try it
10257 10 seconds later... and to give up on it every time it timed out
10259 - Take out the '5 second' timeout from the connection retry
10260 schedule. Now the first connect attempt will wait a full 10
10261 seconds before switching to a new circuit. Perhaps this will help
10262 a lot. Based on observations from Mike Perry.
10263 - Fix a bug on the Windows implementation of tor_mmap_file() that
10264 would prevent the cached-routers file from ever loading. Reported
10268 - Fix an assert failure when a directory authority sets
10269 AuthDirRejectUnlisted and then receives a descriptor from an
10270 unlisted router. Reported by seeess.
10271 - Avoid a double-free when parsing malformed DirServer lines.
10272 - Fix a bug when a BSD-style PF socket is first used. Patch from
10274 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
10275 to resolve an address at a given exit node even when they ask for
10277 - Servers no longer ever list themselves in their "family" line,
10278 even if configured to do so. This makes it easier to configure
10279 family lists conveniently.
10280 - When running as a server, don't fall back to 127.0.0.1 when no
10281 nameservers are configured in /etc/resolv.conf; instead, make the
10282 user fix resolv.conf or specify nameservers explicitly. (Resolves
10284 - Stop accepting certain malformed ports in configured exit policies.
10285 - Don't re-write the fingerprint file every restart, unless it has
10287 - Stop warning when a single nameserver fails: only warn when _all_ of
10288 our nameservers have failed. Also, when we only have one nameserver,
10289 raise the threshold for deciding that the nameserver is dead.
10290 - Directory authorities now only decide that routers are reachable
10291 if their identity keys are as expected.
10292 - When the user uses bad syntax in the Log config line, stop
10293 suggesting other bad syntax as a replacement.
10294 - Correctly detect ipv6 DNS capability on OpenBSD.
10296 o Minor bugfixes (controller):
10297 - Report the circuit number correctly in STREAM CLOSED events. Bug
10298 reported by Mike Perry.
10299 - Do not report bizarre values for results of accounting GETINFOs
10300 when the last second's write or read exceeds the allotted bandwidth.
10301 - Report "unrecognized key" rather than an empty string when the
10302 controller tries to fetch a networkstatus that doesn't exist.
10305 Changes in version 0.1.1.26 - 2006-12-14
10306 o Security bugfixes:
10307 - Stop sending the HttpProxyAuthenticator string to directory
10308 servers when directory connections are tunnelled through Tor.
10309 - Clients no longer store bandwidth history in the state file.
10310 - Do not log introduction points for hidden services if SafeLogging
10314 - Fix an assert failure when a directory authority sets
10315 AuthDirRejectUnlisted and then receives a descriptor from an
10316 unlisted router (reported by seeess).
10319 Changes in version 0.1.2.4-alpha - 2006-12-03
10321 - Add support for using natd; this allows FreeBSDs earlier than
10322 5.1.2 to have ipfw send connections through Tor without using
10323 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
10326 - Make all connections to addresses of the form ".noconnect"
10327 immediately get closed. This lets application/controller combos
10328 successfully test whether they're talking to the same Tor by
10329 watching for STREAM events.
10330 - Make cross.sh cross-compilation script work even when autogen.sh
10331 hasn't been run. (Patch from Michael Mohr.)
10332 - Statistics dumped by -USR2 now include a breakdown of public key
10333 operations, for profiling.
10336 - Fix a major leak when directory authorities parse their
10337 approved-routers list, a minor memory leak when we fail to pick
10338 an exit node, and a few rare leaks on errors.
10339 - Handle TransPort connections even when the server sends data before
10340 the client sends data. Previously, the connection would just hang
10341 until the client sent data. (Patch from tup based on patch from
10343 - Avoid assert failure when our cached-routers file is empty on
10347 - Don't log spurious warnings when we see a circuit close reason we
10348 don't recognize; it's probably just from a newer version of Tor.
10349 - Have directory authorities allow larger amounts of drift in uptime
10350 without replacing the server descriptor: previously, a server that
10351 restarted every 30 minutes could have 48 "interesting" descriptors
10353 - Start linking to the Tor specification and Tor reference manual
10354 correctly in the Windows installer.
10355 - Add Vidalia to the OS X uninstaller script, so when we uninstall
10356 Tor/Privoxy we also uninstall Vidalia.
10357 - Resume building on Irix64, and fix a lot of warnings from its
10358 MIPSpro C compiler.
10359 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
10360 when we're running as a client.
10363 Changes in version 0.1.1.25 - 2006-11-04
10365 - When a client asks us to resolve (rather than connect to)
10366 an address, and we have a cached answer, give them the cached
10367 answer. Previously, we would give them no answer at all.
10368 - We were building exactly the wrong circuits when we predict
10369 hidden service requirements, meaning Tor would have to build all
10370 its circuits on demand.
10371 - If none of our live entry guards have a high uptime, but we
10372 require a guard with a high uptime, try adding a new guard before
10373 we give up on the requirement. This patch should make long-lived
10374 connections more stable on average.
10375 - When testing reachability of our DirPort, don't launch new
10376 tests when there's already one in progress -- unreachable
10377 servers were stacking up dozens of testing streams.
10379 o Security bugfixes:
10380 - When the user sends a NEWNYM signal, clear the client-side DNS
10381 cache too. Otherwise we continue to act on previous information.
10384 - Avoid a memory corruption bug when creating a hash table for
10386 - Avoid possibility of controller-triggered crash when misusing
10387 certain commands from a v0 controller on platforms that do not
10388 handle printf("%s",NULL) gracefully.
10389 - Avoid infinite loop on unexpected controller input.
10390 - Don't log spurious warnings when we see a circuit close reason we
10391 don't recognize; it's probably just from a newer version of Tor.
10392 - Add Vidalia to the OS X uninstaller script, so when we uninstall
10393 Tor/Privoxy we also uninstall Vidalia.
10396 Changes in version 0.1.2.3-alpha - 2006-10-29
10398 - Prepare for servers to publish descriptors less often: never
10399 discard a descriptor simply for being too old until either it is
10400 recommended by no authorities, or until we get a better one for
10401 the same router. Make caches consider retaining old recommended
10402 routers for even longer.
10403 - If most authorities set a BadExit flag for a server, clients
10404 don't think of it as a general-purpose exit. Clients only consider
10405 authorities that advertise themselves as listing bad exits.
10406 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
10407 headers for content, so that we can work better in the presence of
10408 caching HTTP proxies.
10409 - Allow authorities to list nodes as bad exits by fingerprint or by
10412 o Minor features, controller:
10413 - Add a REASON field to CIRC events; for backward compatibility, this
10414 field is sent only to controllers that have enabled the extended
10415 event format. Also, add additional reason codes to explain why
10416 a given circuit has been destroyed or truncated. (Patches from
10418 - Add a REMOTE_REASON field to extended CIRC events to tell the
10419 controller about why a remote OR told us to close a circuit.
10420 - Stream events also now have REASON and REMOTE_REASON fields,
10421 working much like those for circuit events.
10422 - There's now a GETINFO ns/... field so that controllers can ask Tor
10423 about the current status of a router.
10424 - A new event type "NS" to inform a controller when our opinion of
10425 a router's status has changed.
10426 - Add a GETINFO events/names and GETINFO features/names so controllers
10427 can tell which events and features are supported.
10428 - A new CLEARDNSCACHE signal to allow controllers to clear the
10429 client-side DNS cache without expiring circuits.
10431 o Security bugfixes:
10432 - When the user sends a NEWNYM signal, clear the client-side DNS
10433 cache too. Otherwise we continue to act on previous information.
10436 - Avoid sending junk to controllers or segfaulting when a controller
10437 uses EVENT_NEW_DESC with verbose nicknames.
10438 - Stop triggering asserts if the controller tries to extend hidden
10439 service circuits (reported by mwenge).
10440 - Avoid infinite loop on unexpected controller input.
10441 - When the controller does a "GETINFO network-status", tell it
10442 about even those routers whose descriptors are very old, and use
10443 long nicknames where appropriate.
10444 - Change NT service functions to be loaded on demand. This lets us
10445 build with MinGW without breaking Tor for Windows 98 users.
10446 - Do DirPort reachability tests less often, since a single test
10447 chews through many circuits before giving up.
10448 - In the hidden service example in torrc.sample, stop recommending
10449 esoteric and discouraged hidden service options.
10450 - When stopping an NT service, wait up to 10 sec for it to actually
10451 stop. Patch from Matt Edman; resolves bug 295.
10452 - Fix handling of verbose nicknames with ORCONN controller events:
10453 make them show up exactly when requested, rather than exactly when
10455 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
10456 printing a duplicate "$" in the keys we send (reported by mwenge).
10457 - Correctly set maximum connection limit on Cygwin. (This time
10459 - Try to detect Windows correctly when cross-compiling.
10460 - Detect the size of the routers file correctly even if it is
10461 corrupted (on systems without mmap) or not page-aligned (on systems
10462 with mmap). This bug was harmless.
10463 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
10464 to open a stream fails; now we do in more cases. This should
10465 make clients able to find a good exit faster in some cases, since
10466 unhandleable requests will now get an error rather than timing out.
10467 - Resolve two memory leaks when rebuilding the on-disk router cache
10468 (reported by fookoowa).
10469 - Clean up minor code warnings suggested by the MIPSpro C compiler,
10470 and reported by some Centos users.
10471 - Controller signals now work on non-Unix platforms that don't define
10472 SIGUSR1 and SIGUSR2 the way we expect.
10473 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
10474 values before failing, and always enables eventdns.
10475 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
10476 Try to fix this in configure.in by checking for most functions
10477 before we check for libevent.
10480 Changes in version 0.1.2.2-alpha - 2006-10-07
10482 - Make our async eventdns library on-by-default for Tor servers,
10483 and plan to deprecate the separate dnsworker threads.
10484 - Add server-side support for "reverse" DNS lookups (using PTR
10485 records so clients can determine the canonical hostname for a given
10486 IPv4 address). Only supported by servers using eventdns; servers
10487 now announce in their descriptors whether they support eventdns.
10488 - Specify and implement client-side SOCKS5 interface for reverse DNS
10489 lookups (see doc/socks-extensions.txt).
10490 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
10491 connect to directory servers through Tor. Previously, clients needed
10492 to find Tor exits to make private connections to directory servers.
10493 - Avoid choosing Exit nodes for entry or middle hops when the
10494 total bandwidth available from non-Exit nodes is much higher than
10495 the total bandwidth available from Exit nodes.
10496 - Workaround for name servers (like Earthlink's) that hijack failing
10497 DNS requests and replace the no-such-server answer with a "helpful"
10498 redirect to an advertising-driven search portal. Also work around
10499 DNS hijackers who "helpfully" decline to hijack known-invalid
10500 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
10501 lets you turn it off.
10502 - Send out a burst of long-range padding cells once we've established
10503 that we're reachable. Spread them over 4 circuits, so hopefully
10504 a few will be fast. This exercises our bandwidth and bootstraps
10505 us into the directory more quickly.
10507 o New/improved config options:
10508 - Add new config option "ResolvConf" to let the server operator
10509 choose an alternate resolve.conf file when using eventdns.
10510 - Add an "EnforceDistinctSubnets" option to control our "exclude
10511 servers on the same /16" behavior. It's still on by default; this
10512 is mostly for people who want to operate private test networks with
10513 all the machines on the same subnet.
10514 - If one of our entry guards is on the ExcludeNodes list, or the
10515 directory authorities don't think it's a good guard, treat it as
10516 if it were unlisted: stop using it as a guard, and throw it off
10517 the guards list if it stays that way for a long time.
10518 - Allow directory authorities to be marked separately as authorities
10519 for the v1 directory protocol, the v2 directory protocol, and
10520 as hidden service directories, to make it easier to retire old
10521 authorities. V1 authorities should set "HSAuthoritativeDir 1"
10522 to continue being hidden service authorities too.
10523 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
10525 o Minor features, controller:
10526 - Fix CIRC controller events so that controllers can learn the
10527 identity digests of non-Named servers used in circuit paths.
10528 - Let controllers ask for more useful identifiers for servers. Instead
10529 of learning identity digests for un-Named servers and nicknames
10530 for Named servers, the new identifiers include digest, nickname,
10531 and indication of Named status. Off by default; see control-spec.txt
10532 for more information.
10533 - Add a "getinfo address" controller command so it can display Tor's
10534 best guess to the user.
10535 - New controller event to alert the controller when our server
10536 descriptor has changed.
10537 - Give more meaningful errors on controller authentication failure.
10539 o Minor features, other:
10540 - When asked to resolve a hostname, don't use non-exit servers unless
10541 requested to do so. This allows servers with broken DNS to be
10542 useful to the network.
10543 - Divide eventdns log messages into warn and info messages.
10544 - Reserve the nickname "Unnamed" for routers that can't pick
10545 a hostname: any router can call itself Unnamed; directory
10546 authorities will never allocate Unnamed to any particular router;
10547 clients won't believe that any router is the canonical Unnamed.
10548 - Only include function names in log messages for info/debug messages.
10549 For notice/warn/err, the content of the message should be clear on
10550 its own, and printing the function name only confuses users.
10551 - Avoid some false positives during reachability testing: don't try
10552 to test via a server that's on the same /24 as us.
10553 - If we fail to build a circuit to an intended enclave, and it's
10554 not mandatory that we use that enclave, stop wanting it.
10555 - When eventdns is enabled, allow multithreaded builds on NetBSD and
10556 OpenBSD. (We had previously disabled threads on these platforms
10557 because they didn't have working thread-safe resolver functions.)
10559 o Major bugfixes, anonymity/security:
10560 - If a client asked for a server by name, and there's a named server
10561 in our network-status but we don't have its descriptor yet, we
10562 could return an unnamed server instead.
10563 - Fix NetBSD bug that could allow someone to force uninitialized RAM
10564 to be sent to a server's DNS resolver. This only affects NetBSD
10565 and other platforms that do not bounds-check tolower().
10566 - Reject (most) attempts to use Tor circuits with length one. (If
10567 many people start using Tor as a one-hop proxy, exit nodes become
10568 a more attractive target for compromise.)
10569 - Just because your DirPort is open doesn't mean people should be
10570 able to remotely teach you about hidden service descriptors. Now
10571 only accept rendezvous posts if you've got HSAuthoritativeDir set.
10573 o Major bugfixes, other:
10574 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
10575 - When a client asks the server to resolve (not connect to)
10576 an address, and it has a cached answer, give them the cached answer.
10577 Previously, the server would give them no answer at all.
10578 - Allow really slow clients to not hang up five minutes into their
10579 directory downloads (suggested by Adam J. Richter).
10580 - We were building exactly the wrong circuits when we anticipated
10581 hidden service requirements, meaning Tor would have to build all
10582 its circuits on demand.
10583 - Avoid crashing when we mmap a router cache file of size 0.
10584 - When testing reachability of our DirPort, don't launch new
10585 tests when there's already one in progress -- unreachable
10586 servers were stacking up dozens of testing streams.
10588 o Minor bugfixes, correctness:
10589 - If we're a directory mirror and we ask for "all" network status
10590 documents, we would discard status documents from authorities
10591 we don't recognize.
10592 - Avoid a memory corruption bug when creating a hash table for
10594 - Avoid controller-triggered crash when misusing certain commands
10595 from a v0 controller on platforms that do not handle
10596 printf("%s",NULL) gracefully.
10597 - Don't crash when a controller sends a third argument to an
10598 "extendcircuit" request.
10599 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10600 response; fix error code when "getinfo dir/status/" fails.
10601 - Avoid crash when telling controller stream-status and a stream
10603 - Patch from Adam Langley to fix assert() in eventdns.c.
10604 - Fix a debug log message in eventdns to say "X resolved to Y"
10605 instead of "X resolved to X".
10606 - Make eventdns give strings for DNS errors, not just error numbers.
10607 - Track unreachable entry guards correctly: don't conflate
10608 'unreachable by us right now' with 'listed as down by the directory
10609 authorities'. With the old code, if a guard was unreachable by
10610 us but listed as running, it would clog our guard list forever.
10611 - Behave correctly in case we ever have a network with more than
10612 2GB/s total advertised capacity.
10613 - Make TrackExitHosts case-insensitive, and fix the behavior of
10614 ".suffix" TrackExitHosts items to avoid matching in the middle of
10616 - Finally fix the openssl warnings from newer gccs that believe that
10617 ignoring a return value is okay, but casting a return value and
10618 then ignoring it is a sign of madness.
10619 - Prevent the contrib/exitlist script from printing the same
10620 result more than once.
10621 - Patch from Steve Hildrey: Generate network status correctly on
10622 non-versioning dirservers.
10623 - Don't listen to the X-Your-Address-Is hint if you did the lookup
10624 via Tor; otherwise you'll think you're the exit node's IP address.
10626 o Minor bugfixes, performance:
10627 - Two small performance improvements on parsing descriptors.
10628 - Major performance improvement on inserting descriptors: change
10629 algorithm from O(n^2) to O(n).
10630 - Make the common memory allocation path faster on machines where
10631 malloc(0) returns a pointer.
10632 - Start remembering X-Your-Address-Is directory hints even if you're
10633 a client, so you can become a server more smoothly.
10634 - Avoid duplicate entries on MyFamily line in server descriptor.
10636 o Packaging, features:
10637 - Remove architecture from OS X builds. The official builds are
10638 now universal binaries.
10639 - The Debian package now uses --verify-config when (re)starting,
10640 to distinguish configuration errors from other errors.
10641 - Update RPMs to require libevent 1.1b.
10643 o Packaging, bugfixes:
10644 - Patches so Tor builds with MinGW on Windows.
10645 - Patches so Tor might run on Cygwin again.
10646 - Resume building on non-gcc compilers and ancient gcc. Resume
10647 building with the -O0 compile flag. Resume building cleanly on
10649 - Run correctly on OS X platforms with case-sensitive filesystems.
10650 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
10651 - Add autoconf checks so Tor can build on Solaris x86 again.
10654 - Documented (and renamed) ServerDNSSearchDomains and
10655 ServerDNSResolvConfFile options.
10656 - Be clearer that the *ListenAddress directives can be repeated
10660 Changes in version 0.1.1.24 - 2006-09-29
10662 - Allow really slow clients to not hang up five minutes into their
10663 directory downloads (suggested by Adam J. Richter).
10664 - Fix major performance regression from 0.1.0.x: instead of checking
10665 whether we have enough directory information every time we want to
10666 do something, only check when the directory information has changed.
10667 This should improve client CPU usage by 25-50%.
10668 - Don't crash if, after a server has been running for a while,
10669 it can't resolve its hostname.
10672 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10673 - Don't crash when the controller receives a third argument to an
10674 "extendcircuit" request.
10675 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10676 response; fix error code when "getinfo dir/status/" fails.
10677 - Fix configure.in to not produce broken configure files with
10678 more recent versions of autoconf. Thanks to Clint for his auto*
10680 - Fix security bug on NetBSD that could allow someone to force
10681 uninitialized RAM to be sent to a server's DNS resolver. This
10682 only affects NetBSD and other platforms that do not bounds-check
10684 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
10685 methods: these are known to be buggy.
10686 - If we're a directory mirror and we ask for "all" network status
10687 documents, we would discard status documents from authorities
10688 we don't recognize.
10691 Changes in version 0.1.2.1-alpha - 2006-08-27
10693 - Add "eventdns" async dns library from Adam Langley, tweaked to
10694 build on OSX and Windows. Only enabled if you pass the
10695 --enable-eventdns argument to configure.
10696 - Allow servers with no hostname or IP address to learn their
10697 IP address by asking the directory authorities. This code only
10698 kicks in when you would normally have exited with a "no address"
10699 error. Nothing's authenticated, so use with care.
10700 - Rather than waiting a fixed amount of time between retrying
10701 application connections, we wait only 5 seconds for the first,
10702 10 seconds for the second, and 15 seconds for each retry after
10703 that. Hopefully this will improve the expected user experience.
10704 - Patch from Tup to add support for transparent AP connections:
10705 this basically bundles the functionality of trans-proxy-tor
10706 into the Tor mainline. Now hosts with compliant pf/netfilter
10707 implementations can redirect TCP connections straight to Tor
10708 without diverting through SOCKS. Needs docs.
10709 - Busy directory servers save lots of memory by spooling server
10710 descriptors, v1 directories, and v2 networkstatus docs to buffers
10711 as needed rather than en masse. Also mmap the cached-routers
10712 files, so we don't need to keep the whole thing in memory too.
10713 - Automatically avoid picking more than one node from the same
10714 /16 network when constructing a circuit.
10715 - Revise and clean up the torrc.sample that we ship with; add
10716 a section for BandwidthRate and BandwidthBurst.
10719 - Split circuit_t into origin_circuit_t and or_circuit_t, and
10720 split connection_t into edge, or, dir, control, and base structs.
10721 These will save quite a bit of memory on busy servers, and they'll
10722 also help us track down bugs in the code and bugs in the spec.
10723 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
10724 or later. Log when we are doing this, so we can diagnose it when
10725 it fails. (Also, recommend libevent 1.1b for kqueue and
10726 win32 methods; deprecate libevent 1.0b harder; make libevent
10727 recommendation system saner.)
10728 - Start being able to build universal binaries on OS X (thanks
10730 - Export the default exit policy via the control port, so controllers
10731 don't need to guess what it is / will be later.
10732 - Add a man page entry for ProtocolWarnings.
10733 - Add TestVia config option to the man page.
10734 - Remove even more protocol-related warnings from Tor server logs,
10735 such as bad TLS handshakes and malformed begin cells.
10736 - Stop fetching descriptors if you're not a dir mirror and you
10737 haven't tried to establish any circuits lately. [This currently
10738 causes some dangerous behavior, because when you start up again
10739 you'll use your ancient server descriptors.]
10740 - New DirPort behavior: if you have your dirport set, you download
10741 descriptors aggressively like a directory mirror, whether or not
10742 your ORPort is set.
10743 - Get rid of the router_retry_connections notion. Now routers
10744 no longer try to rebuild long-term connections to directory
10745 authorities, and directory authorities no longer try to rebuild
10746 long-term connections to all servers. We still don't hang up
10747 connections in these two cases though -- we need to look at it
10748 more carefully to avoid flapping, and we likely need to wait til
10749 0.1.1.x is obsolete.
10750 - Drop compatibility with obsolete Tors that permit create cells
10751 to have the wrong circ_id_type.
10752 - Re-enable per-connection rate limiting. Get rid of the "OP
10753 bandwidth" concept. Lay groundwork for "bandwidth classes" --
10754 separate global buckets that apply depending on what sort of conn
10756 - Start publishing one minute or so after we find our ORPort
10757 to be reachable. This will help reduce the number of descriptors
10758 we have for ourselves floating around, since it's quite likely
10759 other things (e.g. DirPort) will change during that minute too.
10760 - Fork the v1 directory protocol into its own spec document,
10761 and mark dir-spec.txt as the currently correct (v2) spec.
10764 - When we find our DirPort to be reachable, publish a new descriptor
10765 so we'll tell the world (reported by pnx).
10766 - Publish a new descriptor after we hup/reload. This is important
10767 if our config has changed such that we'll want to start advertising
10768 our DirPort now, etc.
10769 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10770 - When we have a state file we cannot parse, tell the user and
10771 move it aside. Now we avoid situations where the user starts
10772 Tor in 1904, Tor writes a state file with that timestamp in it,
10773 the user fixes her clock, and Tor refuses to start.
10774 - Fix configure.in to not produce broken configure files with
10775 more recent versions of autoconf. Thanks to Clint for his auto*
10777 - "tor --verify-config" now exits with -1(255) or 0 depending on
10778 whether the config options are bad or good.
10779 - Resolve bug 321 when using dnsworkers: append a period to every
10780 address we resolve at the exit node, so that we do not accidentally
10781 pick up local addresses, and so that failing searches are retried
10782 in the resolver search domains. (This is already solved for
10783 eventdns.) (This breaks Blossom servers for now.)
10784 - If we are using an exit enclave and we can't connect, e.g. because
10785 its webserver is misconfigured to not listen on localhost, then
10786 back off and try connecting from somewhere else before we fail.
10789 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
10790 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
10791 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
10792 when the IP address is mapped through MapAddress to a hostname.
10793 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
10794 useless IPv6 DNS resolves.
10795 - Patch suggested by Karsten Loesing: respond to SIGNAL command
10796 before we execute the signal, in case the signal shuts us down.
10797 - Clean up AllowInvalidNodes man page entry.
10798 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
10799 - Add more asserts to track down an assert error on a windows Tor
10800 server with connection_add being called with socket == -1.
10801 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
10802 - Fix misleading log messages: an entry guard that is "unlisted",
10803 as well as not known to be "down" (because we've never heard
10804 of it), is not therefore "up".
10805 - Remove code to special-case "-cvs" ending, since it has not
10806 actually mattered since 0.0.9.
10807 - Make our socks5 handling more robust to broken socks clients:
10808 throw out everything waiting on the buffer in between socks
10809 handshake phases, since they can't possibly (so the theory
10810 goes) have predicted what we plan to respond to them.
10813 Changes in version 0.1.1.23 - 2006-07-30
10815 - Fast Tor servers, especially exit nodes, were triggering asserts
10816 due to a bug in handling the list of pending DNS resolves. Some
10817 bugs still remain here; we're hunting them.
10818 - Entry guards could crash clients by sending unexpected input.
10819 - More fixes on reachability testing: if you find yourself reachable,
10820 then don't ever make any client requests (so you stop predicting
10821 circuits), then hup or have your clock jump, then later your IP
10822 changes, you won't think circuits are working, so you won't try to
10823 test reachability, so you won't publish.
10826 - Avoid a crash if the controller does a resetconf firewallports
10827 and then a setconf fascistfirewall=1.
10828 - Avoid an integer underflow when the dir authority decides whether
10829 a router is stable: we might wrongly label it stable, and compute
10830 a slightly wrong median stability, when a descriptor is published
10832 - Fix a place where we might trigger an assert if we can't build our
10833 own server descriptor yet.
10836 Changes in version 0.1.1.22 - 2006-07-05
10838 - Fix a big bug that was causing servers to not find themselves
10839 reachable if they changed IP addresses. Since only 0.1.1.22+
10840 servers can do reachability testing correctly, now we automatically
10841 make sure to test via one of these.
10842 - Fix to allow clients and mirrors to learn directory info from
10843 descriptor downloads that get cut off partway through.
10844 - Directory authorities had a bug in deciding if a newly published
10845 descriptor was novel enough to make everybody want a copy -- a few
10846 servers seem to be publishing new descriptors many times a minute.
10848 - Fix a rare bug that was causing some servers to complain about
10849 "closing wedged cpuworkers" and skip some circuit create requests.
10850 - Make the Exit flag in directory status documents actually work.
10853 Changes in version 0.1.1.21 - 2006-06-10
10854 o Crash and assert fixes from 0.1.1.20:
10855 - Fix a rare crash on Tor servers that have enabled hibernation.
10856 - Fix a seg fault on startup for Tor networks that use only one
10857 directory authority.
10858 - Fix an assert from a race condition that occurs on Tor servers
10859 while exiting, where various threads are trying to log that they're
10860 exiting, and delete the logs, at the same time.
10861 - Make our unit tests pass again on certain obscure platforms.
10864 - Add support for building SUSE RPM packages.
10865 - Speed up initial bootstrapping for clients: if we are making our
10866 first ever connection to any entry guard, then don't mark it down
10868 - When only one Tor server in the network is labelled as a guard,
10869 and we've already picked him, we would cycle endlessly picking him
10870 again, being unhappy about it, etc. Now we specifically exclude
10871 current guards when picking a new guard.
10872 - Servers send create cells more reliably after the TLS connection
10873 is established: we were sometimes forgetting to send half of them
10874 when we had more than one pending.
10875 - If we get a create cell that asks us to extend somewhere, but the
10876 Tor server there doesn't match the expected digest, we now send
10877 a destroy cell back, rather than silently doing nothing.
10878 - Make options->RedirectExit work again.
10879 - Make cookie authentication for the controller work again.
10880 - Stop being picky about unusual characters in the arguments to
10881 mapaddress. It's none of our business.
10882 - Add a new config option "TestVia" that lets you specify preferred
10883 middle hops to use for test circuits. Perhaps this will let me
10884 debug the reachability problems better.
10886 o Log / documentation fixes:
10887 - If we're a server and some peer has a broken TLS certificate, don't
10888 log about it unless ProtocolWarnings is set, i.e., we want to hear
10889 about protocol violations by others.
10890 - Fix spelling of VirtualAddrNetwork in man page.
10891 - Add a better explanation at the top of the autogenerated torrc file
10892 about what happened to our old torrc.
10895 Changes in version 0.1.1.20 - 2006-05-23
10897 - Downgrade a log severity where servers complain that they're
10899 - Avoid a compile warning on FreeBSD.
10900 - Remove string size limit on NEWDESC messages; solve bug 291.
10901 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
10902 more thoroughly when we're running on windows.
10905 Changes in version 0.1.1.19-rc - 2006-05-03
10907 - Regenerate our local descriptor if it's dirty and we try to use
10908 it locally (e.g. if it changes during reachability detection).
10909 - If we setconf our ORPort to 0, we continued to listen on the
10910 old ORPort and receive connections.
10911 - Avoid a second warning about machine/limits.h on Debian
10913 - Be willing to add our own routerinfo into the routerlist.
10914 Now authorities will include themselves in their directories
10915 and network-statuses.
10916 - Stop trying to upload rendezvous descriptors to every
10917 directory authority: only try the v1 authorities.
10918 - Servers no longer complain when they think they're not
10919 registered with the directory authorities. There were too many
10921 - Backport dist-rpm changes so rpms can be built without errors.
10924 - Implement an option, VirtualAddrMask, to set which addresses
10925 get handed out in response to mapaddress requests. This works
10926 around a bug in tsocks where 127.0.0.0/8 is never socksified.
10929 Changes in version 0.1.1.18-rc - 2006-04-10
10931 - Work harder to download live network-statuses from all the
10932 directory authorities we know about. Improve the threshold
10933 decision logic so we're more robust to edge cases.
10934 - When fetching rendezvous descriptors, we were willing to ask
10935 v2 authorities too, which would always return 404.
10938 - Stop listing down or invalid nodes in the v1 directory. This will
10939 reduce its bulk by about 1/3, and reduce load on directory
10941 - When deciding whether a router is Fast or Guard-worthy, consider
10942 his advertised BandwidthRate and not just the BandwidthCapacity.
10943 - No longer ship INSTALL and README files -- they are useless now.
10944 - Force rpmbuild to behave and honor target_cpu.
10945 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
10946 - Start to include translated versions of the tor-doc-*.html
10947 files, along with the screenshots. Still needs more work.
10948 - Start sending back 512 and 451 errors if mapaddress fails,
10949 rather than not sending anything back at all.
10950 - When we fail to bind or listen on an incoming or outgoing
10951 socket, we should close it before failing. otherwise we just
10952 leak it. (thanks to weasel for finding.)
10953 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
10954 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
10955 - Make NoPublish (even though deprecated) work again.
10956 - Fix a minor security flaw where a versioning auth dirserver
10957 could list a recommended version many times in a row to make
10958 clients more convinced that it's recommended.
10959 - Fix crash bug if there are two unregistered servers running
10960 with the same nickname, one of them is down, and you ask for
10961 them by nickname in your EntryNodes or ExitNodes. Also, try
10962 to pick the one that's running rather than an arbitrary one.
10963 - Fix an infinite loop we could hit if we go offline for too long.
10964 - Complain when we hit WSAENOBUFS on recv() or write() too.
10965 Perhaps this will help us hunt the bug.
10966 - If you're not a versioning dirserver, don't put the string
10967 "client-versions \nserver-versions \n" in your network-status.
10968 - Lower the minimum required number of file descriptors to 1000,
10969 so we can have some overhead for Valgrind on Linux, where the
10970 default ulimit -n is 1024.
10973 - Add tor.dizum.com as the fifth authoritative directory server.
10974 - Add a new config option FetchUselessDescriptors, off by default,
10975 for when you plan to run "exitlist" on your client and you want
10976 to know about even the non-running descriptors.
10979 Changes in version 0.1.1.17-rc - 2006-03-28
10981 - Clients and servers since 0.1.1.10-alpha have been expiring
10982 connections whenever they are idle for 5 minutes and they *do*
10983 have circuits on them. Oops. With this new version, clients will
10984 discard their previous entry guard choices and avoid choosing
10985 entry guards running these flawed versions.
10986 - Fix memory leak when uncompressing concatenated zlib streams. This
10987 was causing substantial leaks over time on Tor servers.
10988 - The v1 directory was including servers as much as 48 hours old,
10989 because that's how the new routerlist->routers works. Now only
10990 include them if they're 20 hours old or less.
10993 - Resume building on irix64, netbsd 2.0, etc.
10994 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
10996 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
10997 and it is confusing some users.
10998 - Mirrors stop caching the v1 directory so often.
10999 - Make the max number of old descriptors that a cache will hold
11000 rise with the number of directory authorities, so we can scale.
11001 - Change our win32 uname() hack to be more forgiving about what
11002 win32 versions it thinks it's found.
11005 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
11007 - When the controller's *setconf commands fail, collect an error
11008 message in a string and hand it back to the controller.
11009 - Make the v2 dir's "Fast" flag based on relative capacity, just
11010 like "Stable" is based on median uptime. Name everything in the
11011 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
11012 - Log server fingerprint on startup, so new server operators don't
11013 have to go hunting around their filesystem for it.
11014 - Return a robots.txt on our dirport to discourage google indexing.
11015 - Let the controller ask for GETINFO dir/status/foo so it can ask
11016 directly rather than connecting to the dir port. Only works when
11017 dirport is set for now.
11019 o New config options rather than constants in the code:
11020 - SocksTimeout: How long do we let a socks connection wait
11021 unattached before we fail it?
11022 - CircuitBuildTimeout: Cull non-open circuits that were born
11023 at least this many seconds ago.
11024 - CircuitIdleTimeout: Cull open clean circuits that were born
11025 at least this many seconds ago.
11028 Changes in version 0.1.1.16-rc - 2006-03-18
11029 o Bugfixes on 0.1.1.15-rc:
11030 - Fix assert when the controller asks to attachstream a connect-wait
11031 or resolve-wait stream.
11032 - Now do address rewriting when the controller asks us to attach
11033 to a particular circuit too. This will let Blossom specify
11034 "moria2.exit" without having to learn what moria2's IP address is.
11035 - Make the "tor --verify-config" command-line work again, so people
11036 can automatically check if their torrc will parse.
11037 - Authoritative dirservers no longer require an open connection from
11038 a server to consider him "reachable". We need this change because
11039 when we add new auth dirservers, old servers won't know not to
11041 - Let Tor build on Sun CC again.
11042 - Fix an off-by-one buffer size in dirserv.c that magically never
11043 hit our three authorities but broke sjmurdoch's own tor network.
11044 - If we as a directory mirror don't know of any v1 directory
11045 authorities, then don't try to cache any v1 directories.
11046 - Stop warning about unknown servers in our family when they are
11047 given as hex digests.
11048 - Stop complaining as quickly to the server operator that he
11049 hasn't registered his nickname/key binding.
11050 - Various cleanups so we can add new V2 Auth Dirservers.
11051 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
11052 reflect the updated flags in our v2 dir protocol.
11053 - Resume allowing non-printable characters for exit streams (both
11054 for connecting and for resolving). Now we tolerate applications
11055 that don't follow the RFCs. But continue to block malformed names
11058 o Bugfixes on 0.1.0.x:
11059 - Fix assert bug in close_logs(): when we close and delete logs,
11060 remove them all from the global "logfiles" list.
11061 - Fix minor integer overflow in calculating when we expect to use up
11062 our bandwidth allocation before hibernating.
11063 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
11064 there are multiple SSLs installed with different versions.
11065 - When we try to be a server and Address is not explicitly set and
11066 our hostname resolves to a private IP address, try to use an
11067 interface address if it has a public address. Now Windows machines
11068 that think of themselves as localhost can work by default.
11071 - Let the controller ask for GETINFO dir/server/foo so it can ask
11072 directly rather than connecting to the dir port.
11073 - Let the controller tell us about certain router descriptors
11074 that it doesn't want Tor to use in circuits. Implement
11075 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
11076 - New config option SafeSocks to reject all application connections
11077 using unsafe socks protocols. Defaults to off.
11080 Changes in version 0.1.1.15-rc - 2006-03-11
11081 o Bugfixes and cleanups:
11082 - When we're printing strings from the network, don't try to print
11083 non-printable characters. This protects us against shell escape
11084 sequence exploits, and also against attacks to fool humans into
11085 misreading their logs.
11086 - Fix a bug where Tor would fail to establish any connections if you
11087 left it off for 24 hours and then started it: we were happy with
11088 the obsolete network statuses, but they all referred to router
11089 descriptors that were too old to fetch, so we ended up with no
11090 valid router descriptors.
11091 - Fix a seg fault in the controller's "getinfo orconn-status"
11092 command while listing status on incoming handshaking connections.
11093 Introduce a status name "NEW" for these connections.
11094 - If we get a linelist or linelist_s config option from the torrc
11095 (e.g. ExitPolicy) and it has no value, warn and skip rather than
11096 silently resetting it to its default.
11097 - Don't abandon entry guards until they've been down or gone for
11099 - Cleaner and quieter log messages.
11102 - New controller signal NEWNYM that makes new application requests
11103 use clean circuits.
11104 - Add a new circuit purpose 'controller' to let the controller ask
11105 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
11106 controller command to let you specify the purpose if you're
11107 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
11108 command to let you change a circuit's purpose after it's been
11110 - Accept "private:*" in routerdesc exit policies; not generated yet
11111 because older Tors do not understand it.
11112 - Add BSD-style contributed startup script "rc.subr" from Peter
11116 Changes in version 0.1.1.14-alpha - 2006-02-20
11117 o Bugfixes on 0.1.1.x:
11118 - Don't die if we ask for a stdout or stderr log (even implicitly)
11119 and we're set to RunAsDaemon -- just warn.
11120 - We still had a few bugs in the OR connection rotation code that
11121 caused directory servers to slowly aggregate connections to other
11122 fast Tor servers. This time for sure!
11123 - Make log entries on Win32 include the name of the function again.
11124 - We were treating a pair of exit policies if they were equal even
11125 if one said accept and the other said reject -- causing us to
11126 not always publish a new descriptor since we thought nothing
11128 - Retry pending server downloads as well as pending networkstatus
11129 downloads when we unexpectedly get a socks request.
11130 - We were ignoring the IS_FAST flag in the directory status,
11131 meaning we were willing to pick trivial-bandwidth nodes for "fast"
11133 - If the controller's SAVECONF command fails (e.g. due to file
11134 permissions), let the controller know that it failed.
11137 - If we're trying to be a Tor server and running Windows 95/98/ME
11138 as a server, explain that we'll likely crash.
11139 - When we're a server, a client asks for an old-style directory,
11140 and our write bucket is empty, don't give it to him. This way
11141 small servers can continue to serve the directory *sometimes*,
11142 without getting overloaded.
11143 - Compress exit policies even more -- look for duplicate lines
11145 - Clients now honor the "guard" flag in the router status when
11146 picking entry guards, rather than looking at is_fast or is_stable.
11147 - Retain unrecognized lines in $DATADIR/state file, so that we can
11148 be forward-compatible.
11149 - Generate 18.0.0.0/8 address policy format in descs when we can;
11150 warn when the mask is not reducible to a bit-prefix.
11151 - Let the user set ControlListenAddress in the torrc. This can be
11152 dangerous, but there are some cases (like a secured LAN) where it
11154 - Split ReachableAddresses into ReachableDirAddresses and
11155 ReachableORAddresses, so we can restrict Dir conns to port 80
11156 and OR conns to port 443.
11157 - Now we can target arch and OS in rpm builds (contributed by
11158 Phobos). Also make the resulting dist-rpm filename match the
11160 - New config options to help controllers: FetchServerDescriptors
11161 and FetchHidServDescriptors for whether to fetch server
11162 info and hidserv info or let the controller do it, and
11163 PublishServerDescriptor and PublishHidServDescriptors.
11164 - Also let the controller set the __AllDirActionsPrivate config
11165 option if you want all directory fetches/publishes to happen via
11166 Tor (it assumes your controller bootstraps your circuits).
11169 Changes in version 0.1.0.17 - 2006-02-17
11170 o Crash bugfixes on 0.1.0.x:
11171 - When servers with a non-zero DirPort came out of hibernation,
11172 sometimes they would trigger an assert.
11174 o Other important bugfixes:
11175 - On platforms that don't have getrlimit (like Windows), we were
11176 artificially constraining ourselves to a max of 1024
11177 connections. Now just assume that we can handle as many as 15000
11178 connections. Hopefully this won't cause other problems.
11180 o Backported features:
11181 - When we're a server, a client asks for an old-style directory,
11182 and our write bucket is empty, don't give it to him. This way
11183 small servers can continue to serve the directory *sometimes*,
11184 without getting overloaded.
11185 - Whenever you get a 503 in response to a directory fetch, try
11186 once more. This will become important once servers start sending
11187 503's whenever they feel busy.
11188 - Fetch a new directory every 120 minutes, not every 40 minutes.
11189 Now that we have hundreds of thousands of users running the old
11190 directory algorithm, it's starting to hurt a lot.
11191 - Bump up the period for forcing a hidden service descriptor upload
11192 from 20 minutes to 1 hour.
11195 Changes in version 0.1.1.13-alpha - 2006-02-09
11196 o Crashes in 0.1.1.x:
11197 - When you tried to setconf ORPort via the controller, Tor would
11198 crash. So people using TorCP to become a server were sad.
11199 - Solve (I hope) the stack-smashing bug that we were seeing on fast
11200 servers. The problem appears to be something do with OpenSSL's
11201 random number generation, or how we call it, or something. Let me
11202 know if the crashes continue.
11203 - Turn crypto hardware acceleration off by default, until we find
11204 somebody smart who can test it for us. (It appears to produce
11205 seg faults in at least some cases.)
11206 - Fix a rare assert error when we've tried all intro points for
11207 a hidden service and we try fetching the service descriptor again:
11208 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
11211 - Fix a major load balance bug: we were round-robining in 16 KB
11212 chunks, and servers with bandwidthrate of 20 KB, while downloading
11213 a 600 KB directory, would starve their other connections. Now we
11214 try to be a bit more fair.
11215 - Dir authorities and mirrors were never expiring the newest
11216 descriptor for each server, causing memory and directory bloat.
11217 - Fix memory-bloating and connection-bloating bug on servers: We
11218 were never closing any connection that had ever had a circuit on
11219 it, because we were checking conn->n_circuits == 0, yet we had a
11220 bug that let it go negative.
11221 - Make Tor work using squid as your http proxy again -- squid
11222 returns an error if you ask for a URL that's too long, and it uses
11223 a really generic error message. Plus, many people are behind a
11224 transparent squid so they don't even realize it.
11225 - On platforms that don't have getrlimit (like Windows), we were
11226 artificially constraining ourselves to a max of 1024
11227 connections. Now just assume that we can handle as many as 15000
11228 connections. Hopefully this won't cause other problems.
11229 - Add a new config option ExitPolicyRejectPrivate which defaults to
11230 1. This means all exit policies will begin with rejecting private
11231 addresses, unless the server operator explicitly turns it off.
11234 - Clients no longer download descriptors for non-running
11236 - Before we add new directory authorities, we should make it
11237 clear that only v1 authorities should receive/publish hidden
11238 service descriptors.
11241 - As soon as we've fetched some more directory info, immediately
11242 try to download more server descriptors. This way we don't have
11243 a 10 second pause during initial bootstrapping.
11244 - Remove even more loud log messages that the server operator can't
11246 - When we're running an obsolete or un-recommended version, make
11247 the log message more clear about what the problem is and what
11248 versions *are* still recommended.
11249 - Provide a more useful warn message when our onion queue gets full:
11250 the CPU is too slow or the exit policy is too liberal.
11251 - Don't warn when we receive a 503 from a dirserver/cache -- this
11252 will pave the way for them being able to refuse if they're busy.
11253 - When we fail to bind a listener, try to provide a more useful
11254 log message: e.g., "Is Tor already running?"
11255 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
11256 Goldberg can prove things about our handshake protocol more
11258 - MaxConn has been obsolete for a while now. Document the ConnLimit
11259 config option, which is a *minimum* number of file descriptors
11260 that must be available else Tor refuses to start.
11261 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
11262 if you log to syslog and want something other than LOG_DAEMON.
11263 - Make dirservers generate a separate "guard" flag to mean,
11264 "would make a good entry guard". Make clients parse it and vote
11265 on it. Not used by clients yet.
11266 - Implement --with-libevent-dir option to ./configure. Also, improve
11267 search techniques to find libevent, and use those for openssl too.
11268 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
11269 - Only start testing reachability once we've established a
11270 circuit. This will make startup on dirservers less noisy.
11271 - Don't try to upload hidden service descriptors until we have
11272 established a circuit.
11273 - Fix the controller's "attachstream 0" command to treat conn like
11274 it just connected, doing address remapping, handling .exit and
11275 .onion idioms, and so on. Now we're more uniform in making sure
11276 that the controller hears about new and closing connections.
11279 Changes in version 0.1.1.12-alpha - 2006-01-11
11280 o Bugfixes on 0.1.1.x:
11281 - The fix to close duplicate server connections was closing all
11282 Tor client connections if they didn't establish a circuit
11283 quickly enough. Oops.
11284 - Fix minor memory issue (double-free) that happened on exit.
11286 o Bugfixes on 0.1.0.x:
11287 - Tor didn't warn when it failed to open a log file.
11290 Changes in version 0.1.1.11-alpha - 2006-01-10
11291 o Crashes in 0.1.1.x:
11292 - Include all the assert/crash fixes from 0.1.0.16.
11293 - If you start Tor and then quit very quickly, there were some
11294 races that tried to free things that weren't allocated yet.
11295 - Fix a rare memory stomp if you're running hidden services.
11296 - Fix segfault when specifying DirServer in config without nickname.
11297 - Fix a seg fault when you finish connecting to a server but at
11298 that moment you dump his server descriptor.
11299 - Extendcircuit and Attachstream controller commands would
11300 assert/crash if you don't give them enough arguments.
11301 - Fix an assert error when we're out of space in the connection_list
11302 and we try to post a hidden service descriptor (reported by weasel).
11303 - If you specify a relative torrc path and you set RunAsDaemon in
11304 your torrc, then it chdir()'s to the new directory. If you HUP,
11305 it tries to load the new torrc location, fails, and exits.
11306 The fix: no longer allow a relative path to torrc using -f.
11309 - Implement "entry guards": automatically choose a handful of entry
11310 nodes and stick with them for all circuits. Only pick new guards
11311 when the ones you have are unsuitable, and if the old guards
11312 become suitable again, switch back. This will increase security
11313 dramatically against certain end-point attacks. The EntryNodes
11314 config option now provides some hints about which entry guards you
11315 want to use most; and StrictEntryNodes means to only use those.
11316 - New directory logic: download by descriptor digest, not by
11317 fingerprint. Caches try to download all listed digests from
11318 authorities; clients try to download "best" digests from caches.
11319 This avoids partitioning and isolating attacks better.
11320 - Make the "stable" router flag in network-status be the median of
11321 the uptimes of running valid servers, and make clients pay
11322 attention to the network-status flags. Thus the cutoff adapts
11323 to the stability of the network as a whole, making IRC, IM, etc
11324 connections more reliable.
11327 - Tor servers with dynamic IP addresses were needing to wait 18
11328 hours before they could start doing reachability testing using
11329 the new IP address and ports. This is because they were using
11330 the internal descriptor to learn what to test, yet they were only
11331 rebuilding the descriptor once they decided they were reachable.
11332 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
11333 to download certain server descriptors, throw them away, and then
11334 fetch them again after 30 minutes. Now mirrors throw away these
11335 server descriptors so clients can't get them.
11336 - We were leaving duplicate connections to other ORs open for a week,
11337 rather than closing them once we detect a duplicate. This only
11338 really affected authdirservers, but it affected them a lot.
11339 - Spread the authdirservers' reachability testing over the entire
11340 testing interval, so we don't try to do 500 TLS's at once every
11344 - If the network is down, and we try to connect to a conn because
11345 we have a circuit in mind, and we timeout (30 seconds) because the
11346 network never answers, we were expiring the circuit, but we weren't
11347 obsoleting the connection or telling the entry_guards functions.
11348 - Some Tor servers process billions of cells per day. These statistics
11349 need to be uint64_t's.
11350 - Check for integer overflows in more places, when adding elements
11351 to smartlists. This could possibly prevent a buffer overflow
11352 on malicious huge inputs. I don't see any, but I haven't looked
11354 - ReachableAddresses kept growing new "reject *:*" lines on every
11356 - When you "setconf log" via the controller, it should remove all
11357 logs. We were automatically adding back in a "log notice stdout".
11358 - Newly bootstrapped Tor networks couldn't establish hidden service
11359 circuits until they had nodes with high uptime. Be more tolerant.
11360 - We were marking servers down when they could not answer every piece
11361 of the directory request we sent them. This was far too harsh.
11362 - Fix the torify (tsocks) config file to not use Tor for localhost
11364 - Directory authorities now go to the proper authority when asking for
11365 a networkstatus, even when they want a compressed one.
11366 - Fix a harmless bug that was causing Tor servers to log
11367 "Got an end because of misc error, but we're not an AP. Closing."
11368 - Authorities were treating their own descriptor changes as cosmetic,
11369 meaning the descriptor available in the network-status and the
11370 descriptor that clients downloaded were different.
11371 - The OS X installer was adding a symlink for tor_resolve but
11372 the binary was called tor-resolve (reported by Thomas Hardly).
11373 - Workaround a problem with some http proxies where they refuse GET
11374 requests that specify "Content-Length: 0" (reported by Adrian).
11375 - Fix wrong log message when you add a "HiddenServiceNodes" config
11376 line without any HiddenServiceDir line (reported by Chris Thomas).
11379 - Write the TorVersion into the state file so we have a prayer of
11380 keeping forward and backward compatibility.
11381 - Revive the FascistFirewall config option rather than eliminating it:
11382 now it's a synonym for ReachableAddresses *:80,*:443.
11383 - Clients choose directory servers from the network status lists,
11384 not from their internal list of router descriptors. Now they can
11385 go to caches directly rather than needing to go to authorities
11387 - Directory authorities ignore router descriptors that have only
11388 cosmetic differences: do this for 0.1.0.x servers now too.
11389 - Add a new flag to network-status indicating whether the server
11390 can answer v2 directory requests too.
11391 - Authdirs now stop whining so loudly about bad descriptors that
11392 they fetch from other dirservers. So when there's a log complaint,
11393 it's for sure from a freshly uploaded descriptor.
11394 - Reduce memory requirements in our structs by changing the order
11396 - There used to be two ways to specify your listening ports in a
11397 server descriptor: on the "router" line and with a separate "ports"
11398 line. Remove support for the "ports" line.
11399 - New config option "AuthDirRejectUnlisted" for auth dirservers as
11400 a panic button: if we get flooded with unusable servers we can
11401 revert to only listing servers in the approved-routers file.
11402 - Auth dir servers can now mark a fingerprint as "!reject" or
11403 "!invalid" in the approved-routers file (as its nickname), to
11404 refuse descriptors outright or include them but marked as invalid.
11405 - Servers store bandwidth history across restarts/crashes.
11406 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
11407 get a better idea of why their circuits failed. Not used yet.
11408 - Directory mirrors now cache up to 16 unrecognized network-status
11409 docs. Now we can add new authdirservers and they'll be cached too.
11410 - When picking a random directory, prefer non-authorities if any
11412 - New controller option "getinfo desc/all-recent" to fetch the
11413 latest server descriptor for every router that Tor knows about.
11416 Changes in version 0.1.0.16 - 2006-01-02
11417 o Crash bugfixes on 0.1.0.x:
11418 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
11419 corrupting the heap, losing FDs, or crashing when we need to resize
11420 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
11421 - It turns out sparc64 platforms crash on unaligned memory access
11422 too -- so detect and avoid this.
11423 - Handle truncated compressed data correctly (by detecting it and
11425 - Fix possible-but-unlikely free(NULL) in control.c.
11426 - When we were closing connections, there was a rare case that
11427 stomped on memory, triggering seg faults and asserts.
11428 - Avoid potential infinite recursion when building a descriptor. (We
11429 don't know that it ever happened, but better to fix it anyway.)
11430 - We were neglecting to unlink marked circuits from soon-to-close OR
11431 connections, which caused some rare scribbling on freed memory.
11432 - Fix a memory stomping race bug when closing the joining point of two
11433 rendezvous circuits.
11434 - Fix an assert in time parsing found by Steven Murdoch.
11436 o Other bugfixes on 0.1.0.x:
11437 - When we're doing reachability testing, provide more useful log
11438 messages so the operator knows what to expect.
11439 - Do not check whether DirPort is reachable when we are suppressing
11440 advertising it because of hibernation.
11441 - When building with -static or on Solaris, we sometimes needed -ldl.
11442 - When we're deciding whether a stream has enough circuits around
11443 that can handle it, count the freshly dirty ones and not the ones
11444 that are so dirty they won't be able to handle it.
11445 - When we're expiring old circuits, we had a logic error that caused
11446 us to close new rendezvous circuits rather than old ones.
11447 - Give a more helpful log message when you try to change ORPort via
11448 the controller: you should upgrade Tor if you want that to work.
11449 - We were failing to parse Tor versions that start with "Tor ".
11450 - Tolerate faulty streams better: when a stream fails for reason
11451 exitpolicy, stop assuming that the router is lying about his exit
11452 policy. When a stream fails for reason misc, allow it to retry just
11453 as if it was resolvefailed. When a stream has failed three times,
11454 reset its failure count so we can try again and get all three tries.
11457 Changes in version 0.1.1.10-alpha - 2005-12-11
11458 o Correctness bugfixes on 0.1.0.x:
11459 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
11460 corrupting the heap, losing FDs, or crashing when we need to resize
11461 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
11462 - Stop doing the complex voodoo overkill checking for insecure
11463 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
11464 - When we were closing connections, there was a rare case that
11465 stomped on memory, triggering seg faults and asserts.
11466 - We were neglecting to unlink marked circuits from soon-to-close OR
11467 connections, which caused some rare scribbling on freed memory.
11468 - When we're deciding whether a stream has enough circuits around
11469 that can handle it, count the freshly dirty ones and not the ones
11470 that are so dirty they won't be able to handle it.
11471 - Recover better from TCP connections to Tor servers that are
11472 broken but don't tell you (it happens!); and rotate TLS
11473 connections once a week.
11474 - When we're expiring old circuits, we had a logic error that caused
11475 us to close new rendezvous circuits rather than old ones.
11476 - Fix a scary-looking but apparently harmless bug where circuits
11477 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
11478 servers, and never switch to state CIRCUIT_STATE_OPEN.
11479 - When building with -static or on Solaris, we sometimes needed to
11481 - Give a useful message when people run Tor as the wrong user,
11482 rather than telling them to start chowning random directories.
11483 - We were failing to inform the controller about new .onion streams.
11485 o Security bugfixes on 0.1.0.x:
11486 - Refuse server descriptors if the fingerprint line doesn't match
11487 the included identity key. Tor doesn't care, but other apps (and
11488 humans) might actually be trusting the fingerprint line.
11489 - We used to kill the circuit when we receive a relay command we
11490 don't recognize. Now we just drop it.
11491 - Start obeying our firewall options more rigorously:
11492 . If we can't get to a dirserver directly, try going via Tor.
11493 . Don't ever try to connect (as a client) to a place our
11494 firewall options forbid.
11495 . If we specify a proxy and also firewall options, obey the
11496 firewall options even when we're using the proxy: some proxies
11497 can only proxy to certain destinations.
11498 - Fix a bug found by Lasse Overlier: when we were making internal
11499 circuits (intended to be cannibalized later for rendezvous and
11500 introduction circuits), we were picking them so that they had
11501 useful exit nodes. There was no need for this, and it actually
11502 aids some statistical attacks.
11503 - Start treating internal circuits and exit circuits separately.
11504 It's important to keep them separate because internal circuits
11505 have their last hops picked like middle hops, rather than like
11506 exit hops. So exiting on them will break the user's expectations.
11508 o Bugfixes on 0.1.1.x:
11509 - Take out the mis-feature where we tried to detect IP address
11510 flapping for people with DynDNS, and chose not to upload a new
11511 server descriptor sometimes.
11512 - Try to be compatible with OpenSSL 0.9.6 again.
11513 - Log fix: when the controller is logging about .onion addresses,
11514 sometimes it didn't include the ".onion" part of the address.
11515 - Don't try to modify options->DirServers internally -- if the
11516 user didn't specify any, just add the default ones directly to
11517 the trusted dirserver list. This fixes a bug where people running
11518 controllers would use SETCONF on some totally unrelated config
11519 option, and Tor would start yelling at them about changing their
11521 - Let the controller's redirectstream command specify a port, in
11522 case the controller wants to change that too.
11523 - When we requested a pile of server descriptors, we sometimes
11524 accidentally launched a duplicate request for the first one.
11525 - Bugfix for trackhostexits: write down the fingerprint of the
11526 chosen exit, not its nickname, because the chosen exit might not
11528 - When parsing foo.exit, if foo is unknown, and we are leaving
11529 circuits unattached, set the chosen_exit field and leave the
11530 address empty. This matters because controllers got confused
11532 - Directory authorities no longer try to download server
11533 descriptors that they know they will reject.
11535 o Features and updates:
11536 - Replace balanced trees with hash tables: this should make stuff
11537 significantly faster.
11538 - Resume using the AES counter-mode implementation that we ship,
11539 rather than OpenSSL's. Ours is significantly faster.
11540 - Many other CPU and memory improvements.
11541 - Add a new config option FastFirstHopPK (on by default) so clients
11542 do a trivial crypto handshake for their first hop, since TLS has
11543 already taken care of confidentiality and authentication.
11544 - Add a new config option TestSocks so people can see if their
11545 applications are using socks4, socks4a, socks5-with-ip, or
11546 socks5-with-hostname. This way they don't have to keep mucking
11547 with tcpdump and wondering if something got cached somewhere.
11548 - Warn when listening on a public address for socks. I suspect a
11549 lot of people are setting themselves up as open socks proxies,
11550 and they have no idea that jerks on the Internet are using them,
11551 since they simply proxy the traffic into the Tor network.
11552 - Add "private:*" as an alias in configuration for policies. Now
11553 you can simplify your exit policy rather than needing to list
11554 every single internal or nonroutable network space.
11555 - Add a new controller event type that allows controllers to get
11556 all server descriptors that were uploaded to a router in its role
11557 as authoritative dirserver.
11558 - Start shipping socks-extensions.txt, tor-doc-unix.html,
11559 tor-doc-server.html, and stylesheet.css in the tarball.
11560 - Stop shipping tor-doc.html in the tarball.
11563 Changes in version 0.1.1.9-alpha - 2005-11-15
11564 o Usability improvements:
11565 - Start calling it FooListenAddress rather than FooBindAddress,
11566 since few of our users know what it means to bind an address
11568 - Reduce clutter in server logs. We're going to try to make
11569 them actually usable now. New config option ProtocolWarnings that
11570 lets you hear about how _other Tors_ are breaking the protocol. Off
11572 - Divide log messages into logging domains. Once we put some sort
11573 of interface on this, it will let people looking at more verbose
11574 log levels specify the topics they want to hear more about.
11575 - Make directory servers return better http 404 error messages
11576 instead of a generic "Servers unavailable".
11577 - Check for even more Windows version flags when writing the platform
11578 string in server descriptors, and note any we don't recognize.
11579 - Clean up more of the OpenSSL memory when exiting, so we can detect
11580 memory leaks better.
11581 - Make directory authorities be non-versioning, non-naming by
11582 default. Now we can add new directory servers without requiring
11583 their operators to pay close attention.
11584 - When logging via syslog, include the pid whenever we provide
11585 a log entry. Suggested by Todd Fries.
11587 o Performance improvements:
11588 - Directory servers now silently throw away new descriptors that
11589 haven't changed much if the timestamps are similar. We do this to
11590 tolerate older Tor servers that upload a new descriptor every 15
11591 minutes. (It seemed like a good idea at the time.)
11592 - Inline bottleneck smartlist functions; use fast versions by default.
11593 - Add a "Map from digest to void*" abstraction digestmap_t so we
11594 can do less hex encoding/decoding. Use it in router_get_by_digest()
11595 to resolve a performance bottleneck.
11596 - Allow tor_gzip_uncompress to extract as much as possible from
11597 truncated compressed data. Try to extract as many
11598 descriptors as possible from truncated http responses (when
11599 DIR_PURPOSE_FETCH_ROUTERDESC).
11600 - Make circ->onionskin a pointer, not a static array. moria2 was using
11601 125000 circuit_t's after it had been up for a few weeks, which
11602 translates to 20+ megs of wasted space.
11603 - The private half of our EDH handshake keys are now chosen out
11604 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
11606 o Security improvements:
11607 - Start making directory caches retain old routerinfos, so soon
11608 clients can start asking by digest of descriptor rather than by
11609 fingerprint of server.
11610 - Add half our entropy from RAND_poll in OpenSSL. This knows how
11611 to use egd (if present), openbsd weirdness (if present), vms/os2
11612 weirdness (if we ever port there), and more in the future.
11614 o Bugfixes on 0.1.0.x:
11615 - Do round-robin writes of at most 16 kB per write. This might be
11616 more fair on loaded Tor servers, and it might resolve our Windows
11617 crash bug. It might also slow things down.
11618 - Our TLS handshakes were generating a single public/private
11619 keypair for the TLS context, rather than making a new one for
11620 each new connections. Oops. (But we were still rotating them
11621 periodically, so it's not so bad.)
11622 - When we were cannibalizing a circuit with a particular exit
11623 node in mind, we weren't checking to see if that exit node was
11624 already present earlier in the circuit. Oops.
11625 - When a Tor server's IP changes (e.g. from a dyndns address),
11626 upload a new descriptor so clients will learn too.
11627 - Really busy servers were keeping enough circuits open on stable
11628 connections that they were wrapping around the circuit_id
11629 space. (It's only two bytes.) This exposed a bug where we would
11630 feel free to reuse a circuit_id even if it still exists but has
11631 been marked for close. Try to fix this bug. Some bug remains.
11632 - If we would close a stream early (e.g. it asks for a .exit that
11633 we know would refuse it) but the LeaveStreamsUnattached config
11634 option is set by the controller, then don't close it.
11636 o Bugfixes on 0.1.1.8-alpha:
11637 - Fix a big pile of memory leaks, some of them serious.
11638 - Do not try to download a routerdesc if we would immediately reject
11640 - Resume inserting a newline between all router descriptors when
11641 generating (old style) signed directories, since our spec says
11643 - When providing content-type application/octet-stream for
11644 server descriptors using .z, we were leaving out the
11645 content-encoding header. Oops. (Everything tolerated this just
11646 fine, but that doesn't mean we need to be part of the problem.)
11647 - Fix a potential seg fault in getconf and getinfo using version 1
11648 of the controller protocol.
11649 - Avoid crash: do not check whether DirPort is reachable when we
11650 are suppressing it because of hibernation.
11651 - Make --hash-password not crash on exit.
11654 Changes in version 0.1.1.8-alpha - 2005-10-07
11655 o New features (major):
11656 - Clients don't download or use the directory anymore. Now they
11657 download and use network-statuses from the trusted dirservers,
11658 and fetch individual server descriptors as needed from mirrors.
11659 See dir-spec.txt for all the gory details.
11660 - Be more conservative about whether to advertise our DirPort.
11661 The main change is to not advertise if we're running at capacity
11662 and either a) we could hibernate or b) our capacity is low and
11663 we're using a default DirPort.
11664 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
11666 o New features (minor):
11667 - Try to be smart about when to retry network-status and
11668 server-descriptor fetches. Still needs some tuning.
11669 - Stop parsing, storing, or using running-routers output (but
11670 mirrors still cache and serve it).
11671 - Consider a threshold of versioning dirservers (dirservers who have
11672 an opinion about which Tor versions are still recommended) before
11673 deciding whether to warn the user that he's obsolete.
11674 - Dirservers can now reject/invalidate by key and IP, with the
11675 config options "AuthDirInvalid" and "AuthDirReject". This is
11676 useful since currently we automatically list servers as running
11677 and usable even if we know they're jerks.
11678 - Provide dire warnings to any users who set DirServer; move it out
11679 of torrc.sample and into torrc.complete.
11680 - Add MyFamily to torrc.sample in the server section.
11681 - Add nicknames to the DirServer line, so we can refer to them
11682 without requiring all our users to memorize their IP addresses.
11683 - When we get an EOF or a timeout on a directory connection, note
11684 how many bytes of serverdesc we are dropping. This will help
11685 us determine whether it is smart to parse incomplete serverdesc
11687 - Add a new function to "change pseudonyms" -- that is, to stop
11688 using any currently-dirty circuits for new streams, so we don't
11689 link new actions to old actions. Currently it's only called on
11690 HUP (or SIGNAL RELOAD).
11691 - On sighup, if UseHelperNodes changed to 1, use new circuits.
11692 - Start using RAND_bytes rather than RAND_pseudo_bytes from
11693 OpenSSL. Also, reseed our entropy every hour, not just at
11694 startup. And entropy in 512-bit chunks, not 160-bit chunks.
11696 o Fixes on 0.1.1.7-alpha:
11697 - Nobody ever implemented EVENT_ADDRMAP for control protocol
11698 version 0, so don't let version 0 controllers ask for it.
11699 - If you requested something with too many newlines via the
11700 v1 controller protocol, you could crash tor.
11701 - Fix a number of memory leaks, including some pretty serious ones.
11702 - Re-enable DirPort testing again, so Tor servers will be willing
11703 to advertise their DirPort if it's reachable.
11704 - On TLS handshake, only check the other router's nickname against
11705 its expected nickname if is_named is set.
11707 o Fixes forward-ported from 0.1.0.15:
11708 - Don't crash when we don't have any spare file descriptors and we
11709 try to spawn a dns or cpu worker.
11710 - Make the numbers in read-history and write-history into uint64s,
11711 so they don't overflow and publish negatives in the descriptor.
11713 o Fixes on 0.1.0.x:
11714 - For the OS X package's modified privoxy config file, comment
11715 out the "logfile" line so we don't log everything passed
11717 - We were whining about using socks4 or socks5-with-local-lookup
11718 even when it's an IP in the "virtual" range we designed exactly
11720 - We were leaking some memory every time the client changes IPs.
11721 - Never call free() on tor_malloc()d memory. This will help us
11722 use dmalloc to detect memory leaks.
11723 - Check for named servers when looking them up by nickname;
11724 warn when we'recalling a non-named server by its nickname;
11725 don't warn twice about the same name.
11726 - Try to list MyFamily elements by key, not by nickname, and warn
11727 if we've not heard of the server.
11728 - Make windows platform detection (uname equivalent) smarter.
11729 - It turns out sparc64 doesn't like unaligned access either.
11732 Changes in version 0.1.0.15 - 2005-09-23
11733 o Bugfixes on 0.1.0.x:
11734 - Reject ports 465 and 587 (spam targets) in default exit policy.
11735 - Don't crash when we don't have any spare file descriptors and we
11736 try to spawn a dns or cpu worker.
11737 - Get rid of IgnoreVersion undocumented config option, and make us
11738 only warn, never exit, when we're running an obsolete version.
11739 - Don't try to print a null string when your server finds itself to
11740 be unreachable and the Address config option is empty.
11741 - Make the numbers in read-history and write-history into uint64s,
11742 so they don't overflow and publish negatives in the descriptor.
11743 - Fix a minor memory leak in smartlist_string_remove().
11744 - We were only allowing ourselves to upload a server descriptor at
11745 most every 20 minutes, even if it changed earlier than that.
11746 - Clean up log entries that pointed to old URLs.
11749 Changes in version 0.1.1.7-alpha - 2005-09-14
11750 o Fixes on 0.1.1.6-alpha:
11751 - Exit servers were crashing when people asked them to make a
11752 connection to an address not in their exit policy.
11753 - Looking up a non-existent stream for a v1 control connection would
11755 - Fix a seg fault if we ask a dirserver for a descriptor by
11756 fingerprint but he doesn't know about him.
11757 - SETCONF was appending items to linelists, not clearing them.
11758 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
11759 out and refuse the setconf if it would fail.
11760 - Downgrade the dirserver log messages when whining about
11764 - Add Peter Palfrader's check-tor script to tor/contrib/
11765 It lets you easily check whether a given server (referenced by
11766 nickname) is reachable by you.
11767 - Numerous changes to move towards client-side v2 directories. Not
11770 o Fixes on 0.1.0.x:
11771 - If the user gave tor an odd number of command-line arguments,
11772 we were silently ignoring the last one. Now we complain and fail.
11773 [This wins the oldest-bug prize -- this bug has been present since
11774 November 2002, as released in Tor 0.0.0.]
11775 - Do not use unaligned memory access on alpha, mips, or mipsel.
11776 It *works*, but is very slow, so we treat them as if it doesn't.
11777 - Retry directory requests if we fail to get an answer we like
11778 from a given dirserver (we were retrying before, but only if
11779 we fail to connect).
11780 - When writing the RecommendedVersions line, sort them first.
11781 - When the client asked for a rendezvous port that the hidden
11782 service didn't want to provide, we were sending an IP address
11783 back along with the end cell. Fortunately, it was zero. But stop
11785 - Correct "your server is reachable" log entries to indicate that
11786 it was self-testing that told us so.
11789 Changes in version 0.1.1.6-alpha - 2005-09-09
11790 o Fixes on 0.1.1.5-alpha:
11791 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
11792 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
11793 - Fix bug with tor_memmem finding a match at the end of the string.
11794 - Make unit tests run without segfaulting.
11795 - Resolve some solaris x86 compile warnings.
11796 - Handle duplicate lines in approved-routers files without warning.
11797 - Fix bug where as soon as a server refused any requests due to his
11798 exit policy (e.g. when we ask for localhost and he tells us that's
11799 127.0.0.1 and he won't do it), we decided he wasn't obeying his
11800 exit policy using him for any exits.
11801 - Only do openssl hardware accelerator stuff if openssl version is
11804 o New controller features/fixes:
11805 - Add a "RESETCONF" command so you can set config options like
11806 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
11807 a config option in the torrc with no value, then it clears it
11808 entirely (rather than setting it to its default).
11809 - Add a "GETINFO config-file" to tell us where torrc is.
11810 - Avoid sending blank lines when GETINFO replies should be empty.
11811 - Add a QUIT command for the controller (for using it manually).
11812 - Fix a bug in SAVECONF that was adding default dirservers and
11813 other redundant entries to the torrc file.
11815 o Start on the new directory design:
11816 - Generate, publish, cache, serve new network-status format.
11817 - Publish individual descriptors (by fingerprint, by "all", and by
11819 - Publish client and server recommended versions separately.
11820 - Allow tor_gzip_uncompress() to handle multiple concatenated
11821 compressed strings. Serve compressed groups of router
11822 descriptors. The compression logic here could be more
11824 - Distinguish v1 authorities (all currently trusted directories)
11825 from v2 authorities (all trusted directories).
11826 - Change DirServers config line to note which dirs are v1 authorities.
11827 - Add configuration option "V1AuthoritativeDirectory 1" which
11828 moria1, moria2, and tor26 should set.
11829 - Remove option when getting directory cache to see whether they
11830 support running-routers; they all do now. Replace it with one
11831 to see whether caches support v2 stuff.
11834 - Dirservers now do their own external reachability testing of each
11835 Tor server, and only list them as running if they've been found to
11836 be reachable. We also send back warnings to the server's logs if
11837 it uploads a descriptor that we already believe is unreachable.
11838 - Implement exit enclaves: if we know an IP address for the
11839 destination, and there's a running Tor server at that address
11840 which allows exit to the destination, then extend the circuit to
11841 that exit first. This provides end-to-end encryption and end-to-end
11842 authentication. Also, if the user wants a .exit address or enclave,
11843 use 4 hops rather than 3, and cannibalize a general circ for it
11845 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
11846 controller. Also, rotate dns and cpu workers if the controller
11847 changes options that will affect them; and initialize the dns
11848 worker cache tree whether or not we start out as a server.
11849 - Only upload a new server descriptor when options change, 18
11850 hours have passed, uptime is reset, or bandwidth changes a lot.
11851 - Check [X-]Forwarded-For headers in HTTP requests when generating
11852 log messages. This lets people run dirservers (and caches) behind
11853 Apache but still know which IP addresses are causing warnings.
11855 o Config option changes:
11856 - Replace (Fascist)Firewall* config options with a new
11857 ReachableAddresses option that understands address policies.
11858 For example, "ReachableAddresses *:80,*:443"
11859 - Get rid of IgnoreVersion undocumented config option, and make us
11860 only warn, never exit, when we're running an obsolete version.
11861 - Make MonthlyAccountingStart config option truly obsolete now.
11863 o Fixes on 0.1.0.x:
11864 - Reject ports 465 and 587 in the default exit policy, since
11865 people have started using them for spam too.
11866 - It turns out we couldn't bootstrap a network since we added
11867 reachability detection in 0.1.0.1-rc. Good thing the Tor network
11868 has never gone down. Add an AssumeReachable config option to let
11869 servers and dirservers bootstrap. When we're trying to build a
11870 high-uptime or high-bandwidth circuit but there aren't enough
11871 suitable servers, try being less picky rather than simply failing.
11872 - Our logic to decide if the OR we connected to was the right guy
11873 was brittle and maybe open to a mitm for unverified routers.
11874 - We weren't cannibalizing circuits correctly for
11875 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
11876 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
11877 build those from scratch. This should make hidden services faster.
11878 - Predict required circuits better, with an eye toward making hidden
11879 services faster on the service end.
11880 - Retry streams if the exit node sends back a 'misc' failure. This
11881 should result in fewer random failures. Also, after failing
11882 from resolve failed or misc, reset the num failures, so we give
11883 it a fair shake next time we try.
11884 - Clean up the rendezvous warn log msgs, and downgrade some to info.
11885 - Reduce severity on logs about dns worker spawning and culling.
11886 - When we're shutting down and we do something like try to post a
11887 server descriptor or rendezvous descriptor, don't complain that
11888 we seem to be unreachable. Of course we are, we're shutting down.
11889 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
11890 We don't use them yet, but maybe one day our DNS resolver will be
11891 able to discover them.
11892 - Make ContactInfo mandatory for authoritative directory servers.
11893 - Require server descriptors to list IPv4 addresses -- hostnames
11894 are no longer allowed. This also fixes some potential security
11895 problems with people providing hostnames as their address and then
11896 preferentially resolving them to partition users.
11897 - Change log line for unreachability to explicitly suggest /etc/hosts
11898 as the culprit. Also make it clearer what IP address and ports we're
11899 testing for reachability.
11900 - Put quotes around user-supplied strings when logging so users are
11901 more likely to realize if they add bad characters (like quotes)
11903 - Let auth dir servers start without specifying an Address config
11905 - Make unit tests (and other invocations that aren't the real Tor)
11906 run without launching listeners, creating subdirectories, and so on.
11909 Changes in version 0.1.1.5-alpha - 2005-08-08
11910 o Bugfixes included in 0.1.0.14.
11912 o Bugfixes on 0.1.0.x:
11913 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
11914 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
11915 it would silently using ignore the 6668.
11918 Changes in version 0.1.0.14 - 2005-08-08
11919 o Bugfixes on 0.1.0.x:
11920 - Fix the other half of the bug with crypto handshakes
11922 - Fix an assert trigger if you send a 'signal term' via the
11923 controller when it's listening for 'event info' messages.
11926 Changes in version 0.1.1.4-alpha - 2005-08-04
11927 o Bugfixes included in 0.1.0.13.
11930 - Improve tor_gettimeofday() granularity on windows.
11931 - Make clients regenerate their keys when their IP address changes.
11932 - Implement some more GETINFO goodness: expose helper nodes, config
11933 options, getinfo keys.
11936 Changes in version 0.1.0.13 - 2005-08-04
11937 o Bugfixes on 0.1.0.x:
11938 - Fix a critical bug in the security of our crypto handshakes.
11939 - Fix a size_t underflow in smartlist_join_strings2() that made
11940 it do bad things when you hand it an empty smartlist.
11941 - Fix Windows installer to ship Tor license (thanks to Aphex for
11942 pointing out this oversight) and put a link to the doc directory
11944 - Explicitly set no-unaligned-access for sparc: it turns out the
11945 new gcc's let you compile broken code, but that doesn't make it
11949 Changes in version 0.1.1.3-alpha - 2005-07-23
11950 o Bugfixes on 0.1.1.2-alpha:
11951 - Fix a bug in handling the controller's "post descriptor"
11953 - Fix several bugs in handling the controller's "extend circuit"
11955 - Fix a bug in handling the controller's "stream status" event.
11956 - Fix an assert failure if we have a controller listening for
11957 circuit events and we go offline.
11958 - Re-allow hidden service descriptors to publish 0 intro points.
11959 - Fix a crash when generating your hidden service descriptor if
11960 you don't have enough intro points already.
11962 o New features on 0.1.1.2-alpha:
11963 - New controller function "getinfo accounting", to ask how
11964 many bytes we've used in this time period.
11965 - Experimental support for helper nodes: a lot of the risk from
11966 a small static adversary comes because users pick new random
11967 nodes every time they rebuild a circuit. Now users will try to
11968 stick to the same small set of entry nodes if they can. Not
11969 enabled by default yet.
11971 o Bugfixes on 0.1.0.12:
11972 - If you're an auth dir server, always publish your dirport,
11973 even if you haven't yet found yourself to be reachable.
11974 - Fix a size_t underflow in smartlist_join_strings2() that made
11975 it do bad things when you hand it an empty smartlist.
11978 Changes in version 0.1.0.12 - 2005-07-18
11979 o New directory servers:
11980 - tor26 has changed IP address.
11982 o Bugfixes on 0.1.0.x:
11983 - Fix a possible double-free in tor_gzip_uncompress().
11984 - When --disable-threads is set, do not search for or link against
11985 pthreads libraries.
11986 - Don't trigger an assert if an authoritative directory server
11987 claims its dirport is 0.
11988 - Fix bug with removing Tor as an NT service: some people were
11989 getting "The service did not return an error." Thanks to Matt
11993 Changes in version 0.1.1.2-alpha - 2005-07-15
11994 o New directory servers:
11995 - tor26 has changed IP address.
11997 o Bugfixes on 0.1.0.x, crashes/leaks:
11998 - Port the servers-not-obeying-their-exit-policies fix from
12000 - Fix an fd leak in start_daemon().
12001 - On Windows, you can't always reopen a port right after you've
12002 closed it. So change retry_listeners() to only close and re-open
12003 ports that have changed.
12004 - Fix a possible double-free in tor_gzip_uncompress().
12006 o Bugfixes on 0.1.0.x, usability:
12007 - When tor_socketpair() fails in Windows, give a reasonable
12008 Windows-style errno back.
12009 - Let people type "tor --install" as well as "tor -install" when
12011 want to make it an NT service.
12012 - NT service patch from Matt Edman to improve error messages.
12013 - When the controller asks for a config option with an abbreviated
12014 name, give the full name in our response.
12015 - Correct the man page entry on TrackHostExitsExpire.
12016 - Looks like we were never delivering deflated (i.e. compressed)
12017 running-routers lists, even when asked. Oops.
12018 - When --disable-threads is set, do not search for or link against
12019 pthreads libraries.
12021 o Bugfixes on 0.1.1.x:
12022 - Fix a seg fault with autodetecting which controller version is
12026 - New hidden service descriptor format: put a version in it, and
12027 let people specify introduction/rendezvous points that aren't
12028 in "the directory" (which is subjective anyway).
12029 - Allow the DEBUG controller event to work again. Mark certain log
12030 entries as "don't tell this to controllers", so we avoid cycles.
12033 Changes in version 0.1.0.11 - 2005-06-30
12034 o Bugfixes on 0.1.0.x:
12035 - Fix major security bug: servers were disregarding their
12036 exit policies if clients behaved unexpectedly.
12037 - Make OS X init script check for missing argument, so we don't
12038 confuse users who invoke it incorrectly.
12039 - Fix a seg fault in "tor --hash-password foo".
12040 - The MAPADDRESS control command was broken.
12043 Changes in version 0.1.1.1-alpha - 2005-06-29
12045 - Make OS X init script check for missing argument, so we don't
12046 confuse users who invoke it incorrectly.
12047 - Fix a seg fault in "tor --hash-password foo".
12048 - Fix a possible way to DoS dirservers.
12049 - When we complain that your exit policy implicitly allows local or
12050 private address spaces, name them explicitly so operators can
12052 - Make the log message less scary when all the dirservers are
12053 temporarily unreachable.
12054 - We were printing the number of idle dns workers incorrectly when
12058 - Revised controller protocol (version 1) that uses ascii rather
12059 than binary. Add supporting libraries in python and java so you
12060 can use the controller from your applications without caring how
12061 our protocol works.
12062 - Spiffy new support for crypto hardware accelerators. Can somebody
12066 Changes in version 0.0.9.10 - 2005-06-16
12067 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
12068 - Refuse relay cells that claim to have a length larger than the
12069 maximum allowed. This prevents a potential attack that could read
12070 arbitrary memory (e.g. keys) from an exit server's process
12074 Changes in version 0.1.0.10 - 2005-06-14
12075 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
12076 libevent before 1.1a.
12079 Changes in version 0.1.0.9-rc - 2005-06-09
12081 - Reset buf->highwater every time buf_shrink() is called, not just on
12082 a successful shrink. This was causing significant memory bloat.
12083 - Fix buffer overflow when checking hashed passwords.
12084 - Security fix: if seeding the RNG on Win32 fails, quit.
12085 - Allow seeding the RNG on Win32 even when you're not running as
12087 - Disable threading on Solaris too. Something is wonky with it,
12088 cpuworkers, and reentrant libs.
12089 - Reenable the part of the code that tries to flush as soon as an
12090 OR outbuf has a full TLS record available. Perhaps this will make
12091 OR outbufs not grow as huge except in rare cases, thus saving lots
12092 of CPU time plus memory.
12093 - Reject malformed .onion addresses rather then passing them on as
12094 normal web requests.
12095 - Adapt patch from Adam Langley: fix possible memory leak in
12096 tor_lookup_hostname().
12097 - Initialize libevent later in the startup process, so the logs are
12098 already established by the time we start logging libevent warns.
12099 - Use correct errno on win32 if libevent fails.
12100 - Check and warn about known-bad/slow libevent versions.
12101 - Pay more attention to the ClientOnly config option.
12102 - Have torctl.in/tor.sh.in check for location of su binary (needed
12104 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
12105 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
12106 HttpProxyAuthenticator
12107 - Stop warning about sigpipes in the logs. We're going to
12108 pretend that getting these occassionally is normal and fine.
12109 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
12111 installer screens; and don't put stuff into StartupItems unless
12112 the user asks you to.
12113 - Require servers that use the default dirservers to have public IP
12114 addresses. We have too many servers that are configured with private
12115 IPs and their admins never notice the log entries complaining that
12116 their descriptors are being rejected.
12117 - Add OSX uninstall instructions. An actual uninstall script will
12121 Changes in version 0.1.0.8-rc - 2005-05-23
12123 - It turns out that kqueue on OS X 10.3.9 was causing kernel
12124 panics. Disable kqueue on all OS X Tors.
12125 - Fix RPM: remove duplicate line accidentally added to the rpm
12127 - Disable threads on openbsd too, since its gethostaddr is not
12129 - Tolerate libevent 0.8 since it still works, even though it's
12131 - Enable building on Red Hat 9.0 again.
12132 - Allow the middle hop of the testing circuit to be running any
12133 version, now that most of them have the bugfix to let them connect
12134 to unknown servers. This will allow reachability testing to work
12135 even when 0.0.9.7-0.0.9.9 become obsolete.
12136 - Handle relay cells with rh.length too large. This prevents
12137 a potential attack that could read arbitrary memory (maybe even
12138 keys) from the exit server's process.
12139 - We screwed up the dirport reachability testing when we don't yet
12140 have a cached version of the directory. Hopefully now fixed.
12141 - Clean up router_load_single_router() (used by the controller),
12142 so it doesn't seg fault on error.
12143 - Fix a minor memory leak when somebody establishes an introduction
12144 point at your Tor server.
12145 - If a socks connection ends because read fails, don't warn that
12146 you're not sending a socks reply back.
12149 - Add HttpProxyAuthenticator config option too, that works like
12150 the HttpsProxyAuthenticator config option.
12151 - Encode hashed controller passwords in hex instead of base64,
12152 to make it easier to write controllers.
12155 Changes in version 0.1.0.7-rc - 2005-05-17
12157 - Fix a bug in the OS X package installer that prevented it from
12158 installing on Tiger.
12159 - Fix a script bug in the OS X package installer that made it
12160 complain during installation.
12161 - Find libevent even if it's hiding in /usr/local/ and your
12162 CFLAGS and LDFLAGS don't tell you to look there.
12163 - Be able to link with libevent as a shared library (the default
12164 after 1.0d), even if it's hiding in /usr/local/lib and even
12165 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
12166 assuming you're running gcc. Otherwise fail and give a useful
12168 - Fix a bug in the RPM packager: set home directory for _tor to
12169 something more reasonable when first installing.
12170 - Free a minor amount of memory that is still reachable on exit.
12173 Changes in version 0.1.0.6-rc - 2005-05-14
12175 - Implement --disable-threads configure option. Disable threads on
12176 netbsd by default, because it appears to have no reentrant resolver
12178 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
12179 release (1.1) detects and disables kqueue if it's broken.
12180 - Append default exit policy before checking for implicit internal
12181 addresses. Now we don't log a bunch of complaints on startup
12182 when using the default exit policy.
12183 - Some people were putting "Address " in their torrc, and they had
12184 a buggy resolver that resolved " " to 0.0.0.0. Oops.
12185 - If DataDir is ~/.tor, and that expands to /.tor, then default to
12186 LOCALSTATEDIR/tor instead.
12187 - Fix fragmented-message bug in TorControl.py.
12188 - Resolve a minor bug which would prevent unreachable dirports
12189 from getting suppressed in the published descriptor.
12190 - When the controller gave us a new descriptor, we weren't resolving
12191 it immediately, so Tor would think its address was 0.0.0.0 until
12192 we fetched a new directory.
12193 - Fix an uppercase/lowercase case error in suppressing a bogus
12194 libevent warning on some Linuxes.
12197 - Begin scrubbing sensitive strings from logs by default. Turn off
12198 the config option SafeLogging if you need to do debugging.
12199 - Switch to a new buffer management algorithm, which tries to avoid
12200 reallocing and copying quite as much. In first tests it looks like
12201 it uses *more* memory on average, but less cpu.
12202 - First cut at support for "create-fast" cells. Clients can use
12203 these when extending to their first hop, since the TLS already
12204 provides forward secrecy and authentication. Not enabled on
12206 - When dirservers refuse a router descriptor, we now log its
12207 contactinfo, platform, and the poster's IP address.
12208 - Call tor_free_all instead of connections_free_all after forking, to
12209 save memory on systems that need to fork.
12210 - Whine at you if you're a server and you don't set your contactinfo.
12211 - Implement --verify-config command-line option to check if your torrc
12212 is valid without actually launching Tor.
12213 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
12214 rather than just rejecting it.
12217 Changes in version 0.1.0.5-rc - 2005-04-27
12219 - Stop trying to print a null pointer if an OR conn fails because
12220 we didn't like its cert.
12222 - Switch our internal buffers implementation to use a ring buffer,
12223 to hopefully improve performance for fast servers a lot.
12224 - Add HttpsProxyAuthenticator support (basic auth only), based
12225 on patch from Adam Langley.
12226 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
12227 the fast servers that have been joining lately.
12228 - Give hidden service accesses extra time on the first attempt,
12229 since 60 seconds is often only barely enough. This might improve
12231 - Improve performance for dirservers: stop re-parsing the whole
12232 directory every time you regenerate it.
12233 - Add more debugging info to help us find the weird dns freebsd
12234 pthreads bug; cleaner debug messages to help track future issues.
12237 Changes in version 0.0.9.9 - 2005-04-23
12238 o Bugfixes on 0.0.9.x:
12239 - If unofficial Tor clients connect and send weird TLS certs, our
12240 Tor server triggers an assert. This release contains a minimal
12241 backport from the broader fix that we put into 0.1.0.4-rc.
12244 Changes in version 0.1.0.4-rc - 2005-04-23
12246 - If unofficial Tor clients connect and send weird TLS certs, our
12247 Tor server triggers an assert. Stop asserting, and start handling
12248 TLS errors better in other situations too.
12249 - When the controller asks us to tell it about all the debug-level
12250 logs, it turns out we were generating debug-level logs while
12251 telling it about them, which turns into a bad loop. Now keep
12252 track of whether you're sending a debug log to the controller,
12253 and don't log when you are.
12254 - Fix the "postdescriptor" feature of the controller interface: on
12255 non-complete success, only say "done" once.
12257 - Clients are now willing to load balance over up to 2mB, not 1mB,
12258 of advertised bandwidth capacity.
12259 - Add a NoPublish config option, so you can be a server (e.g. for
12260 testing running Tor servers in other Tor networks) without
12261 publishing your descriptor to the primary dirservers.
12264 Changes in version 0.1.0.3-rc - 2005-04-08
12265 o Improvements on 0.1.0.2-rc:
12266 - Client now retries when streams end early for 'hibernating' or
12267 'resource limit' reasons, rather than failing them.
12268 - More automated handling for dirserver operators:
12269 - Automatically approve nodes running 0.1.0.2-rc or later,
12270 now that the the reachability detection stuff is working.
12271 - Now we allow two unverified servers with the same nickname
12272 but different keys. But if a nickname is verified, only that
12273 nickname+key are allowed.
12274 - If you're an authdirserver connecting to an address:port,
12275 and it's not the OR you were expecting, forget about that
12276 descriptor. If he *was* the one you were expecting, then forget
12277 about all other descriptors for that address:port.
12278 - Allow servers to publish descriptors from 12 hours in the future.
12279 Corollary: only whine about clock skew from the dirserver if
12280 he's a trusted dirserver (since now even verified servers could
12281 have quite wrong clocks).
12282 - Adjust maximum skew and age for rendezvous descriptors: let skew
12283 be 48 hours rather than 90 minutes.
12284 - Efficiency improvements:
12285 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
12286 it much faster to look up a circuit for each relay cell.
12287 - Remove most calls to assert_all_pending_dns_resolves_ok(),
12288 since they're eating our cpu on exit nodes.
12289 - Stop wasting time doing a case insensitive comparison for every
12290 dns name every time we do any lookup. Canonicalize the names to
12291 lowercase and be done with it.
12292 - Start sending 'truncated' cells back rather than destroy cells,
12293 if the circuit closes in front of you. This means we won't have
12294 to abandon partially built circuits.
12295 - Only warn once per nickname from add_nickname_list_to_smartlist
12296 per failure, so an entrynode or exitnode choice that's down won't
12298 - Put a note in the torrc about abuse potential with the default
12300 - Revise control spec and implementation to allow all log messages to
12301 be sent to controller with their severities intact (suggested by
12302 Matt Edman). Update TorControl to handle new log event types.
12303 - Provide better explanation messages when controller's POSTDESCRIPTOR
12305 - Stop putting nodename in the Platform string in server descriptors.
12306 It doesn't actually help, and it is confusing/upsetting some people.
12308 o Bugfixes on 0.1.0.2-rc:
12309 - We were printing the host mask wrong in exit policies in server
12310 descriptors. This isn't a critical bug though, since we were still
12311 obeying the exit policy internally.
12312 - Fix Tor when compiled with libevent but without pthreads: move
12313 connection_unregister() from _connection_free() to
12315 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
12316 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
12317 when we look through the connection array, we'll find any of the
12318 cpu/dnsworkers. This is no good.
12320 o Bugfixes on 0.0.9.8:
12321 - Fix possible bug on threading platforms (e.g. win32) which was
12322 leaking a file descriptor whenever a cpuworker or dnsworker died.
12323 - When using preferred entry or exit nodes, ignore whether the
12324 circuit wants uptime or capacity. They asked for the nodes, they
12326 - chdir() to your datadirectory at the *end* of the daemonize process,
12327 not the beginning. This was a problem because the first time you
12328 run tor, if your datadir isn't there, and you have runasdaemon set
12329 to 1, it will try to chdir to it before it tries to create it. Oops.
12330 - Handle changed router status correctly when dirserver reloads
12331 fingerprint file. We used to be dropping all unverified descriptors
12332 right then. The bug was hidden because we would immediately
12333 fetch a directory from another dirserver, which would include the
12334 descriptors we just dropped.
12335 - When we're connecting to an OR and he's got a different nickname/key
12336 than we were expecting, only complain loudly if we're an OP or a
12337 dirserver. Complaining loudly to the OR admins just confuses them.
12338 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
12339 artificially capped at 500kB.
12342 Changes in version 0.0.9.8 - 2005-04-07
12343 o Bugfixes on 0.0.9.x:
12344 - We have a bug that I haven't found yet. Sometimes, very rarely,
12345 cpuworkers get stuck in the 'busy' state, even though the cpuworker
12346 thinks of itself as idle. This meant that no new circuits ever got
12347 established. Here's a workaround to kill any cpuworker that's been
12348 busy for more than 100 seconds.
12351 Changes in version 0.1.0.2-rc - 2005-04-01
12352 o Bugfixes on 0.1.0.1-rc:
12353 - Fixes on reachability detection:
12354 - Don't check for reachability while hibernating.
12355 - If ORPort is reachable but DirPort isn't, still publish the
12356 descriptor, but zero out DirPort until it's found reachable.
12357 - When building testing circs for ORPort testing, use only
12358 high-bandwidth nodes, so fewer circuits fail.
12359 - Complain about unreachable ORPort separately from unreachable
12360 DirPort, so the user knows what's going on.
12361 - Make sure we only conclude ORPort reachability if we didn't
12362 initiate the conn. Otherwise we could falsely conclude that
12363 we're reachable just because we connected to the guy earlier
12364 and he used that same pipe to extend to us.
12365 - Authdirservers shouldn't do ORPort reachability detection,
12366 since they're in clique mode, so it will be rare to find a
12367 server not already connected to them.
12368 - When building testing circuits, always pick middle hops running
12369 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
12370 bug. (This is a kludge; it will go away when 0.0.9.x becomes
12372 - When we decide we're reachable, actually publish our descriptor
12374 - Fix bug in redirectstream in the controller.
12375 - Fix the state descriptor strings so logs don't claim edge streams
12376 are in a different state than they actually are.
12377 - Use recent libevent features when possible (this only really affects
12378 win32 and osx right now, because the new libevent with these
12379 features hasn't been released yet). Add code to suppress spurious
12381 - Prevent possible segfault in connection_close_unattached_ap().
12382 - Fix newlines on torrc in win32.
12383 - Improve error msgs when tor-resolve fails.
12385 o Improvements on 0.0.9.x:
12386 - New experimental script tor/contrib/ExerciseServer.py (needs more
12387 work) that uses the controller interface to build circuits and
12388 fetch pages over them. This will help us bootstrap servers that
12389 have lots of capacity but haven't noticed it yet.
12390 - New experimental script tor/contrib/PathDemo.py (needs more work)
12391 that uses the controller interface to let you choose whole paths
12393 "<hostname>.<path,separated by dots>.<length of path>.path"
12394 - When we've connected to an OR and handshaked but didn't like
12395 the result, we were closing the conn without sending destroy
12396 cells back for pending circuits. Now send those destroys.
12399 Changes in version 0.0.9.7 - 2005-04-01
12400 o Bugfixes on 0.0.9.x:
12401 - Fix another race crash bug (thanks to Glenn Fink for reporting).
12402 - Compare identity to identity, not to nickname, when extending to
12403 a router not already in the directory. This was preventing us from
12404 extending to unknown routers. Oops.
12405 - Make sure to create OS X Tor user in <500 range, so we aren't
12406 creating actual system users.
12407 - Note where connection-that-hasn't-sent-end was marked, and fix
12408 a few really loud instances of this harmless bug (it's fixed more
12412 Changes in version 0.1.0.1-rc - 2005-03-28
12414 - Add reachability testing. Your Tor server will automatically try
12415 to see if its ORPort and DirPort are reachable from the outside,
12416 and it won't upload its descriptor until it decides they are.
12417 - Handle unavailable hidden services better. Handle slow or busy
12418 hidden services better.
12419 - Add support for CONNECTing through https proxies, with "HttpsProxy"
12421 - New exit policy: accept most low-numbered ports, rather than
12422 rejecting most low-numbered ports.
12423 - More Tor controller support (still experimental). See
12424 http://tor.eff.org/doc/control-spec.txt for all the new features,
12425 including signals to emulate unix signals from any platform;
12426 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
12427 closestream; closecircuit; etc.
12428 - Make nt services work and start on startup on win32 (based on
12429 patch by Matt Edman).
12430 - Add a new AddressMap config directive to rewrite incoming socks
12431 addresses. This lets you, for example, declare an implicit
12432 required exit node for certain sites.
12433 - Add a new TrackHostExits config directive to trigger addressmaps
12434 for certain incoming socks addresses -- for sites that break when
12435 your exit keeps changing (based on patch by Mike Perry).
12436 - Redo the client-side dns cache so it's just an addressmap too.
12437 - Notice when our IP changes, and reset stats/uptime/reachability.
12438 - When an application is using socks5, give him the whole variety of
12439 potential socks5 responses (connect refused, host unreachable, etc),
12440 rather than just "success" or "failure".
12441 - A more sane version numbering system. See
12442 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
12443 - New contributed script "exitlist": a simple python script to
12444 parse directories and find Tor nodes that exit to listed
12446 - New contributed script "privoxy-tor-toggle" to toggle whether
12447 Privoxy uses Tor. Seems to be configured for Debian by default.
12448 - Report HTTP reasons to client when getting a response from directory
12449 servers -- so you can actually know what went wrong.
12450 - New config option MaxAdvertisedBandwidth which lets you advertise
12451 a low bandwidthrate (to not attract as many circuits) while still
12452 allowing a higher bandwidthrate in reality.
12454 o Robustness/stability fixes:
12455 - Make Tor use Niels Provos's libevent instead of its current
12456 poll-but-sometimes-select mess. This will let us use faster async
12457 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
12459 - pthread support now too. This was forced because when we forked,
12460 we ended up wasting a lot of duplicate ram over time. Also switch
12461 to foo_r versions of some library calls to allow reentry and
12463 - Better handling for heterogeneous / unreliable nodes:
12464 - Annotate circuits w/ whether they aim to contain high uptime nodes
12465 and/or high capacity nodes. When building circuits, choose
12467 - This means that every single node in an intro rend circuit,
12468 not just the last one, will have a minimum uptime.
12469 - New config option LongLivedPorts to indicate application streams
12470 that will want high uptime circuits.
12471 - Servers reset uptime when a dir fetch entirely fails. This
12472 hopefully reflects stability of the server's network connectivity.
12473 - If somebody starts his tor server in Jan 2004 and then fixes his
12474 clock, don't make his published uptime be a year.
12475 - Reset published uptime when you wake up from hibernation.
12476 - Introduce a notion of 'internal' circs, which are chosen without
12477 regard to the exit policy of the last hop. Intro and rendezvous
12478 circs must be internal circs, to avoid leaking information. Resolve
12479 and connect streams can use internal circs if they want.
12480 - New circuit pooling algorithm: make sure to have enough circs around
12481 to satisfy any predicted ports, and also make sure to have 2 internal
12482 circs around if we've required internal circs lately (and with high
12483 uptime if we've seen that lately too).
12484 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
12485 which describes how often we retry making new circuits if current
12486 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
12487 how long we're willing to make use of an already-dirty circuit.
12488 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
12489 circ as necessary, if there are any completed ones lying around
12490 when we try to launch one.
12491 - Make hidden services try to establish a rendezvous for 30 seconds,
12492 rather than for n (where n=3) attempts to build a circuit.
12493 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
12494 "ShutdownWaitLength".
12495 - Try to be more zealous about calling connection_edge_end when
12496 things go bad with edge conns in connection.c.
12497 - Revise tor-spec to add more/better stream end reasons.
12498 - Revise all calls to connection_edge_end to avoid sending "misc",
12499 and to take errno into account where possible.
12502 - Fix a race condition that can trigger an assert, when we have a
12503 pending create cell and an OR connection fails right then.
12504 - Fix several double-mark-for-close bugs, e.g. where we were finding
12505 a conn for a cell even if that conn is already marked for close.
12506 - Make sequence of log messages when starting on win32 with no config
12507 file more reasonable.
12508 - When choosing an exit node for a new non-internal circ, don't take
12509 into account whether it'll be useful for any pending x.onion
12510 addresses -- it won't.
12511 - Turn addr_policy_compare from a tristate to a quadstate; this should
12512 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
12513 for google.com" problem.
12514 - Make "platform" string in descriptor more accurate for Win32 servers,
12515 so it's not just "unknown platform".
12516 - Fix an edge case in parsing config options (thanks weasel).
12517 If they say "--" on the commandline, it's not an option.
12518 - Reject odd-looking addresses at the client (e.g. addresses that
12519 contain a colon), rather than having the server drop them because
12521 - tor-resolve requests were ignoring .exit if there was a working circuit
12522 they could use instead.
12523 - REUSEADDR on normal platforms means you can rebind to the port
12524 right after somebody else has let it go. But REUSEADDR on win32
12525 means to let you bind to the port _even when somebody else
12526 already has it bound_! So, don't do that on Win32.
12527 - Change version parsing logic: a version is "obsolete" if it is not
12528 recommended and (1) there is a newer recommended version in the
12529 same series, or (2) there are no recommended versions in the same
12530 series, but there are some recommended versions in a newer series.
12531 A version is "new" if it is newer than any recommended version in
12533 - Stop most cases of hanging up on a socks connection without sending
12537 - Require BandwidthRate to be at least 20kB/s for servers.
12538 - When a dirserver causes you to give a warn, mention which dirserver
12540 - New config option DirAllowPrivateAddresses for authdirservers.
12541 Now by default they refuse router descriptors that have non-IP or
12542 private-IP addresses.
12543 - Stop publishing socksport in the directory, since it's not
12544 actually meant to be public. For compatibility, publish a 0 there
12546 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
12547 smart" value, that is low for servers and high for clients.
12548 - If our clock jumps forward by 100 seconds or more, assume something
12549 has gone wrong with our network and abandon all not-yet-used circs.
12550 - Warn when exit policy implicitly allows local addresses.
12551 - If we get an incredibly skewed timestamp from a dirserver mirror
12552 that isn't a verified OR, don't warn -- it's probably him that's
12554 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
12555 cookies to disk and doesn't log each web request to disk. (Thanks
12556 to Brett Carrington for pointing this out.)
12557 - When a client asks us for a dir mirror and we don't have one,
12558 launch an attempt to get a fresh one.
12559 - If we're hibernating and we get a SIGINT, exit immediately.
12560 - Add --with-dmalloc ./configure option, to track memory leaks.
12561 - And try to free all memory on closing, so we can detect what
12563 - Cache local dns resolves correctly even when they're .exit
12565 - Give a better warning when some other server advertises an
12566 ORPort that is actually an apache running ssl.
12567 - Add "opt hibernating 1" to server descriptor to make it clearer
12568 whether the server is hibernating.
12571 Changes in version 0.0.9.6 - 2005-03-24
12572 o Bugfixes on 0.0.9.x (crashes and asserts):
12573 - Add new end stream reasons to maintainance branch. Fix bug where
12574 reason (8) could trigger an assert. Prevent bug from recurring.
12575 - Apparently win32 stat wants paths to not end with a slash.
12576 - Fix assert triggers in assert_cpath_layer_ok(), where we were
12577 blowing away the circuit that conn->cpath_layer points to, then
12578 checking to see if the circ is well-formed. Backport check to make
12579 sure we dont use the cpath on a closed connection.
12580 - Prevent circuit_resume_edge_reading_helper() from trying to package
12581 inbufs for marked-for-close streams.
12582 - Don't crash on hup if your options->address has become unresolvable.
12583 - Some systems (like OS X) sometimes accept() a connection and tell
12584 you the remote host is 0.0.0.0:0. If this happens, due to some
12585 other mis-features, we get confused; so refuse the conn for now.
12587 o Bugfixes on 0.0.9.x (other):
12588 - Fix harmless but scary "Unrecognized content encoding" warn message.
12589 - Add new stream error reason: TORPROTOCOL reason means "you are not
12590 speaking a version of Tor I understand; say bye-bye to your stream."
12591 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
12592 into the future, now that we are more tolerant of skew. This
12593 resolves a bug where a Tor server would refuse to cache a directory
12594 because all the directories it gets are too far in the future;
12595 yet the Tor server never logs any complaints about clock skew.
12596 - Mac packaging magic: make man pages useable, and do not overwrite
12597 existing torrc files.
12598 - Make OS X log happily to /var/log/tor/tor.log
12601 Changes in version 0.0.9.5 - 2005-02-22
12602 o Bugfixes on 0.0.9.x:
12603 - Fix an assert race at exit nodes when resolve requests fail.
12604 - Stop picking unverified dir mirrors--it only leads to misery.
12605 - Patch from Matt Edman to make NT services work better. Service
12606 support is still not compiled into the executable by default.
12607 - Patch from Dmitri Bely so the Tor service runs better under
12608 the win32 SYSTEM account.
12609 - Make tor-resolve actually work (?) on Win32.
12610 - Fix a sign bug when getrlimit claims to have 4+ billion
12611 file descriptors available.
12612 - Stop refusing to start when bandwidthburst == bandwidthrate.
12613 - When create cells have been on the onion queue more than five
12614 seconds, just send back a destroy and take them off the list.
12617 Changes in version 0.0.9.4 - 2005-02-03
12618 o Bugfixes on 0.0.9:
12619 - Fix an assert bug that took down most of our servers: when
12620 a server claims to have 1 GB of bandwidthburst, don't
12622 - Don't crash as badly if we have spawned the max allowed number
12623 of dnsworkers, or we're out of file descriptors.
12624 - Block more file-sharing ports in the default exit policy.
12625 - MaxConn is now automatically set to the hard limit of max
12626 file descriptors we're allowed (ulimit -n), minus a few for
12628 - Give a clearer message when servers need to raise their
12629 ulimit -n when they start running out of file descriptors.
12630 - SGI Compatibility patches from Jan Schaumann.
12631 - Tolerate a corrupt cached directory better.
12632 - When a dirserver hasn't approved your server, list which one.
12633 - Go into soft hibernation after 95% of the bandwidth is used,
12634 not 99%. This is especially important for daily hibernators who
12635 have a small accounting max. Hopefully it will result in fewer
12636 cut connections when the hard hibernation starts.
12637 - Load-balance better when using servers that claim more than
12638 800kB/s of capacity.
12639 - Make NT services work (experimental, only used if compiled in).
12642 Changes in version 0.0.9.3 - 2005-01-21
12643 o Bugfixes on 0.0.9:
12644 - Backport the cpu use fixes from main branch, so busy servers won't
12645 need as much processor time.
12646 - Work better when we go offline and then come back, or when we
12647 run Tor at boot before the network is up. We do this by
12648 optimistically trying to fetch a new directory whenever an
12649 application request comes in and we think we're offline -- the
12650 human is hopefully a good measure of when the network is back.
12651 - Backport some minimal hidserv bugfixes: keep rend circuits open as
12652 long as you keep using them; actually publish hidserv descriptors
12653 shortly after they change, rather than waiting 20-40 minutes.
12654 - Enable Mac startup script by default.
12655 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
12656 - When you update AllowUnverifiedNodes or FirewallPorts via the
12657 controller's setconf feature, we were always appending, never
12659 - When you update HiddenServiceDir via setconf, it was screwing up
12660 the order of reading the lines, making it fail.
12661 - Do not rewrite a cached directory back to the cache; otherwise we
12662 will think it is recent and not fetch a newer one on startup.
12663 - Workaround for webservers that lie about Content-Encoding: Tor
12664 now tries to autodetect compressed directories and compression
12665 itself. This lets us Proxypass dir fetches through apache.
12668 Changes in version 0.0.9.2 - 2005-01-04
12669 o Bugfixes on 0.0.9 (crashes and asserts):
12670 - Fix an assert on startup when the disk is full and you're logging
12672 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
12673 style address, then we'd crash.
12674 - Fix an assert trigger when the running-routers string we get from
12675 a dirserver is broken.
12676 - Make worker threads start and run on win32. Now win32 servers
12678 - Bandaid (not actually fix, but now it doesn't crash) an assert
12679 where the dns worker dies mysteriously and the main Tor process
12680 doesn't remember anything about the address it was resolving.
12682 o Bugfixes on 0.0.9 (Win32):
12683 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
12684 name out of the warning/assert messages.
12685 - Fix a superficial "unhandled error on read" bug on win32.
12686 - The win32 installer no longer requires a click-through for our
12687 license, since our Free Software license grants rights but does not
12689 - Win32: When connecting to a dirserver fails, try another one
12690 immediately. (This was already working for non-win32 Tors.)
12691 - Stop trying to parse $HOME on win32 when hunting for default
12693 - Make tor-resolve.c work on win32 by calling network_init().
12695 o Bugfixes on 0.0.9 (other):
12696 - Make 0.0.9.x build on Solaris again.
12697 - Due to a fencepost error, we were blowing away the \n when reporting
12698 confvalue items in the controller. So asking for multiple config
12699 values at once couldn't work.
12700 - When listing circuits that are pending on an opening OR connection,
12701 if we're an OR we were listing circuits that *end* at us as
12702 being pending on every listener, dns/cpu worker, etc. Stop that.
12703 - Dirservers were failing to create 'running-routers' or 'directory'
12704 strings if we had more than some threshold of routers. Fix them so
12705 they can handle any number of routers.
12706 - Fix a superficial "Duplicate mark for close" bug.
12707 - Stop checking for clock skew for OR connections, even for servers.
12708 - Fix a fencepost error that was chopping off the last letter of any
12709 nickname that is the maximum allowed nickname length.
12710 - Update URLs in log messages so they point to the new website.
12711 - Fix a potential problem in mangling server private keys while
12712 writing to disk (not triggered yet, as far as we know).
12713 - Include the licenses for other free software we include in Tor,
12714 now that we're shipping binary distributions more regularly.
12717 Changes in version 0.0.9.1 - 2004-12-15
12718 o Bugfixes on 0.0.9:
12719 - Make hibernation actually work.
12720 - Make HashedControlPassword config option work.
12721 - When we're reporting event circuit status to a controller,
12722 don't use the stream status code.
12725 Changes in version 0.0.9 - 2004-12-12
12727 - Clean up manpage and torrc.sample file.
12728 - Clean up severities and text of log warnings.
12730 - Make servers trigger an assert when they enter hibernation.
12733 Changes in version 0.0.9rc7 - 2004-12-08
12734 o Bugfixes on 0.0.9rc:
12735 - Fix a stack-trashing crash when an exit node begins hibernating.
12736 - Avoid looking at unallocated memory while considering which
12737 ports we need to build circuits to cover.
12738 - Stop a sigpipe: when an 'end' cell races with eof from the app,
12739 we shouldn't hold-open-until-flush if the eof arrived first.
12740 - Fix a bug with init_cookie_authentication() in the controller.
12741 - When recommending new-format log lines, if the upper bound is
12742 LOG_ERR, leave it implicit.
12744 o Bugfixes on 0.0.8.1:
12745 - Fix a whole slew of memory leaks.
12746 - Fix isspace() and friends so they still make Solaris happy
12747 but also so they don't trigger asserts on win32.
12748 - Fix parse_iso_time on platforms without strptime (eg win32).
12749 - win32: tolerate extra "readable" events better.
12750 - win32: when being multithreaded, leave parent fdarray open.
12751 - Make unit tests work on win32.
12754 Changes in version 0.0.9rc6 - 2004-12-06
12755 o Bugfixes on 0.0.9pre:
12756 - Clean up some more integer underflow opportunities (not exploitable
12758 - While hibernating, hup should not regrow our listeners.
12759 - Send an end to the streams we close when we hibernate, rather
12760 than just chopping them off.
12761 - React to eof immediately on non-open edge connections.
12763 o Bugfixes on 0.0.8.1:
12764 - Calculate timeout for waiting for a connected cell from the time
12765 we sent the begin cell, not from the time the stream started. If
12766 it took a long time to establish the circuit, we would time out
12767 right after sending the begin cell.
12768 - Fix router_compare_addr_to_addr_policy: it was not treating a port
12769 of * as always matching, so we were picking reject *:* nodes as
12770 exit nodes too. Oops.
12773 - New circuit building strategy: keep a list of ports that we've
12774 used in the past 6 hours, and always try to have 2 circuits open
12775 or on the way that will handle each such port. Seed us with port
12776 80 so web users won't complain that Tor is "slow to start up".
12777 - Make kill -USR1 dump more useful stats about circuits.
12778 - When warning about retrying or giving up, print the address, so
12779 the user knows which one it's talking about.
12780 - If you haven't used a clean circuit in an hour, throw it away,
12781 just to be on the safe side. (This means after 6 hours a totally
12782 unused Tor client will have no circuits open.)
12785 Changes in version 0.0.9rc5 - 2004-12-01
12786 o Bugfixes on 0.0.8.1:
12787 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
12788 - Let resolve conns retry/expire also, rather than sticking around
12790 - If we are using select, make sure we stay within FD_SETSIZE.
12792 o Bugfixes on 0.0.9pre:
12793 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
12794 but doesn't seem to be currently; thanks to Ilja van Sprundel for
12796 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
12797 instead. Impose minima and maxima for all *Period options; impose
12798 even tighter maxima for fetching if we are a caching dirserver.
12799 Clip rather than rejecting.
12800 - Fetch cached running-routers from servers that serve it (that is,
12801 authdirservers and servers running 0.0.9rc5-cvs or later.)
12804 - Accept *:706 (silc) in default exit policy.
12805 - Implement new versioning format for post 0.1.
12806 - Support "foo.nickname.exit" addresses, to let Alice request the
12807 address "foo" as viewed by exit node "nickname". Based on a patch
12809 - Make tor --version --version dump the cvs Id of every file.
12812 Changes in version 0.0.9rc4 - 2004-11-28
12813 o Bugfixes on 0.0.8.1:
12814 - Make windows sockets actually non-blocking (oops), and handle
12815 win32 socket errors better.
12817 o Bugfixes on 0.0.9rc1:
12818 - Actually catch the -USR2 signal.
12821 Changes in version 0.0.9rc3 - 2004-11-25
12822 o Bugfixes on 0.0.8.1:
12823 - Flush the log file descriptor after we print "Tor opening log file",
12824 so we don't see those messages days later.
12826 o Bugfixes on 0.0.9rc1:
12827 - Make tor-resolve work again.
12828 - Avoid infinite loop in tor-resolve if tor hangs up on it.
12829 - Fix an assert trigger for clients/servers handling resolves.
12832 Changes in version 0.0.9rc2 - 2004-11-24
12833 o Bugfixes on 0.0.9rc1:
12834 - I broke socks5 support while fixing the eof bug.
12835 - Allow unitless bandwidths and intervals; they default to bytes
12837 - New servers don't start out hibernating; they are active until
12838 they run out of bytes, so they have a better estimate of how
12839 long it takes, and so their operators can know they're working.
12842 Changes in version 0.0.9rc1 - 2004-11-23
12843 o Bugfixes on 0.0.8.1:
12844 - Finally fix a bug that's been plaguing us for a year:
12845 With high load, circuit package window was reaching 0. Whenever
12846 we got a circuit-level sendme, we were reading a lot on each
12847 socket, but only writing out a bit. So we would eventually reach
12848 eof. This would be noticed and acted on even when there were still
12849 bytes sitting in the inbuf.
12850 - When poll() is interrupted, we shouldn't believe the revents values.
12852 o Bugfixes on 0.0.9pre6:
12853 - Fix hibernate bug that caused pre6 to be broken.
12854 - Don't keep rephist info for routers that haven't had activity for
12855 24 hours. (This matters now that clients have keys, since we track
12857 - Never call close_temp_logs while validating log options.
12858 - Fix backslash-escaping on tor.sh.in and torctl.in.
12861 - Implement weekly/monthly/daily accounting: now you specify your
12862 hibernation properties by
12863 AccountingMax N bytes|KB|MB|GB|TB
12864 AccountingStart day|week|month [day] HH:MM
12865 Defaults to "month 1 0:00".
12866 - Let bandwidth and interval config options be specified as 5 bytes,
12867 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
12868 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
12869 get back to normal.)
12870 - If your requested entry or exit node has advertised bandwidth 0,
12872 - Be more greedy about filling up relay cells -- we try reading again
12873 once we've processed the stuff we read, in case enough has arrived
12874 to fill the last cell completely.
12875 - Apply NT service patch from Osamu Fujino. Still needs more work.
12878 Changes in version 0.0.9pre6 - 2004-11-15
12879 o Bugfixes on 0.0.8.1:
12880 - Fix assert failure on malformed socks4a requests.
12881 - Use identity comparison, not nickname comparison, to choose which
12882 half of circuit-ID-space each side gets to use. This is needed
12883 because sometimes we think of a router as a nickname, and sometimes
12884 as a hex ID, and we can't predict what the other side will do.
12885 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
12886 write() call will fail and we handle it there.
12887 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
12888 and smartlist_len, which are two major profiling offenders.
12890 o Bugfixes on 0.0.9pre5:
12891 - Fix a bug in read_all that was corrupting config files on windows.
12892 - When we're raising the max number of open file descriptors to
12893 'unlimited', don't log that we just raised it to '-1'.
12894 - Include event code with events, as required by control-spec.txt.
12895 - Don't give a fingerprint when clients do --list-fingerprint:
12896 it's misleading, because it will never be the same again.
12897 - Stop using strlcpy in tor_strndup, since it was slowing us
12899 - Remove warn on startup about missing cached-directory file.
12900 - Make kill -USR1 work again.
12901 - Hibernate if we start tor during the "wait for wakeup-time" phase
12902 of an accounting interval. Log our hibernation plans better.
12903 - Authoritative dirservers now also cache their directory, so they
12904 have it on start-up.
12907 - Fetch running-routers; cache running-routers; compress
12908 running-routers; serve compressed running-routers.z
12909 - Add NSI installer script contributed by J Doe.
12910 - Commit VC6 and VC7 workspace/project files.
12911 - Commit a tor.spec for making RPM files, with help from jbash.
12912 - Add contrib/torctl.in contributed by Glenn Fink.
12913 - Implement the control-spec's SAVECONF command, to write your
12914 configuration to torrc.
12915 - Get cookie authentication for the controller closer to working.
12916 - Include control-spec.txt in the tarball.
12917 - When set_conf changes our server descriptor, upload a new copy.
12918 But don't upload it too often if there are frequent changes.
12919 - Document authentication config in man page, and document signals
12921 - Clean up confusing parts of man page and torrc.sample.
12922 - Make expand_filename handle ~ and ~username.
12923 - Use autoconf to enable largefile support where necessary. Use
12924 ftello where available, since ftell can fail at 2GB.
12925 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
12926 log more informatively.
12927 - Give a slightly more useful output for "tor -h".
12928 - Refuse application socks connections to port 0.
12929 - Check clock skew for verified servers, but allow unverified
12930 servers and clients to have any clock skew.
12931 - Break DirFetchPostPeriod into:
12932 - DirFetchPeriod for fetching full directory,
12933 - StatusFetchPeriod for fetching running-routers,
12934 - DirPostPeriod for posting server descriptor,
12935 - RendPostPeriod for posting hidden service descriptors.
12936 - Make sure the hidden service descriptors are at a random offset
12937 from each other, to hinder linkability.
12940 Changes in version 0.0.9pre5 - 2004-11-09
12941 o Bugfixes on 0.0.9pre4:
12942 - Fix a seg fault in unit tests (doesn't affect main program).
12943 - Fix an assert bug where a hidden service provider would fail if
12944 the first hop of his rendezvous circuit was down.
12945 - Hidden service operators now correctly handle version 1 style
12946 INTRODUCE1 cells (nobody generates them still, so not a critical
12948 - If do_hup fails, actually notice.
12949 - Handle more errnos from accept() without closing the listener.
12950 Some OpenBSD machines were closing their listeners because
12951 they ran out of file descriptors.
12952 - Send resolve cells to exit routers that are running a new
12953 enough version of the resolve code to work right.
12954 - Better handling of winsock includes on non-MSV win32 compilers.
12955 - Some people had wrapped their tor client/server in a script
12956 that would restart it whenever it died. This did not play well
12957 with our "shut down if your version is obsolete" code. Now people
12958 don't fetch a new directory if their local cached version is
12960 - Make our autogen.sh work on ksh as well as bash.
12963 - Hibernation: New config option "AccountingMaxKB" lets you
12964 set how many KBytes per month you want to allow your server to
12965 consume. Rather than spreading those bytes out evenly over the
12966 month, we instead hibernate for some of the month and pop up
12967 at a deterministic time, work until the bytes are consumed, then
12968 hibernate again. Config option "MonthlyAccountingStart" lets you
12969 specify which day of the month your billing cycle starts on.
12970 - Control interface: a separate program can now talk to your
12971 client/server over a socket, and get/set config options, receive
12972 notifications of circuits and streams starting/finishing/dying,
12973 bandwidth used, etc. The next step is to get some GUIs working.
12974 Let us know if you want to help out. See doc/control-spec.txt .
12975 - Ship a contrib/tor-control.py as an example script to interact
12976 with the control port.
12977 - "tor --hash-password zzyxz" will output a salted password for
12978 use in authenticating to the control interface.
12979 - New log format in config:
12980 "Log minsev[-maxsev] stdout|stderr|syslog" or
12981 "Log minsev[-maxsev] file /var/foo"
12984 - DirPolicy config option, to let people reject incoming addresses
12985 from their dirserver.
12986 - "tor --list-fingerprint" will list your identity key fingerprint
12988 - Add "pass" target for RedirectExit, to make it easier to break
12989 out of a sequence of RedirectExit rules.
12990 - Clients now generate a TLS cert too, in preparation for having
12991 them act more like real nodes.
12992 - Ship src/win32/ in the tarball, so people can use it to build.
12993 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
12995 - New "router-status" line in directory, to better bind each verified
12996 nickname to its identity key.
12997 - Deprecate unofficial config option abbreviations, and abbreviations
12998 not on the command line.
12999 - Add a pure-C tor-resolve implementation.
13000 - Use getrlimit and friends to ensure we can reach MaxConn (currently
13001 1024) file descriptors.
13003 o Code security improvements, inspired by Ilja:
13004 - Replace sprintf with snprintf. (I think they were all safe, but
13006 - Replace strcpy/strncpy with strlcpy in more places.
13007 - Avoid strcat; use snprintf or strlcat instead.
13008 - snprintf wrapper with consistent (though not C99) overflow behavior.
13011 Changes in version 0.0.9pre4 - 2004-10-17
13012 o Bugfixes on 0.0.9pre3:
13013 - If the server doesn't specify an exit policy, use the real default
13014 exit policy, not reject *:*.
13015 - Ignore fascistfirewall when uploading/downloading hidden service
13016 descriptors, since we go through Tor for those; and when using
13017 an HttpProxy, since we assume it can reach them all.
13018 - When looking for an authoritative dirserver, use only the ones
13019 configured at boot. Don't bother looking in the directory.
13020 - The rest of the fix for get_default_conf_file() on older win32.
13021 - Make 'Routerfile' config option obsolete.
13024 - New 'MyFamily nick1,...' config option for a server to
13025 specify other servers that shouldn't be used in the same circuit
13026 with it. Only believed if nick1 also specifies us.
13027 - New 'NodeFamily nick1,nick2,...' config option for a client to
13028 specify nodes that it doesn't want to use in the same circuit.
13029 - New 'Redirectexit pattern address:port' config option for a
13030 server to redirect exit connections, e.g. to a local squid.
13033 Changes in version 0.0.9pre3 - 2004-10-13
13034 o Bugfixes on 0.0.8.1:
13035 - Better torrc example lines for dirbindaddress and orbindaddress.
13036 - Improved bounds checking on parsed ints (e.g. config options and
13037 the ones we find in directories.)
13038 - Better handling of size_t vs int, so we're more robust on 64
13040 - Fix the rest of the bug where a newly started OR would appear
13041 as unverified even after we've added his fingerprint and hupped
13043 - Fix a bug from 0.0.7: when read() failed on a stream, we would
13044 close it without sending back an end. So 'connection refused'
13045 would simply be ignored and the user would get no response.
13047 o Bugfixes on 0.0.9pre2:
13048 - Serving the cached-on-disk directory to people is bad. We now
13049 provide no directory until we've fetched a fresh one.
13050 - Workaround for bug on windows where cached-directories get crlf
13052 - Make get_default_conf_file() work on older windows too.
13053 - If we write a *:* exit policy line in the descriptor, don't write
13054 any more exit policy lines.
13057 - Use only 0.0.9pre1 and later servers for resolve cells.
13058 - Make the dirservers file obsolete.
13059 - Include a dir-signing-key token in directories to tell the
13060 parsing entity which key is being used to sign.
13061 - Remove the built-in bulky default dirservers string.
13062 - New config option "Dirserver %s:%d [fingerprint]", which can be
13063 repeated as many times as needed. If no dirservers specified,
13064 default to moria1,moria2,tor26.
13065 - Make moria2 advertise a dirport of 80, so people behind firewalls
13066 will be able to get a directory.
13067 - Http proxy support
13068 - Dirservers translate requests for http://%s:%d/x to /x
13069 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
13070 be routed through this host.
13071 - Clients ask for /tor/x rather than /x for new enough dirservers.
13072 This way we can one day coexist peacefully with apache.
13073 - Clients specify a "Host: %s%d" http header, to be compatible
13074 with more proxies, and so running squid on an exit node can work.
13077 Changes in version 0.0.8.1 - 2004-10-13
13079 - Fix a seg fault that can be triggered remotely for Tor
13080 clients/servers with an open dirport.
13081 - Fix a rare assert trigger, where routerinfos for entries in
13082 our cpath would expire while we're building the path.
13083 - Fix a bug in OutboundBindAddress so it (hopefully) works.
13084 - Fix a rare seg fault for people running hidden services on
13085 intermittent connections.
13086 - Fix a bug in parsing opt keywords with objects.
13087 - Fix a stale pointer assert bug when a stream detaches and
13089 - Fix a string format vulnerability (probably not exploitable)
13090 in reporting stats locally.
13091 - Fix an assert trigger: sometimes launching circuits can fail
13092 immediately, e.g. because too many circuits have failed recently.
13093 - Fix a compile warning on 64 bit platforms.
13096 Changes in version 0.0.9pre2 - 2004-10-03
13098 - Make fetching a cached directory work for 64-bit platforms too.
13099 - Make zlib.h a required header, not an optional header.
13102 Changes in version 0.0.9pre1 - 2004-10-01
13104 - Stop using separate defaults for no-config-file and
13105 empty-config-file. Now you have to explicitly turn off SocksPort,
13106 if you don't want it open.
13107 - Fix a bug in OutboundBindAddress so it (hopefully) works.
13108 - Improve man page to mention more of the 0.0.8 features.
13109 - Fix a rare seg fault for people running hidden services on
13110 intermittent connections.
13111 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
13113 - Fix more dns related bugs: send back resolve_failed and end cells
13114 more reliably when the resolve fails, rather than closing the
13115 circuit and then trying to send the cell. Also attach dummy resolve
13116 connections to a circuit *before* calling dns_resolve(), to fix
13117 a bug where cached answers would never be sent in RESOLVED cells.
13118 - When we run out of disk space, or other log writing error, don't
13119 crash. Just stop logging to that log and continue.
13120 - We were starting to daemonize before we opened our logs, so if
13121 there were any problems opening logs, we would complain to stderr,
13122 which wouldn't work, and then mysteriously exit.
13123 - Fix a rare bug where sometimes a verified OR would connect to us
13124 before he'd uploaded his descriptor, which would cause us to
13125 assign conn->nickname as though he's unverified. Now we look through
13126 the fingerprint list to see if he's there.
13127 - Fix a rare assert trigger, where routerinfos for entries in
13128 our cpath would expire while we're building the path.
13131 - Clients can ask dirservers for /dir.z to get a compressed version
13132 of the directory. Only works for servers running 0.0.9, of course.
13133 - Make clients cache directories and use them to seed their router
13134 lists at startup. This means clients have a datadir again.
13135 - Configuration infrastructure support for warning on obsolete
13137 - Respond to content-encoding headers by trying to uncompress as
13139 - Reply with a deflated directory when a client asks for "dir.z".
13140 We could use allow-encodings instead, but allow-encodings isn't
13141 specified in HTTP 1.0.
13142 - Raise the max dns workers from 50 to 100.
13143 - Discourage people from setting their dirfetchpostperiod more often
13144 than once per minute.
13145 - Protect dirservers from overzealous descriptor uploading -- wait
13146 10 seconds after directory gets dirty, before regenerating.
13149 Changes in version 0.0.8 - 2004-08-25
13150 o Port it to SunOS 5.9 / Athena
13153 Changes in version 0.0.8rc2 - 2004-08-20
13154 o Make it compile on cygwin again.
13155 o When picking unverified routers, skip those with low uptime and/or
13156 low bandwidth, depending on what properties you care about.
13159 Changes in version 0.0.8rc1 - 2004-08-18
13160 o Changes from 0.0.7.3:
13162 - Fix assert triggers: if the other side returns an address 0.0.0.0,
13163 don't put it into the client dns cache.
13164 - If a begin failed due to exit policy, but we believe the IP address
13165 should have been allowed, switch that router to exitpolicy reject *:*
13166 until we get our next directory.
13168 - Clients choose nodes proportional to advertised bandwidth.
13169 - Avoid using nodes with low uptime as introduction points.
13170 - Handle servers with dynamic IP addresses: don't replace
13171 options->Address with the resolved one at startup, and
13172 detect our address right before we make a routerinfo each time.
13173 - 'FascistFirewall' option to pick dirservers and ORs on specific
13174 ports; plus 'FirewallPorts' config option to tell FascistFirewall
13175 which ports are open. (Defaults to 80,443)
13176 - Be more aggressive about trying to make circuits when the network
13177 has changed (e.g. when you unsuspend your laptop).
13178 - Check for time skew on http headers; report date in response to
13180 - If the entrynode config line has only one node, don't pick it as
13182 - Add strict{entry|exit}nodes config options. If set to 1, then
13183 we refuse to build circuits that don't include the specified entry
13185 - OutboundBindAddress config option, to bind to a specific
13186 IP address for outgoing connect()s.
13187 - End truncated log entries (e.g. directories) with "[truncated]".
13189 o Patches to 0.0.8preX:
13191 - Patches to compile and run on win32 again (maybe)?
13192 - Fix crash when looking for ~/.torrc with no $HOME set.
13193 - Fix a race bug in the unit tests.
13194 - Handle verified/unverified name collisions better when new
13195 routerinfo's arrive in a directory.
13196 - Sometimes routers were getting entered into the stats before
13197 we'd assigned their identity_digest. Oops.
13198 - Only pick and establish intro points after we've gotten a
13201 - AllowUnverifiedNodes config option to let circuits choose no-name
13202 routers in entry,middle,exit,introduction,rendezvous positions.
13203 Allow middle and rendezvous positions by default.
13204 - Add a man page for tor-resolve.
13207 Changes in version 0.0.7.3 - 2004-08-12
13208 o Stop dnsworkers from triggering an assert failure when you
13209 ask them to resolve the host "".
13212 Changes in version 0.0.8pre3 - 2004-08-09
13213 o Changes from 0.0.7.2:
13214 - Allow multiple ORs with same nickname in routerlist -- now when
13215 people give us one identity key for a nickname, then later
13216 another, we don't constantly complain until the first expires.
13217 - Remember used bandwidth (both in and out), and publish 15-minute
13218 snapshots for the past day into our descriptor.
13219 - You can now fetch $DIRURL/running-routers to get just the
13220 running-routers line, not the whole descriptor list. (But
13221 clients don't use this yet.)
13222 - When people mistakenly use Tor as an http proxy, point them
13223 at the tor-doc.html rather than the INSTALL.
13224 - Remove our mostly unused -- and broken -- hex_encode()
13225 function. Use base16_encode() instead. (Thanks to Timo Lindfors
13226 for pointing out this bug.)
13227 - Rotate onion keys every 12 hours, not every 2 hours, so we have
13228 fewer problems with people using the wrong key.
13229 - Change the default exit policy to reject the default edonkey,
13230 kazaa, gnutella ports.
13231 - Add replace_file() to util.[ch] to handle win32's rename().
13233 o Changes from 0.0.8preX:
13234 - Fix two bugs in saving onion keys to disk when rotating, so
13235 hopefully we'll get fewer people using old onion keys.
13236 - Fix an assert error that was making SocksPolicy not work.
13237 - Be willing to expire routers that have an open dirport -- it's
13238 just the authoritative dirservers we want to not forget.
13239 - Reject tor-resolve requests for .onion addresses early, so we
13240 don't build a whole rendezvous circuit and then fail.
13241 - When you're warning a server that he's unverified, don't cry
13242 wolf unpredictably.
13243 - Fix a race condition: don't try to extend onto a connection
13244 that's still handshaking.
13245 - For servers in clique mode, require the conn to be open before
13246 you'll choose it for your path.
13247 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
13248 end relay cell, etc.
13249 - Measure bandwidth capacity over the last 24 hours, not just 12
13250 - Bugfix: authoritative dirservers were making and signing a new
13251 directory for each client, rather than reusing the cached one.
13254 Changes in version 0.0.8pre2 - 2004-08-04
13255 o Changes from 0.0.7.2:
13257 - Check directory signature _before_ you decide whether you're
13258 you're running an obsolete version and should exit.
13259 - Check directory signature _before_ you parse the running-routers
13260 list to decide who's running or verified.
13261 - Bugfixes and features:
13262 - Check return value of fclose while writing to disk, so we don't
13263 end up with broken files when servers run out of disk space.
13264 - Log a warning if the user uses an unsafe socks variant, so people
13265 are more likely to learn about privoxy or socat.
13266 - Dirservers now include RFC1123-style dates in the HTTP headers,
13267 which one day we will use to better detect clock skew.
13269 o Changes from 0.0.8pre1:
13270 - Make it compile without warnings again on win32.
13271 - Log a warning if you're running an unverified server, to let you
13272 know you might want to get it verified.
13273 - Only pick a default nickname if you plan to be a server.
13276 Changes in version 0.0.8pre1 - 2004-07-23
13278 - Made our unit tests compile again on OpenBSD 3.5, and tor
13279 itself compile again on OpenBSD on a sparc64.
13280 - We were neglecting milliseconds when logging on win32, so
13281 everything appeared to happen at the beginning of each second.
13283 o Protocol changes:
13284 - 'Extend' relay cell payloads now include the digest of the
13285 intended next hop's identity key. Now we can verify that we're
13286 extending to the right router, and also extend to routers we
13287 hadn't heard of before.
13290 - Tor nodes can now act as relays (with an advertised ORPort)
13291 without being manually verified by the dirserver operators.
13292 - Uploaded descriptors of unverified routers are now accepted
13293 by the dirservers, and included in the directory.
13294 - Verified routers are listed by nickname in the running-routers
13295 list; unverified routers are listed as "$<fingerprint>".
13296 - We now use hash-of-identity-key in most places rather than
13297 nickname or addr:port, for improved security/flexibility.
13298 - To avoid Sybil attacks, paths still use only verified servers.
13299 But now we have a chance to play around with hybrid approaches.
13300 - Nodes track bandwidth usage to estimate capacity (not used yet).
13301 - ClientOnly option for nodes that never want to become servers.
13302 - Directory caching.
13303 - "AuthoritativeDir 1" option for the official dirservers.
13304 - Now other nodes (clients and servers) will cache the latest
13305 directory they've pulled down.
13306 - They can enable their DirPort to serve it to others.
13307 - Clients will pull down a directory from any node with an open
13308 DirPort, and check the signature/timestamp correctly.
13309 - Authoritative dirservers now fetch directories from other
13310 authdirservers, to stay better synced.
13311 - Running-routers list tells who's down also, along with noting
13312 if they're verified (listed by nickname) or unverified (listed
13314 - Allow dirservers to serve running-router list separately.
13315 This isn't used yet.
13316 - ORs connect-on-demand to other ORs
13317 - If you get an extend cell to an OR you're not connected to,
13318 connect, handshake, and forward the create cell.
13319 - The authoritative dirservers stay connected to everybody,
13320 and everybody stays connected to 0.0.7 servers, but otherwise
13321 clients/servers expire unused connections after 5 minutes.
13322 - When servers get a sigint, they delay 30 seconds (refusing new
13323 connections) then exit. A second sigint causes immediate exit.
13324 - File and name management:
13325 - Look for .torrc if no CONFDIR "torrc" is found.
13326 - If no datadir is defined, then choose, make, and secure ~/.tor
13328 - If torrc not found, exitpolicy reject *:*.
13329 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
13330 - If no nickname is defined, derive default from hostname.
13331 - Rename secret key files, e.g. identity.key -> secret_id_key,
13332 to discourage people from mailing their identity key to tor-ops.
13333 - Refuse to build a circuit before the directory has arrived --
13334 it won't work anyway, since you won't know the right onion keys
13336 - Try other dirservers immediately if the one you try is down. This
13337 should tolerate down dirservers better now.
13338 - Parse tor version numbers so we can do an is-newer-than check
13339 rather than an is-in-the-list check.
13340 - New socks command 'resolve', to let us shim gethostbyname()
13342 - A 'tor_resolve' script to access the socks resolve functionality.
13343 - A new socks-extensions.txt doc file to describe our
13344 interpretation and extensions to the socks protocols.
13345 - Add a ContactInfo option, which gets published in descriptor.
13346 - Publish OR uptime in descriptor (and thus in directory) too.
13347 - Write tor version at the top of each log file
13348 - New docs in the tarball:
13350 - Document that you should proxy your SSL traffic too.
13353 Changes in version 0.0.7.2 - 2004-07-07
13354 o A better fix for the 0.0.0.0 problem, that will hopefully
13355 eliminate the remaining related assertion failures.
13358 Changes in version 0.0.7.1 - 2004-07-04
13359 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
13360 since internally we use 0.0.0.0 to signify "not yet resolved".
13363 Changes in version 0.0.7 - 2004-06-07
13364 o Updated the man page to reflect the new features.
13367 Changes in version 0.0.7rc2 - 2004-06-06
13368 o Changes from 0.0.7rc1:
13369 - Make it build on Win32 again.
13370 o Changes from 0.0.6.2:
13371 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
13375 Changes in version 0.0.7rc1 - 2004-06-02
13377 - On sighup, we were adding another log without removing the first
13378 one. So log messages would get duplicated n times for n sighups.
13379 - Several cases of using a connection after we'd freed it. The
13380 problem was that connections that are pending resolve are in both
13381 the pending_resolve tree, and also the circuit's resolving_streams
13382 list. When you want to remove one, you must remove it from both.
13383 - Fix a double-mark-for-close where an end cell arrived for a
13384 resolving stream, and then the resolve failed.
13385 - Check directory signatures based on name of signer, not on whom
13386 we got the directory from. This will let us cache directories more
13389 - Crank up some of our constants to handle more users.
13392 Changes in version 0.0.7pre1 - 2004-06-02
13393 o Fixes for crashes and other obnoxious bugs:
13394 - Fix an epipe bug: sometimes when directory connections failed
13395 to connect, we would give them a chance to flush before closing
13397 - When we detached from a circuit because of resolvefailed, we
13398 would immediately try the same circuit twice more, and then
13399 give up on the resolve thinking we'd tried three different
13401 - Limit the number of intro circuits we'll attempt to build for a
13402 hidden service per 15-minute period.
13403 - Check recommended-software string *early*, before actually parsing
13404 the directory. Thus we can detect an obsolete version and exit,
13405 even if the new directory format doesn't parse.
13406 o Fixes for security bugs:
13407 - Remember which nodes are dirservers when you startup, and if a
13408 random OR enables his dirport, don't automatically assume he's
13409 a trusted dirserver.
13411 - Directory connections were asking the wrong poll socket to
13412 start writing, and not asking themselves to start writing.
13413 - When we detached from a circuit because we sent a begin but
13414 didn't get a connected, we would use it again the first time;
13415 but after that we would correctly switch to a different one.
13416 - Stop warning when the first onion decrypt attempt fails; they
13417 will sometimes legitimately fail now that we rotate keys.
13418 - Override unaligned-access-ok check when $host_cpu is ia64 or
13419 arm. Apparently they allow it but the kernel whines.
13420 - Dirservers try to reconnect periodically too, in case connections
13422 - Fix some memory leaks in directory servers.
13423 - Allow backslash in Win32 filenames.
13424 - Made Tor build complain-free on FreeBSD, hopefully without
13425 breaking other BSD builds. We'll see.
13427 - Doxygen markup on all functions and global variables.
13428 - Make directory functions update routerlist, not replace it. So
13429 now directory disagreements are not so critical a problem.
13430 - Remove the upper limit on number of descriptors in a dirserver's
13431 directory (not that we were anywhere close).
13432 - Allow multiple logfiles at different severity ranges.
13433 - Allow *BindAddress to specify ":port" rather than setting *Port
13434 separately. Allow multiple instances of each BindAddress config
13435 option, so you can bind to multiple interfaces if you want.
13436 - Allow multiple exit policy lines, which are processed in order.
13437 Now we don't need that huge line with all the commas in it.
13438 - Enable accept/reject policies on SOCKS connections, so you can bind
13439 to 0.0.0.0 but still control who can use your OP.
13442 Changes in version 0.0.6.2 - 2004-05-16
13443 o Our integrity-checking digest was checking only the most recent cell,
13444 not the previous cells like we'd thought.
13445 Thanks to Stefan Mark for finding the flaw!
13448 Changes in version 0.0.6.1 - 2004-05-06
13449 o Fix two bugs in our AES counter-mode implementation (this affected
13450 onion-level stream encryption, but not TLS-level). It turns
13451 out we were doing something much more akin to a 16-character
13452 polyalphabetic cipher. Oops.
13453 Thanks to Stefan Mark for finding the flaw!
13454 o Retire moria3 as a directory server, and add tor26 as a directory
13458 Changes in version 0.0.6 - 2004-05-02
13459 [version bump only]
13462 Changes in version 0.0.6rc4 - 2004-05-01
13463 o Update the built-in dirservers list to use the new directory format
13464 o Fix a rare seg fault: if a node offering a hidden service attempts
13465 to build a circuit to Alice's rendezvous point and fails before it
13466 reaches the last hop, it retries with a different circuit, but
13468 o Handle windows socket errors correctly.
13471 Changes in version 0.0.6rc3 - 2004-04-28
13472 o Don't expire non-general excess circuits (if we had enough
13473 circuits open, we were expiring rendezvous circuits -- even
13474 when they had a stream attached. oops.)
13475 o Fetch randomness from /dev/urandom better (not via fopen/fread)
13476 o Better debugging for tls errors
13477 o Some versions of openssl have an SSL_pending function that erroneously
13478 returns bytes when there is a non-application record pending.
13479 o Set Content-Type on the directory and hidserv descriptor.
13480 o Remove IVs from cipher code, since AES-ctr has none.
13481 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
13482 o We were using an array of length zero in a few places.
13483 o win32's gethostbyname can't resolve an IP to an IP.
13484 o win32's close can't close a socket.
13487 Changes in version 0.0.6rc2 - 2004-04-26
13488 o Fix a bug where we were closing tls connections intermittently.
13489 It turns out openssl keeps its errors around -- so if an error
13490 happens, and you don't ask about it, and then another openssl
13491 operation happens and succeeds, and you ask if there was an error,
13492 it tells you about the first error. Fun fun.
13493 o Fix a bug that's been lurking since 27 may 03 (!)
13494 When passing back a destroy cell, we would use the wrong circ id.
13495 'Mostly harmless', but still worth fixing.
13496 o Since we don't support truncateds much, don't bother sending them;
13497 just close the circ.
13498 o check for <machine/limits.h> so we build on NetBSD again (I hope).
13499 o don't crash if a conn that sent a begin has suddenly lost its circuit
13500 (this was quite rare).
13503 Changes in version 0.0.6rc1 - 2004-04-25
13504 o We now rotate link (tls context) keys and onion keys.
13505 o CREATE cells now include oaep padding, so you can tell
13506 if you decrypted them correctly.
13507 o Add bandwidthburst to server descriptor.
13508 o Directories now say which dirserver signed them.
13509 o Use a tor_assert macro that logs failed assertions too.
13512 Changes in version 0.0.6pre5 - 2004-04-18
13513 o changes from 0.0.6pre4:
13514 - make tor build on broken freebsd 5.2 installs
13515 - fix a failed assert when you try an intro point, get a nack, and try
13516 a second one and it works.
13517 - when alice uses a port that the hidden service doesn't accept,
13518 it now sends back an end cell (denied by exit policy). otherwise
13519 alice would just have to wait to time out.
13520 - fix another rare bug: when we had tried all the intro
13521 points for a hidden service, we fetched the descriptor
13522 again, but we left our introcirc thinking it had already
13523 sent an intro, so it kept waiting for a response...
13524 - bugfix: when you sleep your hidden-service laptop, as soon
13525 as it wakes up it tries to upload a service descriptor, but
13526 socketpair fails for some reason (localhost not up yet?).
13527 now we simply give up on that upload, and we'll try again later.
13528 i'd still like to find the bug though.
13529 - if an intro circ waiting for an ack dies before getting one, then
13531 - we were reusing stale service descriptors and refetching usable
13535 Changes in version 0.0.6pre4 - 2004-04-14
13536 o changes from 0.0.6pre3:
13537 - when bob fails to connect to the rendezvous point, and his
13538 circ didn't fail because of the rendezvous point itself, then
13539 he retries a couple of times
13540 - we expire introduction and rendezvous circs more thoroughly
13541 (sometimes they were hanging around forever)
13542 - we expire unattached rendezvous streams that have been around
13543 too long (they were sticking around forever).
13544 - fix a measly fencepost error that was crashing everybody with
13548 Changes in version 0.0.6pre3 - 2004-04-14
13549 o changes from 0.0.6pre2:
13550 - make hup work again
13551 - fix some memory leaks for dirservers
13552 - allow more skew in rendezvous descriptor timestamps, to help
13553 handle people like blanu who don't know what time it is
13554 - normal circs are 3 hops, but some rend/intro circs are 4, if
13555 the initiator doesn't get to choose the last hop
13556 - send acks for introductions, so alice can know whether to try
13558 - bob publishes intro points more correctly
13559 o changes from 0.0.5:
13560 - fix an assert trigger that's been plaguing us since the days
13561 of 0.0.2prexx (thanks weasel!)
13562 - retry stream correctly when we fail to connect because of
13563 exit-policy-reject (should try another) or can't-resolve-address
13564 (also should try another, because dns on random internet servers
13566 - when we hup a dirserver and we've *removed* a server from the
13567 approved-routers list, now we remove that server from the
13568 in-memory directories too
13571 Changes in version 0.0.6pre2 - 2004-04-08
13572 o We fixed our base32 implementation. Now it works on all architectures.
13575 Changes in version 0.0.6pre1 - 2004-04-08
13577 - Hidden services and rendezvous points are implemented. Go to
13578 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
13579 hidden services. (This only works via a socks4a proxy such as
13580 Privoxy, and currently it's quite slow.)
13583 Changes in version 0.0.5 - 2004-03-30
13584 [version bump only]
13587 Changes in version 0.0.5rc3 - 2004-03-29
13588 o Install torrc as torrc.sample -- we no longer clobber your
13590 o Re-enable recommendedversion checking (we broke it in rc2, oops)
13591 o Add in a 'notice' log level for things the operator should hear
13592 but that aren't warnings
13595 Changes in version 0.0.5rc2 - 2004-03-29
13596 o Hold socks connection open until reply is flushed (if possible)
13597 o Make exit nodes resolve IPs to IPs immediately, rather than asking
13598 the dns farm to do it.
13599 o Fix c99 aliasing warnings in rephist.c
13600 o Don't include server descriptors that are older than 24 hours in the
13602 o Give socks 'reject' replies their whole 15s to attempt to flush,
13603 rather than seeing the 60s timeout and assuming the flush had failed.
13604 o Clean automake droppings from the cvs repository
13607 Changes in version 0.0.5rc1 - 2004-03-28
13608 o Fix mangled-state bug in directory fetching (was causing sigpipes).
13609 o Only build circuits after we've fetched the directory: clients were
13610 using only the directory servers before they'd fetched a directory.
13611 This also means longer startup time; so it goes.
13612 o Fix an assert trigger where an OP would fail to handshake, and we'd
13613 expect it to have a nickname.
13614 o Work around a tsocks bug: do a socks reject when AP connection dies
13615 early, else tsocks goes into an infinite loop.
13618 Changes in version 0.0.4 - 2004-03-26
13619 o When connecting to a dirserver or OR and the network is down,
13623 Changes in version 0.0.3 - 2004-03-26
13624 o Warn and fail if server chose a nickname with illegal characters
13625 o Port to Solaris and Sparc:
13626 - include missing header fcntl.h
13627 - have autoconf find -lsocket -lnsl automatically
13628 - deal with hardware word alignment
13629 - make uname() work (solaris has a different return convention)
13630 - switch from using signal() to sigaction()
13631 o Preliminary work on reputation system:
13632 - Keep statistics on success/fail of connect attempts; they're published
13633 by kill -USR1 currently.
13634 - Add a RunTesting option to try to learn link state by creating test
13635 circuits, even when SocksPort is off.
13636 - Remove unused open circuits when there are too many.
13639 Changes in version 0.0.2 - 2004-03-19
13640 - Include strlcpy and strlcat for safer string ops
13641 - define INADDR_NONE so we compile (but still not run) on solaris
13644 Changes in version 0.0.2pre27 - 2004-03-14
13646 - Allow internal tor networks (we were rejecting internal IPs,
13647 now we allow them if they're set explicitly).
13648 - And fix a few endian issues.
13651 Changes in version 0.0.2pre26 - 2004-03-14
13653 - If a stream times out after 15s without a connected cell, don't
13654 try that circuit again: try a new one.
13655 - Retry streams at most 4 times. Then give up.
13656 - When a dirserver gets a descriptor from an unknown router, it
13657 logs its fingerprint (so the dirserver operator can choose to
13658 accept it even without mail from the server operator).
13659 - Inform unapproved servers when we reject their descriptors.
13660 - Make tor build on Windows again. It works as a client, who knows
13662 - Clearer instructions in the torrc for how to set up a server.
13663 - Be more efficient about reading fd's when our global token bucket
13664 (used for rate limiting) becomes empty.
13666 - Stop asserting that computers always go forward in time. It's
13668 - When we sent a cell (e.g. destroy) and then marked an OR connection
13669 expired, we might close it before finishing a flush if the other
13670 side isn't reading right then.
13671 - Don't allow dirservers to start if they haven't defined
13672 RecommendedVersions
13673 - We were caching transient dns failures. Oops.
13674 - Prevent servers from publishing an internal IP as their address.
13675 - Address a strcat vulnerability in circuit.c
13678 Changes in version 0.0.2pre25 - 2004-03-04
13680 - Put the OR's IP in its router descriptor, not its fqdn. That way
13681 we'll stop being stalled by gethostbyname for nodes with flaky dns,
13684 - If the user typed in an address that didn't resolve, the server
13688 Changes in version 0.0.2pre24 - 2004-03-03
13690 - Fix an assertion failure in dns.c, where we were trying to dequeue
13691 a pending dns resolve even if it wasn't pending
13692 - Fix a spurious socks5 warning about still trying to write after the
13693 connection is finished.
13694 - Hold certain marked_for_close connections open until they're finished
13695 flushing, rather than losing bytes by closing them too early.
13696 - Correctly report the reason for ending a stream
13697 - Remove some duplicate calls to connection_mark_for_close
13698 - Put switch_id and start_daemon earlier in the boot sequence, so it
13699 will actually try to chdir() to options.DataDirectory
13700 - Make 'make test' exit(1) if a test fails; fix some unit tests
13701 - Make tor fail when you use a config option it doesn't know about,
13702 rather than warn and continue.
13703 - Make --version work
13704 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
13707 Changes in version 0.0.2pre23 - 2004-02-29
13709 - Print a statement when the first circ is finished, so the user
13710 knows it's working.
13711 - If a relay cell is unrecognized at the end of the circuit,
13712 send back a destroy. (So attacks to mutate cells are more
13714 - New config option 'excludenodes' to avoid certain nodes for circuits.
13715 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
13716 so you can collect coredumps there.
13718 - Fix a bug in tls flushing where sometimes data got wedged and
13719 didn't flush until more data got sent. Hopefully this bug was
13720 a big factor in the random delays we were seeing.
13721 - Make 'connected' cells include the resolved IP, so the client
13722 dns cache actually gets populated.
13723 - Disallow changing from ORPort=0 to ORPort>0 on hup.
13724 - When we time-out on a stream and detach from the circuit, send an
13725 end cell down it first.
13726 - Only warn about an unknown router (in exitnodes, entrynodes,
13727 excludenodes) after we've fetched a directory.
13730 Changes in version 0.0.2pre22 - 2004-02-26
13732 - Servers publish less revealing uname information in descriptors.
13733 - More memory tracking and assertions, to crash more usefully when
13735 - If the default torrc isn't there, just use some default defaults.
13736 Plus provide an internal dirservers file if they don't have one.
13737 - When the user tries to use Tor as an http proxy, give them an http
13738 501 failure explaining that we're a socks proxy.
13739 - Dump a new router.desc on hup, to help confused people who change
13740 their exit policies and then wonder why router.desc doesn't reflect
13742 - Clean up the generic tor.sh init script that we ship with.
13744 - If the exit stream is pending on the resolve, and a destroy arrives,
13745 then the stream wasn't getting removed from the pending list. I
13746 think this was the one causing recent server crashes.
13747 - Use a more robust poll on OSX 10.3, since their poll is flaky.
13748 - When it couldn't resolve any dirservers, it was useless from then on.
13749 Now it reloads the RouterFile (or default dirservers) if it has no
13751 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
13752 many users don't even *have* a /usr/local/sbin/.
13755 Changes in version 0.0.2pre21 - 2004-02-18
13757 - There's a ChangeLog file that actually reflects the changelog.
13758 - There's a 'torify' wrapper script, with an accompanying
13759 tor-tsocks.conf, that simplifies the process of using tsocks for
13760 tor. It even has a man page.
13761 - The tor binary gets installed to sbin rather than bin now.
13762 - Retry streams where the connected cell hasn't arrived in 15 seconds
13763 - Clean up exit policy handling -- get the default out of the torrc,
13764 so we can update it without forcing each server operator to fix
13766 - Allow imaps and pop3s in default exit policy
13768 - Prevent picking middleman nodes as the last node in the circuit
13771 Changes in version 0.0.2pre20 - 2004-01-30
13773 - We now have a deb package, and it's in debian unstable. Go to
13774 it, apt-getters. :)
13775 - I've split the TotalBandwidth option into BandwidthRate (how many
13776 bytes per second you want to allow, long-term) and
13777 BandwidthBurst (how many bytes you will allow at once before the cap
13778 kicks in). This better token bucket approach lets you, say, set
13779 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
13780 performance while not exceeding your monthly bandwidth quota.
13781 - Push out a tls record's worth of data once you've got it, rather
13782 than waiting until you've read everything waiting to be read. This
13783 may improve performance by pipelining better. We'll see.
13784 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
13785 from failed circuits (if they haven't been connected yet) and attach
13787 - Expire old streams that haven't managed to connect. Some day we'll
13788 have them reattach to new circuits instead.
13791 - Fix several memory leaks that were causing servers to become bloated
13793 - Fix a few very rare assert triggers. A few more remain.
13794 - Setuid to User _before_ complaining about running as root.
13797 Changes in version 0.0.2pre19 - 2004-01-07
13799 - Fix deadlock condition in dns farm. We were telling a child to die by
13800 closing the parent's file descriptor to him. But newer children were
13801 inheriting the open file descriptor from the parent, and since they
13802 weren't closing it, the socket never closed, so the child never read
13803 eof, so he never knew to exit. Similarly, dns workers were holding
13804 open other sockets, leading to all sorts of chaos.
13805 - New cleaner daemon() code for forking and backgrounding.
13806 - If you log to a file, it now prints an entry at the top of the
13807 logfile so you know it's working.
13808 - The onionskin challenge length was 30 bytes longer than necessary.
13809 - Started to patch up the spec so it's not quite so out of date.
13812 Changes in version 0.0.2pre18 - 2004-01-02
13814 - Fix endian issues with the 'integrity' field in the relay header.
13815 - Fix a potential bug where connections in state
13816 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
13819 Changes in version 0.0.2pre17 - 2003-12-30
13821 - Made --debuglogfile (or any second log file, actually) work.
13822 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
13823 adversary could force us into an infinite loop.
13826 - Each onionskin handshake now includes a hash of the computed key,
13827 to prove the server's identity and help perfect forward secrecy.
13828 - Changed cell size from 256 to 512 bytes (working toward compatibility
13830 - Changed cell length to 2 bytes, and moved it to the relay header.
13831 - Implemented end-to-end integrity checking for the payloads of
13833 - Separated streamid from 'recognized' (otherwise circuits will get
13834 messed up when we try to have streams exit from the middle). We
13835 use the integrity-checking to confirm that a cell is addressed to
13837 - Randomize the initial circid and streamid values, so an adversary who
13838 breaks into a node can't learn how many circuits or streams have
13842 Changes in version 0.0.2pre16 - 2003-12-14
13844 - Fixed a bug that made HUP trigger an assert
13845 - Fixed a bug where a circuit that immediately failed wasn't being
13846 counted as a failed circuit in counting retries.
13849 - Now we close the circuit when we get a truncated cell: otherwise we're
13850 open to an anonymity attack where a bad node in the path truncates
13851 the circuit and then we open streams at him.
13852 - Add port ranges to exit policies
13853 - Add a conservative default exit policy
13854 - Warn if you're running tor as root
13855 - on HUP, retry OR connections and close/rebind listeners
13856 - options.EntryNodes: try these nodes first when picking the first node
13857 - options.ExitNodes: if your best choices happen to include any of
13858 your preferred exit nodes, you choose among just those preferred
13860 - options.ExcludedNodes: nodes that are never picked in path building
13863 Changes in version 0.0.2pre15 - 2003-12-03
13864 o Robustness and bugfixes:
13865 - Sometimes clients would cache incorrect DNS resolves, which would
13866 really screw things up.
13867 - An OP that goes offline would slowly leak all its sockets and stop
13869 - A wide variety of bugfixes in exit node selection, exit policy
13870 handling, and processing pending streams when a new circuit is
13872 - Pick nodes for a path only from those the directory says are up
13873 - Choose randomly from all running dirservers, not always the first one
13874 - Increase allowed http header size for directory fetch.
13875 - Stop writing to stderr (if we're daemonized it will be closed).
13876 - Enable -g always, so cores will be more useful to me.
13877 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
13880 - Wrote a man page. It lists commonly used options.
13883 - Change default loglevel to warn.
13884 - Make PidFile default to null rather than littering in your CWD.
13885 - OnionRouter config option is now obsolete. Instead it just checks
13887 - Moved to a single unified torrc file for both clients and servers.
13890 Changes in version 0.0.2pre14 - 2003-11-29
13891 o Robustness and bugfixes:
13892 - Force the admin to make the DataDirectory himself
13893 - to get ownership/permissions right
13894 - so clients no longer make a DataDirectory and then never use it
13895 - fix bug where a client who was offline for 45 minutes would never
13896 pull down a directory again
13897 - fix (or at least hide really well) the dns assert bug that was
13898 causing server crashes
13899 - warnings and improved robustness wrt clockskew for certs
13900 - use the native daemon(3) to daemonize, when available
13901 - exit if bind() fails
13902 - exit if neither socksport nor orport is defined
13903 - include our own tor_timegm (Win32 doesn't have its own)
13904 - bugfix for win32 with lots of connections
13905 - fix minor bias in PRNG
13906 - make dirserver more robust to corrupt cached directory
13909 - Wrote the design document (woo)
13911 o Circuit building and exit policies:
13912 - Circuits no longer try to use nodes that the directory has told them
13914 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
13915 bitcounts (18.0.0.0/8).
13916 - Make AP connections standby for a circuit if no suitable circuit
13917 exists, rather than failing
13918 - Circuits choose exit node based on addr/port, exit policies, and
13919 which AP connections are standing by
13920 - Bump min pathlen from 2 to 3
13921 - Relay end cells have a payload to describe why the stream ended.
13922 - If the stream failed because of exit policy, try again with a new
13924 - Clients have a dns cache to remember resolved addresses.
13925 - Notice more quickly when we have no working circuits
13928 - APPort is now called SocksPort
13929 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
13931 - RecommendedVersions is now a config variable rather than
13932 hardcoded (for dirservers)
13933 - Reloads config on HUP
13934 - Usage info on -h or --help
13935 - If you set User and Group config vars, it'll setu/gid to them.
13938 Changes in version 0.0.2pre13 - 2003-10-19
13939 o General stability:
13940 - SSL_write no longer fails when it returns WANTWRITE and the number
13941 of bytes in the buf has changed by the next SSL_write call.
13942 - Fix segfault fetching directory when network is down
13943 - Fix a variety of minor memory leaks
13944 - Dirservers reload the fingerprints file on HUP, so I don't have
13945 to take down the network when I approve a new router
13946 - Default server config file has explicit Address line to specify fqdn
13949 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
13950 - Make listener connections not ever alloc bufs
13952 o Autoconf improvements:
13953 - don't clobber an external CFLAGS in ./configure
13954 - Make install now works
13955 - create var/lib/tor on make install
13956 - autocreate a tor.sh initscript to help distribs
13957 - autocreate the torrc and sample-server-torrc with correct paths
13959 o Log files and Daemonizing now work:
13960 - If --DebugLogFile is specified, log to it at -l debug
13961 - If --LogFile is specified, use it instead of commandline
13962 - If --RunAsDaemon is set, tor forks and backgrounds on startup