2 This document summarizes new features and bugfixes in each stable release
3 of Tor. If you want to see more detailed descriptions of the changes in
4 each development snapshot, see the ChangeLog file.
6 Changes in version 0.2.1.24 - 2010-02-21
7 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
11 - Work correctly out-of-the-box with even more vendor-patched versions
12 of OpenSSL. In particular, make it so Debian and OS X don't need
13 customized patches to run/build.
16 Changes in version 0.2.1.23 - 2010-02-13
17 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
18 again on the latest OS X, and updates the location of a directory
21 o Major bugfixes (performance):
22 - We were selecting our guards uniformly at random, and then weighting
23 which of our guards we'd use uniformly at random. This imbalance
24 meant that Tor clients were severely limited on throughput (and
25 probably latency too) by the first hop in their circuit. Now we
26 select guards weighted by currently advertised bandwidth. We also
27 automatically discard guards picked using the old algorithm. Fixes
28 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
31 - Make Tor work again on the latest OS X: when deciding whether to
32 use strange flags to turn TLS renegotiation on, detect the OpenSSL
33 version at run-time, not compile time. We need to do this because
34 Apple doesn't update its dev-tools headers when it updates its
35 libraries in a security patch.
36 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
37 that could happen on 32-bit platforms with 64-bit time_t. Also fix
38 a memory leak when requesting a hidden service descriptor we've
39 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
43 - Refactor resolve_my_address() to not use gethostbyname() anymore.
44 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
47 - Avoid a mad rush at the beginning of each month when each client
48 rotates half of its guards. Instead we spread the rotation out
49 throughout the month, but we still avoid leaving a precise timestamp
50 in the state file about when we first picked the guard. Improves
51 over the behavior introduced in 0.1.2.17.
54 Changes in version 0.2.1.22 - 2010-01-19
55 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
56 authorities -- it would tell you its whole history of bridge descriptors
57 if you make the right directory request. This stable update also
58 rotates two of the seven v3 directory authority keys and locations.
60 o Directory authority changes:
61 - Rotate keys (both v3 identity and relay identity) for moria1
65 - Stop bridge directory authorities from answering dbg-stability.txt
66 directory queries, which would let people fetch a list of all
67 bridge identities they track. Bugfix on 0.2.1.6-alpha.
70 Changes in version 0.2.1.21 - 2009-12-21
71 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
72 library. If you use Tor on Linux / Unix and you're getting SSL
73 renegotiation errors, upgrading should help. We also recommend an
74 upgrade if you're an exit relay.
77 - Work around a security feature in OpenSSL 0.9.8l that prevents our
78 handshake from working unless we explicitly tell OpenSSL that we
79 are using SSL renegotiation safely. We are, of course, but OpenSSL
80 0.9.8l won't work unless we say we are.
81 - Avoid crashing if the client is trying to upload many bytes and the
82 circuit gets torn down at the same time, or if the flip side
83 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
86 - Do not refuse to learn about authority certs and v2 networkstatus
87 documents that are older than the latest consensus. This bug might
88 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
89 Spotted and fixed by xmux.
90 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
91 trigger platform-specific option misparsing case found by Coverity
93 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
94 trigger assert. Fixes bug 1173.
97 Changes in version 0.2.1.20 - 2009-10-15
98 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
99 services at once, prepares for more performance improvements, and
100 fixes a bunch of smaller bugs.
102 The Windows and OS X bundles also include a more recent Vidalia,
103 and switch from Privoxy to Polipo.
105 The OS X installers are now drag and drop. It's best to un-install
106 Tor/Vidalia and then install this new bundle, rather than upgrade. If
107 you want to upgrade, you'll need to update the paths for Tor and Polipo
108 in the Vidalia Settings window.
111 - Send circuit or stream sendme cells when our window has decreased
112 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
113 by Karsten when testing the "reduce circuit window" performance
114 patch. Bugfix on the 54th commit on Tor -- from July 2002,
115 before the release of Tor 0.0.0. This is the new winner of the
117 - Fix a remotely triggerable memory leak when a consensus document
118 contains more than one signature from the same voter. Bugfix on
120 - Avoid segfault in rare cases when finishing an introduction circuit
121 as a client and finding out that we don't have an introduction key
122 for it. Fixes bug 1073. Reported by Aaron Swartz.
125 - Tor now reads the "circwindow" parameter out of the consensus,
126 and uses that value for its circuit package window rather than the
127 default of 1000 cells. Begins the implementation of proposal 168.
129 o New directory authorities:
130 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
132 - Move moria1 and tonga to alternate IP addresses.
135 - Fix a signed/unsigned compile warning in 0.2.1.19.
136 - Fix possible segmentation fault on directory authorities. Bugfix on
138 - Fix an extremely rare infinite recursion bug that could occur if
139 we tried to log a message after shutting down the log subsystem.
140 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
141 - Fix an obscure bug where hidden services on 64-bit big-endian
142 systems might mis-read the timestamp in v3 introduce cells, and
143 refuse to connect back to the client. Discovered by "rotor".
144 Bugfix on 0.2.1.6-alpha.
145 - We were triggering a CLOCK_SKEW controller status event whenever
146 we connect via the v2 connection protocol to any relay that has
147 a wrong clock. Instead, we should only inform the controller when
148 it's a trusted authority that claims our clock is wrong. Bugfix
149 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
150 - We were telling the controller about CHECKING_REACHABILITY and
151 REACHABILITY_FAILED status events whenever we launch a testing
152 circuit or notice that one has failed. Instead, only tell the
153 controller when we want to inform the user of overall success or
154 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
156 - Don't warn when we're using a circuit that ends with a node
157 excluded in ExcludeExitNodes, but the circuit is not used to access
158 the outside world. This should help fix bug 1090. Bugfix on
160 - Work around a small memory leak in some versions of OpenSSL that
161 stopped the memory used by the hostname TLS extension from being
165 - Add a "getinfo status/accepted-server-descriptor" controller
166 command, which is the recommended way for controllers to learn
167 whether our server descriptor has been successfully received by at
168 least on directory authority. Un-recommend good-server-descriptor
169 getinfo and status events until we have a better design for them.
172 Changes in version 0.2.1.19 - 2009-07-28
173 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
177 - Make accessing hidden services on 0.2.1.x work right again.
178 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
179 part of patch provided by "optimist".
182 - When a relay/bridge is writing out its identity key fingerprint to
183 the "fingerprint" file and to its logs, write it without spaces. Now
184 it will look like the fingerprints in our bridges documentation,
185 and confuse fewer users.
188 - Relays no longer publish a new server descriptor if they change
189 their MaxAdvertisedBandwidth config option but it doesn't end up
190 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
191 fixes bug 1026. Patch from Sebastian.
192 - Avoid leaking memory every time we get a create cell but we have
193 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
194 fixes bug 1034. Reported by BarkerJr.
197 Changes in version 0.2.1.18 - 2009-07-24
198 Tor 0.2.1.18 lays the foundations for performance improvements,
199 adds status events to help users diagnose bootstrap problems, adds
200 optional authentication/authorization for hidden services, fixes a
201 variety of potential anonymity problems, and includes a huge pile of
202 other features and bug fixes.
204 o Major features (clients):
205 - Start sending "bootstrap phase" status events to the controller,
206 so it can keep the user informed of progress fetching directory
207 information and establishing circuits. Also inform the controller
208 if we think we're stuck at a particular bootstrap phase. Implements
210 - Clients replace entry guards that were chosen more than a few months
211 ago. This change should significantly improve client performance,
212 especially once more people upgrade, since relays that have been
213 a guard for a long time are currently overloaded.
214 - Network status consensus documents and votes now contain bandwidth
215 information for each relay. Clients use the bandwidth values
216 in the consensus, rather than the bandwidth values in each
217 relay descriptor. This approach opens the door to more accurate
218 bandwidth estimates once the directory authorities start doing
219 active measurements. Implements part of proposal 141.
221 o Major features (relays):
222 - Disable and refactor some debugging checks that forced a linear scan
223 over the whole server-side DNS cache. These accounted for over 50%
224 of CPU time on a relatively busy exit node's gprof profile. Also,
225 disable some debugging checks that appeared in exit node profile
226 data. Found by Jacob.
227 - New DirPortFrontPage option that takes an html file and publishes
228 it as "/" on the DirPort. Now relay operators can provide a
229 disclaimer without needing to set up a separate webserver. There's
230 a sample disclaimer in contrib/tor-exit-notice.html.
232 o Major features (hidden services):
233 - Make it possible to build hidden services that only certain clients
234 are allowed to connect to. This is enforced at several points,
235 so that unauthorized clients are unable to send INTRODUCE cells
236 to the service, or even (depending on the type of authentication)
237 to learn introduction points. This feature raises the bar for
238 certain kinds of active attacks against hidden services. Design
239 and code by Karsten Loesing. Implements proposal 121.
240 - Relays now store and serve v2 hidden service descriptors by default,
241 i.e., the new default value for HidServDirectoryV2 is 1. This is
242 the last step in proposal 114, which aims to make hidden service
243 lookups more reliable.
245 o Major features (path selection):
246 - ExitNodes and Exclude*Nodes config options now allow you to restrict
247 by country code ("{US}") or IP address or address pattern
248 ("255.128.0.0/16"). Patch from Robert Hogan. It still needs some
249 refinement to decide what config options should take priority if
250 you ask to both use a particular node and exclude it.
252 o Major features (misc):
253 - When building a consensus, do not include routers that are down.
254 This cuts down 30% to 40% on consensus size. Implements proposal
256 - New TestingTorNetwork config option to allow adjustment of
257 previously constant values that could slow bootstrapping. Implements
258 proposal 135. Patch from Karsten.
259 - Convert many internal address representations to optionally hold
260 IPv6 addresses. Generate and accept IPv6 addresses in many protocol
261 elements. Make resolver code handle nameservers located at IPv6
263 - More work on making our TLS handshake blend in: modify the list
264 of ciphers advertised by OpenSSL in client mode to even more
265 closely resemble a common web browser. We cheat a little so that
266 we can advertise ciphers that the locally installed OpenSSL doesn't
268 - Use the TLS1 hostname extension to more closely resemble browser
271 o Security fixes (anonymity/entropy):
272 - Never use a connection with a mismatched address to extend a
273 circuit, unless that connection is canonical. A canonical
274 connection is one whose address is authenticated by the router's
275 identity key, either in a NETINFO cell or in a router descriptor.
276 - Implement most of proposal 110: The first K cells to be sent
277 along a circuit are marked as special "early" cells; only K "early"
278 cells will be allowed. Once this code is universal, we can block
279 certain kinds of denial-of-service attack by requiring that EXTEND
280 commands must be sent using an "early" cell.
281 - Resume using OpenSSL's RAND_poll() for better (and more portable)
282 cross-platform entropy collection again. We used to use it, then
283 stopped using it because of a bug that could crash systems that
284 called RAND_poll when they had a lot of fds open. It looks like the
285 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
286 at startup, and to call RAND_poll() when we reseed later only if
287 we have a non-buggy OpenSSL version.
288 - When the client is choosing entry guards, now it selects at most
289 one guard from a given relay family. Otherwise we could end up with
290 all of our entry points into the network run by the same operator.
291 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
292 - Do not use or believe expired v3 authority certificates. Patch
293 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
294 - Drop begin cells to a hidden service if they come from the middle
295 of a circuit. Patch from lark.
296 - When we erroneously receive two EXTEND cells for the same circuit
297 ID on the same connection, drop the second. Patch from lark.
298 - Authorities now vote for the Stable flag for any router whose
299 weighted MTBF is at least 5 days, regardless of the mean MTBF.
300 - Clients now never report any stream end reason except 'MISC'.
301 Implements proposal 148.
303 o Major bugfixes (crashes):
304 - Parse dates and IPv4 addresses in a locale- and libc-independent
305 manner, to avoid platform-dependent behavior on malformed input.
306 - Fix a crash that occurs on exit nodes when a nameserver request
307 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
308 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
310 - Do not assume that a stack-allocated character array will be
311 64-bit aligned on platforms that demand that uint64_t access is
312 aligned. Possible fix for bug 604.
313 - Resolve a very rare crash bug that could occur when the user forced
314 a nameserver reconfiguration during the middle of a nameserver
315 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
316 - Avoid a "0 divided by 0" calculation when calculating router uptime
317 at directory authorities. Bugfix on 0.2.0.8-alpha.
318 - Fix an assertion bug in parsing policy-related options; possible fix
320 - Rate-limit too-many-sockets messages: when they happen, they happen
321 a lot and end up filling up the disk. Resolves bug 748.
322 - Fix a race condition that could cause crashes or memory corruption
323 when running as a server with a controller listening for log
325 - Avoid crashing when we have a policy specified in a DirPolicy or
326 SocksPolicy or ReachableAddresses option with ports set on it,
327 and we re-load the policy. May fix bug 996.
328 - Fix an assertion failure on 64-bit platforms when we allocated
329 memory right up to the end of a memarea, then realigned the memory
330 one step beyond the end. Fixes a possible cause of bug 930.
331 - Protect the count of open sockets with a mutex, so we can't
332 corrupt it when two threads are closing or opening sockets at once.
333 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
335 o Major bugfixes (clients):
336 - Discard router descriptors as we load them if they are more than
337 five days old. Otherwise if Tor is off for a long time and then
338 starts with cached descriptors, it will try to use the onion keys
339 in those obsolete descriptors when building circuits. Fixes bug 887.
340 - When we choose to abandon a new entry guard because we think our
341 older ones might be better, close any circuits pending on that
342 new entry guard connection. This fix should make us recover much
343 faster when our network is down and then comes back. Bugfix on
344 0.1.2.8-beta; found by lodger.
345 - When Tor clients restart after 1-5 days, they discard all their
346 cached descriptors as too old, but they still use the cached
347 consensus document. This approach is good for robustness, but
348 bad for performance: since they don't know any bandwidths, they
349 end up choosing at random rather than weighting their choice by
350 speed. Fixed by the above feature of putting bandwidths in the
353 o Major bugfixes (relays):
354 - Relays were falling out of the networkstatus consensus for
355 part of a day if they changed their local config but the
356 authorities discarded their new descriptor as "not sufficiently
357 different". Now directory authorities accept a descriptor as changed
358 if BandwidthRate or BandwidthBurst changed. Partial fix for bug 962;
360 - Ensure that two circuits can never exist on the same connection
361 with the same circuit ID, even if one is marked for close. This
362 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
363 - Directory authorities were neglecting to mark relays down in their
364 internal histories if the relays fall off the routerlist without
365 ever being found unreachable. So there were relays in the histories
366 that haven't been seen for eight months, and are listed as being
367 up for eight months. This wreaked havoc on the "median wfu" and
368 "median mtbf" calculations, in turn making Guard and Stable flags
369 wrong, hurting network performance. Fixes bugs 696 and 969. Bugfix
372 o Major bugfixes (hidden services):
373 - When establishing a hidden service, introduction points that
374 originate from cannibalized circuits were completely ignored
375 and not included in rendezvous service descriptors. This might
376 have been another reason for delay in making a hidden service
377 available. Bugfix from long ago (0.0.9.x?)
379 o Major bugfixes (memory and resource management):
380 - Fixed some memory leaks -- some quite frequent, some almost
381 impossible to trigger -- based on results from Coverity.
382 - Speed up parsing and cut down on memory fragmentation by using
383 stack-style allocations for parsing directory objects. Previously,
384 this accounted for over 40% of allocations from within Tor's code
385 on a typical directory cache.
386 - Use a Bloom filter rather than a digest-based set to track which
387 descriptors we need to keep around when we're cleaning out old
388 router descriptors. This speeds up the computation significantly,
389 and may reduce fragmentation.
391 o New/changed config options:
392 - Now NodeFamily and MyFamily config options allow spaces in
393 identity fingerprints, so it's easier to paste them in.
394 Suggested by Lucky Green.
395 - Allow ports 465 and 587 in the default exit policy again. We had
396 rejected them in 0.1.0.15, because back in 2005 they were commonly
397 misconfigured and ended up as spam targets. We hear they are better
398 locked down these days.
399 - Make TrackHostExit mappings expire a while after their last use, not
400 after their creation. Patch from Robert Hogan.
401 - Add an ExcludeExitNodes option so users can list a set of nodes
402 that should be be excluded from the exit node position, but
403 allowed elsewhere. Implements proposal 151.
404 - New --hush command-line option similar to --quiet. While --quiet
405 disables all logging to the console on startup, --hush limits the
406 output to messages of warning and error severity.
407 - New configure/torrc options (--enable-geoip-stats,
408 DirRecordUsageByCountry) to record how many IPs we've served
409 directory info to in each country code, how many status documents
410 total we've sent to each country code, and what share of the total
411 directory requests we should expect to see.
412 - Make outbound DNS packets respect the OutboundBindAddress setting.
413 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
414 - Allow separate log levels to be configured for different logging
415 domains. For example, this allows one to log all notices, warnings,
416 or errors, plus all memory management messages of level debug or
417 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
418 - Update to the "June 3 2009" ip-to-country file.
420 o Minor features (relays):
421 - Raise the minimum rate limiting to be a relay from 20000 bytes
422 to 20480 bytes (aka 20KB/s), to match our documentation. Also
423 update directory authorities so they always assign the Fast flag
424 to relays with 20KB/s of capacity. Now people running relays won't
425 suddenly find themselves not seeing any use, if the network gets
427 - If we're a relay and we change our IP address, be more verbose
428 about the reason that made us change. Should help track down
429 further bugs for relays on dynamic IP addresses.
430 - Exit servers can now answer resolve requests for ip6.arpa addresses.
431 - Implement most of Proposal 152: allow specialized servers to permit
432 single-hop circuits, and clients to use those servers to build
433 single-hop circuits when using a specialized controller. Patch
434 from Josh Albrecht. Resolves feature request 768.
435 - When relays do their initial bandwidth measurement, don't limit
436 to just our entry guards for the test circuits. Otherwise we tend
437 to have multiple test circuits going through a single entry guard,
438 which makes our bandwidth test less accurate. Fixes part of bug 654;
439 patch contributed by Josh Albrecht.
441 o Minor features (directory authorities):
442 - Try not to open more than one descriptor-downloading connection
443 to an authority at once. This should reduce load on directory
444 authorities. Fixes bug 366.
445 - Add cross-certification to newly generated certificates, so that
446 a signing key is enough information to look up a certificate. Start
447 serving certificates by <identity digest, signing key digest>
448 pairs. Implements proposal 157.
449 - When a directory authority downloads a descriptor that it then
450 immediately rejects, do not retry downloading it right away. Should
451 save some bandwidth on authorities. Fix for bug 888. Patch by
453 - Directory authorities now serve a /tor/dbg-stability.txt URL to
454 help debug WFU and MTBF calculations.
455 - In directory authorities' approved-routers files, allow
456 fingerprints with or without space.
458 o Minor features (directory mirrors):
459 - When a download gets us zero good descriptors, do not notify
460 Tor that new directory information has arrived.
461 - Servers support a new URL scheme for consensus downloads that
462 allows the client to specify which authorities are trusted.
463 The server then only sends the consensus if the client will trust
464 it. Otherwise a 404 error is sent back. Clients use this
465 new scheme when the server supports it (meaning it's running
466 0.2.1.1-alpha or later). Implements proposal 134.
468 o Minor features (bridges):
469 - If the bridge config line doesn't specify a port, assume 443.
470 This makes bridge lines a bit smaller and easier for users to
472 - If we're using bridges and our network goes away, be more willing
473 to forgive our bridges and try again when we get an application
476 o Minor features (hidden services):
477 - When the client launches an introduction circuit, retry with a
478 new circuit after 30 seconds rather than 60 seconds.
479 - Launch a second client-side introduction circuit in parallel
480 after a delay of 15 seconds (based on work by Christian Wilms).
481 - Hidden services start out building five intro circuits rather
482 than three, and when the first three finish they publish a service
483 descriptor using those. Now we publish our service descriptor much
484 faster after restart.
485 - Drop the requirement to have an open dir port for storing and
486 serving v2 hidden service descriptors.
488 o Minor features (build and packaging):
489 - On Linux, use the prctl call to re-enable core dumps when the User
491 - Try to make sure that the version of Libevent we're running with
492 is binary-compatible with the one we built with. May address bug
494 - Add a new --enable-local-appdata configuration switch to change
495 the default location of the datadir on win32 from APPDATA to
496 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
497 entirely. Patch from coderman.
498 - Build correctly against versions of OpenSSL 0.9.8 or later that
499 are built without support for deprecated functions.
500 - On platforms with a maximum syslog string length, truncate syslog
501 messages to that length ourselves, rather than relying on the
502 system to do it for us.
503 - Automatically detect MacOSX versions earlier than 10.4.0, and
504 disable kqueue from inside Tor when running with these versions.
505 We previously did this from the startup script, but that was no
506 help to people who didn't use the startup script. Resolves bug 863.
507 - Build correctly when configured to build outside the main source
508 path. Patch from Michael Gold.
509 - Disable GCC's strict alias optimization by default, to avoid the
510 likelihood of its introducing subtle bugs whenever our code violates
511 the letter of C99's alias rules.
512 - Change the contrib/tor.logrotate script so it makes the new
513 logs as "_tor:_tor" rather than the default, which is generally
514 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
515 - Change our header file guard macros to be less likely to conflict
516 with system headers. Adam Langley noticed that we were conflicting
517 with log.h on Android.
518 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
519 and stop using a warning that had become unfixably verbose under
521 - Use a lockfile to make sure that two Tor processes are not
522 simultaneously running with the same datadir.
523 - Allow OpenSSL to use dynamic locks if it wants.
524 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
526 o Minor features (controllers):
527 - When generating circuit events with verbose nicknames for
528 controllers, try harder to look up nicknames for routers on a
529 circuit. (Previously, we would look in the router descriptors we had
530 for nicknames, but not in the consensus.) Partial fix for bug 941.
531 - New controller event NEWCONSENSUS that lists the networkstatus
532 lines for every recommended relay. Now controllers like Torflow
533 can keep up-to-date on which relays they should be using.
534 - New controller event "clients_seen" to report a geoip-based summary
535 of which countries we've seen clients from recently. Now controllers
536 like Vidalia can show bridge operators that they're actually making
538 - Add a 'getinfo status/clients-seen' controller command, in case
539 controllers want to hear clients_seen events but connect late.
540 - New CONSENSUS_ARRIVED event to note when a new consensus has
541 been fetched and validated.
542 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
543 controllers to prevent SIGHUP from reloading the configuration.
545 - Return circuit purposes in response to GETINFO circuit-status.
547 - Serve the latest v3 networkstatus consensus via the control
548 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
549 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
550 controller can query our current bootstrap state in case it attaches
551 partway through and wants to catch up.
552 - Provide circuit purposes along with circuit events to the controller.
554 o Minor features (tools):
555 - Do not have tor-resolve automatically refuse all .onion addresses;
556 if AutomapHostsOnResolve is set in your torrc, this will work fine.
557 - Add a -p option to tor-resolve for specifying the SOCKS port: some
558 people find host:port too confusing.
559 - Print the SOCKS5 error message string as well as the error code
560 when a tor-resolve request fails. Patch from Jacob.
562 o Minor bugfixes (memory and resource management):
563 - Clients no longer cache certificates for authorities they do not
564 recognize. Bugfix on 0.2.0.9-alpha.
565 - Do not use C's stdio library for writing to log files. This will
566 improve logging performance by a minute amount, and will stop
567 leaking fds when our disk is full. Fixes bug 861.
568 - Stop erroneous use of O_APPEND in cases where we did not in fact
569 want to re-seek to the end of a file before every last write().
570 - Fix a small alignment and memory-wasting bug on buffer chunks.
572 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
573 to avoid unused RAM in buffer chunks and memory pools.
574 - Reduce the default smartlist size from 32 to 16; it turns out that
575 most smartlists hold around 8-12 elements tops.
576 - Make dumpstats() log the fullness and size of openssl-internal
578 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
579 patch to their OpenSSL, turn it on to save memory on servers. This
580 patch will (with any luck) get included in a mainline distribution
582 - Fix a memory leak when v3 directory authorities load their keys
583 and cert from disk. Bugfix on 0.2.0.1-alpha.
584 - Stop using malloc_usable_size() to use more area than we had
585 actually allocated: it was safe, but made valgrind really unhappy.
586 - Make the assert_circuit_ok() function work correctly on circuits that
587 have already been marked for close.
588 - Fix uninitialized size field for memory area allocation: may improve
589 memory performance during directory parsing.
591 o Minor bugfixes (clients):
592 - Stop reloading the router list from disk for no reason when we
593 run out of reachable directory mirrors. Once upon a time reloading
594 it would set the 'is_running' flag back to 1 for them. It hasn't
595 done that for a long time.
596 - When we had picked an exit node for a connection, but marked it as
597 "optional", and it turned out we had no onion key for the exit,
598 stop wanting that exit and try again. This situation may not
599 be possible now, but will probably become feasible with proposal
600 158. Spotted by rovv. Fixes another case of bug 752.
601 - Fix a bug in address parsing that was preventing bridges or hidden
602 service targets from being at IPv6 addresses.
603 - Do not remove routers as too old if we do not have any consensus
604 document. Bugfix on 0.2.0.7-alpha.
605 - When an exit relay resolves a stream address to a local IP address,
606 do not just keep retrying that same exit relay over and
607 over. Instead, just close the stream. Addresses bug 872. Bugfix
608 on 0.2.0.32. Patch from rovv.
609 - Made Tor a little less aggressive about deleting expired
610 certificates. Partial fix for bug 854.
611 - Treat duplicate certificate fetches as failures, so that we do
612 not try to re-fetch an expired certificate over and over and over.
613 - Do not say we're fetching a certificate when we'll in fact skip it
614 because of a pending download.
615 - If we have correct permissions on $datadir, we complain to stdout
616 and fail to start. But dangerous permissions on
617 $datadir/cached-status/ would cause us to open a log and complain
618 there. Now complain to stdout and fail to start in both cases. Fixes
619 bug 820, reported by seeess.
621 o Minor bugfixes (bridges):
622 - When we made bridge authorities stop serving bridge descriptors over
623 unencrypted links, we also broke DirPort reachability testing for
624 bridges. So bridges with a non-zero DirPort were printing spurious
625 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
626 - Don't allow a bridge to publish its router descriptor to a
627 non-bridge directory authority. Fixes part of bug 932.
628 - When we change to or from being a bridge, reset our counts of
629 client usage by country. Fixes bug 932.
631 o Minor bugfixes (relays):
632 - Log correct error messages for DNS-related network errors on
634 - Actually return -1 in the error case for read_bandwidth_usage().
635 Harmless bug, since we currently don't care about the return value
636 anywhere. Bugfix on 0.2.0.9-alpha.
637 - Provide a more useful log message if bug 977 (related to buffer
638 freelists) ever reappears, and do not crash right away.
639 - We were already rejecting relay begin cells with destination port
640 of 0. Now also reject extend cells with destination port or address
641 of 0. Suggested by lark.
642 - When we can't transmit a DNS request due to a network error, retry
643 it after a while, and eventually transmit a failing response to
644 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
645 - Solve a bug that kept hardware crypto acceleration from getting
646 enabled when accounting was turned on. Fixes bug 907. Bugfix on
648 - When a canonical connection appears later in our internal list
649 than a noncanonical one for a given OR ID, always use the
650 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
652 - Avoid some nasty corner cases in the logic for marking connections
653 as too old or obsolete or noncanonical for circuits. Partial
655 - Fix another interesting corner-case of bug 891 spotted by rovv:
656 Previously, if two hosts had different amounts of clock drift, and
657 one of them created a new connection with just the wrong timing,
658 the other might decide to deprecate the new connection erroneously.
659 Bugfix on 0.1.1.13-alpha.
660 - If one win32 nameserver fails to get added, continue adding the
661 rest, and don't automatically fail.
662 - Fix a bug where an unreachable relay would establish enough
663 reachability testing circuits to do a bandwidth test -- if
664 we already have a connection to the middle hop of the testing
665 circuit, then it could establish the last hop by using the existing
666 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
667 circuits no longer use entry guards in 0.2.1.3-alpha.
669 o Minor bugfixes (directory authorities):
670 - Limit uploaded directory documents to be 16M rather than 500K.
671 The directory authorities were refusing v3 consensus votes from
672 other authorities, since the votes are now 504K. Fixes bug 959;
673 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
674 - Directory authorities should never send a 503 "busy" response to
675 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
677 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
678 headers. Bugfix on 0.2.0.10-alpha.
680 o Minor bugfixes (hidden services):
681 - When we can't find an intro key for a v2 hidden service descriptor,
682 fall back to the v0 hidden service descriptor and log a bug message.
683 Workaround for bug 1024.
684 - In very rare situations new hidden service descriptors were
685 published earlier than 30 seconds after the last change to the
686 service. (We currently think that a hidden service descriptor
687 that's been stable for 30 seconds is worth publishing.)
688 - If a hidden service sends us an END cell, do not consider
689 retrying the connection; just close it. Patch from rovv.
690 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
691 service directories if they have no advertised dir port. Bugfix
694 o Minor bugfixes (tools):
695 - In the torify(1) manpage, mention that tsocks will leak your
698 o Minor bugfixes (controllers):
699 - If the controller claimed responsibility for a stream, but that
700 stream never finished making its connection, it would live
701 forever in circuit_wait state. Now we close it after SocksTimeout
702 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
703 - Make DNS resolved controller events into "CLOSED", not
704 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
706 - The control port would close the connection before flushing long
707 replies, such as the network consensus, if a QUIT command was issued
708 before the reply had completed. Now, the control port flushes all
709 pending replies before closing the connection. Also fix a spurious
710 warning when a QUIT command is issued after a malformed or rejected
711 AUTHENTICATE command, but before the connection was closed. Patch
712 by Marcus Griep. Fixes bugs 1015 and 1016.
713 - Fix a bug that made stream bandwidth get misreported to the
716 o Deprecated and removed features:
717 - The old "tor --version --version" command, which would print out
718 the subversion "Id" of most of the source files, is now removed. It
719 turned out to be less useful than we'd expected, and harder to
721 - RedirectExits has been removed. It was deprecated since
723 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
724 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
725 - Cell pools are now always enabled; --disable-cell-pools is ignored.
726 - Directory mirrors no longer fetch the v1 directory or
727 running-routers files. They are obsolete, and nobody asks for them
728 anymore. This is the first step to making v1 authorities obsolete.
729 - Take out the TestVia config option, since it was a workaround for
730 a bug that was fixed in Tor 0.1.1.21.
731 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
732 HiddenServiceExcludeNodes as obsolete: they never worked properly,
733 and nobody seems to be using them. Fixes bug 754. Bugfix on
734 0.1.0.1-rc. Patch from Christian Wilms.
735 - Remove all backward-compatibility code for relays running
736 versions of Tor so old that they no longer work at all on the
739 o Code simplifications and refactoring:
740 - Tool-assisted documentation cleanup. Nearly every function or
741 static variable in Tor should have its own documentation now.
742 - Rename the confusing or_is_obsolete field to the more appropriate
743 is_bad_for_new_circs, and move it to or_connection_t where it
745 - Move edge-only flags from connection_t to edge_connection_t: not
746 only is this better coding, but on machines of plausible alignment,
747 it should save 4-8 bytes per connection_t. "Every little bit helps."
748 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
749 for consistency; keep old option working for backward compatibility.
750 - Simplify the code for finding connections to use for a circuit.
751 - Revise the connection_new functions so that a more typesafe variant
752 exists. This will work better with Coverity, and let us find any
753 actual mistakes we're making here.
754 - Refactor unit testing logic so that dmalloc can be used sensibly
755 with unit tests to check for memory leaks.
756 - Move all hidden-service related fields from connection and circuit
757 structure to substructures: this way they won't eat so much memory.
758 - Squeeze 2-5% out of client performance (according to oprofile) by
759 improving the implementation of some policy-manipulation functions.
760 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
761 be more efficient. Formerly it was quadratic in the number of
762 servers; now it should be linear. Fixes bug 509.
763 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
764 and n_conn_id_digest fields into a separate structure that's
765 only needed when the circuit has not yet attached to an n_conn.
766 - Optimize out calls to time(NULL) that occur for every IO operation,
767 or for every cell. On systems like Windows where time() is a
768 slow syscall, this fix will be slightly helpful.
771 Changes in version 0.2.0.35 - 2009-06-24
773 - Avoid crashing in the presence of certain malformed descriptors.
774 Found by lark, and by automated fuzzing.
775 - Fix an edge case where a malicious exit relay could convince a
776 controller that the client's DNS question resolves to an internal IP
777 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
780 - Finally fix the bug where dynamic-IP relays disappear when their
781 IP address changes: directory mirrors were mistakenly telling
782 them their old address if they asked via begin_dir, so they
783 never got an accurate answer about their new address, so they
784 just vanished after a day. For belt-and-suspenders, relays that
785 don't set Address in their config now avoid using begin_dir for
786 all direct connections. Should fix bugs 827, 883, and 900.
787 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
788 that would occur on some exit nodes when DNS failures and timeouts
789 occurred in certain patterns. Fix for bug 957.
792 - When starting with a cache over a few days old, do not leak
793 memory for the obsolete router descriptors in it. Bugfix on
794 0.2.0.33; fixes bug 672.
795 - Hidden service clients didn't use a cached service descriptor that
796 was older than 15 minutes, but wouldn't fetch a new one either,
797 because there was already one in the cache. Now, fetch a v2
798 descriptor unless the same descriptor was added to the cache within
799 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
802 Changes in version 0.2.0.34 - 2009-02-08
803 Tor 0.2.0.34 features several more security-related fixes. You should
804 upgrade, especially if you run an exit relay (remote crash) or a
805 directory authority (remote infinite loop), or you're on an older
806 (pre-XP) or not-recently-patched Windows (remote exploit).
808 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
809 have many known flaws, and nobody should be using them. You should
810 upgrade. If you're using a Linux or BSD and its packages are obsolete,
811 stop using those packages and upgrade anyway.
814 - Fix an infinite-loop bug on handling corrupt votes under certain
815 circumstances. Bugfix on 0.2.0.8-alpha.
816 - Fix a temporary DoS vulnerability that could be performed by
817 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
818 - Avoid a potential crash on exit nodes when processing malformed
819 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
820 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
821 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
824 - Fix compilation on systems where time_t is a 64-bit integer.
825 Patch from Matthias Drochner.
826 - Don't consider expiring already-closed client connections. Fixes
827 bug 893. Bugfix on 0.0.2pre20.
830 Changes in version 0.2.0.33 - 2009-01-21
831 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
832 useful to users. It also finally fixes a bug where a relay or client
833 that's been off for many days would take a long time to bootstrap.
835 This update also fixes an important security-related bug reported by
836 Ilja van Sprundel. You should upgrade. (We'll send out more details
837 about the bug once people have had some time to upgrade.)
840 - Fix a heap-corruption bug that may be remotely triggerable on
841 some platforms. Reported by Ilja van Sprundel.
844 - When a stream at an exit relay is in state "resolving" or
845 "connecting" and it receives an "end" relay cell, the exit relay
846 would silently ignore the end cell and not close the stream. If
847 the client never closes the circuit, then the exit relay never
848 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
850 - When sending CREATED cells back for a given circuit, use a 64-bit
851 connection ID to find the right connection, rather than an addr:port
852 combination. Now that we can have multiple OR connections between
853 the same ORs, it is no longer possible to use addr:port to uniquely
854 identify a connection.
855 - Bridge relays that had DirPort set to 0 would stop fetching
856 descriptors shortly after startup, and then briefly resume
857 after a new bandwidth test and/or after publishing a new bridge
858 descriptor. Bridge users that try to bootstrap from them would
859 get a recent networkstatus but would get descriptors from up to
860 18 hours earlier, meaning most of the descriptors were obsolete
861 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
862 - Prevent bridge relays from serving their 'extrainfo' document
863 to anybody who asks, now that extrainfo docs include potentially
864 sensitive aggregated client geoip summaries. Bugfix on
866 - If the cached networkstatus consensus is more than five days old,
867 discard it rather than trying to use it. In theory it could be
868 useful because it lists alternate directory mirrors, but in practice
869 it just means we spend many minutes trying directory mirrors that
870 are long gone from the network. Also discard router descriptors as
871 we load them if they are more than five days old, since the onion
872 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
875 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
876 could make gcc generate non-functional binary search code. Bugfix
878 - Build correctly on platforms without socklen_t.
879 - Compile without warnings on solaris.
880 - Avoid potential crash on internal error during signature collection.
881 Fixes bug 864. Patch from rovv.
882 - Correct handling of possible malformed authority signing key
883 certificates with internal signature types. Fixes bug 880.
884 Bugfix on 0.2.0.3-alpha.
885 - Fix a hard-to-trigger resource leak when logging credential status.
887 - When we can't initialize DNS because the network is down, do not
888 automatically stop Tor from starting. Instead, we retry failed
889 dns_init() every 10 minutes, and change the exit policy to reject
890 *:* until one succeeds. Fixes bug 691.
891 - Use 64 bits instead of 32 bits for connection identifiers used with
892 the controller protocol, to greatly reduce risk of identifier reuse.
893 - When we're choosing an exit node for a circuit, and we have
894 no pending streams, choose a good general exit rather than one that
895 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
896 - Fix another case of assuming, when a specific exit is requested,
897 that we know more than the user about what hosts it allows.
898 Fixes one case of bug 752. Patch from rovv.
899 - Clip the MaxCircuitDirtiness config option to a minimum of 10
900 seconds. Warn the user if lower values are given in the
901 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
902 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
903 user if lower values are given in the configuration. Bugfix on
904 0.1.1.17-rc. Patch by Sebastian.
905 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
906 the cache because we already had a v0 descriptor with the same ID.
907 Bugfix on 0.2.0.18-alpha.
908 - Fix a race condition when freeing keys shared between main thread
909 and CPU workers that could result in a memory leak. Bugfix on
910 0.1.0.1-rc. Fixes bug 889.
911 - Send a valid END cell back when a client tries to connect to a
912 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
913 840. Patch from rovv.
914 - Check which hops rendezvous stream cells are associated with to
915 prevent possible guess-the-streamid injection attacks from
916 intermediate hops. Fixes another case of bug 446. Based on patch
918 - If a broken client asks a non-exit router to connect somewhere,
919 do not even do the DNS lookup before rejecting the connection.
920 Fixes another case of bug 619. Patch from rovv.
921 - When a relay gets a create cell it can't decrypt (e.g. because it's
922 using the wrong onion key), we were dropping it and letting the
923 client time out. Now actually answer with a destroy cell. Fixes
924 bug 904. Bugfix on 0.0.2pre8.
926 o Minor bugfixes (hidden services):
927 - Do not throw away existing introduction points on SIGHUP. Bugfix on
928 0.0.6pre1. Patch by Karsten. Fixes bug 874.
931 - Report the case where all signatures in a detached set are rejected
932 differently than the case where there is an error handling the
934 - When we realize that another process has modified our cached
935 descriptors, print out a more useful error message rather than
936 triggering an assertion. Fixes bug 885. Patch from Karsten.
937 - Implement the 0x20 hack to better resist DNS poisoning: set the
938 case on outgoing DNS requests randomly, and reject responses that do
939 not match the case correctly. This logic can be disabled with the
940 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
941 of servers that do not reliably preserve case in replies. See
942 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
944 - Check DNS replies for more matching fields to better resist DNS
946 - Never use OpenSSL compression: it wastes RAM and CPU trying to
947 compress cells, which are basically all encrypted, compressed, or
951 Changes in version 0.2.0.32 - 2008-11-20
952 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
953 packages (and maybe other packages) noticed by Theo de Raadt, fixes
954 a smaller security flaw that might allow an attacker to access local
955 services, further improves hidden service performance, and fixes a
956 variety of other issues.
959 - The "User" and "Group" config options did not clear the
960 supplementary group entries for the Tor process. The "User" option
961 is now more robust, and we now set the groups to the specified
962 user's primary group. The "Group" option is now ignored. For more
963 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
964 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
965 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
966 - The "ClientDNSRejectInternalAddresses" config option wasn't being
967 consistently obeyed: if an exit relay refuses a stream because its
968 exit policy doesn't allow it, we would remember what IP address
969 the relay said the destination address resolves to, even if it's
970 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
973 - Fix a DOS opportunity during the voting signature collection process
974 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
976 o Major bugfixes (hidden services):
977 - When fetching v0 and v2 rendezvous service descriptors in parallel,
978 we were failing the whole hidden service request when the v0
979 descriptor fetch fails, even if the v2 fetch is still pending and
980 might succeed. Similarly, if the last v2 fetch fails, we were
981 failing the whole hidden service request even if a v0 fetch is
982 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
983 - When extending a circuit to a hidden service directory to upload a
984 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
985 requests failed, because the router descriptor has not been
986 downloaded yet. In these cases, do not attempt to upload the
987 rendezvous descriptor, but wait until the router descriptor is
988 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
989 descriptor from a hidden service directory for which the router
990 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
994 - Fix several infrequent memory leaks spotted by Coverity.
995 - When testing for libevent functions, set the LDFLAGS variable
996 correctly. Found by Riastradh.
997 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
998 bootstrapping with tunneled directory connections. Bugfix on
999 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
1000 - When asked to connect to A.B.exit:80, if we don't know the IP for A
1001 and we know that server B rejects most-but-not all connections to
1002 port 80, we would previously reject the connection. Now, we assume
1003 the user knows what they were asking for. Fixes bug 752. Bugfix
1004 on 0.0.9rc5. Diagnosed by BarkerJr.
1005 - If we overrun our per-second write limits a little, count this as
1006 having used up our write allocation for the second, and choke
1007 outgoing directory writes. Previously, we had only counted this when
1008 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
1009 Bugfix on 0.2.0.x (??).
1010 - Remove the old v2 directory authority 'lefkada' from the default
1011 list. It has been gone for many months.
1012 - Stop doing unaligned memory access that generated bus errors on
1013 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
1014 - Make USR2 log-level switch take effect immediately. Bugfix on
1017 o Minor bugfixes (controller):
1018 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
1019 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
1022 Changes in version 0.2.0.31 - 2008-09-03
1023 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
1024 a big bug we're seeing where in rare cases traffic from one Tor stream
1025 gets mixed into another stream, and fixes a variety of smaller issues.
1028 - Make sure that two circuits can never exist on the same connection
1029 with the same circuit ID, even if one is marked for close. This
1030 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
1031 - Relays now reject risky extend cells: if the extend cell includes
1032 a digest of all zeroes, or asks to extend back to the relay that
1033 sent the extend cell, tear down the circuit. Ideas suggested
1035 - If not enough of our entry guards are available so we add a new
1036 one, we might use the new one even if it overlapped with the
1037 current circuit's exit relay (or its family). Anonymity bugfix
1038 pointed out by rovv.
1041 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
1042 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
1043 - Correctly detect the presence of the linux/netfilter_ipv4.h header
1044 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
1045 - Pick size of default geoip filename string correctly on windows.
1046 Fixes bug 806. Bugfix on 0.2.0.30.
1047 - Make the autoconf script accept the obsolete --with-ssl-dir
1048 option as an alias for the actually-working --with-openssl-dir
1049 option. Fix the help documentation to recommend --with-openssl-dir.
1050 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
1051 - When using the TransPort option on OpenBSD, and using the User
1052 option to change UID and drop privileges, make sure to open
1053 /dev/pf before dropping privileges. Fixes bug 782. Patch from
1054 Christopher Davis. Bugfix on 0.1.2.1-alpha.
1055 - Try to attach connections immediately upon receiving a RENDEZVOUS2
1056 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
1057 on the client side when connecting to a hidden service. Bugfix
1058 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
1059 - When closing an application-side connection because its circuit is
1060 getting torn down, generate the stream event correctly. Bugfix on
1061 0.1.2.x. Anonymous patch.
1064 Changes in version 0.2.0.30 - 2008-07-15
1065 This new stable release switches to a more efficient directory
1066 distribution design, adds features to make connections to the Tor
1067 network harder to block, allows Tor to act as a DNS proxy, adds separate
1068 rate limiting for relayed traffic to make it easier for clients to
1069 become relays, fixes a variety of potential anonymity problems, and
1070 includes the usual huge pile of other features and bug fixes.
1072 o New v3 directory design:
1073 - Tor now uses a new way to learn about and distribute information
1074 about the network: the directory authorities vote on a common
1075 network status document rather than each publishing their own
1076 opinion. Now clients and caches download only one networkstatus
1077 document to bootstrap, rather than downloading one for each
1078 authority. Clients only download router descriptors listed in
1079 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
1081 - Set up moria1, tor26, and dizum as v3 directory authorities
1082 in addition to being v2 authorities. Also add three new ones:
1083 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
1084 dannenberg (run by CCC).
1085 - Switch to multi-level keys for directory authorities: now their
1086 long-term identity key can be kept offline, and they periodically
1087 generate a new signing key. Clients fetch the "key certificates"
1088 to keep up to date on the right keys. Add a standalone tool
1089 "tor-gencert" to generate key certificates. Implements proposal 103.
1090 - Add a new V3AuthUseLegacyKey config option to make it easier for
1091 v3 authorities to change their identity keys if another bug like
1092 Debian's OpenSSL RNG flaw appears.
1093 - Authorities and caches fetch the v2 networkstatus documents
1094 less often, now that v3 is recommended.
1096 o Make Tor connections stand out less on the wire:
1097 - Use an improved TLS handshake designed by Steven Murdoch in proposal
1098 124, as revised in proposal 130. The new handshake is meant to
1099 be harder for censors to fingerprint, and it adds the ability
1100 to detect certain kinds of man-in-the-middle traffic analysis
1101 attacks. The new handshake format includes version negotiation for
1102 OR connections as described in proposal 105, which will allow us
1103 to improve Tor's link protocol more safely in the future.
1104 - Enable encrypted directory connections by default for non-relays,
1105 so censor tools that block Tor directory connections based on their
1106 plaintext patterns will no longer work. This means Tor works in
1107 certain censored countries by default again.
1108 - Stop including recognizeable strings in the commonname part of
1109 Tor's x509 certificates.
1111 o Implement bridge relays:
1112 - Bridge relays (or "bridges" for short) are Tor relays that aren't
1113 listed in the main Tor directory. Since there is no complete public
1114 list of them, even an ISP that is filtering connections to all the
1115 known Tor relays probably won't be able to block all the bridges.
1116 See doc/design-paper/blocking.pdf and proposal 125 for details.
1117 - New config option BridgeRelay that specifies you want to be a
1118 bridge relay rather than a normal relay. When BridgeRelay is set
1119 to 1, then a) you cache dir info even if your DirPort ins't on,
1120 and b) the default for PublishServerDescriptor is now "bridge"
1121 rather than "v2,v3".
1122 - New config option "UseBridges 1" for clients that want to use bridge
1123 relays instead of ordinary entry guards. Clients then specify
1124 bridge relays by adding "Bridge" lines to their config file. Users
1125 can learn about a bridge relay either manually through word of
1126 mouth, or by one of our rate-limited mechanisms for giving out
1127 bridge addresses without letting an attacker easily enumerate them
1128 all. See https://www.torproject.org/bridges for details.
1129 - Bridge relays behave like clients with respect to time intervals
1130 for downloading new v3 consensus documents -- otherwise they
1131 stand out. Bridge users now wait until the end of the interval,
1132 so their bridge relay will be sure to have a new consensus document.
1134 o Implement bridge directory authorities:
1135 - Bridge authorities are like normal directory authorities, except
1136 they don't serve a list of known bridges. Therefore users that know
1137 a bridge's fingerprint can fetch a relay descriptor for that bridge,
1138 including fetching updates e.g. if the bridge changes IP address,
1139 yet an attacker can't just fetch a list of all the bridges.
1140 - Set up Tonga as the default bridge directory authority.
1141 - Bridge authorities refuse to serve bridge descriptors or other
1142 bridge information over unencrypted connections (that is, when
1143 responding to direct DirPort requests rather than begin_dir cells.)
1144 - Bridge directory authorities do reachability testing on the
1145 bridges they know. They provide router status summaries to the
1146 controller via "getinfo ns/purpose/bridge", and also dump summaries
1147 to a file periodically, so we can keep internal stats about which
1148 bridges are functioning.
1149 - If bridge users set the UpdateBridgesFromAuthority config option,
1150 but the digest they ask for is a 404 on the bridge authority,
1151 they fall back to contacting the bridge directly.
1152 - Bridges always use begin_dir to publish their server descriptor to
1153 the bridge authority using an anonymous encrypted tunnel.
1154 - Early work on a "bridge community" design: if bridge authorities set
1155 the BridgePassword config option, they will serve a snapshot of
1156 known bridge routerstatuses from their DirPort to anybody who
1157 knows that password. Unset by default.
1158 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
1159 report sanitized aggregated summaries in their extra-info documents
1160 privately to the bridge authority, listing which countries are
1161 able to reach them. We hope this mechanism will let us learn when
1162 certain countries start trying to block bridges.
1163 - Bridge authorities write bridge descriptors to disk, so they can
1164 reload them after a reboot. They can also export the descriptors
1165 to other programs, so we can distribute them to blocked users via
1166 the BridgeDB interface, e.g. via https://bridges.torproject.org/
1167 and bridges@torproject.org.
1169 o Tor can be a DNS proxy:
1170 - The new client-side DNS proxy feature replaces the need for
1171 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
1172 for DNS requests on port 9999, use the Tor network to resolve them
1173 anonymously, and send the reply back like a regular DNS server.
1174 The code still only implements a subset of DNS.
1175 - Add a new AutomapHostsOnResolve option: when it is enabled, any
1176 resolve request for hosts matching a given pattern causes Tor to
1177 generate an internal virtual address mapping for that host. This
1178 allows DNSPort to work sensibly with hidden service users. By
1179 default, .exit and .onion addresses are remapped; the list of
1180 patterns can be reconfigured with AutomapHostsSuffixes.
1181 - Add an "-F" option to tor-resolve to force a resolve for a .onion
1182 address. Thanks to the AutomapHostsOnResolve option, this is no
1183 longer a completely silly thing to do.
1185 o Major features (relay usability):
1186 - New config options RelayBandwidthRate and RelayBandwidthBurst:
1187 a separate set of token buckets for relayed traffic. Right now
1188 relayed traffic is defined as answers to directory requests, and
1189 OR connections that don't have any local circuits on them. See
1190 proposal 111 for details.
1191 - Create listener connections before we setuid to the configured
1192 User and Group. Now non-Windows users can choose port values
1193 under 1024, start Tor as root, and have Tor bind those ports
1194 before it changes to another UID. (Windows users could already
1196 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
1197 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
1198 on "vserver" accounts. Patch from coderman.
1200 o Major features (directory authorities):
1201 - Directory authorities track weighted fractional uptime and weighted
1202 mean-time-between failures for relays. WFU is suitable for deciding
1203 whether a node is "usually up", while MTBF is suitable for deciding
1204 whether a node is "likely to stay up." We need both, because
1205 "usually up" is a good requirement for guards, while "likely to
1206 stay up" is a good requirement for long-lived connections.
1207 - Directory authorities use a new formula for selecting which relays
1208 to advertise as Guards: they must be in the top 7/8 in terms of
1209 how long we have known about them, and above the median of those
1210 nodes in terms of weighted fractional uptime.
1211 - Directory authorities use a new formula for selecting which relays
1212 to advertise as Stable: when we have 4 or more days of data, use
1213 median measured MTBF rather than median declared uptime. Implements
1215 - Directory authorities accept and serve "extra info" documents for
1216 routers. Routers now publish their bandwidth-history lines in the
1217 extra-info docs rather than the main descriptor. This step saves
1218 60% (!) on compressed router descriptor downloads. Servers upload
1219 extra-info docs to any authority that accepts them; directory
1220 authorities now allow multiple router descriptors and/or extra
1221 info documents to be uploaded in a single go. Authorities, and
1222 caches that have been configured to download extra-info documents,
1223 download them as needed. Implements proposal 104.
1224 - Authorities now list relays who have the same nickname as
1225 a different named relay, but list them with a new flag:
1226 "Unnamed". Now we can make use of relays that happen to pick the
1227 same nickname as a server that registered two years ago and then
1228 disappeared. Implements proposal 122.
1229 - Store routers in a file called cached-descriptors instead of in
1230 cached-routers. Initialize cached-descriptors from cached-routers
1231 if the old format is around. The new format allows us to store
1232 annotations along with descriptors, to record the time we received
1233 each descriptor, its source, and its purpose: currently one of
1234 general, controller, or bridge.
1236 o Major features (other):
1237 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
1238 Tor can warn and/or refuse connections to ports commonly used with
1239 vulnerable-plaintext protocols. Currently we warn on ports 23,
1240 109, 110, and 143, but we don't reject any. Based on proposal 129
1241 by Kevin Bauer and Damon McCoy.
1242 - Integrate Karsten Loesing's Google Summer of Code project to publish
1243 hidden service descriptors on a set of redundant relays that are a
1244 function of the hidden service address. Now we don't have to rely
1245 on three central hidden service authorities for publishing and
1246 fetching every hidden service descriptor. Implements proposal 114.
1247 - Allow tunnelled directory connections to ask for an encrypted
1248 "begin_dir" connection or an anonymized "uses a full Tor circuit"
1249 connection independently. Now we can make anonymized begin_dir
1250 connections for (e.g.) more secure hidden service posting and
1253 o Major bugfixes (crashes and assert failures):
1254 - Stop imposing an arbitrary maximum on the number of file descriptors
1255 used for busy servers. Bug reported by Olaf Selke; patch from
1257 - Avoid possible failures when generating a directory with routers
1258 with over-long versions strings, or too many flags set.
1259 - Fix a rare assert error when we're closing one of our threads:
1260 use a mutex to protect the list of logs, so we never write to the
1261 list as it's being freed. Fixes the very rare bug 575, which is
1262 kind of the revenge of bug 222.
1263 - Avoid segfault in the case where a badly behaved v2 versioning
1264 directory sends a signed networkstatus with missing client-versions.
1265 - When we hit an EOF on a log (probably because we're shutting down),
1266 don't try to remove the log from the list: just mark it as
1267 unusable. (Bulletproofs against bug 222.)
1269 o Major bugfixes (code security fixes):
1270 - Detect size overflow in zlib code. Reported by Justin Ferguson and
1272 - Rewrite directory tokenization code to never run off the end of
1273 a string. Fixes bug 455. Patch from croup.
1274 - Be more paranoid about overwriting sensitive memory on free(),
1275 as a defensive programming tactic to ensure forward secrecy.
1277 o Major bugfixes (anonymity fixes):
1278 - Reject requests for reverse-dns lookup of names that are in
1279 a private address space. Patch from lodger.
1280 - Never report that we've used more bandwidth than we're willing to
1281 relay: it leaks how much non-relay traffic we're using. Resolves
1283 - As a client, do not believe any server that tells us that an
1284 address maps to an internal address space.
1285 - Warn about unsafe ControlPort configurations.
1286 - Directory authorities now call routers Fast if their bandwidth is
1287 at least 100KB/s, and consider their bandwidth adequate to be a
1288 Guard if it is at least 250KB/s, no matter the medians. This fix
1289 complements proposal 107.
1290 - Directory authorities now never mark more than 2 servers per IP as
1291 Valid and Running (or 5 on addresses shared by authorities).
1292 Implements proposal 109, by Kevin Bauer and Damon McCoy.
1293 - If we're a relay, avoid picking ourselves as an introduction point,
1294 a rendezvous point, or as the final hop for internal circuits. Bug
1295 reported by taranis and lodger.
1296 - Exit relays that are used as a client can now reach themselves
1297 using the .exit notation, rather than just launching an infinite
1298 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
1299 - Fix a bug where, when we were choosing the 'end stream reason' to
1300 put in our relay end cell that we send to the exit relay, Tor
1301 clients on Windows were sometimes sending the wrong 'reason'. The
1302 anonymity problem is that exit relays may be able to guess whether
1303 the client is running Windows, thus helping partition the anonymity
1304 set. Down the road we should stop sending reasons to exit relays,
1305 or otherwise prevent future versions of this bug.
1306 - Only update guard status (usable / not usable) once we have
1307 enough directory information. This was causing us to discard all our
1308 guards on startup if we hadn't been running for a few weeks. Fixes
1310 - When our directory information has been expired for a while, stop
1311 being willing to build circuits using it. Fixes bug 401.
1313 o Major bugfixes (peace of mind for relay operators)
1314 - Non-exit relays no longer answer "resolve" relay cells, so they
1315 can't be induced to do arbitrary DNS requests. (Tor clients already
1316 avoid using non-exit relays for resolve cells, but now servers
1317 enforce this too.) Fixes bug 619. Patch from lodger.
1318 - When we setconf ClientOnly to 1, close any current OR and Dir
1319 listeners. Reported by mwenge.
1321 o Major bugfixes (other):
1322 - If we only ever used Tor for hidden service lookups or posts, we
1323 would stop building circuits and start refusing connections after
1324 24 hours, since we falsely believed that Tor was dormant. Reported
1326 - Add a new __HashedControlSessionPassword option for controllers
1327 to use for one-off session password hashes that shouldn't get
1328 saved to disk by SAVECONF --- Vidalia users were accumulating a
1329 pile of HashedControlPassword lines in their torrc files, one for
1330 each time they had restarted Tor and then clicked Save. Make Tor
1331 automatically convert "HashedControlPassword" to this new option but
1332 only when it's given on the command line. Partial fix for bug 586.
1333 - Patch from "Andrew S. Lists" to catch when we contact a directory
1334 mirror at IP address X and he says we look like we're coming from
1335 IP address X. Otherwise this would screw up our address detection.
1336 - Reject uploaded descriptors and extrainfo documents if they're
1337 huge. Otherwise we'll cache them all over the network and it'll
1338 clog everything up. Suggested by Aljosha Judmayer.
1339 - When a hidden service was trying to establish an introduction point,
1340 and Tor *did* manage to reuse one of the preemptively built
1341 circuits, it didn't correctly remember which one it used,
1342 so it asked for another one soon after, until there were no
1343 more preemptive circuits, at which point it launched one from
1344 scratch. Bugfix on 0.0.9.x.
1346 o Rate limiting and load balancing improvements:
1347 - When we add data to a write buffer in response to the data on that
1348 write buffer getting low because of a flush, do not consider the
1349 newly added data as a candidate for immediate flushing, but rather
1350 make it wait until the next round of writing. Otherwise, we flush
1351 and refill recursively, and a single greedy TLS connection can
1352 eat all of our bandwidth.
1353 - When counting the number of bytes written on a TLS connection,
1354 look at the BIO actually used for writing to the network, not
1355 at the BIO used (sometimes) to buffer data for the network.
1356 Looking at different BIOs could result in write counts on the
1357 order of ULONG_MAX. Fixes bug 614.
1358 - If we change our MaxAdvertisedBandwidth and then reload torrc,
1359 Tor won't realize it should publish a new relay descriptor. Fixes
1360 bug 688, reported by mfr.
1361 - Avoid using too little bandwidth when our clock skips a few seconds.
1362 - Choose which bridge to use proportional to its advertised bandwidth,
1363 rather than uniformly at random. This should speed up Tor for
1364 bridge users. Also do this for people who set StrictEntryNodes.
1366 o Bootstrapping faster and building circuits more intelligently:
1367 - Fix bug 660 that was preventing us from knowing that we should
1368 preemptively build circuits to handle expected directory requests.
1369 - When we're checking if we have enough dir info for each relay
1370 to begin establishing circuits, make sure that we actually have
1371 the descriptor listed in the consensus, not just any descriptor.
1372 - Correctly notify one-hop connections when a circuit build has
1373 failed. Possible fix for bug 669. Found by lodger.
1374 - Clients now hold circuitless TLS connections open for 1.5 times
1375 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
1376 rebuild a new circuit over them within that timeframe. Previously,
1377 they held them open only for KeepalivePeriod (5 minutes).
1379 o Performance improvements (memory):
1380 - Add OpenBSD malloc code from "phk" as an optional malloc
1381 replacement on Linux: some glibc libraries do very poorly with
1382 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
1383 ./configure to get the replacement malloc code.
1384 - Switch our old ring buffer implementation for one more like that
1385 used by free Unix kernels. The wasted space in a buffer with 1mb
1386 of data will now be more like 8k than 1mb. The new implementation
1387 also avoids realloc();realloc(); patterns that can contribute to
1388 memory fragmentation.
1389 - Change the way that Tor buffers data that it is waiting to write.
1390 Instead of queueing data cells in an enormous ring buffer for each
1391 client->OR or OR->OR connection, we now queue cells on a separate
1392 queue for each circuit. This lets us use less slack memory, and
1393 will eventually let us be smarter about prioritizing different kinds
1395 - Reference-count and share copies of address policy entries; only 5%
1396 of them were actually distinct.
1397 - Tune parameters for cell pool allocation to minimize amount of
1399 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
1400 for every single inactive connection_t. Free items from the
1401 4k/16k-buffer free lists when they haven't been used for a while.
1402 - Make memory debugging information describe more about history
1403 of cell allocation, so we can help reduce our memory use.
1404 - Be even more aggressive about releasing RAM from small
1405 empty buffers. Thanks to our free-list code, this shouldn't be too
1406 performance-intensive.
1407 - Log malloc statistics from mallinfo() on platforms where it exists.
1408 - Use memory pools to allocate cells with better speed and memory
1409 efficiency, especially on platforms where malloc() is inefficient.
1410 - Add a --with-tcmalloc option to the configure script to link
1411 against tcmalloc (if present). Does not yet search for non-system
1414 o Performance improvements (socket management):
1415 - Count the number of open sockets separately from the number of
1416 active connection_t objects. This will let us avoid underusing
1417 our allocated connection limit.
1418 - We no longer use socket pairs to link an edge connection to an
1419 anonymous directory connection or a DirPort test connection.
1420 Instead, we track the link internally and transfer the data
1421 in-process. This saves two sockets per "linked" connection (at the
1422 client and at the server), and avoids the nasty Windows socketpair()
1424 - We were leaking a file descriptor if Tor started with a zero-length
1425 cached-descriptors file. Patch by "freddy77".
1427 o Performance improvements (CPU use):
1428 - Never walk through the list of logs if we know that no log target
1429 is interested in a given message.
1430 - Call routerlist_remove_old_routers() much less often. This should
1431 speed startup, especially on directory caches.
1432 - Base64 decoding was actually showing up on our profile when parsing
1433 the initial descriptor file; switch to an in-process all-at-once
1434 implementation that's about 3.5x times faster than calling out to
1436 - Use a slightly simpler string hashing algorithm (copying Python's
1437 instead of Java's) and optimize our digest hashing algorithm to take
1438 advantage of 64-bit platforms and to remove some possibly-costly
1440 - When implementing AES counter mode, update only the portions of the
1441 counter buffer that need to change, and don't keep separate
1442 network-order and host-order counters on big-endian hosts (where
1444 - Add an in-place version of aes_crypt() so that we can avoid doing a
1445 needless memcpy() call on each cell payload.
1446 - Use Critical Sections rather than Mutexes for synchronizing threads
1447 on win32; Mutexes are heavier-weight, and designed for synchronizing
1450 o Performance improvements (bandwidth use):
1451 - Don't try to launch new descriptor downloads quite so often when we
1452 already have enough directory information to build circuits.
1453 - Version 1 directories are no longer generated in full. Instead,
1454 authorities generate and serve "stub" v1 directories that list
1455 no servers. This will stop Tor versions 0.1.0.x and earlier from
1456 working, but (for security reasons) nobody should be running those
1458 - Avoid going directly to the directory authorities even if you're a
1459 relay, if you haven't found yourself reachable yet or if you've
1460 decided not to advertise your dirport yet. Addresses bug 556.
1461 - If we've gone 12 hours since our last bandwidth check, and we
1462 estimate we have less than 50KB bandwidth capacity but we could
1463 handle more, do another bandwidth test.
1464 - Support "If-Modified-Since" when answering HTTP requests for
1465 directories, running-routers documents, and v2 and v3 networkstatus
1466 documents. (There's no need to support it for router descriptors,
1467 since those are downloaded by descriptor digest.)
1468 - Stop fetching directory info so aggressively if your DirPort is
1469 on but your ORPort is off; stop fetching v2 dir info entirely.
1470 You can override these choices with the new FetchDirInfoEarly
1473 o Changed config option behavior (features):
1474 - Configuration files now accept C-style strings as values. This
1475 helps encode characters not allowed in the current configuration
1476 file format, such as newline or #. Addresses bug 557.
1477 - Add hidden services and DNSPorts to the list of things that make
1478 Tor accept that it has running ports. Change starting Tor with no
1479 ports from a fatal error to a warning; we might change it back if
1480 this turns out to confuse anybody. Fixes bug 579.
1481 - Make PublishServerDescriptor default to 1, so the default doesn't
1482 have to change as we invent new directory protocol versions.
1483 - Allow people to say PreferTunnelledDirConns rather than
1484 PreferTunneledDirConns, for those alternate-spellers out there.
1485 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
1486 accommodate the growing number of servers that use the default
1487 and are reaching it.
1488 - Make it possible to enable HashedControlPassword and
1489 CookieAuthentication at the same time.
1490 - When a TrackHostExits-chosen exit fails too many times in a row,
1491 stop using it. Fixes bug 437.
1493 o Changed config option behavior (bugfixes):
1494 - Do not read the configuration file when we've only been told to
1495 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
1496 based on patch from Sebastian Hahn.
1497 - Actually validate the options passed to AuthDirReject,
1498 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
1499 - Make "ClientOnly 1" config option disable directory ports too.
1500 - Don't stop fetching descriptors when FetchUselessDescriptors is
1501 set, even if we stop asking for circuits. Bug reported by tup
1503 - Servers used to decline to publish their DirPort if their
1504 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
1505 they look only at BandwidthRate and RelayBandwidthRate.
1506 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
1507 minus 1 byte: the actual maximum declared bandwidth.
1508 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
1509 - Make the NodeFamilies config option work. (Reported by
1510 lodger -- it has never actually worked, even though we added it
1512 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
1513 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
1515 o New config options:
1516 - New configuration options AuthDirMaxServersPerAddr and
1517 AuthDirMaxServersperAuthAddr to override default maximum number
1518 of servers allowed on a single IP address. This is important for
1519 running a test network on a single host.
1520 - Three new config options (AlternateDirAuthority,
1521 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
1522 user selectively replace the default directory authorities by type,
1523 rather than the all-or-nothing replacement that DirServer offers.
1524 - New config options AuthDirBadDir and AuthDirListBadDirs for
1525 authorities to mark certain relays as "bad directories" in the
1526 networkstatus documents. Also supports the "!baddir" directive in
1527 the approved-routers file.
1528 - New config option V2AuthoritativeDirectory that all v2 directory
1529 authorities must set. This lets v3 authorities choose not to serve
1530 v2 directory information.
1532 o Minor features (other):
1533 - When we're not serving v2 directory information, there is no reason
1534 to actually keep any around. Remove the obsolete files and directory
1535 on startup if they are very old and we aren't going to serve them.
1536 - When we negotiate a v2 link-layer connection (not yet implemented),
1537 accept RELAY_EARLY cells and turn them into RELAY cells if we've
1538 negotiated a v1 connection for their next step. Initial steps for
1540 - When we have no consensus, check FallbackNetworkstatusFile (defaults
1541 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
1542 we can start out knowing some directory caches. We don't ship with
1543 a fallback consensus by default though, because it was making
1544 bootstrapping take too long while we tried many down relays.
1545 - Authorities send back an X-Descriptor-Not-New header in response to
1546 an accepted-but-discarded descriptor upload. Partially implements
1548 - If we find a cached-routers file that's been sitting around for more
1549 than 28 days unmodified, then most likely it's a leftover from
1550 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
1552 - When we (as a cache) download a descriptor because it was listed
1553 in a consensus, remember when the consensus was supposed to expire,
1554 and don't expire the descriptor until then.
1555 - Optionally (if built with -DEXPORTMALLINFO) export the output
1556 of mallinfo via http, as tor/mallinfo.txt. Only accessible
1558 - Tag every guard node in our state file with the version that
1559 we believe added it, or with our own version if we add it. This way,
1560 if a user temporarily runs an old version of Tor and then switches
1561 back to a new one, she doesn't automatically lose her guards.
1562 - When somebody requests a list of statuses or servers, and we have
1563 none of those, return a 404 rather than an empty 200.
1564 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
1566 - Add an HSAuthorityRecordStats option that hidden service authorities
1567 can use to track statistics of overall hidden service usage without
1568 logging information that would be as useful to an attacker.
1569 - Allow multiple HiddenServicePort directives with the same virtual
1570 port; when they occur, the user is sent round-robin to one
1571 of the target ports chosen at random. Partially fixes bug 393 by
1572 adding limited ad-hoc round-robining.
1573 - Revamp file-writing logic so we don't need to have the entire
1574 contents of a file in memory at once before we write to disk. Tor,
1577 o Minor bugfixes (other):
1578 - Alter the code that tries to recover from unhandled write
1579 errors, to not try to flush onto a socket that's given us
1581 - Directory mirrors no longer include a guess at the client's IP
1582 address if the connection appears to be coming from the same /24
1583 network; it was producing too many wrong guesses.
1584 - If we're trying to flush the last bytes on a connection (for
1585 example, when answering a directory request), reset the
1586 time-to-give-up timeout every time we manage to write something
1588 - Reject router descriptors with out-of-range bandwidthcapacity or
1589 bandwidthburst values.
1590 - If we can't expand our list of entry guards (e.g. because we're
1591 using bridges or we have StrictEntryNodes set), don't mark relays
1592 down when they fail a directory request. Otherwise we're too quick
1593 to mark all our entry points down.
1594 - Authorities no longer send back "400 you're unreachable please fix
1595 it" errors to Tor servers that aren't online all the time. We're
1596 supposed to tolerate these servers now.
1597 - Let directory authorities startup even when they can't generate
1598 a descriptor immediately, e.g. because they don't know their
1600 - Correctly enforce that elements of directory objects do not appear
1601 more often than they are allowed to appear.
1602 - Stop allowing hibernating servers to be "stable" or "fast".
1603 - On Windows, we were preventing other processes from reading
1604 cached-routers while Tor was running. (Reported by janbar)
1605 - Check return values from pthread_mutex functions.
1606 - When opening /dev/null in finish_daemonize(), do not pass the
1607 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
1608 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
1610 o Controller features:
1611 - The GETCONF command now escapes and quotes configuration values
1612 that don't otherwise fit into the torrc file.
1613 - The SETCONF command now handles quoted values correctly.
1614 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
1615 ask about source, timestamp of arrival, purpose, etc. We need
1616 something like this to help Vidalia not do GeoIP lookups on bridge
1618 - Allow multiple HashedControlPassword config lines, to support
1619 multiple controller passwords.
1620 - Accept LF instead of CRLF on controller, since some software has a
1621 hard time generating real Internet newlines.
1622 - Add GETINFO values for the server status events
1623 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
1625 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
1626 GETINFO for Torstat to use until it can switch to using extrainfos.
1627 - New config option CookieAuthFile to choose a new location for the
1628 cookie authentication file, and config option
1629 CookieAuthFileGroupReadable to make it group-readable.
1630 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
1631 match requests to applications. Patch from Robert Hogan.
1632 - Add a RESOLVE command to launch hostname lookups. Original patch
1634 - Add GETINFO status/enough-dir-info to let controllers tell whether
1635 Tor has downloaded sufficient directory information. Patch from Tup.
1636 - You can now use the ControlSocket option to tell Tor to listen for
1637 controller connections on Unix domain sockets on systems that
1638 support them. Patch from Peter Palfrader.
1639 - New "GETINFO address-mappings/*" command to get address mappings
1640 with expiry information. "addr-mappings/*" is now deprecated.
1642 - Add a new config option __DisablePredictedCircuits designed for
1643 use by the controller, when we don't want Tor to build any circuits
1645 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
1646 so we can exit from the middle of the circuit.
1647 - Implement "getinfo status/circuit-established".
1648 - Implement "getinfo status/version/..." so a controller can tell
1649 whether the current version is recommended, and whether any versions
1650 are good, and how many authorities agree. Patch from "shibz".
1651 - Controllers should now specify cache=no or cache=yes when using
1652 the +POSTDESCRIPTOR command.
1653 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
1654 Robert Hogan. Fixes the first part of bug 681.
1655 - When reporting clock skew, and we know that the clock is _at least
1656 as skewed_ as some value, but we don't know the actual value,
1657 report the value as a "minimum skew."
1659 o Controller bugfixes:
1660 - Generate "STATUS_SERVER" events rather than misspelled
1661 "STATUS_SEVER" events. Caught by mwenge.
1662 - Reject controller commands over 1MB in length, so rogue
1663 processes can't run us out of memory.
1664 - Change the behavior of "getinfo status/good-server-descriptor"
1665 so it doesn't return failure when any authority disappears.
1666 - Send NAMESERVER_STATUS messages for a single failed nameserver
1668 - When the DANGEROUS_VERSION controller status event told us we're
1669 running an obsolete version, it used the string "OLD" to describe
1670 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
1671 "OBSOLETE" in both cases.
1672 - Respond to INT and TERM SIGNAL commands before we execute the
1673 signal, in case the signal shuts us down. We had a patch in
1674 0.1.2.1-alpha that tried to do this by queueing the response on
1675 the connection's buffer before shutting down, but that really
1676 isn't the same thing at all. Bug located by Matt Edman.
1677 - Provide DNS expiry times in GMT, not in local time. For backward
1678 compatibility, ADDRMAP events only provide GMT expiry in an extended
1679 field. "GETINFO address-mappings" always does the right thing.
1680 - Use CRLF line endings properly in NS events.
1681 - Make 'getinfo fingerprint' return a 551 error if we're not a
1682 server, so we match what the control spec claims we do. Reported
1684 - Fix a typo in an error message when extendcircuit fails that
1685 caused us to not follow the \r\n-based delimiter protocol. Reported
1687 - When tunneling an encrypted directory connection, and its first
1688 circuit fails, do not leave it unattached and ask the controller
1689 to deal. Fixes the second part of bug 681.
1690 - Treat some 403 responses from directory servers as INFO rather than
1691 WARN-severity events.
1693 o Portability / building / compiling:
1694 - When building with --enable-gcc-warnings, check for whether Apple's
1695 warning "-Wshorten-64-to-32" is available.
1696 - Support compilation to target iPhone; patch from cjacker huang.
1697 To build for iPhone, pass the --enable-iphone option to configure.
1698 - Detect non-ASCII platforms (if any still exist) and refuse to
1699 build there: some of our code assumes that 'A' is 65 and so on.
1700 - Clear up some MIPSPro compiler warnings.
1701 - Make autoconf search for libevent, openssl, and zlib consistently.
1702 - Update deprecated macros in configure.in.
1703 - When warning about missing headers, tell the user to let us
1704 know if the compile succeeds anyway, so we can downgrade the
1706 - Include the current subversion revision as part of the version
1707 string: either fetch it directly if we're in an SVN checkout, do
1708 some magic to guess it if we're in an SVK checkout, or use
1709 the last-detected version if we're building from a .tar.gz.
1710 Use this version consistently in log messages.
1711 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
1712 - Read resolv.conf files correctly on platforms where read() returns
1713 partial results on small file reads.
1714 - Build without verbose warnings even on gcc 4.2 and 4.3.
1715 - On Windows, correctly detect errors when listing the contents of
1716 a directory. Fix from lodger.
1717 - Run 'make test' as part of 'make dist', so we stop releasing so
1718 many development snapshots that fail their unit tests.
1719 - Add support to detect Libevent versions in the 1.4.x series
1721 - Add command-line arguments to unit-test executable so that we can
1722 invoke any chosen test from the command line rather than having
1723 to run the whole test suite at once; and so that we can turn on
1724 logging for the unit tests.
1725 - Do not automatically run configure from autogen.sh. This
1726 non-standard behavior tended to annoy people who have built other
1728 - Fix a macro/CPP interaction that was confusing some compilers:
1729 some GCCs don't like #if/#endif pairs inside macro arguments.
1731 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
1732 Fixes bug 704; fix from Steven Murdoch.
1733 - Correctly detect transparent proxy support on Linux hosts that
1734 require in.h to be included before netfilter_ipv4.h. Patch
1737 o Logging improvements:
1738 - When we haven't had any application requests lately, don't bother
1739 logging that we have expired a bunch of descriptors.
1740 - When attempting to open a logfile fails, tell us why.
1741 - Only log guard node status when guard node status has changed.
1742 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
1743 make "INFO" 75% less verbose.
1744 - When SafeLogging is disabled, log addresses along with all TLS
1746 - Report TLS "zero return" case as a "clean close" and "IO error"
1747 as a "close". Stop calling closes "unexpected closes": existing
1748 Tors don't use SSL_close(), so having a connection close without
1749 the TLS shutdown handshake is hardly unexpected.
1750 - When we receive a consensus from the future, warn about skew.
1751 - Make "not enough dir info yet" warnings describe *why* Tor feels
1752 it doesn't have enough directory info yet.
1753 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
1754 consumers. (We already do this on HUP.)
1755 - Give more descriptive well-formedness errors for out-of-range
1756 hidden service descriptor/protocol versions.
1757 - Stop recommending that every server operator send mail to tor-ops.
1758 Resolves bug 597. Bugfix on 0.1.2.x.
1759 - Improve skew reporting: try to give the user a better log message
1760 about how skewed they are, and how much this matters.
1761 - New --quiet command-line option to suppress the default console log.
1762 Good in combination with --hash-password.
1763 - Don't complain that "your server has not managed to confirm that its
1764 ports are reachable" if we haven't been able to build any circuits
1766 - Detect the reason for failing to mmap a descriptor file we just
1767 wrote, and give a more useful log message. Fixes bug 533.
1768 - Always prepend "Bug: " to any log message about a bug.
1769 - When dumping memory usage, list bytes used in buffer memory
1771 - When running with dmalloc, dump more stats on hup and on exit.
1772 - Put a platform string (e.g. "Linux i686") in the startup log
1773 message, so when people paste just their logs, we know if it's
1774 OpenBSD or Windows or what.
1775 - When logging memory usage, break down memory used in buffers by
1777 - When we are reporting the DirServer line we just parsed, we were
1778 logging the second stanza of the key fingerprint, not the first.
1779 - Even though Windows is equally happy with / and \ as path separators,
1780 try to use \ consistently on Windows and / consistently on Unix: it
1781 makes the log messages nicer.
1782 - On OSX, stop warning the user that kqueue support in libevent is
1783 "experimental", since it seems to have worked fine for ages.
1785 o Contributed scripts and tools:
1786 - Update linux-tor-prio.sh script to allow QoS based on the uid of
1787 the Tor process. Patch from Marco Bonetti with tweaks from Mike
1789 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
1790 Unix users an easy way to script their Tor process (e.g. by
1791 adjusting bandwidth based on the time of the day).
1792 - In the exitlist script, only consider the most recently published
1793 server descriptor for each server. Also, when the user requests
1794 a list of servers that _reject_ connections to a given address,
1795 explicitly exclude the IPs that also have servers that accept
1796 connections to that address. Resolves bug 405.
1797 - Include a new contrib/tor-exit-notice.html file that exit relay
1798 operators can put on their website to help reduce abuse queries.
1800 o Newly deprecated features:
1801 - The status/version/num-versioning and status/version/num-concurring
1802 GETINFO controller options are no longer useful in the v3 directory
1803 protocol: treat them as deprecated, and warn when they're used.
1804 - The RedirectExits config option is now deprecated.
1807 - Drop the old code to choke directory connections when the
1808 corresponding OR connections got full: thanks to the cell queue
1809 feature, OR conns don't get full any more.
1810 - Remove the old "dns worker" server DNS code: it hasn't been default
1811 since 0.1.2.2-alpha, and all the servers are using the new
1813 - Remove the code to generate the oldest (v1) directory format.
1814 - Remove support for the old bw_accounting file: we've been storing
1815 bandwidth accounting information in the state file since
1816 0.1.2.5-alpha. This may result in bandwidth accounting errors
1817 if you try to upgrade from 0.1.1.x or earlier, or if you try to
1818 downgrade to 0.1.1.x or earlier.
1819 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
1820 it, it had no AES, and it hasn't seen any security patches since
1822 - Stop overloading the circuit_t.onionskin field for both "onionskin
1823 from a CREATE cell that we are waiting for a cpuworker to be
1824 assigned" and "onionskin from an EXTEND cell that we are going to
1825 send to an OR as soon as we are connected". Might help with bug 600.
1826 - Remove the tor_strpartition() function: its logic was confused,
1827 and it was only used for one thing that could be implemented far
1829 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
1830 and TorControl.py, as they use the old v0 controller protocol,
1831 and are obsoleted by TorFlow anyway.
1832 - Drop support for v1 rendezvous descriptors, since we never used
1833 them anyway, and the code has probably rotted by now. Based on
1834 patch from Karsten Loesing.
1835 - Stop allowing address masks that do not correspond to bit prefixes.
1836 We have warned about these for a really long time; now it's time
1837 to reject them. (Patch from croup.)
1838 - Remove an optimization in the AES counter-mode code that assumed
1839 that the counter never exceeded 2^68. When the counter can be set
1840 arbitrarily as an IV (as it is by Karsten's new hidden services
1841 code), this assumption no longer holds.
1842 - Disable the SETROUTERPURPOSE controller command: it is now
1846 Changes in version 0.1.2.19 - 2008-01-17
1847 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
1848 exit policy a little bit more conservative so it's safer to run an
1849 exit relay on a home system, and fixes a variety of smaller issues.
1852 - Exit policies now reject connections that are addressed to a
1853 relay's public (external) IP address too, unless
1854 ExitPolicyRejectPrivate is turned off. We do this because too
1855 many relays are running nearby to services that trust them based
1859 - When the clock jumps forward a lot, do not allow the bandwidth
1860 buckets to become negative. Fixes bug 544.
1861 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
1862 on every successful resolve. Reported by Mike Perry.
1863 - Purge old entries from the "rephist" database and the hidden
1864 service descriptor database even when DirPort is zero.
1865 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
1866 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
1867 crashing or mis-answering these requests.
1868 - When we decide to send a 503 response to a request for servers, do
1869 not then also send the server descriptors: this defeats the whole
1870 purpose. Fixes bug 539.
1873 - Changing the ExitPolicyRejectPrivate setting should cause us to
1874 rebuild our server descriptor.
1875 - Fix handling of hex nicknames when answering controller requests for
1876 networkstatus by name, or when deciding whether to warn about
1877 unknown routers in a config option. (Patch from mwenge.)
1878 - Fix a couple of hard-to-trigger autoconf problems that could result
1879 in really weird results on platforms whose sys/types.h files define
1880 nonstandard integer types.
1881 - Don't try to create the datadir when running --verify-config or
1882 --hash-password. Resolves bug 540.
1883 - If we were having problems getting a particular descriptor from the
1884 directory caches, and then we learned about a new descriptor for
1885 that router, we weren't resetting our failure count. Reported
1887 - Although we fixed bug 539 (where servers would send HTTP status 503
1888 responses _and_ send a body too), there are still servers out there
1889 that haven't upgraded. Therefore, make clients parse such bodies
1890 when they receive them.
1891 - Run correctly on systems where rlim_t is larger than unsigned long.
1892 This includes some 64-bit systems.
1893 - Run correctly on platforms (like some versions of OS X 10.5) where
1894 the real limit for number of open files is OPEN_FILES, not rlim_max
1895 from getrlimit(RLIMIT_NOFILES).
1896 - Avoid a spurious free on base64 failure.
1897 - Avoid segfaults on certain complex invocations of
1898 router_get_by_hexdigest().
1899 - Fix rare bug on REDIRECTSTREAM control command when called with no
1900 port set: it could erroneously report an error when none had
1904 Changes in version 0.1.2.18 - 2007-10-28
1905 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
1906 hidden service introduction that were causing huge delays, and a big
1907 bug that was causing some servers to disappear from the network status
1908 lists for a few hours each day.
1910 o Major bugfixes (crashes):
1911 - If a connection is shut down abruptly because of something that
1912 happened inside connection_flushed_some(), do not call
1913 connection_finished_flushing(). Should fix bug 451:
1914 "connection_stop_writing: Assertion conn->write_event failed"
1915 Bugfix on 0.1.2.7-alpha.
1916 - Fix possible segfaults in functions called from
1917 rend_process_relay_cell().
1919 o Major bugfixes (hidden services):
1920 - Hidden services were choosing introduction points uniquely by
1921 hexdigest, but when constructing the hidden service descriptor
1922 they merely wrote the (potentially ambiguous) nickname.
1923 - Clients now use the v2 intro format for hidden service
1924 connections: they specify their chosen rendezvous point by identity
1925 digest rather than by (potentially ambiguous) nickname. These
1926 changes could speed up hidden service connections dramatically.
1928 o Major bugfixes (other):
1929 - Stop publishing a new server descriptor just because we get a
1930 HUP signal. This led (in a roundabout way) to some servers getting
1931 dropped from the networkstatus lists for a few hours each day.
1932 - When looking for a circuit to cannibalize, consider family as well
1933 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
1934 circuit cannibalization).
1935 - When a router wasn't listed in a new networkstatus, we were leaving
1936 the flags for that router alone -- meaning it remained Named,
1937 Running, etc -- even though absence from the networkstatus means
1938 that it shouldn't be considered to exist at all anymore. Now we
1939 clear all the flags for routers that fall out of the networkstatus
1940 consensus. Fixes bug 529.
1943 - Don't try to access (or alter) the state file when running
1944 --list-fingerprint or --verify-config or --hash-password. Resolves
1946 - When generating information telling us how to extend to a given
1947 router, do not try to include the nickname if it is
1948 absent. Resolves bug 467.
1949 - Fix a user-triggerable segfault in expand_filename(). (There isn't
1950 a way to trigger this remotely.)
1951 - When sending a status event to the controller telling it that an
1952 OR address is reachable, set the port correctly. (Previously we
1953 were reporting the dir port.)
1954 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
1955 command. Bugfix on 0.1.2.17.
1956 - When loading bandwidth history, do not believe any information in
1957 the future. Fixes bug 434.
1958 - When loading entry guard information, do not believe any information
1960 - When we have our clock set far in the future and generate an
1961 onion key, then re-set our clock to be correct, we should not stop
1962 the onion key from getting rotated.
1963 - On some platforms, accept() can return a broken address. Detect
1964 this more quietly, and deal accordingly. Fixes bug 483.
1965 - It's not actually an error to find a non-pending entry in the DNS
1966 cache when canceling a pending resolve. Don't log unless stuff
1967 is fishy. Resolves bug 463.
1968 - Don't reset trusted dir server list when we set a configuration
1969 option. Patch from Robert Hogan.
1972 Changes in version 0.1.2.17 - 2007-08-30
1973 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
1974 X bundles. Vidalia 0.0.14 makes authentication required for the
1975 ControlPort in the default configuration, which addresses important
1976 security risks. Everybody who uses Vidalia (or another controller)
1979 In addition, this Tor update fixes major load balancing problems with
1980 path selection, which should speed things up a lot once many people
1983 o Major bugfixes (security):
1984 - We removed support for the old (v0) control protocol. It has been
1985 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
1986 become more of a headache than it's worth.
1988 o Major bugfixes (load balancing):
1989 - When choosing nodes for non-guard positions, weight guards
1990 proportionally less, since they already have enough load. Patch
1992 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
1993 will allow fast Tor servers to get more attention.
1994 - When we're upgrading from an old Tor version, forget our current
1995 guards and pick new ones according to the new weightings. These
1996 three load balancing patches could raise effective network capacity
1997 by a factor of four. Thanks to Mike Perry for measurements.
1999 o Major bugfixes (stream expiration):
2000 - Expire not-yet-successful application streams in all cases if
2001 they've been around longer than SocksTimeout. Right now there are
2002 some cases where the stream will live forever, demanding a new
2003 circuit every 15 seconds. Fixes bug 454; reported by lodger.
2005 o Minor features (controller):
2006 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
2007 is valid before any authentication has been received. It tells
2008 a controller what kind of authentication is expected, and what
2009 protocol is spoken. Implements proposal 119.
2011 o Minor bugfixes (performance):
2012 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
2013 greatly speeding up loading cached-routers from disk on startup.
2014 - Disable sentinel-based debugging for buffer code: we squashed all
2015 the bugs that this was supposed to detect a long time ago, and now
2016 its only effect is to change our buffer sizes from nice powers of
2017 two (which platform mallocs tend to like) to values slightly over
2018 powers of two (which make some platform mallocs sad).
2020 o Minor bugfixes (misc):
2021 - If exit bandwidth ever exceeds one third of total bandwidth, then
2022 use the correct formula to weight exit nodes when choosing paths.
2023 Based on patch from Mike Perry.
2024 - Choose perfectly fairly among routers when choosing by bandwidth and
2025 weighting by fraction of bandwidth provided by exits. Previously, we
2026 would choose with only approximate fairness, and correct ourselves
2027 if we ran off the end of the list.
2028 - If we require CookieAuthentication but we fail to write the
2029 cookie file, we would warn but not exit, and end up in a state
2030 where no controller could authenticate. Now we exit.
2031 - If we require CookieAuthentication, stop generating a new cookie
2032 every time we change any piece of our config.
2033 - Refuse to start with certain directory authority keys, and
2034 encourage people using them to stop.
2035 - Terminate multi-line control events properly. Original patch
2037 - Fix a minor memory leak when we fail to find enough suitable
2038 servers to choose a circuit.
2039 - Stop leaking part of the descriptor when we run into a particularly
2040 unparseable piece of it.
2043 Changes in version 0.1.2.16 - 2007-08-01
2044 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
2045 remote attacker in certain situations to rewrite the user's torrc
2046 configuration file. This can completely compromise anonymity of users
2047 in most configurations, including those running the Vidalia bundles,
2048 TorK, etc. Or worse.
2050 o Major security fixes:
2051 - Close immediately after missing authentication on control port;
2052 do not allow multiple authentication attempts.
2055 Changes in version 0.1.2.15 - 2007-07-17
2056 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
2057 problems, fixes compilation on BSD, and fixes a variety of other
2058 bugs. Everybody should upgrade.
2060 o Major bugfixes (compilation):
2061 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
2063 o Major bugfixes (crashes):
2064 - Try even harder not to dereference the first character after
2065 an mmap(). Reported by lodger.
2066 - Fix a crash bug in directory authorities when we re-number the
2067 routerlist while inserting a new router.
2068 - When the cached-routers file is an even multiple of the page size,
2069 don't run off the end and crash. (Fixes bug 455; based on idea
2071 - Fix eventdns.c behavior on Solaris: It is critical to include
2072 orconfig.h _before_ sys/types.h, so that we can get the expected
2073 definition of _FILE_OFFSET_BITS.
2075 o Major bugfixes (security):
2076 - Fix a possible buffer overrun when using BSD natd support. Bug
2078 - When sending destroy cells from a circuit's origin, don't include
2079 the reason for tearing down the circuit. The spec says we didn't,
2080 and now we actually don't. Reported by lodger.
2081 - Keep streamids from different exits on a circuit separate. This
2082 bug may have allowed other routers on a given circuit to inject
2083 cells into streams. Reported by lodger; fixes bug 446.
2084 - If there's a never-before-connected-to guard node in our list,
2085 never choose any guards past it. This way we don't expand our
2086 guard list unless we need to.
2088 o Minor bugfixes (guard nodes):
2089 - Weight guard selection by bandwidth, so that low-bandwidth nodes
2090 don't get overused as guards.
2092 o Minor bugfixes (directory):
2093 - Correctly count the number of authorities that recommend each
2094 version. Previously, we were under-counting by 1.
2095 - Fix a potential crash bug when we load many server descriptors at
2096 once and some of them make others of them obsolete. Fixes bug 458.
2098 o Minor bugfixes (hidden services):
2099 - Stop tearing down the whole circuit when the user asks for a
2100 connection to a port that the hidden service didn't configure.
2103 o Minor bugfixes (misc):
2104 - On Windows, we were preventing other processes from reading
2105 cached-routers while Tor was running. Reported by janbar.
2106 - Fix a possible (but very unlikely) bug in picking routers by
2107 bandwidth. Add a log message to confirm that it is in fact
2108 unlikely. Patch from lodger.
2109 - Backport a couple of memory leak fixes.
2110 - Backport miscellaneous cosmetic bugfixes.
2113 Changes in version 0.1.2.14 - 2007-05-25
2114 Tor 0.1.2.14 changes the addresses of two directory authorities (this
2115 change especially affects those who serve or use hidden services),
2116 and fixes several other crash- and security-related bugs.
2118 o Directory authority changes:
2119 - Two directory authorities (moria1 and moria2) just moved to new
2120 IP addresses. This change will particularly affect those who serve
2121 or use hidden services.
2123 o Major bugfixes (crashes):
2124 - If a directory server runs out of space in the connection table
2125 as it's processing a begin_dir request, it will free the exit stream
2126 but leave it attached to the circuit, leading to unpredictable
2127 behavior. (Reported by seeess, fixes bug 425.)
2128 - Fix a bug in dirserv_remove_invalid() that would cause authorities
2129 to corrupt memory under some really unlikely scenarios.
2130 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
2131 - Avoid segfaults when reading from mmaped descriptor file. (Reported
2134 o Major bugfixes (security):
2135 - When choosing an entry guard for a circuit, avoid using guards
2136 that are in the same family as the chosen exit -- not just guards
2137 that are exactly the chosen exit. (Reported by lodger.)
2139 o Major bugfixes (resource management):
2140 - If a directory authority is down, skip it when deciding where to get
2141 networkstatus objects or descriptors. Otherwise we keep asking
2142 every 10 seconds forever. Fixes bug 384.
2143 - Count it as a failure if we fetch a valid network-status but we
2144 don't want to keep it. Otherwise we'll keep fetching it and keep
2145 not wanting to keep it. Fixes part of bug 422.
2146 - If all of our dirservers have given us bad or no networkstatuses
2147 lately, then stop hammering them once per minute even when we
2148 think they're failed. Fixes another part of bug 422.
2151 - Actually set the purpose correctly for descriptors inserted with
2153 - When we have k non-v2 authorities in our DirServer config,
2154 we ignored the last k authorities in the list when updating our
2156 - Correctly back-off from requesting router descriptors that we are
2157 having a hard time downloading.
2158 - Read resolv.conf files correctly on platforms where read() returns
2159 partial results on small file reads.
2160 - Don't rebuild the entire router store every time we get 32K of
2161 routers: rebuild it when the journal gets very large, or when
2162 the gaps in the store get very large.
2165 - When routers publish SVN revisions in their router descriptors,
2166 authorities now include those versions correctly in networkstatus
2168 - Warn when using a version of libevent before 1.3b to run a server on
2169 OSX or BSD: these versions interact badly with userspace threads.
2172 Changes in version 0.1.2.13 - 2007-04-24
2173 This release features some major anonymity fixes, such as safer path
2174 selection; better client performance; faster bootstrapping, better
2175 address detection, and better DNS support for servers; write limiting as
2176 well as read limiting to make servers easier to run; and a huge pile of
2177 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
2179 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
2180 of the Freenode IRC network, remembering his patience and vision for
2181 free speech on the Internet.
2183 o Major features, client performance:
2184 - Weight directory requests by advertised bandwidth. Now we can
2185 let servers enable write limiting but still allow most clients to
2186 succeed at their directory requests. (We still ignore weights when
2187 choosing a directory authority; I hope this is a feature.)
2188 - Stop overloading exit nodes -- avoid choosing them for entry or
2189 middle hops when the total bandwidth available from non-exit nodes
2190 is much higher than the total bandwidth available from exit nodes.
2191 - Rather than waiting a fixed amount of time between retrying
2192 application connections, we wait only 10 seconds for the first,
2193 10 seconds for the second, and 15 seconds for each retry after
2194 that. Hopefully this will improve the expected user experience.
2195 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
2196 to open a stream fails; now we do in more cases. This should
2197 make clients able to find a good exit faster in some cases, since
2198 unhandleable requests will now get an error rather than timing out.
2200 o Major features, client functionality:
2201 - Implement BEGIN_DIR cells, so we can connect to a directory
2202 server via TLS to do encrypted directory requests rather than
2203 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
2204 config options if you like. For now, this feature only works if
2205 you already have a descriptor for the destination dirserver.
2206 - Add support for transparent application connections: this basically
2207 bundles the functionality of trans-proxy-tor into the Tor
2208 mainline. Now hosts with compliant pf/netfilter implementations
2209 can redirect TCP connections straight to Tor without diverting
2210 through SOCKS. (Based on patch from tup.)
2211 - Add support for using natd; this allows FreeBSDs earlier than
2212 5.1.2 to have ipfw send connections through Tor without using
2213 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
2215 o Major features, servers:
2216 - Setting up a dyndns name for your server is now optional: servers
2217 with no hostname or IP address will learn their IP address by
2218 asking the directory authorities. This code only kicks in when you
2219 would normally have exited with a "no address" error. Nothing's
2220 authenticated, so use with care.
2221 - Directory servers now spool server descriptors, v1 directories,
2222 and v2 networkstatus objects to buffers as needed rather than en
2223 masse. They also mmap the cached-routers files. These steps save
2225 - Stop requiring clients to have well-formed certificates, and stop
2226 checking nicknames in certificates. (Clients have certificates so
2227 that they can look like Tor servers, but in the future we might want
2228 to allow them to look like regular TLS clients instead. Nicknames
2229 in certificates serve no purpose other than making our protocol
2230 easier to recognize on the wire.) Implements proposal 106.
2232 o Improvements on DNS support:
2233 - Add "eventdns" asynchronous dns library originally based on code
2234 from Adam Langley. Now we can discard the old rickety dnsworker
2235 concept, and support a wider variety of DNS functions. Allows
2236 multithreaded builds on NetBSD and OpenBSD again.
2237 - Add server-side support for "reverse" DNS lookups (using PTR
2238 records so clients can determine the canonical hostname for a given
2239 IPv4 address). Only supported by servers using eventdns; servers
2240 now announce in their descriptors if they don't support eventdns.
2241 - Workaround for name servers (like Earthlink's) that hijack failing
2242 DNS requests and replace the no-such-server answer with a "helpful"
2243 redirect to an advertising-driven search portal. Also work around
2244 DNS hijackers who "helpfully" decline to hijack known-invalid
2245 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
2246 lets you turn it off.
2247 - Servers now check for the case when common DNS requests are going to
2248 wildcarded addresses (i.e. all getting the same answer), and change
2249 their exit policy to reject *:* if it's happening.
2250 - When asked to resolve a hostname, don't use non-exit servers unless
2251 requested to do so. This allows servers with broken DNS to be
2252 useful to the network.
2253 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
2254 useless IPv6 DNS resolves.
2255 - Specify and implement client-side SOCKS5 interface for reverse DNS
2256 lookups (see doc/socks-extensions.txt). Also cache them.
2257 - When we change nameservers or IP addresses, reset and re-launch
2258 our tests for DNS hijacking.
2260 o Improvements on reachability testing:
2261 - Servers send out a burst of long-range padding cells once they've
2262 established that they're reachable. Spread them over 4 circuits,
2263 so hopefully a few will be fast. This exercises bandwidth and
2264 bootstraps them into the directory more quickly.
2265 - When we find our DirPort to be reachable, publish a new descriptor
2266 so we'll tell the world (reported by pnx).
2267 - Directory authorities now only decide that routers are reachable
2268 if their identity keys are as expected.
2269 - Do DirPort reachability tests less often, since a single test
2270 chews through many circuits before giving up.
2271 - Avoid some false positives during reachability testing: don't try
2272 to test via a server that's on the same /24 network as us.
2273 - Start publishing one minute or so after we find our ORPort
2274 to be reachable. This will help reduce the number of descriptors
2275 we have for ourselves floating around, since it's quite likely
2276 other things (e.g. DirPort) will change during that minute too.
2277 - Routers no longer try to rebuild long-term connections to directory
2278 authorities, and directory authorities no longer try to rebuild
2279 long-term connections to all servers. We still don't hang up
2280 connections in these two cases though -- we need to look at it
2281 more carefully to avoid flapping, and we likely need to wait til
2282 0.1.1.x is obsolete.
2284 o Improvements on rate limiting:
2285 - Enable write limiting as well as read limiting. Now we sacrifice
2286 capacity if we're pushing out lots of directory traffic, rather
2287 than overrunning the user's intended bandwidth limits.
2288 - Include TLS overhead when counting bandwidth usage; previously, we
2289 would count only the bytes sent over TLS, but not the bytes used
2291 - Servers decline directory requests much more aggressively when
2292 they're low on bandwidth. Otherwise they end up queueing more and
2293 more directory responses, which can't be good for latency.
2294 - But never refuse directory requests from local addresses.
2295 - Be willing to read or write on local connections (e.g. controller
2296 connections) even when the global rate limiting buckets are empty.
2297 - Flush local controller connection buffers periodically as we're
2298 writing to them, so we avoid queueing 4+ megabytes of data before
2300 - Revise and clean up the torrc.sample that we ship with; add
2301 a section for BandwidthRate and BandwidthBurst.
2303 o Major features, NT services:
2304 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
2305 command-line flag so that admins can override the default by saying
2306 "tor --service install --user "SomeUser"". This will not affect
2307 existing installed services. Also, warn the user that the service
2308 will look for its configuration file in the service user's
2309 %appdata% directory. (We can't do the "hardwire the user's appdata
2310 directory" trick any more, since we may not have read access to that
2312 - Support running the Tor service with a torrc not in the same
2313 directory as tor.exe and default to using the torrc located in
2314 the %appdata%\Tor\ of the user who installed the service. Patch
2316 - Add an --ignore-missing-torrc command-line option so that we can
2317 get the "use sensible defaults if the configuration file doesn't
2318 exist" behavior even when specifying a torrc location on the
2320 - When stopping an NT service, wait up to 10 sec for it to actually
2321 stop. (Patch from Matt Edman; resolves bug 295.)
2323 o Directory authority improvements:
2324 - Stop letting hibernating or obsolete servers affect uptime and
2326 - Stop listing hibernating servers in the v1 directory.
2327 - Authorities no longer recommend exits as guards if this would shift
2328 too much load to the exit nodes.
2329 - Authorities now specify server versions in networkstatus. This adds
2330 about 2% to the size of compressed networkstatus docs, and allows
2331 clients to tell which servers support BEGIN_DIR and which don't.
2332 The implementation is forward-compatible with a proposed future
2333 protocol version scheme not tied to Tor versions.
2334 - DirServer configuration lines now have an orport= option so
2335 clients can open encrypted tunnels to the authorities without
2336 having downloaded their descriptors yet. Enabled for moria1,
2337 moria2, tor26, and lefkada now in the default configuration.
2338 - Add a BadDirectory flag to network status docs so that authorities
2339 can (eventually) tell clients about caches they believe to be
2340 broken. Not used yet.
2341 - Allow authorities to list nodes as bad exits in their
2342 approved-routers file by fingerprint or by address. If most
2343 authorities set a BadExit flag for a server, clients don't think
2344 of it as a general-purpose exit. Clients only consider authorities
2345 that advertise themselves as listing bad exits.
2346 - Patch from Steve Hildrey: Generate network status correctly on
2347 non-versioning dirservers.
2348 - Have directory authorities allow larger amounts of drift in uptime
2349 without replacing the server descriptor: previously, a server that
2350 restarted every 30 minutes could have 48 "interesting" descriptors
2352 - Reserve the nickname "Unnamed" for routers that can't pick
2353 a hostname: any router can call itself Unnamed; directory
2354 authorities will never allocate Unnamed to any particular router;
2355 clients won't believe that any router is the canonical Unnamed.
2357 o Directory mirrors and clients:
2358 - Discard any v1 directory info that's over 1 month old (for
2359 directories) or over 1 week old (for running-routers lists).
2360 - Clients track responses with status 503 from dirservers. After a
2361 dirserver has given us a 503, we try not to use it until an hour has
2362 gone by, or until we have no dirservers that haven't given us a 503.
2363 - When we get a 503 from a directory, and we're not a server, we no
2364 longer count the failure against the total number of failures
2365 allowed for the object we're trying to download.
2366 - Prepare for servers to publish descriptors less often: never
2367 discard a descriptor simply for being too old until either it is
2368 recommended by no authorities, or until we get a better one for
2369 the same router. Make caches consider retaining old recommended
2370 routers for even longer.
2371 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
2372 headers for content, so that we can work better in the presence of
2373 caching HTTP proxies.
2374 - Stop fetching descriptors if you're not a dir mirror and you
2375 haven't tried to establish any circuits lately. (This currently
2376 causes some dangerous behavior, because when you start up again
2377 you'll use your ancient server descriptors.)
2379 o Major fixes, crashes:
2380 - Stop crashing when the controller asks us to resetconf more than
2381 one config option at once. (Vidalia 0.0.11 does this.)
2382 - Fix a longstanding obscure crash bug that could occur when we run
2383 out of DNS worker processes, if we're not using eventdns. (Resolves
2385 - Fix an assert that could trigger if a controller quickly set then
2386 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
2387 - Avoid crash when telling controller about stream-status and a
2389 - Avoid sending junk to controllers or segfaulting when a controller
2390 uses EVENT_NEW_DESC with verbose nicknames.
2391 - Stop triggering asserts if the controller tries to extend hidden
2392 service circuits (reported by mwenge).
2393 - If we start a server with ClientOnly 1, then set ClientOnly to 0
2394 and hup, stop triggering an assert based on an empty onion_key.
2395 - Mask out all signals in sub-threads; only the libevent signal
2396 handler should be processing them. This should prevent some crashes
2397 on some machines using pthreads. (Patch from coderman.)
2398 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
2400 o Major fixes, anonymity/security:
2401 - Automatically avoid picking more than one node from the same
2402 /16 network when constructing a circuit. Add an
2403 "EnforceDistinctSubnets" option to let people disable it if they
2404 want to operate private test networks on a single subnet.
2405 - When generating bandwidth history, round down to the nearest
2406 1k. When storing accounting data, round up to the nearest 1k.
2407 - When we're running as a server, remember when we last rotated onion
2408 keys, so that we will rotate keys once they're a week old even if
2409 we never stay up for a week ourselves.
2410 - If a client asked for a server by name, and there's a named server
2411 in our network-status but we don't have its descriptor yet, we
2412 could return an unnamed server instead.
2413 - Reject (most) attempts to use Tor circuits with length one. (If
2414 many people start using Tor as a one-hop proxy, exit nodes become
2415 a more attractive target for compromise.)
2416 - Just because your DirPort is open doesn't mean people should be
2417 able to remotely teach you about hidden service descriptors. Now
2418 only accept rendezvous posts if you've got HSAuthoritativeDir set.
2419 - Fix a potential race condition in the rpm installer. Found by
2421 - Do not log IPs with TLS failures for incoming TLS
2422 connections. (Fixes bug 382.)
2424 o Major fixes, other:
2425 - If our system clock jumps back in time, don't publish a negative
2426 uptime in the descriptor.
2427 - When we start during an accounting interval before it's time to wake
2428 up, remember to wake up at the correct time. (May fix bug 342.)
2429 - Previously, we would cache up to 16 old networkstatus documents
2430 indefinitely, if they came from nontrusted authorities. Now we
2431 discard them if they are more than 10 days old.
2432 - When we have a state file we cannot parse, tell the user and
2433 move it aside. Now we avoid situations where the user starts
2434 Tor in 1904, Tor writes a state file with that timestamp in it,
2435 the user fixes her clock, and Tor refuses to start.
2436 - Publish a new descriptor after we hup/reload. This is important
2437 if our config has changed such that we'll want to start advertising
2438 our DirPort now, etc.
2439 - If we are using an exit enclave and we can't connect, e.g. because
2440 its webserver is misconfigured to not listen on localhost, then
2441 back off and try connecting from somewhere else before we fail.
2443 o New config options or behaviors:
2444 - When EntryNodes are configured, rebuild the guard list to contain,
2445 in order: the EntryNodes that were guards before; the rest of the
2446 EntryNodes; the nodes that were guards before.
2447 - Do not warn when individual nodes in the configuration's EntryNodes,
2448 ExitNodes, etc are down: warn only when all possible nodes
2449 are down. (Fixes bug 348.)
2450 - Put a lower-bound on MaxAdvertisedBandwidth.
2451 - Start using the state file to store bandwidth accounting data:
2452 the bw_accounting file is now obsolete. We'll keep generating it
2453 for a while for people who are still using 0.1.2.4-alpha.
2454 - Try to batch changes to the state file so that we do as few
2455 disk writes as possible while still storing important things in
2457 - The state file and the bw_accounting file get saved less often when
2458 the AvoidDiskWrites config option is set.
2459 - Make PIDFile work on Windows.
2460 - Add internal descriptions for a bunch of configuration options:
2461 accessible via controller interface and in comments in saved
2463 - Reject *:563 (NNTPS) in the default exit policy. We already reject
2464 NNTP by default, so this seems like a sensible addition.
2465 - Clients now reject hostnames with invalid characters. This should
2466 avoid some inadvertent info leaks. Add an option
2467 AllowNonRFC953Hostnames to disable this behavior, in case somebody
2468 is running a private network with hosts called @, !, and #.
2469 - Check for addresses with invalid characters at the exit as well,
2470 and warn less verbosely when they fail. You can override this by
2471 setting ServerDNSAllowNonRFC953Addresses to 1.
2472 - Remove some options that have been deprecated since at least
2473 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
2474 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
2475 to set log options. Mark PathlenCoinWeight as obsolete.
2476 - Stop accepting certain malformed ports in configured exit policies.
2477 - When the user uses bad syntax in the Log config line, stop
2478 suggesting other bad syntax as a replacement.
2479 - Add new config option "ResolvConf" to let the server operator
2480 choose an alternate resolve.conf file when using eventdns.
2481 - If one of our entry guards is on the ExcludeNodes list, or the
2482 directory authorities don't think it's a good guard, treat it as
2483 if it were unlisted: stop using it as a guard, and throw it off
2484 the guards list if it stays that way for a long time.
2485 - Allow directory authorities to be marked separately as authorities
2486 for the v1 directory protocol, the v2 directory protocol, and
2487 as hidden service directories, to make it easier to retire old
2488 authorities. V1 authorities should set "HSAuthoritativeDir 1"
2489 to continue being hidden service authorities too.
2490 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
2491 - Make TrackExitHosts case-insensitive, and fix the behavior of
2492 ".suffix" TrackExitHosts items to avoid matching in the middle of
2494 - New DirPort behavior: if you have your dirport set, you download
2495 descriptors aggressively like a directory mirror, whether or not
2499 - Create a new file ReleaseNotes which was the old ChangeLog. The
2500 new ChangeLog file now includes the notes for all development
2502 - Add a new address-spec.txt document to describe our special-case
2503 addresses: .exit, .onion, and .noconnnect.
2504 - Fork the v1 directory protocol into its own spec document,
2505 and mark dir-spec.txt as the currently correct (v2) spec.
2507 o Packaging, porting, and contrib
2508 - "tor --verify-config" now exits with -1(255) or 0 depending on
2509 whether the config options are bad or good.
2510 - The Debian package now uses --verify-config when (re)starting,
2511 to distinguish configuration errors from other errors.
2512 - Adapt a patch from goodell to let the contrib/exitlist script
2513 take arguments rather than require direct editing.
2514 - Prevent the contrib/exitlist script from printing the same
2515 result more than once.
2516 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
2517 - In the hidden service example in torrc.sample, stop recommending
2518 esoteric and discouraged hidden service options.
2519 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
2520 values before failing, and always enables eventdns.
2521 - Try to detect Windows correctly when cross-compiling.
2522 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
2523 Try to fix this in configure.in by checking for most functions
2524 before we check for libevent.
2525 - Update RPMs to require libevent 1.2.
2526 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
2527 or later. Log when we are doing this, so we can diagnose it when
2528 it fails. (Also, recommend libevent 1.1b for kqueue and
2529 win32 methods; deprecate libevent 1.0b harder; make libevent
2530 recommendation system saner.)
2531 - Build with recent (1.3+) libevents on platforms that do not
2532 define the nonstandard types "u_int8_t" and friends.
2533 - Remove architecture from OS X builds. The official builds are
2534 now universal binaries.
2535 - Run correctly on OS X platforms with case-sensitive filesystems.
2536 - Correctly set maximum connection limit on Cygwin. (This time
2538 - Start compiling on MinGW on Windows (patches from Mike Chiussi
2540 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
2541 - Finally fix the openssl warnings from newer gccs that believe that
2542 ignoring a return value is okay, but casting a return value and
2543 then ignoring it is a sign of madness.
2544 - On architectures where sizeof(int)>4, still clamp declarable
2545 bandwidth to INT32_MAX.
2547 o Minor features, controller:
2548 - Warn the user when an application uses the obsolete binary v0
2549 control protocol. We're planning to remove support for it during
2550 the next development series, so it's good to give people some
2552 - Add STREAM_BW events to report per-entry-stream bandwidth
2553 use. (Patch from Robert Hogan.)
2554 - Rate-limit SIGNEWNYM signals in response to controllers that
2555 impolitely generate them for every single stream. (Patch from
2556 mwenge; closes bug 394.)
2557 - Add a REMAP status to stream events to note that a stream's
2558 address has changed because of a cached address or a MapAddress
2560 - Make REMAP stream events have a SOURCE (cache or exit), and
2561 make them generated in every case where we get a successful
2562 connected or resolved cell.
2563 - Track reasons for OR connection failure; make these reasons
2564 available via the controller interface. (Patch from Mike Perry.)
2565 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
2566 can learn when clients are sending malformed hostnames to Tor.
2567 - Specify and implement some of the controller status events.
2568 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
2569 - Reimplement GETINFO so that info/names stays in sync with the
2571 - Implement "GETINFO fingerprint".
2572 - Implement "SETEVENTS GUARD" so controllers can get updates on
2573 entry guard status as it changes.
2574 - Make all connections to addresses of the form ".noconnect"
2575 immediately get closed. This lets application/controller combos
2576 successfully test whether they're talking to the same Tor by
2577 watching for STREAM events.
2578 - Add a REASON field to CIRC events; for backward compatibility, this
2579 field is sent only to controllers that have enabled the extended
2580 event format. Also, add additional reason codes to explain why
2581 a given circuit has been destroyed or truncated. (Patches from
2583 - Add a REMOTE_REASON field to extended CIRC events to tell the
2584 controller why a remote OR told us to close a circuit.
2585 - Stream events also now have REASON and REMOTE_REASON fields,
2586 working much like those for circuit events.
2587 - There's now a GETINFO ns/... field so that controllers can ask Tor
2588 about the current status of a router.
2589 - A new event type "NS" to inform a controller when our opinion of
2590 a router's status has changed.
2591 - Add a GETINFO events/names and GETINFO features/names so controllers
2592 can tell which events and features are supported.
2593 - A new CLEARDNSCACHE signal to allow controllers to clear the
2594 client-side DNS cache without expiring circuits.
2595 - Fix CIRC controller events so that controllers can learn the
2596 identity digests of non-Named servers used in circuit paths.
2597 - Let controllers ask for more useful identifiers for servers. Instead
2598 of learning identity digests for un-Named servers and nicknames
2599 for Named servers, the new identifiers include digest, nickname,
2600 and indication of Named status. Off by default; see control-spec.txt
2601 for more information.
2602 - Add a "getinfo address" controller command so it can display Tor's
2603 best guess to the user.
2604 - New controller event to alert the controller when our server
2605 descriptor has changed.
2606 - Give more meaningful errors on controller authentication failure.
2607 - Export the default exit policy via the control port, so controllers
2608 don't need to guess what it is / will be later.
2610 o Minor bugfixes, controller:
2611 - When creating a circuit via the controller, send a 'launched'
2612 event when we're done, so we follow the spec better.
2613 - Correct the control spec to match how the code actually responds
2614 to 'getinfo addr-mappings/*'. Reported by daejees.
2615 - The control spec described a GUARDS event, but the code
2616 implemented a GUARD event. Standardize on GUARD, but let people
2617 ask for GUARDS too. Reported by daejees.
2618 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
2619 clear the corresponding on_circuit variable, and remember later
2620 that we don't need to send a redundant CLOSED event. (Resolves part
2622 - Report events where a resolve succeeded or where we got a socks
2623 protocol error correctly, rather than calling both of them
2625 - Change reported stream target addresses to IP consistently when
2626 we finally get the IP from an exit node.
2627 - Send log messages to the controller even if they happen to be very
2629 - Flush ERR-level controller status events just like we currently
2630 flush ERR-level log events, so that a Tor shutdown doesn't prevent
2631 the controller from learning about current events.
2632 - Report the circuit number correctly in STREAM CLOSED events. Bug
2633 reported by Mike Perry.
2634 - Do not report bizarre values for results of accounting GETINFOs
2635 when the last second's write or read exceeds the allotted bandwidth.
2636 - Report "unrecognized key" rather than an empty string when the
2637 controller tries to fetch a networkstatus that doesn't exist.
2638 - When the controller does a "GETINFO network-status", tell it
2639 about even those routers whose descriptors are very old, and use
2640 long nicknames where appropriate.
2641 - Fix handling of verbose nicknames with ORCONN controller events:
2642 make them show up exactly when requested, rather than exactly when
2644 - Controller signals now work on non-Unix platforms that don't define
2645 SIGUSR1 and SIGUSR2 the way we expect.
2646 - Respond to SIGNAL command before we execute the signal, in case
2647 the signal shuts us down. Suggested by Karsten Loesing.
2648 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
2650 o Minor features, code performance:
2651 - Major performance improvement on inserting descriptors: change
2652 algorithm from O(n^2) to O(n).
2653 - Do not rotate onion key immediately after setting it for the first
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.)
2660 - Statistics dumped by -USR2 now include a breakdown of public key
2661 operations, for profiling.
2662 - Make the common memory allocation path faster on machines where
2663 malloc(0) returns a pointer.
2664 - Split circuit_t into origin_circuit_t and or_circuit_t, and
2665 split connection_t into edge, or, dir, control, and base structs.
2666 These will save quite a bit of memory on busy servers, and they'll
2667 also help us track down bugs in the code and bugs in the spec.
2668 - Use OpenSSL's AES implementation on platforms where it's faster.
2669 This could save us as much as 10% CPU usage.
2671 o Minor features, descriptors and descriptor handling:
2672 - Avoid duplicate entries on MyFamily line in server descriptor.
2673 - When Tor receives a router descriptor that it asked for, but
2674 no longer wants (because it has received fresh networkstatuses
2675 in the meantime), do not warn the user. Cache the descriptor if
2676 we're a cache; drop it if we aren't.
2677 - Servers no longer ever list themselves in their "family" line,
2678 even if configured to do so. This makes it easier to configure
2679 family lists conveniently.
2681 o Minor fixes, confusing/misleading log messages:
2682 - Display correct results when reporting which versions are
2683 recommended, and how recommended they are. (Resolves bug 383.)
2684 - Inform the server operator when we decide not to advertise a
2685 DirPort due to AccountingMax enabled or a low BandwidthRate.
2686 - Only include function names in log messages for info/debug messages.
2687 For notice/warn/err, the content of the message should be clear on
2688 its own, and printing the function name only confuses users.
2689 - Remove even more protocol-related warnings from Tor server logs,
2690 such as bad TLS handshakes and malformed begin cells.
2691 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
2692 when the IP address is mapped through MapAddress to a hostname.
2693 - Fix misleading log messages: an entry guard that is "unlisted",
2694 as well as not known to be "down" (because we've never heard
2695 of it), is not therefore "up".
2697 o Minor fixes, old/obsolete behavior:
2698 - Start assuming we can use a create_fast cell if we don't know
2699 what version a router is running.
2700 - We no longer look for identity and onion keys in "identity.key" and
2701 "onion.key" -- these were replaced by secret_id_key and
2702 secret_onion_key in 0.0.8pre1.
2703 - We no longer require unrecognized directory entries to be
2705 - Drop compatibility with obsolete Tors that permit create cells
2706 to have the wrong circ_id_type.
2707 - Remove code to special-case "-cvs" ending, since it has not
2708 actually mattered since 0.0.9.
2709 - Don't re-write the fingerprint file every restart, unless it has
2712 o Minor fixes, misc client-side behavior:
2713 - Always remove expired routers and networkstatus docs before checking
2714 whether we have enough information to build circuits. (Fixes
2716 - When computing clock skew from directory HTTP headers, consider what
2717 time it was when we finished asking for the directory, not what
2719 - Make our socks5 handling more robust to broken socks clients:
2720 throw out everything waiting on the buffer in between socks
2721 handshake phases, since they can't possibly (so the theory
2722 goes) have predicted what we plan to respond to them.
2723 - Expire socks connections if they spend too long waiting for the
2724 handshake to finish. Previously we would let them sit around for
2725 days, if the connecting application didn't close them either.
2726 - And if the socks handshake hasn't started, don't send a
2727 "DNS resolve socks failed" handshake reply; just close it.
2728 - If the user asks to use invalid exit nodes, be willing to use
2730 - Track unreachable entry guards correctly: don't conflate
2731 'unreachable by us right now' with 'listed as down by the directory
2732 authorities'. With the old code, if a guard was unreachable by us
2733 but listed as running, it would clog our guard list forever.
2734 - Behave correctly in case we ever have a network with more than
2735 2GB/s total advertised capacity.
2736 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
2737 - Fix a memory leak when we ask for "all" networkstatuses and we
2738 get one we don't recognize.
2741 Changes in version 0.1.1.26 - 2006-12-14
2742 o Security bugfixes:
2743 - Stop sending the HttpProxyAuthenticator string to directory
2744 servers when directory connections are tunnelled through Tor.
2745 - Clients no longer store bandwidth history in the state file.
2746 - Do not log introduction points for hidden services if SafeLogging
2750 - Fix an assert failure when a directory authority sets
2751 AuthDirRejectUnlisted and then receives a descriptor from an
2752 unlisted router (reported by seeess).
2755 Changes in version 0.1.1.25 - 2006-11-04
2757 - When a client asks us to resolve (rather than connect to)
2758 an address, and we have a cached answer, give them the cached
2759 answer. Previously, we would give them no answer at all.
2760 - We were building exactly the wrong circuits when we predict
2761 hidden service requirements, meaning Tor would have to build all
2762 its circuits on demand.
2763 - If none of our live entry guards have a high uptime, but we
2764 require a guard with a high uptime, try adding a new guard before
2765 we give up on the requirement. This patch should make long-lived
2766 connections more stable on average.
2767 - When testing reachability of our DirPort, don't launch new
2768 tests when there's already one in progress -- unreachable
2769 servers were stacking up dozens of testing streams.
2771 o Security bugfixes:
2772 - When the user sends a NEWNYM signal, clear the client-side DNS
2773 cache too. Otherwise we continue to act on previous information.
2776 - Avoid a memory corruption bug when creating a hash table for
2778 - Avoid possibility of controller-triggered crash when misusing
2779 certain commands from a v0 controller on platforms that do not
2780 handle printf("%s",NULL) gracefully.
2781 - Avoid infinite loop on unexpected controller input.
2782 - Don't log spurious warnings when we see a circuit close reason we
2783 don't recognize; it's probably just from a newer version of Tor.
2784 - Add Vidalia to the OS X uninstaller script, so when we uninstall
2785 Tor/Privoxy we also uninstall Vidalia.
2788 Changes in version 0.1.1.24 - 2006-09-29
2790 - Allow really slow clients to not hang up five minutes into their
2791 directory downloads (suggested by Adam J. Richter).
2792 - Fix major performance regression from 0.1.0.x: instead of checking
2793 whether we have enough directory information every time we want to
2794 do something, only check when the directory information has changed.
2795 This should improve client CPU usage by 25-50%.
2796 - Don't crash if, after a server has been running for a while,
2797 it can't resolve its hostname.
2798 - When a client asks us to resolve (not connect to) an address,
2799 and we have a cached answer, give them the cached answer.
2800 Previously, we would give them no answer at all.
2803 - Allow Tor to start when RunAsDaemon is set but no logs are set.
2804 - Don't crash when the controller receives a third argument to an
2805 "extendcircuit" request.
2806 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
2807 response; fix error code when "getinfo dir/status/" fails.
2808 - Fix configure.in to not produce broken configure files with
2809 more recent versions of autoconf. Thanks to Clint for his auto*
2811 - Fix security bug on NetBSD that could allow someone to force
2812 uninitialized RAM to be sent to a server's DNS resolver. This
2813 only affects NetBSD and other platforms that do not bounds-check
2815 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
2816 methods: these are known to be buggy.
2817 - If we're a directory mirror and we ask for "all" network status
2818 documents, we would discard status documents from authorities
2822 Changes in version 0.1.1.23 - 2006-07-30
2824 - Fast Tor servers, especially exit nodes, were triggering asserts
2825 due to a bug in handling the list of pending DNS resolves. Some
2826 bugs still remain here; we're hunting them.
2827 - Entry guards could crash clients by sending unexpected input.
2828 - More fixes on reachability testing: if you find yourself reachable,
2829 then don't ever make any client requests (so you stop predicting
2830 circuits), then hup or have your clock jump, then later your IP
2831 changes, you won't think circuits are working, so you won't try to
2832 test reachability, so you won't publish.
2835 - Avoid a crash if the controller does a resetconf firewallports
2836 and then a setconf fascistfirewall=1.
2837 - Avoid an integer underflow when the dir authority decides whether
2838 a router is stable: we might wrongly label it stable, and compute
2839 a slightly wrong median stability, when a descriptor is published
2841 - Fix a place where we might trigger an assert if we can't build our
2842 own server descriptor yet.
2845 Changes in version 0.1.1.22 - 2006-07-05
2847 - Fix a big bug that was causing servers to not find themselves
2848 reachable if they changed IP addresses. Since only 0.1.1.22+
2849 servers can do reachability testing correctly, now we automatically
2850 make sure to test via one of these.
2851 - Fix to allow clients and mirrors to learn directory info from
2852 descriptor downloads that get cut off partway through.
2853 - Directory authorities had a bug in deciding if a newly published
2854 descriptor was novel enough to make everybody want a copy -- a few
2855 servers seem to be publishing new descriptors many times a minute.
2857 - Fix a rare bug that was causing some servers to complain about
2858 "closing wedged cpuworkers" and skip some circuit create requests.
2859 - Make the Exit flag in directory status documents actually work.
2862 Changes in version 0.1.1.21 - 2006-06-10
2863 o Crash and assert fixes from 0.1.1.20:
2864 - Fix a rare crash on Tor servers that have enabled hibernation.
2865 - Fix a seg fault on startup for Tor networks that use only one
2866 directory authority.
2867 - Fix an assert from a race condition that occurs on Tor servers
2868 while exiting, where various threads are trying to log that they're
2869 exiting, and delete the logs, at the same time.
2870 - Make our unit tests pass again on certain obscure platforms.
2873 - Add support for building SUSE RPM packages.
2874 - Speed up initial bootstrapping for clients: if we are making our
2875 first ever connection to any entry guard, then don't mark it down
2877 - When only one Tor server in the network is labelled as a guard,
2878 and we've already picked him, we would cycle endlessly picking him
2879 again, being unhappy about it, etc. Now we specifically exclude
2880 current guards when picking a new guard.
2881 - Servers send create cells more reliably after the TLS connection
2882 is established: we were sometimes forgetting to send half of them
2883 when we had more than one pending.
2884 - If we get a create cell that asks us to extend somewhere, but the
2885 Tor server there doesn't match the expected digest, we now send
2886 a destroy cell back, rather than silently doing nothing.
2887 - Make options->RedirectExit work again.
2888 - Make cookie authentication for the controller work again.
2889 - Stop being picky about unusual characters in the arguments to
2890 mapaddress. It's none of our business.
2891 - Add a new config option "TestVia" that lets you specify preferred
2892 middle hops to use for test circuits. Perhaps this will let me
2893 debug the reachability problems better.
2895 o Log / documentation fixes:
2896 - If we're a server and some peer has a broken TLS certificate, don't
2897 log about it unless ProtocolWarnings is set, i.e., we want to hear
2898 about protocol violations by others.
2899 - Fix spelling of VirtualAddrNetwork in man page.
2900 - Add a better explanation at the top of the autogenerated torrc file
2901 about what happened to our old torrc.
2904 Changes in version 0.1.1.20 - 2006-05-23
2905 o Crash and assert fixes from 0.1.0.17:
2906 - Fix assert bug in close_logs() on exit: when we close and delete
2907 logs, remove them all from the global "logfiles" list.
2908 - Fix an assert error when we're out of space in the connection_list
2909 and we try to post a hidden service descriptor (reported by Peter
2911 - Fix a rare assert error when we've tried all intro points for
2912 a hidden service and we try fetching the service descriptor again:
2913 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
2914 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
2915 out and refuse the setconf if it would fail.
2916 - If you specify a relative torrc path and you set RunAsDaemon in
2917 your torrc, then it chdir()'s to the new directory. If you then
2918 HUP, it tries to load the new torrc location, fails, and exits.
2919 The fix: no longer allow a relative path to torrc when using -f.
2920 - Check for integer overflows in more places, when adding elements
2921 to smartlists. This could possibly prevent a buffer overflow
2922 on malicious huge inputs.
2924 o Security fixes, major:
2925 - When we're printing strings from the network, don't try to print
2926 non-printable characters. Now we're safer against shell escape
2927 sequence exploits, and also against attacks to fool users into
2928 misreading their logs.
2929 - Implement entry guards: automatically choose a handful of entry
2930 nodes and stick with them for all circuits. Only pick new guards
2931 when the ones you have are unsuitable, and if the old guards
2932 become suitable again, switch back. This will increase security
2933 dramatically against certain end-point attacks. The EntryNodes
2934 config option now provides some hints about which entry guards you
2935 want to use most; and StrictEntryNodes means to only use those.
2936 Fixes CVE-2006-0414.
2937 - Implement exit enclaves: if we know an IP address for the
2938 destination, and there's a running Tor server at that address
2939 which allows exit to the destination, then extend the circuit to
2940 that exit first. This provides end-to-end encryption and end-to-end
2941 authentication. Also, if the user wants a .exit address or enclave,
2942 use 4 hops rather than 3, and cannibalize a general circ for it
2944 - Obey our firewall options more faithfully:
2945 . If we can't get to a dirserver directly, try going via Tor.
2946 . Don't ever try to connect (as a client) to a place our
2947 firewall options forbid.
2948 . If we specify a proxy and also firewall options, obey the
2949 firewall options even when we're using the proxy: some proxies
2950 can only proxy to certain destinations.
2951 - Make clients regenerate their keys when their IP address changes.
2952 - For the OS X package's modified privoxy config file, comment
2953 out the "logfile" line so we don't log everything passed
2955 - Our TLS handshakes were generating a single public/private
2956 keypair for the TLS context, rather than making a new one for
2957 each new connection. Oops. (But we were still rotating them
2958 periodically, so it's not so bad.)
2959 - When we were cannibalizing a circuit with a particular exit
2960 node in mind, we weren't checking to see if that exit node was
2961 already present earlier in the circuit. Now we are.
2962 - Require server descriptors to list IPv4 addresses -- hostnames
2963 are no longer allowed. This also fixes potential vulnerabilities
2964 to servers providing hostnames as their address and then
2965 preferentially resolving them so they can partition users.
2966 - Our logic to decide if the OR we connected to was the right guy
2967 was brittle and maybe open to a mitm for invalid routers.
2969 o Security fixes, minor:
2970 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
2971 Ian Goldberg can prove things about our handshake protocol more
2973 - Make directory authorities generate a separate "guard" flag to
2974 mean "would make a good entry guard". Clients now honor the
2975 is_guard flag rather than looking at is_fast or is_stable.
2976 - Try to list MyFamily elements by key, not by nickname, and warn
2977 if we've not heard of a server.
2978 - Start using RAND_bytes rather than RAND_pseudo_bytes from
2979 OpenSSL. Also, reseed our entropy every hour, not just at
2980 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
2981 - Refuse server descriptors where the fingerprint line doesn't match
2982 the included identity key. Tor doesn't care, but other apps (and
2983 humans) might actually be trusting the fingerprint line.
2984 - We used to kill the circuit when we receive a relay command we
2985 don't recognize. Now we just drop that cell.
2986 - Fix a bug found by Lasse Overlier: when we were making internal
2987 circuits (intended to be cannibalized later for rendezvous and
2988 introduction circuits), we were picking them so that they had
2989 useful exit nodes. There was no need for this, and it actually
2990 aids some statistical attacks.
2991 - Start treating internal circuits and exit circuits separately.
2992 It's important to keep them separate because internal circuits
2993 have their last hops picked like middle hops, rather than like
2994 exit hops. So exiting on them will break the user's expectations.
2995 - Fix a possible way to DoS dirservers.
2996 - When the client asked for a rendezvous port that the hidden
2997 service didn't want to provide, we were sending an IP address
2998 back along with the end cell. Fortunately, it was zero. But stop
3001 o Packaging improvements:
3002 - Implement --with-libevent-dir option to ./configure. Improve
3003 search techniques to find libevent, and use those for openssl too.
3004 - Fix a couple of bugs in OpenSSL detection. Deal better when
3005 there are multiple SSLs installed with different versions.
3006 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
3007 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
3009 - Make unit tests (and other invocations that aren't the real Tor)
3010 run without launching listeners, creating subdirectories, and so on.
3011 - The OS X installer was adding a symlink for tor_resolve but
3012 the binary was called tor-resolve (reported by Thomas Hardly).
3013 - Now we can target arch and OS in rpm builds (contributed by
3014 Phobos). Also make the resulting dist-rpm filename match the
3016 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
3017 if you log to syslog and want something other than LOG_DAEMON.
3018 - Fix the torify (tsocks) config file to not use Tor for localhost
3020 - Start shipping socks-extensions.txt, tor-doc-unix.html,
3021 tor-doc-server.html, and stylesheet.css in the tarball.
3022 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
3023 They are useless now.
3024 - Add Peter Palfrader's contributed check-tor script. It lets you
3025 easily check whether a given server (referenced by nickname)
3026 is reachable by you.
3027 - Add BSD-style contributed startup script "rc.subr" from Peter
3030 o Directory improvements -- new directory protocol:
3031 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
3032 - Authorities and caches publish individual descriptors (by
3033 digest, by fingerprint, by "all", and by "tell me yours").
3034 - Clients don't download or use the old directory anymore. Now they
3035 download network-statuses from the directory authorities, and
3036 fetch individual server descriptors as needed from mirrors.
3037 - Clients don't download descriptors of non-running servers.
3038 - Download descriptors by digest, not by fingerprint. Caches try to
3039 download all listed digests from authorities; clients try to
3040 download "best" digests from caches. This avoids partitioning
3041 and isolating attacks better.
3042 - Only upload a new server descriptor when options change, 18
3043 hours have passed, uptime is reset, or bandwidth changes a lot.
3044 - Directory authorities silently throw away new descriptors that
3045 haven't changed much if the timestamps are similar. We do this to
3046 tolerate older Tor servers that upload a new descriptor every 15
3047 minutes. (It seemed like a good idea at the time.)
3048 - Clients choose directory servers from the network status lists,
3049 not from their internal list of router descriptors. Now they can
3050 go to caches directly rather than needing to go to authorities
3051 to bootstrap the first set of descriptors.
3052 - When picking a random directory, prefer non-authorities if any
3054 - Add a new flag to network-status indicating whether the server
3055 can answer v2 directory requests too.
3056 - Directory mirrors now cache up to 16 unrecognized network-status
3057 docs, so new directory authorities will be cached too.
3058 - Stop parsing, storing, or using running-routers output (but
3059 mirrors still cache and serve it).
3060 - Clients consider a threshold of "versioning" directory authorities
3061 before deciding whether to warn the user that he's obsolete.
3062 - Authorities publish separate sorted lists of recommended versions
3063 for clients and for servers.
3064 - Change DirServers config line to note which dirs are v1 authorities.
3065 - Put nicknames on the DirServer line, so we can refer to them
3066 without requiring all our users to memorize their IP addresses.
3067 - Remove option when getting directory cache to see whether they
3068 support running-routers; they all do now. Replace it with one
3069 to see whether caches support v2 stuff.
3070 - Stop listing down or invalid nodes in the v1 directory. This
3071 reduces its bulk by about 1/3, and reduces load on mirrors.
3072 - Mirrors no longer cache the v1 directory as often.
3073 - If we as a directory mirror don't know of any v1 directory
3074 authorities, then don't try to cache any v1 directories.
3076 o Other directory improvements:
3077 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
3078 fifth authoritative directory servers.
3079 - Directory authorities no longer require an open connection from
3080 a server to consider him "reachable". We need this change because
3081 when we add new directory authorities, old servers won't know not
3083 - Dir authorities now do their own external reachability testing
3084 of each server, and only list as running the ones they found to
3085 be reachable. We also send back warnings to the server's logs if
3086 it uploads a descriptor that we already believe is unreachable.
3087 - Spread the directory authorities' reachability testing over the
3088 entire testing interval, so we don't try to do 500 TLS's at once
3090 - Make the "stable" router flag in network-status be the median of
3091 the uptimes of running valid servers, and make clients pay
3092 attention to the network-status flags. Thus the cutoff adapts
3093 to the stability of the network as a whole, making IRC, IM, etc
3094 connections more reliable.
3095 - Make the v2 dir's "Fast" flag based on relative capacity, just
3096 like "Stable" is based on median uptime. Name everything in the
3097 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
3098 - Retry directory requests if we fail to get an answer we like
3099 from a given dirserver (we were retrying before, but only if
3100 we fail to connect).
3101 - Return a robots.txt on our dirport to discourage google indexing.
3103 o Controller protocol improvements:
3104 - Revised controller protocol (version 1) that uses ascii rather
3105 than binary: tor/doc/control-spec.txt. Add supporting libraries
3106 in python and java and c# so you can use the controller from your
3107 applications without caring how our protocol works.
3108 - Allow the DEBUG controller event to work again. Mark certain log
3109 entries as "don't tell this to controllers", so we avoid cycles.
3110 - New controller function "getinfo accounting", to ask how
3111 many bytes we've used in this time period.
3112 - Add a "resetconf" command so you can set config options like
3113 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
3114 a config option in the torrc with no value, then it clears it
3115 entirely (rather than setting it to its default).
3116 - Add a "getinfo config-file" to tell us where torrc is. Also
3117 expose guard nodes, config options/names.
3118 - Add a "quit" command (when when using the controller manually).
3119 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
3120 stop using any currently-dirty circuits for new streams, so we
3121 don't link new actions to old actions. This also occurs on HUP
3123 - If we would close a stream early (e.g. it asks for a .exit that
3124 we know would refuse it) but the LeaveStreamsUnattached config
3125 option is set by the controller, then don't close it.
3126 - Add a new controller event type "authdir_newdescs" that allows
3127 controllers to get all server descriptors that were uploaded to
3128 a router in its role as directory authority.
3129 - New controller option "getinfo desc/all-recent" to fetch the
3130 latest server descriptor for every router that Tor knows about.
3131 - Fix the controller's "attachstream 0" command to treat conn like
3132 it just connected, doing address remapping, handling .exit and
3133 .onion idioms, and so on. Now we're more uniform in making sure
3134 that the controller hears about new and closing connections.
3135 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
3136 the controller. Also, rotate dns and cpu workers if the controller
3137 changes options that will affect them; and initialize the dns
3138 worker cache tree whether or not we start out as a server.
3139 - Add a new circuit purpose 'controller' to let the controller ask
3140 for a circuit that Tor won't try to use. Extend the "extendcircuit"
3141 controller command to let you specify the purpose if you're starting
3142 a new circuit. Add a new "setcircuitpurpose" controller command to
3143 let you change a circuit's purpose after it's been created.
3144 - Let the controller ask for "getinfo dir/server/foo" so it can ask
3145 directly rather than connecting to the dir port. "getinfo
3146 dir/status/foo" also works, but currently only if your DirPort
3148 - Let the controller tell us about certain router descriptors
3149 that it doesn't want Tor to use in circuits. Implement
3150 "setrouterpurpose" and modify "+postdescriptor" to do this.
3151 - If the controller's *setconf commands fail, collect an error
3152 message in a string and hand it back to the controller -- don't
3153 just tell them to go read their logs.
3155 o Scalability, resource management, and performance:
3156 - Fix a major load balance bug: we were round-robin reading in 16 KB
3157 chunks, and servers with bandwidthrate of 20 KB, while downloading
3158 a 600 KB directory, would starve their other connections. Now we
3159 try to be a bit more fair.
3160 - Be more conservative about whether to advertise our DirPort.
3161 The main change is to not advertise if we're running at capacity
3162 and either a) we could hibernate ever or b) our capacity is low
3163 and we're using a default DirPort.
3164 - We weren't cannibalizing circuits correctly for
3165 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
3166 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
3167 build those from scratch. This should make hidden services faster.
3168 - Predict required circuits better, with an eye toward making hidden
3169 services faster on the service end.
3170 - Compress exit policies even more: look for duplicate lines and
3172 - Generate 18.0.0.0/8 address policy format in descs when we can;
3173 warn when the mask is not reducible to a bit-prefix.
3174 - There used to be two ways to specify your listening ports in a
3175 server descriptor: on the "router" line and with a separate "ports"
3176 line. Remove support for the "ports" line.
3177 - Reduce memory requirements in our structs by changing the order
3178 of fields. Replace balanced trees with hash tables. Inline
3179 bottleneck smartlist functions. Add a "Map from digest to void*"
3180 abstraction so we can do less hex encoding/decoding, and use it
3181 in router_get_by_digest(). Many other CPU and memory improvements.
3182 - Allow tor_gzip_uncompress to extract as much as possible from
3183 truncated compressed data. Try to extract as many
3184 descriptors as possible from truncated http responses (when
3185 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
3186 - Make circ->onionskin a pointer, not a static array. moria2 was using
3187 125000 circuit_t's after it had been up for a few weeks, which
3188 translates to 20+ megs of wasted space.
3189 - The private half of our EDH handshake keys are now chosen out
3190 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
3191 - Stop doing the complex voodoo overkill checking for insecure
3192 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
3193 - Do round-robin writes for TLS of at most 16 kB per write. This
3194 might be more fair on loaded Tor servers.
3195 - Do not use unaligned memory access on alpha, mips, or mipsel.
3196 It *works*, but is very slow, so we treat them as if it doesn't.
3198 o Other bugfixes and improvements:
3199 - Start storing useful information to $DATADIR/state, so we can
3200 remember things across invocations of Tor. Retain unrecognized
3201 lines so we can be forward-compatible, and write a TorVersion line
3202 so we can be backward-compatible.
3203 - If ORPort is set, Address is not explicitly set, and our hostname
3204 resolves to a private IP address, try to use an interface address
3205 if it has a public address. Now Windows machines that think of
3206 themselves as localhost can guess their address.
3207 - Regenerate our local descriptor if it's dirty and we try to use
3208 it locally (e.g. if it changes during reachability detection).
3209 This was causing some Tor servers to keep publishing the same
3210 initial descriptor forever.
3211 - Tor servers with dynamic IP addresses were needing to wait 18
3212 hours before they could start doing reachability testing using
3213 the new IP address and ports. This is because they were using
3214 the internal descriptor to learn what to test, yet they were only
3215 rebuilding the descriptor once they decided they were reachable.
3216 - It turns out we couldn't bootstrap a network since we added
3217 reachability detection in 0.1.0.1-rc. Good thing the Tor network
3218 has never gone down. Add an AssumeReachable config option to let
3219 servers and authorities bootstrap. When we're trying to build a
3220 high-uptime or high-bandwidth circuit but there aren't enough
3221 suitable servers, try being less picky rather than simply failing.
3222 - Newly bootstrapped Tor networks couldn't establish hidden service
3223 circuits until they had nodes with high uptime. Be more tolerant.
3224 - Really busy servers were keeping enough circuits open on stable
3225 connections that they were wrapping around the circuit_id
3226 space. (It's only two bytes.) This exposed a bug where we would
3227 feel free to reuse a circuit_id even if it still exists but has
3228 been marked for close. Try to fix this bug. Some bug remains.
3229 - When we fail to bind or listen on an incoming or outgoing
3230 socket, we now close it before refusing, rather than just
3231 leaking it. (Thanks to Peter Palfrader for finding.)
3232 - Fix a file descriptor leak in start_daemon().
3233 - On Windows, you can't always reopen a port right after you've
3234 closed it. So change retry_listeners() to only close and re-open
3235 ports that have changed.
3236 - Workaround a problem with some http proxies that refuse GET
3237 requests that specify "Content-Length: 0". Reported by Adrian.
3238 - Recover better from TCP connections to Tor servers that are
3239 broken but don't tell you (it happens!); and rotate TLS
3240 connections once a week.
3241 - Fix a scary-looking but apparently harmless bug where circuits
3242 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
3243 servers, and never switch to state CIRCUIT_STATE_OPEN.
3244 - Check for even more Windows version flags when writing the platform
3245 string in server descriptors, and note any we don't recognize.
3246 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
3247 get a better idea of why their circuits failed. Not used yet.
3248 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
3249 We don't use them yet, but maybe one day our DNS resolver will be
3250 able to discover them.
3251 - Let people type "tor --install" as well as "tor -install" when they
3252 want to make it an NT service.
3253 - Looks like we were never delivering deflated (i.e. compressed)
3254 running-routers lists, even when asked. Oops.
3255 - We were leaking some memory every time the client changed IPs.
3256 - Clean up more of the OpenSSL memory when exiting, so we can detect
3257 memory leaks better.
3258 - Never call free() on tor_malloc()d memory. This will help us
3259 use dmalloc to detect memory leaks.
3260 - Some Tor servers process billions of cells per day. These
3261 statistics are now uint64_t's.
3262 - Check [X-]Forwarded-For headers in HTTP requests when generating
3263 log messages. This lets people run dirservers (and caches) behind
3264 Apache but still know which IP addresses are causing warnings.
3265 - Fix minor integer overflow in calculating when we expect to use up
3266 our bandwidth allocation before hibernating.
3267 - Lower the minimum required number of file descriptors to 1000,
3268 so we can have some overhead for Valgrind on Linux, where the
3269 default ulimit -n is 1024.
3270 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
3271 and its existence is confusing some users.
3273 o Config option fixes:
3274 - Add a new config option ExitPolicyRejectPrivate which defaults
3275 to on. Now all exit policies will begin with rejecting private
3276 addresses, unless the server operator explicitly turns it off.
3277 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
3278 - Add new ReachableORAddresses and ReachableDirAddresses options
3279 that understand address policies. FascistFirewall is now a synonym
3280 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
3281 - Start calling it FooListenAddress rather than FooBindAddress,
3282 since few of our users know what it means to bind an address
3284 - If the user gave Tor an odd number of command-line arguments,
3285 we were silently ignoring the last one. Now we complain and fail.
3286 This wins the oldest-bug prize -- this bug has been present since
3287 November 2002, as released in Tor 0.0.0.
3288 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
3289 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
3290 it would silently ignore the 6668.
3291 - If we get a linelist or linelist_s config option from the torrc,
3292 e.g. ExitPolicy, and it has no value, warn and skip rather than
3293 silently resetting it to its default.
3294 - Setconf was appending items to linelists, not clearing them.
3295 - Add MyFamily to torrc.sample in the server section, so operators
3296 will be more likely to learn that it exists.
3297 - Make ContactInfo mandatory for authoritative directory servers.
3298 - MaxConn has been obsolete for a while now. Document the ConnLimit
3299 config option, which is a *minimum* number of file descriptors
3300 that must be available else Tor refuses to start.
3301 - Get rid of IgnoreVersion undocumented config option, and make us
3302 only warn, never exit, when we're running an obsolete version.
3303 - Make MonthlyAccountingStart config option truly obsolete now.
3304 - Correct the man page entry on TrackHostExitsExpire.
3305 - Let directory authorities start even if they don't specify an
3306 Address config option.
3307 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
3308 reflect the updated flags in our v2 dir protocol.
3310 o Config option features:
3311 - Add a new config option FastFirstHopPK (on by default) so clients
3312 do a trivial crypto handshake for their first hop, since TLS has
3313 already taken care of confidentiality and authentication.
3314 - Let the user set ControlListenAddress in the torrc. This can be
3315 dangerous, but there are some cases (like a secured LAN) where it
3317 - New config options to help controllers: FetchServerDescriptors
3318 and FetchHidServDescriptors for whether to fetch server
3319 info and hidserv info or let the controller do it, and
3320 PublishServerDescriptor and PublishHidServDescriptors.
3321 - Also let the controller set the __AllDirActionsPrivate config
3322 option if you want all directory fetches/publishes to happen via
3323 Tor (it assumes your controller bootstraps your circuits).
3324 - Add "HardwareAccel" config option: support for crypto hardware
3325 accelerators via OpenSSL. Off by default, until we find somebody
3326 smart who can test it for us. (It appears to produce seg faults
3327 in at least some cases.)
3328 - New config option "AuthDirRejectUnlisted" for directory authorities
3329 as a panic button: if we get flooded with unusable servers we can
3330 revert to only listing servers in the approved-routers file.
3331 - Directory authorities can now reject/invalidate by key and IP,
3332 with the config options "AuthDirInvalid" and "AuthDirReject", or
3333 by marking a fingerprint as "!reject" or "!invalid" (as its
3334 nickname) in the approved-routers file. This is useful since
3335 currently we automatically list servers as running and usable
3336 even if we know they're jerks.
3337 - Add a new config option TestSocks so people can see whether their
3338 applications are using socks4, socks4a, socks5-with-ip, or
3339 socks5-with-fqdn. This way they don't have to keep mucking
3340 with tcpdump and wondering if something got cached somewhere.
3341 - Add "private:*" as an alias in configuration for policies. Now
3342 you can simplify your exit policy rather than needing to list
3343 every single internal or nonroutable network space.
3344 - Accept "private:*" in routerdesc exit policies; not generated yet
3345 because older Tors do not understand it.
3346 - Add configuration option "V1AuthoritativeDirectory 1" which
3347 moria1, moria2, and tor26 have set.
3348 - Implement an option, VirtualAddrMask, to set which addresses
3349 get handed out in response to mapaddress requests. This works
3350 around a bug in tsocks where 127.0.0.0/8 is never socksified.
3351 - Add a new config option FetchUselessDescriptors, off by default,
3352 for when you plan to run "exitlist" on your client and you want
3353 to know about even the non-running descriptors.
3354 - SocksTimeout: How long do we let a socks connection wait
3355 unattached before we fail it?
3356 - CircuitBuildTimeout: Cull non-open circuits that were born
3357 at least this many seconds ago.
3358 - CircuitIdleTimeout: Cull open clean circuits that were born
3359 at least this many seconds ago.
3360 - New config option SafeSocks to reject all application connections
3361 using unsafe socks protocols. Defaults to off.
3363 o Improved and clearer log messages:
3364 - Reduce clutter in server logs. We're going to try to make
3365 them actually usable now. New config option ProtocolWarnings that
3366 lets you hear about how _other Tors_ are breaking the protocol. Off
3368 - Divide log messages into logging domains. Once we put some sort
3369 of interface on this, it will let people looking at more verbose
3370 log levels specify the topics they want to hear more about.
3371 - Log server fingerprint on startup, so new server operators don't
3372 have to go hunting around their filesystem for it.
3373 - Provide dire warnings to any users who set DirServer manually;
3374 move it out of torrc.sample and into torrc.complete.
3375 - Make the log message less scary when all the dirservers are
3376 temporarily unreachable.
3377 - When tor_socketpair() fails in Windows, give a reasonable
3378 Windows-style errno back.
3379 - Improve tor_gettimeofday() granularity on windows.
3380 - We were printing the number of idle dns workers incorrectly when
3382 - Handle duplicate lines in approved-routers files without warning.
3383 - We were whining about using socks4 or socks5-with-local-lookup
3384 even when it's an IP address in the "virtual" range we designed
3385 exactly for this case.
3386 - Check for named servers when looking them up by nickname;
3387 warn when we're calling a non-named server by its nickname;
3388 don't warn twice about the same name.
3389 - Downgrade the dirserver log messages when whining about
3391 - Correct "your server is reachable" log entries to indicate that
3392 it was self-testing that told us so.
3393 - If we're trying to be a Tor server and running Windows 95/98/ME
3394 as a server, explain that we'll likely crash.
3395 - Provide a more useful warn message when our onion queue gets full:
3396 the CPU is too slow or the exit policy is too liberal.
3397 - Don't warn when we receive a 503 from a dirserver/cache -- this
3398 will pave the way for them being able to refuse if they're busy.
3399 - When we fail to bind a listener, try to provide a more useful
3400 log message: e.g., "Is Tor already running?"
3401 - Only start testing reachability once we've established a
3402 circuit. This will make startup on dir authorities less noisy.
3403 - Don't try to upload hidden service descriptors until we have
3404 established a circuit.
3405 - Tor didn't warn when it failed to open a log file.
3406 - Warn when listening on a public address for socks. We suspect a
3407 lot of people are setting themselves up as open socks proxies,
3408 and they have no idea that jerks on the Internet are using them,
3409 since they simply proxy the traffic into the Tor network.
3410 - Give a useful message when people run Tor as the wrong user,
3411 rather than telling them to start chowning random directories.
3412 - Fix a harmless bug that was causing Tor servers to log
3413 "Got an end because of misc error, but we're not an AP. Closing."
3414 - Fix wrong log message when you add a "HiddenServiceNodes" config
3415 line without any HiddenServiceDir line (reported by Chris Thomas).
3416 - Directory authorities now stop whining so loudly about bad
3417 descriptors that they fetch from other dirservers. So when there's
3418 a log complaint, it's for sure from a freshly uploaded descriptor.
3419 - When logging via syslog, include the pid whenever we provide
3420 a log entry. Suggested by Todd Fries.
3421 - When we're shutting down and we do something like try to post a
3422 server descriptor or rendezvous descriptor, don't complain that
3423 we seem to be unreachable. Of course we are, we're shutting down.
3424 - Change log line for unreachability to explicitly suggest /etc/hosts
3425 as the culprit. Also make it clearer what IP address and ports we're
3426 testing for reachability.
3427 - Put quotes around user-supplied strings when logging so users are
3428 more likely to realize if they add bad characters (like quotes)
3430 - NT service patch from Matt Edman to improve error messages on Win32.
3433 Changes in version 0.1.0.17 - 2006-02-17
3434 o Crash bugfixes on 0.1.0.x:
3435 - When servers with a non-zero DirPort came out of hibernation,
3436 sometimes they would trigger an assert.
3438 o Other important bugfixes:
3439 - On platforms that don't have getrlimit (like Windows), we were
3440 artificially constraining ourselves to a max of 1024
3441 connections. Now just assume that we can handle as many as 15000
3442 connections. Hopefully this won't cause other problems.
3444 o Backported features:
3445 - When we're a server, a client asks for an old-style directory,
3446 and our write bucket is empty, don't give it to him. This way
3447 small servers can continue to serve the directory *sometimes*,
3448 without getting overloaded.
3449 - Whenever you get a 503 in response to a directory fetch, try
3450 once more. This will become important once servers start sending
3451 503's whenever they feel busy.
3452 - Fetch a new directory every 120 minutes, not every 40 minutes.
3453 Now that we have hundreds of thousands of users running the old
3454 directory algorithm, it's starting to hurt a lot.
3455 - Bump up the period for forcing a hidden service descriptor upload
3456 from 20 minutes to 1 hour.
3459 Changes in version 0.1.0.16 - 2006-01-02
3460 o Crash bugfixes on 0.1.0.x:
3461 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
3462 corrupting the heap, losing FDs, or crashing when we need to resize
3463 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
3464 - It turns out sparc64 platforms crash on unaligned memory access
3465 too -- so detect and avoid this.
3466 - Handle truncated compressed data correctly (by detecting it and
3468 - Fix possible-but-unlikely free(NULL) in control.c.
3469 - When we were closing connections, there was a rare case that
3470 stomped on memory, triggering seg faults and asserts.
3471 - Avoid potential infinite recursion when building a descriptor. (We
3472 don't know that it ever happened, but better to fix it anyway.)
3473 - We were neglecting to unlink marked circuits from soon-to-close OR
3474 connections, which caused some rare scribbling on freed memory.
3475 - Fix a memory stomping race bug when closing the joining point of two
3476 rendezvous circuits.
3477 - Fix an assert in time parsing found by Steven Murdoch.
3479 o Other bugfixes on 0.1.0.x:
3480 - When we're doing reachability testing, provide more useful log
3481 messages so the operator knows what to expect.
3482 - Do not check whether DirPort is reachable when we are suppressing
3483 advertising it because of hibernation.
3484 - When building with -static or on Solaris, we sometimes needed -ldl.
3485 - One of the dirservers (tor26) changed its IP address.
3486 - When we're deciding whether a stream has enough circuits around
3487 that can handle it, count the freshly dirty ones and not the ones
3488 that are so dirty they won't be able to handle it.
3489 - When we're expiring old circuits, we had a logic error that caused
3490 us to close new rendezvous circuits rather than old ones.
3491 - Give a more helpful log message when you try to change ORPort via
3492 the controller: you should upgrade Tor if you want that to work.
3493 - We were failing to parse Tor versions that start with "Tor ".
3494 - Tolerate faulty streams better: when a stream fails for reason
3495 exitpolicy, stop assuming that the router is lying about his exit
3496 policy. When a stream fails for reason misc, allow it to retry just
3497 as if it was resolvefailed. When a stream has failed three times,
3498 reset its failure count so we can try again and get all three tries.
3501 Changes in version 0.1.0.15 - 2005-09-23
3502 o Bugfixes on 0.1.0.x:
3503 - Reject ports 465 and 587 (spam targets) in default exit policy.
3504 - Don't crash when we don't have any spare file descriptors and we
3505 try to spawn a dns or cpu worker.
3506 - Get rid of IgnoreVersion undocumented config option, and make us
3507 only warn, never exit, when we're running an obsolete version.
3508 - Don't try to print a null string when your server finds itself to
3509 be unreachable and the Address config option is empty.
3510 - Make the numbers in read-history and write-history into uint64s,
3511 so they don't overflow and publish negatives in the descriptor.
3512 - Fix a minor memory leak in smartlist_string_remove().
3513 - We were only allowing ourselves to upload a server descriptor at
3514 most every 20 minutes, even if it changed earlier than that.
3515 - Clean up log entries that pointed to old URLs.
3518 Changes in version 0.1.0.14 - 2005-08-08
3519 o Bugfixes on 0.1.0.x:
3520 - Fix the other half of the bug with crypto handshakes
3522 - Fix an assert trigger if you send a 'signal term' via the
3523 controller when it's listening for 'event info' messages.
3526 Changes in version 0.1.0.13 - 2005-08-04
3527 o Bugfixes on 0.1.0.x:
3528 - Fix a critical bug in the security of our crypto handshakes.
3529 - Fix a size_t underflow in smartlist_join_strings2() that made
3530 it do bad things when you hand it an empty smartlist.
3531 - Fix Windows installer to ship Tor license (thanks to Aphex for
3532 pointing out this oversight) and put a link to the doc directory
3534 - Explicitly set no-unaligned-access for sparc: it turns out the
3535 new gcc's let you compile broken code, but that doesn't make it
3539 Changes in version 0.1.0.12 - 2005-07-18
3540 o New directory servers:
3541 - tor26 has changed IP address.
3543 o Bugfixes on 0.1.0.x:
3544 - Fix a possible double-free in tor_gzip_uncompress().
3545 - When --disable-threads is set, do not search for or link against
3547 - Don't trigger an assert if an authoritative directory server
3548 claims its dirport is 0.
3549 - Fix bug with removing Tor as an NT service: some people were
3550 getting "The service did not return an error." Thanks to Matt
3554 Changes in version 0.1.0.11 - 2005-06-30
3555 o Bugfixes on 0.1.0.x:
3556 - Fix major security bug: servers were disregarding their
3557 exit policies if clients behaved unexpectedly.
3558 - Make OS X init script check for missing argument, so we don't
3559 confuse users who invoke it incorrectly.
3560 - Fix a seg fault in "tor --hash-password foo".
3561 - The MAPADDRESS control command was broken.
3564 Changes in version 0.1.0.10 - 2005-06-14
3566 - Make NT services work and start on startup on Win32 (based on
3567 patch by Matt Edman). See the FAQ entry for details.
3568 - Make 'platform' string in descriptor more accurate for Win32
3569 servers, so it's not just "unknown platform".
3570 - REUSEADDR on normal platforms means you can rebind to the port
3571 right after somebody else has let it go. But REUSEADDR on Win32
3572 means you can bind to the port _even when somebody else already
3573 has it bound_! So, don't do that on Win32.
3574 - Clean up the log messages when starting on Win32 with no config
3576 - Allow seeding the RNG on Win32 even when you're not running as
3577 Administrator. If seeding the RNG on Win32 fails, quit.
3579 o Assert / crash bugs:
3580 - Refuse relay cells that claim to have a length larger than the
3581 maximum allowed. This prevents a potential attack that could read
3582 arbitrary memory (e.g. keys) from an exit server's process
3584 - If unofficial Tor clients connect and send weird TLS certs, our
3585 Tor server triggers an assert. Stop asserting, and start handling
3586 TLS errors better in other situations too.
3587 - Fix a race condition that can trigger an assert when we have a
3588 pending create cell and an OR connection attempt fails.
3591 - Use pthreads for worker processes rather than forking. This was
3592 forced because when we forked, we ended up wasting a lot of
3593 duplicate ram over time.
3594 - Also switch to foo_r versions of some library calls to allow
3595 reentry and threadsafeness.
3596 - Implement --disable-threads configure option. Disable threads on
3597 netbsd and openbsd by default, because they have no reentrant
3598 resolver functions (!), and on solaris since it has other
3600 - Fix possible bug on threading platforms (e.g. win32) which was
3601 leaking a file descriptor whenever a cpuworker or dnsworker died.
3602 - Fix a minor memory leak when somebody establishes an introduction
3603 point at your Tor server.
3604 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
3606 - Add ./configure --with-dmalloc option, to track memory leaks.
3607 - And try to free all memory on closing, so we can detect what
3610 o Protocol correctness:
3611 - When we've connected to an OR and handshaked but didn't like
3612 the result, we were closing the conn without sending destroy
3613 cells back for pending circuits. Now send those destroys.
3614 - Start sending 'truncated' cells back rather than destroy cells
3615 if the circuit closes in front of you. This means we won't have
3616 to abandon partially built circuits.
3617 - Handle changed router status correctly when dirserver reloads
3618 fingerprint file. We used to be dropping all unverified descriptors
3619 right then. The bug was hidden because we would immediately
3620 fetch a directory from another dirserver, which would include the
3621 descriptors we just dropped.
3622 - Revise tor-spec to add more/better stream end reasons.
3623 - Revise all calls to connection_edge_end to avoid sending 'misc',
3624 and to take errno into account where possible.
3625 - Client now retries when streams end early for 'hibernating' or
3626 'resource limit' reasons, rather than failing them.
3627 - Try to be more zealous about calling connection_edge_end when
3628 things go bad with edge conns in connection.c.
3630 o Robustness improvements:
3631 - Better handling for heterogeneous / unreliable nodes:
3632 - Annotate circuits with whether they aim to contain high uptime
3633 nodes and/or high capacity nodes. When building circuits, choose
3635 - This means that every single node in an intro rend circuit,
3636 not just the last one, will have a minimum uptime.
3637 - New config option LongLivedPorts to indicate application streams
3638 that will want high uptime circuits.
3639 - Servers reset uptime when a dir fetch entirely fails. This
3640 hopefully reflects stability of the server's network connectivity.
3641 - If somebody starts his tor server in Jan 2004 and then fixes his
3642 clock, don't make his published uptime be a year.
3643 - Reset published uptime when we wake up from hibernation.
3644 - Introduce a notion of 'internal' circs, which are chosen without
3645 regard to the exit policy of the last hop. Intro and rendezvous
3646 circs must be internal circs, to avoid leaking information. Resolve
3647 and connect streams can use internal circs if they want.
3648 - New circuit pooling algorithm: keep track of what destination ports
3649 we've used recently (start out assuming we'll want to use 80), and
3650 make sure to have enough circs around to satisfy these ports. Also
3651 make sure to have 2 internal circs around if we've required internal
3652 circs lately (and with high uptime if we've seen that lately too).
3653 - Turn addr_policy_compare from a tristate to a quadstate; this should
3654 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
3655 for google.com" problem.
3656 - When a client asks us for a dir mirror and we don't have one,
3657 launch an attempt to get a fresh one.
3658 - First cut at support for "create-fast" cells. Clients can use
3659 these when extending to their first hop, since the TLS already
3660 provides forward secrecy and authentication. Not enabled on
3663 o Reachability testing.
3664 - Your Tor server will automatically try to see if its ORPort and
3665 DirPort are reachable from the outside, and it won't upload its
3666 descriptor until it decides at least ORPort is reachable (when
3667 DirPort is not yet found reachable, publish it as zero).
3668 - When building testing circs for ORPort testing, use only
3669 high-bandwidth nodes, so fewer circuits fail.
3670 - Notice when our IP changes, and reset stats/uptime/reachability.
3671 - Authdirservers don't do ORPort reachability detection, since
3672 they're in clique mode, so it will be rare to find a server not
3673 already connected to them.
3674 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
3678 - Now we allow two unverified servers with the same nickname
3679 but different keys. But if a nickname is verified, only that
3680 nickname+key are allowed.
3681 - If you're an authdirserver connecting to an address:port,
3682 and it's not the OR you were expecting, forget about that
3683 descriptor. If he *was* the one you were expecting, then forget
3684 about all other descriptors for that address:port.
3685 - Allow servers to publish descriptors from 12 hours in the future.
3686 Corollary: only whine about clock skew from the dirserver if
3687 he's a trusted dirserver (since now even verified servers could
3688 have quite wrong clocks).
3689 - Require servers that use the default dirservers to have public IP
3690 addresses. We have too many servers that are configured with private
3691 IPs and their admins never notice the log entries complaining that
3692 their descriptors are being rejected.
3694 o Efficiency improvements:
3695 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
3696 and /dev/poll), and hopefully work better on Windows too.
3697 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
3698 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
3699 - Find libevent even if it's hiding in /usr/local/ and your
3700 CFLAGS and LDFLAGS don't tell you to look there.
3701 - Be able to link with libevent as a shared library (the default
3702 after 1.0d), even if it's hiding in /usr/local/lib and even
3703 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
3704 assuming you're running gcc. Otherwise fail and give a useful
3706 - Switch to a new buffer management algorithm, which tries to avoid
3707 reallocing and copying quite as much. In first tests it looks like
3708 it uses *more* memory on average, but less cpu.
3709 - Switch our internal buffers implementation to use a ring buffer,
3710 to hopefully improve performance for fast servers a lot.
3711 - Reenable the part of the code that tries to flush as soon as an
3712 OR outbuf has a full TLS record available. Perhaps this will make
3713 OR outbufs not grow as huge except in rare cases, thus saving lots
3714 of CPU time plus memory.
3715 - Improve performance for dirservers: stop re-parsing the whole
3716 directory every time you regenerate it.
3717 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
3718 it much faster to look up a circuit for each relay cell.
3719 - Remove most calls to assert_all_pending_dns_resolves_ok(),
3720 since they're eating our cpu on exit nodes.
3721 - Stop wasting time doing a case insensitive comparison for every
3722 dns name every time we do any lookup. Canonicalize the names to
3723 lowercase when you first see them.
3726 - Handle unavailable hidden services better. Handle slow or busy
3727 hidden services better.
3728 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
3729 circ as necessary, if there are any completed ones lying around
3730 when we try to launch one.
3731 - Make hidden services try to establish a rendezvous for 30 seconds
3732 after fetching the descriptor, rather than for n (where n=3)
3733 attempts to build a circuit.
3734 - Adjust maximum skew and age for rendezvous descriptors: let skew
3735 be 48 hours rather than 90 minutes.
3736 - Reject malformed .onion addresses rather then passing them on as
3737 normal web requests.
3740 - More Tor controller support. See
3741 http://tor.eff.org/doc/control-spec.txt for all the new features,
3742 including signals to emulate unix signals from any platform;
3743 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
3744 closestream; closecircuit; etc.
3745 - Encode hashed controller passwords in hex instead of base64,
3746 to make it easier to write controllers.
3747 - Revise control spec and implementation to allow all log messages to
3748 be sent to controller with their severities intact (suggested by
3749 Matt Edman). Disable debug-level logs while delivering a debug-level
3750 log to the controller, to prevent loop. Update TorControl to handle
3751 new log event types.
3753 o New config options/defaults:
3754 - Begin scrubbing sensitive strings from logs by default. Turn off
3755 the config option SafeLogging if you need to do debugging.
3756 - New exit policy: accept most low-numbered ports, rather than
3757 rejecting most low-numbered ports.
3758 - Put a note in the torrc about abuse potential with the default
3760 - Add support for CONNECTing through https proxies, with "HttpsProxy"
3762 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
3763 based on patch from Adam Langley (basic auth only).
3764 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
3765 the fast servers that have been joining lately. (Clients are now
3766 willing to load balance over up to 2 MB of advertised bandwidth
3768 - New config option MaxAdvertisedBandwidth which lets you advertise
3769 a low bandwidthrate (to not attract as many circuits) while still
3770 allowing a higher bandwidthrate in reality.
3771 - Require BandwidthRate to be at least 20kB/s for servers.
3772 - Add a NoPublish config option, so you can be a server (e.g. for
3773 testing running Tor servers in other Tor networks) without
3774 publishing your descriptor to the primary dirservers.
3775 - Add a new AddressMap config directive to rewrite incoming socks
3776 addresses. This lets you, for example, declare an implicit
3777 required exit node for certain sites.
3778 - Add a new TrackHostExits config directive to trigger addressmaps
3779 for certain incoming socks addresses -- for sites that break when
3780 your exit keeps changing (based on patch from Mike Perry).
3781 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
3782 which describes how often we retry making new circuits if current
3783 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
3784 how long we're willing to make use of an already-dirty circuit.
3785 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
3786 a config option "ShutdownWaitLength" (when using kill -INT on
3788 - Fix an edge case in parsing config options: if they say "--"
3789 on the commandline, it's not a config option (thanks weasel).
3790 - New config option DirAllowPrivateAddresses for authdirservers.
3791 Now by default they refuse router descriptors that have non-IP or
3792 private-IP addresses.
3793 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
3794 smart" default value: low for servers and high for clients.
3795 - Some people were putting "Address " in their torrc, and they had
3796 a buggy resolver that resolved " " to 0.0.0.0. Oops.
3797 - If DataDir is ~/.tor, and that expands to /.tor, then default to
3798 LOCALSTATEDIR/tor instead.
3799 - Implement --verify-config command-line option to check if your torrc
3800 is valid without actually launching Tor.
3802 o Logging improvements:
3803 - When dirservers refuse a server descriptor, we now log its
3804 contactinfo, platform, and the poster's IP address.
3805 - Only warn once per nickname from add_nickname_list_to_smartlist()
3806 per failure, so an entrynode or exitnode choice that's down won't
3808 - When we're connecting to an OR and he's got a different nickname/key
3809 than we were expecting, only complain loudly if we're an OP or a
3810 dirserver. Complaining loudly to the OR admins just confuses them.
3811 - Whine at you if you're a server and you don't set your contactinfo.
3812 - Warn when exit policy implicitly allows local addresses.
3813 - Give a better warning when some other server advertises an
3814 ORPort that is actually an apache running ssl.
3815 - If we get an incredibly skewed timestamp from a dirserver mirror
3816 that isn't a verified OR, don't warn -- it's probably him that's
3818 - When a dirserver causes you to give a warn, mention which dirserver
3820 - Initialize libevent later in the startup process, so the logs are
3821 already established by the time we start logging libevent warns.
3822 - Use correct errno on win32 if libevent fails.
3823 - Check and warn about known-bad/slow libevent versions.
3824 - Stop warning about sigpipes in the logs. We're going to
3825 pretend that getting these occassionally is normal and fine.
3827 o New contrib scripts:
3828 - New experimental script tor/contrib/exitlist: a simple python
3829 script to parse directories and find Tor nodes that exit to listed
3831 - New experimental script tor/contrib/ExerciseServer.py (needs more
3832 work) that uses the controller interface to build circuits and
3833 fetch pages over them. This will help us bootstrap servers that
3834 have lots of capacity but haven't noticed it yet.
3835 - New experimental script tor/contrib/PathDemo.py (needs more work)
3836 that uses the controller interface to let you choose whole paths
3838 "<hostname>.<path,separated by dots>.<length of path>.path"
3839 - New contributed script "privoxy-tor-toggle" to toggle whether
3840 Privoxy uses Tor. Seems to be configured for Debian by default.
3841 - Have torctl.in/tor.sh.in check for location of su binary (needed
3845 - chdir() to your datadirectory at the *end* of the daemonize process,
3846 not the beginning. This was a problem because the first time you
3847 run tor, if your datadir isn't there, and you have runasdaemon set
3848 to 1, it will try to chdir to it before it tries to create it. Oops.
3849 - Fix several double-mark-for-close bugs, e.g. where we were finding
3850 a conn for a cell even if that conn is already marked for close.
3851 - Stop most cases of hanging up on a socks connection without sending
3853 - Fix a bug in the RPM package: set home directory for _tor to
3854 something more reasonable when first installing.
3855 - Stop putting nodename in the Platform string in server descriptors.
3856 It doesn't actually help, and it is confusing/upsetting some people.
3857 - When using preferred entry or exit nodes, ignore whether the
3858 circuit wants uptime or capacity. They asked for the nodes, they
3860 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
3861 artificially capped at 500kB.
3862 - Cache local dns resolves correctly even when they're .exit
3864 - If we're hibernating and we get a SIGINT, exit immediately.
3865 - tor-resolve requests were ignoring .exit if there was a working circuit
3866 they could use instead.
3867 - Pay more attention to the ClientOnly config option.
3868 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
3869 installer screens; and don't put stuff into StartupItems unless
3870 the user asks you to.
3873 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
3874 rather than just rejecting it.
3875 - If our clock jumps forward by 100 seconds or more, assume something
3876 has gone wrong with our network and abandon all not-yet-used circs.
3877 - When an application is using socks5, give him the whole variety of
3878 potential socks5 responses (connect refused, host unreachable, etc),
3879 rather than just "success" or "failure".
3880 - A more sane version numbering system. See
3881 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
3882 - Change version parsing logic: a version is "obsolete" if it is not
3883 recommended and (1) there is a newer recommended version in the
3884 same series, or (2) there are no recommended versions in the same
3885 series, but there are some recommended versions in a newer series.
3886 A version is "new" if it is newer than any recommended version in
3888 - Report HTTP reasons to client when getting a response from directory
3889 servers -- so you can actually know what went wrong.
3890 - Reject odd-looking addresses at the client (e.g. addresses that
3891 contain a colon), rather than having the server drop them because
3893 - Stop publishing socksport in the directory, since it's not
3894 actually meant to be public. For compatibility, publish a 0 there
3896 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
3897 cookies to disk and doesn't log each web request to disk. (Thanks
3898 to Brett Carrington for pointing this out.)
3899 - Add OSX uninstall instructions. An actual uninstall script will
3901 - Add "opt hibernating 1" to server descriptor to make it clearer
3902 whether the server is hibernating.
3905 Changes in version 0.0.9.10 - 2005-06-16
3906 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
3907 - Refuse relay cells that claim to have a length larger than the
3908 maximum allowed. This prevents a potential attack that could read
3909 arbitrary memory (e.g. keys) from an exit server's process
3913 Changes in version 0.0.9.9 - 2005-04-23
3914 o Bugfixes on 0.0.9.x:
3915 - If unofficial Tor clients connect and send weird TLS certs, our
3916 Tor server triggers an assert. This release contains a minimal
3917 backport from the broader fix that we put into 0.1.0.4-rc.
3920 Changes in version 0.0.9.8 - 2005-04-07
3921 o Bugfixes on 0.0.9.x:
3922 - We have a bug that I haven't found yet. Sometimes, very rarely,
3923 cpuworkers get stuck in the 'busy' state, even though the cpuworker
3924 thinks of itself as idle. This meant that no new circuits ever got
3925 established. Here's a workaround to kill any cpuworker that's been
3926 busy for more than 100 seconds.
3929 Changes in version 0.0.9.7 - 2005-04-01
3930 o Bugfixes on 0.0.9.x:
3931 - Fix another race crash bug (thanks to Glenn Fink for reporting).
3932 - Compare identity to identity, not to nickname, when extending to
3933 a router not already in the directory. This was preventing us from
3934 extending to unknown routers. Oops.
3935 - Make sure to create OS X Tor user in <500 range, so we aren't
3936 creating actual system users.
3937 - Note where connection-that-hasn't-sent-end was marked, and fix
3938 a few really loud instances of this harmless bug (it's fixed more
3942 Changes in version 0.0.9.6 - 2005-03-24
3943 o Bugfixes on 0.0.9.x (crashes and asserts):
3944 - Add new end stream reasons to maintainance branch. Fix bug where
3945 reason (8) could trigger an assert. Prevent bug from recurring.
3946 - Apparently win32 stat wants paths to not end with a slash.
3947 - Fix assert triggers in assert_cpath_layer_ok(), where we were
3948 blowing away the circuit that conn->cpath_layer points to, then
3949 checking to see if the circ is well-formed. Backport check to make
3950 sure we dont use the cpath on a closed connection.
3951 - Prevent circuit_resume_edge_reading_helper() from trying to package
3952 inbufs for marked-for-close streams.
3953 - Don't crash on hup if your options->address has become unresolvable.
3954 - Some systems (like OS X) sometimes accept() a connection and tell
3955 you the remote host is 0.0.0.0:0. If this happens, due to some
3956 other mis-features, we get confused; so refuse the conn for now.
3958 o Bugfixes on 0.0.9.x (other):
3959 - Fix harmless but scary "Unrecognized content encoding" warn message.
3960 - Add new stream error reason: TORPROTOCOL reason means "you are not
3961 speaking a version of Tor I understand; say bye-bye to your stream."
3962 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
3963 into the future, now that we are more tolerant of skew. This
3964 resolves a bug where a Tor server would refuse to cache a directory
3965 because all the directories it gets are too far in the future;
3966 yet the Tor server never logs any complaints about clock skew.
3967 - Mac packaging magic: make man pages useable, and do not overwrite
3968 existing torrc files.
3969 - Make OS X log happily to /var/log/tor/tor.log
3972 Changes in version 0.0.9.5 - 2005-02-22
3973 o Bugfixes on 0.0.9.x:
3974 - Fix an assert race at exit nodes when resolve requests fail.
3975 - Stop picking unverified dir mirrors--it only leads to misery.
3976 - Patch from Matt Edman to make NT services work better. Service
3977 support is still not compiled into the executable by default.
3978 - Patch from Dmitri Bely so the Tor service runs better under
3979 the win32 SYSTEM account.
3980 - Make tor-resolve actually work (?) on Win32.
3981 - Fix a sign bug when getrlimit claims to have 4+ billion
3982 file descriptors available.
3983 - Stop refusing to start when bandwidthburst == bandwidthrate.
3984 - When create cells have been on the onion queue more than five
3985 seconds, just send back a destroy and take them off the list.
3988 Changes in version 0.0.9.4 - 2005-02-03
3989 o Bugfixes on 0.0.9:
3990 - Fix an assert bug that took down most of our servers: when
3991 a server claims to have 1 GB of bandwidthburst, don't
3993 - Don't crash as badly if we have spawned the max allowed number
3994 of dnsworkers, or we're out of file descriptors.
3995 - Block more file-sharing ports in the default exit policy.
3996 - MaxConn is now automatically set to the hard limit of max
3997 file descriptors we're allowed (ulimit -n), minus a few for
3999 - Give a clearer message when servers need to raise their
4000 ulimit -n when they start running out of file descriptors.
4001 - SGI Compatibility patches from Jan Schaumann.
4002 - Tolerate a corrupt cached directory better.
4003 - When a dirserver hasn't approved your server, list which one.
4004 - Go into soft hibernation after 95% of the bandwidth is used,
4005 not 99%. This is especially important for daily hibernators who
4006 have a small accounting max. Hopefully it will result in fewer
4007 cut connections when the hard hibernation starts.
4008 - Load-balance better when using servers that claim more than
4009 800kB/s of capacity.
4010 - Make NT services work (experimental, only used if compiled in).
4013 Changes in version 0.0.9.3 - 2005-01-21
4014 o Bugfixes on 0.0.9:
4015 - Backport the cpu use fixes from main branch, so busy servers won't
4016 need as much processor time.
4017 - Work better when we go offline and then come back, or when we
4018 run Tor at boot before the network is up. We do this by
4019 optimistically trying to fetch a new directory whenever an
4020 application request comes in and we think we're offline -- the
4021 human is hopefully a good measure of when the network is back.
4022 - Backport some minimal hidserv bugfixes: keep rend circuits open as
4023 long as you keep using them; actually publish hidserv descriptors
4024 shortly after they change, rather than waiting 20-40 minutes.
4025 - Enable Mac startup script by default.
4026 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
4027 - When you update AllowUnverifiedNodes or FirewallPorts via the
4028 controller's setconf feature, we were always appending, never
4030 - When you update HiddenServiceDir via setconf, it was screwing up
4031 the order of reading the lines, making it fail.
4032 - Do not rewrite a cached directory back to the cache; otherwise we
4033 will think it is recent and not fetch a newer one on startup.
4034 - Workaround for webservers that lie about Content-Encoding: Tor
4035 now tries to autodetect compressed directories and compression
4036 itself. This lets us Proxypass dir fetches through apache.
4039 Changes in version 0.0.9.2 - 2005-01-04
4040 o Bugfixes on 0.0.9 (crashes and asserts):
4041 - Fix an assert on startup when the disk is full and you're logging
4043 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
4044 style address, then we'd crash.
4045 - Fix an assert trigger when the running-routers string we get from
4046 a dirserver is broken.
4047 - Make worker threads start and run on win32. Now win32 servers
4049 - Bandaid (not actually fix, but now it doesn't crash) an assert
4050 where the dns worker dies mysteriously and the main Tor process
4051 doesn't remember anything about the address it was resolving.
4053 o Bugfixes on 0.0.9 (Win32):
4054 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
4055 name out of the warning/assert messages.
4056 - Fix a superficial "unhandled error on read" bug on win32.
4057 - The win32 installer no longer requires a click-through for our
4058 license, since our Free Software license grants rights but does not
4060 - Win32: When connecting to a dirserver fails, try another one
4061 immediately. (This was already working for non-win32 Tors.)
4062 - Stop trying to parse $HOME on win32 when hunting for default
4064 - Make tor-resolve.c work on win32 by calling network_init().
4066 o Bugfixes on 0.0.9 (other):
4067 - Make 0.0.9.x build on Solaris again.
4068 - Due to a fencepost error, we were blowing away the \n when reporting
4069 confvalue items in the controller. So asking for multiple config
4070 values at once couldn't work.
4071 - When listing circuits that are pending on an opening OR connection,
4072 if we're an OR we were listing circuits that *end* at us as
4073 being pending on every listener, dns/cpu worker, etc. Stop that.
4074 - Dirservers were failing to create 'running-routers' or 'directory'
4075 strings if we had more than some threshold of routers. Fix them so
4076 they can handle any number of routers.
4077 - Fix a superficial "Duplicate mark for close" bug.
4078 - Stop checking for clock skew for OR connections, even for servers.
4079 - Fix a fencepost error that was chopping off the last letter of any
4080 nickname that is the maximum allowed nickname length.
4081 - Update URLs in log messages so they point to the new website.
4082 - Fix a potential problem in mangling server private keys while
4083 writing to disk (not triggered yet, as far as we know).
4084 - Include the licenses for other free software we include in Tor,
4085 now that we're shipping binary distributions more regularly.
4088 Changes in version 0.0.9.1 - 2004-12-15
4089 o Bugfixes on 0.0.9:
4090 - Make hibernation actually work.
4091 - Make HashedControlPassword config option work.
4092 - When we're reporting event circuit status to a controller,
4093 don't use the stream status code.
4096 Changes in version 0.0.9 - 2004-12-12
4097 o Bugfixes on 0.0.8.1 (Crashes and asserts):
4098 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
4099 write() call will fail and we handle it there.
4100 - When we run out of disk space, or other log writing error, don't
4101 crash. Just stop logging to that log and continue.
4102 - Fix isspace() and friends so they still make Solaris happy
4103 but also so they don't trigger asserts on win32.
4104 - Fix assert failure on malformed socks4a requests.
4105 - Fix an assert bug where a hidden service provider would fail if
4106 the first hop of his rendezvous circuit was down.
4107 - Better handling of size_t vs int, so we're more robust on 64
4110 o Bugfixes on 0.0.8.1 (Win32):
4111 - Make windows sockets actually non-blocking (oops), and handle
4112 win32 socket errors better.
4113 - Fix parse_iso_time on platforms without strptime (eg win32).
4114 - win32: when being multithreaded, leave parent fdarray open.
4115 - Better handling of winsock includes on non-MSV win32 compilers.
4116 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
4118 - Make unit tests work on win32.
4120 o Bugfixes on 0.0.8.1 (Path selection and streams):
4121 - Calculate timeout for waiting for a connected cell from the time
4122 we sent the begin cell, not from the time the stream started. If
4123 it took a long time to establish the circuit, we would time out
4124 right after sending the begin cell.
4125 - Fix router_compare_addr_to_addr_policy: it was not treating a port
4126 of * as always matching, so we were picking reject *:* nodes as
4127 exit nodes too. Oops.
4128 - When read() failed on a stream, we would close it without sending
4129 back an end. So 'connection refused' would simply be ignored and
4130 the user would get no response.
4131 - Stop a sigpipe: when an 'end' cell races with eof from the app,
4132 we shouldn't hold-open-until-flush if the eof arrived first.
4133 - Let resolve conns retry/expire also, rather than sticking around
4135 - Fix more dns related bugs: send back resolve_failed and end cells
4136 more reliably when the resolve fails, rather than closing the
4137 circuit and then trying to send the cell. Also attach dummy resolve
4138 connections to a circuit *before* calling dns_resolve(), to fix
4139 a bug where cached answers would never be sent in RESOLVED cells.
4141 o Bugfixes on 0.0.8.1 (Circuits):
4142 - Finally fix a bug that's been plaguing us for a year:
4143 With high load, circuit package window was reaching 0. Whenever
4144 we got a circuit-level sendme, we were reading a lot on each
4145 socket, but only writing out a bit. So we would eventually reach
4146 eof. This would be noticed and acted on even when there were still
4147 bytes sitting in the inbuf.
4148 - Use identity comparison, not nickname comparison, to choose which
4149 half of circuit-ID-space each side gets to use. This is needed
4150 because sometimes we think of a router as a nickname, and sometimes
4151 as a hex ID, and we can't predict what the other side will do.
4153 o Bugfixes on 0.0.8.1 (Other):
4154 - Fix a whole slew of memory leaks.
4155 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
4156 - If we are using select, make sure we stay within FD_SETSIZE.
4157 - When poll() is interrupted, we shouldn't believe the revents values.
4158 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
4159 and smartlist_len, which are two major profiling offenders.
4160 - If do_hup fails, actually notice.
4161 - Flush the log file descriptor after we print "Tor opening log file",
4162 so we don't see those messages days later.
4163 - Hidden service operators now correctly handle version 1 style
4164 INTRODUCE1 cells (nobody generates them still, so not a critical
4166 - Handle more errnos from accept() without closing the listener.
4167 Some OpenBSD machines were closing their listeners because
4168 they ran out of file descriptors.
4169 - Some people had wrapped their tor client/server in a script
4170 that would restart it whenever it died. This did not play well
4171 with our "shut down if your version is obsolete" code. Now people
4172 don't fetch a new directory if their local cached version is
4174 - Make our autogen.sh work on ksh as well as bash.
4175 - Better torrc example lines for dirbindaddress and orbindaddress.
4176 - Improved bounds checking on parsed ints (e.g. config options and
4177 the ones we find in directories.)
4178 - Stop using separate defaults for no-config-file and
4179 empty-config-file. Now you have to explicitly turn off SocksPort,
4180 if you don't want it open.
4181 - We were starting to daemonize before we opened our logs, so if
4182 there were any problems opening logs, we would complain to stderr,
4183 which wouldn't work, and then mysteriously exit.
4184 - If a verified OR connects to us before he's uploaded his descriptor,
4185 or we verify him and hup but he still has the original TLS
4186 connection, then conn->nickname is still set like he's unverified.
4188 o Code security improvements, inspired by Ilja:
4189 - tor_snprintf wrapper over snprintf with consistent (though not C99)
4191 - Replace sprintf with tor_snprintf. (I think they were all safe, but
4193 - Replace strcpy/strncpy with strlcpy in more places.
4194 - Avoid strcat; use tor_snprintf or strlcat instead.
4196 o Features (circuits and streams):
4197 - New circuit building strategy: keep a list of ports that we've
4198 used in the past 6 hours, and always try to have 2 circuits open
4199 or on the way that will handle each such port. Seed us with port
4200 80 so web users won't complain that Tor is "slow to start up".
4201 - Make kill -USR1 dump more useful stats about circuits.
4202 - When warning about retrying or giving up, print the address, so
4203 the user knows which one it's talking about.
4204 - If you haven't used a clean circuit in an hour, throw it away,
4205 just to be on the safe side. (This means after 6 hours a totally
4206 unused Tor client will have no circuits open.)
4207 - Support "foo.nickname.exit" addresses, to let Alice request the
4208 address "foo" as viewed by exit node "nickname". Based on a patch
4210 - If your requested entry or exit node has advertised bandwidth 0,
4212 - Be more greedy about filling up relay cells -- we try reading again
4213 once we've processed the stuff we read, in case enough has arrived
4214 to fill the last cell completely.
4215 - Refuse application socks connections to port 0.
4216 - Use only 0.0.9pre1 and later servers for resolve cells.
4218 o Features (bandwidth):
4219 - Hibernation: New config option "AccountingMax" lets you
4220 set how many bytes per month (in each direction) you want to
4221 allow your server to consume. Rather than spreading those
4222 bytes out evenly over the month, we instead hibernate for some
4223 of the month and pop up at a deterministic time, work until
4224 the bytes are consumed, then hibernate again. Config option
4225 "MonthlyAccountingStart" lets you specify which day of the month
4226 your billing cycle starts on.
4227 - Implement weekly/monthly/daily accounting: now you specify your
4228 hibernation properties by
4229 AccountingMax N bytes|KB|MB|GB|TB
4230 AccountingStart day|week|month [day] HH:MM
4231 Defaults to "month 1 0:00".
4232 - Let bandwidth and interval config options be specified as 5 bytes,
4233 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
4235 o Features (directories):
4236 - New "router-status" line in directory, to better bind each verified
4237 nickname to its identity key.
4238 - Clients can ask dirservers for /dir.z to get a compressed version
4239 of the directory. Only works for servers running 0.0.9, of course.
4240 - Make clients cache directories and use them to seed their router
4241 lists at startup. This means clients have a datadir again.
4242 - Respond to content-encoding headers by trying to uncompress as
4244 - Clients and servers now fetch running-routers; cache
4245 running-routers; compress running-routers; serve compressed
4247 - Make moria2 advertise a dirport of 80, so people behind firewalls
4248 will be able to get a directory.
4249 - Http proxy support
4250 - Dirservers translate requests for http://%s:%d/x to /x
4251 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
4252 be routed through this host.
4253 - Clients ask for /tor/x rather than /x for new enough dirservers.
4254 This way we can one day coexist peacefully with apache.
4255 - Clients specify a "Host: %s%d" http header, to be compatible
4256 with more proxies, and so running squid on an exit node can work.
4257 - Protect dirservers from overzealous descriptor uploading -- wait
4258 10 seconds after directory gets dirty, before regenerating.
4260 o Features (packages and install):
4261 - Add NSI installer contributed by J Doe.
4262 - Apply NT service patch from Osamu Fujino. Still needs more work.
4263 - Commit VC6 and VC7 workspace/project files.
4264 - Commit a tor.spec for making RPM files, with help from jbash.
4265 - Add contrib/torctl.in contributed by Glenn Fink.
4266 - Make expand_filename handle ~ and ~username.
4267 - Use autoconf to enable largefile support where necessary. Use
4268 ftello where available, since ftell can fail at 2GB.
4269 - Ship src/win32/ in the tarball, so people can use it to build.
4270 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
4273 o Features (ui controller):
4274 - Control interface: a separate program can now talk to your
4275 client/server over a socket, and get/set config options, receive
4276 notifications of circuits and streams starting/finishing/dying,
4277 bandwidth used, etc. The next step is to get some GUIs working.
4278 Let us know if you want to help out. See doc/control-spec.txt .
4279 - Ship a contrib/tor-control.py as an example script to interact
4280 with the control port.
4281 - "tor --hash-password zzyxz" will output a salted password for
4282 use in authenticating to the control interface.
4283 - Implement the control-spec's SAVECONF command, to write your
4284 configuration to torrc.
4285 - Get cookie authentication for the controller closer to working.
4286 - When set_conf changes our server descriptor, upload a new copy.
4287 But don't upload it too often if there are frequent changes.
4289 o Features (config and command-line):
4290 - Deprecate unofficial config option abbreviations, and abbreviations
4291 not on the command line.
4292 - Configuration infrastructure support for warning on obsolete
4294 - Give a slightly more useful output for "tor -h".
4295 - Break DirFetchPostPeriod into:
4296 - DirFetchPeriod for fetching full directory,
4297 - StatusFetchPeriod for fetching running-routers,
4298 - DirPostPeriod for posting server descriptor,
4299 - RendPostPeriod for posting hidden service descriptors.
4300 - New log format in config:
4301 "Log minsev[-maxsev] stdout|stderr|syslog" or
4302 "Log minsev[-maxsev] file /var/foo"
4303 - DirPolicy config option, to let people reject incoming addresses
4304 from their dirserver.
4305 - "tor --list-fingerprint" will list your identity key fingerprint
4307 - Make tor --version --version dump the cvs Id of every file.
4308 - New 'MyFamily nick1,...' config option for a server to
4309 specify other servers that shouldn't be used in the same circuit
4310 with it. Only believed if nick1 also specifies us.
4311 - New 'NodeFamily nick1,nick2,...' config option for a client to
4312 specify nodes that it doesn't want to use in the same circuit.
4313 - New 'Redirectexit pattern address:port' config option for a
4314 server to redirect exit connections, e.g. to a local squid.
4315 - Add "pass" target for RedirectExit, to make it easier to break
4316 out of a sequence of RedirectExit rules.
4317 - Make the dirservers file obsolete.
4318 - Include a dir-signing-key token in directories to tell the
4319 parsing entity which key is being used to sign.
4320 - Remove the built-in bulky default dirservers string.
4321 - New config option "Dirserver %s:%d [fingerprint]", which can be
4322 repeated as many times as needed. If no dirservers specified,
4323 default to moria1,moria2,tor26.
4324 - Make 'Routerfile' config option obsolete.
4325 - Discourage people from setting their dirfetchpostperiod more often
4326 than once per minute.
4329 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
4330 get back to normal.)
4331 - Accept *:706 (silc) in default exit policy.
4332 - Implement new versioning format for post 0.1.
4333 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
4334 log more informatively.
4335 - Check clock skew for verified servers, but allow unverified
4336 servers and clients to have any clock skew.
4337 - Make sure the hidden service descriptors are at a random offset
4338 from each other, to hinder linkability.
4339 - Clients now generate a TLS cert too, in preparation for having
4340 them act more like real nodes.
4341 - Add a pure-C tor-resolve implementation.
4342 - Use getrlimit and friends to ensure we can reach MaxConn (currently
4343 1024) file descriptors.
4344 - Raise the max dns workers from 50 to 100.
4347 Changes in version 0.0.8.1 - 2004-10-13
4349 - Fix a seg fault that can be triggered remotely for Tor
4350 clients/servers with an open dirport.
4351 - Fix a rare assert trigger, where routerinfos for entries in
4352 our cpath would expire while we're building the path.
4353 - Fix a bug in OutboundBindAddress so it (hopefully) works.
4354 - Fix a rare seg fault for people running hidden services on
4355 intermittent connections.
4356 - Fix a bug in parsing opt keywords with objects.
4357 - Fix a stale pointer assert bug when a stream detaches and
4359 - Fix a string format vulnerability (probably not exploitable)
4360 in reporting stats locally.
4361 - Fix an assert trigger: sometimes launching circuits can fail
4362 immediately, e.g. because too many circuits have failed recently.
4363 - Fix a compile warning on 64 bit platforms.
4366 Changes in version 0.0.8 - 2004-08-25
4368 - Made our unit tests compile again on OpenBSD 3.5, and tor
4369 itself compile again on OpenBSD on a sparc64.
4370 - We were neglecting milliseconds when logging on win32, so
4371 everything appeared to happen at the beginning of each second.
4372 - Check directory signature _before_ you decide whether you're
4373 you're running an obsolete version and should exit.
4374 - Check directory signature _before_ you parse the running-routers
4375 list to decide who's running.
4376 - Check return value of fclose while writing to disk, so we don't
4377 end up with broken files when servers run out of disk space.
4378 - Port it to SunOS 5.9 / Athena
4379 - Fix two bugs in saving onion keys to disk when rotating, so
4380 hopefully we'll get fewer people using old onion keys.
4381 - Remove our mostly unused -- and broken -- hex_encode()
4382 function. Use base16_encode() instead. (Thanks to Timo Lindfors
4383 for pointing out this bug.)
4384 - Only pick and establish intro points after we've gotten a
4386 - Fix assert triggers: if the other side returns an address 0.0.0.0,
4387 don't put it into the client dns cache.
4388 - If a begin failed due to exit policy, but we believe the IP
4389 address should have been allowed, switch that router to exitpolicy
4390 reject *:* until we get our next directory.
4393 - 'Extend' relay cell payloads now include the digest of the
4394 intended next hop's identity key. Now we can verify that we're
4395 extending to the right router, and also extend to routers we
4396 hadn't heard of before.
4399 - Tor nodes can now act as relays (with an advertised ORPort)
4400 without being manually verified by the dirserver operators.
4401 - Uploaded descriptors of unverified routers are now accepted
4402 by the dirservers, and included in the directory.
4403 - Verified routers are listed by nickname in the running-routers
4404 list; unverified routers are listed as "$<fingerprint>".
4405 - We now use hash-of-identity-key in most places rather than
4406 nickname or addr:port, for improved security/flexibility.
4407 - AllowUnverifiedNodes config option to let circuits choose no-name
4408 routers in entry,middle,exit,introduction,rendezvous positions.
4409 Allow middle and rendezvous positions by default.
4410 - When picking unverified routers, skip those with low uptime and/or
4411 low bandwidth, depending on what properties you care about.
4412 - ClientOnly option for nodes that never want to become servers.
4413 - Directory caching.
4414 - "AuthoritativeDir 1" option for the official dirservers.
4415 - Now other nodes (clients and servers) will cache the latest
4416 directory they've pulled down.
4417 - They can enable their DirPort to serve it to others.
4418 - Clients will pull down a directory from any node with an open
4419 DirPort, and check the signature/timestamp correctly.
4420 - Authoritative dirservers now fetch directories from other
4421 authdirservers, to stay better synced.
4422 - Running-routers list tells who's down also, along with noting
4423 if they're verified (listed by nickname) or unverified (listed
4425 - Allow dirservers to serve running-router list separately.
4426 This isn't used yet.
4427 - You can now fetch $DIRURL/running-routers to get just the
4428 running-routers line, not the whole descriptor list. (But
4429 clients don't use this yet.)
4430 - Clients choose nodes proportional to advertised bandwidth.
4431 - Clients avoid using nodes with low uptime as introduction points.
4432 - Handle servers with dynamic IP addresses: don't just replace
4433 options->Address with the resolved one at startup, and
4434 detect our address right before we make a routerinfo each time.
4435 - 'FascistFirewall' option to pick dirservers and ORs on specific
4436 ports; plus 'FirewallPorts' config option to tell FascistFirewall
4437 which ports are open. (Defaults to 80,443)
4438 - Try other dirservers immediately if the one you try is down. This
4439 should tolerate down dirservers better now.
4440 - ORs connect-on-demand to other ORs
4441 - If you get an extend cell to an OR you're not connected to,
4442 connect, handshake, and forward the create cell.
4443 - The authoritative dirservers stay connected to everybody,
4444 and everybody stays connected to 0.0.7 servers, but otherwise
4445 clients/servers expire unused connections after 5 minutes.
4446 - When servers get a sigint, they delay 30 seconds (refusing new
4447 connections) then exit. A second sigint causes immediate exit.
4448 - File and name management:
4449 - Look for .torrc if no CONFDIR "torrc" is found.
4450 - If no datadir is defined, then choose, make, and secure ~/.tor
4452 - If torrc not found, exitpolicy reject *:*.
4453 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
4454 - If no nickname is defined, derive default from hostname.
4455 - Rename secret key files, e.g. identity.key -> secret_id_key,
4456 to discourage people from mailing their identity key to tor-ops.
4457 - Refuse to build a circuit before the directory has arrived --
4458 it won't work anyway, since you won't know the right onion keys
4460 - Parse tor version numbers so we can do an is-newer-than check
4461 rather than an is-in-the-list check.
4462 - New socks command 'resolve', to let us shim gethostbyname()
4464 - A 'tor_resolve' script to access the socks resolve functionality.
4465 - A new socks-extensions.txt doc file to describe our
4466 interpretation and extensions to the socks protocols.
4467 - Add a ContactInfo option, which gets published in descriptor.
4468 - Write tor version at the top of each log file
4469 - New docs in the tarball:
4471 - Document that you should proxy your SSL traffic too.
4472 - Log a warning if the user uses an unsafe socks variant, so people
4473 are more likely to learn about privoxy or socat.
4474 - Log a warning if you're running an unverified server, to let you
4475 know you might want to get it verified.
4476 - Change the default exit policy to reject the default edonkey,
4477 kazaa, gnutella ports.
4478 - Add replace_file() to util.[ch] to handle win32's rename().
4479 - Publish OR uptime in descriptor (and thus in directory) too.
4480 - Remember used bandwidth (both in and out), and publish 15-minute
4481 snapshots for the past day into our descriptor.
4482 - Be more aggressive about trying to make circuits when the network
4483 has changed (e.g. when you unsuspend your laptop).
4484 - Check for time skew on http headers; report date in response to
4486 - If the entrynode config line has only one node, don't pick it as
4488 - Add strict{entry|exit}nodes config options. If set to 1, then
4489 we refuse to build circuits that don't include the specified entry
4491 - OutboundBindAddress config option, to bind to a specific
4492 IP address for outgoing connect()s.
4493 - End truncated log entries (e.g. directories) with "[truncated]".
4496 Changes in version 0.0.7.3 - 2004-08-12
4497 o Stop dnsworkers from triggering an assert failure when you
4498 ask them to resolve the host "".
4501 Changes in version 0.0.7.2 - 2004-07-07
4502 o A better fix for the 0.0.0.0 problem, that will hopefully
4503 eliminate the remaining related assertion failures.
4506 Changes in version 0.0.7.1 - 2004-07-04
4507 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
4508 since internally we use 0.0.0.0 to signify "not yet resolved".
4511 Changes in version 0.0.7 - 2004-06-07
4512 o Fixes for crashes and other obnoxious bugs:
4513 - Fix an epipe bug: sometimes when directory connections failed
4514 to connect, we would give them a chance to flush before closing
4516 - When we detached from a circuit because of resolvefailed, we
4517 would immediately try the same circuit twice more, and then
4518 give up on the resolve thinking we'd tried three different
4520 - Limit the number of intro circuits we'll attempt to build for a
4521 hidden service per 15-minute period.
4522 - Check recommended-software string *early*, before actually parsing
4523 the directory. Thus we can detect an obsolete version and exit,
4524 even if the new directory format doesn't parse.
4525 o Fixes for security bugs:
4526 - Remember which nodes are dirservers when you startup, and if a
4527 random OR enables his dirport, don't automatically assume he's
4528 a trusted dirserver.
4530 - Directory connections were asking the wrong poll socket to
4531 start writing, and not asking themselves to start writing.
4532 - When we detached from a circuit because we sent a begin but
4533 didn't get a connected, we would use it again the first time;
4534 but after that we would correctly switch to a different one.
4535 - Stop warning when the first onion decrypt attempt fails; they
4536 will sometimes legitimately fail now that we rotate keys.
4537 - Override unaligned-access-ok check when $host_cpu is ia64 or
4538 arm. Apparently they allow it but the kernel whines.
4539 - Dirservers try to reconnect periodically too, in case connections
4541 - Fix some memory leaks in directory servers.
4542 - Allow backslash in Win32 filenames.
4543 - Made Tor build complain-free on FreeBSD, hopefully without
4544 breaking other BSD builds. We'll see.
4545 - Check directory signatures based on name of signer, not on whom
4546 we got the directory from. This will let us cache directories more
4548 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
4551 - Doxygen markup on all functions and global variables.
4552 - Make directory functions update routerlist, not replace it. So
4553 now directory disagreements are not so critical a problem.
4554 - Remove the upper limit on number of descriptors in a dirserver's
4555 directory (not that we were anywhere close).
4556 - Allow multiple logfiles at different severity ranges.
4557 - Allow *BindAddress to specify ":port" rather than setting *Port
4558 separately. Allow multiple instances of each BindAddress config
4559 option, so you can bind to multiple interfaces if you want.
4560 - Allow multiple exit policy lines, which are processed in order.
4561 Now we don't need that huge line with all the commas in it.
4562 - Enable accept/reject policies on SOCKS connections, so you can bind
4563 to 0.0.0.0 but still control who can use your OP.
4564 - Updated the man page to reflect these features.
4567 Changes in version 0.0.6.2 - 2004-05-16
4568 o Our integrity-checking digest was checking only the most recent cell,
4569 not the previous cells like we'd thought.
4570 Thanks to Stefan Mark for finding the flaw!
4573 Changes in version 0.0.6.1 - 2004-05-06
4574 o Fix two bugs in our AES counter-mode implementation (this affected
4575 onion-level stream encryption, but not TLS-level). It turns
4576 out we were doing something much more akin to a 16-character
4577 polyalphabetic cipher. Oops.
4578 Thanks to Stefan Mark for finding the flaw!
4579 o Retire moria3 as a directory server, and add tor26 as a directory
4583 Changes in version 0.0.6 - 2004-05-02
4585 - Hidden services and rendezvous points are implemented. Go to
4586 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
4587 hidden services. (This only works via a socks4a proxy such as
4588 Privoxy, and currently it's quite slow.)
4589 - We now rotate link (tls context) keys and onion keys.
4590 - CREATE cells now include oaep padding, so you can tell
4591 if you decrypted them correctly.
4592 - Retry stream correctly when we fail to connect because of
4593 exit-policy-reject (should try another) or can't-resolve-address.
4594 - When we hup a dirserver and we've *removed* a server from the
4595 approved-routers list, now we remove that server from the
4596 in-memory directories too.
4597 - Add bandwidthburst to server descriptor.
4598 - Directories now say which dirserver signed them.
4599 - Use a tor_assert macro that logs failed assertions too.
4600 - Since we don't support truncateds much, don't bother sending them;
4601 just close the circ.
4602 - Fetch randomness from /dev/urandom better (not via fopen/fread)
4603 - Better debugging for tls errors
4604 - Set Content-Type on the directory and hidserv descriptor.
4605 - Remove IVs from cipher code, since AES-ctr has none.
4607 - Fix an assert trigger for exit nodes that's been plaguing us since
4608 the days of 0.0.2prexx (thanks weasel!)
4609 - Fix a bug where we were closing tls connections intermittently.
4610 It turns out openssl keeps its errors around -- so if an error
4611 happens, and you don't ask about it, and then another openssl
4612 operation happens and succeeds, and you ask if there was an error,
4613 it tells you about the first error.
4614 - Fix a bug that's been lurking since 27 may 03 (!)
4615 When passing back a destroy cell, we would use the wrong circ id.
4616 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
4617 - Some versions of openssl have an SSL_pending function that erroneously
4618 returns bytes when there is a non-application record pending.
4619 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
4620 o We were using an array of length zero in a few places.
4621 o Win32's gethostbyname can't resolve an IP to an IP.
4622 o Win32's close can't close a socket.
4623 o Handle windows socket errors correctly.
4625 - check for <sys/limits.h> so we build on FreeBSD again, and
4626 <machine/limits.h> for NetBSD.
4629 Changes in version 0.0.5 - 2004-03-30
4630 o Install torrc as torrc.sample -- we no longer clobber your
4632 o Fix mangled-state bug in directory fetching (was causing sigpipes).
4633 o Only build circuits after we've fetched the directory: clients were
4634 using only the directory servers before they'd fetched a directory.
4635 This also means longer startup time; so it goes.
4636 o Fix an assert trigger where an OP would fail to handshake, and we'd
4637 expect it to have a nickname.
4638 o Work around a tsocks bug: do a socks reject when AP connection dies
4639 early, else tsocks goes into an infinite loop.
4640 o Hold socks connection open until reply is flushed (if possible)
4641 o Make exit nodes resolve IPs to IPs immediately, rather than asking
4642 the dns farm to do it.
4643 o Fix c99 aliasing warnings in rephist.c
4644 o Don't include server descriptors that are older than 24 hours in the
4646 o Give socks 'reject' replies their whole 15s to attempt to flush,
4647 rather than seeing the 60s timeout and assuming the flush had failed.
4648 o Clean automake droppings from the cvs repository
4649 o Add in a 'notice' log level for things the operator should hear
4650 but that aren't warnings
4653 Changes in version 0.0.4 - 2004-03-26
4654 o When connecting to a dirserver or OR and the network is down,
4658 Changes in version 0.0.3 - 2004-03-26
4659 o Warn and fail if server chose a nickname with illegal characters
4660 o Port to Solaris and Sparc:
4661 - include missing header fcntl.h
4662 - have autoconf find -lsocket -lnsl automatically
4663 - deal with hardware word alignment
4664 - make uname() work (solaris has a different return convention)
4665 - switch from using signal() to sigaction()
4666 o Preliminary work on reputation system:
4667 - Keep statistics on success/fail of connect attempts; they're published
4668 by kill -USR1 currently.
4669 - Add a RunTesting option to try to learn link state by creating test
4670 circuits, even when SocksPort is off.
4671 - Remove unused open circuits when there are too many.
4674 Changes in version 0.0.2 - 2004-03-19
4675 - Include strlcpy and strlcat for safer string ops
4676 - define INADDR_NONE so we compile (but still not run) on solaris
4679 Changes in version 0.0.2pre27 - 2004-03-14
4681 - Allow internal tor networks (we were rejecting internal IPs,
4682 now we allow them if they're set explicitly).
4683 - And fix a few endian issues.
4686 Changes in version 0.0.2pre26 - 2004-03-14
4688 - If a stream times out after 15s without a connected cell, don't
4689 try that circuit again: try a new one.
4690 - Retry streams at most 4 times. Then give up.
4691 - When a dirserver gets a descriptor from an unknown router, it
4692 logs its fingerprint (so the dirserver operator can choose to
4693 accept it even without mail from the server operator).
4694 - Inform unapproved servers when we reject their descriptors.
4695 - Make tor build on Windows again. It works as a client, who knows
4697 - Clearer instructions in the torrc for how to set up a server.
4698 - Be more efficient about reading fd's when our global token bucket
4699 (used for rate limiting) becomes empty.
4701 - Stop asserting that computers always go forward in time. It's
4703 - When we sent a cell (e.g. destroy) and then marked an OR connection
4704 expired, we might close it before finishing a flush if the other
4705 side isn't reading right then.
4706 - Don't allow dirservers to start if they haven't defined
4708 - We were caching transient dns failures. Oops.
4709 - Prevent servers from publishing an internal IP as their address.
4710 - Address a strcat vulnerability in circuit.c
4713 Changes in version 0.0.2pre25 - 2004-03-04
4715 - Put the OR's IP in its router descriptor, not its fqdn. That way
4716 we'll stop being stalled by gethostbyname for nodes with flaky dns,
4719 - If the user typed in an address that didn't resolve, the server
4723 Changes in version 0.0.2pre24 - 2004-03-03
4725 - Fix an assertion failure in dns.c, where we were trying to dequeue
4726 a pending dns resolve even if it wasn't pending
4727 - Fix a spurious socks5 warning about still trying to write after the
4728 connection is finished.
4729 - Hold certain marked_for_close connections open until they're finished
4730 flushing, rather than losing bytes by closing them too early.
4731 - Correctly report the reason for ending a stream
4732 - Remove some duplicate calls to connection_mark_for_close
4733 - Put switch_id and start_daemon earlier in the boot sequence, so it
4734 will actually try to chdir() to options.DataDirectory
4735 - Make 'make test' exit(1) if a test fails; fix some unit tests
4736 - Make tor fail when you use a config option it doesn't know about,
4737 rather than warn and continue.
4738 - Make --version work
4739 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
4742 Changes in version 0.0.2pre23 - 2004-02-29
4744 - Print a statement when the first circ is finished, so the user
4746 - If a relay cell is unrecognized at the end of the circuit,
4747 send back a destroy. (So attacks to mutate cells are more
4749 - New config option 'excludenodes' to avoid certain nodes for circuits.
4750 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
4751 so you can collect coredumps there.
4753 - Fix a bug in tls flushing where sometimes data got wedged and
4754 didn't flush until more data got sent. Hopefully this bug was
4755 a big factor in the random delays we were seeing.
4756 - Make 'connected' cells include the resolved IP, so the client
4757 dns cache actually gets populated.
4758 - Disallow changing from ORPort=0 to ORPort>0 on hup.
4759 - When we time-out on a stream and detach from the circuit, send an
4760 end cell down it first.
4761 - Only warn about an unknown router (in exitnodes, entrynodes,
4762 excludenodes) after we've fetched a directory.
4765 Changes in version 0.0.2pre22 - 2004-02-26
4767 - Servers publish less revealing uname information in descriptors.
4768 - More memory tracking and assertions, to crash more usefully when
4770 - If the default torrc isn't there, just use some default defaults.
4771 Plus provide an internal dirservers file if they don't have one.
4772 - When the user tries to use Tor as an http proxy, give them an http
4773 501 failure explaining that we're a socks proxy.
4774 - Dump a new router.desc on hup, to help confused people who change
4775 their exit policies and then wonder why router.desc doesn't reflect
4777 - Clean up the generic tor.sh init script that we ship with.
4779 - If the exit stream is pending on the resolve, and a destroy arrives,
4780 then the stream wasn't getting removed from the pending list. I
4781 think this was the one causing recent server crashes.
4782 - Use a more robust poll on OSX 10.3, since their poll is flaky.
4783 - When it couldn't resolve any dirservers, it was useless from then on.
4784 Now it reloads the RouterFile (or default dirservers) if it has no
4786 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
4787 many users don't even *have* a /usr/local/sbin/.
4790 Changes in version 0.0.2pre21 - 2004-02-18
4792 - There's a ChangeLog file that actually reflects the changelog.
4793 - There's a 'torify' wrapper script, with an accompanying
4794 tor-tsocks.conf, that simplifies the process of using tsocks for
4795 tor. It even has a man page.
4796 - The tor binary gets installed to sbin rather than bin now.
4797 - Retry streams where the connected cell hasn't arrived in 15 seconds
4798 - Clean up exit policy handling -- get the default out of the torrc,
4799 so we can update it without forcing each server operator to fix
4801 - Allow imaps and pop3s in default exit policy
4803 - Prevent picking middleman nodes as the last node in the circuit
4806 Changes in version 0.0.2pre20 - 2004-01-30
4808 - We now have a deb package, and it's in debian unstable. Go to
4810 - I've split the TotalBandwidth option into BandwidthRate (how many
4811 bytes per second you want to allow, long-term) and
4812 BandwidthBurst (how many bytes you will allow at once before the cap
4813 kicks in). This better token bucket approach lets you, say, set
4814 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
4815 performance while not exceeding your monthly bandwidth quota.
4816 - Push out a tls record's worth of data once you've got it, rather
4817 than waiting until you've read everything waiting to be read. This
4818 may improve performance by pipelining better. We'll see.
4819 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
4820 from failed circuits (if they haven't been connected yet) and attach
4822 - Expire old streams that haven't managed to connect. Some day we'll
4823 have them reattach to new circuits instead.
4826 - Fix several memory leaks that were causing servers to become bloated
4828 - Fix a few very rare assert triggers. A few more remain.
4829 - Setuid to User _before_ complaining about running as root.
4832 Changes in version 0.0.2pre19 - 2004-01-07
4834 - Fix deadlock condition in dns farm. We were telling a child to die by
4835 closing the parent's file descriptor to him. But newer children were
4836 inheriting the open file descriptor from the parent, and since they
4837 weren't closing it, the socket never closed, so the child never read
4838 eof, so he never knew to exit. Similarly, dns workers were holding
4839 open other sockets, leading to all sorts of chaos.
4840 - New cleaner daemon() code for forking and backgrounding.
4841 - If you log to a file, it now prints an entry at the top of the
4842 logfile so you know it's working.
4843 - The onionskin challenge length was 30 bytes longer than necessary.
4844 - Started to patch up the spec so it's not quite so out of date.
4847 Changes in version 0.0.2pre18 - 2004-01-02
4849 - Fix endian issues with the 'integrity' field in the relay header.
4850 - Fix a potential bug where connections in state
4851 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
4854 Changes in version 0.0.2pre17 - 2003-12-30
4856 - Made --debuglogfile (or any second log file, actually) work.
4857 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
4858 adversary could force us into an infinite loop.
4861 - Each onionskin handshake now includes a hash of the computed key,
4862 to prove the server's identity and help perfect forward secrecy.
4863 - Changed cell size from 256 to 512 bytes (working toward compatibility
4865 - Changed cell length to 2 bytes, and moved it to the relay header.
4866 - Implemented end-to-end integrity checking for the payloads of
4868 - Separated streamid from 'recognized' (otherwise circuits will get
4869 messed up when we try to have streams exit from the middle). We
4870 use the integrity-checking to confirm that a cell is addressed to
4872 - Randomize the initial circid and streamid values, so an adversary who
4873 breaks into a node can't learn how many circuits or streams have
4877 Changes in version 0.0.2pre16 - 2003-12-14
4879 - Fixed a bug that made HUP trigger an assert
4880 - Fixed a bug where a circuit that immediately failed wasn't being
4881 counted as a failed circuit in counting retries.
4884 - Now we close the circuit when we get a truncated cell: otherwise we're
4885 open to an anonymity attack where a bad node in the path truncates
4886 the circuit and then we open streams at him.
4887 - Add port ranges to exit policies
4888 - Add a conservative default exit policy
4889 - Warn if you're running tor as root
4890 - on HUP, retry OR connections and close/rebind listeners
4891 - options.EntryNodes: try these nodes first when picking the first node
4892 - options.ExitNodes: if your best choices happen to include any of
4893 your preferred exit nodes, you choose among just those preferred
4895 - options.ExcludedNodes: nodes that are never picked in path building
4898 Changes in version 0.0.2pre15 - 2003-12-03
4899 o Robustness and bugfixes:
4900 - Sometimes clients would cache incorrect DNS resolves, which would
4901 really screw things up.
4902 - An OP that goes offline would slowly leak all its sockets and stop
4904 - A wide variety of bugfixes in exit node selection, exit policy
4905 handling, and processing pending streams when a new circuit is
4907 - Pick nodes for a path only from those the directory says are up
4908 - Choose randomly from all running dirservers, not always the first one
4909 - Increase allowed http header size for directory fetch.
4910 - Stop writing to stderr (if we're daemonized it will be closed).
4911 - Enable -g always, so cores will be more useful to me.
4912 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
4915 - Wrote a man page. It lists commonly used options.
4918 - Change default loglevel to warn.
4919 - Make PidFile default to null rather than littering in your CWD.
4920 - OnionRouter config option is now obsolete. Instead it just checks
4922 - Moved to a single unified torrc file for both clients and servers.
4925 Changes in version 0.0.2pre14 - 2003-11-29
4926 o Robustness and bugfixes:
4927 - Force the admin to make the DataDirectory himself
4928 - to get ownership/permissions right
4929 - so clients no longer make a DataDirectory and then never use it
4930 - fix bug where a client who was offline for 45 minutes would never
4931 pull down a directory again
4932 - fix (or at least hide really well) the dns assert bug that was
4933 causing server crashes
4934 - warnings and improved robustness wrt clockskew for certs
4935 - use the native daemon(3) to daemonize, when available
4936 - exit if bind() fails
4937 - exit if neither socksport nor orport is defined
4938 - include our own tor_timegm (Win32 doesn't have its own)
4939 - bugfix for win32 with lots of connections
4940 - fix minor bias in PRNG
4941 - make dirserver more robust to corrupt cached directory
4944 - Wrote the design document (woo)
4946 o Circuit building and exit policies:
4947 - Circuits no longer try to use nodes that the directory has told them
4949 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
4950 bitcounts (18.0.0.0/8).
4951 - Make AP connections standby for a circuit if no suitable circuit
4952 exists, rather than failing
4953 - Circuits choose exit node based on addr/port, exit policies, and
4954 which AP connections are standing by
4955 - Bump min pathlen from 2 to 3
4956 - Relay end cells have a payload to describe why the stream ended.
4957 - If the stream failed because of exit policy, try again with a new
4959 - Clients have a dns cache to remember resolved addresses.
4960 - Notice more quickly when we have no working circuits
4963 - APPort is now called SocksPort
4964 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
4966 - RecommendedVersions is now a config variable rather than
4967 hardcoded (for dirservers)
4968 - Reloads config on HUP
4969 - Usage info on -h or --help
4970 - If you set User and Group config vars, it'll setu/gid to them.
4972 Changes in version 0.0.2pre13 - 2003-10-19
4973 o General stability:
4974 - SSL_write no longer fails when it returns WANTWRITE and the number
4975 of bytes in the buf has changed by the next SSL_write call.
4976 - Fix segfault fetching directory when network is down
4977 - Fix a variety of minor memory leaks
4978 - Dirservers reload the fingerprints file on HUP, so I don't have
4979 to take down the network when I approve a new router
4980 - Default server config file has explicit Address line to specify fqdn
4983 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
4984 - Make listener connections not ever alloc bufs
4986 o Autoconf improvements:
4987 - don't clobber an external CFLAGS in ./configure
4988 - Make install now works
4989 - create var/lib/tor on make install
4990 - autocreate a tor.sh initscript to help distribs
4991 - autocreate the torrc and sample-server-torrc with correct paths
4993 o Log files and Daemonizing now work:
4994 - If --DebugLogFile is specified, log to it at -l debug
4995 - If --LogFile is specified, use it instead of commandline
4996 - If --RunAsDaemon is set, tor forks and backgrounds on startup