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