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