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