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