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