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