1 Changes in version 0.2.1.6-alpha - 2008-09-xx
3 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
4 Tor to fail to start if you had it configured to use a bridge
5 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
6 - When extending a circuit to a hidden service directory to upload a
7 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8 requests failed, because the router descriptor has not been
9 downloaded yet. In these cases, do not attempt to upload the
10 rendezvous descriptor, but wait until the router descriptor is
11 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
12 descriptor from a hidden service directory for which the router
13 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
15 - DNS replies need to have names matching their requests, but these names
16 should be in the questions section, not necessarily in the answers
17 section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
20 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
22 - Fixed some memory leaks --some quite frequent, some almost impossible
23 to trigger-- based on results from Coverity.
24 - When testing for libevent functions, set the LDFLAGS variable
25 correctly. (Found by Riastradh.)
26 - Fix an assertion bug in parsing policy-related options; possible fix
28 - Catch and report a few more bootstrapping failure cases when Tor
29 fails to establish a TCP connection. Cleanup on 0.2.1.x.
30 - When fetching v0 and v2 rendezvous service descriptors in parallel,
31 we were failing the whole hidden service request when the v0
32 descriptor fetch fails, even if the v2 fetch is still pending and
33 might succeed. Similarly, if the last v2 fetch fails, we were
34 failing the whole hidden service request even if a v0 fetch is
35 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
36 - Avoid a bug where the FistFirstHopPK 0 option would keep Tor from
37 bootstrapping with tunneled directory connections. Bugfix on
38 0.1.2.5-alpha. Fixes bug 797.
41 - Update to the "September 1 2008" ip-to-country file.
42 - Allow ports 465 and 587 in the default exit policy again. We had
43 rejected them in 0.1.0.15, because back in 2005 they were commonly
44 misconfigured and ended up as spam targets. We hear they are better
45 locked down these days.
46 - Use a lockfile to make sure that two Tor processes are not
47 simultaneously running with the same datadir.
48 - Directory mirrors store and serve v2 hidden service descriptors by
49 default (i.e. new default value for HidServDirectoryV2 is 1).
50 - Serve the latest v3 networkstatus consensus via the control
51 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
52 - Better logging about stability/reliability calculations on directory
55 o Code simplifications and refactoring:
56 - Revise the connection_new functions so that a more typesafe variant
57 exists. This will work better with Coverity, and let us find any
58 actual mistakes we're making here.
59 - Refactor unit testing logic so that dmalloc can be used sensibly with
60 unit tests to check for memory leaks.
63 Changes in version 0.2.0.31 - 2008-09-03
64 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
65 a big bug we're seeing where in rare cases traffic from one Tor stream
66 gets mixed into another stream, and fixes a variety of smaller issues.
69 - Make sure that two circuits can never exist on the same connection
70 with the same circuit ID, even if one is marked for close. This
71 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
72 - Relays now reject risky extend cells: if the extend cell includes
73 a digest of all zeroes, or asks to extend back to the relay that
74 sent the extend cell, tear down the circuit. Ideas suggested
76 - If not enough of our entry guards are available so we add a new
77 one, we might use the new one even if it overlapped with the
78 current circuit's exit relay (or its family). Anonymity bugfix
82 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
83 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
84 - Correctly detect the presence of the linux/netfilter_ipv4.h header
85 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
86 - Pick size of default geoip filename string correctly on windows.
87 Fixes bug 806. Bugfix on 0.2.0.30.
88 - Make the autoconf script accept the obsolete --with-ssl-dir
89 option as an alias for the actually-working --with-openssl-dir
90 option. Fix the help documentation to recommend --with-openssl-dir.
91 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
92 - Disallow session resumption attempts during the renegotiation
93 stage of the v2 handshake protocol. Clients should never be trying
94 session resumption at this point, but apparently some did, in
95 ways that caused the handshake to fail. Bug found by Geoff Goodell.
96 Bugfix on 0.2.0.20-rc.
97 - When using the TransPort option on OpenBSD, and using the User
98 option to change UID and drop privileges, make sure to open
99 /dev/pf before dropping privileges. Fixes bug 782. Patch from
100 Christopher Davis. Bugfix on 0.1.2.1-alpha.
101 - Try to attach connections immediately upon receiving a RENDEZVOUS2
102 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
103 on the client side when connecting to a hidden service. Bugfix
104 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
105 - When closing an application-side connection because its circuit is
106 getting torn down, generate the stream event correctly. Bugfix on
107 0.1.2.x. Anonymous patch.
110 Changes in version 0.2.1.5-alpha - 2008-08-31
111 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
112 in a lot of the infrastructure for adding authorization to hidden
113 services, lays the groundwork for having clients read their load
114 balancing information out of the networkstatus consensus rather than
115 the individual router descriptors, addresses two potential anonymity
116 issues, and fixes a variety of smaller issues.
119 - Convert many internal address representations to optionally hold
121 - Generate and accept IPv6 addresses in many protocol elements.
122 - Make resolver code handle nameservers located at ipv6 addresses.
123 - Begin implementation of proposal 121 ("Client authorization for
124 hidden services"): configure hidden services with client
125 authorization, publish descriptors for them, and configure
126 authorization data for hidden services at clients. The next
127 step is to actually access hidden services that perform client
129 - More progress toward proposal 141: Network status consensus
130 documents and votes now contain bandwidth information for each
131 router and a summary of that router's exit policy. Eventually this
132 will be used by clients so that they do not have to download every
133 known descriptor before building circuits.
135 o Major bugfixes (on 0.2.0.x and before):
136 - When sending CREATED cells back for a given circuit, use a 64-bit
137 connection ID to find the right connection, rather than an addr:port
138 combination. Now that we can have multiple OR connections between
139 the same ORs, it is no longer possible to use addr:port to uniquely
140 identify a connection.
141 - Relays now reject risky extend cells: if the extend cell includes
142 a digest of all zeroes, or asks to extend back to the relay that
143 sent the extend cell, tear down the circuit. Ideas suggested
145 - If not enough of our entry guards are available so we add a new
146 one, we might use the new one even if it overlapped with the
147 current circuit's exit relay (or its family). Anonymity bugfix
151 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
152 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
153 - When using the TransPort option on OpenBSD, and using the User
154 option to change UID and drop privileges, make sure to open /dev/pf
155 before dropping privileges. Fixes bug 782. Patch from Christopher
156 Davis. Bugfix on 0.1.2.1-alpha.
157 - Correctly detect the presence of the linux/netfilter_ipv4.h header
158 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
159 - Add a missing safe_str() call for a debug log message.
160 - Use 64 bits instead of 32 bits for connection identifiers used with
161 the controller protocol, to greatly reduce risk of identifier reuse.
162 - Make the autoconf script accept the obsolete --with-ssl-dir
163 option as an alias for the actually-working --with-openssl-dir
164 option. Fix the help documentation to recommend --with-openssl-dir.
165 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
168 - Rate-limit too-many-sockets messages: when they happen, they happen
169 a lot. Resolves bug 748.
170 - Resist DNS poisoning a little better by making sure that names in
171 answer sections match.
172 - Print the SOCKS5 error message string as well as the error code
173 when a tor-resolve request fails. Patch from Jacob.
176 Changes in version 0.2.1.4-alpha - 2008-08-04
177 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
180 - The address part of exit policies was not correctly written
181 to router descriptors. This generated router descriptors that failed
182 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
184 - Tor triggered a false assert when extending a circuit to a relay
185 but we already have a connection open to that relay. Noticed by
186 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
189 - Fix a hidden service logging bug: in some edge cases, the router
190 descriptor of a previously picked introduction point becomes
191 obsolete and we need to give up on it rather than continually
192 complaining that it has become obsolete. Observed by xiando. Bugfix
196 - Take out the TestVia config option, since it was a workaround for
197 a bug that was fixed in Tor 0.1.1.21.
200 Changes in version 0.2.1.3-alpha - 2008-08-03
201 Tor 0.2.1.3-alpha implements most of the pieces to prevent
202 infinite-length circuit attacks (see proposal 110); fixes a bug that
203 might cause exit relays to corrupt streams they send back; allows
204 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
205 ExcludeExitNodes config options; and fixes a big pile of bugs.
207 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
208 - Send a bootstrap problem "warn" event on the first problem if the
209 reason is NO_ROUTE (that is, our network is down).
212 - Implement most of proposal 110: The first K cells to be sent
213 along a circuit are marked as special "early" cells; only K "early"
214 cells will be allowed. Once this code is universal, we can block
215 certain kinds of DOS attack by requiring that EXTEND commands must
216 be sent using an "early" cell.
219 - Try to attach connections immediately upon receiving a RENDEZVOUS2
220 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
221 on the client side when connecting to a hidden service. Bugfix
222 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
223 - Ensure that two circuits can never exist on the same connection
224 with the same circuit ID, even if one is marked for close. This
225 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
228 - When relays do their initial bandwidth measurement, don't limit
229 to just our entry guards for the test circuits. Otherwise we tend
230 to have multiple test circuits going through a single entry guard,
231 which makes our bandwidth test less accurate. Fixes part of bug 654;
232 patch contributed by Josh Albrecht.
233 - Add an ExcludeExitNodes option so users can list a set of nodes
234 that should be be excluded from the exit node position, but
235 allowed elsewhere. Implements proposal 151.
236 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
237 ExcludeNodes and ExcludeExitNodes lists.
238 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
239 be more efficient. Formerly it was quadratic in the number of
240 servers; now it should be linear. Fixes bug 509.
241 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
242 and n_conn_id_digest fields into a separate structure that's
243 only needed when the circuit has not yet attached to an n_conn.
246 - Change the contrib/tor.logrotate script so it makes the new
247 logs as "_tor:_tor" rather than the default, which is generally
248 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
249 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
250 warnings (occasionally), but it can also cause the compiler to
251 eliminate error-checking code. Suggested by Peter Gutmann.
252 - When a hidden service is giving up on an introduction point candidate
253 that was not included in the last published rendezvous descriptor,
254 don't reschedule publication of the next descriptor. Fixes bug 763.
256 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
257 HiddenServiceExcludeNodes as obsolete: they never worked properly,
258 and nobody claims to be using them. Fixes bug 754. Bugfix on
259 0.1.0.1-rc. Patch from Christian Wilms.
260 - Fix a small alignment and memory-wasting bug on buffer chunks.
263 o Minor bugfixes (controller):
264 - When closing an application-side connection because its circuit
265 is getting torn down, generate the stream event correctly.
266 Bugfix on 0.1.2.x. Anonymous patch.
269 - Remove all backward-compatibility code to support relays running
270 versions of Tor so old that they no longer work at all on the
274 Changes in version 0.2.0.29-rc - 2008-07-08
275 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
276 hidden-service performance bugs, and fixes a bunch of smaller bugs.
279 - If you have more than one bridge but don't know their keys,
280 you would only launch a request for the descriptor of the first one
281 on your list. (Tor considered launching requests for the others, but
282 found that it already had a connection on the way for $0000...0000
283 so it didn't open another.) Bugfix on 0.2.0.x.
284 - If you have more than one bridge but don't know their keys, and the
285 connection to one of the bridges failed, you would cancel all
286 pending bridge connections. (After all, they all have the same
287 digest.) Bugfix on 0.2.0.x.
288 - When a hidden service was trying to establish an introduction point,
289 and Tor had built circuits preemptively for such purposes, we
290 were ignoring all the preemptive circuits and launching a new one
291 instead. Bugfix on 0.2.0.14-alpha.
292 - When a hidden service was trying to establish an introduction point,
293 and Tor *did* manage to reuse one of the preemptively built
294 circuits, it didn't correctly remember which one it used,
295 so it asked for another one soon after, until there were no
296 more preemptive circuits, at which point it launched one from
297 scratch. Bugfix on 0.0.9.x.
298 - Make directory servers include the X-Your-Address-Is: http header in
299 their responses even for begin_dir conns. Now clients who only
300 ever use begin_dir connections still have a way to learn their IP
301 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
304 - Fix a macro/CPP interaction that was confusing some compilers:
305 some GCCs don't like #if/#endif pairs inside macro arguments.
307 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
308 Fixes bug 704; fix from Steven Murdoch.
309 - When opening /dev/null in finish_daemonize(), do not pass the
310 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
311 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
312 - Correctly detect transparent proxy support on Linux hosts that
313 require in.h to be included before netfilter_ipv4.h. Patch
315 - Disallow session resumption attempts during the renegotiation
316 stage of the v2 handshake protocol. Clients should never be trying
317 session resumption at this point, but apparently some did, in
318 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
319 found by Geoff Goodell.
322 Changes in version 0.2.1.2-alpha - 2008-06-20
323 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
324 make it easier to set up your own private Tor network; fixes several
325 big bugs with using more than one bridge relay; fixes a big bug with
326 offering hidden services quickly after Tor starts; and uses a better
327 API for reporting potential bootstrapping problems to the controller.
330 - New TestingTorNetwork config option to allow adjustment of
331 previously constant values that, while reasonable, could slow
332 bootstrapping. Implements proposal 135. Patch from Karsten.
335 - If you have more than one bridge but don't know their digests,
336 you would only learn a request for the descriptor of the first one
337 on your list. (Tor considered launching requests for the others, but
338 found that it already had a connection on the way for $0000...0000
339 so it didn't open another.) Bugfix on 0.2.0.x.
340 - If you have more than one bridge but don't know their digests,
341 and the connection to one of the bridges failed, you would cancel
342 all pending bridge connections. (After all, they all have the
343 same digest.) Bugfix on 0.2.0.x.
344 - When establishing a hidden service, introduction points that
345 originate from cannibalized circuits are completely ignored and not
346 included in rendezvous service descriptors. This might be another
347 reason for delay in making a hidden service available. Bugfix
348 from long ago (0.0.9.x?)
351 - Allow OpenSSL to use dynamic locks if it wants.
352 - When building a consensus, do not include routers that are down.
353 This will cut down 30% to 40% on consensus size. Implements
355 - In directory authorities' approved-routers files, allow
356 fingerprints with or without space.
357 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
358 controller can query our current bootstrap state in case it attaches
359 partway through and wants to catch up.
360 - Send an initial "Starting" bootstrap status event, so we have a
361 state to start out in.
364 - Asking for a conditional consensus at .../consensus/<fingerprints>
365 would crash a dirserver if it did not already have a
366 consensus. Bugfix on 0.2.1.1-alpha.
367 - Clean up some macro/CPP interactions: some GCC versions don't like
368 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
371 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
372 - Directory authorities shouldn't complain about bootstrapping
373 problems just because they do a lot of reachability testing and
374 some of the connection attempts fail.
375 - Start sending "count" and "recommendation" key/value pairs in
376 bootstrap problem status events, so the controller can hear about
377 problems even before Tor decides they're worth reporting for sure.
378 - If you're using bridges, generate "bootstrap problem" warnings
379 as soon as you run out of working bridges, rather than waiting
380 for ten failures -- which will never happen if you have less than
382 - If we close our OR connection because there's been a circuit
383 pending on it for too long, we were telling our bootstrap status
384 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
387 Changes in version 0.2.1.1-alpha - 2008-06-13
388 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
389 were making the Tor process bloat especially on Linux; makes our TLS
390 handshake blend in better; sends "bootstrap phase" status events to
391 the controller, so it can keep the user informed of progress (and
392 problems) fetching directory information and establishing circuits;
393 and adds a variety of smaller features.
396 - More work on making our TLS handshake blend in: modify the list
397 of ciphers advertised by OpenSSL in client mode to even more
398 closely resemble a common web browser. We cheat a little so that
399 we can advertise ciphers that the locally installed OpenSSL doesn't
401 - Start sending "bootstrap phase" status events to the controller,
402 so it can keep the user informed of progress fetching directory
403 information and establishing circuits. Also inform the controller
404 if we think we're stuck at a particular bootstrap phase. Implements
406 - Resume using OpenSSL's RAND_poll() for better (and more portable)
407 cross-platform entropy collection again. We used to use it, then
408 stopped using it because of a bug that could crash systems that
409 called RAND_poll when they had a lot of fds open. It looks like the
410 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
411 at startup, and to call RAND_poll() when we reseed later only if
412 we have a non-buggy OpenSSL version.
415 - When we choose to abandon a new entry guard because we think our
416 older ones might be better, close any circuits pending on that
417 new entry guard connection. This fix should make us recover much
418 faster when our network is down and then comes back. Bugfix on
419 0.1.2.8-beta; found by lodger.
421 o Memory fixes and improvements:
422 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
423 to avoid unused RAM in buffer chunks and memory pools.
424 - Speed up parsing and cut down on memory fragmentation by using
425 stack-style allocations for parsing directory objects. Previously,
426 this accounted for over 40% of allocations from within Tor's code
427 on a typical directory cache.
428 - Use a Bloom filter rather than a digest-based set to track which
429 descriptors we need to keep around when we're cleaning out old
430 router descriptors. This speeds up the computation significantly,
431 and may reduce fragmentation.
432 - Reduce the default smartlist size from 32 to 16; it turns out that
433 most smartlists hold around 8-12 elements tops.
434 - Make dumpstats() log the fullness and size of openssl-internal
436 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
437 patch to their OpenSSL, turn it on to save memory on servers. This
438 patch will (with any luck) get included in a mainline distribution
440 - Never use OpenSSL compression: it wastes RAM and CPU trying to
441 compress cells, which are basically all encrypted, compressed,
445 - Stop reloading the router list from disk for no reason when we
446 run out of reachable directory mirrors. Once upon a time reloading
447 it would set the 'is_running' flag back to 1 for them. It hasn't
448 done that for a long time.
449 - In very rare situations new hidden service descriptors were
450 published earlier than 30 seconds after the last change to the
451 service. (We currently think that a hidden service descriptor
452 that's been stable for 30 seconds is worth publishing.)
455 - Allow separate log levels to be configured for different logging
456 domains. For example, this allows one to log all notices, warnings,
457 or errors, plus all memory management messages of level debug or
458 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
459 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
460 and stop using a warning that had become unfixably verbose under
462 - New --hush command-line option similar to --quiet. While --quiet
463 disables all logging to the console on startup, --hush limits the
464 output to messages of warning and error severity.
465 - Servers support a new URL scheme for consensus downloads that
466 allows the client to specify which authorities are trusted.
467 The server then only sends the consensus if the client will trust
468 it. Otherwise a 404 error is sent back. Clients use this
469 new scheme when the server supports it (meaning it's running
470 0.2.1.1-alpha or later). Implements proposal 134.
471 - New configure/torrc options (--enable-geoip-stats,
472 DirRecordUsageByCountry) to record how many IPs we've served
473 directory info to in each country code, how many status documents
474 total we've sent to each country code, and what share of the total
475 directory requests we should expect to see.
476 - Use the TLS1 hostname extension to more closely resemble browser
478 - Lots of new unit tests.
479 - Add a macro to implement the common pattern of iterating through
480 two parallel lists in lockstep.
483 Changes in version 0.2.0.28-rc - 2008-06-13
484 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
485 performance bug, and fixes a bunch of smaller bugs.
488 - Fix a bug where, when we were choosing the 'end stream reason' to
489 put in our relay end cell that we send to the exit relay, Tor
490 clients on Windows were sometimes sending the wrong 'reason'. The
491 anonymity problem is that exit relays may be able to guess whether
492 the client is running Windows, thus helping partition the anonymity
493 set. Down the road we should stop sending reasons to exit relays,
494 or otherwise prevent future versions of this bug.
497 - While setting up a hidden service, some valid introduction circuits
498 were overlooked and abandoned. This might be the reason for
499 the long delay in making a hidden service available. Bugfix on
503 - Update to the "June 9 2008" ip-to-country file.
504 - Run 'make test' as part of 'make dist', so we stop releasing so
505 many development snapshots that fail their unit tests.
508 - When we're checking if we have enough dir info for each relay
509 to begin establishing circuits, make sure that we actually have
510 the descriptor listed in the consensus, not just any descriptor.
512 - Bridge relays no longer print "xx=0" in their extrainfo document
513 for every single country code in the geoip db. Bugfix on
515 - Only warn when we fail to load the geoip file if we were planning to
516 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
517 - If we change our MaxAdvertisedBandwidth and then reload torrc,
518 Tor won't realize it should publish a new relay descriptor. Fixes
519 bug 688, reported by mfr. Bugfix on 0.1.2.x.
520 - When we haven't had any application requests lately, don't bother
521 logging that we have expired a bunch of descriptors. Bugfix
523 - Make relay cells written on a connection count as non-padding when
524 tracking how long a connection has been in use. Bugfix on
525 0.2.0.1-alpha. Spotted by lodger.
526 - Fix unit tests in 0.2.0.27-rc.
527 - Fix compile on Windows.
530 Changes in version 0.2.0.27-rc - 2008-06-03
531 Tor 0.2.0.27-rc adds a few features we left out of the earlier
532 release candidates. In particular, we now include an IP-to-country
533 GeoIP database, so controllers can easily look up what country a
534 given relay is in, and so bridge relays can give us some sanitized
535 summaries about which countries are making use of bridges. (See proposal
536 126-geoip-fetching.txt for details.)
539 - Include an IP-to-country GeoIP file in the tarball, so bridge
540 relays can report sanitized summaries of the usage they're seeing.
543 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
544 Robert Hogan. Fixes the first part of bug 681.
545 - Make bridge authorities never serve extrainfo docs.
546 - Add support to detect Libevent versions in the 1.4.x series
548 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
549 - Include a new contrib/tor-exit-notice.html file that exit relay
550 operators can put on their website to help reduce abuse queries.
553 - When tunneling an encrypted directory connection, and its first
554 circuit fails, do not leave it unattached and ask the controller
555 to deal. Fixes the second part of bug 681.
556 - Make bridge authorities correctly expire old extrainfo documents
560 Changes in version 0.2.0.26-rc - 2008-05-13
561 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
562 in Debian's OpenSSL packages. All users running any 0.2.0.x version
563 should upgrade, whether they're running Debian or not.
565 o Major security fixes:
566 - Use new V3 directory authority keys on the tor26, gabelmoo, and
567 moria1 V3 directory authorities. The old keys were generated with
568 a vulnerable version of Debian's OpenSSL package, and must be
569 considered compromised. Other authorities' keys were not generated
570 with an affected version of OpenSSL.
573 - List authority signatures as "unrecognized" based on DirServer
574 lines, not on cert cache. Bugfix on 0.2.0.x.
577 - Add a new V3AuthUseLegacyKey option to make it easier for
578 authorities to change their identity keys if they have to.
581 Changes in version 0.2.0.25-rc - 2008-04-23
582 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
585 - Remember to initialize threading before initializing logging.
586 Otherwise, many BSD-family implementations will crash hard on
587 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
590 - Authorities correctly free policies on bad servers on
591 exit. Fixes bug 672. Bugfix on 0.2.0.x.
594 Changes in version 0.2.0.24-rc - 2008-04-22
595 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
596 v3 directory authority, makes relays with dynamic IP addresses and no
597 DirPort notice more quickly when their IP address changes, fixes a few
598 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
600 o New directory authorities:
601 - Take lefkada out of the list of v3 directory authorities, since
602 it has been down for months.
603 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
607 - Detect address changes more quickly on non-directory mirror
608 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
610 o Minor features (security):
611 - Reject requests for reverse-dns lookup of names that are in
612 a private address space. Patch from lodger.
613 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
616 o Minor bugfixes (crashes):
617 - Avoid a rare assert that can trigger when Tor doesn't have much
618 directory information yet and it tries to fetch a v2 hidden
619 service descriptor. Fixes bug 651, reported by nwf.
620 - Initialize log mutex before initializing dmalloc. Otherwise,
621 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
622 - Use recursive pthread mutexes in order to avoid deadlock when
623 logging debug-level messages to a controller. Bug spotted by nwf,
624 bugfix on 0.2.0.16-alpha.
626 o Minor bugfixes (resource management):
627 - Keep address policies from leaking memory: start their refcount
628 at 1, not 2. Bugfix on 0.2.0.16-alpha.
629 - Free authority certificates on exit, so they don't look like memory
630 leaks. Bugfix on 0.2.0.19-alpha.
631 - Free static hashtables for policy maps and for TLS connections on
632 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
633 - Avoid allocating extra space when computing consensuses on 64-bit
634 platforms. Bug spotted by aakova.
636 o Minor bugfixes (misc):
637 - Do not read the configuration file when we've only been told to
638 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
639 based on patch from Sebastian Hahn.
640 - Exit relays that are used as a client can now reach themselves
641 using the .exit notation, rather than just launching an infinite
642 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
643 - When attempting to open a logfile fails, tell us why.
644 - Fix a dumb bug that was preventing us from knowing that we should
645 preemptively build circuits to handle expected directory requests.
646 Fixes bug 660. Bugfix on 0.1.2.x.
647 - Warn less verbosely about clock skew from netinfo cells from
648 untrusted sources. Fixes bug 663.
649 - Make controller stream events for DNS requests more consistent,
650 by adding "new stream" events for DNS requests, and removing
651 spurious "stream closed" events" for cached reverse resolves.
652 Patch from mwenge. Fixes bug 646.
653 - Correctly notify one-hop connections when a circuit build has
654 failed. Possible fix for bug 669. Found by lodger.
657 Changes in version 0.2.0.23-rc - 2008-03-24
658 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
659 makes bootstrapping faster if the first directory mirror you contact
660 is down. The bundles also include the new Vidalia 0.1.2 release.
663 - When a tunneled directory request is made to a directory server
664 that's down, notice after 30 seconds rather than 120 seconds. Also,
665 fail any begindir streams that are pending on it, so they can
666 retry elsewhere. This was causing multi-minute delays on bootstrap.
669 Changes in version 0.2.0.22-rc - 2008-03-18
670 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
671 enables encrypted directory connections by default for non-relays, fixes
672 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
673 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
676 - Enable encrypted directory connections by default for non-relays,
677 so censor tools that block Tor directory connections based on their
678 plaintext patterns will no longer work. This means Tor works in
679 certain censored countries by default again.
682 - Make sure servers always request certificates from clients during
683 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
684 - Do not enter a CPU-eating loop when a connection is closed in
685 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
686 diagnosed by lodger; bugfix on 0.2.0.20-rc.
687 - Fix assertion failure that could occur when a blocked circuit
688 became unblocked, and it had pending client DNS requests. Bugfix
689 on 0.2.0.1-alpha. Fixes bug 632.
691 o Minor bugfixes (on 0.1.2.x):
692 - Generate "STATUS_SERVER" events rather than misspelled
693 "STATUS_SEVER" events. Caught by mwenge.
694 - When counting the number of bytes written on a TLS connection,
695 look at the BIO actually used for writing to the network, not
696 at the BIO used (sometimes) to buffer data for the network.
697 Looking at different BIOs could result in write counts on the
698 order of ULONG_MAX. Fixes bug 614.
699 - On Windows, correctly detect errors when listing the contents of
700 a directory. Fix from lodger.
702 o Minor bugfixes (on 0.2.0.x):
703 - Downgrade "sslv3 alert handshake failure" message to INFO.
704 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
705 left BandwidthRate and BandwidthBurst at the default, we would be
706 silently limited by those defaults. Now raise them to match the
707 RelayBandwidth* values.
708 - Fix the SVK version detection logic to work correctly on a branch.
709 - Make --enable-openbsd-malloc work correctly on Linux with alpha
711 - Logging functions now check that the passed severity is sane.
712 - Use proper log levels in the testsuite call of
713 get_interface_address6().
714 - When using a nonstandard malloc, do not use the platform values for
715 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
716 - Make the openbsd malloc code use 8k pages on alpha CPUs and
718 - Detect mismatched page sizes when using --enable-openbsd-malloc.
719 - Avoid double-marked-for-close warning when certain kinds of invalid
720 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
721 for bug 617. Bugfix on 0.2.0.1-alpha.
722 - Make sure that the "NULL-means-reject *:*" convention is followed by
723 all the policy manipulation functions, avoiding some possible crash
724 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
725 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
726 actually works, and doesn't warn about every single reverse lookup.
727 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
730 - Only log guard node status when guard node status has changed.
731 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
732 make "INFO" 75% less verbose.
735 Changes in version 0.2.0.21-rc - 2008-03-02
736 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
737 makes Tor work well with Vidalia again, fixes a rare assert bug,
738 and fixes a pair of more minor bugs. The bundles also include Vidalia
739 0.1.0 and Torbutton 1.1.16.
742 - The control port should declare that it requires password auth
743 when HashedControlSessionPassword is set too. Patch from Matt Edman;
744 bugfix on 0.2.0.20-rc. Fixes bug 615.
745 - Downgrade assert in connection_buckets_decrement() to a log message.
746 This may help us solve bug 614, and in any case will make its
747 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
748 - We were sometimes miscounting the number of bytes read from the
749 network, causing our rate limiting to not be followed exactly.
750 Bugfix on 0.2.0.16-alpha. Reported by lodger.
753 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
754 OpenSSL versions should have been working fine. Diagnosis and patch
755 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
756 Bugfix on 0.2.0.20-rc.
759 Changes in version 0.2.0.20-rc - 2008-02-24
760 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
761 makes more progress towards normalizing Tor's TLS handshake, makes
762 hidden services work better again, helps relays bootstrap if they don't
763 know their IP address, adds optional support for linking in openbsd's
764 allocator or tcmalloc, allows really fast relays to scale past 15000
765 sockets, and fixes a bunch of minor bugs reported by Veracode.
768 - Enable the revised TLS handshake based on the one designed by
769 Steven Murdoch in proposal 124, as revised in proposal 130. It
770 includes version negotiation for OR connections as described in
771 proposal 105. The new handshake is meant to be harder for censors
772 to fingerprint, and it adds the ability to detect certain kinds of
773 man-in-the-middle traffic analysis attacks. The version negotiation
774 feature will allow us to improve Tor's link protocol more safely
776 - Choose which bridge to use proportional to its advertised bandwidth,
777 rather than uniformly at random. This should speed up Tor for
778 bridge users. Also do this for people who set StrictEntryNodes.
779 - When a TrackHostExits-chosen exit fails too many times in a row,
780 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
783 - Resolved problems with (re-)fetching hidden service descriptors.
784 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
786 - If we only ever used Tor for hidden service lookups or posts, we
787 would stop building circuits and start refusing connections after
788 24 hours, since we falsely believed that Tor was dormant. Reported
789 by nwf; bugfix on 0.1.2.x.
790 - Servers that don't know their own IP address should go to the
791 authorities for their first directory fetch, even if their DirPort
792 is off or if they don't know they're reachable yet. This will help
793 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
794 - When counting the number of open sockets, count not only the number
795 of sockets we have received from the socket() call, but also
796 the number we've gotten from accept() and socketpair(). This bug
797 made us fail to count all sockets that we were using for incoming
798 connections. Bugfix on 0.2.0.x.
799 - Fix code used to find strings within buffers, when those strings
800 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
801 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
802 - Add a new __HashedControlSessionPassword option for controllers
803 to use for one-off session password hashes that shouldn't get
804 saved to disk by SAVECONF --- Vidalia users were accumulating a
805 pile of HashedControlPassword lines in their torrc files, one for
806 each time they had restarted Tor and then clicked Save. Make Tor
807 automatically convert "HashedControlPassword" to this new option but
808 only when it's given on the command line. Partial fix for bug 586.
810 o Minor features (performance):
811 - Tune parameters for cell pool allocation to minimize amount of
813 - Add OpenBSD malloc code from phk as an optional malloc
814 replacement on Linux: some glibc libraries do very poorly
815 with Tor's memory allocation patterns. Pass
816 --enable-openbsd-malloc to get the replacement malloc code.
817 - Add a --with-tcmalloc option to the configure script to link
818 against tcmalloc (if present). Does not yet search for
819 non-system include paths.
820 - Stop imposing an arbitrary maximum on the number of file descriptors
821 used for busy servers. Bug reported by Olaf Selke; patch from
824 o Minor features (other):
825 - When SafeLogging is disabled, log addresses along with all TLS
827 - When building with --enable-gcc-warnings, check for whether Apple's
828 warning "-Wshorten-64-to-32" is available.
829 - Add a --passphrase-fd argument to the tor-gencert command for
832 o Minor bugfixes (memory leaks and code problems):
833 - We were leaking a file descriptor if Tor started with a zero-length
834 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
835 - Detect size overflow in zlib code. Reported by Justin Ferguson and
837 - We were comparing the raw BridgePassword entry with a base64'ed
838 version of it, when handling a "/tor/networkstatus-bridges"
839 directory request. Now compare correctly. Noticed by Veracode.
840 - Recover from bad tracked-since value in MTBF-history file.
842 - Alter the code that tries to recover from unhandled write
843 errors, to not try to flush onto a socket that's given us
844 unhandled errors. Bugfix on 0.1.2.x.
845 - Make Unix controlsockets work correctly on OpenBSD. Patch from
846 tup. Bugfix on 0.2.0.3-alpha.
848 o Minor bugfixes (other):
849 - If we have an extra-info document for our server, always make
850 it available on the control port, even if we haven't gotten
851 a copy of it from an authority yet. Patch from mwenge.
852 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
853 - Directory mirrors no longer include a guess at the client's IP
854 address if the connection appears to be coming from the same /24
855 network; it was producing too many wrong guesses.
856 - Make the new hidden service code respect the SafeLogging setting.
857 Bugfix on 0.2.0.x. Patch from Karsten.
858 - When starting as an authority, do not overwrite all certificates
859 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
860 - If we're trying to flush the last bytes on a connection (for
861 example, when answering a directory request), reset the
862 time-to-give-up timeout every time we manage to write something
863 on the socket. Bugfix on 0.1.2.x.
864 - Change the behavior of "getinfo status/good-server-descriptor"
865 so it doesn't return failure when any authority disappears.
866 - Even though the man page said that "TrackHostExits ." should
867 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
868 - Report TLS "zero return" case as a "clean close" and "IO error"
869 as a "close". Stop calling closes "unexpected closes": existing
870 Tors don't use SSL_close(), so having a connection close without
871 the TLS shutdown handshake is hardly unexpected.
872 - Send NAMESERVER_STATUS messages for a single failed nameserver
875 o Code simplifications and refactoring:
876 - Remove the tor_strpartition function: its logic was confused,
877 and it was only used for one thing that could be implemented far
881 Changes in version 0.2.0.19-alpha - 2008-02-09
882 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
883 handshake, makes path selection for relays more secure and IP address
884 guessing more robust, and generally fixes a lot of bugs in preparation
885 for calling the 0.2.0 branch stable.
888 - Do not include recognizeable strings in the commonname part of
889 Tor's x509 certificates.
892 - If we're a relay, avoid picking ourselves as an introduction point,
893 a rendezvous point, or as the final hop for internal circuits. Bug
894 reported by taranis and lodger. Bugfix on 0.1.2.x.
895 - Patch from "Andrew S. Lists" to catch when we contact a directory
896 mirror at IP address X and he says we look like we're coming from
897 IP address X. Bugfix on 0.1.2.x.
899 o Minor features (security):
900 - Be more paranoid about overwriting sensitive memory on free(),
901 as a defensive programming tactic to ensure forward secrecy.
903 o Minor features (directory authority):
904 - Actually validate the options passed to AuthDirReject,
905 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
906 - Reject router descriptors with out-of-range bandwidthcapacity or
907 bandwidthburst values.
909 o Minor features (controller):
910 - Reject controller commands over 1MB in length. This keeps rogue
911 processes from running us out of memory.
913 o Minor features (misc):
914 - Give more descriptive well-formedness errors for out-of-range
915 hidden service descriptor/protocol versions.
916 - Make memory debugging information describe more about history
917 of cell allocation, so we can help reduce our memory use.
919 o Deprecated features (controller):
920 - The status/version/num-versioning and status/version/num-concurring
921 GETINFO options are no longer useful in the v3 directory protocol:
922 treat them as deprecated, and warn when they're used.
925 - When our consensus networkstatus has been expired for a while, stop
926 being willing to build circuits using it. Fixes bug 401. Bugfix
928 - Directory caches now fetch certificates from all authorities
929 listed in a networkstatus consensus, even when they do not
930 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
931 - When connecting to a bridge without specifying its key, insert
932 the connection into the identity-to-connection map as soon as
933 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
934 - Detect versions of OS X where malloc_good_size() is present in the
935 library but never actually declared. Resolves bug 587. Bugfix
937 - Stop incorrectly truncating zlib responses to directory authority
938 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
939 - Stop recommending that every server operator send mail to tor-ops.
940 Resolves bug 597. Bugfix on 0.1.2.x.
941 - Don't trigger an assert if we start a directory authority with a
942 private IP address (like 127.0.0.1).
943 - Avoid possible failures when generating a directory with routers
944 with over-long versions strings, or too many flags set. Bugfix
946 - If an attempt to launch a DNS resolve request over the control
947 port fails because we have overrun the limit on the number of
948 connections, tell the controller that the request has failed.
949 - Avoid using too little bandwidth when our clock skips a few
950 seconds. Bugfix on 0.1.2.x.
951 - Fix shell error when warning about missing packages in configure
952 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
953 - Do not become confused when receiving a spurious VERSIONS-like
954 cell from a confused v1 client. Bugfix on 0.2.0.x.
955 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
956 introduction points for a hidden service have failed. Patch from
957 Karsten Loesing. Bugfix on 0.2.0.x.
959 o Code simplifications and refactoring:
960 - Remove some needless generality from cpuworker code, for improved
962 - Stop overloading the circuit_t.onionskin field for both "onionskin
963 from a CREATE cell that we are waiting for a cpuworker to be
964 assigned" and "onionskin from an EXTEND cell that we are going to
965 send to an OR as soon as we are connected". Might help with bug 600.
966 - Add an in-place version of aes_crypt() so that we can avoid doing a
967 needless memcpy() call on each cell payload.
970 Changes in version 0.2.0.18-alpha - 2008-01-25
971 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
972 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
973 that can warn or reject connections to ports generally associated with
974 vulnerable-plaintext protocols.
976 o New directory authorities:
977 - Set up dannenberg (run by CCC) as the sixth v3 directory
981 - Fix a major memory leak when attempting to use the v2 TLS
982 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
983 - We accidentally enabled the under-development v2 TLS handshake
984 code, which was causing log entries like "TLS error while
985 renegotiating handshake". Disable it again. Resolves bug 590.
986 - We were computing the wrong Content-Length: header for directory
987 responses that need to be compressed on the fly, causing clients
988 asking for those items to always fail. Bugfix on 0.2.0.x; partially
992 - Avoid going directly to the directory authorities even if you're a
993 relay, if you haven't found yourself reachable yet or if you've
994 decided not to advertise your dirport yet. Addresses bug 556.
995 - If we've gone 12 hours since our last bandwidth check, and we
996 estimate we have less than 50KB bandwidth capacity but we could
997 handle more, do another bandwidth test.
998 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
999 Tor can warn and/or refuse connections to ports commonly used with
1000 vulnerable-plaintext protocols. Currently we warn on ports 23,
1001 109, 110, and 143, but we don't reject any.
1004 - When we setconf ClientOnly to 1, close any current OR and Dir
1005 listeners. Reported by mwenge.
1006 - When we get a consensus that's been signed by more people than
1007 we expect, don't log about it; it's not a big deal. Reported
1011 - Don't answer "/tor/networkstatus-bridges" directory requests if
1012 the request isn't encrypted.
1013 - Make "ClientOnly 1" config option disable directory ports too.
1014 - Patches from Karsten Loesing to make v2 hidden services more
1015 robust: work even when there aren't enough HSDir relays available;
1016 retry when a v2 rend desc fetch fails; but don't retry if we
1017 already have a usable v0 rend desc.
1020 Changes in version 0.2.0.17-alpha - 2008-01-17
1021 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
1024 - Make the tor-gencert man page get included correctly in the tarball.
1027 Changes in version 0.2.0.16-alpha - 2008-01-17
1028 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
1029 Loesing, and generally cleans up a lot of features and minor bugs.
1031 o New directory authorities:
1032 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
1035 o Major performance improvements:
1036 - Switch our old ring buffer implementation for one more like that
1037 used by free Unix kernels. The wasted space in a buffer with 1mb
1038 of data will now be more like 8k than 1mb. The new implementation
1039 also avoids realloc();realloc(); patterns that can contribute to
1040 memory fragmentation.
1043 - Configuration files now accept C-style strings as values. This
1044 helps encode characters not allowed in the current configuration
1045 file format, such as newline or #. Addresses bug 557.
1046 - Although we fixed bug 539 (where servers would send HTTP status 503
1047 responses _and_ send a body too), there are still servers out
1048 there that haven't upgraded. Therefore, make clients parse such
1049 bodies when they receive them.
1050 - When we're not serving v2 directory information, there is no reason
1051 to actually keep any around. Remove the obsolete files and directory
1052 on startup if they are very old and we aren't going to serve them.
1054 o Minor performance improvements:
1055 - Reference-count and share copies of address policy entries; only 5%
1056 of them were actually distinct.
1057 - Never walk through the list of logs if we know that no log is
1058 interested in a given message.
1061 - When an authority has not signed a consensus, do not try to
1062 download a nonexistent "certificate with key 00000000". Bugfix
1063 on 0.2.0.x. Fixes bug 569.
1064 - Fix a rare assert error when we're closing one of our threads:
1065 use a mutex to protect the list of logs, so we never write to the
1066 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
1067 bug 575, which is kind of the revenge of bug 222.
1068 - Patch from Karsten Loesing to complain less at both the client
1069 and the relay when a relay used to have the HSDir flag but doesn't
1070 anymore, and we try to upload a hidden service descriptor.
1071 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
1073 - Do not try to download missing certificates until we have tried
1074 to check our fallback consensus. Fixes bug 583.
1075 - Make bridges round reported GeoIP stats info up to the nearest
1076 estimate, not down. Now we can distinguish between "0 people from
1077 this country" and "1 person from this country".
1078 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
1079 - Avoid possible segfault if key generation fails in
1080 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
1081 - Avoid segfault in the case where a badly behaved v2 versioning
1082 directory sends a signed networkstatus with missing client-versions.
1084 - Avoid segfaults on certain complex invocations of
1085 router_get_by_hexdigest(). Bugfix on 0.1.2.
1086 - Correct bad index on array access in parse_http_time(). Bugfix
1088 - Fix possible bug in vote generation when server versions are present
1089 but client versions are not.
1090 - Fix rare bug on REDIRECTSTREAM control command when called with no
1091 port set: it could erroneously report an error when none had
1093 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
1094 compressing large objects and find ourselves with more than 4k
1095 left over. Bugfix on 0.2.0.
1096 - Fix a small memory leak when setting up a hidden service.
1097 - Fix a few memory leaks that could in theory happen under bizarre
1099 - Fix an assert if we post a general-purpose descriptor via the
1100 control port but that descriptor isn't mentioned in our current
1101 network consensus. Bug reported by Jon McLachlan; bugfix on
1104 o Minor features (controller):
1105 - Get NS events working again. Patch from tup.
1106 - The GETCONF command now escapes and quotes configuration values
1107 that don't otherwise fit into the torrc file.
1108 - The SETCONF command now handles quoted values correctly.
1110 o Minor features (directory authorities):
1111 - New configuration options to override default maximum number of
1112 servers allowed on a single IP address. This is important for
1113 running a test network on a single host.
1114 - Actually implement the -s option to tor-gencert.
1115 - Add a manual page for tor-gencert.
1117 o Minor features (bridges):
1118 - Bridge authorities no longer serve bridge descriptors over
1119 unencrypted connections.
1121 o Minor features (other):
1122 - Add hidden services and DNSPorts to the list of things that make
1123 Tor accept that it has running ports. Change starting Tor with no
1124 ports from a fatal error to a warning; we might change it back if
1125 this turns out to confuse anybody. Fixes bug 579.
1128 Changes in version 0.1.2.19 - 2008-01-17
1129 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
1130 exit policy a little bit more conservative so it's safer to run an
1131 exit relay on a home system, and fixes a variety of smaller issues.
1134 - Exit policies now reject connections that are addressed to a
1135 relay's public (external) IP address too, unless
1136 ExitPolicyRejectPrivate is turned off. We do this because too
1137 many relays are running nearby to services that trust them based
1141 - When the clock jumps forward a lot, do not allow the bandwidth
1142 buckets to become negative. Fixes bug 544.
1143 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
1144 on every successful resolve. Reported by Mike Perry.
1145 - Purge old entries from the "rephist" database and the hidden
1146 service descriptor database even when DirPort is zero.
1147 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
1148 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
1149 crashing or mis-answering these requests.
1150 - When we decide to send a 503 response to a request for servers, do
1151 not then also send the server descriptors: this defeats the whole
1152 purpose. Fixes bug 539.
1155 - Changing the ExitPolicyRejectPrivate setting should cause us to
1156 rebuild our server descriptor.
1157 - Fix handling of hex nicknames when answering controller requests for
1158 networkstatus by name, or when deciding whether to warn about
1159 unknown routers in a config option. (Patch from mwenge.)
1160 - Fix a couple of hard-to-trigger autoconf problems that could result
1161 in really weird results on platforms whose sys/types.h files define
1162 nonstandard integer types.
1163 - Don't try to create the datadir when running --verify-config or
1164 --hash-password. Resolves bug 540.
1165 - If we were having problems getting a particular descriptor from the
1166 directory caches, and then we learned about a new descriptor for
1167 that router, we weren't resetting our failure count. Reported
1169 - Although we fixed bug 539 (where servers would send HTTP status 503
1170 responses _and_ send a body too), there are still servers out there
1171 that haven't upgraded. Therefore, make clients parse such bodies
1172 when they receive them.
1173 - Run correctly on systems where rlim_t is larger than unsigned long.
1174 This includes some 64-bit systems.
1175 - Run correctly on platforms (like some versions of OS X 10.5) where
1176 the real limit for number of open files is OPEN_FILES, not rlim_max
1177 from getrlimit(RLIMIT_NOFILES).
1178 - Avoid a spurious free on base64 failure.
1179 - Avoid segfaults on certain complex invocations of
1180 router_get_by_hexdigest().
1181 - Fix rare bug on REDIRECTSTREAM control command when called with no
1182 port set: it could erroneously report an error when none had
1186 Changes in version 0.2.0.15-alpha - 2007-12-25
1187 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
1188 features added in 0.2.0.13-alpha.
1191 - Fix several remotely triggerable asserts based on DirPort requests
1192 for a v2 or v3 networkstatus object before we were prepared. This
1193 was particularly bad for 0.2.0.13 and later bridge relays, who
1194 would never have a v2 networkstatus and would thus always crash
1195 when used. Bugfixes on 0.2.0.x.
1196 - Estimate the v3 networkstatus size more accurately, rather than
1197 estimating it at zero bytes and giving it artificially high priority
1198 compared to other directory requests. Bugfix on 0.2.0.x.
1201 - Fix configure.in logic for cross-compilation.
1202 - When we load a bridge descriptor from the cache, and it was
1203 previously unreachable, mark it as retriable so we won't just
1204 ignore it. Also, try fetching a new copy immediately. Bugfixes
1206 - The bridge GeoIP stats were counting other relays, for example
1207 self-reachability and authority-reachability tests.
1210 - Support compilation to target iPhone; patch from cjacker huang.
1211 To build for iPhone, pass the --enable-iphone option to configure.
1214 Changes in version 0.2.0.14-alpha - 2007-12-23
1216 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
1217 without a datadirectory from a previous Tor install. Reported
1219 - Fix a crash when we fetch a descriptor that turns out to be
1220 unexpected (it used to be in our networkstatus when we started
1221 fetching it, but it isn't in our current networkstatus), and we
1222 aren't using bridges. Bugfix on 0.2.0.x.
1223 - Fix a crash when accessing hidden services: it would work the first
1224 time you use a given introduction point for your service, but
1225 on subsequent requests we'd be using garbage memory. Fixed by
1226 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
1227 - Fix a crash when we load a bridge descriptor from disk but we don't
1228 currently have a Bridge line for it in our torrc. Bugfix on
1232 - If bridge authorities set BridgePassword, they will serve a
1233 snapshot of known bridge routerstatuses from their DirPort to
1234 anybody who knows that password. Unset by default.
1237 - Make the unit tests build again.
1238 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
1239 - Make PublishServerDescriptor default to 1, so the default doesn't
1240 have to change as we invent new directory protocol versions.
1241 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
1242 be included unless sys/time.h is already included. Fixes
1243 bug 553. Bugfix on 0.2.0.x.
1244 - If we receive a general-purpose descriptor and then receive an
1245 identical bridge-purpose descriptor soon after, don't discard
1246 the next one as a duplicate.
1249 - If BridgeRelay is set to 1, then the default for
1250 PublishServerDescriptor is now "bridge" rather than "v2,v3".
1251 - If the user sets RelayBandwidthRate but doesn't set
1252 RelayBandwidthBurst, then make them equal rather than erroring out.
1255 Changes in version 0.2.0.13-alpha - 2007-12-21
1256 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
1257 Goodell, fixes many more bugs, and adds a lot of infrastructure for
1260 o New directory authorities:
1261 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
1265 - Only update guard status (usable / not usable) once we have
1266 enough directory information. This was causing us to always pick
1267 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
1268 causing us to discard all our guards on startup if we hadn't been
1269 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
1270 - Purge old entries from the "rephist" database and the hidden
1271 service descriptor databases even when DirPort is zero. Bugfix
1273 - We were ignoring our RelayBandwidthRate for the first 30 seconds
1274 after opening a circuit -- even a relayed circuit. Bugfix on
1276 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
1277 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
1278 crashing or mis-answering these types of requests.
1279 - Relays were publishing their server descriptor to v1 and v2
1280 directory authorities, but they didn't try publishing to v3-only
1281 authorities. Fix this; and also stop publishing to v1 authorities.
1283 - When we were reading router descriptors from cache, we were ignoring
1284 the annotations -- so for example we were reading in bridge-purpose
1285 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
1286 - When we decided to send a 503 response to a request for servers, we
1287 were then also sending the server descriptors: this defeats the
1288 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
1291 - Bridge relays now behave like clients with respect to time
1292 intervals for downloading new consensus documents -- otherwise they
1293 stand out. Bridge users now wait until the end of the interval,
1294 so their bridge relay will be sure to have a new consensus document.
1295 - Three new config options (AlternateDirAuthority,
1296 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
1297 user selectively replace the default directory authorities by type,
1298 rather than the all-or-nothing replacement that DirServer offers.
1299 - Tor can now be configured to read a GeoIP file from disk in one
1300 of two formats. This can be used by controllers to map IP addresses
1301 to countries. Eventually, it may support exit-by-country.
1302 - When possible, bridge relays remember which countries users
1303 are coming from, and report aggregate information in their
1304 extra-info documents, so that the bridge authorities can learn
1305 where Tor is blocked.
1306 - Bridge directory authorities now do reachability testing on the
1307 bridges they know. They provide router status summaries to the
1308 controller via "getinfo ns/purpose/bridge", and also dump summaries
1309 to a file periodically.
1310 - Stop fetching directory info so aggressively if your DirPort is
1311 on but your ORPort is off; stop fetching v2 dir info entirely.
1312 You can override these choices with the new FetchDirInfoEarly
1316 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
1317 consensus documents when there are too many relays at a single
1318 IP address. Now clear it in v2 network status documents too, and
1319 also clear it in routerinfo_t when the relay is no longer listed
1320 in the relevant networkstatus document.
1321 - Don't crash if we get an unexpected value for the
1322 PublishServerDescriptor config option. Reported by Matt Edman;
1323 bugfix on 0.2.0.9-alpha.
1324 - Our new v2 hidden service descriptor format allows descriptors
1325 that have no introduction points. But Tor crashed when we tried
1326 to build a descriptor with no intro points (and it would have
1327 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
1329 - Fix building with dmalloc 5.5.2 with glibc.
1330 - Reject uploaded descriptors and extrainfo documents if they're
1331 huge. Otherwise we'll cache them all over the network and it'll
1332 clog everything up. Reported by Aljosha Judmayer.
1333 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
1334 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
1335 - When the DANGEROUS_VERSION controller status event told us we're
1336 running an obsolete version, it used the string "OLD" to describe
1337 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
1338 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
1339 - If we can't expand our list of entry guards (e.g. because we're
1340 using bridges or we have StrictEntryNodes set), don't mark relays
1341 down when they fail a directory request. Otherwise we're too quick
1342 to mark all our entry points down. Bugfix on 0.1.2.x.
1343 - Fix handling of hex nicknames when answering controller requests for
1344 networkstatus by name, or when deciding whether to warn about unknown
1345 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
1346 - Fix a couple of hard-to-trigger autoconf problems that could result
1347 in really weird results on platforms whose sys/types.h files define
1348 nonstandard integer types. Bugfix on 0.1.2.x.
1349 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
1350 - Don't crash on name lookup when we have no current consensus. Fixes
1351 bug 538; bugfix on 0.2.0.x.
1352 - Only Tors that want to mirror the v2 directory info should
1353 create the "cached-status" directory in their datadir. (All Tors
1354 used to create it.) Bugfix on 0.2.0.9-alpha.
1355 - Directory authorities should only automatically download Extra Info
1356 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
1359 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
1360 consumers. (We already do this on HUP.)
1361 - Authorities and caches fetch the v2 networkstatus documents
1362 less often, now that v3 is encouraged.
1363 - Add a new config option BridgeRelay that specifies you want to
1364 be a bridge relay. Right now the only difference is that it makes
1365 you answer begin_dir requests, and it makes you cache dir info,
1366 even if your DirPort isn't on.
1367 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
1368 ask about source, timestamp of arrival, purpose, etc. We need
1369 something like this to help Vidalia not do GeoIP lookups on bridge
1371 - Allow multiple HashedControlPassword config lines, to support
1372 multiple controller passwords.
1373 - Authorities now decide whether they're authoritative for a given
1374 router based on the router's purpose.
1375 - New config options AuthDirBadDir and AuthDirListBadDirs for
1376 authorities to mark certain relays as "bad directories" in the
1377 networkstatus documents. Also supports the "!baddir" directive in
1378 the approved-routers file.
1381 Changes in version 0.2.0.12-alpha - 2007-11-16
1382 This twelfth development snapshot fixes some more build problems as
1383 well as a few minor bugs.
1386 - Make it build on OpenBSD again. Patch from tup.
1387 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
1388 package-building for Red Hat, OS X, etc.
1390 o Minor bugfixes (on 0.1.2.x):
1391 - Changing the ExitPolicyRejectPrivate setting should cause us to
1392 rebuild our server descriptor.
1394 o Minor bugfixes (on 0.2.0.x):
1395 - When we're lacking a consensus, don't try to perform rendezvous
1396 operations. Reported by Karsten Loesing.
1397 - Fix a small memory leak whenever we decide against using a
1398 newly picked entry guard. Reported by Mike Perry.
1399 - When authorities detected more than two relays running on the same
1400 IP address, they were clearing all the status flags but forgetting
1401 to clear the "hsdir" flag. So clients were being told that a
1402 given relay was the right choice for a v2 hsdir lookup, yet they
1403 never had its descriptor because it was marked as 'not running'
1405 - If we're trying to fetch a bridge descriptor and there's no way
1406 the bridge authority could help us (for example, we don't know
1407 a digest, or there is no bridge authority), don't be so eager to
1408 fall back to asking the bridge authority.
1409 - If we're using bridges or have strictentrynodes set, and our
1410 chosen exit is in the same family as all our bridges/entry guards,
1411 then be flexible about families.
1414 - When we negotiate a v2 link-layer connection (not yet implemented),
1415 accept RELAY_EARLY cells and turn them into RELAY cells if we've
1416 negotiated a v1 connection for their next step. Initial code for
1420 Changes in version 0.2.0.11-alpha - 2007-11-12
1421 This eleventh development snapshot fixes some build problems with
1422 the previous snapshot. It also includes a more secure-by-default exit
1423 policy for relays, fixes an enormous memory leak for exit relays, and
1424 fixes another bug where servers were falling out of the directory list.
1427 - Exit policies now reject connections that are addressed to a
1428 relay's public (external) IP address too, unless
1429 ExitPolicyRejectPrivate is turned off. We do this because too
1430 many relays are running nearby to services that trust them based
1431 on network address. Bugfix on 0.1.2.x.
1434 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
1435 on every successful resolve. Reported by Mike Perry; bugfix
1437 - On authorities, never downgrade to old router descriptors simply
1438 because they're listed in the consensus. This created a catch-22
1439 where we wouldn't list a new descriptor because there was an
1440 old one in the consensus, and we couldn't get the new one in the
1441 consensus because we wouldn't list it. Possible fix for bug 548.
1442 Also, this might cause bug 543 to appear on authorities; if so,
1443 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
1445 o Packaging fixes on 0.2.0.10-alpha:
1446 - We were including instructions about what to do with the
1447 src/config/fallback-consensus file, but we weren't actually
1448 including it in the tarball. Disable all of that for now.
1451 - Allow people to say PreferTunnelledDirConns rather than
1452 PreferTunneledDirConns, for those alternate-spellers out there.
1455 - Don't reevaluate all the information from our consensus document
1456 just because we've downloaded a v2 networkstatus that we intend
1457 to cache. Fixes bug 545; bugfix on 0.2.0.x.
1460 Changes in version 0.2.0.10-alpha - 2007-11-10
1461 This tenth development snapshot adds a third v3 directory authority
1462 run by Mike Perry, adds most of Karsten Loesing's new hidden service
1463 descriptor format, fixes a bad crash bug and new bridge bugs introduced
1464 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
1465 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
1466 addresses many more minor issues.
1468 o New directory authorities:
1469 - Set up ides (run by Mike Perry) as the third v3 directory authority.
1472 - Allow tunnelled directory connections to ask for an encrypted
1473 "begin_dir" connection or an anonymized "uses a full Tor circuit"
1474 connection independently. Now we can make anonymized begin_dir
1475 connections for (e.g.) more secure hidden service posting and
1477 - More progress on proposal 114: code from Karsten Loesing to
1478 implement new hidden service descriptor format.
1479 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
1480 accommodate the growing number of servers that use the default
1481 and are reaching it.
1482 - Directory authorities use a new formula for selecting which nodes
1483 to advertise as Guards: they must be in the top 7/8 in terms of
1484 how long we have known about them, and above the median of those
1485 nodes in terms of weighted fractional uptime.
1486 - Make "not enough dir info yet" warnings describe *why* Tor feels
1487 it doesn't have enough directory info yet.
1490 - Stop servers from crashing if they set a Family option (or
1491 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
1493 - Make bridge users work again -- the move to v3 directories in
1494 0.2.0.9-alpha had introduced a number of bugs that made bridges
1495 no longer work for clients.
1496 - When the clock jumps forward a lot, do not allow the bandwidth
1497 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
1499 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
1500 - When the consensus lists a router descriptor that we previously were
1501 mirroring, but that we considered non-canonical, reload the
1502 descriptor as canonical. This fixes bug 543 where Tor servers
1503 would start complaining after a few days that they don't have
1504 enough directory information to build a circuit.
1505 - Consider replacing the current consensus when certificates arrive
1506 that make the pending consensus valid. Previously, we were only
1507 considering replacement when the new certs _didn't_ help.
1508 - Fix an assert error on startup if we didn't already have the
1509 consensus and certs cached in our datadirectory: we were caching
1510 the consensus in consensus_waiting_for_certs but then free'ing it
1512 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
1513 Request) if we need more v3 certs but we've already got pending
1514 requests for all of them.
1515 - Correctly back off from failing certificate downloads. Fixes
1517 - Authorities don't vote on the Running flag if they have been running
1518 for less than 30 minutes themselves. Fixes bug 547, where a newly
1519 started authority would vote that everyone was down.
1522 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
1523 it, it had no AES, and it hasn't seen any security patches since
1527 - Clients now hold circuitless TLS connections open for 1.5 times
1528 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
1529 rebuild a new circuit over them within that timeframe. Previously,
1530 they held them open only for KeepalivePeriod (5 minutes).
1531 - Use "If-Modified-Since" to avoid retrieving consensus
1532 networkstatuses that we already have.
1533 - When we have no consensus, check FallbackNetworkstatusFile (defaults
1534 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
1535 we start knowing some directory caches.
1536 - When we receive a consensus from the future, warn about skew.
1537 - Improve skew reporting: try to give the user a better log message
1538 about how skewed they are, and how much this matters.
1539 - When we have a certificate for an authority, believe that
1540 certificate's claims about the authority's IP address.
1541 - New --quiet command-line option to suppress the default console log.
1542 Good in combination with --hash-password.
1543 - Authorities send back an X-Descriptor-Not-New header in response to
1544 an accepted-but-discarded descriptor upload. Partially implements
1546 - Make the log message for "tls error. breaking." more useful.
1547 - Better log messages about certificate downloads, to attempt to
1548 track down the second incarnation of bug 546.
1550 o Minor features (bridges):
1551 - If bridge users set UpdateBridgesFromAuthority, but the digest
1552 they ask for is a 404 from the bridge authority, they now fall
1553 back to trying the bridge directly.
1554 - Bridges now use begin_dir to publish their server descriptor to
1555 the bridge authority, even when they haven't set TunnelDirConns.
1557 o Minor features (controller):
1558 - When reporting clock skew, and we know that the clock is _at least
1559 as skewed_ as some value, but we don't know the actual value,
1560 report the value as a "minimum skew."
1563 - Update linux-tor-prio.sh script to allow QoS based on the uid of
1564 the Tor process. Patch from Marco Bonetti with tweaks from Mike
1568 - Refuse to start if both ORPort and UseBridges are set. Bugfix
1569 on 0.2.0.x, suggested by Matt Edman.
1570 - Don't stop fetching descriptors when FetchUselessDescriptors is
1571 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
1572 reported by tup and ioerror.
1573 - Better log message on vote from unknown authority.
1574 - Don't log "Launching 0 request for 0 router" message.
1576 o Minor bugfixes (memory leaks):
1577 - Stop leaking memory every time we parse a v3 certificate. Bugfix
1579 - Stop leaking memory every time we load a v3 certificate. Bugfix
1580 on 0.2.0.1-alpha. Fixes bug 536.
1581 - Stop leaking a cached networkstatus on exit. Bugfix on
1583 - Stop leaking voter information every time we free a consensus.
1584 Bugfix on 0.2.0.3-alpha.
1585 - Stop leaking signed data every time we check a voter signature.
1586 Bugfix on 0.2.0.3-alpha.
1587 - Stop leaking a signature every time we fail to parse a consensus or
1588 a vote. Bugfix on 0.2.0.3-alpha.
1589 - Stop leaking v2_download_status_map on shutdown. Bugfix on
1591 - Stop leaking conn->nickname every time we make a connection to a
1592 Tor relay without knowing its expected identity digest (e.g. when
1593 using bridges). Bugfix on 0.2.0.3-alpha.
1595 - Minor bugfixes (portability):
1596 - Run correctly on platforms where rlim_t is larger than unsigned
1597 long, and/or where the real limit for number of open files is
1598 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
1599 particular, these may be needed for OS X 10.5.
1602 Changes in version 0.1.2.18 - 2007-10-28
1603 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
1604 hidden service introduction that were causing huge delays, and a big
1605 bug that was causing some servers to disappear from the network status
1606 lists for a few hours each day.
1608 o Major bugfixes (crashes):
1609 - If a connection is shut down abruptly because of something that
1610 happened inside connection_flushed_some(), do not call
1611 connection_finished_flushing(). Should fix bug 451:
1612 "connection_stop_writing: Assertion conn->write_event failed"
1613 Bugfix on 0.1.2.7-alpha.
1614 - Fix possible segfaults in functions called from
1615 rend_process_relay_cell().
1617 o Major bugfixes (hidden services):
1618 - Hidden services were choosing introduction points uniquely by
1619 hexdigest, but when constructing the hidden service descriptor
1620 they merely wrote the (potentially ambiguous) nickname.
1621 - Clients now use the v2 intro format for hidden service
1622 connections: they specify their chosen rendezvous point by identity
1623 digest rather than by (potentially ambiguous) nickname. These
1624 changes could speed up hidden service connections dramatically.
1626 o Major bugfixes (other):
1627 - Stop publishing a new server descriptor just because we get a
1628 HUP signal. This led (in a roundabout way) to some servers getting
1629 dropped from the networkstatus lists for a few hours each day.
1630 - When looking for a circuit to cannibalize, consider family as well
1631 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
1632 circuit cannibalization).
1633 - When a router wasn't listed in a new networkstatus, we were leaving
1634 the flags for that router alone -- meaning it remained Named,
1635 Running, etc -- even though absence from the networkstatus means
1636 that it shouldn't be considered to exist at all anymore. Now we
1637 clear all the flags for routers that fall out of the networkstatus
1638 consensus. Fixes bug 529.
1641 - Don't try to access (or alter) the state file when running
1642 --list-fingerprint or --verify-config or --hash-password. Resolves
1644 - When generating information telling us how to extend to a given
1645 router, do not try to include the nickname if it is
1646 absent. Resolves bug 467.
1647 - Fix a user-triggerable segfault in expand_filename(). (There isn't
1648 a way to trigger this remotely.)
1649 - When sending a status event to the controller telling it that an
1650 OR address is reachable, set the port correctly. (Previously we
1651 were reporting the dir port.)
1652 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
1653 command. Bugfix on 0.1.2.17.
1654 - When loading bandwidth history, do not believe any information in
1655 the future. Fixes bug 434.
1656 - When loading entry guard information, do not believe any information
1658 - When we have our clock set far in the future and generate an
1659 onion key, then re-set our clock to be correct, we should not stop
1660 the onion key from getting rotated.
1661 - On some platforms, accept() can return a broken address. Detect
1662 this more quietly, and deal accordingly. Fixes bug 483.
1663 - It's not actually an error to find a non-pending entry in the DNS
1664 cache when canceling a pending resolve. Don't log unless stuff
1665 is fishy. Resolves bug 463.
1666 - Don't reset trusted dir server list when we set a configuration
1667 option. Patch from Robert Hogan.
1668 - Don't try to create the datadir when running --verify-config or
1669 --hash-password. Resolves bug 540.
1672 Changes in version 0.2.0.9-alpha - 2007-10-24
1673 This ninth development snapshot switches clients to the new v3 directory
1674 system; allows servers to be listed in the network status even when they
1675 have the same nickname as a registered server; and fixes many other
1676 bugs including a big one that was causing some servers to disappear
1677 from the network status lists for a few hours each day.
1679 o Major features (directory system):
1680 - Clients now download v3 consensus networkstatus documents instead
1681 of v2 networkstatus documents. Clients and caches now base their
1682 opinions about routers on these consensus documents. Clients only
1683 download router descriptors listed in the consensus.
1684 - Authorities now list servers who have the same nickname as
1685 a different named server, but list them with a new flag,
1686 "Unnamed". Now we can list servers that happen to pick the same
1687 nickname as a server that registered two years ago and then
1688 disappeared. Partially implements proposal 122.
1689 - If the consensus lists a router as "Unnamed", the name is assigned
1690 to a different router: do not identify the router by that name.
1691 Partially implements proposal 122.
1692 - Authorities can now come to a consensus on which method to use to
1693 compute the consensus. This gives us forward compatibility.
1696 - Stop publishing a new server descriptor just because we HUP or
1697 when we find our DirPort to be reachable but won't actually publish
1698 it. New descriptors without any real changes are dropped by the
1699 authorities, and can screw up our "publish every 18 hours" schedule.
1701 - When a router wasn't listed in a new networkstatus, we were leaving
1702 the flags for that router alone -- meaning it remained Named,
1703 Running, etc -- even though absence from the networkstatus means
1704 that it shouldn't be considered to exist at all anymore. Now we
1705 clear all the flags for routers that fall out of the networkstatus
1706 consensus. Fixes bug 529; bugfix on 0.1.2.x.
1707 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
1708 extrainfo documents and then discard them immediately for not
1709 matching the latest router. Bugfix on 0.2.0.1-alpha.
1711 o Minor features (v3 directory protocol):
1712 - Allow tor-gencert to generate a new certificate without replacing
1714 - Allow certificates to include an address.
1715 - When we change our directory-cache settings, reschedule all voting
1716 and download operations.
1717 - Reattempt certificate downloads immediately on failure, as long as
1718 we haven't failed a threshold number of times yet.
1719 - Delay retrying consensus downloads while we're downloading
1720 certificates to verify the one we just got. Also, count getting a
1721 consensus that we already have (or one that isn't valid) as a failure,
1722 and count failing to get the certificates after 20 minutes as a
1724 - Build circuits and download descriptors even if our consensus is a
1725 little expired. (This feature will go away once authorities are
1728 o Minor features (router descriptor cache):
1729 - If we find a cached-routers file that's been sitting around for more
1730 than 28 days unmodified, then most likely it's a leftover from
1731 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
1733 - When we (as a cache) download a descriptor because it was listed
1734 in a consensus, remember when the consensus was supposed to expire,
1735 and don't expire the descriptor until then.
1737 o Minor features (performance):
1738 - Call routerlist_remove_old_routers() much less often. This should
1739 speed startup, especially on directory caches.
1740 - Don't try to launch new descriptor downloads quite so often when we
1741 already have enough directory information to build circuits.
1742 - Base64 decoding was actually showing up on our profile when parsing
1743 the initial descriptor file; switch to an in-process all-at-once
1744 implementation that's about 3.5x times faster than calling out to
1747 o Minor features (compilation):
1748 - Detect non-ASCII platforms (if any still exist) and refuse to
1749 build there: some of our code assumes that 'A' is 65 and so on.
1751 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
1752 - Make the "next period" votes into "current period" votes immediately
1753 after publishing the consensus; avoid a heisenbug that made them
1754 stick around indefinitely.
1755 - When we discard a vote as a duplicate, do not report this as
1757 - Treat missing v3 keys or certificates as an error when running as a
1758 v3 directory authority.
1759 - When we're configured to be a v3 authority, but we're only listed
1760 as a non-v3 authority in our DirServer line for ourself, correct
1762 - If an authority doesn't have a qualified hostname, just put
1763 its address in the vote. This fixes the problem where we referred to
1764 "moria on moria:9031."
1765 - Distinguish between detached signatures for the wrong period, and
1766 detached signatures for a divergent vote.
1767 - Fix a small memory leak when computing a consensus.
1768 - When there's no concensus, we were forming a vote every 30
1769 minutes, but writing the "valid-after" line in our vote based
1770 on our configured V3AuthVotingInterval: so unless the intervals
1771 matched up, we immediately rejected our own vote because it didn't
1772 start at the voting interval that caused us to construct a vote.
1774 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
1775 - Delete unverified-consensus when the real consensus is set.
1776 - Consider retrying a consensus networkstatus fetch immediately
1777 after one fails: don't wait 60 seconds to notice.
1778 - When fetching a consensus as a cache, wait until a newer consensus
1779 should exist before trying to replace the current one.
1780 - Use a more forgiving schedule for retrying failed consensus
1781 downloads than for other types.
1783 o Minor bugfixes (other directory issues):
1784 - Correct the implementation of "download votes by digest." Bugfix on
1786 - Authorities no longer send back "400 you're unreachable please fix
1787 it" errors to Tor servers that aren't online all the time. We're
1788 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
1790 o Minor bugfixes (controller):
1791 - Don't reset trusted dir server list when we set a configuration
1792 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
1793 - Respond to INT and TERM SIGNAL commands before we execute the
1794 signal, in case the signal shuts us down. We had a patch in
1795 0.1.2.1-alpha that tried to do this by queueing the response on
1796 the connection's buffer before shutting down, but that really
1797 isn't the same thing at all. Bug located by Matt Edman.
1799 o Minor bugfixes (misc):
1800 - Correctly check for bad options to the "PublishServerDescriptor"
1801 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
1802 - Stop leaking memory on failing case of base32_decode, and make
1803 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
1804 - Don't try to download extrainfo documents when we're trying to
1805 fetch enough directory info to build a circuit: having enough
1806 info should get priority. Bugfix on 0.2.0.x.
1807 - Don't complain that "your server has not managed to confirm that its
1808 ports are reachable" if we haven't been able to build any circuits
1809 yet. Bug found by spending four hours without a v3 consensus. Bugfix
1811 - Detect the reason for failing to mmap a descriptor file we just
1812 wrote, and give a more useful log message. Fixes bug 533. Bugfix
1815 o Code simplifications and refactoring:
1816 - Remove support for the old bw_accounting file: we've been storing
1817 bandwidth accounting information in the state file since
1818 0.1.2.5-alpha. This may result in bandwidth accounting errors
1819 if you try to upgrade from 0.1.1.x or earlier, or if you try to
1820 downgrade to 0.1.1.x or earlier.
1821 - New convenience code to locate a file within the DataDirectory.
1822 - Move non-authority functionality out of dirvote.c.
1823 - Refactor the arguments for router_pick_{directory_|trusteddir}server
1824 so that they all take the same named flags.
1827 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
1828 Unix users an easy way to script their Tor process (e.g. by
1829 adjusting bandwidth based on the time of the day).
1832 Changes in version 0.2.0.8-alpha - 2007-10-12
1833 This eighth development snapshot fixes a crash bug that's been bothering
1834 us since February 2007, lets bridge authorities store a list of bridge
1835 descriptors they've seen, gets v3 directory voting closer to working,
1836 starts caching v3 directory consensus documents on directory mirrors,
1837 and fixes a variety of smaller issues including some minor memory leaks.
1839 o Major features (router descriptor cache):
1840 - Store routers in a file called cached-descriptors instead of in
1841 cached-routers. Initialize cached-descriptors from cached-routers
1842 if the old format is around. The new format allows us to store
1843 annotations along with descriptors.
1844 - Use annotations to record the time we received each descriptor, its
1845 source, and its purpose.
1846 - Disable the SETROUTERPURPOSE controller command: it is now
1848 - Controllers should now specify cache=no or cache=yes when using
1849 the +POSTDESCRIPTOR command.
1850 - Bridge authorities now write bridge descriptors to disk, meaning
1851 we can export them to other programs and begin distributing them
1854 o Major features (directory authorities):
1855 - When a v3 authority is missing votes or signatures, it now tries
1857 - Directory authorities track weighted fractional uptime as well as
1858 weighted mean-time-between failures. WFU is suitable for deciding
1859 whether a node is "usually up", while MTBF is suitable for deciding
1860 whether a node is "likely to stay up." We need both, because
1861 "usually up" is a good requirement for guards, while "likely to
1862 stay up" is a good requirement for long-lived connections.
1864 o Major features (v3 directory system):
1865 - Caches now download v3 network status documents as needed,
1866 and download the descriptors listed in them.
1867 - All hosts now attempt to download and keep fresh v3 authority
1868 certificates, and re-attempt after failures.
1869 - More internal-consistency checks for vote parsing.
1871 o Major bugfixes (crashes):
1872 - If a connection is shut down abruptly because of something that
1873 happened inside connection_flushed_some(), do not call
1874 connection_finished_flushing(). Should fix bug 451. Bugfix on
1877 o Major bugfixes (performance):
1878 - Fix really bad O(n^2) performance when parsing a long list of
1879 routers: Instead of searching the entire list for an "extra-info "
1880 string which usually wasn't there, once for every routerinfo
1881 we read, just scan lines forward until we find one we like.
1883 - When we add data to a write buffer in response to the data on that
1884 write buffer getting low because of a flush, do not consider the
1885 newly added data as a candidate for immediate flushing, but rather
1886 make it wait until the next round of writing. Otherwise, we flush
1887 and refill recursively, and a single greedy TLS connection can
1888 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
1890 o Minor features (v3 authority system):
1891 - Add more ways for tools to download the votes that lead to the
1893 - Send a 503 when low on bandwidth and a vote, consensus, or
1894 certificate is requested.
1895 - If-modified-since is now implemented properly for all kinds of
1896 certificate requests.
1898 o Minor bugfixes (network statuses):
1899 - Tweak the implementation of proposal 109 slightly: allow at most
1900 two Tor servers on the same IP address, except if it's the location
1901 of a directory authority, in which case allow five. Bugfix on
1904 o Minor bugfixes (controller):
1905 - When sending a status event to the controller telling it that an
1906 OR address is reachable, set the port correctly. (Previously we
1907 were reporting the dir port.) Bugfix on 0.1.2.x.
1909 o Minor bugfixes (v3 directory system):
1910 - Fix logic to look up a cert by its signing key digest. Bugfix on
1912 - Only change the reply to a vote to "OK" if it's not already
1913 set. This gets rid of annoying "400 OK" log messages, which may
1914 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
1915 - When we get a valid consensus, recompute the voting schedule.
1916 - Base the valid-after time of a vote on the consensus voting
1917 schedule, not on our preferred schedule.
1918 - Make the return values and messages from signature uploads and
1919 downloads more sensible.
1920 - Fix a memory leak when serving votes and consensus documents, and
1921 another when serving certificates.
1923 o Minor bugfixes (performance):
1924 - Use a slightly simpler string hashing algorithm (copying Python's
1925 instead of Java's) and optimize our digest hashing algorithm to take
1926 advantage of 64-bit platforms and to remove some possibly-costly
1928 - Fix a minor memory leak whenever we parse guards from our state
1929 file. Bugfix on 0.2.0.7-alpha.
1930 - Fix a minor memory leak whenever we write out a file. Bugfix on
1932 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
1933 command. Bugfix on 0.2.0.5-alpha.
1935 o Minor bugfixes (portability):
1936 - On some platforms, accept() can return a broken address. Detect
1937 this more quietly, and deal accordingly. Fixes bug 483.
1938 - Stop calling tor_strlower() on uninitialized memory in some cases.
1939 Bugfix in 0.2.0.7-alpha.
1941 o Minor bugfixes (usability):
1942 - Treat some 403 responses from directory servers as INFO rather than
1943 WARN-severity events.
1944 - It's not actually an error to find a non-pending entry in the DNS
1945 cache when canceling a pending resolve. Don't log unless stuff is
1946 fishy. Resolves bug 463.
1948 o Minor bugfixes (anonymity):
1949 - Never report that we've used more bandwidth than we're willing to
1950 relay: it leaks how much non-relay traffic we're using. Resolves
1952 - When looking for a circuit to cannibalize, consider family as well
1953 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
1954 circuit cannibalization).
1956 o Code simplifications and refactoring:
1957 - Make a bunch of functions static. Remove some dead code.
1958 - Pull out about a third of the really big routerlist.c; put it in a
1959 new module, networkstatus.c.
1960 - Merge the extra fields in local_routerstatus_t back into
1961 routerstatus_t: we used to need one routerstatus_t for each
1962 authority's opinion, plus a local_routerstatus_t for the locally
1963 computed consensus opinion. To save space, we put the locally
1964 modified fields into local_routerstatus_t, and only the common
1965 stuff into routerstatus_t. But once v3 directories are in use,
1966 clients and caches will no longer need to hold authority opinions;
1967 thus, the rationale for keeping the types separate is now gone.
1968 - Make the code used to reschedule and reattempt downloads more
1970 - Turn all 'Are we a directory server/mirror?' logic into a call to
1972 - Remove the code to generate the oldest (v1) directory format.
1973 The code has been disabled since 0.2.0.5-alpha.
1976 Changes in version 0.2.0.7-alpha - 2007-09-21
1977 This seventh development snapshot makes bridges work again, makes bridge
1978 authorities work for the first time, fixes two huge performance flaws
1979 in hidden services, and fixes a variety of minor issues.
1981 o New directory authorities:
1982 - Set up moria1 and tor26 as the first v3 directory authorities. See
1983 doc/spec/dir-spec.txt for details on the new directory design.
1985 o Major bugfixes (crashes):
1986 - Fix possible segfaults in functions called from
1987 rend_process_relay_cell(). Bugfix on 0.1.2.x.
1989 o Major bugfixes (bridges):
1990 - Fix a bug that made servers send a "404 Not found" in response to
1991 attempts to fetch their server descriptor. This caused Tor servers
1992 to take many minutes to establish reachability for their DirPort,
1993 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
1994 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
1995 users configure that and specify a bridge with an identity
1996 fingerprint, now they will lookup the bridge descriptor at the
1997 default bridge authority via a one-hop tunnel, but once circuits
1998 are established they will switch to a three-hop tunnel for later
1999 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
2001 o Major bugfixes (hidden services):
2002 - Hidden services were choosing introduction points uniquely by
2003 hexdigest, but when constructing the hidden service descriptor
2004 they merely wrote the (potentially ambiguous) nickname.
2005 - Clients now use the v2 intro format for hidden service
2006 connections: they specify their chosen rendezvous point by identity
2007 digest rather than by (potentially ambiguous) nickname. Both
2008 are bugfixes on 0.1.2.x, and they could speed up hidden service
2009 connections dramatically. Thanks to Karsten Loesing.
2011 o Minor features (security):
2012 - As a client, do not believe any server that tells us that an
2013 address maps to an internal address space.
2014 - Make it possible to enable HashedControlPassword and
2015 CookieAuthentication at the same time.
2017 o Minor features (guard nodes):
2018 - Tag every guard node in our state file with the version that
2019 we believe added it, or with our own version if we add it. This way,
2020 if a user temporarily runs an old version of Tor and then switches
2021 back to a new one, she doesn't automatically lose her guards.
2023 o Minor features (speed):
2024 - When implementing AES counter mode, update only the portions of the
2025 counter buffer that need to change, and don't keep separate
2026 network-order and host-order counters when they are the same (i.e.,
2027 on big-endian hosts.)
2029 o Minor features (controller):
2030 - Accept LF instead of CRLF on controller, since some software has a
2031 hard time generating real Internet newlines.
2032 - Add GETINFO values for the server status events
2033 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
2037 - Routers no longer include bandwidth-history lines in their
2038 descriptors; this information is already available in extra-info
2039 documents, and including it in router descriptors took up 60%
2040 (!) of compressed router descriptor downloads. Completes
2041 implementation of proposal 104.
2042 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
2043 and TorControl.py, as they use the old v0 controller protocol,
2044 and are obsoleted by TorFlow anyway.
2045 - Drop support for v1 rendezvous descriptors, since we never used
2046 them anyway, and the code has probably rotted by now. Based on
2047 patch from Karsten Loesing.
2048 - On OSX, stop warning the user that kqueue support in libevent is
2049 "experimental", since it seems to have worked fine for ages.
2052 - When generating information telling us how to extend to a given
2053 router, do not try to include the nickname if it is absent. Fixes
2054 bug 467. Bugfix on 0.2.0.3-alpha.
2055 - Fix a user-triggerable (but not remotely-triggerable) segfault
2056 in expand_filename(). Bugfix on 0.1.2.x.
2057 - Fix a memory leak when freeing incomplete requests from DNSPort.
2058 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
2059 - Don't try to access (or alter) the state file when running
2060 --list-fingerprint or --verify-config or --hash-password. (Resolves
2061 bug 499.) Bugfix on 0.1.2.x.
2062 - Servers used to decline to publish their DirPort if their
2063 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
2064 were below a threshold. Now they only look at BandwidthRate and
2065 RelayBandwidthRate. Bugfix on 0.1.2.x.
2066 - Remove an optimization in the AES counter-mode code that assumed
2067 that the counter never exceeded 2^68. When the counter can be set
2068 arbitrarily as an IV (as it is by Karsten's new hidden services
2069 code), this assumption no longer holds. Bugfix on 0.1.2.x.
2070 - Resume listing "AUTHORITY" flag for authorities in network status.
2071 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
2073 o Code simplifications and refactoring:
2074 - Revamp file-writing logic so we don't need to have the entire
2075 contents of a file in memory at once before we write to disk. Tor,
2077 - Turn "descriptor store" into a full-fledged type.
2078 - Move all NT services code into a separate source file.
2079 - Unify all code that computes medians, percentile elements, etc.
2080 - Get rid of a needless malloc when parsing address policies.
2083 Changes in version 0.1.2.17 - 2007-08-30
2084 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
2085 X bundles. Vidalia 0.0.14 makes authentication required for the
2086 ControlPort in the default configuration, which addresses important
2087 security risks. Everybody who uses Vidalia (or another controller)
2090 In addition, this Tor update fixes major load balancing problems with
2091 path selection, which should speed things up a lot once many people
2094 o Major bugfixes (security):
2095 - We removed support for the old (v0) control protocol. It has been
2096 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
2097 become more of a headache than it's worth.
2099 o Major bugfixes (load balancing):
2100 - When choosing nodes for non-guard positions, weight guards
2101 proportionally less, since they already have enough load. Patch
2103 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
2104 will allow fast Tor servers to get more attention.
2105 - When we're upgrading from an old Tor version, forget our current
2106 guards and pick new ones according to the new weightings. These
2107 three load balancing patches could raise effective network capacity
2108 by a factor of four. Thanks to Mike Perry for measurements.
2110 o Major bugfixes (stream expiration):
2111 - Expire not-yet-successful application streams in all cases if
2112 they've been around longer than SocksTimeout. Right now there are
2113 some cases where the stream will live forever, demanding a new
2114 circuit every 15 seconds. Fixes bug 454; reported by lodger.
2116 o Minor features (controller):
2117 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
2118 is valid before any authentication has been received. It tells
2119 a controller what kind of authentication is expected, and what
2120 protocol is spoken. Implements proposal 119.
2122 o Minor bugfixes (performance):
2123 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
2124 greatly speeding up loading cached-routers from disk on startup.
2125 - Disable sentinel-based debugging for buffer code: we squashed all
2126 the bugs that this was supposed to detect a long time ago, and now
2127 its only effect is to change our buffer sizes from nice powers of
2128 two (which platform mallocs tend to like) to values slightly over
2129 powers of two (which make some platform mallocs sad).
2131 o Minor bugfixes (misc):
2132 - If exit bandwidth ever exceeds one third of total bandwidth, then
2133 use the correct formula to weight exit nodes when choosing paths.
2134 Based on patch from Mike Perry.
2135 - Choose perfectly fairly among routers when choosing by bandwidth and
2136 weighting by fraction of bandwidth provided by exits. Previously, we
2137 would choose with only approximate fairness, and correct ourselves
2138 if we ran off the end of the list.
2139 - If we require CookieAuthentication but we fail to write the
2140 cookie file, we would warn but not exit, and end up in a state
2141 where no controller could authenticate. Now we exit.
2142 - If we require CookieAuthentication, stop generating a new cookie
2143 every time we change any piece of our config.
2144 - Refuse to start with certain directory authority keys, and
2145 encourage people using them to stop.
2146 - Terminate multi-line control events properly. Original patch
2148 - Fix a minor memory leak when we fail to find enough suitable
2149 servers to choose a circuit.
2150 - Stop leaking part of the descriptor when we run into a particularly
2151 unparseable piece of it.
2154 Changes in version 0.2.0.6-alpha - 2007-08-26
2155 This sixth development snapshot features a new Vidalia version in the
2156 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
2157 the ControlPort in the default configuration, which addresses important
2160 In addition, this snapshot fixes major load balancing problems
2161 with path selection, which should speed things up a lot once many
2162 people have upgraded. The directory authorities also use a new
2163 mean-time-between-failure approach to tracking which servers are stable,
2164 rather than just looking at the most recent uptime.
2166 o New directory authorities:
2167 - Set up Tonga as the default bridge directory authority.
2170 - Directory authorities now track servers by weighted
2171 mean-times-between-failures. When we have 4 or more days of data,
2172 use measured MTBF rather than declared uptime to decide whether
2173 to call a router Stable. Implements proposal 108.
2175 o Major bugfixes (load balancing):
2176 - When choosing nodes for non-guard positions, weight guards
2177 proportionally less, since they already have enough load. Patch
2179 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
2180 will allow fast Tor servers to get more attention.
2181 - When we're upgrading from an old Tor version, forget our current
2182 guards and pick new ones according to the new weightings. These
2183 three load balancing patches could raise effective network capacity
2184 by a factor of four. Thanks to Mike Perry for measurements.
2186 o Major bugfixes (descriptor parsing):
2187 - Handle unexpected whitespace better in malformed descriptors. Bug
2188 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
2191 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
2192 GETINFO for Torstat to use until it can switch to using extrainfos.
2193 - Optionally (if built with -DEXPORTMALLINFO) export the output
2194 of mallinfo via http, as tor/mallinfo.txt. Only accessible
2198 - Do not intermix bridge routers with controller-added
2199 routers. (Bugfix on 0.2.0.x)
2200 - Do not fail with an assert when accept() returns an unexpected
2201 address family. Addresses but does not wholly fix bug 483. (Bugfix
2203 - Let directory authorities startup even when they can't generate
2204 a descriptor immediately, e.g. because they don't know their
2206 - Stop putting the authentication cookie in a file called "0"
2207 in your working directory if you don't specify anything for the
2208 new CookieAuthFile option. Reported by Matt Edman.
2209 - Make it possible to read the PROTOCOLINFO response in a way that
2210 conforms to our control-spec. Reported by Matt Edman.
2211 - Fix a minor memory leak when we fail to find enough suitable
2212 servers to choose a circuit. Bugfix on 0.1.2.x.
2213 - Stop leaking part of the descriptor when we run into a particularly
2214 unparseable piece of it. Bugfix on 0.1.2.x.
2215 - Unmap the extrainfo cache file on exit.
2218 Changes in version 0.2.0.5-alpha - 2007-08-19
2219 This fifth development snapshot fixes compilation on Windows again;
2220 fixes an obnoxious client-side bug that slowed things down and put
2221 extra load on the network; gets us closer to using the v3 directory
2222 voting scheme; makes it easier for Tor controllers to use cookie-based
2223 authentication; and fixes a variety of other bugs.
2226 - Version 1 directories are no longer generated in full. Instead,
2227 authorities generate and serve "stub" v1 directories that list
2228 no servers. This will stop Tor versions 0.1.0.x and earlier from
2229 working, but (for security reasons) nobody should be running those
2232 o Major bugfixes (compilation, 0.2.0.x):
2233 - Try to fix Win32 compilation again: improve checking for IPv6 types.
2234 - Try to fix MSVC compilation: build correctly on platforms that do
2235 not define s6_addr16 or s6_addr32.
2236 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
2239 o Major bugfixes (stream expiration):
2240 - Expire not-yet-successful application streams in all cases if
2241 they've been around longer than SocksTimeout. Right now there are
2242 some cases where the stream will live forever, demanding a new
2243 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
2246 o Minor features (directory servers):
2247 - When somebody requests a list of statuses or servers, and we have
2248 none of those, return a 404 rather than an empty 200.
2250 o Minor features (directory voting):
2251 - Store v3 consensus status consensuses on disk, and reload them
2254 o Minor features (security):
2255 - Warn about unsafe ControlPort configurations.
2256 - Refuse to start with certain directory authority keys, and
2257 encourage people using them to stop.
2259 o Minor features (controller):
2260 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
2261 is valid before any authentication has been received. It tells
2262 a controller what kind of authentication is expected, and what
2263 protocol is spoken. Implements proposal 119.
2264 - New config option CookieAuthFile to choose a new location for the
2265 cookie authentication file, and config option
2266 CookieAuthFileGroupReadable to make it group-readable.
2268 o Minor features (unit testing):
2269 - Add command-line arguments to unit-test executable so that we can
2270 invoke any chosen test from the command line rather than having
2271 to run the whole test suite at once; and so that we can turn on
2272 logging for the unit tests.
2274 o Minor bugfixes (on 0.1.2.x):
2275 - If we require CookieAuthentication but we fail to write the
2276 cookie file, we would warn but not exit, and end up in a state
2277 where no controller could authenticate. Now we exit.
2278 - If we require CookieAuthentication, stop generating a new cookie
2279 every time we change any piece of our config.
2280 - When loading bandwidth history, do not believe any information in
2281 the future. Fixes bug 434.
2282 - When loading entry guard information, do not believe any information
2284 - When we have our clock set far in the future and generate an
2285 onion key, then re-set our clock to be correct, we should not stop
2286 the onion key from getting rotated.
2287 - Clean up torrc sample config file.
2288 - Do not automatically run configure from autogen.sh. This
2289 non-standard behavior tended to annoy people who have built other
2292 o Minor bugfixes (on 0.2.0.x):
2293 - Fix a bug with AutomapHostsOnResolve that would always cause
2294 the second request to fail. Bug reported by Kate. Bugfix on
2296 - Fix a bug in ADDRMAP controller replies that would sometimes
2297 try to print a NULL. Patch from tup.
2298 - Read v3 directory authority keys from the right location.
2299 - Numerous bugfixes to directory voting code.
2302 Changes in version 0.1.2.16 - 2007-08-01
2303 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
2304 remote attacker in certain situations to rewrite the user's torrc
2305 configuration file. This can completely compromise anonymity of users
2306 in most configurations, including those running the Vidalia bundles,
2307 TorK, etc. Or worse.
2309 o Major security fixes:
2310 - Close immediately after missing authentication on control port;
2311 do not allow multiple authentication attempts.
2314 Changes in version 0.2.0.4-alpha - 2007-08-01
2315 This fourth development snapshot fixes a critical security vulnerability
2316 for most users, specifically those running Vidalia, TorK, etc. Everybody
2317 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
2319 o Major security fixes:
2320 - Close immediately after missing authentication on control port;
2321 do not allow multiple authentication attempts.
2323 o Major bugfixes (compilation):
2324 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
2327 o Minor features (performance):
2328 - Be even more aggressive about releasing RAM from small
2329 empty buffers. Thanks to our free-list code, this shouldn't be too
2330 performance-intensive.
2331 - Disable sentinel-based debugging for buffer code: we squashed all
2332 the bugs that this was supposed to detect a long time ago, and
2333 now its only effect is to change our buffer sizes from nice
2334 powers of two (which platform mallocs tend to like) to values
2335 slightly over powers of two (which make some platform mallocs sad).
2336 - Log malloc statistics from mallinfo() on platforms where it
2340 Changes in version 0.2.0.3-alpha - 2007-07-29
2341 This third development snapshot introduces new experimental
2342 blocking-resistance features and a preliminary version of the v3
2343 directory voting design, and includes many other smaller features
2347 - The first pieces of our "bridge" design for blocking-resistance
2348 are implemented. People can run bridge directory authorities;
2349 people can run bridges; and people can configure their Tor clients
2350 with a set of bridges to use as the first hop into the Tor network.
2351 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
2353 - Create listener connections before we setuid to the configured
2354 User and Group. Now non-Windows users can choose port values
2355 under 1024, start Tor as root, and have Tor bind those ports
2356 before it changes to another UID. (Windows users could already
2358 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
2359 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
2360 on "vserver" accounts. (Patch from coderman.)
2361 - Be even more aggressive about separating local traffic from relayed
2362 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
2364 o Major features (experimental):
2365 - First cut of code for "v3 dir voting": directory authorities will
2366 vote on a common network status document rather than each publishing
2367 their own opinion. This code needs more testing and more corner-case
2368 handling before it's ready for use.
2371 - Directory authorities now call routers Fast if their bandwidth is
2372 at least 100KB/s, and consider their bandwidth adequate to be a
2373 Guard if it is at least 250KB/s, no matter the medians. This fix
2374 complements proposal 107. [Bugfix on 0.1.2.x]
2375 - Directory authorities now never mark more than 3 servers per IP as
2376 Valid and Running. (Implements proposal 109, by Kevin Bauer and
2378 - Minor change to organizationName and commonName generation
2379 procedures in TLS certificates during Tor handshakes, to invalidate
2380 some earlier censorware approaches. This is not a long-term
2381 solution, but applying it will give us a bit of time to look into
2382 the epidemiology of countermeasures as they spread.
2384 o Major bugfixes (directory):
2385 - Rewrite directory tokenization code to never run off the end of
2386 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
2388 o Minor features (controller):
2389 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
2390 match requests to applications. (Patch from Robert Hogan.)
2391 - Report address and port correctly on connections to DNSPort. (Patch
2393 - Add a RESOLVE command to launch hostname lookups. (Original patch
2395 - Add GETINFO status/enough-dir-info to let controllers tell whether
2396 Tor has downloaded sufficient directory information. (Patch
2398 - You can now use the ControlSocket option to tell Tor to listen for
2399 controller connections on Unix domain sockets on systems that
2400 support them. (Patch from Peter Palfrader.)
2401 - STREAM NEW events are generated for DNSPort requests and for
2402 tunneled directory connections. (Patch from Robert Hogan.)
2403 - New "GETINFO address-mappings/*" command to get address mappings
2404 with expiry information. "addr-mappings/*" is now deprecated.
2407 o Minor features (misc):
2408 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
2410 - The tor-gencert tool for v3 directory authorities now creates all
2411 files as readable to the file creator only, and write-protects
2412 the authority identity key.
2413 - When dumping memory usage, list bytes used in buffer memory
2415 - When running with dmalloc, dump more stats on hup and on exit.
2416 - Directory authorities now fail quickly and (relatively) harmlessly
2417 if they generate a network status document that is somehow
2420 o Traffic load balancing improvements:
2421 - If exit bandwidth ever exceeds one third of total bandwidth, then
2422 use the correct formula to weight exit nodes when choosing paths.
2423 (Based on patch from Mike Perry.)
2424 - Choose perfectly fairly among routers when choosing by bandwidth and
2425 weighting by fraction of bandwidth provided by exits. Previously, we
2426 would choose with only approximate fairness, and correct ourselves
2427 if we ran off the end of the list. [Bugfix on 0.1.2.x]
2429 o Performance improvements:
2430 - Be more aggressive with freeing buffer RAM or putting it on the
2432 - Use Critical Sections rather than Mutexes for synchronizing threads
2433 on win32; Mutexes are heavier-weight, and designed for synchronizing
2436 o Deprecated and removed features:
2437 - RedirectExits is now deprecated.
2438 - Stop allowing address masks that do not correspond to bit prefixes.
2439 We have warned about these for a really long time; now it's time
2440 to reject them. (Patch from croup.)
2442 o Minor bugfixes (directory):
2443 - Fix another crash bug related to extra-info caching. (Bug found by
2444 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
2445 - Directories no longer return a "304 not modified" when they don't
2446 have the networkstatus the client asked for. Also fix a memory
2447 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
2448 - We had accidentally labelled 0.1.2.x directory servers as not
2449 suitable for begin_dir requests, and had labelled no directory
2450 servers as suitable for uploading extra-info documents. [Bugfix
2453 o Minor bugfixes (dns):
2454 - Fix a crash when DNSPort is set more than once. (Patch from Robert
2455 Hogan.) [Bugfix on 0.2.0.2-alpha]
2456 - Add DNSPort connections to the global connection list, so that we
2457 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
2459 - Fix a dangling reference that could lead to a crash when DNSPort is
2460 changed or closed (Patch from Robert Hogan.) [Bugfix on
2463 o Minor bugfixes (controller):
2464 - Provide DNS expiry times in GMT, not in local time. For backward
2465 compatibility, ADDRMAP events only provide GMT expiry in an extended
2466 field. "GETINFO address-mappings" always does the right thing.
2467 - Use CRLF line endings properly in NS events.
2468 - Terminate multi-line control events properly. (Original patch
2469 from tup.) [Bugfix on 0.1.2.x-alpha]
2470 - Do not include spaces in SOURCE_ADDR fields in STREAM
2471 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
2474 Changes in version 0.1.2.15 - 2007-07-17
2475 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
2476 problems, fixes compilation on BSD, and fixes a variety of other
2477 bugs. Everybody should upgrade.
2479 o Major bugfixes (compilation):
2480 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
2482 o Major bugfixes (crashes):
2483 - Try even harder not to dereference the first character after
2484 an mmap(). Reported by lodger.
2485 - Fix a crash bug in directory authorities when we re-number the
2486 routerlist while inserting a new router.
2487 - When the cached-routers file is an even multiple of the page size,
2488 don't run off the end and crash. (Fixes bug 455; based on idea
2490 - Fix eventdns.c behavior on Solaris: It is critical to include
2491 orconfig.h _before_ sys/types.h, so that we can get the expected
2492 definition of _FILE_OFFSET_BITS.
2494 o Major bugfixes (security):
2495 - Fix a possible buffer overrun when using BSD natd support. Bug
2497 - When sending destroy cells from a circuit's origin, don't include
2498 the reason for tearing down the circuit. The spec says we didn't,
2499 and now we actually don't. Reported by lodger.
2500 - Keep streamids from different exits on a circuit separate. This
2501 bug may have allowed other routers on a given circuit to inject
2502 cells into streams. Reported by lodger; fixes bug 446.
2503 - If there's a never-before-connected-to guard node in our list,
2504 never choose any guards past it. This way we don't expand our
2505 guard list unless we need to.
2507 o Minor bugfixes (guard nodes):
2508 - Weight guard selection by bandwidth, so that low-bandwidth nodes
2509 don't get overused as guards.
2511 o Minor bugfixes (directory):
2512 - Correctly count the number of authorities that recommend each
2513 version. Previously, we were under-counting by 1.
2514 - Fix a potential crash bug when we load many server descriptors at
2515 once and some of them make others of them obsolete. Fixes bug 458.
2517 o Minor bugfixes (hidden services):
2518 - Stop tearing down the whole circuit when the user asks for a
2519 connection to a port that the hidden service didn't configure.
2522 o Minor bugfixes (misc):
2523 - On Windows, we were preventing other processes from reading
2524 cached-routers while Tor was running. Reported by janbar.
2525 - Fix a possible (but very unlikely) bug in picking routers by
2526 bandwidth. Add a log message to confirm that it is in fact
2527 unlikely. Patch from lodger.
2528 - Backport a couple of memory leak fixes.
2529 - Backport miscellaneous cosmetic bugfixes.
2532 Changes in version 0.2.0.2-alpha - 2007-06-02
2533 o Major bugfixes on 0.2.0.1-alpha:
2534 - Fix an assertion failure related to servers without extra-info digests.
2535 Resolves bugs 441 and 442.
2537 o Minor features (directory):
2538 - Support "If-Modified-Since" when answering HTTP requests for
2539 directories, running-routers documents, and network-status documents.
2540 (There's no need to support it for router descriptors, since those
2541 are downloaded by descriptor digest.)
2543 o Minor build issues:
2544 - Clear up some MIPSPro compiler warnings.
2545 - When building from a tarball on a machine that happens to have SVK
2546 installed, report the micro-revision as whatever version existed
2547 in the tarball, not as "x".
2550 Changes in version 0.2.0.1-alpha - 2007-06-01
2551 This early development snapshot provides new features for people running
2552 Tor as both a client and a server (check out the new RelayBandwidth
2553 config options); lets Tor run as a DNS proxy; and generally moves us
2554 forward on a lot of fronts.
2556 o Major features, server usability:
2557 - New config options RelayBandwidthRate and RelayBandwidthBurst:
2558 a separate set of token buckets for relayed traffic. Right now
2559 relayed traffic is defined as answers to directory requests, and
2560 OR connections that don't have any local circuits on them.
2562 o Major features, client usability:
2563 - A client-side DNS proxy feature to replace the need for
2564 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
2565 for DNS requests on port 9999, use the Tor network to resolve them
2566 anonymously, and send the reply back like a regular DNS server.
2567 The code still only implements a subset of DNS.
2568 - Make PreferTunneledDirConns and TunnelDirConns work even when
2569 we have no cached directory info. This means Tor clients can now
2570 do all of their connections protected by TLS.
2572 o Major features, performance and efficiency:
2573 - Directory authorities accept and serve "extra info" documents for
2574 routers. These documents contain fields from router descriptors
2575 that aren't usually needed, and that use a lot of excess
2576 bandwidth. Once these fields are removed from router descriptors,
2577 the bandwidth savings should be about 60%. [Partially implements
2579 - Servers upload extra-info documents to any authority that accepts
2580 them. Authorities (and caches that have been configured to download
2581 extra-info documents) download them as needed. [Partially implements
2583 - Change the way that Tor buffers data that it is waiting to write.
2584 Instead of queueing data cells in an enormous ring buffer for each
2585 client->OR or OR->OR connection, we now queue cells on a separate
2586 queue for each circuit. This lets us use less slack memory, and
2587 will eventually let us be smarter about prioritizing different kinds
2589 - Use memory pools to allocate cells with better speed and memory
2590 efficiency, especially on platforms where malloc() is inefficient.
2591 - Stop reading on edge connections when their corresponding circuit
2592 buffers are full; start again as the circuits empty out.
2594 o Major features, other:
2595 - Add an HSAuthorityRecordStats option that hidden service authorities
2596 can use to track statistics of overall hidden service usage without
2597 logging information that would be very useful to an attacker.
2598 - Start work implementing multi-level keys for directory authorities:
2599 Add a standalone tool to generate key certificates. (Proposal 103.)
2602 - Directory authorities now call routers Stable if they have an
2603 uptime of at least 30 days, even if that's not the median uptime
2604 in the network. Implements proposal 107, suggested by Kevin Bauer
2607 o Minor fixes (resource management):
2608 - Count the number of open sockets separately from the number
2609 of active connection_t objects. This will let us avoid underusing
2610 our allocated connection limit.
2611 - We no longer use socket pairs to link an edge connection to an
2612 anonymous directory connection or a DirPort test connection.
2613 Instead, we track the link internally and transfer the data
2614 in-process. This saves two sockets per "linked" connection (at the
2615 client and at the server), and avoids the nasty Windows socketpair()
2617 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
2618 for every single inactive connection_t. Free items from the
2619 4k/16k-buffer free lists when they haven't been used for a while.
2621 o Minor features (build):
2622 - Make autoconf search for libevent, openssl, and zlib consistently.
2623 - Update deprecated macros in configure.in.
2624 - When warning about missing headers, tell the user to let us
2625 know if the compile succeeds anyway, so we can downgrade the
2627 - Include the current subversion revision as part of the version
2628 string: either fetch it directly if we're in an SVN checkout, do
2629 some magic to guess it if we're in an SVK checkout, or use
2630 the last-detected version if we're building from a .tar.gz.
2631 Use this version consistently in log messages.
2633 o Minor features (logging):
2634 - Always prepend "Bug: " to any log message about a bug.
2635 - Put a platform string (e.g. "Linux i686") in the startup log
2636 message, so when people paste just their logs, we know if it's
2637 OpenBSD or Windows or what.
2638 - When logging memory usage, break down memory used in buffers by
2641 o Minor features (directory system):
2642 - New config option V2AuthoritativeDirectory that all directory
2643 authorities should set. This will let future authorities choose
2644 not to serve V2 directory information.
2645 - Directory authorities allow multiple router descriptors and/or extra
2646 info documents to be uploaded in a single go. This will make
2647 implementing proposal 104 simpler.
2649 o Minor features (controller):
2650 - Add a new config option __DisablePredictedCircuits designed for
2651 use by the controller, when we don't want Tor to build any circuits
2653 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
2654 so we can exit from the middle of the circuit.
2655 - Implement "getinfo status/circuit-established".
2656 - Implement "getinfo status/version/..." so a controller can tell
2657 whether the current version is recommended, and whether any versions
2658 are good, and how many authorities agree. (Patch from shibz.)
2660 o Minor features (hidden services):
2661 - Allow multiple HiddenServicePort directives with the same virtual
2662 port; when they occur, the user is sent round-robin to one
2663 of the target ports chosen at random. Partially fixes bug 393 by
2664 adding limited ad-hoc round-robining.
2666 o Minor features (other):
2668 - Add a new AutomapHostsOnResolve option: when it is enabled, any
2669 resolve request for hosts matching a given pattern causes Tor to
2670 generate an internal virtual address mapping for that host. This
2671 allows DNSPort to work sensibly with hidden service users. By
2672 default, .exit and .onion addresses are remapped; the list of
2673 patterns can be reconfigured with AutomapHostsSuffixes.
2674 - Add an "-F" option to tor-resolve to force a resolve for a .onion
2675 address. Thanks to the AutomapHostsOnResolve option, this is no
2676 longer a completely silly thing to do.
2677 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
2678 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
2679 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
2680 minus 1 byte: the actual maximum declared bandwidth.
2683 - Removed support for the old binary "version 0" controller protocol.
2684 This has been deprecated since 0.1.1, and warnings have been issued
2685 since 0.1.2. When we encounter a v0 control message, we now send
2686 back an error and close the connection.
2687 - Remove the old "dns worker" server DNS code: it hasn't been default
2688 since 0.1.2.2-alpha, and all the servers seem to be using the new
2691 o Minor bugfixes (portability):
2692 - Even though Windows is equally happy with / and \ as path separators,
2693 try to use \ consistently on Windows and / consistently on Unix: it
2694 makes the log messages nicer.
2695 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
2696 - Read resolv.conf files correctly on platforms where read() returns
2697 partial results on small file reads.
2699 o Minor bugfixes (directory):
2700 - Correctly enforce that elements of directory objects do not appear
2701 more often than they are allowed to appear.
2702 - When we are reporting the DirServer line we just parsed, we were
2703 logging the second stanza of the key fingerprint, not the first.
2705 o Minor bugfixes (logging):
2706 - When we hit an EOF on a log (probably because we're shutting down),
2707 don't try to remove the log from the list: just mark it as
2708 unusable. (Bulletproofs against bug 222.)
2710 o Minor bugfixes (other):
2711 - In the exitlist script, only consider the most recently published
2712 server descriptor for each server. Also, when the user requests
2713 a list of servers that _reject_ connections to a given address,
2714 explicitly exclude the IPs that also have servers that accept
2715 connections to that address. (Resolves bug 405.)
2716 - Stop allowing hibernating servers to be "stable" or "fast".
2717 - On Windows, we were preventing other processes from reading
2718 cached-routers while Tor was running. (Reported by janbar)
2719 - Make the NodeFamilies config option work. (Reported by
2720 lodger -- it has never actually worked, even though we added it
2722 - Check return values from pthread_mutex functions.
2723 - Don't save non-general-purpose router descriptors to the disk cache,
2724 because we have no way of remembering what their purpose was when
2726 - Add even more asserts to hunt down bug 417.
2727 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
2728 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
2729 Add a log message to confirm that it is in fact unlikely.
2731 o Minor bugfixes (controller):
2732 - Make 'getinfo fingerprint' return a 551 error if we're not a
2733 server, so we match what the control spec claims we do. Reported
2735 - Fix a typo in an error message when extendcircuit fails that
2736 caused us to not follow the \r\n-based delimiter protocol. Reported
2739 o Code simplifications and refactoring:
2740 - Stop passing around circuit_t and crypt_path_t pointers that are
2741 implicit in other procedure arguments.
2742 - Drop the old code to choke directory connections when the
2743 corresponding OR connections got full: thanks to the cell queue
2744 feature, OR conns don't get full any more.
2745 - Make dns_resolve() handle attaching connections to circuits
2746 properly, so the caller doesn't have to.
2747 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
2748 - Keep the connection array as a dynamic smartlist_t, rather than as
2749 a fixed-sized array. This is important, as the number of connections
2750 is becoming increasingly decoupled from the number of sockets.
2753 Changes in version 0.1.2.14 - 2007-05-25
2754 Tor 0.1.2.14 changes the addresses of two directory authorities (this
2755 change especially affects those who serve or use hidden services),
2756 and fixes several other crash- and security-related bugs.
2758 o Directory authority changes:
2759 - Two directory authorities (moria1 and moria2) just moved to new
2760 IP addresses. This change will particularly affect those who serve
2761 or use hidden services.
2763 o Major bugfixes (crashes):
2764 - If a directory server runs out of space in the connection table
2765 as it's processing a begin_dir request, it will free the exit stream
2766 but leave it attached to the circuit, leading to unpredictable
2767 behavior. (Reported by seeess, fixes bug 425.)
2768 - Fix a bug in dirserv_remove_invalid() that would cause authorities
2769 to corrupt memory under some really unlikely scenarios.
2770 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
2771 - Avoid segfaults when reading from mmaped descriptor file. (Reported
2774 o Major bugfixes (security):
2775 - When choosing an entry guard for a circuit, avoid using guards
2776 that are in the same family as the chosen exit -- not just guards
2777 that are exactly the chosen exit. (Reported by lodger.)
2779 o Major bugfixes (resource management):
2780 - If a directory authority is down, skip it when deciding where to get
2781 networkstatus objects or descriptors. Otherwise we keep asking
2782 every 10 seconds forever. Fixes bug 384.
2783 - Count it as a failure if we fetch a valid network-status but we
2784 don't want to keep it. Otherwise we'll keep fetching it and keep
2785 not wanting to keep it. Fixes part of bug 422.
2786 - If all of our dirservers have given us bad or no networkstatuses
2787 lately, then stop hammering them once per minute even when we
2788 think they're failed. Fixes another part of bug 422.
2791 - Actually set the purpose correctly for descriptors inserted with
2793 - When we have k non-v2 authorities in our DirServer config,
2794 we ignored the last k authorities in the list when updating our
2796 - Correctly back-off from requesting router descriptors that we are
2797 having a hard time downloading.
2798 - Read resolv.conf files correctly on platforms where read() returns
2799 partial results on small file reads.
2800 - Don't rebuild the entire router store every time we get 32K of
2801 routers: rebuild it when the journal gets very large, or when
2802 the gaps in the store get very large.
2805 - When routers publish SVN revisions in their router descriptors,
2806 authorities now include those versions correctly in networkstatus
2808 - Warn when using a version of libevent before 1.3b to run a server on
2809 OSX or BSD: these versions interact badly with userspace threads.
2812 Changes in version 0.1.2.13 - 2007-04-24
2813 This release features some major anonymity fixes, such as safer path
2814 selection; better client performance; faster bootstrapping, better
2815 address detection, and better DNS support for servers; write limiting as
2816 well as read limiting to make servers easier to run; and a huge pile of
2817 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
2819 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
2820 of the Freenode IRC network, remembering his patience and vision for
2821 free speech on the Internet.
2824 - Fix a memory leak when we ask for "all" networkstatuses and we
2825 get one we don't recognize.
2826 - Add more asserts to hunt down bug 417.
2827 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
2830 Changes in version 0.1.2.12-rc - 2007-03-16
2832 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
2833 directory information requested inside Tor connections (i.e. via
2834 begin_dir cells). It only triggered when the same connection was
2835 serving other data at the same time. Reported by seeess.
2838 - When creating a circuit via the controller, send a 'launched'
2839 event when we're done, so we follow the spec better.
2842 Changes in version 0.1.2.11-rc - 2007-03-15
2843 o Minor bugfixes (controller), reported by daejees:
2844 - Correct the control spec to match how the code actually responds
2845 to 'getinfo addr-mappings/*'.
2846 - The control spec described a GUARDS event, but the code
2847 implemented a GUARD event. Standardize on GUARD, but let people
2851 Changes in version 0.1.2.10-rc - 2007-03-07
2852 o Major bugfixes (Windows):
2853 - Do not load the NT services library functions (which may not exist)
2854 just to detect if we're a service trying to shut down. Now we run
2855 on Win98 and friends again.
2857 o Minor bugfixes (other):
2858 - Clarify a couple of log messages.
2859 - Fix a misleading socks5 error number.
2862 Changes in version 0.1.2.9-rc - 2007-03-02
2863 o Major bugfixes (Windows):
2864 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
2865 of the usual GCC "%llu". This prevents a bug when saving 64-bit
2866 int configuration values: the high-order 32 bits would get
2867 truncated. In particular, we were being bitten by the default
2868 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
2869 and maybe also bug 397.)
2871 o Minor bugfixes (performance):
2872 - Use OpenSSL's AES implementation on platforms where it's faster.
2873 This could save us as much as 10% CPU usage.
2875 o Minor bugfixes (server):
2876 - Do not rotate onion key immediately after setting it for the first
2879 o Minor bugfixes (directory authorities):
2880 - Stop calling servers that have been hibernating for a long time
2881 "stable". Also, stop letting hibernating or obsolete servers affect
2882 uptime and bandwidth cutoffs.
2883 - Stop listing hibernating servers in the v1 directory.
2885 o Minor bugfixes (hidden services):
2886 - Upload hidden service descriptors slightly less often, to reduce
2887 load on authorities.
2889 o Minor bugfixes (other):
2890 - Fix an assert that could trigger if a controller quickly set then
2891 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
2892 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
2894 - Fix a potential race condition in the rpm installer. Found by
2896 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
2897 of 2 as indicating that the server is completely bad; it sometimes
2898 means that the server is just bad for the request in question. (may fix
2899 the last of bug 326.)
2900 - Disable encrypted directory connections when we don't have a server
2901 descriptor for the destination. We'll get this working again in
2905 Changes in version 0.1.2.8-beta - 2007-02-26
2906 o Major bugfixes (crashes):
2907 - Stop crashing when the controller asks us to resetconf more than
2908 one config option at once. (Vidalia 0.0.11 does this.)
2909 - Fix a crash that happened on Win98 when we're given command-line
2910 arguments: don't try to load NT service functions from advapi32.dll
2911 except when we need them. (Bug introduced in 0.1.2.7-alpha;
2913 - Fix a longstanding obscure crash bug that could occur when
2914 we run out of DNS worker processes. (Resolves bug 390.)
2916 o Major bugfixes (hidden services):
2917 - Correctly detect whether hidden service descriptor downloads are
2918 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
2920 o Major bugfixes (accounting):
2921 - When we start during an accounting interval before it's time to wake
2922 up, remember to wake up at the correct time. (May fix bug 342.)
2924 o Minor bugfixes (controller):
2925 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
2926 clear the corresponding on_circuit variable, and remember later
2927 that we don't need to send a redundant CLOSED event. (Resolves part
2929 - Report events where a resolve succeeded or where we got a socks
2930 protocol error correctly, rather than calling both of them
2932 - Change reported stream target addresses to IP consistently when
2933 we finally get the IP from an exit node.
2934 - Send log messages to the controller even if they happen to be very
2937 o Minor bugfixes (other):
2938 - Display correct results when reporting which versions are
2939 recommended, and how recommended they are. (Resolves bug 383.)
2940 - Improve our estimates for directory bandwidth to be less random:
2941 guess that an unrecognized directory will have the average bandwidth
2942 from all known directories, not that it will have the average
2943 bandwidth from those directories earlier than it on the list.
2944 - If we start a server with ClientOnly 1, then set ClientOnly to 0
2945 and hup, stop triggering an assert based on an empty onion_key.
2946 - On platforms with no working mmap() equivalent, don't warn the
2947 user when cached-routers doesn't exist.
2948 - Warn the user when mmap() [or its equivalent] fails for some reason
2949 other than file-not-found.
2950 - Don't warn the user when cached-routers.new doesn't exist: that's
2951 perfectly fine when starting up for the first time.
2952 - When EntryNodes are configured, rebuild the guard list to contain,
2953 in order: the EntryNodes that were guards before; the rest of the
2954 EntryNodes; the nodes that were guards before.
2955 - Mask out all signals in sub-threads; only the libevent signal
2956 handler should be processing them. This should prevent some crashes
2957 on some machines using pthreads. (Patch from coderman.)
2958 - Fix switched arguments on memset in the implementation of
2959 tor_munmap() for systems with no mmap() call.
2960 - When Tor receives a router descriptor that it asked for, but
2961 no longer wants (because it has received fresh networkstatuses
2962 in the meantime), do not warn the user. Cache the descriptor if
2963 we're a cache; drop it if we aren't.
2964 - Make earlier entry guards _really_ get retried when the network
2966 - On a malformed DNS reply, always give an error to the corresponding
2968 - Build with recent libevents on platforms that do not define the
2969 nonstandard types "u_int8_t" and friends.
2971 o Minor features (controller):
2972 - Warn the user when an application uses the obsolete binary v0
2973 control protocol. We're planning to remove support for it during
2974 the next development series, so it's good to give people some
2976 - Add STREAM_BW events to report per-entry-stream bandwidth
2977 use. (Patch from Robert Hogan.)
2978 - Rate-limit SIGNEWNYM signals in response to controllers that
2979 impolitely generate them for every single stream. (Patch from
2980 mwenge; closes bug 394.)
2981 - Make REMAP stream events have a SOURCE (cache or exit), and
2982 make them generated in every case where we get a successful
2983 connected or resolved cell.
2985 o Minor bugfixes (performance):
2986 - Call router_have_min_dir_info half as often. (This is showing up in
2987 some profiles, but not others.)
2988 - When using GCC, make log_debug never get called at all, and its
2989 arguments never get evaluated, when no debug logs are configured.
2990 (This is showing up in some profiles, but not others.)
2993 - Remove some never-implemented options. Mark PathlenCoinWeight as
2995 - Implement proposal 106: Stop requiring clients to have well-formed
2996 certificates; stop checking nicknames in certificates. (Clients
2997 have certificates so that they can look like Tor servers, but in
2998 the future we might want to allow them to look like regular TLS
2999 clients instead. Nicknames in certificates serve no purpose other
3000 than making our protocol easier to recognize on the wire.)
3001 - Revise messages on handshake failure again to be even more clear about
3002 which are incoming connections and which are outgoing.
3003 - Discard any v1 directory info that's over 1 month old (for
3004 directories) or over 1 week old (for running-routers lists).
3005 - Do not warn when individual nodes in the configuration's EntryNodes,
3006 ExitNodes, etc are down: warn only when all possible nodes
3007 are down. (Fixes bug 348.)
3008 - Always remove expired routers and networkstatus docs before checking
3009 whether we have enough information to build circuits. (Fixes
3011 - Put a lower-bound on MaxAdvertisedBandwidth.
3014 Changes in version 0.1.2.7-alpha - 2007-02-06
3015 o Major bugfixes (rate limiting):
3016 - Servers decline directory requests much more aggressively when
3017 they're low on bandwidth. Otherwise they end up queueing more and
3018 more directory responses, which can't be good for latency.
3019 - But never refuse directory requests from local addresses.
3020 - Fix a memory leak when sending a 503 response for a networkstatus
3022 - Be willing to read or write on local connections (e.g. controller
3023 connections) even when the global rate limiting buckets are empty.
3024 - If our system clock jumps back in time, don't publish a negative
3025 uptime in the descriptor. Also, don't let the global rate limiting
3026 buckets go absurdly negative.
3027 - Flush local controller connection buffers periodically as we're
3028 writing to them, so we avoid queueing 4+ megabytes of data before
3031 o Major bugfixes (NT services):
3032 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
3033 command-line flag so that admins can override the default by saying
3034 "tor --service install --user "SomeUser"". This will not affect
3035 existing installed services. Also, warn the user that the service
3036 will look for its configuration file in the service user's
3037 %appdata% directory. (We can't do the 'hardwire the user's appdata
3038 directory' trick any more, since we may not have read access to that
3041 o Major bugfixes (other):
3042 - Previously, we would cache up to 16 old networkstatus documents
3043 indefinitely, if they came from nontrusted authorities. Now we
3044 discard them if they are more than 10 days old.
3045 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
3047 - Detect and reject malformed DNS responses containing circular
3049 - If exits are rare enough that we're not marking exits as guards,
3050 ignore exit bandwidth when we're deciding the required bandwidth
3052 - When we're handling a directory connection tunneled over Tor,
3053 don't fill up internal memory buffers with all the data we want
3054 to tunnel; instead, only add it if the OR connection that will
3055 eventually receive it has some room for it. (This can lead to
3056 slowdowns in tunneled dir connections; a better solution will have
3059 o Minor bugfixes (dns):
3060 - Add some defensive programming to eventdns.c in an attempt to catch
3061 possible memory-stomping bugs.
3062 - Detect and reject DNS replies containing IPv4 or IPv6 records with
3063 an incorrect number of bytes. (Previously, we would ignore the
3065 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
3066 in the correct order, and doesn't crash.
3067 - Free memory held in recently-completed DNS lookup attempts on exit.
3068 This was not a memory leak, but may have been hiding memory leaks.
3069 - Handle TTL values correctly on reverse DNS lookups.
3070 - Treat failure to parse resolv.conf as an error.
3072 o Minor bugfixes (other):
3073 - Fix crash with "tor --list-fingerprint" (reported by seeess).
3074 - When computing clock skew from directory HTTP headers, consider what
3075 time it was when we finished asking for the directory, not what
3077 - Expire socks connections if they spend too long waiting for the
3078 handshake to finish. Previously we would let them sit around for
3079 days, if the connecting application didn't close them either.
3080 - And if the socks handshake hasn't started, don't send a
3081 "DNS resolve socks failed" handshake reply; just close it.
3082 - Stop using C functions that OpenBSD's linker doesn't like.
3083 - Don't launch requests for descriptors unless we have networkstatuses
3084 from at least half of the authorities. This delays the first
3085 download slightly under pathological circumstances, but can prevent
3086 us from downloading a bunch of descriptors we don't need.
3087 - Do not log IPs with TLS failures for incoming TLS
3088 connections. (Fixes bug 382.)
3089 - If the user asks to use invalid exit nodes, be willing to use
3091 - Stop using the reserved ac_cv namespace in our configure script.
3092 - Call stat() slightly less often; use fstat() when possible.
3093 - Refactor the way we handle pending circuits when an OR connection
3094 completes or fails, in an attempt to fix a rare crash bug.
3095 - Only rewrite a conn's address based on X-Forwarded-For: headers
3096 if it's a parseable public IP address; and stop adding extra quotes
3097 to the resulting address.
3100 - Weight directory requests by advertised bandwidth. Now we can
3101 let servers enable write limiting but still allow most clients to
3102 succeed at their directory requests. (We still ignore weights when
3103 choosing a directory authority; I hope this is a feature.)
3106 - Create a new file ReleaseNotes which was the old ChangeLog. The
3107 new ChangeLog file now includes the summaries for all development
3109 - Check for addresses with invalid characters at the exit as well
3110 as at the client, and warn less verbosely when they fail. You can
3111 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
3112 - Adapt a patch from goodell to let the contrib/exitlist script
3113 take arguments rather than require direct editing.
3114 - Inform the server operator when we decide not to advertise a
3115 DirPort due to AccountingMax enabled or a low BandwidthRate. It
3116 was confusing Zax, so now we're hopefully more helpful.
3117 - Bring us one step closer to being able to establish an encrypted
3118 directory tunnel without knowing a descriptor first. Still not
3119 ready yet. As part of the change, now assume we can use a
3120 create_fast cell if we don't know anything about a router.
3121 - Allow exit nodes to use nameservers running on ports other than 53.
3122 - Servers now cache reverse DNS replies.
3123 - Add an --ignore-missing-torrc command-line option so that we can
3124 get the "use sensible defaults if the configuration file doesn't
3125 exist" behavior even when specifying a torrc location on the command
3128 o Minor features (controller):
3129 - Track reasons for OR connection failure; make these reasons
3130 available via the controller interface. (Patch from Mike Perry.)
3131 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
3132 can learn when clients are sending malformed hostnames to Tor.
3133 - Clean up documentation for controller status events.
3134 - Add a REMAP status to stream events to note that a stream's
3135 address has changed because of a cached address or a MapAddress
3139 Changes in version 0.1.2.6-alpha - 2007-01-09
3141 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
3142 connection handles more than 4 gigs in either direction, we crash.
3143 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
3144 advertised exit node, somebody might try to exit from us when
3145 we're bootstrapping and before we've built our descriptor yet.
3146 Refuse the connection rather than crashing.
3149 - Warn if we (as a server) find that we've resolved an address that we
3150 weren't planning to resolve.
3151 - Warn that using select() on any libevent version before 1.1 will be
3152 unnecessarily slow (even for select()).
3153 - Flush ERR-level controller status events just like we currently
3154 flush ERR-level log events, so that a Tor shutdown doesn't prevent
3155 the controller from learning about current events.
3157 o Minor features (more controller status events):
3158 - Implement EXTERNAL_ADDRESS server status event so controllers can
3159 learn when our address changes.
3160 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
3161 can learn when directories reject our descriptor.
3162 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
3163 can learn when a client application is speaking a non-socks protocol
3165 - Implement DANGEROUS_SOCKS client status event so controllers
3166 can learn when a client application is leaking DNS addresses.
3167 - Implement BUG general status event so controllers can learn when
3168 Tor is unhappy about its internal invariants.
3169 - Implement CLOCK_SKEW general status event so controllers can learn
3170 when Tor thinks the system clock is set incorrectly.
3171 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
3172 server status events so controllers can learn when their descriptors
3173 are accepted by a directory.
3174 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
3175 server status events so controllers can learn about Tor's progress in
3176 deciding whether it's reachable from the outside.
3177 - Implement BAD_LIBEVENT general status event so controllers can learn
3178 when we have a version/method combination in libevent that needs to
3180 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
3181 and DNS_USELESS server status events so controllers can learn
3182 about changes to DNS server status.
3184 o Minor features (directory):
3185 - Authorities no longer recommend exits as guards if this would shift
3186 too much load to the exit nodes.
3189 Changes in version 0.1.2.5-alpha - 2007-01-06
3191 - Enable write limiting as well as read limiting. Now we sacrifice
3192 capacity if we're pushing out lots of directory traffic, rather
3193 than overrunning the user's intended bandwidth limits.
3194 - Include TLS overhead when counting bandwidth usage; previously, we
3195 would count only the bytes sent over TLS, but not the bytes used
3197 - Support running the Tor service with a torrc not in the same
3198 directory as tor.exe and default to using the torrc located in
3199 the %appdata%\Tor\ of the user who installed the service. Patch
3201 - Servers now check for the case when common DNS requests are going to
3202 wildcarded addresses (i.e. all getting the same answer), and change
3203 their exit policy to reject *:* if it's happening.
3204 - Implement BEGIN_DIR cells, so we can connect to the directory
3205 server via TLS to do encrypted directory requests rather than
3206 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
3207 config options if you like.
3209 o Minor features (config and docs):
3210 - Start using the state file to store bandwidth accounting data:
3211 the bw_accounting file is now obsolete. We'll keep generating it
3212 for a while for people who are still using 0.1.2.4-alpha.
3213 - Try to batch changes to the state file so that we do as few
3214 disk writes as possible while still storing important things in
3216 - The state file and the bw_accounting file get saved less often when
3217 the AvoidDiskWrites config option is set.
3218 - Make PIDFile work on Windows (untested).
3219 - Add internal descriptions for a bunch of configuration options:
3220 accessible via controller interface and in comments in saved
3222 - Reject *:563 (NNTPS) in the default exit policy. We already reject
3223 NNTP by default, so this seems like a sensible addition.
3224 - Clients now reject hostnames with invalid characters. This should
3225 avoid some inadvertent info leaks. Add an option
3226 AllowNonRFC953Hostnames to disable this behavior, in case somebody
3227 is running a private network with hosts called @, !, and #.
3228 - Add a maintainer script to tell us which options are missing
3229 documentation: "make check-docs".
3230 - Add a new address-spec.txt document to describe our special-case
3231 addresses: .exit, .onion, and .noconnnect.
3233 o Minor features (DNS):
3234 - Ongoing work on eventdns infrastructure: now it has dns server
3235 and ipv6 support. One day Tor will make use of it.
3236 - Add client-side caching for reverse DNS lookups.
3237 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
3238 - When we change nameservers or IP addresses, reset and re-launch
3239 our tests for DNS hijacking.
3241 o Minor features (directory):
3242 - Authorities now specify server versions in networkstatus. This adds
3243 about 2% to the size of compressed networkstatus docs, and allows
3244 clients to tell which servers support BEGIN_DIR and which don't.
3245 The implementation is forward-compatible with a proposed future
3246 protocol version scheme not tied to Tor versions.
3247 - DirServer configuration lines now have an orport= option so
3248 clients can open encrypted tunnels to the authorities without
3249 having downloaded their descriptors yet. Enabled for moria1,
3250 moria2, tor26, and lefkada now in the default configuration.
3251 - Directory servers are more willing to send a 503 "busy" if they
3252 are near their write limit, especially for v1 directory requests.
3253 Now they can use their limited bandwidth for actual Tor traffic.
3254 - Clients track responses with status 503 from dirservers. After a
3255 dirserver has given us a 503, we try not to use it until an hour has
3256 gone by, or until we have no dirservers that haven't given us a 503.
3257 - When we get a 503 from a directory, and we're not a server, we don't
3258 count the failure against the total number of failures allowed
3259 for the thing we're trying to download.
3260 - Report X-Your-Address-Is correctly from tunneled directory
3261 connections; don't report X-Your-Address-Is when it's an internal
3262 address; and never believe reported remote addresses when they're
3264 - Protect against an unlikely DoS attack on directory servers.
3265 - Add a BadDirectory flag to network status docs so that authorities
3266 can (eventually) tell clients about caches they believe to be
3269 o Minor features (controller):
3270 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
3271 - Reimplement GETINFO so that info/names stays in sync with the
3273 - Implement "GETINFO fingerprint".
3274 - Implement "SETEVENTS GUARD" so controllers can get updates on
3275 entry guard status as it changes.
3277 o Minor features (clean up obsolete pieces):
3278 - Remove some options that have been deprecated since at least
3279 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
3280 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
3282 - We no longer look for identity and onion keys in "identity.key" and
3283 "onion.key" -- these were replaced by secret_id_key and
3284 secret_onion_key in 0.0.8pre1.
3285 - We no longer require unrecognized directory entries to be
3288 o Major bugfixes (security):
3289 - Stop sending the HttpProxyAuthenticator string to directory
3290 servers when directory connections are tunnelled through Tor.
3291 - Clients no longer store bandwidth history in the state file.
3292 - Do not log introduction points for hidden services if SafeLogging
3294 - When generating bandwidth history, round down to the nearest
3295 1k. When storing accounting data, round up to the nearest 1k.
3296 - When we're running as a server, remember when we last rotated onion
3297 keys, so that we will rotate keys once they're a week old even if
3298 we never stay up for a week ourselves.
3300 o Major bugfixes (other):
3301 - Fix a longstanding bug in eventdns that prevented the count of
3302 timed-out resolves from ever being reset. This bug caused us to
3303 give up on a nameserver the third time it timed out, and try it
3304 10 seconds later... and to give up on it every time it timed out
3306 - Take out the '5 second' timeout from the connection retry
3307 schedule. Now the first connect attempt will wait a full 10
3308 seconds before switching to a new circuit. Perhaps this will help
3309 a lot. Based on observations from Mike Perry.
3310 - Fix a bug on the Windows implementation of tor_mmap_file() that
3311 would prevent the cached-routers file from ever loading. Reported
3315 - Fix an assert failure when a directory authority sets
3316 AuthDirRejectUnlisted and then receives a descriptor from an
3317 unlisted router. Reported by seeess.
3318 - Avoid a double-free when parsing malformed DirServer lines.
3319 - Fix a bug when a BSD-style PF socket is first used. Patch from
3321 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
3322 to resolve an address at a given exit node even when they ask for
3324 - Servers no longer ever list themselves in their "family" line,
3325 even if configured to do so. This makes it easier to configure
3326 family lists conveniently.
3327 - When running as a server, don't fall back to 127.0.0.1 when no
3328 nameservers are configured in /etc/resolv.conf; instead, make the
3329 user fix resolv.conf or specify nameservers explicitly. (Resolves
3331 - Stop accepting certain malformed ports in configured exit policies.
3332 - Don't re-write the fingerprint file every restart, unless it has
3334 - Stop warning when a single nameserver fails: only warn when _all_ of
3335 our nameservers have failed. Also, when we only have one nameserver,
3336 raise the threshold for deciding that the nameserver is dead.
3337 - Directory authorities now only decide that routers are reachable
3338 if their identity keys are as expected.
3339 - When the user uses bad syntax in the Log config line, stop
3340 suggesting other bad syntax as a replacement.
3341 - Correctly detect ipv6 DNS capability on OpenBSD.
3343 o Minor bugfixes (controller):
3344 - Report the circuit number correctly in STREAM CLOSED events. Bug
3345 reported by Mike Perry.
3346 - Do not report bizarre values for results of accounting GETINFOs
3347 when the last second's write or read exceeds the allotted bandwidth.
3348 - Report "unrecognized key" rather than an empty string when the
3349 controller tries to fetch a networkstatus that doesn't exist.
3352 Changes in version 0.1.1.26 - 2006-12-14
3353 o Security bugfixes:
3354 - Stop sending the HttpProxyAuthenticator string to directory
3355 servers when directory connections are tunnelled through Tor.
3356 - Clients no longer store bandwidth history in the state file.
3357 - Do not log introduction points for hidden services if SafeLogging
3361 - Fix an assert failure when a directory authority sets
3362 AuthDirRejectUnlisted and then receives a descriptor from an
3363 unlisted router (reported by seeess).
3366 Changes in version 0.1.2.4-alpha - 2006-12-03
3368 - Add support for using natd; this allows FreeBSDs earlier than
3369 5.1.2 to have ipfw send connections through Tor without using
3370 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
3373 - Make all connections to addresses of the form ".noconnect"
3374 immediately get closed. This lets application/controller combos
3375 successfully test whether they're talking to the same Tor by
3376 watching for STREAM events.
3377 - Make cross.sh cross-compilation script work even when autogen.sh
3378 hasn't been run. (Patch from Michael Mohr.)
3379 - Statistics dumped by -USR2 now include a breakdown of public key
3380 operations, for profiling.
3383 - Fix a major leak when directory authorities parse their
3384 approved-routers list, a minor memory leak when we fail to pick
3385 an exit node, and a few rare leaks on errors.
3386 - Handle TransPort connections even when the server sends data before
3387 the client sends data. Previously, the connection would just hang
3388 until the client sent data. (Patch from tup based on patch from
3390 - Avoid assert failure when our cached-routers file is empty on
3394 - Don't log spurious warnings when we see a circuit close reason we
3395 don't recognize; it's probably just from a newer version of Tor.
3396 - Have directory authorities allow larger amounts of drift in uptime
3397 without replacing the server descriptor: previously, a server that
3398 restarted every 30 minutes could have 48 "interesting" descriptors
3400 - Start linking to the Tor specification and Tor reference manual
3401 correctly in the Windows installer.
3402 - Add Vidalia to the OS X uninstaller script, so when we uninstall
3403 Tor/Privoxy we also uninstall Vidalia.
3404 - Resume building on Irix64, and fix a lot of warnings from its
3406 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
3407 when we're running as a client.
3410 Changes in version 0.1.1.25 - 2006-11-04
3412 - When a client asks us to resolve (rather than connect to)
3413 an address, and we have a cached answer, give them the cached
3414 answer. Previously, we would give them no answer at all.
3415 - We were building exactly the wrong circuits when we predict
3416 hidden service requirements, meaning Tor would have to build all
3417 its circuits on demand.
3418 - If none of our live entry guards have a high uptime, but we
3419 require a guard with a high uptime, try adding a new guard before
3420 we give up on the requirement. This patch should make long-lived
3421 connections more stable on average.
3422 - When testing reachability of our DirPort, don't launch new
3423 tests when there's already one in progress -- unreachable
3424 servers were stacking up dozens of testing streams.
3426 o Security bugfixes:
3427 - When the user sends a NEWNYM signal, clear the client-side DNS
3428 cache too. Otherwise we continue to act on previous information.
3431 - Avoid a memory corruption bug when creating a hash table for
3433 - Avoid possibility of controller-triggered crash when misusing
3434 certain commands from a v0 controller on platforms that do not
3435 handle printf("%s",NULL) gracefully.
3436 - Avoid infinite loop on unexpected controller input.
3437 - Don't log spurious warnings when we see a circuit close reason we
3438 don't recognize; it's probably just from a newer version of Tor.
3439 - Add Vidalia to the OS X uninstaller script, so when we uninstall
3440 Tor/Privoxy we also uninstall Vidalia.
3443 Changes in version 0.1.2.3-alpha - 2006-10-29
3445 - Prepare for servers to publish descriptors less often: never
3446 discard a descriptor simply for being too old until either it is
3447 recommended by no authorities, or until we get a better one for
3448 the same router. Make caches consider retaining old recommended
3449 routers for even longer.
3450 - If most authorities set a BadExit flag for a server, clients
3451 don't think of it as a general-purpose exit. Clients only consider
3452 authorities that advertise themselves as listing bad exits.
3453 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
3454 headers for content, so that we can work better in the presence of
3455 caching HTTP proxies.
3456 - Allow authorities to list nodes as bad exits by fingerprint or by
3459 o Minor features, controller:
3460 - Add a REASON field to CIRC events; for backward compatibility, this
3461 field is sent only to controllers that have enabled the extended
3462 event format. Also, add additional reason codes to explain why
3463 a given circuit has been destroyed or truncated. (Patches from
3465 - Add a REMOTE_REASON field to extended CIRC events to tell the
3466 controller about why a remote OR told us to close a circuit.
3467 - Stream events also now have REASON and REMOTE_REASON fields,
3468 working much like those for circuit events.
3469 - There's now a GETINFO ns/... field so that controllers can ask Tor
3470 about the current status of a router.
3471 - A new event type "NS" to inform a controller when our opinion of
3472 a router's status has changed.
3473 - Add a GETINFO events/names and GETINFO features/names so controllers
3474 can tell which events and features are supported.
3475 - A new CLEARDNSCACHE signal to allow controllers to clear the
3476 client-side DNS cache without expiring circuits.
3478 o Security bugfixes:
3479 - When the user sends a NEWNYM signal, clear the client-side DNS
3480 cache too. Otherwise we continue to act on previous information.
3483 - Avoid sending junk to controllers or segfaulting when a controller
3484 uses EVENT_NEW_DESC with verbose nicknames.
3485 - Stop triggering asserts if the controller tries to extend hidden
3486 service circuits (reported by mwenge).
3487 - Avoid infinite loop on unexpected controller input.
3488 - When the controller does a "GETINFO network-status", tell it
3489 about even those routers whose descriptors are very old, and use
3490 long nicknames where appropriate.
3491 - Change NT service functions to be loaded on demand. This lets us
3492 build with MinGW without breaking Tor for Windows 98 users.
3493 - Do DirPort reachability tests less often, since a single test
3494 chews through many circuits before giving up.
3495 - In the hidden service example in torrc.sample, stop recommending
3496 esoteric and discouraged hidden service options.
3497 - When stopping an NT service, wait up to 10 sec for it to actually
3498 stop. (Patch from Matt Edman; resolves bug 295.)
3499 - Fix handling of verbose nicknames with ORCONN controller events:
3500 make them show up exactly when requested, rather than exactly when
3502 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
3503 printing a duplicate "$" in the keys we send (reported by mwenge).
3504 - Correctly set maximum connection limit on Cygwin. (This time
3506 - Try to detect Windows correctly when cross-compiling.
3507 - Detect the size of the routers file correctly even if it is
3508 corrupted (on systems without mmap) or not page-aligned (on systems
3509 with mmap). This bug was harmless.
3510 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
3511 to open a stream fails; now we do in more cases. This should
3512 make clients able to find a good exit faster in some cases, since
3513 unhandleable requests will now get an error rather than timing out.
3514 - Resolve two memory leaks when rebuilding the on-disk router cache
3515 (reported by fookoowa).
3516 - Clean up minor code warnings suggested by the MIPSpro C compiler,
3517 and reported by some Centos users.
3518 - Controller signals now work on non-Unix platforms that don't define
3519 SIGUSR1 and SIGUSR2 the way we expect.
3520 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
3521 values before failing, and always enables eventdns.
3522 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
3523 Try to fix this in configure.in by checking for most functions
3524 before we check for libevent.
3527 Changes in version 0.1.2.2-alpha - 2006-10-07
3529 - Make our async eventdns library on-by-default for Tor servers,
3530 and plan to deprecate the separate dnsworker threads.
3531 - Add server-side support for "reverse" DNS lookups (using PTR
3532 records so clients can determine the canonical hostname for a given
3533 IPv4 address). Only supported by servers using eventdns; servers
3534 now announce in their descriptors whether they support eventdns.
3535 - Specify and implement client-side SOCKS5 interface for reverse DNS
3536 lookups (see doc/socks-extensions.txt).
3537 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
3538 connect to directory servers through Tor. Previously, clients needed
3539 to find Tor exits to make private connections to directory servers.
3540 - Avoid choosing Exit nodes for entry or middle hops when the
3541 total bandwidth available from non-Exit nodes is much higher than
3542 the total bandwidth available from Exit nodes.
3543 - Workaround for name servers (like Earthlink's) that hijack failing
3544 DNS requests and replace the no-such-server answer with a "helpful"
3545 redirect to an advertising-driven search portal. Also work around
3546 DNS hijackers who "helpfully" decline to hijack known-invalid
3547 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
3548 lets you turn it off.
3549 - Send out a burst of long-range padding cells once we've established
3550 that we're reachable. Spread them over 4 circuits, so hopefully
3551 a few will be fast. This exercises our bandwidth and bootstraps
3552 us into the directory more quickly.
3554 o New/improved config options:
3555 - Add new config option "ResolvConf" to let the server operator
3556 choose an alternate resolve.conf file when using eventdns.
3557 - Add an "EnforceDistinctSubnets" option to control our "exclude
3558 servers on the same /16" behavior. It's still on by default; this
3559 is mostly for people who want to operate private test networks with
3560 all the machines on the same subnet.
3561 - If one of our entry guards is on the ExcludeNodes list, or the
3562 directory authorities don't think it's a good guard, treat it as
3563 if it were unlisted: stop using it as a guard, and throw it off
3564 the guards list if it stays that way for a long time.
3565 - Allow directory authorities to be marked separately as authorities
3566 for the v1 directory protocol, the v2 directory protocol, and
3567 as hidden service directories, to make it easier to retire old
3568 authorities. V1 authorities should set "HSAuthoritativeDir 1"
3569 to continue being hidden service authorities too.
3570 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
3572 o Minor features, controller:
3573 - Fix CIRC controller events so that controllers can learn the
3574 identity digests of non-Named servers used in circuit paths.
3575 - Let controllers ask for more useful identifiers for servers. Instead
3576 of learning identity digests for un-Named servers and nicknames
3577 for Named servers, the new identifiers include digest, nickname,
3578 and indication of Named status. Off by default; see control-spec.txt
3579 for more information.
3580 - Add a "getinfo address" controller command so it can display Tor's
3581 best guess to the user.
3582 - New controller event to alert the controller when our server
3583 descriptor has changed.
3584 - Give more meaningful errors on controller authentication failure.
3586 o Minor features, other:
3587 - When asked to resolve a hostname, don't use non-exit servers unless
3588 requested to do so. This allows servers with broken DNS to be
3589 useful to the network.
3590 - Divide eventdns log messages into warn and info messages.
3591 - Reserve the nickname "Unnamed" for routers that can't pick
3592 a hostname: any router can call itself Unnamed; directory
3593 authorities will never allocate Unnamed to any particular router;
3594 clients won't believe that any router is the canonical Unnamed.
3595 - Only include function names in log messages for info/debug messages.
3596 For notice/warn/err, the content of the message should be clear on
3597 its own, and printing the function name only confuses users.
3598 - Avoid some false positives during reachability testing: don't try
3599 to test via a server that's on the same /24 as us.
3600 - If we fail to build a circuit to an intended enclave, and it's
3601 not mandatory that we use that enclave, stop wanting it.
3602 - When eventdns is enabled, allow multithreaded builds on NetBSD and
3603 OpenBSD. (We had previously disabled threads on these platforms
3604 because they didn't have working thread-safe resolver functions.)
3606 o Major bugfixes, anonymity/security:
3607 - If a client asked for a server by name, and there's a named server
3608 in our network-status but we don't have its descriptor yet, we
3609 could return an unnamed server instead.
3610 - Fix NetBSD bug that could allow someone to force uninitialized RAM
3611 to be sent to a server's DNS resolver. This only affects NetBSD
3612 and other platforms that do not bounds-check tolower().
3613 - Reject (most) attempts to use Tor circuits with length one. (If
3614 many people start using Tor as a one-hop proxy, exit nodes become
3615 a more attractive target for compromise.)
3616 - Just because your DirPort is open doesn't mean people should be
3617 able to remotely teach you about hidden service descriptors. Now
3618 only accept rendezvous posts if you've got HSAuthoritativeDir set.
3620 o Major bugfixes, other:
3621 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
3622 - When a client asks the server to resolve (not connect to)
3623 an address, and it has a cached answer, give them the cached answer.
3624 Previously, the server would give them no answer at all.
3625 - Allow really slow clients to not hang up five minutes into their
3626 directory downloads (suggested by Adam J. Richter).
3627 - We were building exactly the wrong circuits when we anticipated
3628 hidden service requirements, meaning Tor would have to build all
3629 its circuits on demand.
3630 - Avoid crashing when we mmap a router cache file of size 0.
3631 - When testing reachability of our DirPort, don't launch new
3632 tests when there's already one in progress -- unreachable
3633 servers were stacking up dozens of testing streams.
3635 o Minor bugfixes, correctness:
3636 - If we're a directory mirror and we ask for "all" network status
3637 documents, we would discard status documents from authorities
3639 - Avoid a memory corruption bug when creating a hash table for
3641 - Avoid controller-triggered crash when misusing certain commands
3642 from a v0 controller on platforms that do not handle
3643 printf("%s",NULL) gracefully.
3644 - Don't crash when a controller sends a third argument to an
3645 "extendcircuit" request.
3646 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
3647 response; fix error code when "getinfo dir/status/" fails.
3648 - Avoid crash when telling controller stream-status and a stream
3650 - Patch from Adam Langley to fix assert() in eventdns.c.
3651 - Fix a debug log message in eventdns to say "X resolved to Y"
3652 instead of "X resolved to X".
3653 - Make eventdns give strings for DNS errors, not just error numbers.
3654 - Track unreachable entry guards correctly: don't conflate
3655 'unreachable by us right now' with 'listed as down by the directory
3656 authorities'. With the old code, if a guard was unreachable by
3657 us but listed as running, it would clog our guard list forever.
3658 - Behave correctly in case we ever have a network with more than
3659 2GB/s total advertised capacity.
3660 - Make TrackExitHosts case-insensitive, and fix the behavior of
3661 ".suffix" TrackExitHosts items to avoid matching in the middle of
3663 - Finally fix the openssl warnings from newer gccs that believe that
3664 ignoring a return value is okay, but casting a return value and
3665 then ignoring it is a sign of madness.
3666 - Prevent the contrib/exitlist script from printing the same
3667 result more than once.
3668 - Patch from Steve Hildrey: Generate network status correctly on
3669 non-versioning dirservers.
3670 - Don't listen to the X-Your-Address-Is hint if you did the lookup
3671 via Tor; otherwise you'll think you're the exit node's IP address.
3673 o Minor bugfixes, performance:
3674 - Two small performance improvements on parsing descriptors.
3675 - Major performance improvement on inserting descriptors: change
3676 algorithm from O(n^2) to O(n).
3677 - Make the common memory allocation path faster on machines where
3678 malloc(0) returns a pointer.
3679 - Start remembering X-Your-Address-Is directory hints even if you're
3680 a client, so you can become a server more smoothly.
3681 - Avoid duplicate entries on MyFamily line in server descriptor.
3683 o Packaging, features:
3684 - Remove architecture from OS X builds. The official builds are
3685 now universal binaries.
3686 - The Debian package now uses --verify-config when (re)starting,
3687 to distinguish configuration errors from other errors.
3688 - Update RPMs to require libevent 1.1b.
3690 o Packaging, bugfixes:
3691 - Patches so Tor builds with MinGW on Windows.
3692 - Patches so Tor might run on Cygwin again.
3693 - Resume building on non-gcc compilers and ancient gcc. Resume
3694 building with the -O0 compile flag. Resume building cleanly on
3696 - Run correctly on OS X platforms with case-sensitive filesystems.
3697 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
3698 - Add autoconf checks so Tor can build on Solaris x86 again.
3701 - Documented (and renamed) ServerDNSSearchDomains and
3702 ServerDNSResolvConfFile options.
3703 - Be clearer that the *ListenAddress directives can be repeated
3707 Changes in version 0.1.1.24 - 2006-09-29
3709 - Allow really slow clients to not hang up five minutes into their
3710 directory downloads (suggested by Adam J. Richter).
3711 - Fix major performance regression from 0.1.0.x: instead of checking
3712 whether we have enough directory information every time we want to
3713 do something, only check when the directory information has changed.
3714 This should improve client CPU usage by 25-50%.
3715 - Don't crash if, after a server has been running for a while,
3716 it can't resolve its hostname.
3719 - Allow Tor to start when RunAsDaemon is set but no logs are set.
3720 - Don't crash when the controller receives a third argument to an
3721 "extendcircuit" request.
3722 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
3723 response; fix error code when "getinfo dir/status/" fails.
3724 - Fix configure.in to not produce broken configure files with
3725 more recent versions of autoconf. Thanks to Clint for his auto*
3727 - Fix security bug on NetBSD that could allow someone to force
3728 uninitialized RAM to be sent to a server's DNS resolver. This
3729 only affects NetBSD and other platforms that do not bounds-check
3731 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
3732 methods: these are known to be buggy.
3733 - If we're a directory mirror and we ask for "all" network status
3734 documents, we would discard status documents from authorities
3738 Changes in version 0.1.2.1-alpha - 2006-08-27
3740 - Add "eventdns" async dns library from Adam Langley, tweaked to
3741 build on OSX and Windows. Only enabled if you pass the
3742 --enable-eventdns argument to configure.
3743 - Allow servers with no hostname or IP address to learn their
3744 IP address by asking the directory authorities. This code only
3745 kicks in when you would normally have exited with a "no address"
3746 error. Nothing's authenticated, so use with care.
3747 - Rather than waiting a fixed amount of time between retrying
3748 application connections, we wait only 5 seconds for the first,
3749 10 seconds for the second, and 15 seconds for each retry after
3750 that. Hopefully this will improve the expected user experience.
3751 - Patch from Tup to add support for transparent AP connections:
3752 this basically bundles the functionality of trans-proxy-tor
3753 into the Tor mainline. Now hosts with compliant pf/netfilter
3754 implementations can redirect TCP connections straight to Tor
3755 without diverting through SOCKS. Needs docs.
3756 - Busy directory servers save lots of memory by spooling server
3757 descriptors, v1 directories, and v2 networkstatus docs to buffers
3758 as needed rather than en masse. Also mmap the cached-routers
3759 files, so we don't need to keep the whole thing in memory too.
3760 - Automatically avoid picking more than one node from the same
3761 /16 network when constructing a circuit.
3762 - Revise and clean up the torrc.sample that we ship with; add
3763 a section for BandwidthRate and BandwidthBurst.
3766 - Split circuit_t into origin_circuit_t and or_circuit_t, and
3767 split connection_t into edge, or, dir, control, and base structs.
3768 These will save quite a bit of memory on busy servers, and they'll
3769 also help us track down bugs in the code and bugs in the spec.
3770 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
3771 or later. Log when we are doing this, so we can diagnose it when
3772 it fails. (Also, recommend libevent 1.1b for kqueue and
3773 win32 methods; deprecate libevent 1.0b harder; make libevent
3774 recommendation system saner.)
3775 - Start being able to build universal binaries on OS X (thanks
3777 - Export the default exit policy via the control port, so controllers
3778 don't need to guess what it is / will be later.
3779 - Add a man page entry for ProtocolWarnings.
3780 - Add TestVia config option to the man page.
3781 - Remove even more protocol-related warnings from Tor server logs,
3782 such as bad TLS handshakes and malformed begin cells.
3783 - Stop fetching descriptors if you're not a dir mirror and you
3784 haven't tried to establish any circuits lately. [This currently
3785 causes some dangerous behavior, because when you start up again
3786 you'll use your ancient server descriptors.]
3787 - New DirPort behavior: if you have your dirport set, you download
3788 descriptors aggressively like a directory mirror, whether or not
3790 - Get rid of the router_retry_connections notion. Now routers
3791 no longer try to rebuild long-term connections to directory
3792 authorities, and directory authorities no longer try to rebuild
3793 long-term connections to all servers. We still don't hang up
3794 connections in these two cases though -- we need to look at it
3795 more carefully to avoid flapping, and we likely need to wait til
3796 0.1.1.x is obsolete.
3797 - Drop compatibility with obsolete Tors that permit create cells
3798 to have the wrong circ_id_type.
3799 - Re-enable per-connection rate limiting. Get rid of the "OP
3800 bandwidth" concept. Lay groundwork for "bandwidth classes" --
3801 separate global buckets that apply depending on what sort of conn
3803 - Start publishing one minute or so after we find our ORPort
3804 to be reachable. This will help reduce the number of descriptors
3805 we have for ourselves floating around, since it's quite likely
3806 other things (e.g. DirPort) will change during that minute too.
3807 - Fork the v1 directory protocol into its own spec document,
3808 and mark dir-spec.txt as the currently correct (v2) spec.
3811 - When we find our DirPort to be reachable, publish a new descriptor
3812 so we'll tell the world (reported by pnx).
3813 - Publish a new descriptor after we hup/reload. This is important
3814 if our config has changed such that we'll want to start advertising
3815 our DirPort now, etc.
3816 - Allow Tor to start when RunAsDaemon is set but no logs are set.
3817 - When we have a state file we cannot parse, tell the user and
3818 move it aside. Now we avoid situations where the user starts
3819 Tor in 1904, Tor writes a state file with that timestamp in it,
3820 the user fixes her clock, and Tor refuses to start.
3821 - Fix configure.in to not produce broken configure files with
3822 more recent versions of autoconf. Thanks to Clint for his auto*
3824 - "tor --verify-config" now exits with -1(255) or 0 depending on
3825 whether the config options are bad or good.
3826 - Resolve bug 321 when using dnsworkers: append a period to every
3827 address we resolve at the exit node, so that we do not accidentally
3828 pick up local addresses, and so that failing searches are retried
3829 in the resolver search domains. (This is already solved for
3830 eventdns.) (This breaks Blossom servers for now.)
3831 - If we are using an exit enclave and we can't connect, e.g. because
3832 its webserver is misconfigured to not listen on localhost, then
3833 back off and try connecting from somewhere else before we fail.
3836 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
3837 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
3838 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
3839 when the IP address is mapped through MapAddress to a hostname.
3840 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
3841 useless IPv6 DNS resolves.
3842 - Patch suggested by Karsten Loesing: respond to SIGNAL command
3843 before we execute the signal, in case the signal shuts us down.
3844 - Clean up AllowInvalidNodes man page entry.
3845 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
3846 - Add more asserts to track down an assert error on a windows Tor
3847 server with connection_add being called with socket == -1.
3848 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
3849 - Fix misleading log messages: an entry guard that is "unlisted",
3850 as well as not known to be "down" (because we've never heard
3851 of it), is not therefore "up".
3852 - Remove code to special-case "-cvs" ending, since it has not
3853 actually mattered since 0.0.9.
3854 - Make our socks5 handling more robust to broken socks clients:
3855 throw out everything waiting on the buffer in between socks
3856 handshake phases, since they can't possibly (so the theory
3857 goes) have predicted what we plan to respond to them.
3860 Changes in version 0.1.1.23 - 2006-07-30
3862 - Fast Tor servers, especially exit nodes, were triggering asserts
3863 due to a bug in handling the list of pending DNS resolves. Some
3864 bugs still remain here; we're hunting them.
3865 - Entry guards could crash clients by sending unexpected input.
3866 - More fixes on reachability testing: if you find yourself reachable,
3867 then don't ever make any client requests (so you stop predicting
3868 circuits), then hup or have your clock jump, then later your IP
3869 changes, you won't think circuits are working, so you won't try to
3870 test reachability, so you won't publish.
3873 - Avoid a crash if the controller does a resetconf firewallports
3874 and then a setconf fascistfirewall=1.
3875 - Avoid an integer underflow when the dir authority decides whether
3876 a router is stable: we might wrongly label it stable, and compute
3877 a slightly wrong median stability, when a descriptor is published
3879 - Fix a place where we might trigger an assert if we can't build our
3880 own server descriptor yet.
3883 Changes in version 0.1.1.22 - 2006-07-05
3885 - Fix a big bug that was causing servers to not find themselves
3886 reachable if they changed IP addresses. Since only 0.1.1.22+
3887 servers can do reachability testing correctly, now we automatically
3888 make sure to test via one of these.
3889 - Fix to allow clients and mirrors to learn directory info from
3890 descriptor downloads that get cut off partway through.
3891 - Directory authorities had a bug in deciding if a newly published
3892 descriptor was novel enough to make everybody want a copy -- a few
3893 servers seem to be publishing new descriptors many times a minute.
3895 - Fix a rare bug that was causing some servers to complain about
3896 "closing wedged cpuworkers" and skip some circuit create requests.
3897 - Make the Exit flag in directory status documents actually work.
3900 Changes in version 0.1.1.21 - 2006-06-10
3901 o Crash and assert fixes from 0.1.1.20:
3902 - Fix a rare crash on Tor servers that have enabled hibernation.
3903 - Fix a seg fault on startup for Tor networks that use only one
3904 directory authority.
3905 - Fix an assert from a race condition that occurs on Tor servers
3906 while exiting, where various threads are trying to log that they're
3907 exiting, and delete the logs, at the same time.
3908 - Make our unit tests pass again on certain obscure platforms.
3911 - Add support for building SUSE RPM packages.
3912 - Speed up initial bootstrapping for clients: if we are making our
3913 first ever connection to any entry guard, then don't mark it down
3915 - When only one Tor server in the network is labelled as a guard,
3916 and we've already picked him, we would cycle endlessly picking him
3917 again, being unhappy about it, etc. Now we specifically exclude
3918 current guards when picking a new guard.
3919 - Servers send create cells more reliably after the TLS connection
3920 is established: we were sometimes forgetting to send half of them
3921 when we had more than one pending.
3922 - If we get a create cell that asks us to extend somewhere, but the
3923 Tor server there doesn't match the expected digest, we now send
3924 a destroy cell back, rather than silently doing nothing.
3925 - Make options->RedirectExit work again.
3926 - Make cookie authentication for the controller work again.
3927 - Stop being picky about unusual characters in the arguments to
3928 mapaddress. It's none of our business.
3929 - Add a new config option "TestVia" that lets you specify preferred
3930 middle hops to use for test circuits. Perhaps this will let me
3931 debug the reachability problems better.
3933 o Log / documentation fixes:
3934 - If we're a server and some peer has a broken TLS certificate, don't
3935 log about it unless ProtocolWarnings is set, i.e., we want to hear
3936 about protocol violations by others.
3937 - Fix spelling of VirtualAddrNetwork in man page.
3938 - Add a better explanation at the top of the autogenerated torrc file
3939 about what happened to our old torrc.
3942 Changes in version 0.1.1.20 - 2006-05-23
3944 - Downgrade a log severity where servers complain that they're
3946 - Avoid a compile warning on FreeBSD.
3947 - Remove string size limit on NEWDESC messages; solve bug 291.
3948 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
3949 more thoroughly when we're running on windows.
3952 Changes in version 0.1.1.19-rc - 2006-05-03
3954 - Regenerate our local descriptor if it's dirty and we try to use
3955 it locally (e.g. if it changes during reachability detection).
3956 - If we setconf our ORPort to 0, we continued to listen on the
3957 old ORPort and receive connections.
3958 - Avoid a second warning about machine/limits.h on Debian
3960 - Be willing to add our own routerinfo into the routerlist.
3961 Now authorities will include themselves in their directories
3962 and network-statuses.
3963 - Stop trying to upload rendezvous descriptors to every
3964 directory authority: only try the v1 authorities.
3965 - Servers no longer complain when they think they're not
3966 registered with the directory authorities. There were too many
3968 - Backport dist-rpm changes so rpms can be built without errors.
3971 - Implement an option, VirtualAddrMask, to set which addresses
3972 get handed out in response to mapaddress requests. This works
3973 around a bug in tsocks where 127.0.0.0/8 is never socksified.
3976 Changes in version 0.1.1.18-rc - 2006-04-10
3978 - Work harder to download live network-statuses from all the
3979 directory authorities we know about. Improve the threshold
3980 decision logic so we're more robust to edge cases.
3981 - When fetching rendezvous descriptors, we were willing to ask
3982 v2 authorities too, which would always return 404.
3985 - Stop listing down or invalid nodes in the v1 directory. This will
3986 reduce its bulk by about 1/3, and reduce load on directory
3988 - When deciding whether a router is Fast or Guard-worthy, consider
3989 his advertised BandwidthRate and not just the BandwidthCapacity.
3990 - No longer ship INSTALL and README files -- they are useless now.
3991 - Force rpmbuild to behave and honor target_cpu.
3992 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
3993 - Start to include translated versions of the tor-doc-*.html
3994 files, along with the screenshots. Still needs more work.
3995 - Start sending back 512 and 451 errors if mapaddress fails,
3996 rather than not sending anything back at all.
3997 - When we fail to bind or listen on an incoming or outgoing
3998 socket, we should close it before failing. otherwise we just
3999 leak it. (thanks to weasel for finding.)
4000 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
4001 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
4002 - Make NoPublish (even though deprecated) work again.
4003 - Fix a minor security flaw where a versioning auth dirserver
4004 could list a recommended version many times in a row to make
4005 clients more convinced that it's recommended.
4006 - Fix crash bug if there are two unregistered servers running
4007 with the same nickname, one of them is down, and you ask for
4008 them by nickname in your EntryNodes or ExitNodes. Also, try
4009 to pick the one that's running rather than an arbitrary one.
4010 - Fix an infinite loop we could hit if we go offline for too long.
4011 - Complain when we hit WSAENOBUFS on recv() or write() too.
4012 Perhaps this will help us hunt the bug.
4013 - If you're not a versioning dirserver, don't put the string
4014 "client-versions \nserver-versions \n" in your network-status.
4015 - Lower the minimum required number of file descriptors to 1000,
4016 so we can have some overhead for Valgrind on Linux, where the
4017 default ulimit -n is 1024.
4020 - Add tor.dizum.com as the fifth authoritative directory server.
4021 - Add a new config option FetchUselessDescriptors, off by default,
4022 for when you plan to run "exitlist" on your client and you want
4023 to know about even the non-running descriptors.
4026 Changes in version 0.1.1.17-rc - 2006-03-28
4028 - Clients and servers since 0.1.1.10-alpha have been expiring
4029 connections whenever they are idle for 5 minutes and they *do*
4030 have circuits on them. Oops. With this new version, clients will
4031 discard their previous entry guard choices and avoid choosing
4032 entry guards running these flawed versions.
4033 - Fix memory leak when uncompressing concatenated zlib streams. This
4034 was causing substantial leaks over time on Tor servers.
4035 - The v1 directory was including servers as much as 48 hours old,
4036 because that's how the new routerlist->routers works. Now only
4037 include them if they're 20 hours old or less.
4040 - Resume building on irix64, netbsd 2.0, etc.
4041 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
4043 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
4044 and it is confusing some users.
4045 - Mirrors stop caching the v1 directory so often.
4046 - Make the max number of old descriptors that a cache will hold
4047 rise with the number of directory authorities, so we can scale.
4048 - Change our win32 uname() hack to be more forgiving about what
4049 win32 versions it thinks it's found.
4052 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
4054 - When the controller's *setconf commands fail, collect an error
4055 message in a string and hand it back to the controller.
4056 - Make the v2 dir's "Fast" flag based on relative capacity, just
4057 like "Stable" is based on median uptime. Name everything in the
4058 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
4059 - Log server fingerprint on startup, so new server operators don't
4060 have to go hunting around their filesystem for it.
4061 - Return a robots.txt on our dirport to discourage google indexing.
4062 - Let the controller ask for GETINFO dir/status/foo so it can ask
4063 directly rather than connecting to the dir port. Only works when
4064 dirport is set for now.
4066 o New config options rather than constants in the code:
4067 - SocksTimeout: How long do we let a socks connection wait
4068 unattached before we fail it?
4069 - CircuitBuildTimeout: Cull non-open circuits that were born
4070 at least this many seconds ago.
4071 - CircuitIdleTimeout: Cull open clean circuits that were born
4072 at least this many seconds ago.
4075 Changes in version 0.1.1.16-rc - 2006-03-18
4076 o Bugfixes on 0.1.1.15-rc:
4077 - Fix assert when the controller asks to attachstream a connect-wait
4078 or resolve-wait stream.
4079 - Now do address rewriting when the controller asks us to attach
4080 to a particular circuit too. This will let Blossom specify
4081 "moria2.exit" without having to learn what moria2's IP address is.
4082 - Make the "tor --verify-config" command-line work again, so people
4083 can automatically check if their torrc will parse.
4084 - Authoritative dirservers no longer require an open connection from
4085 a server to consider him "reachable". We need this change because
4086 when we add new auth dirservers, old servers won't know not to
4088 - Let Tor build on Sun CC again.
4089 - Fix an off-by-one buffer size in dirserv.c that magically never
4090 hit our three authorities but broke sjmurdoch's own tor network.
4091 - If we as a directory mirror don't know of any v1 directory
4092 authorities, then don't try to cache any v1 directories.
4093 - Stop warning about unknown servers in our family when they are
4094 given as hex digests.
4095 - Stop complaining as quickly to the server operator that he
4096 hasn't registered his nickname/key binding.
4097 - Various cleanups so we can add new V2 Auth Dirservers.
4098 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
4099 reflect the updated flags in our v2 dir protocol.
4100 - Resume allowing non-printable characters for exit streams (both
4101 for connecting and for resolving). Now we tolerate applications
4102 that don't follow the RFCs. But continue to block malformed names
4105 o Bugfixes on 0.1.0.x:
4106 - Fix assert bug in close_logs(): when we close and delete logs,
4107 remove them all from the global "logfiles" list.
4108 - Fix minor integer overflow in calculating when we expect to use up
4109 our bandwidth allocation before hibernating.
4110 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
4111 there are multiple SSLs installed with different versions.
4112 - When we try to be a server and Address is not explicitly set and
4113 our hostname resolves to a private IP address, try to use an
4114 interface address if it has a public address. Now Windows machines
4115 that think of themselves as localhost can work by default.
4118 - Let the controller ask for GETINFO dir/server/foo so it can ask
4119 directly rather than connecting to the dir port.
4120 - Let the controller tell us about certain router descriptors
4121 that it doesn't want Tor to use in circuits. Implement
4122 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
4123 - New config option SafeSocks to reject all application connections
4124 using unsafe socks protocols. Defaults to off.
4127 Changes in version 0.1.1.15-rc - 2006-03-11
4128 o Bugfixes and cleanups:
4129 - When we're printing strings from the network, don't try to print
4130 non-printable characters. This protects us against shell escape
4131 sequence exploits, and also against attacks to fool humans into
4132 misreading their logs.
4133 - Fix a bug where Tor would fail to establish any connections if you
4134 left it off for 24 hours and then started it: we were happy with
4135 the obsolete network statuses, but they all referred to router
4136 descriptors that were too old to fetch, so we ended up with no
4137 valid router descriptors.
4138 - Fix a seg fault in the controller's "getinfo orconn-status"
4139 command while listing status on incoming handshaking connections.
4140 Introduce a status name "NEW" for these connections.
4141 - If we get a linelist or linelist_s config option from the torrc
4142 (e.g. ExitPolicy) and it has no value, warn and skip rather than
4143 silently resetting it to its default.
4144 - Don't abandon entry guards until they've been down or gone for
4146 - Cleaner and quieter log messages.
4149 - New controller signal NEWNYM that makes new application requests
4151 - Add a new circuit purpose 'controller' to let the controller ask
4152 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
4153 controller command to let you specify the purpose if you're
4154 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
4155 command to let you change a circuit's purpose after it's been
4157 - Accept "private:*" in routerdesc exit policies; not generated yet
4158 because older Tors do not understand it.
4159 - Add BSD-style contributed startup script "rc.subr" from Peter
4163 Changes in version 0.1.1.14-alpha - 2006-02-20
4164 o Bugfixes on 0.1.1.x:
4165 - Don't die if we ask for a stdout or stderr log (even implicitly)
4166 and we're set to RunAsDaemon -- just warn.
4167 - We still had a few bugs in the OR connection rotation code that
4168 caused directory servers to slowly aggregate connections to other
4169 fast Tor servers. This time for sure!
4170 - Make log entries on Win32 include the name of the function again.
4171 - We were treating a pair of exit policies if they were equal even
4172 if one said accept and the other said reject -- causing us to
4173 not always publish a new descriptor since we thought nothing
4175 - Retry pending server downloads as well as pending networkstatus
4176 downloads when we unexpectedly get a socks request.
4177 - We were ignoring the IS_FAST flag in the directory status,
4178 meaning we were willing to pick trivial-bandwidth nodes for "fast"
4180 - If the controller's SAVECONF command fails (e.g. due to file
4181 permissions), let the controller know that it failed.
4184 - If we're trying to be a Tor server and running Windows 95/98/ME
4185 as a server, explain that we'll likely crash.
4186 - When we're a server, a client asks for an old-style directory,
4187 and our write bucket is empty, don't give it to him. This way
4188 small servers can continue to serve the directory *sometimes*,
4189 without getting overloaded.
4190 - Compress exit policies even more -- look for duplicate lines
4192 - Clients now honor the "guard" flag in the router status when
4193 picking entry guards, rather than looking at is_fast or is_stable.
4194 - Retain unrecognized lines in $DATADIR/state file, so that we can
4195 be forward-compatible.
4196 - Generate 18.0.0.0/8 address policy format in descs when we can;
4197 warn when the mask is not reducible to a bit-prefix.
4198 - Let the user set ControlListenAddress in the torrc. This can be
4199 dangerous, but there are some cases (like a secured LAN) where it
4201 - Split ReachableAddresses into ReachableDirAddresses and
4202 ReachableORAddresses, so we can restrict Dir conns to port 80
4203 and OR conns to port 443.
4204 - Now we can target arch and OS in rpm builds (contributed by
4205 Phobos). Also make the resulting dist-rpm filename match the
4207 - New config options to help controllers: FetchServerDescriptors
4208 and FetchHidServDescriptors for whether to fetch server
4209 info and hidserv info or let the controller do it, and
4210 PublishServerDescriptor and PublishHidServDescriptors.
4211 - Also let the controller set the __AllDirActionsPrivate config
4212 option if you want all directory fetches/publishes to happen via
4213 Tor (it assumes your controller bootstraps your circuits).
4216 Changes in version 0.1.0.17 - 2006-02-17
4217 o Crash bugfixes on 0.1.0.x:
4218 - When servers with a non-zero DirPort came out of hibernation,
4219 sometimes they would trigger an assert.
4221 o Other important bugfixes:
4222 - On platforms that don't have getrlimit (like Windows), we were
4223 artificially constraining ourselves to a max of 1024
4224 connections. Now just assume that we can handle as many as 15000
4225 connections. Hopefully this won't cause other problems.
4227 o Backported features:
4228 - When we're a server, a client asks for an old-style directory,
4229 and our write bucket is empty, don't give it to him. This way
4230 small servers can continue to serve the directory *sometimes*,
4231 without getting overloaded.
4232 - Whenever you get a 503 in response to a directory fetch, try
4233 once more. This will become important once servers start sending
4234 503's whenever they feel busy.
4235 - Fetch a new directory every 120 minutes, not every 40 minutes.
4236 Now that we have hundreds of thousands of users running the old
4237 directory algorithm, it's starting to hurt a lot.
4238 - Bump up the period for forcing a hidden service descriptor upload
4239 from 20 minutes to 1 hour.
4242 Changes in version 0.1.1.13-alpha - 2006-02-09
4243 o Crashes in 0.1.1.x:
4244 - When you tried to setconf ORPort via the controller, Tor would
4245 crash. So people using TorCP to become a server were sad.
4246 - Solve (I hope) the stack-smashing bug that we were seeing on fast
4247 servers. The problem appears to be something do with OpenSSL's
4248 random number generation, or how we call it, or something. Let me
4249 know if the crashes continue.
4250 - Turn crypto hardware acceleration off by default, until we find
4251 somebody smart who can test it for us. (It appears to produce
4252 seg faults in at least some cases.)
4253 - Fix a rare assert error when we've tried all intro points for
4254 a hidden service and we try fetching the service descriptor again:
4255 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
4258 - Fix a major load balance bug: we were round-robining in 16 KB
4259 chunks, and servers with bandwidthrate of 20 KB, while downloading
4260 a 600 KB directory, would starve their other connections. Now we
4261 try to be a bit more fair.
4262 - Dir authorities and mirrors were never expiring the newest
4263 descriptor for each server, causing memory and directory bloat.
4264 - Fix memory-bloating and connection-bloating bug on servers: We
4265 were never closing any connection that had ever had a circuit on
4266 it, because we were checking conn->n_circuits == 0, yet we had a
4267 bug that let it go negative.
4268 - Make Tor work using squid as your http proxy again -- squid
4269 returns an error if you ask for a URL that's too long, and it uses
4270 a really generic error message. Plus, many people are behind a
4271 transparent squid so they don't even realize it.
4272 - On platforms that don't have getrlimit (like Windows), we were
4273 artificially constraining ourselves to a max of 1024
4274 connections. Now just assume that we can handle as many as 15000
4275 connections. Hopefully this won't cause other problems.
4276 - Add a new config option ExitPolicyRejectPrivate which defaults to
4277 1. This means all exit policies will begin with rejecting private
4278 addresses, unless the server operator explicitly turns it off.
4281 - Clients no longer download descriptors for non-running
4283 - Before we add new directory authorities, we should make it
4284 clear that only v1 authorities should receive/publish hidden
4285 service descriptors.
4288 - As soon as we've fetched some more directory info, immediately
4289 try to download more server descriptors. This way we don't have
4290 a 10 second pause during initial bootstrapping.
4291 - Remove even more loud log messages that the server operator can't
4293 - When we're running an obsolete or un-recommended version, make
4294 the log message more clear about what the problem is and what
4295 versions *are* still recommended.
4296 - Provide a more useful warn message when our onion queue gets full:
4297 the CPU is too slow or the exit policy is too liberal.
4298 - Don't warn when we receive a 503 from a dirserver/cache -- this
4299 will pave the way for them being able to refuse if they're busy.
4300 - When we fail to bind a listener, try to provide a more useful
4301 log message: e.g., "Is Tor already running?"
4302 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
4303 Goldberg can prove things about our handshake protocol more
4305 - MaxConn has been obsolete for a while now. Document the ConnLimit
4306 config option, which is a *minimum* number of file descriptors
4307 that must be available else Tor refuses to start.
4308 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
4309 if you log to syslog and want something other than LOG_DAEMON.
4310 - Make dirservers generate a separate "guard" flag to mean,
4311 "would make a good entry guard". Make clients parse it and vote
4312 on it. Not used by clients yet.
4313 - Implement --with-libevent-dir option to ./configure. Also, improve
4314 search techniques to find libevent, and use those for openssl too.
4315 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
4316 - Only start testing reachability once we've established a
4317 circuit. This will make startup on dirservers less noisy.
4318 - Don't try to upload hidden service descriptors until we have
4319 established a circuit.
4320 - Fix the controller's "attachstream 0" command to treat conn like
4321 it just connected, doing address remapping, handling .exit and
4322 .onion idioms, and so on. Now we're more uniform in making sure
4323 that the controller hears about new and closing connections.
4326 Changes in version 0.1.1.12-alpha - 2006-01-11
4327 o Bugfixes on 0.1.1.x:
4328 - The fix to close duplicate server connections was closing all
4329 Tor client connections if they didn't establish a circuit
4330 quickly enough. Oops.
4331 - Fix minor memory issue (double-free) that happened on exit.
4333 o Bugfixes on 0.1.0.x:
4334 - Tor didn't warn when it failed to open a log file.
4337 Changes in version 0.1.1.11-alpha - 2006-01-10
4338 o Crashes in 0.1.1.x:
4339 - Include all the assert/crash fixes from 0.1.0.16.
4340 - If you start Tor and then quit very quickly, there were some
4341 races that tried to free things that weren't allocated yet.
4342 - Fix a rare memory stomp if you're running hidden services.
4343 - Fix segfault when specifying DirServer in config without nickname.
4344 - Fix a seg fault when you finish connecting to a server but at
4345 that moment you dump his server descriptor.
4346 - Extendcircuit and Attachstream controller commands would
4347 assert/crash if you don't give them enough arguments.
4348 - Fix an assert error when we're out of space in the connection_list
4349 and we try to post a hidden service descriptor (reported by weasel).
4350 - If you specify a relative torrc path and you set RunAsDaemon in
4351 your torrc, then it chdir()'s to the new directory. If you HUP,
4352 it tries to load the new torrc location, fails, and exits.
4353 The fix: no longer allow a relative path to torrc using -f.
4356 - Implement "entry guards": automatically choose a handful of entry
4357 nodes and stick with them for all circuits. Only pick new guards
4358 when the ones you have are unsuitable, and if the old guards
4359 become suitable again, switch back. This will increase security
4360 dramatically against certain end-point attacks. The EntryNodes
4361 config option now provides some hints about which entry guards you
4362 want to use most; and StrictEntryNodes means to only use those.
4363 - New directory logic: download by descriptor digest, not by
4364 fingerprint. Caches try to download all listed digests from
4365 authorities; clients try to download "best" digests from caches.
4366 This avoids partitioning and isolating attacks better.
4367 - Make the "stable" router flag in network-status be the median of
4368 the uptimes of running valid servers, and make clients pay
4369 attention to the network-status flags. Thus the cutoff adapts
4370 to the stability of the network as a whole, making IRC, IM, etc
4371 connections more reliable.
4374 - Tor servers with dynamic IP addresses were needing to wait 18
4375 hours before they could start doing reachability testing using
4376 the new IP address and ports. This is because they were using
4377 the internal descriptor to learn what to test, yet they were only
4378 rebuilding the descriptor once they decided they were reachable.
4379 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
4380 to download certain server descriptors, throw them away, and then
4381 fetch them again after 30 minutes. Now mirrors throw away these
4382 server descriptors so clients can't get them.
4383 - We were leaving duplicate connections to other ORs open for a week,
4384 rather than closing them once we detect a duplicate. This only
4385 really affected authdirservers, but it affected them a lot.
4386 - Spread the authdirservers' reachability testing over the entire
4387 testing interval, so we don't try to do 500 TLS's at once every
4391 - If the network is down, and we try to connect to a conn because
4392 we have a circuit in mind, and we timeout (30 seconds) because the
4393 network never answers, we were expiring the circuit, but we weren't
4394 obsoleting the connection or telling the entry_guards functions.
4395 - Some Tor servers process billions of cells per day. These statistics
4396 need to be uint64_t's.
4397 - Check for integer overflows in more places, when adding elements
4398 to smartlists. This could possibly prevent a buffer overflow
4399 on malicious huge inputs. I don't see any, but I haven't looked
4401 - ReachableAddresses kept growing new "reject *:*" lines on every
4403 - When you "setconf log" via the controller, it should remove all
4404 logs. We were automatically adding back in a "log notice stdout".
4405 - Newly bootstrapped Tor networks couldn't establish hidden service
4406 circuits until they had nodes with high uptime. Be more tolerant.
4407 - We were marking servers down when they could not answer every piece
4408 of the directory request we sent them. This was far too harsh.
4409 - Fix the torify (tsocks) config file to not use Tor for localhost
4411 - Directory authorities now go to the proper authority when asking for
4412 a networkstatus, even when they want a compressed one.
4413 - Fix a harmless bug that was causing Tor servers to log
4414 "Got an end because of misc error, but we're not an AP. Closing."
4415 - Authorities were treating their own descriptor changes as cosmetic,
4416 meaning the descriptor available in the network-status and the
4417 descriptor that clients downloaded were different.
4418 - The OS X installer was adding a symlink for tor_resolve but
4419 the binary was called tor-resolve (reported by Thomas Hardly).
4420 - Workaround a problem with some http proxies where they refuse GET
4421 requests that specify "Content-Length: 0" (reported by Adrian).
4422 - Fix wrong log message when you add a "HiddenServiceNodes" config
4423 line without any HiddenServiceDir line (reported by Chris Thomas).
4426 - Write the TorVersion into the state file so we have a prayer of
4427 keeping forward and backward compatibility.
4428 - Revive the FascistFirewall config option rather than eliminating it:
4429 now it's a synonym for ReachableAddresses *:80,*:443.
4430 - Clients choose directory servers from the network status lists,
4431 not from their internal list of router descriptors. Now they can
4432 go to caches directly rather than needing to go to authorities
4434 - Directory authorities ignore router descriptors that have only
4435 cosmetic differences: do this for 0.1.0.x servers now too.
4436 - Add a new flag to network-status indicating whether the server
4437 can answer v2 directory requests too.
4438 - Authdirs now stop whining so loudly about bad descriptors that
4439 they fetch from other dirservers. So when there's a log complaint,
4440 it's for sure from a freshly uploaded descriptor.
4441 - Reduce memory requirements in our structs by changing the order
4443 - There used to be two ways to specify your listening ports in a
4444 server descriptor: on the "router" line and with a separate "ports"
4445 line. Remove support for the "ports" line.
4446 - New config option "AuthDirRejectUnlisted" for auth dirservers as
4447 a panic button: if we get flooded with unusable servers we can
4448 revert to only listing servers in the approved-routers file.
4449 - Auth dir servers can now mark a fingerprint as "!reject" or
4450 "!invalid" in the approved-routers file (as its nickname), to
4451 refuse descriptors outright or include them but marked as invalid.
4452 - Servers store bandwidth history across restarts/crashes.
4453 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
4454 get a better idea of why their circuits failed. Not used yet.
4455 - Directory mirrors now cache up to 16 unrecognized network-status
4456 docs. Now we can add new authdirservers and they'll be cached too.
4457 - When picking a random directory, prefer non-authorities if any
4459 - New controller option "getinfo desc/all-recent" to fetch the
4460 latest server descriptor for every router that Tor knows about.
4463 Changes in version 0.1.0.16 - 2006-01-02
4464 o Crash bugfixes on 0.1.0.x:
4465 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
4466 corrupting the heap, losing FDs, or crashing when we need to resize
4467 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
4468 - It turns out sparc64 platforms crash on unaligned memory access
4469 too -- so detect and avoid this.
4470 - Handle truncated compressed data correctly (by detecting it and
4472 - Fix possible-but-unlikely free(NULL) in control.c.
4473 - When we were closing connections, there was a rare case that
4474 stomped on memory, triggering seg faults and asserts.
4475 - Avoid potential infinite recursion when building a descriptor. (We
4476 don't know that it ever happened, but better to fix it anyway.)
4477 - We were neglecting to unlink marked circuits from soon-to-close OR
4478 connections, which caused some rare scribbling on freed memory.
4479 - Fix a memory stomping race bug when closing the joining point of two
4480 rendezvous circuits.
4481 - Fix an assert in time parsing found by Steven Murdoch.
4483 o Other bugfixes on 0.1.0.x:
4484 - When we're doing reachability testing, provide more useful log
4485 messages so the operator knows what to expect.
4486 - Do not check whether DirPort is reachable when we are suppressing
4487 advertising it because of hibernation.
4488 - When building with -static or on Solaris, we sometimes needed -ldl.
4489 - When we're deciding whether a stream has enough circuits around
4490 that can handle it, count the freshly dirty ones and not the ones
4491 that are so dirty they won't be able to handle it.
4492 - When we're expiring old circuits, we had a logic error that caused
4493 us to close new rendezvous circuits rather than old ones.
4494 - Give a more helpful log message when you try to change ORPort via
4495 the controller: you should upgrade Tor if you want that to work.
4496 - We were failing to parse Tor versions that start with "Tor ".
4497 - Tolerate faulty streams better: when a stream fails for reason
4498 exitpolicy, stop assuming that the router is lying about his exit
4499 policy. When a stream fails for reason misc, allow it to retry just
4500 as if it was resolvefailed. When a stream has failed three times,
4501 reset its failure count so we can try again and get all three tries.
4504 Changes in version 0.1.1.10-alpha - 2005-12-11
4505 o Correctness bugfixes on 0.1.0.x:
4506 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
4507 corrupting the heap, losing FDs, or crashing when we need to resize
4508 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
4509 - Stop doing the complex voodoo overkill checking for insecure
4510 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
4511 - When we were closing connections, there was a rare case that
4512 stomped on memory, triggering seg faults and asserts.
4513 - We were neglecting to unlink marked circuits from soon-to-close OR
4514 connections, which caused some rare scribbling on freed memory.
4515 - When we're deciding whether a stream has enough circuits around
4516 that can handle it, count the freshly dirty ones and not the ones
4517 that are so dirty they won't be able to handle it.
4518 - Recover better from TCP connections to Tor servers that are
4519 broken but don't tell you (it happens!); and rotate TLS
4520 connections once a week.
4521 - When we're expiring old circuits, we had a logic error that caused
4522 us to close new rendezvous circuits rather than old ones.
4523 - Fix a scary-looking but apparently harmless bug where circuits
4524 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
4525 servers, and never switch to state CIRCUIT_STATE_OPEN.
4526 - When building with -static or on Solaris, we sometimes needed to
4528 - Give a useful message when people run Tor as the wrong user,
4529 rather than telling them to start chowning random directories.
4530 - We were failing to inform the controller about new .onion streams.
4532 o Security bugfixes on 0.1.0.x:
4533 - Refuse server descriptors if the fingerprint line doesn't match
4534 the included identity key. Tor doesn't care, but other apps (and
4535 humans) might actually be trusting the fingerprint line.
4536 - We used to kill the circuit when we receive a relay command we
4537 don't recognize. Now we just drop it.
4538 - Start obeying our firewall options more rigorously:
4539 . If we can't get to a dirserver directly, try going via Tor.
4540 . Don't ever try to connect (as a client) to a place our
4541 firewall options forbid.
4542 . If we specify a proxy and also firewall options, obey the
4543 firewall options even when we're using the proxy: some proxies
4544 can only proxy to certain destinations.
4545 - Fix a bug found by Lasse Overlier: when we were making internal
4546 circuits (intended to be cannibalized later for rendezvous and
4547 introduction circuits), we were picking them so that they had
4548 useful exit nodes. There was no need for this, and it actually
4549 aids some statistical attacks.
4550 - Start treating internal circuits and exit circuits separately.
4551 It's important to keep them separate because internal circuits
4552 have their last hops picked like middle hops, rather than like
4553 exit hops. So exiting on them will break the user's expectations.
4555 o Bugfixes on 0.1.1.x:
4556 - Take out the mis-feature where we tried to detect IP address
4557 flapping for people with DynDNS, and chose not to upload a new
4558 server descriptor sometimes.
4559 - Try to be compatible with OpenSSL 0.9.6 again.
4560 - Log fix: when the controller is logging about .onion addresses,
4561 sometimes it didn't include the ".onion" part of the address.
4562 - Don't try to modify options->DirServers internally -- if the
4563 user didn't specify any, just add the default ones directly to
4564 the trusted dirserver list. This fixes a bug where people running
4565 controllers would use SETCONF on some totally unrelated config
4566 option, and Tor would start yelling at them about changing their
4568 - Let the controller's redirectstream command specify a port, in
4569 case the controller wants to change that too.
4570 - When we requested a pile of server descriptors, we sometimes
4571 accidentally launched a duplicate request for the first one.
4572 - Bugfix for trackhostexits: write down the fingerprint of the
4573 chosen exit, not its nickname, because the chosen exit might not
4575 - When parsing foo.exit, if foo is unknown, and we are leaving
4576 circuits unattached, set the chosen_exit field and leave the
4577 address empty. This matters because controllers got confused
4579 - Directory authorities no longer try to download server
4580 descriptors that they know they will reject.
4582 o Features and updates:
4583 - Replace balanced trees with hash tables: this should make stuff
4584 significantly faster.
4585 - Resume using the AES counter-mode implementation that we ship,
4586 rather than OpenSSL's. Ours is significantly faster.
4587 - Many other CPU and memory improvements.
4588 - Add a new config option FastFirstHopPK (on by default) so clients
4589 do a trivial crypto handshake for their first hop, since TLS has
4590 already taken care of confidentiality and authentication.
4591 - Add a new config option TestSocks so people can see if their
4592 applications are using socks4, socks4a, socks5-with-ip, or
4593 socks5-with-hostname. This way they don't have to keep mucking
4594 with tcpdump and wondering if something got cached somewhere.
4595 - Warn when listening on a public address for socks. I suspect a
4596 lot of people are setting themselves up as open socks proxies,
4597 and they have no idea that jerks on the Internet are using them,
4598 since they simply proxy the traffic into the Tor network.
4599 - Add "private:*" as an alias in configuration for policies. Now
4600 you can simplify your exit policy rather than needing to list
4601 every single internal or nonroutable network space.
4602 - Add a new controller event type that allows controllers to get
4603 all server descriptors that were uploaded to a router in its role
4604 as authoritative dirserver.
4605 - Start shipping socks-extensions.txt, tor-doc-unix.html,
4606 tor-doc-server.html, and stylesheet.css in the tarball.
4607 - Stop shipping tor-doc.html in the tarball.
4610 Changes in version 0.1.1.9-alpha - 2005-11-15
4611 o Usability improvements:
4612 - Start calling it FooListenAddress rather than FooBindAddress,
4613 since few of our users know what it means to bind an address
4615 - Reduce clutter in server logs. We're going to try to make
4616 them actually usable now. New config option ProtocolWarnings that
4617 lets you hear about how _other Tors_ are breaking the protocol. Off
4619 - Divide log messages into logging domains. Once we put some sort
4620 of interface on this, it will let people looking at more verbose
4621 log levels specify the topics they want to hear more about.
4622 - Make directory servers return better http 404 error messages
4623 instead of a generic "Servers unavailable".
4624 - Check for even more Windows version flags when writing the platform
4625 string in server descriptors, and note any we don't recognize.
4626 - Clean up more of the OpenSSL memory when exiting, so we can detect
4627 memory leaks better.
4628 - Make directory authorities be non-versioning, non-naming by
4629 default. Now we can add new directory servers without requiring
4630 their operators to pay close attention.
4631 - When logging via syslog, include the pid whenever we provide
4632 a log entry. Suggested by Todd Fries.
4634 o Performance improvements:
4635 - Directory servers now silently throw away new descriptors that
4636 haven't changed much if the timestamps are similar. We do this to
4637 tolerate older Tor servers that upload a new descriptor every 15
4638 minutes. (It seemed like a good idea at the time.)
4639 - Inline bottleneck smartlist functions; use fast versions by default.
4640 - Add a "Map from digest to void*" abstraction digestmap_t so we
4641 can do less hex encoding/decoding. Use it in router_get_by_digest()
4642 to resolve a performance bottleneck.
4643 - Allow tor_gzip_uncompress to extract as much as possible from
4644 truncated compressed data. Try to extract as many
4645 descriptors as possible from truncated http responses (when
4646 DIR_PURPOSE_FETCH_ROUTERDESC).
4647 - Make circ->onionskin a pointer, not a static array. moria2 was using
4648 125000 circuit_t's after it had been up for a few weeks, which
4649 translates to 20+ megs of wasted space.
4650 - The private half of our EDH handshake keys are now chosen out
4651 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
4653 o Security improvements:
4654 - Start making directory caches retain old routerinfos, so soon
4655 clients can start asking by digest of descriptor rather than by
4656 fingerprint of server.
4657 - Add half our entropy from RAND_poll in OpenSSL. This knows how
4658 to use egd (if present), openbsd weirdness (if present), vms/os2
4659 weirdness (if we ever port there), and more in the future.
4661 o Bugfixes on 0.1.0.x:
4662 - Do round-robin writes of at most 16 kB per write. This might be
4663 more fair on loaded Tor servers, and it might resolve our Windows
4664 crash bug. It might also slow things down.
4665 - Our TLS handshakes were generating a single public/private
4666 keypair for the TLS context, rather than making a new one for
4667 each new connections. Oops. (But we were still rotating them
4668 periodically, so it's not so bad.)
4669 - When we were cannibalizing a circuit with a particular exit
4670 node in mind, we weren't checking to see if that exit node was
4671 already present earlier in the circuit. Oops.
4672 - When a Tor server's IP changes (e.g. from a dyndns address),
4673 upload a new descriptor so clients will learn too.
4674 - Really busy servers were keeping enough circuits open on stable
4675 connections that they were wrapping around the circuit_id
4676 space. (It's only two bytes.) This exposed a bug where we would
4677 feel free to reuse a circuit_id even if it still exists but has
4678 been marked for close. Try to fix this bug. Some bug remains.
4679 - If we would close a stream early (e.g. it asks for a .exit that
4680 we know would refuse it) but the LeaveStreamsUnattached config
4681 option is set by the controller, then don't close it.
4683 o Bugfixes on 0.1.1.8-alpha:
4684 - Fix a big pile of memory leaks, some of them serious.
4685 - Do not try to download a routerdesc if we would immediately reject
4687 - Resume inserting a newline between all router descriptors when
4688 generating (old style) signed directories, since our spec says
4690 - When providing content-type application/octet-stream for
4691 server descriptors using .z, we were leaving out the
4692 content-encoding header. Oops. (Everything tolerated this just
4693 fine, but that doesn't mean we need to be part of the problem.)
4694 - Fix a potential seg fault in getconf and getinfo using version 1
4695 of the controller protocol.
4696 - Avoid crash: do not check whether DirPort is reachable when we
4697 are suppressing it because of hibernation.
4698 - Make --hash-password not crash on exit.
4701 Changes in version 0.1.1.8-alpha - 2005-10-07
4702 o New features (major):
4703 - Clients don't download or use the directory anymore. Now they
4704 download and use network-statuses from the trusted dirservers,
4705 and fetch individual server descriptors as needed from mirrors.
4706 See dir-spec.txt for all the gory details.
4707 - Be more conservative about whether to advertise our DirPort.
4708 The main change is to not advertise if we're running at capacity
4709 and either a) we could hibernate or b) our capacity is low and
4710 we're using a default DirPort.
4711 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
4713 o New features (minor):
4714 - Try to be smart about when to retry network-status and
4715 server-descriptor fetches. Still needs some tuning.
4716 - Stop parsing, storing, or using running-routers output (but
4717 mirrors still cache and serve it).
4718 - Consider a threshold of versioning dirservers (dirservers who have
4719 an opinion about which Tor versions are still recommended) before
4720 deciding whether to warn the user that he's obsolete.
4721 - Dirservers can now reject/invalidate by key and IP, with the
4722 config options "AuthDirInvalid" and "AuthDirReject". This is
4723 useful since currently we automatically list servers as running
4724 and usable even if we know they're jerks.
4725 - Provide dire warnings to any users who set DirServer; move it out
4726 of torrc.sample and into torrc.complete.
4727 - Add MyFamily to torrc.sample in the server section.
4728 - Add nicknames to the DirServer line, so we can refer to them
4729 without requiring all our users to memorize their IP addresses.
4730 - When we get an EOF or a timeout on a directory connection, note
4731 how many bytes of serverdesc we are dropping. This will help
4732 us determine whether it is smart to parse incomplete serverdesc
4734 - Add a new function to "change pseudonyms" -- that is, to stop
4735 using any currently-dirty circuits for new streams, so we don't
4736 link new actions to old actions. Currently it's only called on
4737 HUP (or SIGNAL RELOAD).
4738 - On sighup, if UseHelperNodes changed to 1, use new circuits.
4739 - Start using RAND_bytes rather than RAND_pseudo_bytes from
4740 OpenSSL. Also, reseed our entropy every hour, not just at
4741 startup. And entropy in 512-bit chunks, not 160-bit chunks.
4743 o Fixes on 0.1.1.7-alpha:
4744 - Nobody ever implemented EVENT_ADDRMAP for control protocol
4745 version 0, so don't let version 0 controllers ask for it.
4746 - If you requested something with too many newlines via the
4747 v1 controller protocol, you could crash tor.
4748 - Fix a number of memory leaks, including some pretty serious ones.
4749 - Re-enable DirPort testing again, so Tor servers will be willing
4750 to advertise their DirPort if it's reachable.
4751 - On TLS handshake, only check the other router's nickname against
4752 its expected nickname if is_named is set.
4754 o Fixes forward-ported from 0.1.0.15:
4755 - Don't crash when we don't have any spare file descriptors and we
4756 try to spawn a dns or cpu worker.
4757 - Make the numbers in read-history and write-history into uint64s,
4758 so they don't overflow and publish negatives in the descriptor.
4761 - For the OS X package's modified privoxy config file, comment
4762 out the "logfile" line so we don't log everything passed
4764 - We were whining about using socks4 or socks5-with-local-lookup
4765 even when it's an IP in the "virtual" range we designed exactly
4767 - We were leaking some memory every time the client changes IPs.
4768 - Never call free() on tor_malloc()d memory. This will help us
4769 use dmalloc to detect memory leaks.
4770 - Check for named servers when looking them up by nickname;
4771 warn when we'recalling a non-named server by its nickname;
4772 don't warn twice about the same name.
4773 - Try to list MyFamily elements by key, not by nickname, and warn
4774 if we've not heard of the server.
4775 - Make windows platform detection (uname equivalent) smarter.
4776 - It turns out sparc64 doesn't like unaligned access either.
4779 Changes in version 0.1.0.15 - 2005-09-23
4780 o Bugfixes on 0.1.0.x:
4781 - Reject ports 465 and 587 (spam targets) in default exit policy.
4782 - Don't crash when we don't have any spare file descriptors and we
4783 try to spawn a dns or cpu worker.
4784 - Get rid of IgnoreVersion undocumented config option, and make us
4785 only warn, never exit, when we're running an obsolete version.
4786 - Don't try to print a null string when your server finds itself to
4787 be unreachable and the Address config option is empty.
4788 - Make the numbers in read-history and write-history into uint64s,
4789 so they don't overflow and publish negatives in the descriptor.
4790 - Fix a minor memory leak in smartlist_string_remove().
4791 - We were only allowing ourselves to upload a server descriptor at
4792 most every 20 minutes, even if it changed earlier than that.
4793 - Clean up log entries that pointed to old URLs.
4796 Changes in version 0.1.1.7-alpha - 2005-09-14
4797 o Fixes on 0.1.1.6-alpha:
4798 - Exit servers were crashing when people asked them to make a
4799 connection to an address not in their exit policy.
4800 - Looking up a non-existent stream for a v1 control connection would
4802 - Fix a seg fault if we ask a dirserver for a descriptor by
4803 fingerprint but he doesn't know about him.
4804 - SETCONF was appending items to linelists, not clearing them.
4805 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
4806 out and refuse the setconf if it would fail.
4807 - Downgrade the dirserver log messages when whining about
4811 - Add Peter Palfrader's check-tor script to tor/contrib/
4812 It lets you easily check whether a given server (referenced by
4813 nickname) is reachable by you.
4814 - Numerous changes to move towards client-side v2 directories. Not
4818 - If the user gave tor an odd number of command-line arguments,
4819 we were silently ignoring the last one. Now we complain and fail.
4820 [This wins the oldest-bug prize -- this bug has been present since
4821 November 2002, as released in Tor 0.0.0.]
4822 - Do not use unaligned memory access on alpha, mips, or mipsel.
4823 It *works*, but is very slow, so we treat them as if it doesn't.
4824 - Retry directory requests if we fail to get an answer we like
4825 from a given dirserver (we were retrying before, but only if
4826 we fail to connect).
4827 - When writing the RecommendedVersions line, sort them first.
4828 - When the client asked for a rendezvous port that the hidden
4829 service didn't want to provide, we were sending an IP address
4830 back along with the end cell. Fortunately, it was zero. But stop
4832 - Correct "your server is reachable" log entries to indicate that
4833 it was self-testing that told us so.
4836 Changes in version 0.1.1.6-alpha - 2005-09-09
4837 o Fixes on 0.1.1.5-alpha:
4838 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
4839 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
4840 - Fix bug with tor_memmem finding a match at the end of the string.
4841 - Make unit tests run without segfaulting.
4842 - Resolve some solaris x86 compile warnings.
4843 - Handle duplicate lines in approved-routers files without warning.
4844 - Fix bug where as soon as a server refused any requests due to his
4845 exit policy (e.g. when we ask for localhost and he tells us that's
4846 127.0.0.1 and he won't do it), we decided he wasn't obeying his
4847 exit policy using him for any exits.
4848 - Only do openssl hardware accelerator stuff if openssl version is
4851 o New controller features/fixes:
4852 - Add a "RESETCONF" command so you can set config options like
4853 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
4854 a config option in the torrc with no value, then it clears it
4855 entirely (rather than setting it to its default).
4856 - Add a "GETINFO config-file" to tell us where torrc is.
4857 - Avoid sending blank lines when GETINFO replies should be empty.
4858 - Add a QUIT command for the controller (for using it manually).
4859 - Fix a bug in SAVECONF that was adding default dirservers and
4860 other redundant entries to the torrc file.
4862 o Start on the new directory design:
4863 - Generate, publish, cache, serve new network-status format.
4864 - Publish individual descriptors (by fingerprint, by "all", and by
4866 - Publish client and server recommended versions separately.
4867 - Allow tor_gzip_uncompress() to handle multiple concatenated
4868 compressed strings. Serve compressed groups of router
4869 descriptors. The compression logic here could be more
4871 - Distinguish v1 authorities (all currently trusted directories)
4872 from v2 authorities (all trusted directories).
4873 - Change DirServers config line to note which dirs are v1 authorities.
4874 - Add configuration option "V1AuthoritativeDirectory 1" which
4875 moria1, moria2, and tor26 should set.
4876 - Remove option when getting directory cache to see whether they
4877 support running-routers; they all do now. Replace it with one
4878 to see whether caches support v2 stuff.
4881 - Dirservers now do their own external reachability testing of each
4882 Tor server, and only list them as running if they've been found to
4883 be reachable. We also send back warnings to the server's logs if
4884 it uploads a descriptor that we already believe is unreachable.
4885 - Implement exit enclaves: if we know an IP address for the
4886 destination, and there's a running Tor server at that address
4887 which allows exit to the destination, then extend the circuit to
4888 that exit first. This provides end-to-end encryption and end-to-end
4889 authentication. Also, if the user wants a .exit address or enclave,
4890 use 4 hops rather than 3, and cannibalize a general circ for it
4892 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
4893 controller. Also, rotate dns and cpu workers if the controller
4894 changes options that will affect them; and initialize the dns
4895 worker cache tree whether or not we start out as a server.
4896 - Only upload a new server descriptor when options change, 18
4897 hours have passed, uptime is reset, or bandwidth changes a lot.
4898 - Check [X-]Forwarded-For headers in HTTP requests when generating
4899 log messages. This lets people run dirservers (and caches) behind
4900 Apache but still know which IP addresses are causing warnings.
4902 o Config option changes:
4903 - Replace (Fascist)Firewall* config options with a new
4904 ReachableAddresses option that understands address policies.
4905 For example, "ReachableAddresses *:80,*:443"
4906 - Get rid of IgnoreVersion undocumented config option, and make us
4907 only warn, never exit, when we're running an obsolete version.
4908 - Make MonthlyAccountingStart config option truly obsolete now.
4911 - Reject ports 465 and 587 in the default exit policy, since
4912 people have started using them for spam too.
4913 - It turns out we couldn't bootstrap a network since we added
4914 reachability detection in 0.1.0.1-rc. Good thing the Tor network
4915 has never gone down. Add an AssumeReachable config option to let
4916 servers and dirservers bootstrap. When we're trying to build a
4917 high-uptime or high-bandwidth circuit but there aren't enough
4918 suitable servers, try being less picky rather than simply failing.
4919 - Our logic to decide if the OR we connected to was the right guy
4920 was brittle and maybe open to a mitm for unverified routers.
4921 - We weren't cannibalizing circuits correctly for
4922 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
4923 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
4924 build those from scratch. This should make hidden services faster.
4925 - Predict required circuits better, with an eye toward making hidden
4926 services faster on the service end.
4927 - Retry streams if the exit node sends back a 'misc' failure. This
4928 should result in fewer random failures. Also, after failing
4929 from resolve failed or misc, reset the num failures, so we give
4930 it a fair shake next time we try.
4931 - Clean up the rendezvous warn log msgs, and downgrade some to info.
4932 - Reduce severity on logs about dns worker spawning and culling.
4933 - When we're shutting down and we do something like try to post a
4934 server descriptor or rendezvous descriptor, don't complain that
4935 we seem to be unreachable. Of course we are, we're shutting down.
4936 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
4937 We don't use them yet, but maybe one day our DNS resolver will be
4938 able to discover them.
4939 - Make ContactInfo mandatory for authoritative directory servers.
4940 - Require server descriptors to list IPv4 addresses -- hostnames
4941 are no longer allowed. This also fixes some potential security
4942 problems with people providing hostnames as their address and then
4943 preferentially resolving them to partition users.
4944 - Change log line for unreachability to explicitly suggest /etc/hosts
4945 as the culprit. Also make it clearer what IP address and ports we're
4946 testing for reachability.
4947 - Put quotes around user-supplied strings when logging so users are
4948 more likely to realize if they add bad characters (like quotes)
4950 - Let auth dir servers start without specifying an Address config
4952 - Make unit tests (and other invocations that aren't the real Tor)
4953 run without launching listeners, creating subdirectories, and so on.
4956 Changes in version 0.1.1.5-alpha - 2005-08-08
4957 o Bugfixes included in 0.1.0.14.
4959 o Bugfixes on 0.1.0.x:
4960 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
4961 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
4962 it would silently using ignore the 6668.
4965 Changes in version 0.1.0.14 - 2005-08-08
4966 o Bugfixes on 0.1.0.x:
4967 - Fix the other half of the bug with crypto handshakes
4969 - Fix an assert trigger if you send a 'signal term' via the
4970 controller when it's listening for 'event info' messages.
4973 Changes in version 0.1.1.4-alpha - 2005-08-04
4974 o Bugfixes included in 0.1.0.13.
4977 - Improve tor_gettimeofday() granularity on windows.
4978 - Make clients regenerate their keys when their IP address changes.
4979 - Implement some more GETINFO goodness: expose helper nodes, config
4980 options, getinfo keys.
4983 Changes in version 0.1.0.13 - 2005-08-04
4984 o Bugfixes on 0.1.0.x:
4985 - Fix a critical bug in the security of our crypto handshakes.
4986 - Fix a size_t underflow in smartlist_join_strings2() that made
4987 it do bad things when you hand it an empty smartlist.
4988 - Fix Windows installer to ship Tor license (thanks to Aphex for
4989 pointing out this oversight) and put a link to the doc directory
4991 - Explicitly set no-unaligned-access for sparc: it turns out the
4992 new gcc's let you compile broken code, but that doesn't make it
4996 Changes in version 0.1.1.3-alpha - 2005-07-23
4997 o Bugfixes on 0.1.1.2-alpha:
4998 - Fix a bug in handling the controller's "post descriptor"
5000 - Fix several bugs in handling the controller's "extend circuit"
5002 - Fix a bug in handling the controller's "stream status" event.
5003 - Fix an assert failure if we have a controller listening for
5004 circuit events and we go offline.
5005 - Re-allow hidden service descriptors to publish 0 intro points.
5006 - Fix a crash when generating your hidden service descriptor if
5007 you don't have enough intro points already.
5009 o New features on 0.1.1.2-alpha:
5010 - New controller function "getinfo accounting", to ask how
5011 many bytes we've used in this time period.
5012 - Experimental support for helper nodes: a lot of the risk from
5013 a small static adversary comes because users pick new random
5014 nodes every time they rebuild a circuit. Now users will try to
5015 stick to the same small set of entry nodes if they can. Not
5016 enabled by default yet.
5018 o Bugfixes on 0.1.0.12:
5019 - If you're an auth dir server, always publish your dirport,
5020 even if you haven't yet found yourself to be reachable.
5021 - Fix a size_t underflow in smartlist_join_strings2() that made
5022 it do bad things when you hand it an empty smartlist.
5025 Changes in version 0.1.0.12 - 2005-07-18
5026 o New directory servers:
5027 - tor26 has changed IP address.
5029 o Bugfixes on 0.1.0.x:
5030 - Fix a possible double-free in tor_gzip_uncompress().
5031 - When --disable-threads is set, do not search for or link against
5033 - Don't trigger an assert if an authoritative directory server
5034 claims its dirport is 0.
5035 - Fix bug with removing Tor as an NT service: some people were
5036 getting "The service did not return an error." Thanks to Matt
5040 Changes in version 0.1.1.2-alpha - 2005-07-15
5041 o New directory servers:
5042 - tor26 has changed IP address.
5044 o Bugfixes on 0.1.0.x, crashes/leaks:
5045 - Port the servers-not-obeying-their-exit-policies fix from
5047 - Fix an fd leak in start_daemon().
5048 - On Windows, you can't always reopen a port right after you've
5049 closed it. So change retry_listeners() to only close and re-open
5050 ports that have changed.
5051 - Fix a possible double-free in tor_gzip_uncompress().
5053 o Bugfixes on 0.1.0.x, usability:
5054 - When tor_socketpair() fails in Windows, give a reasonable
5055 Windows-style errno back.
5056 - Let people type "tor --install" as well as "tor -install" when
5058 want to make it an NT service.
5059 - NT service patch from Matt Edman to improve error messages.
5060 - When the controller asks for a config option with an abbreviated
5061 name, give the full name in our response.
5062 - Correct the man page entry on TrackHostExitsExpire.
5063 - Looks like we were never delivering deflated (i.e. compressed)
5064 running-routers lists, even when asked. Oops.
5065 - When --disable-threads is set, do not search for or link against
5068 o Bugfixes on 0.1.1.x:
5069 - Fix a seg fault with autodetecting which controller version is
5073 - New hidden service descriptor format: put a version in it, and
5074 let people specify introduction/rendezvous points that aren't
5075 in "the directory" (which is subjective anyway).
5076 - Allow the DEBUG controller event to work again. Mark certain log
5077 entries as "don't tell this to controllers", so we avoid cycles.
5080 Changes in version 0.1.0.11 - 2005-06-30
5081 o Bugfixes on 0.1.0.x:
5082 - Fix major security bug: servers were disregarding their
5083 exit policies if clients behaved unexpectedly.
5084 - Make OS X init script check for missing argument, so we don't
5085 confuse users who invoke it incorrectly.
5086 - Fix a seg fault in "tor --hash-password foo".
5087 - The MAPADDRESS control command was broken.
5090 Changes in version 0.1.1.1-alpha - 2005-06-29
5092 - Make OS X init script check for missing argument, so we don't
5093 confuse users who invoke it incorrectly.
5094 - Fix a seg fault in "tor --hash-password foo".
5095 - Fix a possible way to DoS dirservers.
5096 - When we complain that your exit policy implicitly allows local or
5097 private address spaces, name them explicitly so operators can
5099 - Make the log message less scary when all the dirservers are
5100 temporarily unreachable.
5101 - We were printing the number of idle dns workers incorrectly when
5105 - Revised controller protocol (version 1) that uses ascii rather
5106 than binary. Add supporting libraries in python and java so you
5107 can use the controller from your applications without caring how
5109 - Spiffy new support for crypto hardware accelerators. Can somebody
5113 Changes in version 0.0.9.10 - 2005-06-16
5114 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
5115 - Refuse relay cells that claim to have a length larger than the
5116 maximum allowed. This prevents a potential attack that could read
5117 arbitrary memory (e.g. keys) from an exit server's process
5121 Changes in version 0.1.0.10 - 2005-06-14
5122 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
5123 libevent before 1.1a.
5126 Changes in version 0.1.0.9-rc - 2005-06-09
5128 - Reset buf->highwater every time buf_shrink() is called, not just on
5129 a successful shrink. This was causing significant memory bloat.
5130 - Fix buffer overflow when checking hashed passwords.
5131 - Security fix: if seeding the RNG on Win32 fails, quit.
5132 - Allow seeding the RNG on Win32 even when you're not running as
5134 - Disable threading on Solaris too. Something is wonky with it,
5135 cpuworkers, and reentrant libs.
5136 - Reenable the part of the code that tries to flush as soon as an
5137 OR outbuf has a full TLS record available. Perhaps this will make
5138 OR outbufs not grow as huge except in rare cases, thus saving lots
5139 of CPU time plus memory.
5140 - Reject malformed .onion addresses rather then passing them on as
5141 normal web requests.
5142 - Adapt patch from Adam Langley: fix possible memory leak in
5143 tor_lookup_hostname().
5144 - Initialize libevent later in the startup process, so the logs are
5145 already established by the time we start logging libevent warns.
5146 - Use correct errno on win32 if libevent fails.
5147 - Check and warn about known-bad/slow libevent versions.
5148 - Pay more attention to the ClientOnly config option.
5149 - Have torctl.in/tor.sh.in check for location of su binary (needed
5151 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
5152 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
5153 HttpProxyAuthenticator
5154 - Stop warning about sigpipes in the logs. We're going to
5155 pretend that getting these occassionally is normal and fine.
5156 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
5158 installer screens; and don't put stuff into StartupItems unless
5159 the user asks you to.
5160 - Require servers that use the default dirservers to have public IP
5161 addresses. We have too many servers that are configured with private
5162 IPs and their admins never notice the log entries complaining that
5163 their descriptors are being rejected.
5164 - Add OSX uninstall instructions. An actual uninstall script will
5168 Changes in version 0.1.0.8-rc - 2005-05-23
5170 - It turns out that kqueue on OS X 10.3.9 was causing kernel
5171 panics. Disable kqueue on all OS X Tors.
5172 - Fix RPM: remove duplicate line accidentally added to the rpm
5174 - Disable threads on openbsd too, since its gethostaddr is not
5176 - Tolerate libevent 0.8 since it still works, even though it's
5178 - Enable building on Red Hat 9.0 again.
5179 - Allow the middle hop of the testing circuit to be running any
5180 version, now that most of them have the bugfix to let them connect
5181 to unknown servers. This will allow reachability testing to work
5182 even when 0.0.9.7-0.0.9.9 become obsolete.
5183 - Handle relay cells with rh.length too large. This prevents
5184 a potential attack that could read arbitrary memory (maybe even
5185 keys) from the exit server's process.
5186 - We screwed up the dirport reachability testing when we don't yet
5187 have a cached version of the directory. Hopefully now fixed.
5188 - Clean up router_load_single_router() (used by the controller),
5189 so it doesn't seg fault on error.
5190 - Fix a minor memory leak when somebody establishes an introduction
5191 point at your Tor server.
5192 - If a socks connection ends because read fails, don't warn that
5193 you're not sending a socks reply back.
5196 - Add HttpProxyAuthenticator config option too, that works like
5197 the HttpsProxyAuthenticator config option.
5198 - Encode hashed controller passwords in hex instead of base64,
5199 to make it easier to write controllers.
5202 Changes in version 0.1.0.7-rc - 2005-05-17
5204 - Fix a bug in the OS X package installer that prevented it from
5205 installing on Tiger.
5206 - Fix a script bug in the OS X package installer that made it
5207 complain during installation.
5208 - Find libevent even if it's hiding in /usr/local/ and your
5209 CFLAGS and LDFLAGS don't tell you to look there.
5210 - Be able to link with libevent as a shared library (the default
5211 after 1.0d), even if it's hiding in /usr/local/lib and even
5212 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
5213 assuming you're running gcc. Otherwise fail and give a useful
5215 - Fix a bug in the RPM packager: set home directory for _tor to
5216 something more reasonable when first installing.
5217 - Free a minor amount of memory that is still reachable on exit.
5220 Changes in version 0.1.0.6-rc - 2005-05-14
5222 - Implement --disable-threads configure option. Disable threads on
5223 netbsd by default, because it appears to have no reentrant resolver
5225 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
5226 release (1.1) detects and disables kqueue if it's broken.
5227 - Append default exit policy before checking for implicit internal
5228 addresses. Now we don't log a bunch of complaints on startup
5229 when using the default exit policy.
5230 - Some people were putting "Address " in their torrc, and they had
5231 a buggy resolver that resolved " " to 0.0.0.0. Oops.
5232 - If DataDir is ~/.tor, and that expands to /.tor, then default to
5233 LOCALSTATEDIR/tor instead.
5234 - Fix fragmented-message bug in TorControl.py.
5235 - Resolve a minor bug which would prevent unreachable dirports
5236 from getting suppressed in the published descriptor.
5237 - When the controller gave us a new descriptor, we weren't resolving
5238 it immediately, so Tor would think its address was 0.0.0.0 until
5239 we fetched a new directory.
5240 - Fix an uppercase/lowercase case error in suppressing a bogus
5241 libevent warning on some Linuxes.
5244 - Begin scrubbing sensitive strings from logs by default. Turn off
5245 the config option SafeLogging if you need to do debugging.
5246 - Switch to a new buffer management algorithm, which tries to avoid
5247 reallocing and copying quite as much. In first tests it looks like
5248 it uses *more* memory on average, but less cpu.
5249 - First cut at support for "create-fast" cells. Clients can use
5250 these when extending to their first hop, since the TLS already
5251 provides forward secrecy and authentication. Not enabled on
5253 - When dirservers refuse a router descriptor, we now log its
5254 contactinfo, platform, and the poster's IP address.
5255 - Call tor_free_all instead of connections_free_all after forking, to
5256 save memory on systems that need to fork.
5257 - Whine at you if you're a server and you don't set your contactinfo.
5258 - Implement --verify-config command-line option to check if your torrc
5259 is valid without actually launching Tor.
5260 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
5261 rather than just rejecting it.
5264 Changes in version 0.1.0.5-rc - 2005-04-27
5266 - Stop trying to print a null pointer if an OR conn fails because
5267 we didn't like its cert.
5269 - Switch our internal buffers implementation to use a ring buffer,
5270 to hopefully improve performance for fast servers a lot.
5271 - Add HttpsProxyAuthenticator support (basic auth only), based
5272 on patch from Adam Langley.
5273 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
5274 the fast servers that have been joining lately.
5275 - Give hidden service accesses extra time on the first attempt,
5276 since 60 seconds is often only barely enough. This might improve
5278 - Improve performance for dirservers: stop re-parsing the whole
5279 directory every time you regenerate it.
5280 - Add more debugging info to help us find the weird dns freebsd
5281 pthreads bug; cleaner debug messages to help track future issues.
5284 Changes in version 0.0.9.9 - 2005-04-23
5285 o Bugfixes on 0.0.9.x:
5286 - If unofficial Tor clients connect and send weird TLS certs, our
5287 Tor server triggers an assert. This release contains a minimal
5288 backport from the broader fix that we put into 0.1.0.4-rc.
5291 Changes in version 0.1.0.4-rc - 2005-04-23
5293 - If unofficial Tor clients connect and send weird TLS certs, our
5294 Tor server triggers an assert. Stop asserting, and start handling
5295 TLS errors better in other situations too.
5296 - When the controller asks us to tell it about all the debug-level
5297 logs, it turns out we were generating debug-level logs while
5298 telling it about them, which turns into a bad loop. Now keep
5299 track of whether you're sending a debug log to the controller,
5300 and don't log when you are.
5301 - Fix the "postdescriptor" feature of the controller interface: on
5302 non-complete success, only say "done" once.
5304 - Clients are now willing to load balance over up to 2mB, not 1mB,
5305 of advertised bandwidth capacity.
5306 - Add a NoPublish config option, so you can be a server (e.g. for
5307 testing running Tor servers in other Tor networks) without
5308 publishing your descriptor to the primary dirservers.
5311 Changes in version 0.1.0.3-rc - 2005-04-08
5312 o Improvements on 0.1.0.2-rc:
5313 - Client now retries when streams end early for 'hibernating' or
5314 'resource limit' reasons, rather than failing them.
5315 - More automated handling for dirserver operators:
5316 - Automatically approve nodes running 0.1.0.2-rc or later,
5317 now that the the reachability detection stuff is working.
5318 - Now we allow two unverified servers with the same nickname
5319 but different keys. But if a nickname is verified, only that
5320 nickname+key are allowed.
5321 - If you're an authdirserver connecting to an address:port,
5322 and it's not the OR you were expecting, forget about that
5323 descriptor. If he *was* the one you were expecting, then forget
5324 about all other descriptors for that address:port.
5325 - Allow servers to publish descriptors from 12 hours in the future.
5326 Corollary: only whine about clock skew from the dirserver if
5327 he's a trusted dirserver (since now even verified servers could
5328 have quite wrong clocks).
5329 - Adjust maximum skew and age for rendezvous descriptors: let skew
5330 be 48 hours rather than 90 minutes.
5331 - Efficiency improvements:
5332 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
5333 it much faster to look up a circuit for each relay cell.
5334 - Remove most calls to assert_all_pending_dns_resolves_ok(),
5335 since they're eating our cpu on exit nodes.
5336 - Stop wasting time doing a case insensitive comparison for every
5337 dns name every time we do any lookup. Canonicalize the names to
5338 lowercase and be done with it.
5339 - Start sending 'truncated' cells back rather than destroy cells,
5340 if the circuit closes in front of you. This means we won't have
5341 to abandon partially built circuits.
5342 - Only warn once per nickname from add_nickname_list_to_smartlist
5343 per failure, so an entrynode or exitnode choice that's down won't
5345 - Put a note in the torrc about abuse potential with the default
5347 - Revise control spec and implementation to allow all log messages to
5348 be sent to controller with their severities intact (suggested by
5349 Matt Edman). Update TorControl to handle new log event types.
5350 - Provide better explanation messages when controller's POSTDESCRIPTOR
5352 - Stop putting nodename in the Platform string in server descriptors.
5353 It doesn't actually help, and it is confusing/upsetting some people.
5355 o Bugfixes on 0.1.0.2-rc:
5356 - We were printing the host mask wrong in exit policies in server
5357 descriptors. This isn't a critical bug though, since we were still
5358 obeying the exit policy internally.
5359 - Fix Tor when compiled with libevent but without pthreads: move
5360 connection_unregister() from _connection_free() to
5362 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
5363 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
5364 when we look through the connection array, we'll find any of the
5365 cpu/dnsworkers. This is no good.
5367 o Bugfixes on 0.0.9.8:
5368 - Fix possible bug on threading platforms (e.g. win32) which was
5369 leaking a file descriptor whenever a cpuworker or dnsworker died.
5370 - When using preferred entry or exit nodes, ignore whether the
5371 circuit wants uptime or capacity. They asked for the nodes, they
5373 - chdir() to your datadirectory at the *end* of the daemonize process,
5374 not the beginning. This was a problem because the first time you
5375 run tor, if your datadir isn't there, and you have runasdaemon set
5376 to 1, it will try to chdir to it before it tries to create it. Oops.
5377 - Handle changed router status correctly when dirserver reloads
5378 fingerprint file. We used to be dropping all unverified descriptors
5379 right then. The bug was hidden because we would immediately
5380 fetch a directory from another dirserver, which would include the
5381 descriptors we just dropped.
5382 - When we're connecting to an OR and he's got a different nickname/key
5383 than we were expecting, only complain loudly if we're an OP or a
5384 dirserver. Complaining loudly to the OR admins just confuses them.
5385 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
5386 artificially capped at 500kB.
5389 Changes in version 0.0.9.8 - 2005-04-07
5390 o Bugfixes on 0.0.9.x:
5391 - We have a bug that I haven't found yet. Sometimes, very rarely,
5392 cpuworkers get stuck in the 'busy' state, even though the cpuworker
5393 thinks of itself as idle. This meant that no new circuits ever got
5394 established. Here's a workaround to kill any cpuworker that's been
5395 busy for more than 100 seconds.
5398 Changes in version 0.1.0.2-rc - 2005-04-01
5399 o Bugfixes on 0.1.0.1-rc:
5400 - Fixes on reachability detection:
5401 - Don't check for reachability while hibernating.
5402 - If ORPort is reachable but DirPort isn't, still publish the
5403 descriptor, but zero out DirPort until it's found reachable.
5404 - When building testing circs for ORPort testing, use only
5405 high-bandwidth nodes, so fewer circuits fail.
5406 - Complain about unreachable ORPort separately from unreachable
5407 DirPort, so the user knows what's going on.
5408 - Make sure we only conclude ORPort reachability if we didn't
5409 initiate the conn. Otherwise we could falsely conclude that
5410 we're reachable just because we connected to the guy earlier
5411 and he used that same pipe to extend to us.
5412 - Authdirservers shouldn't do ORPort reachability detection,
5413 since they're in clique mode, so it will be rare to find a
5414 server not already connected to them.
5415 - When building testing circuits, always pick middle hops running
5416 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
5417 bug. (This is a kludge; it will go away when 0.0.9.x becomes
5419 - When we decide we're reachable, actually publish our descriptor
5421 - Fix bug in redirectstream in the controller.
5422 - Fix the state descriptor strings so logs don't claim edge streams
5423 are in a different state than they actually are.
5424 - Use recent libevent features when possible (this only really affects
5425 win32 and osx right now, because the new libevent with these
5426 features hasn't been released yet). Add code to suppress spurious
5428 - Prevent possible segfault in connection_close_unattached_ap().
5429 - Fix newlines on torrc in win32.
5430 - Improve error msgs when tor-resolve fails.
5432 o Improvements on 0.0.9.x:
5433 - New experimental script tor/contrib/ExerciseServer.py (needs more
5434 work) that uses the controller interface to build circuits and
5435 fetch pages over them. This will help us bootstrap servers that
5436 have lots of capacity but haven't noticed it yet.
5437 - New experimental script tor/contrib/PathDemo.py (needs more work)
5438 that uses the controller interface to let you choose whole paths
5440 "<hostname>.<path,separated by dots>.<length of path>.path"
5441 - When we've connected to an OR and handshaked but didn't like
5442 the result, we were closing the conn without sending destroy
5443 cells back for pending circuits. Now send those destroys.
5446 Changes in version 0.0.9.7 - 2005-04-01
5447 o Bugfixes on 0.0.9.x:
5448 - Fix another race crash bug (thanks to Glenn Fink for reporting).
5449 - Compare identity to identity, not to nickname, when extending to
5450 a router not already in the directory. This was preventing us from
5451 extending to unknown routers. Oops.
5452 - Make sure to create OS X Tor user in <500 range, so we aren't
5453 creating actual system users.
5454 - Note where connection-that-hasn't-sent-end was marked, and fix
5455 a few really loud instances of this harmless bug (it's fixed more
5459 Changes in version 0.1.0.1-rc - 2005-03-28
5461 - Add reachability testing. Your Tor server will automatically try
5462 to see if its ORPort and DirPort are reachable from the outside,
5463 and it won't upload its descriptor until it decides they are.
5464 - Handle unavailable hidden services better. Handle slow or busy
5465 hidden services better.
5466 - Add support for CONNECTing through https proxies, with "HttpsProxy"
5468 - New exit policy: accept most low-numbered ports, rather than
5469 rejecting most low-numbered ports.
5470 - More Tor controller support (still experimental). See
5471 http://tor.eff.org/doc/control-spec.txt for all the new features,
5472 including signals to emulate unix signals from any platform;
5473 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
5474 closestream; closecircuit; etc.
5475 - Make nt services work and start on startup on win32 (based on
5476 patch by Matt Edman).
5477 - Add a new AddressMap config directive to rewrite incoming socks
5478 addresses. This lets you, for example, declare an implicit
5479 required exit node for certain sites.
5480 - Add a new TrackHostExits config directive to trigger addressmaps
5481 for certain incoming socks addresses -- for sites that break when
5482 your exit keeps changing (based on patch by Mike Perry).
5483 - Redo the client-side dns cache so it's just an addressmap too.
5484 - Notice when our IP changes, and reset stats/uptime/reachability.
5485 - When an application is using socks5, give him the whole variety of
5486 potential socks5 responses (connect refused, host unreachable, etc),
5487 rather than just "success" or "failure".
5488 - A more sane version numbering system. See
5489 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
5490 - New contributed script "exitlist": a simple python script to
5491 parse directories and find Tor nodes that exit to listed
5493 - New contributed script "privoxy-tor-toggle" to toggle whether
5494 Privoxy uses Tor. Seems to be configured for Debian by default.
5495 - Report HTTP reasons to client when getting a response from directory
5496 servers -- so you can actually know what went wrong.
5497 - New config option MaxAdvertisedBandwidth which lets you advertise
5498 a low bandwidthrate (to not attract as many circuits) while still
5499 allowing a higher bandwidthrate in reality.
5501 o Robustness/stability fixes:
5502 - Make Tor use Niels Provos's libevent instead of its current
5503 poll-but-sometimes-select mess. This will let us use faster async
5504 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
5506 - pthread support now too. This was forced because when we forked,
5507 we ended up wasting a lot of duplicate ram over time. Also switch
5508 to foo_r versions of some library calls to allow reentry and
5510 - Better handling for heterogeneous / unreliable nodes:
5511 - Annotate circuits w/ whether they aim to contain high uptime nodes
5512 and/or high capacity nodes. When building circuits, choose
5514 - This means that every single node in an intro rend circuit,
5515 not just the last one, will have a minimum uptime.
5516 - New config option LongLivedPorts to indicate application streams
5517 that will want high uptime circuits.
5518 - Servers reset uptime when a dir fetch entirely fails. This
5519 hopefully reflects stability of the server's network connectivity.
5520 - If somebody starts his tor server in Jan 2004 and then fixes his
5521 clock, don't make his published uptime be a year.
5522 - Reset published uptime when you wake up from hibernation.
5523 - Introduce a notion of 'internal' circs, which are chosen without
5524 regard to the exit policy of the last hop. Intro and rendezvous
5525 circs must be internal circs, to avoid leaking information. Resolve
5526 and connect streams can use internal circs if they want.
5527 - New circuit pooling algorithm: make sure to have enough circs around
5528 to satisfy any predicted ports, and also make sure to have 2 internal
5529 circs around if we've required internal circs lately (and with high
5530 uptime if we've seen that lately too).
5531 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
5532 which describes how often we retry making new circuits if current
5533 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
5534 how long we're willing to make use of an already-dirty circuit.
5535 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
5536 circ as necessary, if there are any completed ones lying around
5537 when we try to launch one.
5538 - Make hidden services try to establish a rendezvous for 30 seconds,
5539 rather than for n (where n=3) attempts to build a circuit.
5540 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
5541 "ShutdownWaitLength".
5542 - Try to be more zealous about calling connection_edge_end when
5543 things go bad with edge conns in connection.c.
5544 - Revise tor-spec to add more/better stream end reasons.
5545 - Revise all calls to connection_edge_end to avoid sending "misc",
5546 and to take errno into account where possible.
5549 - Fix a race condition that can trigger an assert, when we have a
5550 pending create cell and an OR connection fails right then.
5551 - Fix several double-mark-for-close bugs, e.g. where we were finding
5552 a conn for a cell even if that conn is already marked for close.
5553 - Make sequence of log messages when starting on win32 with no config
5554 file more reasonable.
5555 - When choosing an exit node for a new non-internal circ, don't take
5556 into account whether it'll be useful for any pending x.onion
5557 addresses -- it won't.
5558 - Turn addr_policy_compare from a tristate to a quadstate; this should
5559 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
5560 for google.com" problem.
5561 - Make "platform" string in descriptor more accurate for Win32 servers,
5562 so it's not just "unknown platform".
5563 - Fix an edge case in parsing config options (thanks weasel).
5564 If they say "--" on the commandline, it's not an option.
5565 - Reject odd-looking addresses at the client (e.g. addresses that
5566 contain a colon), rather than having the server drop them because
5568 - tor-resolve requests were ignoring .exit if there was a working circuit
5569 they could use instead.
5570 - REUSEADDR on normal platforms means you can rebind to the port
5571 right after somebody else has let it go. But REUSEADDR on win32
5572 means to let you bind to the port _even when somebody else
5573 already has it bound_! So, don't do that on Win32.
5574 - Change version parsing logic: a version is "obsolete" if it is not
5575 recommended and (1) there is a newer recommended version in the
5576 same series, or (2) there are no recommended versions in the same
5577 series, but there are some recommended versions in a newer series.
5578 A version is "new" if it is newer than any recommended version in
5580 - Stop most cases of hanging up on a socks connection without sending
5584 - Require BandwidthRate to be at least 20kB/s for servers.
5585 - When a dirserver causes you to give a warn, mention which dirserver
5587 - New config option DirAllowPrivateAddresses for authdirservers.
5588 Now by default they refuse router descriptors that have non-IP or
5589 private-IP addresses.
5590 - Stop publishing socksport in the directory, since it's not
5591 actually meant to be public. For compatibility, publish a 0 there
5593 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
5594 smart" value, that is low for servers and high for clients.
5595 - If our clock jumps forward by 100 seconds or more, assume something
5596 has gone wrong with our network and abandon all not-yet-used circs.
5597 - Warn when exit policy implicitly allows local addresses.
5598 - If we get an incredibly skewed timestamp from a dirserver mirror
5599 that isn't a verified OR, don't warn -- it's probably him that's
5601 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
5602 cookies to disk and doesn't log each web request to disk. (Thanks
5603 to Brett Carrington for pointing this out.)
5604 - When a client asks us for a dir mirror and we don't have one,
5605 launch an attempt to get a fresh one.
5606 - If we're hibernating and we get a SIGINT, exit immediately.
5607 - Add --with-dmalloc ./configure option, to track memory leaks.
5608 - And try to free all memory on closing, so we can detect what
5610 - Cache local dns resolves correctly even when they're .exit
5612 - Give a better warning when some other server advertises an
5613 ORPort that is actually an apache running ssl.
5614 - Add "opt hibernating 1" to server descriptor to make it clearer
5615 whether the server is hibernating.
5618 Changes in version 0.0.9.6 - 2005-03-24
5619 o Bugfixes on 0.0.9.x (crashes and asserts):
5620 - Add new end stream reasons to maintainance branch. Fix bug where
5621 reason (8) could trigger an assert. Prevent bug from recurring.
5622 - Apparently win32 stat wants paths to not end with a slash.
5623 - Fix assert triggers in assert_cpath_layer_ok(), where we were
5624 blowing away the circuit that conn->cpath_layer points to, then
5625 checking to see if the circ is well-formed. Backport check to make
5626 sure we dont use the cpath on a closed connection.
5627 - Prevent circuit_resume_edge_reading_helper() from trying to package
5628 inbufs for marked-for-close streams.
5629 - Don't crash on hup if your options->address has become unresolvable.
5630 - Some systems (like OS X) sometimes accept() a connection and tell
5631 you the remote host is 0.0.0.0:0. If this happens, due to some
5632 other mis-features, we get confused; so refuse the conn for now.
5634 o Bugfixes on 0.0.9.x (other):
5635 - Fix harmless but scary "Unrecognized content encoding" warn message.
5636 - Add new stream error reason: TORPROTOCOL reason means "you are not
5637 speaking a version of Tor I understand; say bye-bye to your stream."
5638 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
5639 into the future, now that we are more tolerant of skew. This
5640 resolves a bug where a Tor server would refuse to cache a directory
5641 because all the directories it gets are too far in the future;
5642 yet the Tor server never logs any complaints about clock skew.
5643 - Mac packaging magic: make man pages useable, and do not overwrite
5644 existing torrc files.
5645 - Make OS X log happily to /var/log/tor/tor.log
5648 Changes in version 0.0.9.5 - 2005-02-22
5649 o Bugfixes on 0.0.9.x:
5650 - Fix an assert race at exit nodes when resolve requests fail.
5651 - Stop picking unverified dir mirrors--it only leads to misery.
5652 - Patch from Matt Edman to make NT services work better. Service
5653 support is still not compiled into the executable by default.
5654 - Patch from Dmitri Bely so the Tor service runs better under
5655 the win32 SYSTEM account.
5656 - Make tor-resolve actually work (?) on Win32.
5657 - Fix a sign bug when getrlimit claims to have 4+ billion
5658 file descriptors available.
5659 - Stop refusing to start when bandwidthburst == bandwidthrate.
5660 - When create cells have been on the onion queue more than five
5661 seconds, just send back a destroy and take them off the list.
5664 Changes in version 0.0.9.4 - 2005-02-03
5665 o Bugfixes on 0.0.9:
5666 - Fix an assert bug that took down most of our servers: when
5667 a server claims to have 1 GB of bandwidthburst, don't
5669 - Don't crash as badly if we have spawned the max allowed number
5670 of dnsworkers, or we're out of file descriptors.
5671 - Block more file-sharing ports in the default exit policy.
5672 - MaxConn is now automatically set to the hard limit of max
5673 file descriptors we're allowed (ulimit -n), minus a few for
5675 - Give a clearer message when servers need to raise their
5676 ulimit -n when they start running out of file descriptors.
5677 - SGI Compatibility patches from Jan Schaumann.
5678 - Tolerate a corrupt cached directory better.
5679 - When a dirserver hasn't approved your server, list which one.
5680 - Go into soft hibernation after 95% of the bandwidth is used,
5681 not 99%. This is especially important for daily hibernators who
5682 have a small accounting max. Hopefully it will result in fewer
5683 cut connections when the hard hibernation starts.
5684 - Load-balance better when using servers that claim more than
5685 800kB/s of capacity.
5686 - Make NT services work (experimental, only used if compiled in).
5689 Changes in version 0.0.9.3 - 2005-01-21
5690 o Bugfixes on 0.0.9:
5691 - Backport the cpu use fixes from main branch, so busy servers won't
5692 need as much processor time.
5693 - Work better when we go offline and then come back, or when we
5694 run Tor at boot before the network is up. We do this by
5695 optimistically trying to fetch a new directory whenever an
5696 application request comes in and we think we're offline -- the
5697 human is hopefully a good measure of when the network is back.
5698 - Backport some minimal hidserv bugfixes: keep rend circuits open as
5699 long as you keep using them; actually publish hidserv descriptors
5700 shortly after they change, rather than waiting 20-40 minutes.
5701 - Enable Mac startup script by default.
5702 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
5703 - When you update AllowUnverifiedNodes or FirewallPorts via the
5704 controller's setconf feature, we were always appending, never
5706 - When you update HiddenServiceDir via setconf, it was screwing up
5707 the order of reading the lines, making it fail.
5708 - Do not rewrite a cached directory back to the cache; otherwise we
5709 will think it is recent and not fetch a newer one on startup.
5710 - Workaround for webservers that lie about Content-Encoding: Tor
5711 now tries to autodetect compressed directories and compression
5712 itself. This lets us Proxypass dir fetches through apache.
5715 Changes in version 0.0.9.2 - 2005-01-04
5716 o Bugfixes on 0.0.9 (crashes and asserts):
5717 - Fix an assert on startup when the disk is full and you're logging
5719 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
5720 style address, then we'd crash.
5721 - Fix an assert trigger when the running-routers string we get from
5722 a dirserver is broken.
5723 - Make worker threads start and run on win32. Now win32 servers
5725 - Bandaid (not actually fix, but now it doesn't crash) an assert
5726 where the dns worker dies mysteriously and the main Tor process
5727 doesn't remember anything about the address it was resolving.
5729 o Bugfixes on 0.0.9 (Win32):
5730 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
5731 name out of the warning/assert messages.
5732 - Fix a superficial "unhandled error on read" bug on win32.
5733 - The win32 installer no longer requires a click-through for our
5734 license, since our Free Software license grants rights but does not
5736 - Win32: When connecting to a dirserver fails, try another one
5737 immediately. (This was already working for non-win32 Tors.)
5738 - Stop trying to parse $HOME on win32 when hunting for default
5740 - Make tor-resolve.c work on win32 by calling network_init().
5742 o Bugfixes on 0.0.9 (other):
5743 - Make 0.0.9.x build on Solaris again.
5744 - Due to a fencepost error, we were blowing away the \n when reporting
5745 confvalue items in the controller. So asking for multiple config
5746 values at once couldn't work.
5747 - When listing circuits that are pending on an opening OR connection,
5748 if we're an OR we were listing circuits that *end* at us as
5749 being pending on every listener, dns/cpu worker, etc. Stop that.
5750 - Dirservers were failing to create 'running-routers' or 'directory'
5751 strings if we had more than some threshold of routers. Fix them so
5752 they can handle any number of routers.
5753 - Fix a superficial "Duplicate mark for close" bug.
5754 - Stop checking for clock skew for OR connections, even for servers.
5755 - Fix a fencepost error that was chopping off the last letter of any
5756 nickname that is the maximum allowed nickname length.
5757 - Update URLs in log messages so they point to the new website.
5758 - Fix a potential problem in mangling server private keys while
5759 writing to disk (not triggered yet, as far as we know).
5760 - Include the licenses for other free software we include in Tor,
5761 now that we're shipping binary distributions more regularly.
5764 Changes in version 0.0.9.1 - 2004-12-15
5765 o Bugfixes on 0.0.9:
5766 - Make hibernation actually work.
5767 - Make HashedControlPassword config option work.
5768 - When we're reporting event circuit status to a controller,
5769 don't use the stream status code.
5772 Changes in version 0.0.9 - 2004-12-12
5774 - Clean up manpage and torrc.sample file.
5775 - Clean up severities and text of log warnings.
5777 - Make servers trigger an assert when they enter hibernation.
5780 Changes in version 0.0.9rc7 - 2004-12-08
5781 o Bugfixes on 0.0.9rc:
5782 - Fix a stack-trashing crash when an exit node begins hibernating.
5783 - Avoid looking at unallocated memory while considering which
5784 ports we need to build circuits to cover.
5785 - Stop a sigpipe: when an 'end' cell races with eof from the app,
5786 we shouldn't hold-open-until-flush if the eof arrived first.
5787 - Fix a bug with init_cookie_authentication() in the controller.
5788 - When recommending new-format log lines, if the upper bound is
5789 LOG_ERR, leave it implicit.
5791 o Bugfixes on 0.0.8.1:
5792 - Fix a whole slew of memory leaks.
5793 - Fix isspace() and friends so they still make Solaris happy
5794 but also so they don't trigger asserts on win32.
5795 - Fix parse_iso_time on platforms without strptime (eg win32).
5796 - win32: tolerate extra "readable" events better.
5797 - win32: when being multithreaded, leave parent fdarray open.
5798 - Make unit tests work on win32.
5801 Changes in version 0.0.9rc6 - 2004-12-06
5802 o Bugfixes on 0.0.9pre:
5803 - Clean up some more integer underflow opportunities (not exploitable
5805 - While hibernating, hup should not regrow our listeners.
5806 - Send an end to the streams we close when we hibernate, rather
5807 than just chopping them off.
5808 - React to eof immediately on non-open edge connections.
5810 o Bugfixes on 0.0.8.1:
5811 - Calculate timeout for waiting for a connected cell from the time
5812 we sent the begin cell, not from the time the stream started. If
5813 it took a long time to establish the circuit, we would time out
5814 right after sending the begin cell.
5815 - Fix router_compare_addr_to_addr_policy: it was not treating a port
5816 of * as always matching, so we were picking reject *:* nodes as
5817 exit nodes too. Oops.
5820 - New circuit building strategy: keep a list of ports that we've
5821 used in the past 6 hours, and always try to have 2 circuits open
5822 or on the way that will handle each such port. Seed us with port
5823 80 so web users won't complain that Tor is "slow to start up".
5824 - Make kill -USR1 dump more useful stats about circuits.
5825 - When warning about retrying or giving up, print the address, so
5826 the user knows which one it's talking about.
5827 - If you haven't used a clean circuit in an hour, throw it away,
5828 just to be on the safe side. (This means after 6 hours a totally
5829 unused Tor client will have no circuits open.)
5832 Changes in version 0.0.9rc5 - 2004-12-01
5833 o Bugfixes on 0.0.8.1:
5834 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
5835 - Let resolve conns retry/expire also, rather than sticking around
5837 - If we are using select, make sure we stay within FD_SETSIZE.
5839 o Bugfixes on 0.0.9pre:
5840 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
5841 but doesn't seem to be currently; thanks to Ilja van Sprundel for
5843 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
5844 instead. Impose minima and maxima for all *Period options; impose
5845 even tighter maxima for fetching if we are a caching dirserver.
5846 Clip rather than rejecting.
5847 - Fetch cached running-routers from servers that serve it (that is,
5848 authdirservers and servers running 0.0.9rc5-cvs or later.)
5851 - Accept *:706 (silc) in default exit policy.
5852 - Implement new versioning format for post 0.1.
5853 - Support "foo.nickname.exit" addresses, to let Alice request the
5854 address "foo" as viewed by exit node "nickname". Based on a patch
5856 - Make tor --version --version dump the cvs Id of every file.
5859 Changes in version 0.0.9rc4 - 2004-11-28
5860 o Bugfixes on 0.0.8.1:
5861 - Make windows sockets actually non-blocking (oops), and handle
5862 win32 socket errors better.
5864 o Bugfixes on 0.0.9rc1:
5865 - Actually catch the -USR2 signal.
5868 Changes in version 0.0.9rc3 - 2004-11-25
5869 o Bugfixes on 0.0.8.1:
5870 - Flush the log file descriptor after we print "Tor opening log file",
5871 so we don't see those messages days later.
5873 o Bugfixes on 0.0.9rc1:
5874 - Make tor-resolve work again.
5875 - Avoid infinite loop in tor-resolve if tor hangs up on it.
5876 - Fix an assert trigger for clients/servers handling resolves.
5879 Changes in version 0.0.9rc2 - 2004-11-24
5880 o Bugfixes on 0.0.9rc1:
5881 - I broke socks5 support while fixing the eof bug.
5882 - Allow unitless bandwidths and intervals; they default to bytes
5884 - New servers don't start out hibernating; they are active until
5885 they run out of bytes, so they have a better estimate of how
5886 long it takes, and so their operators can know they're working.
5889 Changes in version 0.0.9rc1 - 2004-11-23
5890 o Bugfixes on 0.0.8.1:
5891 - Finally fix a bug that's been plaguing us for a year:
5892 With high load, circuit package window was reaching 0. Whenever
5893 we got a circuit-level sendme, we were reading a lot on each
5894 socket, but only writing out a bit. So we would eventually reach
5895 eof. This would be noticed and acted on even when there were still
5896 bytes sitting in the inbuf.
5897 - When poll() is interrupted, we shouldn't believe the revents values.
5899 o Bugfixes on 0.0.9pre6:
5900 - Fix hibernate bug that caused pre6 to be broken.
5901 - Don't keep rephist info for routers that haven't had activity for
5902 24 hours. (This matters now that clients have keys, since we track
5904 - Never call close_temp_logs while validating log options.
5905 - Fix backslash-escaping on tor.sh.in and torctl.in.
5908 - Implement weekly/monthly/daily accounting: now you specify your
5909 hibernation properties by
5910 AccountingMax N bytes|KB|MB|GB|TB
5911 AccountingStart day|week|month [day] HH:MM
5912 Defaults to "month 1 0:00".
5913 - Let bandwidth and interval config options be specified as 5 bytes,
5914 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
5915 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
5916 get back to normal.)
5917 - If your requested entry or exit node has advertised bandwidth 0,
5919 - Be more greedy about filling up relay cells -- we try reading again
5920 once we've processed the stuff we read, in case enough has arrived
5921 to fill the last cell completely.
5922 - Apply NT service patch from Osamu Fujino. Still needs more work.
5925 Changes in version 0.0.9pre6 - 2004-11-15
5926 o Bugfixes on 0.0.8.1:
5927 - Fix assert failure on malformed socks4a requests.
5928 - Use identity comparison, not nickname comparison, to choose which
5929 half of circuit-ID-space each side gets to use. This is needed
5930 because sometimes we think of a router as a nickname, and sometimes
5931 as a hex ID, and we can't predict what the other side will do.
5932 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
5933 write() call will fail and we handle it there.
5934 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
5935 and smartlist_len, which are two major profiling offenders.
5937 o Bugfixes on 0.0.9pre5:
5938 - Fix a bug in read_all that was corrupting config files on windows.
5939 - When we're raising the max number of open file descriptors to
5940 'unlimited', don't log that we just raised it to '-1'.
5941 - Include event code with events, as required by control-spec.txt.
5942 - Don't give a fingerprint when clients do --list-fingerprint:
5943 it's misleading, because it will never be the same again.
5944 - Stop using strlcpy in tor_strndup, since it was slowing us
5946 - Remove warn on startup about missing cached-directory file.
5947 - Make kill -USR1 work again.
5948 - Hibernate if we start tor during the "wait for wakeup-time" phase
5949 of an accounting interval. Log our hibernation plans better.
5950 - Authoritative dirservers now also cache their directory, so they
5951 have it on start-up.
5954 - Fetch running-routers; cache running-routers; compress
5955 running-routers; serve compressed running-routers.z
5956 - Add NSI installer script contributed by J Doe.
5957 - Commit VC6 and VC7 workspace/project files.
5958 - Commit a tor.spec for making RPM files, with help from jbash.
5959 - Add contrib/torctl.in contributed by Glenn Fink.
5960 - Implement the control-spec's SAVECONF command, to write your
5961 configuration to torrc.
5962 - Get cookie authentication for the controller closer to working.
5963 - Include control-spec.txt in the tarball.
5964 - When set_conf changes our server descriptor, upload a new copy.
5965 But don't upload it too often if there are frequent changes.
5966 - Document authentication config in man page, and document signals
5968 - Clean up confusing parts of man page and torrc.sample.
5969 - Make expand_filename handle ~ and ~username.
5970 - Use autoconf to enable largefile support where necessary. Use
5971 ftello where available, since ftell can fail at 2GB.
5972 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
5973 log more informatively.
5974 - Give a slightly more useful output for "tor -h".
5975 - Refuse application socks connections to port 0.
5976 - Check clock skew for verified servers, but allow unverified
5977 servers and clients to have any clock skew.
5978 - Break DirFetchPostPeriod into:
5979 - DirFetchPeriod for fetching full directory,
5980 - StatusFetchPeriod for fetching running-routers,
5981 - DirPostPeriod for posting server descriptor,
5982 - RendPostPeriod for posting hidden service descriptors.
5983 - Make sure the hidden service descriptors are at a random offset
5984 from each other, to hinder linkability.
5987 Changes in version 0.0.9pre5 - 2004-11-09
5988 o Bugfixes on 0.0.9pre4:
5989 - Fix a seg fault in unit tests (doesn't affect main program).
5990 - Fix an assert bug where a hidden service provider would fail if
5991 the first hop of his rendezvous circuit was down.
5992 - Hidden service operators now correctly handle version 1 style
5993 INTRODUCE1 cells (nobody generates them still, so not a critical
5995 - If do_hup fails, actually notice.
5996 - Handle more errnos from accept() without closing the listener.
5997 Some OpenBSD machines were closing their listeners because
5998 they ran out of file descriptors.
5999 - Send resolve cells to exit routers that are running a new
6000 enough version of the resolve code to work right.
6001 - Better handling of winsock includes on non-MSV win32 compilers.
6002 - Some people had wrapped their tor client/server in a script
6003 that would restart it whenever it died. This did not play well
6004 with our "shut down if your version is obsolete" code. Now people
6005 don't fetch a new directory if their local cached version is
6007 - Make our autogen.sh work on ksh as well as bash.
6010 - Hibernation: New config option "AccountingMaxKB" lets you
6011 set how many KBytes per month you want to allow your server to
6012 consume. Rather than spreading those bytes out evenly over the
6013 month, we instead hibernate for some of the month and pop up
6014 at a deterministic time, work until the bytes are consumed, then
6015 hibernate again. Config option "MonthlyAccountingStart" lets you
6016 specify which day of the month your billing cycle starts on.
6017 - Control interface: a separate program can now talk to your
6018 client/server over a socket, and get/set config options, receive
6019 notifications of circuits and streams starting/finishing/dying,
6020 bandwidth used, etc. The next step is to get some GUIs working.
6021 Let us know if you want to help out. See doc/control-spec.txt .
6022 - Ship a contrib/tor-control.py as an example script to interact
6023 with the control port.
6024 - "tor --hash-password zzyxz" will output a salted password for
6025 use in authenticating to the control interface.
6026 - New log format in config:
6027 "Log minsev[-maxsev] stdout|stderr|syslog" or
6028 "Log minsev[-maxsev] file /var/foo"
6031 - DirPolicy config option, to let people reject incoming addresses
6032 from their dirserver.
6033 - "tor --list-fingerprint" will list your identity key fingerprint
6035 - Add "pass" target for RedirectExit, to make it easier to break
6036 out of a sequence of RedirectExit rules.
6037 - Clients now generate a TLS cert too, in preparation for having
6038 them act more like real nodes.
6039 - Ship src/win32/ in the tarball, so people can use it to build.
6040 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
6042 - New "router-status" line in directory, to better bind each verified
6043 nickname to its identity key.
6044 - Deprecate unofficial config option abbreviations, and abbreviations
6045 not on the command line.
6046 - Add a pure-C tor-resolve implementation.
6047 - Use getrlimit and friends to ensure we can reach MaxConn (currently
6048 1024) file descriptors.
6050 o Code security improvements, inspired by Ilja:
6051 - Replace sprintf with snprintf. (I think they were all safe, but
6053 - Replace strcpy/strncpy with strlcpy in more places.
6054 - Avoid strcat; use snprintf or strlcat instead.
6055 - snprintf wrapper with consistent (though not C99) overflow behavior.
6058 Changes in version 0.0.9pre4 - 2004-10-17
6059 o Bugfixes on 0.0.9pre3:
6060 - If the server doesn't specify an exit policy, use the real default
6061 exit policy, not reject *:*.
6062 - Ignore fascistfirewall when uploading/downloading hidden service
6063 descriptors, since we go through Tor for those; and when using
6064 an HttpProxy, since we assume it can reach them all.
6065 - When looking for an authoritative dirserver, use only the ones
6066 configured at boot. Don't bother looking in the directory.
6067 - The rest of the fix for get_default_conf_file() on older win32.
6068 - Make 'Routerfile' config option obsolete.
6071 - New 'MyFamily nick1,...' config option for a server to
6072 specify other servers that shouldn't be used in the same circuit
6073 with it. Only believed if nick1 also specifies us.
6074 - New 'NodeFamily nick1,nick2,...' config option for a client to
6075 specify nodes that it doesn't want to use in the same circuit.
6076 - New 'Redirectexit pattern address:port' config option for a
6077 server to redirect exit connections, e.g. to a local squid.
6080 Changes in version 0.0.9pre3 - 2004-10-13
6081 o Bugfixes on 0.0.8.1:
6082 - Better torrc example lines for dirbindaddress and orbindaddress.
6083 - Improved bounds checking on parsed ints (e.g. config options and
6084 the ones we find in directories.)
6085 - Better handling of size_t vs int, so we're more robust on 64
6087 - Fix the rest of the bug where a newly started OR would appear
6088 as unverified even after we've added his fingerprint and hupped
6090 - Fix a bug from 0.0.7: when read() failed on a stream, we would
6091 close it without sending back an end. So 'connection refused'
6092 would simply be ignored and the user would get no response.
6094 o Bugfixes on 0.0.9pre2:
6095 - Serving the cached-on-disk directory to people is bad. We now
6096 provide no directory until we've fetched a fresh one.
6097 - Workaround for bug on windows where cached-directories get crlf
6099 - Make get_default_conf_file() work on older windows too.
6100 - If we write a *:* exit policy line in the descriptor, don't write
6101 any more exit policy lines.
6104 - Use only 0.0.9pre1 and later servers for resolve cells.
6105 - Make the dirservers file obsolete.
6106 - Include a dir-signing-key token in directories to tell the
6107 parsing entity which key is being used to sign.
6108 - Remove the built-in bulky default dirservers string.
6109 - New config option "Dirserver %s:%d [fingerprint]", which can be
6110 repeated as many times as needed. If no dirservers specified,
6111 default to moria1,moria2,tor26.
6112 - Make moria2 advertise a dirport of 80, so people behind firewalls
6113 will be able to get a directory.
6114 - Http proxy support
6115 - Dirservers translate requests for http://%s:%d/x to /x
6116 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
6117 be routed through this host.
6118 - Clients ask for /tor/x rather than /x for new enough dirservers.
6119 This way we can one day coexist peacefully with apache.
6120 - Clients specify a "Host: %s%d" http header, to be compatible
6121 with more proxies, and so running squid on an exit node can work.
6124 Changes in version 0.0.8.1 - 2004-10-13
6126 - Fix a seg fault that can be triggered remotely for Tor
6127 clients/servers with an open dirport.
6128 - Fix a rare assert trigger, where routerinfos for entries in
6129 our cpath would expire while we're building the path.
6130 - Fix a bug in OutboundBindAddress so it (hopefully) works.
6131 - Fix a rare seg fault for people running hidden services on
6132 intermittent connections.
6133 - Fix a bug in parsing opt keywords with objects.
6134 - Fix a stale pointer assert bug when a stream detaches and
6136 - Fix a string format vulnerability (probably not exploitable)
6137 in reporting stats locally.
6138 - Fix an assert trigger: sometimes launching circuits can fail
6139 immediately, e.g. because too many circuits have failed recently.
6140 - Fix a compile warning on 64 bit platforms.
6143 Changes in version 0.0.9pre2 - 2004-10-03
6145 - Make fetching a cached directory work for 64-bit platforms too.
6146 - Make zlib.h a required header, not an optional header.
6149 Changes in version 0.0.9pre1 - 2004-10-01
6151 - Stop using separate defaults for no-config-file and
6152 empty-config-file. Now you have to explicitly turn off SocksPort,
6153 if you don't want it open.
6154 - Fix a bug in OutboundBindAddress so it (hopefully) works.
6155 - Improve man page to mention more of the 0.0.8 features.
6156 - Fix a rare seg fault for people running hidden services on
6157 intermittent connections.
6158 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
6160 - Fix more dns related bugs: send back resolve_failed and end cells
6161 more reliably when the resolve fails, rather than closing the
6162 circuit and then trying to send the cell. Also attach dummy resolve
6163 connections to a circuit *before* calling dns_resolve(), to fix
6164 a bug where cached answers would never be sent in RESOLVED cells.
6165 - When we run out of disk space, or other log writing error, don't
6166 crash. Just stop logging to that log and continue.
6167 - We were starting to daemonize before we opened our logs, so if
6168 there were any problems opening logs, we would complain to stderr,
6169 which wouldn't work, and then mysteriously exit.
6170 - Fix a rare bug where sometimes a verified OR would connect to us
6171 before he'd uploaded his descriptor, which would cause us to
6172 assign conn->nickname as though he's unverified. Now we look through
6173 the fingerprint list to see if he's there.
6174 - Fix a rare assert trigger, where routerinfos for entries in
6175 our cpath would expire while we're building the path.
6178 - Clients can ask dirservers for /dir.z to get a compressed version
6179 of the directory. Only works for servers running 0.0.9, of course.
6180 - Make clients cache directories and use them to seed their router
6181 lists at startup. This means clients have a datadir again.
6182 - Configuration infrastructure support for warning on obsolete
6184 - Respond to content-encoding headers by trying to uncompress as
6186 - Reply with a deflated directory when a client asks for "dir.z".
6187 We could use allow-encodings instead, but allow-encodings isn't
6188 specified in HTTP 1.0.
6189 - Raise the max dns workers from 50 to 100.
6190 - Discourage people from setting their dirfetchpostperiod more often
6191 than once per minute.
6192 - Protect dirservers from overzealous descriptor uploading -- wait
6193 10 seconds after directory gets dirty, before regenerating.
6196 Changes in version 0.0.8 - 2004-08-25
6197 o Port it to SunOS 5.9 / Athena
6200 Changes in version 0.0.8rc2 - 2004-08-20
6201 o Make it compile on cygwin again.
6202 o When picking unverified routers, skip those with low uptime and/or
6203 low bandwidth, depending on what properties you care about.
6206 Changes in version 0.0.8rc1 - 2004-08-18
6207 o Changes from 0.0.7.3:
6209 - Fix assert triggers: if the other side returns an address 0.0.0.0,
6210 don't put it into the client dns cache.
6211 - If a begin failed due to exit policy, but we believe the IP address
6212 should have been allowed, switch that router to exitpolicy reject *:*
6213 until we get our next directory.
6215 - Clients choose nodes proportional to advertised bandwidth.
6216 - Avoid using nodes with low uptime as introduction points.
6217 - Handle servers with dynamic IP addresses: don't replace
6218 options->Address with the resolved one at startup, and
6219 detect our address right before we make a routerinfo each time.
6220 - 'FascistFirewall' option to pick dirservers and ORs on specific
6221 ports; plus 'FirewallPorts' config option to tell FascistFirewall
6222 which ports are open. (Defaults to 80,443)
6223 - Be more aggressive about trying to make circuits when the network
6224 has changed (e.g. when you unsuspend your laptop).
6225 - Check for time skew on http headers; report date in response to
6227 - If the entrynode config line has only one node, don't pick it as
6229 - Add strict{entry|exit}nodes config options. If set to 1, then
6230 we refuse to build circuits that don't include the specified entry
6232 - OutboundBindAddress config option, to bind to a specific
6233 IP address for outgoing connect()s.
6234 - End truncated log entries (e.g. directories) with "[truncated]".
6236 o Patches to 0.0.8preX:
6238 - Patches to compile and run on win32 again (maybe)?
6239 - Fix crash when looking for ~/.torrc with no $HOME set.
6240 - Fix a race bug in the unit tests.
6241 - Handle verified/unverified name collisions better when new
6242 routerinfo's arrive in a directory.
6243 - Sometimes routers were getting entered into the stats before
6244 we'd assigned their identity_digest. Oops.
6245 - Only pick and establish intro points after we've gotten a
6248 - AllowUnverifiedNodes config option to let circuits choose no-name
6249 routers in entry,middle,exit,introduction,rendezvous positions.
6250 Allow middle and rendezvous positions by default.
6251 - Add a man page for tor-resolve.
6254 Changes in version 0.0.7.3 - 2004-08-12
6255 o Stop dnsworkers from triggering an assert failure when you
6256 ask them to resolve the host "".
6259 Changes in version 0.0.8pre3 - 2004-08-09
6260 o Changes from 0.0.7.2:
6261 - Allow multiple ORs with same nickname in routerlist -- now when
6262 people give us one identity key for a nickname, then later
6263 another, we don't constantly complain until the first expires.
6264 - Remember used bandwidth (both in and out), and publish 15-minute
6265 snapshots for the past day into our descriptor.
6266 - You can now fetch $DIRURL/running-routers to get just the
6267 running-routers line, not the whole descriptor list. (But
6268 clients don't use this yet.)
6269 - When people mistakenly use Tor as an http proxy, point them
6270 at the tor-doc.html rather than the INSTALL.
6271 - Remove our mostly unused -- and broken -- hex_encode()
6272 function. Use base16_encode() instead. (Thanks to Timo Lindfors
6273 for pointing out this bug.)
6274 - Rotate onion keys every 12 hours, not every 2 hours, so we have
6275 fewer problems with people using the wrong key.
6276 - Change the default exit policy to reject the default edonkey,
6277 kazaa, gnutella ports.
6278 - Add replace_file() to util.[ch] to handle win32's rename().
6280 o Changes from 0.0.8preX:
6281 - Fix two bugs in saving onion keys to disk when rotating, so
6282 hopefully we'll get fewer people using old onion keys.
6283 - Fix an assert error that was making SocksPolicy not work.
6284 - Be willing to expire routers that have an open dirport -- it's
6285 just the authoritative dirservers we want to not forget.
6286 - Reject tor-resolve requests for .onion addresses early, so we
6287 don't build a whole rendezvous circuit and then fail.
6288 - When you're warning a server that he's unverified, don't cry
6290 - Fix a race condition: don't try to extend onto a connection
6291 that's still handshaking.
6292 - For servers in clique mode, require the conn to be open before
6293 you'll choose it for your path.
6294 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
6295 end relay cell, etc.
6296 - Measure bandwidth capacity over the last 24 hours, not just 12
6297 - Bugfix: authoritative dirservers were making and signing a new
6298 directory for each client, rather than reusing the cached one.
6301 Changes in version 0.0.8pre2 - 2004-08-04
6302 o Changes from 0.0.7.2:
6304 - Check directory signature _before_ you decide whether you're
6305 you're running an obsolete version and should exit.
6306 - Check directory signature _before_ you parse the running-routers
6307 list to decide who's running or verified.
6308 - Bugfixes and features:
6309 - Check return value of fclose while writing to disk, so we don't
6310 end up with broken files when servers run out of disk space.
6311 - Log a warning if the user uses an unsafe socks variant, so people
6312 are more likely to learn about privoxy or socat.
6313 - Dirservers now include RFC1123-style dates in the HTTP headers,
6314 which one day we will use to better detect clock skew.
6316 o Changes from 0.0.8pre1:
6317 - Make it compile without warnings again on win32.
6318 - Log a warning if you're running an unverified server, to let you
6319 know you might want to get it verified.
6320 - Only pick a default nickname if you plan to be a server.
6323 Changes in version 0.0.8pre1 - 2004-07-23
6325 - Made our unit tests compile again on OpenBSD 3.5, and tor
6326 itself compile again on OpenBSD on a sparc64.
6327 - We were neglecting milliseconds when logging on win32, so
6328 everything appeared to happen at the beginning of each second.
6331 - 'Extend' relay cell payloads now include the digest of the
6332 intended next hop's identity key. Now we can verify that we're
6333 extending to the right router, and also extend to routers we
6334 hadn't heard of before.
6337 - Tor nodes can now act as relays (with an advertised ORPort)
6338 without being manually verified by the dirserver operators.
6339 - Uploaded descriptors of unverified routers are now accepted
6340 by the dirservers, and included in the directory.
6341 - Verified routers are listed by nickname in the running-routers
6342 list; unverified routers are listed as "$<fingerprint>".
6343 - We now use hash-of-identity-key in most places rather than
6344 nickname or addr:port, for improved security/flexibility.
6345 - To avoid Sybil attacks, paths still use only verified servers.
6346 But now we have a chance to play around with hybrid approaches.
6347 - Nodes track bandwidth usage to estimate capacity (not used yet).
6348 - ClientOnly option for nodes that never want to become servers.
6349 - Directory caching.
6350 - "AuthoritativeDir 1" option for the official dirservers.
6351 - Now other nodes (clients and servers) will cache the latest
6352 directory they've pulled down.
6353 - They can enable their DirPort to serve it to others.
6354 - Clients will pull down a directory from any node with an open
6355 DirPort, and check the signature/timestamp correctly.
6356 - Authoritative dirservers now fetch directories from other
6357 authdirservers, to stay better synced.
6358 - Running-routers list tells who's down also, along with noting
6359 if they're verified (listed by nickname) or unverified (listed
6361 - Allow dirservers to serve running-router list separately.
6362 This isn't used yet.
6363 - ORs connect-on-demand to other ORs
6364 - If you get an extend cell to an OR you're not connected to,
6365 connect, handshake, and forward the create cell.
6366 - The authoritative dirservers stay connected to everybody,
6367 and everybody stays connected to 0.0.7 servers, but otherwise
6368 clients/servers expire unused connections after 5 minutes.
6369 - When servers get a sigint, they delay 30 seconds (refusing new
6370 connections) then exit. A second sigint causes immediate exit.
6371 - File and name management:
6372 - Look for .torrc if no CONFDIR "torrc" is found.
6373 - If no datadir is defined, then choose, make, and secure ~/.tor
6375 - If torrc not found, exitpolicy reject *:*.
6376 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
6377 - If no nickname is defined, derive default from hostname.
6378 - Rename secret key files, e.g. identity.key -> secret_id_key,
6379 to discourage people from mailing their identity key to tor-ops.
6380 - Refuse to build a circuit before the directory has arrived --
6381 it won't work anyway, since you won't know the right onion keys
6383 - Try other dirservers immediately if the one you try is down. This
6384 should tolerate down dirservers better now.
6385 - Parse tor version numbers so we can do an is-newer-than check
6386 rather than an is-in-the-list check.
6387 - New socks command 'resolve', to let us shim gethostbyname()
6389 - A 'tor_resolve' script to access the socks resolve functionality.
6390 - A new socks-extensions.txt doc file to describe our
6391 interpretation and extensions to the socks protocols.
6392 - Add a ContactInfo option, which gets published in descriptor.
6393 - Publish OR uptime in descriptor (and thus in directory) too.
6394 - Write tor version at the top of each log file
6395 - New docs in the tarball:
6397 - Document that you should proxy your SSL traffic too.
6400 Changes in version 0.0.7.2 - 2004-07-07
6401 o A better fix for the 0.0.0.0 problem, that will hopefully
6402 eliminate the remaining related assertion failures.
6405 Changes in version 0.0.7.1 - 2004-07-04
6406 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
6407 since internally we use 0.0.0.0 to signify "not yet resolved".
6410 Changes in version 0.0.7 - 2004-06-07
6411 o Updated the man page to reflect the new features.
6414 Changes in version 0.0.7rc2 - 2004-06-06
6415 o Changes from 0.0.7rc1:
6416 - Make it build on Win32 again.
6417 o Changes from 0.0.6.2:
6418 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
6422 Changes in version 0.0.7rc1 - 2004-06-02
6424 - On sighup, we were adding another log without removing the first
6425 one. So log messages would get duplicated n times for n sighups.
6426 - Several cases of using a connection after we'd freed it. The
6427 problem was that connections that are pending resolve are in both
6428 the pending_resolve tree, and also the circuit's resolving_streams
6429 list. When you want to remove one, you must remove it from both.
6430 - Fix a double-mark-for-close where an end cell arrived for a
6431 resolving stream, and then the resolve failed.
6432 - Check directory signatures based on name of signer, not on whom
6433 we got the directory from. This will let us cache directories more
6436 - Crank up some of our constants to handle more users.
6439 Changes in version 0.0.7pre1 - 2004-06-02
6440 o Fixes for crashes and other obnoxious bugs:
6441 - Fix an epipe bug: sometimes when directory connections failed
6442 to connect, we would give them a chance to flush before closing
6444 - When we detached from a circuit because of resolvefailed, we
6445 would immediately try the same circuit twice more, and then
6446 give up on the resolve thinking we'd tried three different
6448 - Limit the number of intro circuits we'll attempt to build for a
6449 hidden service per 15-minute period.
6450 - Check recommended-software string *early*, before actually parsing
6451 the directory. Thus we can detect an obsolete version and exit,
6452 even if the new directory format doesn't parse.
6453 o Fixes for security bugs:
6454 - Remember which nodes are dirservers when you startup, and if a
6455 random OR enables his dirport, don't automatically assume he's
6456 a trusted dirserver.
6458 - Directory connections were asking the wrong poll socket to
6459 start writing, and not asking themselves to start writing.
6460 - When we detached from a circuit because we sent a begin but
6461 didn't get a connected, we would use it again the first time;
6462 but after that we would correctly switch to a different one.
6463 - Stop warning when the first onion decrypt attempt fails; they
6464 will sometimes legitimately fail now that we rotate keys.
6465 - Override unaligned-access-ok check when $host_cpu is ia64 or
6466 arm. Apparently they allow it but the kernel whines.
6467 - Dirservers try to reconnect periodically too, in case connections
6469 - Fix some memory leaks in directory servers.
6470 - Allow backslash in Win32 filenames.
6471 - Made Tor build complain-free on FreeBSD, hopefully without
6472 breaking other BSD builds. We'll see.
6474 - Doxygen markup on all functions and global variables.
6475 - Make directory functions update routerlist, not replace it. So
6476 now directory disagreements are not so critical a problem.
6477 - Remove the upper limit on number of descriptors in a dirserver's
6478 directory (not that we were anywhere close).
6479 - Allow multiple logfiles at different severity ranges.
6480 - Allow *BindAddress to specify ":port" rather than setting *Port
6481 separately. Allow multiple instances of each BindAddress config
6482 option, so you can bind to multiple interfaces if you want.
6483 - Allow multiple exit policy lines, which are processed in order.
6484 Now we don't need that huge line with all the commas in it.
6485 - Enable accept/reject policies on SOCKS connections, so you can bind
6486 to 0.0.0.0 but still control who can use your OP.
6489 Changes in version 0.0.6.2 - 2004-05-16
6490 o Our integrity-checking digest was checking only the most recent cell,
6491 not the previous cells like we'd thought.
6492 Thanks to Stefan Mark for finding the flaw!
6495 Changes in version 0.0.6.1 - 2004-05-06
6496 o Fix two bugs in our AES counter-mode implementation (this affected
6497 onion-level stream encryption, but not TLS-level). It turns
6498 out we were doing something much more akin to a 16-character
6499 polyalphabetic cipher. Oops.
6500 Thanks to Stefan Mark for finding the flaw!
6501 o Retire moria3 as a directory server, and add tor26 as a directory
6505 Changes in version 0.0.6 - 2004-05-02
6509 Changes in version 0.0.6rc4 - 2004-05-01
6510 o Update the built-in dirservers list to use the new directory format
6511 o Fix a rare seg fault: if a node offering a hidden service attempts
6512 to build a circuit to Alice's rendezvous point and fails before it
6513 reaches the last hop, it retries with a different circuit, but
6515 o Handle windows socket errors correctly.
6518 Changes in version 0.0.6rc3 - 2004-04-28
6519 o Don't expire non-general excess circuits (if we had enough
6520 circuits open, we were expiring rendezvous circuits -- even
6521 when they had a stream attached. oops.)
6522 o Fetch randomness from /dev/urandom better (not via fopen/fread)
6523 o Better debugging for tls errors
6524 o Some versions of openssl have an SSL_pending function that erroneously
6525 returns bytes when there is a non-application record pending.
6526 o Set Content-Type on the directory and hidserv descriptor.
6527 o Remove IVs from cipher code, since AES-ctr has none.
6528 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
6529 o We were using an array of length zero in a few places.
6530 o win32's gethostbyname can't resolve an IP to an IP.
6531 o win32's close can't close a socket.
6534 Changes in version 0.0.6rc2 - 2004-04-26
6535 o Fix a bug where we were closing tls connections intermittently.
6536 It turns out openssl keeps its errors around -- so if an error
6537 happens, and you don't ask about it, and then another openssl
6538 operation happens and succeeds, and you ask if there was an error,
6539 it tells you about the first error. Fun fun.
6540 o Fix a bug that's been lurking since 27 may 03 (!)
6541 When passing back a destroy cell, we would use the wrong circ id.
6542 'Mostly harmless', but still worth fixing.
6543 o Since we don't support truncateds much, don't bother sending them;
6544 just close the circ.
6545 o check for <machine/limits.h> so we build on NetBSD again (I hope).
6546 o don't crash if a conn that sent a begin has suddenly lost its circuit
6547 (this was quite rare).
6550 Changes in version 0.0.6rc1 - 2004-04-25
6551 o We now rotate link (tls context) keys and onion keys.
6552 o CREATE cells now include oaep padding, so you can tell
6553 if you decrypted them correctly.
6554 o Add bandwidthburst to server descriptor.
6555 o Directories now say which dirserver signed them.
6556 o Use a tor_assert macro that logs failed assertions too.
6559 Changes in version 0.0.6pre5 - 2004-04-18
6560 o changes from 0.0.6pre4:
6561 - make tor build on broken freebsd 5.2 installs
6562 - fix a failed assert when you try an intro point, get a nack, and try
6563 a second one and it works.
6564 - when alice uses a port that the hidden service doesn't accept,
6565 it now sends back an end cell (denied by exit policy). otherwise
6566 alice would just have to wait to time out.
6567 - fix another rare bug: when we had tried all the intro
6568 points for a hidden service, we fetched the descriptor
6569 again, but we left our introcirc thinking it had already
6570 sent an intro, so it kept waiting for a response...
6571 - bugfix: when you sleep your hidden-service laptop, as soon
6572 as it wakes up it tries to upload a service descriptor, but
6573 socketpair fails for some reason (localhost not up yet?).
6574 now we simply give up on that upload, and we'll try again later.
6575 i'd still like to find the bug though.
6576 - if an intro circ waiting for an ack dies before getting one, then
6578 - we were reusing stale service descriptors and refetching usable
6582 Changes in version 0.0.6pre4 - 2004-04-14
6583 o changes from 0.0.6pre3:
6584 - when bob fails to connect to the rendezvous point, and his
6585 circ didn't fail because of the rendezvous point itself, then
6586 he retries a couple of times
6587 - we expire introduction and rendezvous circs more thoroughly
6588 (sometimes they were hanging around forever)
6589 - we expire unattached rendezvous streams that have been around
6590 too long (they were sticking around forever).
6591 - fix a measly fencepost error that was crashing everybody with
6595 Changes in version 0.0.6pre3 - 2004-04-14
6596 o changes from 0.0.6pre2:
6597 - make hup work again
6598 - fix some memory leaks for dirservers
6599 - allow more skew in rendezvous descriptor timestamps, to help
6600 handle people like blanu who don't know what time it is
6601 - normal circs are 3 hops, but some rend/intro circs are 4, if
6602 the initiator doesn't get to choose the last hop
6603 - send acks for introductions, so alice can know whether to try
6605 - bob publishes intro points more correctly
6606 o changes from 0.0.5:
6607 - fix an assert trigger that's been plaguing us since the days
6608 of 0.0.2prexx (thanks weasel!)
6609 - retry stream correctly when we fail to connect because of
6610 exit-policy-reject (should try another) or can't-resolve-address
6611 (also should try another, because dns on random internet servers
6613 - when we hup a dirserver and we've *removed* a server from the
6614 approved-routers list, now we remove that server from the
6615 in-memory directories too
6618 Changes in version 0.0.6pre2 - 2004-04-08
6619 o We fixed our base32 implementation. Now it works on all architectures.
6622 Changes in version 0.0.6pre1 - 2004-04-08
6624 - Hidden services and rendezvous points are implemented. Go to
6625 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
6626 hidden services. (This only works via a socks4a proxy such as
6627 Privoxy, and currently it's quite slow.)
6630 Changes in version 0.0.5 - 2004-03-30
6634 Changes in version 0.0.5rc3 - 2004-03-29
6635 o Install torrc as torrc.sample -- we no longer clobber your
6637 o Re-enable recommendedversion checking (we broke it in rc2, oops)
6638 o Add in a 'notice' log level for things the operator should hear
6639 but that aren't warnings
6642 Changes in version 0.0.5rc2 - 2004-03-29
6643 o Hold socks connection open until reply is flushed (if possible)
6644 o Make exit nodes resolve IPs to IPs immediately, rather than asking
6645 the dns farm to do it.
6646 o Fix c99 aliasing warnings in rephist.c
6647 o Don't include server descriptors that are older than 24 hours in the
6649 o Give socks 'reject' replies their whole 15s to attempt to flush,
6650 rather than seeing the 60s timeout and assuming the flush had failed.
6651 o Clean automake droppings from the cvs repository
6654 Changes in version 0.0.5rc1 - 2004-03-28
6655 o Fix mangled-state bug in directory fetching (was causing sigpipes).
6656 o Only build circuits after we've fetched the directory: clients were
6657 using only the directory servers before they'd fetched a directory.
6658 This also means longer startup time; so it goes.
6659 o Fix an assert trigger where an OP would fail to handshake, and we'd
6660 expect it to have a nickname.
6661 o Work around a tsocks bug: do a socks reject when AP connection dies
6662 early, else tsocks goes into an infinite loop.
6665 Changes in version 0.0.4 - 2004-03-26
6666 o When connecting to a dirserver or OR and the network is down,
6670 Changes in version 0.0.3 - 2004-03-26
6671 o Warn and fail if server chose a nickname with illegal characters
6672 o Port to Solaris and Sparc:
6673 - include missing header fcntl.h
6674 - have autoconf find -lsocket -lnsl automatically
6675 - deal with hardware word alignment
6676 - make uname() work (solaris has a different return convention)
6677 - switch from using signal() to sigaction()
6678 o Preliminary work on reputation system:
6679 - Keep statistics on success/fail of connect attempts; they're published
6680 by kill -USR1 currently.
6681 - Add a RunTesting option to try to learn link state by creating test
6682 circuits, even when SocksPort is off.
6683 - Remove unused open circuits when there are too many.
6686 Changes in version 0.0.2 - 2004-03-19
6687 - Include strlcpy and strlcat for safer string ops
6688 - define INADDR_NONE so we compile (but still not run) on solaris
6691 Changes in version 0.0.2pre27 - 2004-03-14
6693 - Allow internal tor networks (we were rejecting internal IPs,
6694 now we allow them if they're set explicitly).
6695 - And fix a few endian issues.
6698 Changes in version 0.0.2pre26 - 2004-03-14
6700 - If a stream times out after 15s without a connected cell, don't
6701 try that circuit again: try a new one.
6702 - Retry streams at most 4 times. Then give up.
6703 - When a dirserver gets a descriptor from an unknown router, it
6704 logs its fingerprint (so the dirserver operator can choose to
6705 accept it even without mail from the server operator).
6706 - Inform unapproved servers when we reject their descriptors.
6707 - Make tor build on Windows again. It works as a client, who knows
6709 - Clearer instructions in the torrc for how to set up a server.
6710 - Be more efficient about reading fd's when our global token bucket
6711 (used for rate limiting) becomes empty.
6713 - Stop asserting that computers always go forward in time. It's
6715 - When we sent a cell (e.g. destroy) and then marked an OR connection
6716 expired, we might close it before finishing a flush if the other
6717 side isn't reading right then.
6718 - Don't allow dirservers to start if they haven't defined
6720 - We were caching transient dns failures. Oops.
6721 - Prevent servers from publishing an internal IP as their address.
6722 - Address a strcat vulnerability in circuit.c
6725 Changes in version 0.0.2pre25 - 2004-03-04
6727 - Put the OR's IP in its router descriptor, not its fqdn. That way
6728 we'll stop being stalled by gethostbyname for nodes with flaky dns,
6731 - If the user typed in an address that didn't resolve, the server
6735 Changes in version 0.0.2pre24 - 2004-03-03
6737 - Fix an assertion failure in dns.c, where we were trying to dequeue
6738 a pending dns resolve even if it wasn't pending
6739 - Fix a spurious socks5 warning about still trying to write after the
6740 connection is finished.
6741 - Hold certain marked_for_close connections open until they're finished
6742 flushing, rather than losing bytes by closing them too early.
6743 - Correctly report the reason for ending a stream
6744 - Remove some duplicate calls to connection_mark_for_close
6745 - Put switch_id and start_daemon earlier in the boot sequence, so it
6746 will actually try to chdir() to options.DataDirectory
6747 - Make 'make test' exit(1) if a test fails; fix some unit tests
6748 - Make tor fail when you use a config option it doesn't know about,
6749 rather than warn and continue.
6750 - Make --version work
6751 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
6754 Changes in version 0.0.2pre23 - 2004-02-29
6756 - Print a statement when the first circ is finished, so the user
6758 - If a relay cell is unrecognized at the end of the circuit,
6759 send back a destroy. (So attacks to mutate cells are more
6761 - New config option 'excludenodes' to avoid certain nodes for circuits.
6762 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
6763 so you can collect coredumps there.
6765 - Fix a bug in tls flushing where sometimes data got wedged and
6766 didn't flush until more data got sent. Hopefully this bug was
6767 a big factor in the random delays we were seeing.
6768 - Make 'connected' cells include the resolved IP, so the client
6769 dns cache actually gets populated.
6770 - Disallow changing from ORPort=0 to ORPort>0 on hup.
6771 - When we time-out on a stream and detach from the circuit, send an
6772 end cell down it first.
6773 - Only warn about an unknown router (in exitnodes, entrynodes,
6774 excludenodes) after we've fetched a directory.
6777 Changes in version 0.0.2pre22 - 2004-02-26
6779 - Servers publish less revealing uname information in descriptors.
6780 - More memory tracking and assertions, to crash more usefully when
6782 - If the default torrc isn't there, just use some default defaults.
6783 Plus provide an internal dirservers file if they don't have one.
6784 - When the user tries to use Tor as an http proxy, give them an http
6785 501 failure explaining that we're a socks proxy.
6786 - Dump a new router.desc on hup, to help confused people who change
6787 their exit policies and then wonder why router.desc doesn't reflect
6789 - Clean up the generic tor.sh init script that we ship with.
6791 - If the exit stream is pending on the resolve, and a destroy arrives,
6792 then the stream wasn't getting removed from the pending list. I
6793 think this was the one causing recent server crashes.
6794 - Use a more robust poll on OSX 10.3, since their poll is flaky.
6795 - When it couldn't resolve any dirservers, it was useless from then on.
6796 Now it reloads the RouterFile (or default dirservers) if it has no
6798 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
6799 many users don't even *have* a /usr/local/sbin/.
6802 Changes in version 0.0.2pre21 - 2004-02-18
6804 - There's a ChangeLog file that actually reflects the changelog.
6805 - There's a 'torify' wrapper script, with an accompanying
6806 tor-tsocks.conf, that simplifies the process of using tsocks for
6807 tor. It even has a man page.
6808 - The tor binary gets installed to sbin rather than bin now.
6809 - Retry streams where the connected cell hasn't arrived in 15 seconds
6810 - Clean up exit policy handling -- get the default out of the torrc,
6811 so we can update it without forcing each server operator to fix
6813 - Allow imaps and pop3s in default exit policy
6815 - Prevent picking middleman nodes as the last node in the circuit
6818 Changes in version 0.0.2pre20 - 2004-01-30
6820 - We now have a deb package, and it's in debian unstable. Go to
6822 - I've split the TotalBandwidth option into BandwidthRate (how many
6823 bytes per second you want to allow, long-term) and
6824 BandwidthBurst (how many bytes you will allow at once before the cap
6825 kicks in). This better token bucket approach lets you, say, set
6826 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
6827 performance while not exceeding your monthly bandwidth quota.
6828 - Push out a tls record's worth of data once you've got it, rather
6829 than waiting until you've read everything waiting to be read. This
6830 may improve performance by pipelining better. We'll see.
6831 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
6832 from failed circuits (if they haven't been connected yet) and attach
6834 - Expire old streams that haven't managed to connect. Some day we'll
6835 have them reattach to new circuits instead.
6838 - Fix several memory leaks that were causing servers to become bloated
6840 - Fix a few very rare assert triggers. A few more remain.
6841 - Setuid to User _before_ complaining about running as root.
6844 Changes in version 0.0.2pre19 - 2004-01-07
6846 - Fix deadlock condition in dns farm. We were telling a child to die by
6847 closing the parent's file descriptor to him. But newer children were
6848 inheriting the open file descriptor from the parent, and since they
6849 weren't closing it, the socket never closed, so the child never read
6850 eof, so he never knew to exit. Similarly, dns workers were holding
6851 open other sockets, leading to all sorts of chaos.
6852 - New cleaner daemon() code for forking and backgrounding.
6853 - If you log to a file, it now prints an entry at the top of the
6854 logfile so you know it's working.
6855 - The onionskin challenge length was 30 bytes longer than necessary.
6856 - Started to patch up the spec so it's not quite so out of date.
6859 Changes in version 0.0.2pre18 - 2004-01-02
6861 - Fix endian issues with the 'integrity' field in the relay header.
6862 - Fix a potential bug where connections in state
6863 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
6866 Changes in version 0.0.2pre17 - 2003-12-30
6868 - Made --debuglogfile (or any second log file, actually) work.
6869 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
6870 adversary could force us into an infinite loop.
6873 - Each onionskin handshake now includes a hash of the computed key,
6874 to prove the server's identity and help perfect forward secrecy.
6875 - Changed cell size from 256 to 512 bytes (working toward compatibility
6877 - Changed cell length to 2 bytes, and moved it to the relay header.
6878 - Implemented end-to-end integrity checking for the payloads of
6880 - Separated streamid from 'recognized' (otherwise circuits will get
6881 messed up when we try to have streams exit from the middle). We
6882 use the integrity-checking to confirm that a cell is addressed to
6884 - Randomize the initial circid and streamid values, so an adversary who
6885 breaks into a node can't learn how many circuits or streams have
6889 Changes in version 0.0.2pre16 - 2003-12-14
6891 - Fixed a bug that made HUP trigger an assert
6892 - Fixed a bug where a circuit that immediately failed wasn't being
6893 counted as a failed circuit in counting retries.
6896 - Now we close the circuit when we get a truncated cell: otherwise we're
6897 open to an anonymity attack where a bad node in the path truncates
6898 the circuit and then we open streams at him.
6899 - Add port ranges to exit policies
6900 - Add a conservative default exit policy
6901 - Warn if you're running tor as root
6902 - on HUP, retry OR connections and close/rebind listeners
6903 - options.EntryNodes: try these nodes first when picking the first node
6904 - options.ExitNodes: if your best choices happen to include any of
6905 your preferred exit nodes, you choose among just those preferred
6907 - options.ExcludedNodes: nodes that are never picked in path building
6910 Changes in version 0.0.2pre15 - 2003-12-03
6911 o Robustness and bugfixes:
6912 - Sometimes clients would cache incorrect DNS resolves, which would
6913 really screw things up.
6914 - An OP that goes offline would slowly leak all its sockets and stop
6916 - A wide variety of bugfixes in exit node selection, exit policy
6917 handling, and processing pending streams when a new circuit is
6919 - Pick nodes for a path only from those the directory says are up
6920 - Choose randomly from all running dirservers, not always the first one
6921 - Increase allowed http header size for directory fetch.
6922 - Stop writing to stderr (if we're daemonized it will be closed).
6923 - Enable -g always, so cores will be more useful to me.
6924 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
6927 - Wrote a man page. It lists commonly used options.
6930 - Change default loglevel to warn.
6931 - Make PidFile default to null rather than littering in your CWD.
6932 - OnionRouter config option is now obsolete. Instead it just checks
6934 - Moved to a single unified torrc file for both clients and servers.
6937 Changes in version 0.0.2pre14 - 2003-11-29
6938 o Robustness and bugfixes:
6939 - Force the admin to make the DataDirectory himself
6940 - to get ownership/permissions right
6941 - so clients no longer make a DataDirectory and then never use it
6942 - fix bug where a client who was offline for 45 minutes would never
6943 pull down a directory again
6944 - fix (or at least hide really well) the dns assert bug that was
6945 causing server crashes
6946 - warnings and improved robustness wrt clockskew for certs
6947 - use the native daemon(3) to daemonize, when available
6948 - exit if bind() fails
6949 - exit if neither socksport nor orport is defined
6950 - include our own tor_timegm (Win32 doesn't have its own)
6951 - bugfix for win32 with lots of connections
6952 - fix minor bias in PRNG
6953 - make dirserver more robust to corrupt cached directory
6956 - Wrote the design document (woo)
6958 o Circuit building and exit policies:
6959 - Circuits no longer try to use nodes that the directory has told them
6961 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
6962 bitcounts (18.0.0.0/8).
6963 - Make AP connections standby for a circuit if no suitable circuit
6964 exists, rather than failing
6965 - Circuits choose exit node based on addr/port, exit policies, and
6966 which AP connections are standing by
6967 - Bump min pathlen from 2 to 3
6968 - Relay end cells have a payload to describe why the stream ended.
6969 - If the stream failed because of exit policy, try again with a new
6971 - Clients have a dns cache to remember resolved addresses.
6972 - Notice more quickly when we have no working circuits
6975 - APPort is now called SocksPort
6976 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
6978 - RecommendedVersions is now a config variable rather than
6979 hardcoded (for dirservers)
6980 - Reloads config on HUP
6981 - Usage info on -h or --help
6982 - If you set User and Group config vars, it'll setu/gid to them.
6985 Changes in version 0.0.2pre13 - 2003-10-19
6986 o General stability:
6987 - SSL_write no longer fails when it returns WANTWRITE and the number
6988 of bytes in the buf has changed by the next SSL_write call.
6989 - Fix segfault fetching directory when network is down
6990 - Fix a variety of minor memory leaks
6991 - Dirservers reload the fingerprints file on HUP, so I don't have
6992 to take down the network when I approve a new router
6993 - Default server config file has explicit Address line to specify fqdn
6996 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
6997 - Make listener connections not ever alloc bufs
6999 o Autoconf improvements:
7000 - don't clobber an external CFLAGS in ./configure
7001 - Make install now works
7002 - create var/lib/tor on make install
7003 - autocreate a tor.sh initscript to help distribs
7004 - autocreate the torrc and sample-server-torrc with correct paths
7006 o Log files and Daemonizing now work:
7007 - If --DebugLogFile is specified, log to it at -l debug
7008 - If --LogFile is specified, use it instead of commandline
7009 - If --RunAsDaemon is set, tor forks and backgrounds on startup