1 Changes in version 0.2.1.10-alpha - 2009-??-??
3 - Make get_interface_address() function work properly again; stop
4 guessing the wrong parts of our address as our address.
7 Changes in version 0.2.1.9-alpha - 2008-12-25
8 o New directory authorities:
9 - gabelmoo (the authority run by Karsten Loesing) now has a new
13 - Never use a connection with a mismatched address to extend a
14 circuit, unless that connection is canonical. A canonical
15 connection is one whose address is authenticated by the router's
16 identity key, either in a NETINFO cell or in a router descriptor.
17 - Avoid a possible memory corruption bug when receiving hidden service
18 descriptors. Bugfix on 0.2.1.6-alpha.
21 - Fix a logic error that would automatically reject all but the first
22 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
23 part of bug 813/868. Bug spotted by coderman.
24 - When a stream at an exit relay is in state "resolving" or
25 "connecting" and it receives an "end" relay cell, the exit relay
26 would silently ignore the end cell and not close the stream. If
27 the client never closes the circuit, then the exit relay never
28 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
30 - When we can't initialize DNS because the network is down, do not
31 automatically stop Tor from starting. Instead, retry failed
32 dns_inits() every 10 minutes, and change the exit policy to reject
33 *:* until one succeeds. Fixes bug 691.
36 - Give a better error message when an overzealous init script says
37 "sudo -u username tor --user username". Makes Bug 882 easier for
39 - When a directory authority gives us a new guess for our IP address,
40 log which authority we used. Hopefully this will help us debug
41 the recent complaints about bad IP address guesses.
42 - Detect svn revision properly when we're using git-svn.
43 - Try not to open more than one descriptor-downloading connection
44 to an authority at once. This should reduce load on directory
45 authorities. Fixes bug 366.
46 - Add cross-certification to newly generated certificates, so that
47 a signing key is enough information to look up a certificate.
48 Partial implementation of proposal 157.
49 - Start serving certificates by <identity digest, signing key digest>
50 pairs. Partial implementation of proposal 157.
51 - Clients now never report any stream end reason except 'MISC'.
52 Implements proposal 148.
53 - On platforms with a maximum syslog string length, truncate syslog
54 messages to that length ourselves, rather than relying on the
55 system to do it for us.
56 - Optimize out calls to time(NULL) that occur for every IO operation,
57 or for every cell. On systems where time() is a slow syscall,
58 this fix will be slightly helpful.
59 - Exit servers can now answer resolve requests for ip6.arpa addresses.
60 - When we download a descriptor that we then immediately (as
61 a directory authority) reject, do not retry downloading it right
62 away. Should save some bandwidth on authorities. Fix for bug
63 888. Patch by Sebastian Hahn.
64 - When a download gets us zero good descriptors, do not notify
65 Tor that new directory information has arrived.
66 - Avoid some nasty corner cases in the logic for marking connections
67 as too old or obsolete or noncanonical for circuits.
69 o Minor features (controller):
70 - New CONSENSUS_ARRIVED event to note when a new consensus has
71 been fetched and validated.
72 - When we realize that another process has modified our cached
73 descriptors file, print out a more useful error message rather
74 than triggering an assertion. Fixes bug 885. Patch from Karsten.
75 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
76 controllers to prevent SIGHUP from reloading the
77 configuration. Fixes bug 856.
80 - Resume using the correct "REASON=" stream when telling the
81 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
82 - When a canonical connection appears later in our internal list
83 than a noncanonical one for a given OR ID, always use the
84 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
86 - Clip the MaxCircuitDirtiness config option to a minimum of 10
87 seconds. Warn the user if lower values are given in the
88 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
89 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
90 user if lower values are given in the configuration. Bugfix on
91 0.1.1.17-rc. Patch by Sebastian.
92 - Fix a race condition when freeing keys shared between main thread
93 and CPU workers that could result in a memory leak. Bugfix on
94 0.1.0.1-rc. Fixes bug 889.
96 o Minor bugfixes (hidden services):
97 - Do not throw away existing introduction points on SIGHUP (bugfix on
98 0.0.6pre1); also, do not stall hidden services because we're
99 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
100 by John Brooks. Patch by Karsten. Fixes bug 874.
101 - Fix a memory leak when we decline to add a v2 rendezvous
102 descriptor to the cache because we already had a v0 descriptor
103 with the same ID. Bugfix on 0.2.0.18-alpha.
105 o Deprecated and removed features:
106 - RedirectExits has been removed. It was deprecated since
108 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
109 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
110 - Cell pools are now always enabled; --disable-cell-pools is ignored.
112 o Code simplifications and refactoring:
113 - Rename the confusing or_is_obsolete field to the more appropriate
114 is_bad_for_new_circs, and move it to or_connection_t where it
116 - Move edge-only flags from connection_t to edge_connection_t: not
117 only is this better coding, but on machines of plausible alignment,
118 it should save 4-8 bytes per connection_t. "Every little bit helps."
119 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
120 for consistency; keep old option working for backward compatibility.
121 - Simplify the code for finding connections to use for a circuit.
124 Changes in version 0.2.1.8-alpha - 2008-12-08
125 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
126 builds better on unusual platforms like Solaris and old OS X, and
127 fixes a variety of other issues.
130 - New DirPortFrontPage option that takes an html file and publishes
131 it as "/" on the DirPort. Now relay operators can provide a
132 disclaimer without needing to set up a separate webserver. There's
133 a sample disclaimer in contrib/tor-exit-notice.html.
136 - When the client is choosing entry guards, now it selects at most
137 one guard from a given relay family. Otherwise we could end up with
138 all of our entry points into the network run by the same operator.
139 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
142 - Fix a DOS opportunity during the voting signature collection process
143 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
144 - Fix a possible segfault when establishing an exit connection. Bugfix
148 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
150 - Made Tor a little less aggressive about deleting expired
151 certificates. Partial fix for bug 854.
152 - Stop doing unaligned memory access that generated bus errors on
153 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
154 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
155 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
156 - Make USR2 log-level switch take effect immediately. Bugfix on
158 - If one win32 nameserver fails to get added, continue adding the
159 rest, and don't automatically fail.
160 - Use fcntl() for locking when flock() is not available. Should fix
161 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
162 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
163 could make gcc generate non-functional binary search code. Bugfix
165 - Build correctly on platforms without socklen_t.
166 - Avoid potential crash on internal error during signature collection.
167 Fixes bug 864. Patch from rovv.
168 - Do not use C's stdio library for writing to log files. This will
169 improve logging performance by a minute amount, and will stop
170 leaking fds when our disk is full. Fixes bug 861.
171 - Stop erroneous use of O_APPEND in cases where we did not in fact
172 want to re-seek to the end of a file before every last write().
173 - Correct handling of possible malformed authority signing key
174 certificates with internal signature types. Fixes bug 880. Bugfix
176 - Fix a hard-to-trigger resource leak when logging credential status.
180 - Directory mirrors no longer fetch the v1 directory or
181 running-routers files. They are obsolete, and nobody asks for them
182 anymore. This is the first step to making v1 authorities obsolete.
184 o Minor features (controller):
185 - Return circuit purposes in response to GETINFO circuit-status. Fixes
189 Changes in version 0.2.0.32 - 2008-11-20
190 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
191 packages (and maybe other packages) noticed by Theo de Raadt, fixes
192 a smaller security flaw that might allow an attacker to access local
193 services, further improves hidden service performance, and fixes a
194 variety of other issues.
197 - The "User" and "Group" config options did not clear the
198 supplementary group entries for the Tor process. The "User" option
199 is now more robust, and we now set the groups to the specified
200 user's primary group. The "Group" option is now ignored. For more
201 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
202 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
203 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
204 - The "ClientDNSRejectInternalAddresses" config option wasn't being
205 consistently obeyed: if an exit relay refuses a stream because its
206 exit policy doesn't allow it, we would remember what IP address
207 the relay said the destination address resolves to, even if it's
208 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
211 - Fix a DOS opportunity during the voting signature collection process
212 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
214 o Major bugfixes (hidden services):
215 - When fetching v0 and v2 rendezvous service descriptors in parallel,
216 we were failing the whole hidden service request when the v0
217 descriptor fetch fails, even if the v2 fetch is still pending and
218 might succeed. Similarly, if the last v2 fetch fails, we were
219 failing the whole hidden service request even if a v0 fetch is
220 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
221 - When extending a circuit to a hidden service directory to upload a
222 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
223 requests failed, because the router descriptor has not been
224 downloaded yet. In these cases, do not attempt to upload the
225 rendezvous descriptor, but wait until the router descriptor is
226 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
227 descriptor from a hidden service directory for which the router
228 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
232 - Fix several infrequent memory leaks spotted by Coverity.
233 - When testing for libevent functions, set the LDFLAGS variable
234 correctly. Found by Riastradh.
235 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
236 bootstrapping with tunneled directory connections. Bugfix on
237 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
238 - When asked to connect to A.B.exit:80, if we don't know the IP for A
239 and we know that server B rejects most-but-not all connections to
240 port 80, we would previously reject the connection. Now, we assume
241 the user knows what they were asking for. Fixes bug 752. Bugfix
242 on 0.0.9rc5. Diagnosed by BarkerJr.
243 - If we overrun our per-second write limits a little, count this as
244 having used up our write allocation for the second, and choke
245 outgoing directory writes. Previously, we had only counted this when
246 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
247 Bugfix on 0.2.0.x (??).
248 - Remove the old v2 directory authority 'lefkada' from the default
249 list. It has been gone for many months.
250 - Stop doing unaligned memory access that generated bus errors on
251 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
252 - Make USR2 log-level switch take effect immediately. Bugfix on
255 o Minor bugfixes (controller):
256 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
257 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
260 Changes in version 0.2.1.7-alpha - 2008-11-08
261 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
262 packages (and maybe other packages) noticed by Theo de Raadt, fixes
263 a smaller security flaw that might allow an attacker to access local
264 services, adds better defense against DNS poisoning attacks on exit
265 relays, further improves hidden service performance, and fixes a
266 variety of other issues.
269 - The "ClientDNSRejectInternalAddresses" config option wasn't being
270 consistently obeyed: if an exit relay refuses a stream because its
271 exit policy doesn't allow it, we would remember what IP address
272 the relay said the destination address resolves to, even if it's
273 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
274 - The "User" and "Group" config options did not clear the
275 supplementary group entries for the Tor process. The "User" option
276 is now more robust, and we now set the groups to the specified
277 user's primary group. The "Group" option is now ignored. For more
278 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
279 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
280 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
281 - Do not use or believe expired v3 authority certificates. Patch
282 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
285 - Now NodeFamily and MyFamily config options allow spaces in
286 identity fingerprints, so it's easier to paste them in.
287 Suggested by Lucky Green.
288 - Implement the 0x20 hack to better resist DNS poisoning: set the
289 case on outgoing DNS requests randomly, and reject responses that do
290 not match the case correctly. This logic can be disabled with the
291 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
292 of servers that do not reliably preserve case in replies. See
293 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
295 - Preserve case in replies to DNSPort requests in order to support
296 the 0x20 hack for resisting DNS poisoning attacks.
298 o Hidden service performance improvements:
299 - When the client launches an introduction circuit, retry with a
300 new circuit after 30 seconds rather than 60 seconds.
301 - Launch a second client-side introduction circuit in parallel
302 after a delay of 15 seconds (based on work by Christian Wilms).
303 - Hidden services start out building five intro circuits rather
304 than three, and when the first three finish they publish a service
305 descriptor using those. Now we publish our service descriptor much
306 faster after restart.
309 - Minor fix in the warning messages when you're having problems
310 bootstrapping; also, be more forgiving of bootstrap problems when
311 we're still making incremental progress on a given bootstrap phase.
312 - When we're choosing an exit node for a circuit, and we have
313 no pending streams, choose a good general exit rather than one that
314 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
315 - Send a valid END cell back when a client tries to connect to a
316 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
317 840. Patch from rovv.
318 - If a broken client asks a non-exit router to connect somewhere,
319 do not even do the DNS lookup before rejecting the connection.
320 Fixes another case of bug 619. Patch from rovv.
321 - Fix another case of assuming, when a specific exit is requested,
322 that we know more than the user about what hosts it allows.
323 Fixes another case of bug 752. Patch from rovv.
324 - Check which hops rendezvous stream cells are associated with to
325 prevent possible guess-the-streamid injection attacks from
326 intermediate hops. Fixes another case of bug 446. Based on patch
328 - Avoid using a negative right-shift when comparing 32-bit
329 addresses. Possible fix for bug 845 and bug 811.
330 - Make the assert_circuit_ok() function work correctly on circuits that
331 have already been marked for close.
332 - Fix read-off-the-end-of-string error in unit tests when decoding
334 - Fix uninitialized size field for memory area allocation: may improve
335 memory performance during directory parsing.
336 - Treat duplicate certificate fetches as failures, so that we do
337 not try to re-fetch an expired certificate over and over and over.
338 - Do not say we're fetching a certificate when we'll in fact skip it
339 because of a pending download.
342 Changes in version 0.2.1.6-alpha - 2008-09-30
343 Tor 0.2.1.6-alpha further improves performance and robustness of
344 hidden services, starts work on supporting per-country relay selection,
345 and fixes a variety of smaller issues.
348 - Implement proposal 121: make it possible to build hidden services
349 that only certain clients are allowed to connect to. This is
350 enforced at several points, so that unauthorized clients are unable
351 to send INTRODUCE cells to the service, or even (depending on the
352 type of authentication) to learn introduction points. This feature
353 raises the bar for certain kinds of active attacks against hidden
354 services. Code by Karsten Loesing.
355 - Relays now store and serve v2 hidden service descriptors by default,
356 i.e., the new default value for HidServDirectoryV2 is 1. This is
357 the last step in proposal 114, which aims to make hidden service
358 lookups more reliable.
359 - Start work to allow node restrictions to include country codes. The
360 syntax to exclude nodes in a country with country code XX is
361 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
362 refinement to decide what config options should take priority if
363 you ask to both use a particular node and exclude it.
364 - Allow ExitNodes list to include IP ranges and country codes, just
365 like the Exclude*Nodes lists. Patch from Robert Hogan.
368 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
369 Tor to fail to start if you had it configured to use a bridge
370 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
371 - When extending a circuit to a hidden service directory to upload a
372 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
373 requests failed, because the router descriptor had not been
374 downloaded yet. In these cases, we now wait until the router
375 descriptor is downloaded, and then retry. Likewise, clients
376 now skip over a hidden service directory if they don't yet have
377 its router descriptor, rather than futilely requesting it and
378 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
380 - When fetching v0 and v2 rendezvous service descriptors in parallel,
381 we were failing the whole hidden service request when the v0
382 descriptor fetch fails, even if the v2 fetch is still pending and
383 might succeed. Similarly, if the last v2 fetch fails, we were
384 failing the whole hidden service request even if a v0 fetch is
385 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
386 - DNS replies need to have names matching their requests, but
387 these names should be in the questions section, not necessarily
388 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
391 - Update to the "September 1 2008" ip-to-country file.
392 - Allow ports 465 and 587 in the default exit policy again. We had
393 rejected them in 0.1.0.15, because back in 2005 they were commonly
394 misconfigured and ended up as spam targets. We hear they are better
395 locked down these days.
396 - Use a lockfile to make sure that two Tor processes are not
397 simultaneously running with the same datadir.
398 - Serve the latest v3 networkstatus consensus via the control
399 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
400 - Better logging about stability/reliability calculations on directory
402 - Drop the requirement to have an open dir port for storing and
403 serving v2 hidden service descriptors.
404 - Directory authorities now serve a /tor/dbg-stability.txt URL to
405 help debug WFU and MTBF calculations.
406 - Implement most of Proposal 152: allow specialized servers to permit
407 single-hop circuits, and clients to use those servers to build
408 single-hop circuits when using a specialized controller. Patch
409 from Josh Albrecht. Resolves feature request 768.
410 - Add a -p option to tor-resolve for specifying the SOCKS port: some
411 people find host:port too confusing.
412 - Make TrackHostExit mappings expire a while after their last use, not
413 after their creation. Patch from Robert Hogan.
414 - Provide circuit purposes along with circuit events to the controller.
417 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
419 - Fixed some memory leaks -- some quite frequent, some almost
420 impossible to trigger -- based on results from Coverity.
421 - When testing for libevent functions, set the LDFLAGS variable
422 correctly. Found by Riastradh.
423 - Fix an assertion bug in parsing policy-related options; possible fix
425 - Catch and report a few more bootstrapping failure cases when Tor
426 fails to establish a TCP connection. Cleanup on 0.2.1.x.
427 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
428 bootstrapping with tunneled directory connections. Bugfix on
429 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
430 - When asked to connect to A.B.exit:80, if we don't know the IP for A
431 and we know that server B rejects most-but-not all connections to
432 port 80, we would previously reject the connection. Now, we assume
433 the user knows what they were asking for. Fixes bug 752. Bugfix
434 on 0.0.9rc5. Diagnosed by BarkerJr.
435 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
436 service directories if they have no advertised dir port. Bugfix
438 - If we overrun our per-second write limits a little, count this as
439 having used up our write allocation for the second, and choke
440 outgoing directory writes. Previously, we had only counted this when
441 we had met our limits precisely. Fixes bug 824. Patch by rovv.
442 Bugfix on 0.2.0.x (??).
443 - Avoid a "0 divided by 0" calculation when calculating router uptime
444 at directory authorities. Bugfix on 0.2.0.8-alpha.
445 - Make DNS resolved controller events into "CLOSED", not
446 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
448 - Fix a bug where an unreachable relay would establish enough
449 reachability testing circuits to do a bandwidth test -- if
450 we already have a connection to the middle hop of the testing
451 circuit, then it could establish the last hop by using the existing
452 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
453 circuits no longer use entry guards in 0.2.1.3-alpha.
454 - If we have correct permissions on $datadir, we complain to stdout
455 and fail to start. But dangerous permissions on
456 $datadir/cached-status/ would cause us to open a log and complain
457 there. Now complain to stdout and fail to start in both cases. Fixes
458 bug 820, reported by seeess.
459 - Remove the old v2 directory authority 'lefkada' from the default
460 list. It has been gone for many months.
462 o Code simplifications and refactoring:
463 - Revise the connection_new functions so that a more typesafe variant
464 exists. This will work better with Coverity, and let us find any
465 actual mistakes we're making here.
466 - Refactor unit testing logic so that dmalloc can be used sensibly
467 with unit tests to check for memory leaks.
468 - Move all hidden-service related fields from connection and circuit
469 structure to substructures: this way they won't eat so much memory.
472 Changes in version 0.2.0.31 - 2008-09-03
473 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
474 a big bug we're seeing where in rare cases traffic from one Tor stream
475 gets mixed into another stream, and fixes a variety of smaller issues.
478 - Make sure that two circuits can never exist on the same connection
479 with the same circuit ID, even if one is marked for close. This
480 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
481 - Relays now reject risky extend cells: if the extend cell includes
482 a digest of all zeroes, or asks to extend back to the relay that
483 sent the extend cell, tear down the circuit. Ideas suggested
485 - If not enough of our entry guards are available so we add a new
486 one, we might use the new one even if it overlapped with the
487 current circuit's exit relay (or its family). Anonymity bugfix
491 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
492 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
493 - Correctly detect the presence of the linux/netfilter_ipv4.h header
494 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
495 - Pick size of default geoip filename string correctly on windows.
496 Fixes bug 806. Bugfix on 0.2.0.30.
497 - Make the autoconf script accept the obsolete --with-ssl-dir
498 option as an alias for the actually-working --with-openssl-dir
499 option. Fix the help documentation to recommend --with-openssl-dir.
500 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
501 - Disallow session resumption attempts during the renegotiation
502 stage of the v2 handshake protocol. Clients should never be trying
503 session resumption at this point, but apparently some did, in
504 ways that caused the handshake to fail. Bug found by Geoff Goodell.
505 Bugfix on 0.2.0.20-rc.
506 - When using the TransPort option on OpenBSD, and using the User
507 option to change UID and drop privileges, make sure to open
508 /dev/pf before dropping privileges. Fixes bug 782. Patch from
509 Christopher Davis. Bugfix on 0.1.2.1-alpha.
510 - Try to attach connections immediately upon receiving a RENDEZVOUS2
511 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
512 on the client side when connecting to a hidden service. Bugfix
513 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
514 - When closing an application-side connection because its circuit is
515 getting torn down, generate the stream event correctly. Bugfix on
516 0.1.2.x. Anonymous patch.
519 Changes in version 0.2.1.5-alpha - 2008-08-31
520 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
521 in a lot of the infrastructure for adding authorization to hidden
522 services, lays the groundwork for having clients read their load
523 balancing information out of the networkstatus consensus rather than
524 the individual router descriptors, addresses two potential anonymity
525 issues, and fixes a variety of smaller issues.
528 - Convert many internal address representations to optionally hold
530 - Generate and accept IPv6 addresses in many protocol elements.
531 - Make resolver code handle nameservers located at ipv6 addresses.
532 - Begin implementation of proposal 121 ("Client authorization for
533 hidden services"): configure hidden services with client
534 authorization, publish descriptors for them, and configure
535 authorization data for hidden services at clients. The next
536 step is to actually access hidden services that perform client
538 - More progress toward proposal 141: Network status consensus
539 documents and votes now contain bandwidth information for each
540 router and a summary of that router's exit policy. Eventually this
541 will be used by clients so that they do not have to download every
542 known descriptor before building circuits.
544 o Major bugfixes (on 0.2.0.x and before):
545 - When sending CREATED cells back for a given circuit, use a 64-bit
546 connection ID to find the right connection, rather than an addr:port
547 combination. Now that we can have multiple OR connections between
548 the same ORs, it is no longer possible to use addr:port to uniquely
549 identify a connection.
550 - Relays now reject risky extend cells: if the extend cell includes
551 a digest of all zeroes, or asks to extend back to the relay that
552 sent the extend cell, tear down the circuit. Ideas suggested
554 - If not enough of our entry guards are available so we add a new
555 one, we might use the new one even if it overlapped with the
556 current circuit's exit relay (or its family). Anonymity bugfix
560 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
561 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
562 - When using the TransPort option on OpenBSD, and using the User
563 option to change UID and drop privileges, make sure to open /dev/pf
564 before dropping privileges. Fixes bug 782. Patch from Christopher
565 Davis. Bugfix on 0.1.2.1-alpha.
566 - Correctly detect the presence of the linux/netfilter_ipv4.h header
567 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
568 - Add a missing safe_str() call for a debug log message.
569 - Use 64 bits instead of 32 bits for connection identifiers used with
570 the controller protocol, to greatly reduce risk of identifier reuse.
571 - Make the autoconf script accept the obsolete --with-ssl-dir
572 option as an alias for the actually-working --with-openssl-dir
573 option. Fix the help documentation to recommend --with-openssl-dir.
574 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
577 - Rate-limit too-many-sockets messages: when they happen, they happen
578 a lot. Resolves bug 748.
579 - Resist DNS poisoning a little better by making sure that names in
580 answer sections match.
581 - Print the SOCKS5 error message string as well as the error code
582 when a tor-resolve request fails. Patch from Jacob.
585 Changes in version 0.2.1.4-alpha - 2008-08-04
586 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
589 - The address part of exit policies was not correctly written
590 to router descriptors. This generated router descriptors that failed
591 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
593 - Tor triggered a false assert when extending a circuit to a relay
594 but we already have a connection open to that relay. Noticed by
595 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
598 - Fix a hidden service logging bug: in some edge cases, the router
599 descriptor of a previously picked introduction point becomes
600 obsolete and we need to give up on it rather than continually
601 complaining that it has become obsolete. Observed by xiando. Bugfix
605 - Take out the TestVia config option, since it was a workaround for
606 a bug that was fixed in Tor 0.1.1.21.
609 Changes in version 0.2.1.3-alpha - 2008-08-03
610 Tor 0.2.1.3-alpha implements most of the pieces to prevent
611 infinite-length circuit attacks (see proposal 110); fixes a bug that
612 might cause exit relays to corrupt streams they send back; allows
613 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
614 ExcludeExitNodes config options; and fixes a big pile of bugs.
616 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
617 - Send a bootstrap problem "warn" event on the first problem if the
618 reason is NO_ROUTE (that is, our network is down).
621 - Implement most of proposal 110: The first K cells to be sent
622 along a circuit are marked as special "early" cells; only K "early"
623 cells will be allowed. Once this code is universal, we can block
624 certain kinds of DOS attack by requiring that EXTEND commands must
625 be sent using an "early" cell.
628 - Try to attach connections immediately upon receiving a RENDEZVOUS2
629 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
630 on the client side when connecting to a hidden service. Bugfix
631 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
632 - Ensure that two circuits can never exist on the same connection
633 with the same circuit ID, even if one is marked for close. This
634 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
637 - When relays do their initial bandwidth measurement, don't limit
638 to just our entry guards for the test circuits. Otherwise we tend
639 to have multiple test circuits going through a single entry guard,
640 which makes our bandwidth test less accurate. Fixes part of bug 654;
641 patch contributed by Josh Albrecht.
642 - Add an ExcludeExitNodes option so users can list a set of nodes
643 that should be be excluded from the exit node position, but
644 allowed elsewhere. Implements proposal 151.
645 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
646 ExcludeNodes and ExcludeExitNodes lists.
647 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
648 be more efficient. Formerly it was quadratic in the number of
649 servers; now it should be linear. Fixes bug 509.
650 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
651 and n_conn_id_digest fields into a separate structure that's
652 only needed when the circuit has not yet attached to an n_conn.
655 - Change the contrib/tor.logrotate script so it makes the new
656 logs as "_tor:_tor" rather than the default, which is generally
657 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
658 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
659 warnings (occasionally), but it can also cause the compiler to
660 eliminate error-checking code. Suggested by Peter Gutmann.
661 - When a hidden service is giving up on an introduction point candidate
662 that was not included in the last published rendezvous descriptor,
663 don't reschedule publication of the next descriptor. Fixes bug 763.
665 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
666 HiddenServiceExcludeNodes as obsolete: they never worked properly,
667 and nobody claims to be using them. Fixes bug 754. Bugfix on
668 0.1.0.1-rc. Patch from Christian Wilms.
669 - Fix a small alignment and memory-wasting bug on buffer chunks.
672 o Minor bugfixes (controller):
673 - When closing an application-side connection because its circuit
674 is getting torn down, generate the stream event correctly.
675 Bugfix on 0.1.2.x. Anonymous patch.
678 - Remove all backward-compatibility code to support relays running
679 versions of Tor so old that they no longer work at all on the
683 Changes in version 0.2.0.29-rc - 2008-07-08
684 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
685 hidden-service performance bugs, and fixes a bunch of smaller bugs.
688 - If you have more than one bridge but don't know their keys,
689 you would only launch a request for the descriptor of the first one
690 on your list. (Tor considered launching requests for the others, but
691 found that it already had a connection on the way for $0000...0000
692 so it didn't open another.) Bugfix on 0.2.0.x.
693 - If you have more than one bridge but don't know their keys, and the
694 connection to one of the bridges failed, you would cancel all
695 pending bridge connections. (After all, they all have the same
696 digest.) Bugfix on 0.2.0.x.
697 - When a hidden service was trying to establish an introduction point,
698 and Tor had built circuits preemptively for such purposes, we
699 were ignoring all the preemptive circuits and launching a new one
700 instead. Bugfix on 0.2.0.14-alpha.
701 - When a hidden service was trying to establish an introduction point,
702 and Tor *did* manage to reuse one of the preemptively built
703 circuits, it didn't correctly remember which one it used,
704 so it asked for another one soon after, until there were no
705 more preemptive circuits, at which point it launched one from
706 scratch. Bugfix on 0.0.9.x.
707 - Make directory servers include the X-Your-Address-Is: http header in
708 their responses even for begin_dir conns. Now clients who only
709 ever use begin_dir connections still have a way to learn their IP
710 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
713 - Fix a macro/CPP interaction that was confusing some compilers:
714 some GCCs don't like #if/#endif pairs inside macro arguments.
716 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
717 Fixes bug 704; fix from Steven Murdoch.
718 - When opening /dev/null in finish_daemonize(), do not pass the
719 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
720 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
721 - Correctly detect transparent proxy support on Linux hosts that
722 require in.h to be included before netfilter_ipv4.h. Patch
724 - Disallow session resumption attempts during the renegotiation
725 stage of the v2 handshake protocol. Clients should never be trying
726 session resumption at this point, but apparently some did, in
727 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
728 found by Geoff Goodell.
731 Changes in version 0.2.1.2-alpha - 2008-06-20
732 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
733 make it easier to set up your own private Tor network; fixes several
734 big bugs with using more than one bridge relay; fixes a big bug with
735 offering hidden services quickly after Tor starts; and uses a better
736 API for reporting potential bootstrapping problems to the controller.
739 - New TestingTorNetwork config option to allow adjustment of
740 previously constant values that, while reasonable, could slow
741 bootstrapping. Implements proposal 135. Patch from Karsten.
744 - If you have more than one bridge but don't know their digests,
745 you would only learn a request for the descriptor of the first one
746 on your list. (Tor considered launching requests for the others, but
747 found that it already had a connection on the way for $0000...0000
748 so it didn't open another.) Bugfix on 0.2.0.x.
749 - If you have more than one bridge but don't know their digests,
750 and the connection to one of the bridges failed, you would cancel
751 all pending bridge connections. (After all, they all have the
752 same digest.) Bugfix on 0.2.0.x.
753 - When establishing a hidden service, introduction points that
754 originate from cannibalized circuits are completely ignored and not
755 included in rendezvous service descriptors. This might be another
756 reason for delay in making a hidden service available. Bugfix
757 from long ago (0.0.9.x?)
760 - Allow OpenSSL to use dynamic locks if it wants.
761 - When building a consensus, do not include routers that are down.
762 This will cut down 30% to 40% on consensus size. Implements
764 - In directory authorities' approved-routers files, allow
765 fingerprints with or without space.
766 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
767 controller can query our current bootstrap state in case it attaches
768 partway through and wants to catch up.
769 - Send an initial "Starting" bootstrap status event, so we have a
770 state to start out in.
773 - Asking for a conditional consensus at .../consensus/<fingerprints>
774 would crash a dirserver if it did not already have a
775 consensus. Bugfix on 0.2.1.1-alpha.
776 - Clean up some macro/CPP interactions: some GCC versions don't like
777 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
780 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
781 - Directory authorities shouldn't complain about bootstrapping
782 problems just because they do a lot of reachability testing and
783 some of the connection attempts fail.
784 - Start sending "count" and "recommendation" key/value pairs in
785 bootstrap problem status events, so the controller can hear about
786 problems even before Tor decides they're worth reporting for sure.
787 - If you're using bridges, generate "bootstrap problem" warnings
788 as soon as you run out of working bridges, rather than waiting
789 for ten failures -- which will never happen if you have less than
791 - If we close our OR connection because there's been a circuit
792 pending on it for too long, we were telling our bootstrap status
793 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
796 Changes in version 0.2.1.1-alpha - 2008-06-13
797 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
798 were making the Tor process bloat especially on Linux; makes our TLS
799 handshake blend in better; sends "bootstrap phase" status events to
800 the controller, so it can keep the user informed of progress (and
801 problems) fetching directory information and establishing circuits;
802 and adds a variety of smaller features.
805 - More work on making our TLS handshake blend in: modify the list
806 of ciphers advertised by OpenSSL in client mode to even more
807 closely resemble a common web browser. We cheat a little so that
808 we can advertise ciphers that the locally installed OpenSSL doesn't
810 - Start sending "bootstrap phase" status events to the controller,
811 so it can keep the user informed of progress fetching directory
812 information and establishing circuits. Also inform the controller
813 if we think we're stuck at a particular bootstrap phase. Implements
815 - Resume using OpenSSL's RAND_poll() for better (and more portable)
816 cross-platform entropy collection again. We used to use it, then
817 stopped using it because of a bug that could crash systems that
818 called RAND_poll when they had a lot of fds open. It looks like the
819 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
820 at startup, and to call RAND_poll() when we reseed later only if
821 we have a non-buggy OpenSSL version.
824 - When we choose to abandon a new entry guard because we think our
825 older ones might be better, close any circuits pending on that
826 new entry guard connection. This fix should make us recover much
827 faster when our network is down and then comes back. Bugfix on
828 0.1.2.8-beta; found by lodger.
830 o Memory fixes and improvements:
831 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
832 to avoid unused RAM in buffer chunks and memory pools.
833 - Speed up parsing and cut down on memory fragmentation by using
834 stack-style allocations for parsing directory objects. Previously,
835 this accounted for over 40% of allocations from within Tor's code
836 on a typical directory cache.
837 - Use a Bloom filter rather than a digest-based set to track which
838 descriptors we need to keep around when we're cleaning out old
839 router descriptors. This speeds up the computation significantly,
840 and may reduce fragmentation.
841 - Reduce the default smartlist size from 32 to 16; it turns out that
842 most smartlists hold around 8-12 elements tops.
843 - Make dumpstats() log the fullness and size of openssl-internal
845 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
846 patch to their OpenSSL, turn it on to save memory on servers. This
847 patch will (with any luck) get included in a mainline distribution
849 - Never use OpenSSL compression: it wastes RAM and CPU trying to
850 compress cells, which are basically all encrypted, compressed,
854 - Stop reloading the router list from disk for no reason when we
855 run out of reachable directory mirrors. Once upon a time reloading
856 it would set the 'is_running' flag back to 1 for them. It hasn't
857 done that for a long time.
858 - In very rare situations new hidden service descriptors were
859 published earlier than 30 seconds after the last change to the
860 service. (We currently think that a hidden service descriptor
861 that's been stable for 30 seconds is worth publishing.)
864 - Allow separate log levels to be configured for different logging
865 domains. For example, this allows one to log all notices, warnings,
866 or errors, plus all memory management messages of level debug or
867 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
868 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
869 and stop using a warning that had become unfixably verbose under
871 - New --hush command-line option similar to --quiet. While --quiet
872 disables all logging to the console on startup, --hush limits the
873 output to messages of warning and error severity.
874 - Servers support a new URL scheme for consensus downloads that
875 allows the client to specify which authorities are trusted.
876 The server then only sends the consensus if the client will trust
877 it. Otherwise a 404 error is sent back. Clients use this
878 new scheme when the server supports it (meaning it's running
879 0.2.1.1-alpha or later). Implements proposal 134.
880 - New configure/torrc options (--enable-geoip-stats,
881 DirRecordUsageByCountry) to record how many IPs we've served
882 directory info to in each country code, how many status documents
883 total we've sent to each country code, and what share of the total
884 directory requests we should expect to see.
885 - Use the TLS1 hostname extension to more closely resemble browser
887 - Lots of new unit tests.
888 - Add a macro to implement the common pattern of iterating through
889 two parallel lists in lockstep.
892 Changes in version 0.2.0.28-rc - 2008-06-13
893 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
894 performance bug, and fixes a bunch of smaller bugs.
897 - Fix a bug where, when we were choosing the 'end stream reason' to
898 put in our relay end cell that we send to the exit relay, Tor
899 clients on Windows were sometimes sending the wrong 'reason'. The
900 anonymity problem is that exit relays may be able to guess whether
901 the client is running Windows, thus helping partition the anonymity
902 set. Down the road we should stop sending reasons to exit relays,
903 or otherwise prevent future versions of this bug.
906 - While setting up a hidden service, some valid introduction circuits
907 were overlooked and abandoned. This might be the reason for
908 the long delay in making a hidden service available. Bugfix on
912 - Update to the "June 9 2008" ip-to-country file.
913 - Run 'make test' as part of 'make dist', so we stop releasing so
914 many development snapshots that fail their unit tests.
917 - When we're checking if we have enough dir info for each relay
918 to begin establishing circuits, make sure that we actually have
919 the descriptor listed in the consensus, not just any descriptor.
921 - Bridge relays no longer print "xx=0" in their extrainfo document
922 for every single country code in the geoip db. Bugfix on
924 - Only warn when we fail to load the geoip file if we were planning to
925 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
926 - If we change our MaxAdvertisedBandwidth and then reload torrc,
927 Tor won't realize it should publish a new relay descriptor. Fixes
928 bug 688, reported by mfr. Bugfix on 0.1.2.x.
929 - When we haven't had any application requests lately, don't bother
930 logging that we have expired a bunch of descriptors. Bugfix
932 - Make relay cells written on a connection count as non-padding when
933 tracking how long a connection has been in use. Bugfix on
934 0.2.0.1-alpha. Spotted by lodger.
935 - Fix unit tests in 0.2.0.27-rc.
936 - Fix compile on Windows.
939 Changes in version 0.2.0.27-rc - 2008-06-03
940 Tor 0.2.0.27-rc adds a few features we left out of the earlier
941 release candidates. In particular, we now include an IP-to-country
942 GeoIP database, so controllers can easily look up what country a
943 given relay is in, and so bridge relays can give us some sanitized
944 summaries about which countries are making use of bridges. (See proposal
945 126-geoip-fetching.txt for details.)
948 - Include an IP-to-country GeoIP file in the tarball, so bridge
949 relays can report sanitized summaries of the usage they're seeing.
952 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
953 Robert Hogan. Fixes the first part of bug 681.
954 - Make bridge authorities never serve extrainfo docs.
955 - Add support to detect Libevent versions in the 1.4.x series
957 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
958 - Include a new contrib/tor-exit-notice.html file that exit relay
959 operators can put on their website to help reduce abuse queries.
962 - When tunneling an encrypted directory connection, and its first
963 circuit fails, do not leave it unattached and ask the controller
964 to deal. Fixes the second part of bug 681.
965 - Make bridge authorities correctly expire old extrainfo documents
969 Changes in version 0.2.0.26-rc - 2008-05-13
970 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
971 in Debian's OpenSSL packages. All users running any 0.2.0.x version
972 should upgrade, whether they're running Debian or not.
974 o Major security fixes:
975 - Use new V3 directory authority keys on the tor26, gabelmoo, and
976 moria1 V3 directory authorities. The old keys were generated with
977 a vulnerable version of Debian's OpenSSL package, and must be
978 considered compromised. Other authorities' keys were not generated
979 with an affected version of OpenSSL.
982 - List authority signatures as "unrecognized" based on DirServer
983 lines, not on cert cache. Bugfix on 0.2.0.x.
986 - Add a new V3AuthUseLegacyKey option to make it easier for
987 authorities to change their identity keys if they have to.
990 Changes in version 0.2.0.25-rc - 2008-04-23
991 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
994 - Remember to initialize threading before initializing logging.
995 Otherwise, many BSD-family implementations will crash hard on
996 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
999 - Authorities correctly free policies on bad servers on
1000 exit. Fixes bug 672. Bugfix on 0.2.0.x.
1003 Changes in version 0.2.0.24-rc - 2008-04-22
1004 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
1005 v3 directory authority, makes relays with dynamic IP addresses and no
1006 DirPort notice more quickly when their IP address changes, fixes a few
1007 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
1009 o New directory authorities:
1010 - Take lefkada out of the list of v3 directory authorities, since
1011 it has been down for months.
1012 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
1016 - Detect address changes more quickly on non-directory mirror
1017 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
1019 o Minor features (security):
1020 - Reject requests for reverse-dns lookup of names that are in
1021 a private address space. Patch from lodger.
1022 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
1025 o Minor bugfixes (crashes):
1026 - Avoid a rare assert that can trigger when Tor doesn't have much
1027 directory information yet and it tries to fetch a v2 hidden
1028 service descriptor. Fixes bug 651, reported by nwf.
1029 - Initialize log mutex before initializing dmalloc. Otherwise,
1030 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
1031 - Use recursive pthread mutexes in order to avoid deadlock when
1032 logging debug-level messages to a controller. Bug spotted by nwf,
1033 bugfix on 0.2.0.16-alpha.
1035 o Minor bugfixes (resource management):
1036 - Keep address policies from leaking memory: start their refcount
1037 at 1, not 2. Bugfix on 0.2.0.16-alpha.
1038 - Free authority certificates on exit, so they don't look like memory
1039 leaks. Bugfix on 0.2.0.19-alpha.
1040 - Free static hashtables for policy maps and for TLS connections on
1041 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
1042 - Avoid allocating extra space when computing consensuses on 64-bit
1043 platforms. Bug spotted by aakova.
1045 o Minor bugfixes (misc):
1046 - Do not read the configuration file when we've only been told to
1047 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
1048 based on patch from Sebastian Hahn.
1049 - Exit relays that are used as a client can now reach themselves
1050 using the .exit notation, rather than just launching an infinite
1051 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
1052 - When attempting to open a logfile fails, tell us why.
1053 - Fix a dumb bug that was preventing us from knowing that we should
1054 preemptively build circuits to handle expected directory requests.
1055 Fixes bug 660. Bugfix on 0.1.2.x.
1056 - Warn less verbosely about clock skew from netinfo cells from
1057 untrusted sources. Fixes bug 663.
1058 - Make controller stream events for DNS requests more consistent,
1059 by adding "new stream" events for DNS requests, and removing
1060 spurious "stream closed" events" for cached reverse resolves.
1061 Patch from mwenge. Fixes bug 646.
1062 - Correctly notify one-hop connections when a circuit build has
1063 failed. Possible fix for bug 669. Found by lodger.
1066 Changes in version 0.2.0.23-rc - 2008-03-24
1067 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
1068 makes bootstrapping faster if the first directory mirror you contact
1069 is down. The bundles also include the new Vidalia 0.1.2 release.
1072 - When a tunneled directory request is made to a directory server
1073 that's down, notice after 30 seconds rather than 120 seconds. Also,
1074 fail any begindir streams that are pending on it, so they can
1075 retry elsewhere. This was causing multi-minute delays on bootstrap.
1078 Changes in version 0.2.0.22-rc - 2008-03-18
1079 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
1080 enables encrypted directory connections by default for non-relays, fixes
1081 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
1082 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
1085 - Enable encrypted directory connections by default for non-relays,
1086 so censor tools that block Tor directory connections based on their
1087 plaintext patterns will no longer work. This means Tor works in
1088 certain censored countries by default again.
1091 - Make sure servers always request certificates from clients during
1092 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
1093 - Do not enter a CPU-eating loop when a connection is closed in
1094 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
1095 diagnosed by lodger; bugfix on 0.2.0.20-rc.
1096 - Fix assertion failure that could occur when a blocked circuit
1097 became unblocked, and it had pending client DNS requests. Bugfix
1098 on 0.2.0.1-alpha. Fixes bug 632.
1100 o Minor bugfixes (on 0.1.2.x):
1101 - Generate "STATUS_SERVER" events rather than misspelled
1102 "STATUS_SEVER" events. Caught by mwenge.
1103 - When counting the number of bytes written on a TLS connection,
1104 look at the BIO actually used for writing to the network, not
1105 at the BIO used (sometimes) to buffer data for the network.
1106 Looking at different BIOs could result in write counts on the
1107 order of ULONG_MAX. Fixes bug 614.
1108 - On Windows, correctly detect errors when listing the contents of
1109 a directory. Fix from lodger.
1111 o Minor bugfixes (on 0.2.0.x):
1112 - Downgrade "sslv3 alert handshake failure" message to INFO.
1113 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
1114 left BandwidthRate and BandwidthBurst at the default, we would be
1115 silently limited by those defaults. Now raise them to match the
1116 RelayBandwidth* values.
1117 - Fix the SVK version detection logic to work correctly on a branch.
1118 - Make --enable-openbsd-malloc work correctly on Linux with alpha
1119 CPUs. Fixes bug 625.
1120 - Logging functions now check that the passed severity is sane.
1121 - Use proper log levels in the testsuite call of
1122 get_interface_address6().
1123 - When using a nonstandard malloc, do not use the platform values for
1124 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
1125 - Make the openbsd malloc code use 8k pages on alpha CPUs and
1127 - Detect mismatched page sizes when using --enable-openbsd-malloc.
1128 - Avoid double-marked-for-close warning when certain kinds of invalid
1129 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
1130 for bug 617. Bugfix on 0.2.0.1-alpha.
1131 - Make sure that the "NULL-means-reject *:*" convention is followed by
1132 all the policy manipulation functions, avoiding some possible crash
1133 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
1134 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
1135 actually works, and doesn't warn about every single reverse lookup.
1136 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
1139 - Only log guard node status when guard node status has changed.
1140 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
1141 make "INFO" 75% less verbose.
1144 Changes in version 0.2.0.21-rc - 2008-03-02
1145 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
1146 makes Tor work well with Vidalia again, fixes a rare assert bug,
1147 and fixes a pair of more minor bugs. The bundles also include Vidalia
1148 0.1.0 and Torbutton 1.1.16.
1151 - The control port should declare that it requires password auth
1152 when HashedControlSessionPassword is set too. Patch from Matt Edman;
1153 bugfix on 0.2.0.20-rc. Fixes bug 615.
1154 - Downgrade assert in connection_buckets_decrement() to a log message.
1155 This may help us solve bug 614, and in any case will make its
1156 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
1157 - We were sometimes miscounting the number of bytes read from the
1158 network, causing our rate limiting to not be followed exactly.
1159 Bugfix on 0.2.0.16-alpha. Reported by lodger.
1162 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
1163 OpenSSL versions should have been working fine. Diagnosis and patch
1164 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
1165 Bugfix on 0.2.0.20-rc.
1168 Changes in version 0.2.0.20-rc - 2008-02-24
1169 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
1170 makes more progress towards normalizing Tor's TLS handshake, makes
1171 hidden services work better again, helps relays bootstrap if they don't
1172 know their IP address, adds optional support for linking in openbsd's
1173 allocator or tcmalloc, allows really fast relays to scale past 15000
1174 sockets, and fixes a bunch of minor bugs reported by Veracode.
1177 - Enable the revised TLS handshake based on the one designed by
1178 Steven Murdoch in proposal 124, as revised in proposal 130. It
1179 includes version negotiation for OR connections as described in
1180 proposal 105. The new handshake is meant to be harder for censors
1181 to fingerprint, and it adds the ability to detect certain kinds of
1182 man-in-the-middle traffic analysis attacks. The version negotiation
1183 feature will allow us to improve Tor's link protocol more safely
1185 - Choose which bridge to use proportional to its advertised bandwidth,
1186 rather than uniformly at random. This should speed up Tor for
1187 bridge users. Also do this for people who set StrictEntryNodes.
1188 - When a TrackHostExits-chosen exit fails too many times in a row,
1189 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
1192 - Resolved problems with (re-)fetching hidden service descriptors.
1193 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
1195 - If we only ever used Tor for hidden service lookups or posts, we
1196 would stop building circuits and start refusing connections after
1197 24 hours, since we falsely believed that Tor was dormant. Reported
1198 by nwf; bugfix on 0.1.2.x.
1199 - Servers that don't know their own IP address should go to the
1200 authorities for their first directory fetch, even if their DirPort
1201 is off or if they don't know they're reachable yet. This will help
1202 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
1203 - When counting the number of open sockets, count not only the number
1204 of sockets we have received from the socket() call, but also
1205 the number we've gotten from accept() and socketpair(). This bug
1206 made us fail to count all sockets that we were using for incoming
1207 connections. Bugfix on 0.2.0.x.
1208 - Fix code used to find strings within buffers, when those strings
1209 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
1210 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
1211 - Add a new __HashedControlSessionPassword option for controllers
1212 to use for one-off session password hashes that shouldn't get
1213 saved to disk by SAVECONF --- Vidalia users were accumulating a
1214 pile of HashedControlPassword lines in their torrc files, one for
1215 each time they had restarted Tor and then clicked Save. Make Tor
1216 automatically convert "HashedControlPassword" to this new option but
1217 only when it's given on the command line. Partial fix for bug 586.
1219 o Minor features (performance):
1220 - Tune parameters for cell pool allocation to minimize amount of
1222 - Add OpenBSD malloc code from phk as an optional malloc
1223 replacement on Linux: some glibc libraries do very poorly
1224 with Tor's memory allocation patterns. Pass
1225 --enable-openbsd-malloc to get the replacement malloc code.
1226 - Add a --with-tcmalloc option to the configure script to link
1227 against tcmalloc (if present). Does not yet search for
1228 non-system include paths.
1229 - Stop imposing an arbitrary maximum on the number of file descriptors
1230 used for busy servers. Bug reported by Olaf Selke; patch from
1233 o Minor features (other):
1234 - When SafeLogging is disabled, log addresses along with all TLS
1236 - When building with --enable-gcc-warnings, check for whether Apple's
1237 warning "-Wshorten-64-to-32" is available.
1238 - Add a --passphrase-fd argument to the tor-gencert command for
1241 o Minor bugfixes (memory leaks and code problems):
1242 - We were leaking a file descriptor if Tor started with a zero-length
1243 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
1244 - Detect size overflow in zlib code. Reported by Justin Ferguson and
1246 - We were comparing the raw BridgePassword entry with a base64'ed
1247 version of it, when handling a "/tor/networkstatus-bridges"
1248 directory request. Now compare correctly. Noticed by Veracode.
1249 - Recover from bad tracked-since value in MTBF-history file.
1251 - Alter the code that tries to recover from unhandled write
1252 errors, to not try to flush onto a socket that's given us
1253 unhandled errors. Bugfix on 0.1.2.x.
1254 - Make Unix controlsockets work correctly on OpenBSD. Patch from
1255 tup. Bugfix on 0.2.0.3-alpha.
1257 o Minor bugfixes (other):
1258 - If we have an extra-info document for our server, always make
1259 it available on the control port, even if we haven't gotten
1260 a copy of it from an authority yet. Patch from mwenge.
1261 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
1262 - Directory mirrors no longer include a guess at the client's IP
1263 address if the connection appears to be coming from the same /24
1264 network; it was producing too many wrong guesses.
1265 - Make the new hidden service code respect the SafeLogging setting.
1266 Bugfix on 0.2.0.x. Patch from Karsten.
1267 - When starting as an authority, do not overwrite all certificates
1268 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
1269 - If we're trying to flush the last bytes on a connection (for
1270 example, when answering a directory request), reset the
1271 time-to-give-up timeout every time we manage to write something
1272 on the socket. Bugfix on 0.1.2.x.
1273 - Change the behavior of "getinfo status/good-server-descriptor"
1274 so it doesn't return failure when any authority disappears.
1275 - Even though the man page said that "TrackHostExits ." should
1276 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
1277 - Report TLS "zero return" case as a "clean close" and "IO error"
1278 as a "close". Stop calling closes "unexpected closes": existing
1279 Tors don't use SSL_close(), so having a connection close without
1280 the TLS shutdown handshake is hardly unexpected.
1281 - Send NAMESERVER_STATUS messages for a single failed nameserver
1284 o Code simplifications and refactoring:
1285 - Remove the tor_strpartition function: its logic was confused,
1286 and it was only used for one thing that could be implemented far
1290 Changes in version 0.2.0.19-alpha - 2008-02-09
1291 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
1292 handshake, makes path selection for relays more secure and IP address
1293 guessing more robust, and generally fixes a lot of bugs in preparation
1294 for calling the 0.2.0 branch stable.
1297 - Do not include recognizeable strings in the commonname part of
1298 Tor's x509 certificates.
1301 - If we're a relay, avoid picking ourselves as an introduction point,
1302 a rendezvous point, or as the final hop for internal circuits. Bug
1303 reported by taranis and lodger. Bugfix on 0.1.2.x.
1304 - Patch from "Andrew S. Lists" to catch when we contact a directory
1305 mirror at IP address X and he says we look like we're coming from
1306 IP address X. Bugfix on 0.1.2.x.
1308 o Minor features (security):
1309 - Be more paranoid about overwriting sensitive memory on free(),
1310 as a defensive programming tactic to ensure forward secrecy.
1312 o Minor features (directory authority):
1313 - Actually validate the options passed to AuthDirReject,
1314 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
1315 - Reject router descriptors with out-of-range bandwidthcapacity or
1316 bandwidthburst values.
1318 o Minor features (controller):
1319 - Reject controller commands over 1MB in length. This keeps rogue
1320 processes from running us out of memory.
1322 o Minor features (misc):
1323 - Give more descriptive well-formedness errors for out-of-range
1324 hidden service descriptor/protocol versions.
1325 - Make memory debugging information describe more about history
1326 of cell allocation, so we can help reduce our memory use.
1328 o Deprecated features (controller):
1329 - The status/version/num-versioning and status/version/num-concurring
1330 GETINFO options are no longer useful in the v3 directory protocol:
1331 treat them as deprecated, and warn when they're used.
1334 - When our consensus networkstatus has been expired for a while, stop
1335 being willing to build circuits using it. Fixes bug 401. Bugfix
1337 - Directory caches now fetch certificates from all authorities
1338 listed in a networkstatus consensus, even when they do not
1339 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
1340 - When connecting to a bridge without specifying its key, insert
1341 the connection into the identity-to-connection map as soon as
1342 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
1343 - Detect versions of OS X where malloc_good_size() is present in the
1344 library but never actually declared. Resolves bug 587. Bugfix
1346 - Stop incorrectly truncating zlib responses to directory authority
1347 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
1348 - Stop recommending that every server operator send mail to tor-ops.
1349 Resolves bug 597. Bugfix on 0.1.2.x.
1350 - Don't trigger an assert if we start a directory authority with a
1351 private IP address (like 127.0.0.1).
1352 - Avoid possible failures when generating a directory with routers
1353 with over-long versions strings, or too many flags set. Bugfix
1355 - If an attempt to launch a DNS resolve request over the control
1356 port fails because we have overrun the limit on the number of
1357 connections, tell the controller that the request has failed.
1358 - Avoid using too little bandwidth when our clock skips a few
1359 seconds. Bugfix on 0.1.2.x.
1360 - Fix shell error when warning about missing packages in configure
1361 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
1362 - Do not become confused when receiving a spurious VERSIONS-like
1363 cell from a confused v1 client. Bugfix on 0.2.0.x.
1364 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
1365 introduction points for a hidden service have failed. Patch from
1366 Karsten Loesing. Bugfix on 0.2.0.x.
1368 o Code simplifications and refactoring:
1369 - Remove some needless generality from cpuworker code, for improved
1371 - Stop overloading the circuit_t.onionskin field for both "onionskin
1372 from a CREATE cell that we are waiting for a cpuworker to be
1373 assigned" and "onionskin from an EXTEND cell that we are going to
1374 send to an OR as soon as we are connected". Might help with bug 600.
1375 - Add an in-place version of aes_crypt() so that we can avoid doing a
1376 needless memcpy() call on each cell payload.
1379 Changes in version 0.2.0.18-alpha - 2008-01-25
1380 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
1381 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
1382 that can warn or reject connections to ports generally associated with
1383 vulnerable-plaintext protocols.
1385 o New directory authorities:
1386 - Set up dannenberg (run by CCC) as the sixth v3 directory
1390 - Fix a major memory leak when attempting to use the v2 TLS
1391 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
1392 - We accidentally enabled the under-development v2 TLS handshake
1393 code, which was causing log entries like "TLS error while
1394 renegotiating handshake". Disable it again. Resolves bug 590.
1395 - We were computing the wrong Content-Length: header for directory
1396 responses that need to be compressed on the fly, causing clients
1397 asking for those items to always fail. Bugfix on 0.2.0.x; partially
1401 - Avoid going directly to the directory authorities even if you're a
1402 relay, if you haven't found yourself reachable yet or if you've
1403 decided not to advertise your dirport yet. Addresses bug 556.
1404 - If we've gone 12 hours since our last bandwidth check, and we
1405 estimate we have less than 50KB bandwidth capacity but we could
1406 handle more, do another bandwidth test.
1407 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
1408 Tor can warn and/or refuse connections to ports commonly used with
1409 vulnerable-plaintext protocols. Currently we warn on ports 23,
1410 109, 110, and 143, but we don't reject any.
1413 - When we setconf ClientOnly to 1, close any current OR and Dir
1414 listeners. Reported by mwenge.
1415 - When we get a consensus that's been signed by more people than
1416 we expect, don't log about it; it's not a big deal. Reported
1420 - Don't answer "/tor/networkstatus-bridges" directory requests if
1421 the request isn't encrypted.
1422 - Make "ClientOnly 1" config option disable directory ports too.
1423 - Patches from Karsten Loesing to make v2 hidden services more
1424 robust: work even when there aren't enough HSDir relays available;
1425 retry when a v2 rend desc fetch fails; but don't retry if we
1426 already have a usable v0 rend desc.
1429 Changes in version 0.2.0.17-alpha - 2008-01-17
1430 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
1433 - Make the tor-gencert man page get included correctly in the tarball.
1436 Changes in version 0.2.0.16-alpha - 2008-01-17
1437 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
1438 Loesing, and generally cleans up a lot of features and minor bugs.
1440 o New directory authorities:
1441 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
1444 o Major performance improvements:
1445 - Switch our old ring buffer implementation for one more like that
1446 used by free Unix kernels. The wasted space in a buffer with 1mb
1447 of data will now be more like 8k than 1mb. The new implementation
1448 also avoids realloc();realloc(); patterns that can contribute to
1449 memory fragmentation.
1452 - Configuration files now accept C-style strings as values. This
1453 helps encode characters not allowed in the current configuration
1454 file format, such as newline or #. Addresses bug 557.
1455 - Although we fixed bug 539 (where servers would send HTTP status 503
1456 responses _and_ send a body too), there are still servers out
1457 there that haven't upgraded. Therefore, make clients parse such
1458 bodies when they receive them.
1459 - When we're not serving v2 directory information, there is no reason
1460 to actually keep any around. Remove the obsolete files and directory
1461 on startup if they are very old and we aren't going to serve them.
1463 o Minor performance improvements:
1464 - Reference-count and share copies of address policy entries; only 5%
1465 of them were actually distinct.
1466 - Never walk through the list of logs if we know that no log is
1467 interested in a given message.
1470 - When an authority has not signed a consensus, do not try to
1471 download a nonexistent "certificate with key 00000000". Bugfix
1472 on 0.2.0.x. Fixes bug 569.
1473 - Fix a rare assert error when we're closing one of our threads:
1474 use a mutex to protect the list of logs, so we never write to the
1475 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
1476 bug 575, which is kind of the revenge of bug 222.
1477 - Patch from Karsten Loesing to complain less at both the client
1478 and the relay when a relay used to have the HSDir flag but doesn't
1479 anymore, and we try to upload a hidden service descriptor.
1480 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
1482 - Do not try to download missing certificates until we have tried
1483 to check our fallback consensus. Fixes bug 583.
1484 - Make bridges round reported GeoIP stats info up to the nearest
1485 estimate, not down. Now we can distinguish between "0 people from
1486 this country" and "1 person from this country".
1487 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
1488 - Avoid possible segfault if key generation fails in
1489 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
1490 - Avoid segfault in the case where a badly behaved v2 versioning
1491 directory sends a signed networkstatus with missing client-versions.
1493 - Avoid segfaults on certain complex invocations of
1494 router_get_by_hexdigest(). Bugfix on 0.1.2.
1495 - Correct bad index on array access in parse_http_time(). Bugfix
1497 - Fix possible bug in vote generation when server versions are present
1498 but client versions are not.
1499 - Fix rare bug on REDIRECTSTREAM control command when called with no
1500 port set: it could erroneously report an error when none had
1502 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
1503 compressing large objects and find ourselves with more than 4k
1504 left over. Bugfix on 0.2.0.
1505 - Fix a small memory leak when setting up a hidden service.
1506 - Fix a few memory leaks that could in theory happen under bizarre
1508 - Fix an assert if we post a general-purpose descriptor via the
1509 control port but that descriptor isn't mentioned in our current
1510 network consensus. Bug reported by Jon McLachlan; bugfix on
1513 o Minor features (controller):
1514 - Get NS events working again. Patch from tup.
1515 - The GETCONF command now escapes and quotes configuration values
1516 that don't otherwise fit into the torrc file.
1517 - The SETCONF command now handles quoted values correctly.
1519 o Minor features (directory authorities):
1520 - New configuration options to override default maximum number of
1521 servers allowed on a single IP address. This is important for
1522 running a test network on a single host.
1523 - Actually implement the -s option to tor-gencert.
1524 - Add a manual page for tor-gencert.
1526 o Minor features (bridges):
1527 - Bridge authorities no longer serve bridge descriptors over
1528 unencrypted connections.
1530 o Minor features (other):
1531 - Add hidden services and DNSPorts to the list of things that make
1532 Tor accept that it has running ports. Change starting Tor with no
1533 ports from a fatal error to a warning; we might change it back if
1534 this turns out to confuse anybody. Fixes bug 579.
1537 Changes in version 0.1.2.19 - 2008-01-17
1538 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
1539 exit policy a little bit more conservative so it's safer to run an
1540 exit relay on a home system, and fixes a variety of smaller issues.
1543 - Exit policies now reject connections that are addressed to a
1544 relay's public (external) IP address too, unless
1545 ExitPolicyRejectPrivate is turned off. We do this because too
1546 many relays are running nearby to services that trust them based
1550 - When the clock jumps forward a lot, do not allow the bandwidth
1551 buckets to become negative. Fixes bug 544.
1552 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
1553 on every successful resolve. Reported by Mike Perry.
1554 - Purge old entries from the "rephist" database and the hidden
1555 service descriptor database even when DirPort is zero.
1556 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
1557 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
1558 crashing or mis-answering these requests.
1559 - When we decide to send a 503 response to a request for servers, do
1560 not then also send the server descriptors: this defeats the whole
1561 purpose. Fixes bug 539.
1564 - Changing the ExitPolicyRejectPrivate setting should cause us to
1565 rebuild our server descriptor.
1566 - Fix handling of hex nicknames when answering controller requests for
1567 networkstatus by name, or when deciding whether to warn about
1568 unknown routers in a config option. (Patch from mwenge.)
1569 - Fix a couple of hard-to-trigger autoconf problems that could result
1570 in really weird results on platforms whose sys/types.h files define
1571 nonstandard integer types.
1572 - Don't try to create the datadir when running --verify-config or
1573 --hash-password. Resolves bug 540.
1574 - If we were having problems getting a particular descriptor from the
1575 directory caches, and then we learned about a new descriptor for
1576 that router, we weren't resetting our failure count. Reported
1578 - Although we fixed bug 539 (where servers would send HTTP status 503
1579 responses _and_ send a body too), there are still servers out there
1580 that haven't upgraded. Therefore, make clients parse such bodies
1581 when they receive them.
1582 - Run correctly on systems where rlim_t is larger than unsigned long.
1583 This includes some 64-bit systems.
1584 - Run correctly on platforms (like some versions of OS X 10.5) where
1585 the real limit for number of open files is OPEN_FILES, not rlim_max
1586 from getrlimit(RLIMIT_NOFILES).
1587 - Avoid a spurious free on base64 failure.
1588 - Avoid segfaults on certain complex invocations of
1589 router_get_by_hexdigest().
1590 - Fix rare bug on REDIRECTSTREAM control command when called with no
1591 port set: it could erroneously report an error when none had
1595 Changes in version 0.2.0.15-alpha - 2007-12-25
1596 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
1597 features added in 0.2.0.13-alpha.
1600 - Fix several remotely triggerable asserts based on DirPort requests
1601 for a v2 or v3 networkstatus object before we were prepared. This
1602 was particularly bad for 0.2.0.13 and later bridge relays, who
1603 would never have a v2 networkstatus and would thus always crash
1604 when used. Bugfixes on 0.2.0.x.
1605 - Estimate the v3 networkstatus size more accurately, rather than
1606 estimating it at zero bytes and giving it artificially high priority
1607 compared to other directory requests. Bugfix on 0.2.0.x.
1610 - Fix configure.in logic for cross-compilation.
1611 - When we load a bridge descriptor from the cache, and it was
1612 previously unreachable, mark it as retriable so we won't just
1613 ignore it. Also, try fetching a new copy immediately. Bugfixes
1615 - The bridge GeoIP stats were counting other relays, for example
1616 self-reachability and authority-reachability tests.
1619 - Support compilation to target iPhone; patch from cjacker huang.
1620 To build for iPhone, pass the --enable-iphone option to configure.
1623 Changes in version 0.2.0.14-alpha - 2007-12-23
1625 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
1626 without a datadirectory from a previous Tor install. Reported
1628 - Fix a crash when we fetch a descriptor that turns out to be
1629 unexpected (it used to be in our networkstatus when we started
1630 fetching it, but it isn't in our current networkstatus), and we
1631 aren't using bridges. Bugfix on 0.2.0.x.
1632 - Fix a crash when accessing hidden services: it would work the first
1633 time you use a given introduction point for your service, but
1634 on subsequent requests we'd be using garbage memory. Fixed by
1635 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
1636 - Fix a crash when we load a bridge descriptor from disk but we don't
1637 currently have a Bridge line for it in our torrc. Bugfix on
1641 - If bridge authorities set BridgePassword, they will serve a
1642 snapshot of known bridge routerstatuses from their DirPort to
1643 anybody who knows that password. Unset by default.
1646 - Make the unit tests build again.
1647 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
1648 - Make PublishServerDescriptor default to 1, so the default doesn't
1649 have to change as we invent new directory protocol versions.
1650 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
1651 be included unless sys/time.h is already included. Fixes
1652 bug 553. Bugfix on 0.2.0.x.
1653 - If we receive a general-purpose descriptor and then receive an
1654 identical bridge-purpose descriptor soon after, don't discard
1655 the next one as a duplicate.
1658 - If BridgeRelay is set to 1, then the default for
1659 PublishServerDescriptor is now "bridge" rather than "v2,v3".
1660 - If the user sets RelayBandwidthRate but doesn't set
1661 RelayBandwidthBurst, then make them equal rather than erroring out.
1664 Changes in version 0.2.0.13-alpha - 2007-12-21
1665 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
1666 Goodell, fixes many more bugs, and adds a lot of infrastructure for
1669 o New directory authorities:
1670 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
1674 - Only update guard status (usable / not usable) once we have
1675 enough directory information. This was causing us to always pick
1676 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
1677 causing us to discard all our guards on startup if we hadn't been
1678 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
1679 - Purge old entries from the "rephist" database and the hidden
1680 service descriptor databases even when DirPort is zero. Bugfix
1682 - We were ignoring our RelayBandwidthRate for the first 30 seconds
1683 after opening a circuit -- even a relayed circuit. Bugfix on
1685 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
1686 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
1687 crashing or mis-answering these types of requests.
1688 - Relays were publishing their server descriptor to v1 and v2
1689 directory authorities, but they didn't try publishing to v3-only
1690 authorities. Fix this; and also stop publishing to v1 authorities.
1692 - When we were reading router descriptors from cache, we were ignoring
1693 the annotations -- so for example we were reading in bridge-purpose
1694 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
1695 - When we decided to send a 503 response to a request for servers, we
1696 were then also sending the server descriptors: this defeats the
1697 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
1700 - Bridge relays now behave like clients with respect to time
1701 intervals for downloading new consensus documents -- otherwise they
1702 stand out. Bridge users now wait until the end of the interval,
1703 so their bridge relay will be sure to have a new consensus document.
1704 - Three new config options (AlternateDirAuthority,
1705 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
1706 user selectively replace the default directory authorities by type,
1707 rather than the all-or-nothing replacement that DirServer offers.
1708 - Tor can now be configured to read a GeoIP file from disk in one
1709 of two formats. This can be used by controllers to map IP addresses
1710 to countries. Eventually, it may support exit-by-country.
1711 - When possible, bridge relays remember which countries users
1712 are coming from, and report aggregate information in their
1713 extra-info documents, so that the bridge authorities can learn
1714 where Tor is blocked.
1715 - Bridge directory authorities now do reachability testing on the
1716 bridges they know. They provide router status summaries to the
1717 controller via "getinfo ns/purpose/bridge", and also dump summaries
1718 to a file periodically.
1719 - Stop fetching directory info so aggressively if your DirPort is
1720 on but your ORPort is off; stop fetching v2 dir info entirely.
1721 You can override these choices with the new FetchDirInfoEarly
1725 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
1726 consensus documents when there are too many relays at a single
1727 IP address. Now clear it in v2 network status documents too, and
1728 also clear it in routerinfo_t when the relay is no longer listed
1729 in the relevant networkstatus document.
1730 - Don't crash if we get an unexpected value for the
1731 PublishServerDescriptor config option. Reported by Matt Edman;
1732 bugfix on 0.2.0.9-alpha.
1733 - Our new v2 hidden service descriptor format allows descriptors
1734 that have no introduction points. But Tor crashed when we tried
1735 to build a descriptor with no intro points (and it would have
1736 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
1738 - Fix building with dmalloc 5.5.2 with glibc.
1739 - Reject uploaded descriptors and extrainfo documents if they're
1740 huge. Otherwise we'll cache them all over the network and it'll
1741 clog everything up. Reported by Aljosha Judmayer.
1742 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
1743 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
1744 - When the DANGEROUS_VERSION controller status event told us we're
1745 running an obsolete version, it used the string "OLD" to describe
1746 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
1747 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
1748 - If we can't expand our list of entry guards (e.g. because we're
1749 using bridges or we have StrictEntryNodes set), don't mark relays
1750 down when they fail a directory request. Otherwise we're too quick
1751 to mark all our entry points down. Bugfix on 0.1.2.x.
1752 - Fix handling of hex nicknames when answering controller requests for
1753 networkstatus by name, or when deciding whether to warn about unknown
1754 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
1755 - Fix a couple of hard-to-trigger autoconf problems that could result
1756 in really weird results on platforms whose sys/types.h files define
1757 nonstandard integer types. Bugfix on 0.1.2.x.
1758 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
1759 - Don't crash on name lookup when we have no current consensus. Fixes
1760 bug 538; bugfix on 0.2.0.x.
1761 - Only Tors that want to mirror the v2 directory info should
1762 create the "cached-status" directory in their datadir. (All Tors
1763 used to create it.) Bugfix on 0.2.0.9-alpha.
1764 - Directory authorities should only automatically download Extra Info
1765 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
1768 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
1769 consumers. (We already do this on HUP.)
1770 - Authorities and caches fetch the v2 networkstatus documents
1771 less often, now that v3 is encouraged.
1772 - Add a new config option BridgeRelay that specifies you want to
1773 be a bridge relay. Right now the only difference is that it makes
1774 you answer begin_dir requests, and it makes you cache dir info,
1775 even if your DirPort isn't on.
1776 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
1777 ask about source, timestamp of arrival, purpose, etc. We need
1778 something like this to help Vidalia not do GeoIP lookups on bridge
1780 - Allow multiple HashedControlPassword config lines, to support
1781 multiple controller passwords.
1782 - Authorities now decide whether they're authoritative for a given
1783 router based on the router's purpose.
1784 - New config options AuthDirBadDir and AuthDirListBadDirs for
1785 authorities to mark certain relays as "bad directories" in the
1786 networkstatus documents. Also supports the "!baddir" directive in
1787 the approved-routers file.
1790 Changes in version 0.2.0.12-alpha - 2007-11-16
1791 This twelfth development snapshot fixes some more build problems as
1792 well as a few minor bugs.
1795 - Make it build on OpenBSD again. Patch from tup.
1796 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
1797 package-building for Red Hat, OS X, etc.
1799 o Minor bugfixes (on 0.1.2.x):
1800 - Changing the ExitPolicyRejectPrivate setting should cause us to
1801 rebuild our server descriptor.
1803 o Minor bugfixes (on 0.2.0.x):
1804 - When we're lacking a consensus, don't try to perform rendezvous
1805 operations. Reported by Karsten Loesing.
1806 - Fix a small memory leak whenever we decide against using a
1807 newly picked entry guard. Reported by Mike Perry.
1808 - When authorities detected more than two relays running on the same
1809 IP address, they were clearing all the status flags but forgetting
1810 to clear the "hsdir" flag. So clients were being told that a
1811 given relay was the right choice for a v2 hsdir lookup, yet they
1812 never had its descriptor because it was marked as 'not running'
1814 - If we're trying to fetch a bridge descriptor and there's no way
1815 the bridge authority could help us (for example, we don't know
1816 a digest, or there is no bridge authority), don't be so eager to
1817 fall back to asking the bridge authority.
1818 - If we're using bridges or have strictentrynodes set, and our
1819 chosen exit is in the same family as all our bridges/entry guards,
1820 then be flexible about families.
1823 - When we negotiate a v2 link-layer connection (not yet implemented),
1824 accept RELAY_EARLY cells and turn them into RELAY cells if we've
1825 negotiated a v1 connection for their next step. Initial code for
1829 Changes in version 0.2.0.11-alpha - 2007-11-12
1830 This eleventh development snapshot fixes some build problems with
1831 the previous snapshot. It also includes a more secure-by-default exit
1832 policy for relays, fixes an enormous memory leak for exit relays, and
1833 fixes another bug where servers were falling out of the directory list.
1836 - Exit policies now reject connections that are addressed to a
1837 relay's public (external) IP address too, unless
1838 ExitPolicyRejectPrivate is turned off. We do this because too
1839 many relays are running nearby to services that trust them based
1840 on network address. Bugfix on 0.1.2.x.
1843 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
1844 on every successful resolve. Reported by Mike Perry; bugfix
1846 - On authorities, never downgrade to old router descriptors simply
1847 because they're listed in the consensus. This created a catch-22
1848 where we wouldn't list a new descriptor because there was an
1849 old one in the consensus, and we couldn't get the new one in the
1850 consensus because we wouldn't list it. Possible fix for bug 548.
1851 Also, this might cause bug 543 to appear on authorities; if so,
1852 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
1854 o Packaging fixes on 0.2.0.10-alpha:
1855 - We were including instructions about what to do with the
1856 src/config/fallback-consensus file, but we weren't actually
1857 including it in the tarball. Disable all of that for now.
1860 - Allow people to say PreferTunnelledDirConns rather than
1861 PreferTunneledDirConns, for those alternate-spellers out there.
1864 - Don't reevaluate all the information from our consensus document
1865 just because we've downloaded a v2 networkstatus that we intend
1866 to cache. Fixes bug 545; bugfix on 0.2.0.x.
1869 Changes in version 0.2.0.10-alpha - 2007-11-10
1870 This tenth development snapshot adds a third v3 directory authority
1871 run by Mike Perry, adds most of Karsten Loesing's new hidden service
1872 descriptor format, fixes a bad crash bug and new bridge bugs introduced
1873 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
1874 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
1875 addresses many more minor issues.
1877 o New directory authorities:
1878 - Set up ides (run by Mike Perry) as the third v3 directory authority.
1881 - Allow tunnelled directory connections to ask for an encrypted
1882 "begin_dir" connection or an anonymized "uses a full Tor circuit"
1883 connection independently. Now we can make anonymized begin_dir
1884 connections for (e.g.) more secure hidden service posting and
1886 - More progress on proposal 114: code from Karsten Loesing to
1887 implement new hidden service descriptor format.
1888 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
1889 accommodate the growing number of servers that use the default
1890 and are reaching it.
1891 - Directory authorities use a new formula for selecting which nodes
1892 to advertise as Guards: they must be in the top 7/8 in terms of
1893 how long we have known about them, and above the median of those
1894 nodes in terms of weighted fractional uptime.
1895 - Make "not enough dir info yet" warnings describe *why* Tor feels
1896 it doesn't have enough directory info yet.
1899 - Stop servers from crashing if they set a Family option (or
1900 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
1902 - Make bridge users work again -- the move to v3 directories in
1903 0.2.0.9-alpha had introduced a number of bugs that made bridges
1904 no longer work for clients.
1905 - When the clock jumps forward a lot, do not allow the bandwidth
1906 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
1908 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
1909 - When the consensus lists a router descriptor that we previously were
1910 mirroring, but that we considered non-canonical, reload the
1911 descriptor as canonical. This fixes bug 543 where Tor servers
1912 would start complaining after a few days that they don't have
1913 enough directory information to build a circuit.
1914 - Consider replacing the current consensus when certificates arrive
1915 that make the pending consensus valid. Previously, we were only
1916 considering replacement when the new certs _didn't_ help.
1917 - Fix an assert error on startup if we didn't already have the
1918 consensus and certs cached in our datadirectory: we were caching
1919 the consensus in consensus_waiting_for_certs but then free'ing it
1921 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
1922 Request) if we need more v3 certs but we've already got pending
1923 requests for all of them.
1924 - Correctly back off from failing certificate downloads. Fixes
1926 - Authorities don't vote on the Running flag if they have been running
1927 for less than 30 minutes themselves. Fixes bug 547, where a newly
1928 started authority would vote that everyone was down.
1931 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
1932 it, it had no AES, and it hasn't seen any security patches since
1936 - Clients now hold circuitless TLS connections open for 1.5 times
1937 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
1938 rebuild a new circuit over them within that timeframe. Previously,
1939 they held them open only for KeepalivePeriod (5 minutes).
1940 - Use "If-Modified-Since" to avoid retrieving consensus
1941 networkstatuses that we already have.
1942 - When we have no consensus, check FallbackNetworkstatusFile (defaults
1943 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
1944 we start knowing some directory caches.
1945 - When we receive a consensus from the future, warn about skew.
1946 - Improve skew reporting: try to give the user a better log message
1947 about how skewed they are, and how much this matters.
1948 - When we have a certificate for an authority, believe that
1949 certificate's claims about the authority's IP address.
1950 - New --quiet command-line option to suppress the default console log.
1951 Good in combination with --hash-password.
1952 - Authorities send back an X-Descriptor-Not-New header in response to
1953 an accepted-but-discarded descriptor upload. Partially implements
1955 - Make the log message for "tls error. breaking." more useful.
1956 - Better log messages about certificate downloads, to attempt to
1957 track down the second incarnation of bug 546.
1959 o Minor features (bridges):
1960 - If bridge users set UpdateBridgesFromAuthority, but the digest
1961 they ask for is a 404 from the bridge authority, they now fall
1962 back to trying the bridge directly.
1963 - Bridges now use begin_dir to publish their server descriptor to
1964 the bridge authority, even when they haven't set TunnelDirConns.
1966 o Minor features (controller):
1967 - When reporting clock skew, and we know that the clock is _at least
1968 as skewed_ as some value, but we don't know the actual value,
1969 report the value as a "minimum skew."
1972 - Update linux-tor-prio.sh script to allow QoS based on the uid of
1973 the Tor process. Patch from Marco Bonetti with tweaks from Mike
1977 - Refuse to start if both ORPort and UseBridges are set. Bugfix
1978 on 0.2.0.x, suggested by Matt Edman.
1979 - Don't stop fetching descriptors when FetchUselessDescriptors is
1980 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
1981 reported by tup and ioerror.
1982 - Better log message on vote from unknown authority.
1983 - Don't log "Launching 0 request for 0 router" message.
1985 o Minor bugfixes (memory leaks):
1986 - Stop leaking memory every time we parse a v3 certificate. Bugfix
1988 - Stop leaking memory every time we load a v3 certificate. Bugfix
1989 on 0.2.0.1-alpha. Fixes bug 536.
1990 - Stop leaking a cached networkstatus on exit. Bugfix on
1992 - Stop leaking voter information every time we free a consensus.
1993 Bugfix on 0.2.0.3-alpha.
1994 - Stop leaking signed data every time we check a voter signature.
1995 Bugfix on 0.2.0.3-alpha.
1996 - Stop leaking a signature every time we fail to parse a consensus or
1997 a vote. Bugfix on 0.2.0.3-alpha.
1998 - Stop leaking v2_download_status_map on shutdown. Bugfix on
2000 - Stop leaking conn->nickname every time we make a connection to a
2001 Tor relay without knowing its expected identity digest (e.g. when
2002 using bridges). Bugfix on 0.2.0.3-alpha.
2004 - Minor bugfixes (portability):
2005 - Run correctly on platforms where rlim_t is larger than unsigned
2006 long, and/or where the real limit for number of open files is
2007 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
2008 particular, these may be needed for OS X 10.5.
2011 Changes in version 0.1.2.18 - 2007-10-28
2012 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
2013 hidden service introduction that were causing huge delays, and a big
2014 bug that was causing some servers to disappear from the network status
2015 lists for a few hours each day.
2017 o Major bugfixes (crashes):
2018 - If a connection is shut down abruptly because of something that
2019 happened inside connection_flushed_some(), do not call
2020 connection_finished_flushing(). Should fix bug 451:
2021 "connection_stop_writing: Assertion conn->write_event failed"
2022 Bugfix on 0.1.2.7-alpha.
2023 - Fix possible segfaults in functions called from
2024 rend_process_relay_cell().
2026 o Major bugfixes (hidden services):
2027 - Hidden services were choosing introduction points uniquely by
2028 hexdigest, but when constructing the hidden service descriptor
2029 they merely wrote the (potentially ambiguous) nickname.
2030 - Clients now use the v2 intro format for hidden service
2031 connections: they specify their chosen rendezvous point by identity
2032 digest rather than by (potentially ambiguous) nickname. These
2033 changes could speed up hidden service connections dramatically.
2035 o Major bugfixes (other):
2036 - Stop publishing a new server descriptor just because we get a
2037 HUP signal. This led (in a roundabout way) to some servers getting
2038 dropped from the networkstatus lists for a few hours each day.
2039 - When looking for a circuit to cannibalize, consider family as well
2040 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
2041 circuit cannibalization).
2042 - When a router wasn't listed in a new networkstatus, we were leaving
2043 the flags for that router alone -- meaning it remained Named,
2044 Running, etc -- even though absence from the networkstatus means
2045 that it shouldn't be considered to exist at all anymore. Now we
2046 clear all the flags for routers that fall out of the networkstatus
2047 consensus. Fixes bug 529.
2050 - Don't try to access (or alter) the state file when running
2051 --list-fingerprint or --verify-config or --hash-password. Resolves
2053 - When generating information telling us how to extend to a given
2054 router, do not try to include the nickname if it is
2055 absent. Resolves bug 467.
2056 - Fix a user-triggerable segfault in expand_filename(). (There isn't
2057 a way to trigger this remotely.)
2058 - When sending a status event to the controller telling it that an
2059 OR address is reachable, set the port correctly. (Previously we
2060 were reporting the dir port.)
2061 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
2062 command. Bugfix on 0.1.2.17.
2063 - When loading bandwidth history, do not believe any information in
2064 the future. Fixes bug 434.
2065 - When loading entry guard information, do not believe any information
2067 - When we have our clock set far in the future and generate an
2068 onion key, then re-set our clock to be correct, we should not stop
2069 the onion key from getting rotated.
2070 - On some platforms, accept() can return a broken address. Detect
2071 this more quietly, and deal accordingly. Fixes bug 483.
2072 - It's not actually an error to find a non-pending entry in the DNS
2073 cache when canceling a pending resolve. Don't log unless stuff
2074 is fishy. Resolves bug 463.
2075 - Don't reset trusted dir server list when we set a configuration
2076 option. Patch from Robert Hogan.
2077 - Don't try to create the datadir when running --verify-config or
2078 --hash-password. Resolves bug 540.
2081 Changes in version 0.2.0.9-alpha - 2007-10-24
2082 This ninth development snapshot switches clients to the new v3 directory
2083 system; allows servers to be listed in the network status even when they
2084 have the same nickname as a registered server; and fixes many other
2085 bugs including a big one that was causing some servers to disappear
2086 from the network status lists for a few hours each day.
2088 o Major features (directory system):
2089 - Clients now download v3 consensus networkstatus documents instead
2090 of v2 networkstatus documents. Clients and caches now base their
2091 opinions about routers on these consensus documents. Clients only
2092 download router descriptors listed in the consensus.
2093 - Authorities now list servers who have the same nickname as
2094 a different named server, but list them with a new flag,
2095 "Unnamed". Now we can list servers that happen to pick the same
2096 nickname as a server that registered two years ago and then
2097 disappeared. Partially implements proposal 122.
2098 - If the consensus lists a router as "Unnamed", the name is assigned
2099 to a different router: do not identify the router by that name.
2100 Partially implements proposal 122.
2101 - Authorities can now come to a consensus on which method to use to
2102 compute the consensus. This gives us forward compatibility.
2105 - Stop publishing a new server descriptor just because we HUP or
2106 when we find our DirPort to be reachable but won't actually publish
2107 it. New descriptors without any real changes are dropped by the
2108 authorities, and can screw up our "publish every 18 hours" schedule.
2110 - When a router wasn't listed in a new networkstatus, we were leaving
2111 the flags for that router alone -- meaning it remained Named,
2112 Running, etc -- even though absence from the networkstatus means
2113 that it shouldn't be considered to exist at all anymore. Now we
2114 clear all the flags for routers that fall out of the networkstatus
2115 consensus. Fixes bug 529; bugfix on 0.1.2.x.
2116 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
2117 extrainfo documents and then discard them immediately for not
2118 matching the latest router. Bugfix on 0.2.0.1-alpha.
2120 o Minor features (v3 directory protocol):
2121 - Allow tor-gencert to generate a new certificate without replacing
2123 - Allow certificates to include an address.
2124 - When we change our directory-cache settings, reschedule all voting
2125 and download operations.
2126 - Reattempt certificate downloads immediately on failure, as long as
2127 we haven't failed a threshold number of times yet.
2128 - Delay retrying consensus downloads while we're downloading
2129 certificates to verify the one we just got. Also, count getting a
2130 consensus that we already have (or one that isn't valid) as a failure,
2131 and count failing to get the certificates after 20 minutes as a
2133 - Build circuits and download descriptors even if our consensus is a
2134 little expired. (This feature will go away once authorities are
2137 o Minor features (router descriptor cache):
2138 - If we find a cached-routers file that's been sitting around for more
2139 than 28 days unmodified, then most likely it's a leftover from
2140 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
2142 - When we (as a cache) download a descriptor because it was listed
2143 in a consensus, remember when the consensus was supposed to expire,
2144 and don't expire the descriptor until then.
2146 o Minor features (performance):
2147 - Call routerlist_remove_old_routers() much less often. This should
2148 speed startup, especially on directory caches.
2149 - Don't try to launch new descriptor downloads quite so often when we
2150 already have enough directory information to build circuits.
2151 - Base64 decoding was actually showing up on our profile when parsing
2152 the initial descriptor file; switch to an in-process all-at-once
2153 implementation that's about 3.5x times faster than calling out to
2156 o Minor features (compilation):
2157 - Detect non-ASCII platforms (if any still exist) and refuse to
2158 build there: some of our code assumes that 'A' is 65 and so on.
2160 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
2161 - Make the "next period" votes into "current period" votes immediately
2162 after publishing the consensus; avoid a heisenbug that made them
2163 stick around indefinitely.
2164 - When we discard a vote as a duplicate, do not report this as
2166 - Treat missing v3 keys or certificates as an error when running as a
2167 v3 directory authority.
2168 - When we're configured to be a v3 authority, but we're only listed
2169 as a non-v3 authority in our DirServer line for ourself, correct
2171 - If an authority doesn't have a qualified hostname, just put
2172 its address in the vote. This fixes the problem where we referred to
2173 "moria on moria:9031."
2174 - Distinguish between detached signatures for the wrong period, and
2175 detached signatures for a divergent vote.
2176 - Fix a small memory leak when computing a consensus.
2177 - When there's no concensus, we were forming a vote every 30
2178 minutes, but writing the "valid-after" line in our vote based
2179 on our configured V3AuthVotingInterval: so unless the intervals
2180 matched up, we immediately rejected our own vote because it didn't
2181 start at the voting interval that caused us to construct a vote.
2183 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
2184 - Delete unverified-consensus when the real consensus is set.
2185 - Consider retrying a consensus networkstatus fetch immediately
2186 after one fails: don't wait 60 seconds to notice.
2187 - When fetching a consensus as a cache, wait until a newer consensus
2188 should exist before trying to replace the current one.
2189 - Use a more forgiving schedule for retrying failed consensus
2190 downloads than for other types.
2192 o Minor bugfixes (other directory issues):
2193 - Correct the implementation of "download votes by digest." Bugfix on
2195 - Authorities no longer send back "400 you're unreachable please fix
2196 it" errors to Tor servers that aren't online all the time. We're
2197 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
2199 o Minor bugfixes (controller):
2200 - Don't reset trusted dir server list when we set a configuration
2201 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
2202 - Respond to INT and TERM SIGNAL commands before we execute the
2203 signal, in case the signal shuts us down. We had a patch in
2204 0.1.2.1-alpha that tried to do this by queueing the response on
2205 the connection's buffer before shutting down, but that really
2206 isn't the same thing at all. Bug located by Matt Edman.
2208 o Minor bugfixes (misc):
2209 - Correctly check for bad options to the "PublishServerDescriptor"
2210 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
2211 - Stop leaking memory on failing case of base32_decode, and make
2212 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
2213 - Don't try to download extrainfo documents when we're trying to
2214 fetch enough directory info to build a circuit: having enough
2215 info should get priority. Bugfix on 0.2.0.x.
2216 - Don't complain that "your server has not managed to confirm that its
2217 ports are reachable" if we haven't been able to build any circuits
2218 yet. Bug found by spending four hours without a v3 consensus. Bugfix
2220 - Detect the reason for failing to mmap a descriptor file we just
2221 wrote, and give a more useful log message. Fixes bug 533. Bugfix
2224 o Code simplifications and refactoring:
2225 - Remove support for the old bw_accounting file: we've been storing
2226 bandwidth accounting information in the state file since
2227 0.1.2.5-alpha. This may result in bandwidth accounting errors
2228 if you try to upgrade from 0.1.1.x or earlier, or if you try to
2229 downgrade to 0.1.1.x or earlier.
2230 - New convenience code to locate a file within the DataDirectory.
2231 - Move non-authority functionality out of dirvote.c.
2232 - Refactor the arguments for router_pick_{directory_|trusteddir}server
2233 so that they all take the same named flags.
2236 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
2237 Unix users an easy way to script their Tor process (e.g. by
2238 adjusting bandwidth based on the time of the day).
2241 Changes in version 0.2.0.8-alpha - 2007-10-12
2242 This eighth development snapshot fixes a crash bug that's been bothering
2243 us since February 2007, lets bridge authorities store a list of bridge
2244 descriptors they've seen, gets v3 directory voting closer to working,
2245 starts caching v3 directory consensus documents on directory mirrors,
2246 and fixes a variety of smaller issues including some minor memory leaks.
2248 o Major features (router descriptor cache):
2249 - Store routers in a file called cached-descriptors instead of in
2250 cached-routers. Initialize cached-descriptors from cached-routers
2251 if the old format is around. The new format allows us to store
2252 annotations along with descriptors.
2253 - Use annotations to record the time we received each descriptor, its
2254 source, and its purpose.
2255 - Disable the SETROUTERPURPOSE controller command: it is now
2257 - Controllers should now specify cache=no or cache=yes when using
2258 the +POSTDESCRIPTOR command.
2259 - Bridge authorities now write bridge descriptors to disk, meaning
2260 we can export them to other programs and begin distributing them
2263 o Major features (directory authorities):
2264 - When a v3 authority is missing votes or signatures, it now tries
2266 - Directory authorities track weighted fractional uptime as well as
2267 weighted mean-time-between failures. WFU is suitable for deciding
2268 whether a node is "usually up", while MTBF is suitable for deciding
2269 whether a node is "likely to stay up." We need both, because
2270 "usually up" is a good requirement for guards, while "likely to
2271 stay up" is a good requirement for long-lived connections.
2273 o Major features (v3 directory system):
2274 - Caches now download v3 network status documents as needed,
2275 and download the descriptors listed in them.
2276 - All hosts now attempt to download and keep fresh v3 authority
2277 certificates, and re-attempt after failures.
2278 - More internal-consistency checks for vote parsing.
2280 o Major bugfixes (crashes):
2281 - If a connection is shut down abruptly because of something that
2282 happened inside connection_flushed_some(), do not call
2283 connection_finished_flushing(). Should fix bug 451. Bugfix on
2286 o Major bugfixes (performance):
2287 - Fix really bad O(n^2) performance when parsing a long list of
2288 routers: Instead of searching the entire list for an "extra-info "
2289 string which usually wasn't there, once for every routerinfo
2290 we read, just scan lines forward until we find one we like.
2292 - When we add data to a write buffer in response to the data on that
2293 write buffer getting low because of a flush, do not consider the
2294 newly added data as a candidate for immediate flushing, but rather
2295 make it wait until the next round of writing. Otherwise, we flush
2296 and refill recursively, and a single greedy TLS connection can
2297 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
2299 o Minor features (v3 authority system):
2300 - Add more ways for tools to download the votes that lead to the
2302 - Send a 503 when low on bandwidth and a vote, consensus, or
2303 certificate is requested.
2304 - If-modified-since is now implemented properly for all kinds of
2305 certificate requests.
2307 o Minor bugfixes (network statuses):
2308 - Tweak the implementation of proposal 109 slightly: allow at most
2309 two Tor servers on the same IP address, except if it's the location
2310 of a directory authority, in which case allow five. Bugfix on
2313 o Minor bugfixes (controller):
2314 - When sending a status event to the controller telling it that an
2315 OR address is reachable, set the port correctly. (Previously we
2316 were reporting the dir port.) Bugfix on 0.1.2.x.
2318 o Minor bugfixes (v3 directory system):
2319 - Fix logic to look up a cert by its signing key digest. Bugfix on
2321 - Only change the reply to a vote to "OK" if it's not already
2322 set. This gets rid of annoying "400 OK" log messages, which may
2323 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
2324 - When we get a valid consensus, recompute the voting schedule.
2325 - Base the valid-after time of a vote on the consensus voting
2326 schedule, not on our preferred schedule.
2327 - Make the return values and messages from signature uploads and
2328 downloads more sensible.
2329 - Fix a memory leak when serving votes and consensus documents, and
2330 another when serving certificates.
2332 o Minor bugfixes (performance):
2333 - Use a slightly simpler string hashing algorithm (copying Python's
2334 instead of Java's) and optimize our digest hashing algorithm to take
2335 advantage of 64-bit platforms and to remove some possibly-costly
2337 - Fix a minor memory leak whenever we parse guards from our state
2338 file. Bugfix on 0.2.0.7-alpha.
2339 - Fix a minor memory leak whenever we write out a file. Bugfix on
2341 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
2342 command. Bugfix on 0.2.0.5-alpha.
2344 o Minor bugfixes (portability):
2345 - On some platforms, accept() can return a broken address. Detect
2346 this more quietly, and deal accordingly. Fixes bug 483.
2347 - Stop calling tor_strlower() on uninitialized memory in some cases.
2348 Bugfix in 0.2.0.7-alpha.
2350 o Minor bugfixes (usability):
2351 - Treat some 403 responses from directory servers as INFO rather than
2352 WARN-severity events.
2353 - It's not actually an error to find a non-pending entry in the DNS
2354 cache when canceling a pending resolve. Don't log unless stuff is
2355 fishy. Resolves bug 463.
2357 o Minor bugfixes (anonymity):
2358 - Never report that we've used more bandwidth than we're willing to
2359 relay: it leaks how much non-relay traffic we're using. Resolves
2361 - When looking for a circuit to cannibalize, consider family as well
2362 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
2363 circuit cannibalization).
2365 o Code simplifications and refactoring:
2366 - Make a bunch of functions static. Remove some dead code.
2367 - Pull out about a third of the really big routerlist.c; put it in a
2368 new module, networkstatus.c.
2369 - Merge the extra fields in local_routerstatus_t back into
2370 routerstatus_t: we used to need one routerstatus_t for each
2371 authority's opinion, plus a local_routerstatus_t for the locally
2372 computed consensus opinion. To save space, we put the locally
2373 modified fields into local_routerstatus_t, and only the common
2374 stuff into routerstatus_t. But once v3 directories are in use,
2375 clients and caches will no longer need to hold authority opinions;
2376 thus, the rationale for keeping the types separate is now gone.
2377 - Make the code used to reschedule and reattempt downloads more
2379 - Turn all 'Are we a directory server/mirror?' logic into a call to
2381 - Remove the code to generate the oldest (v1) directory format.
2382 The code has been disabled since 0.2.0.5-alpha.
2385 Changes in version 0.2.0.7-alpha - 2007-09-21
2386 This seventh development snapshot makes bridges work again, makes bridge
2387 authorities work for the first time, fixes two huge performance flaws
2388 in hidden services, and fixes a variety of minor issues.
2390 o New directory authorities:
2391 - Set up moria1 and tor26 as the first v3 directory authorities. See
2392 doc/spec/dir-spec.txt for details on the new directory design.
2394 o Major bugfixes (crashes):
2395 - Fix possible segfaults in functions called from
2396 rend_process_relay_cell(). Bugfix on 0.1.2.x.
2398 o Major bugfixes (bridges):
2399 - Fix a bug that made servers send a "404 Not found" in response to
2400 attempts to fetch their server descriptor. This caused Tor servers
2401 to take many minutes to establish reachability for their DirPort,
2402 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
2403 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
2404 users configure that and specify a bridge with an identity
2405 fingerprint, now they will lookup the bridge descriptor at the
2406 default bridge authority via a one-hop tunnel, but once circuits
2407 are established they will switch to a three-hop tunnel for later
2408 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
2410 o Major bugfixes (hidden services):
2411 - Hidden services were choosing introduction points uniquely by
2412 hexdigest, but when constructing the hidden service descriptor
2413 they merely wrote the (potentially ambiguous) nickname.
2414 - Clients now use the v2 intro format for hidden service
2415 connections: they specify their chosen rendezvous point by identity
2416 digest rather than by (potentially ambiguous) nickname. Both
2417 are bugfixes on 0.1.2.x, and they could speed up hidden service
2418 connections dramatically. Thanks to Karsten Loesing.
2420 o Minor features (security):
2421 - As a client, do not believe any server that tells us that an
2422 address maps to an internal address space.
2423 - Make it possible to enable HashedControlPassword and
2424 CookieAuthentication at the same time.
2426 o Minor features (guard nodes):
2427 - Tag every guard node in our state file with the version that
2428 we believe added it, or with our own version if we add it. This way,
2429 if a user temporarily runs an old version of Tor and then switches
2430 back to a new one, she doesn't automatically lose her guards.
2432 o Minor features (speed):
2433 - When implementing AES counter mode, update only the portions of the
2434 counter buffer that need to change, and don't keep separate
2435 network-order and host-order counters when they are the same (i.e.,
2436 on big-endian hosts.)
2438 o Minor features (controller):
2439 - Accept LF instead of CRLF on controller, since some software has a
2440 hard time generating real Internet newlines.
2441 - Add GETINFO values for the server status events
2442 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
2446 - Routers no longer include bandwidth-history lines in their
2447 descriptors; this information is already available in extra-info
2448 documents, and including it in router descriptors took up 60%
2449 (!) of compressed router descriptor downloads. Completes
2450 implementation of proposal 104.
2451 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
2452 and TorControl.py, as they use the old v0 controller protocol,
2453 and are obsoleted by TorFlow anyway.
2454 - Drop support for v1 rendezvous descriptors, since we never used
2455 them anyway, and the code has probably rotted by now. Based on
2456 patch from Karsten Loesing.
2457 - On OSX, stop warning the user that kqueue support in libevent is
2458 "experimental", since it seems to have worked fine for ages.
2461 - When generating information telling us how to extend to a given
2462 router, do not try to include the nickname if it is absent. Fixes
2463 bug 467. Bugfix on 0.2.0.3-alpha.
2464 - Fix a user-triggerable (but not remotely-triggerable) segfault
2465 in expand_filename(). Bugfix on 0.1.2.x.
2466 - Fix a memory leak when freeing incomplete requests from DNSPort.
2467 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
2468 - Don't try to access (or alter) the state file when running
2469 --list-fingerprint or --verify-config or --hash-password. (Resolves
2470 bug 499.) Bugfix on 0.1.2.x.
2471 - Servers used to decline to publish their DirPort if their
2472 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
2473 were below a threshold. Now they only look at BandwidthRate and
2474 RelayBandwidthRate. Bugfix on 0.1.2.x.
2475 - Remove an optimization in the AES counter-mode code that assumed
2476 that the counter never exceeded 2^68. When the counter can be set
2477 arbitrarily as an IV (as it is by Karsten's new hidden services
2478 code), this assumption no longer holds. Bugfix on 0.1.2.x.
2479 - Resume listing "AUTHORITY" flag for authorities in network status.
2480 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
2482 o Code simplifications and refactoring:
2483 - Revamp file-writing logic so we don't need to have the entire
2484 contents of a file in memory at once before we write to disk. Tor,
2486 - Turn "descriptor store" into a full-fledged type.
2487 - Move all NT services code into a separate source file.
2488 - Unify all code that computes medians, percentile elements, etc.
2489 - Get rid of a needless malloc when parsing address policies.
2492 Changes in version 0.1.2.17 - 2007-08-30
2493 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
2494 X bundles. Vidalia 0.0.14 makes authentication required for the
2495 ControlPort in the default configuration, which addresses important
2496 security risks. Everybody who uses Vidalia (or another controller)
2499 In addition, this Tor update fixes major load balancing problems with
2500 path selection, which should speed things up a lot once many people
2503 o Major bugfixes (security):
2504 - We removed support for the old (v0) control protocol. It has been
2505 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
2506 become more of a headache than it's worth.
2508 o Major bugfixes (load balancing):
2509 - When choosing nodes for non-guard positions, weight guards
2510 proportionally less, since they already have enough load. Patch
2512 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
2513 will allow fast Tor servers to get more attention.
2514 - When we're upgrading from an old Tor version, forget our current
2515 guards and pick new ones according to the new weightings. These
2516 three load balancing patches could raise effective network capacity
2517 by a factor of four. Thanks to Mike Perry for measurements.
2519 o Major bugfixes (stream expiration):
2520 - Expire not-yet-successful application streams in all cases if
2521 they've been around longer than SocksTimeout. Right now there are
2522 some cases where the stream will live forever, demanding a new
2523 circuit every 15 seconds. Fixes bug 454; reported by lodger.
2525 o Minor features (controller):
2526 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
2527 is valid before any authentication has been received. It tells
2528 a controller what kind of authentication is expected, and what
2529 protocol is spoken. Implements proposal 119.
2531 o Minor bugfixes (performance):
2532 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
2533 greatly speeding up loading cached-routers from disk on startup.
2534 - Disable sentinel-based debugging for buffer code: we squashed all
2535 the bugs that this was supposed to detect a long time ago, and now
2536 its only effect is to change our buffer sizes from nice powers of
2537 two (which platform mallocs tend to like) to values slightly over
2538 powers of two (which make some platform mallocs sad).
2540 o Minor bugfixes (misc):
2541 - If exit bandwidth ever exceeds one third of total bandwidth, then
2542 use the correct formula to weight exit nodes when choosing paths.
2543 Based on patch from Mike Perry.
2544 - Choose perfectly fairly among routers when choosing by bandwidth and
2545 weighting by fraction of bandwidth provided by exits. Previously, we
2546 would choose with only approximate fairness, and correct ourselves
2547 if we ran off the end of the list.
2548 - If we require CookieAuthentication but we fail to write the
2549 cookie file, we would warn but not exit, and end up in a state
2550 where no controller could authenticate. Now we exit.
2551 - If we require CookieAuthentication, stop generating a new cookie
2552 every time we change any piece of our config.
2553 - Refuse to start with certain directory authority keys, and
2554 encourage people using them to stop.
2555 - Terminate multi-line control events properly. Original patch
2557 - Fix a minor memory leak when we fail to find enough suitable
2558 servers to choose a circuit.
2559 - Stop leaking part of the descriptor when we run into a particularly
2560 unparseable piece of it.
2563 Changes in version 0.2.0.6-alpha - 2007-08-26
2564 This sixth development snapshot features a new Vidalia version in the
2565 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
2566 the ControlPort in the default configuration, which addresses important
2569 In addition, this snapshot fixes major load balancing problems
2570 with path selection, which should speed things up a lot once many
2571 people have upgraded. The directory authorities also use a new
2572 mean-time-between-failure approach to tracking which servers are stable,
2573 rather than just looking at the most recent uptime.
2575 o New directory authorities:
2576 - Set up Tonga as the default bridge directory authority.
2579 - Directory authorities now track servers by weighted
2580 mean-times-between-failures. When we have 4 or more days of data,
2581 use measured MTBF rather than declared uptime to decide whether
2582 to call a router Stable. Implements proposal 108.
2584 o Major bugfixes (load balancing):
2585 - When choosing nodes for non-guard positions, weight guards
2586 proportionally less, since they already have enough load. Patch
2588 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
2589 will allow fast Tor servers to get more attention.
2590 - When we're upgrading from an old Tor version, forget our current
2591 guards and pick new ones according to the new weightings. These
2592 three load balancing patches could raise effective network capacity
2593 by a factor of four. Thanks to Mike Perry for measurements.
2595 o Major bugfixes (descriptor parsing):
2596 - Handle unexpected whitespace better in malformed descriptors. Bug
2597 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
2600 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
2601 GETINFO for Torstat to use until it can switch to using extrainfos.
2602 - Optionally (if built with -DEXPORTMALLINFO) export the output
2603 of mallinfo via http, as tor/mallinfo.txt. Only accessible
2607 - Do not intermix bridge routers with controller-added
2608 routers. (Bugfix on 0.2.0.x)
2609 - Do not fail with an assert when accept() returns an unexpected
2610 address family. Addresses but does not wholly fix bug 483. (Bugfix
2612 - Let directory authorities startup even when they can't generate
2613 a descriptor immediately, e.g. because they don't know their
2615 - Stop putting the authentication cookie in a file called "0"
2616 in your working directory if you don't specify anything for the
2617 new CookieAuthFile option. Reported by Matt Edman.
2618 - Make it possible to read the PROTOCOLINFO response in a way that
2619 conforms to our control-spec. Reported by Matt Edman.
2620 - Fix a minor memory leak when we fail to find enough suitable
2621 servers to choose a circuit. Bugfix on 0.1.2.x.
2622 - Stop leaking part of the descriptor when we run into a particularly
2623 unparseable piece of it. Bugfix on 0.1.2.x.
2624 - Unmap the extrainfo cache file on exit.
2627 Changes in version 0.2.0.5-alpha - 2007-08-19
2628 This fifth development snapshot fixes compilation on Windows again;
2629 fixes an obnoxious client-side bug that slowed things down and put
2630 extra load on the network; gets us closer to using the v3 directory
2631 voting scheme; makes it easier for Tor controllers to use cookie-based
2632 authentication; and fixes a variety of other bugs.
2635 - Version 1 directories are no longer generated in full. Instead,
2636 authorities generate and serve "stub" v1 directories that list
2637 no servers. This will stop Tor versions 0.1.0.x and earlier from
2638 working, but (for security reasons) nobody should be running those
2641 o Major bugfixes (compilation, 0.2.0.x):
2642 - Try to fix Win32 compilation again: improve checking for IPv6 types.
2643 - Try to fix MSVC compilation: build correctly on platforms that do
2644 not define s6_addr16 or s6_addr32.
2645 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
2648 o Major bugfixes (stream expiration):
2649 - Expire not-yet-successful application streams in all cases if
2650 they've been around longer than SocksTimeout. Right now there are
2651 some cases where the stream will live forever, demanding a new
2652 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
2655 o Minor features (directory servers):
2656 - When somebody requests a list of statuses or servers, and we have
2657 none of those, return a 404 rather than an empty 200.
2659 o Minor features (directory voting):
2660 - Store v3 consensus status consensuses on disk, and reload them
2663 o Minor features (security):
2664 - Warn about unsafe ControlPort configurations.
2665 - Refuse to start with certain directory authority keys, and
2666 encourage people using them to stop.
2668 o Minor features (controller):
2669 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
2670 is valid before any authentication has been received. It tells
2671 a controller what kind of authentication is expected, and what
2672 protocol is spoken. Implements proposal 119.
2673 - New config option CookieAuthFile to choose a new location for the
2674 cookie authentication file, and config option
2675 CookieAuthFileGroupReadable to make it group-readable.
2677 o Minor features (unit testing):
2678 - Add command-line arguments to unit-test executable so that we can
2679 invoke any chosen test from the command line rather than having
2680 to run the whole test suite at once; and so that we can turn on
2681 logging for the unit tests.
2683 o Minor bugfixes (on 0.1.2.x):
2684 - If we require CookieAuthentication but we fail to write the
2685 cookie file, we would warn but not exit, and end up in a state
2686 where no controller could authenticate. Now we exit.
2687 - If we require CookieAuthentication, stop generating a new cookie
2688 every time we change any piece of our config.
2689 - When loading bandwidth history, do not believe any information in
2690 the future. Fixes bug 434.
2691 - When loading entry guard information, do not believe any information
2693 - When we have our clock set far in the future and generate an
2694 onion key, then re-set our clock to be correct, we should not stop
2695 the onion key from getting rotated.
2696 - Clean up torrc sample config file.
2697 - Do not automatically run configure from autogen.sh. This
2698 non-standard behavior tended to annoy people who have built other
2701 o Minor bugfixes (on 0.2.0.x):
2702 - Fix a bug with AutomapHostsOnResolve that would always cause
2703 the second request to fail. Bug reported by Kate. Bugfix on
2705 - Fix a bug in ADDRMAP controller replies that would sometimes
2706 try to print a NULL. Patch from tup.
2707 - Read v3 directory authority keys from the right location.
2708 - Numerous bugfixes to directory voting code.
2711 Changes in version 0.1.2.16 - 2007-08-01
2712 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
2713 remote attacker in certain situations to rewrite the user's torrc
2714 configuration file. This can completely compromise anonymity of users
2715 in most configurations, including those running the Vidalia bundles,
2716 TorK, etc. Or worse.
2718 o Major security fixes:
2719 - Close immediately after missing authentication on control port;
2720 do not allow multiple authentication attempts.
2723 Changes in version 0.2.0.4-alpha - 2007-08-01
2724 This fourth development snapshot fixes a critical security vulnerability
2725 for most users, specifically those running Vidalia, TorK, etc. Everybody
2726 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
2728 o Major security fixes:
2729 - Close immediately after missing authentication on control port;
2730 do not allow multiple authentication attempts.
2732 o Major bugfixes (compilation):
2733 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
2736 o Minor features (performance):
2737 - Be even more aggressive about releasing RAM from small
2738 empty buffers. Thanks to our free-list code, this shouldn't be too
2739 performance-intensive.
2740 - Disable sentinel-based debugging for buffer code: we squashed all
2741 the bugs that this was supposed to detect a long time ago, and
2742 now its only effect is to change our buffer sizes from nice
2743 powers of two (which platform mallocs tend to like) to values
2744 slightly over powers of two (which make some platform mallocs sad).
2745 - Log malloc statistics from mallinfo() on platforms where it
2749 Changes in version 0.2.0.3-alpha - 2007-07-29
2750 This third development snapshot introduces new experimental
2751 blocking-resistance features and a preliminary version of the v3
2752 directory voting design, and includes many other smaller features
2756 - The first pieces of our "bridge" design for blocking-resistance
2757 are implemented. People can run bridge directory authorities;
2758 people can run bridges; and people can configure their Tor clients
2759 with a set of bridges to use as the first hop into the Tor network.
2760 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
2762 - Create listener connections before we setuid to the configured
2763 User and Group. Now non-Windows users can choose port values
2764 under 1024, start Tor as root, and have Tor bind those ports
2765 before it changes to another UID. (Windows users could already
2767 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
2768 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
2769 on "vserver" accounts. (Patch from coderman.)
2770 - Be even more aggressive about separating local traffic from relayed
2771 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
2773 o Major features (experimental):
2774 - First cut of code for "v3 dir voting": directory authorities will
2775 vote on a common network status document rather than each publishing
2776 their own opinion. This code needs more testing and more corner-case
2777 handling before it's ready for use.
2780 - Directory authorities now call routers Fast if their bandwidth is
2781 at least 100KB/s, and consider their bandwidth adequate to be a
2782 Guard if it is at least 250KB/s, no matter the medians. This fix
2783 complements proposal 107. [Bugfix on 0.1.2.x]
2784 - Directory authorities now never mark more than 3 servers per IP as
2785 Valid and Running. (Implements proposal 109, by Kevin Bauer and
2787 - Minor change to organizationName and commonName generation
2788 procedures in TLS certificates during Tor handshakes, to invalidate
2789 some earlier censorware approaches. This is not a long-term
2790 solution, but applying it will give us a bit of time to look into
2791 the epidemiology of countermeasures as they spread.
2793 o Major bugfixes (directory):
2794 - Rewrite directory tokenization code to never run off the end of
2795 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
2797 o Minor features (controller):
2798 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
2799 match requests to applications. (Patch from Robert Hogan.)
2800 - Report address and port correctly on connections to DNSPort. (Patch
2802 - Add a RESOLVE command to launch hostname lookups. (Original patch
2804 - Add GETINFO status/enough-dir-info to let controllers tell whether
2805 Tor has downloaded sufficient directory information. (Patch
2807 - You can now use the ControlSocket option to tell Tor to listen for
2808 controller connections on Unix domain sockets on systems that
2809 support them. (Patch from Peter Palfrader.)
2810 - STREAM NEW events are generated for DNSPort requests and for
2811 tunneled directory connections. (Patch from Robert Hogan.)
2812 - New "GETINFO address-mappings/*" command to get address mappings
2813 with expiry information. "addr-mappings/*" is now deprecated.
2816 o Minor features (misc):
2817 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
2819 - The tor-gencert tool for v3 directory authorities now creates all
2820 files as readable to the file creator only, and write-protects
2821 the authority identity key.
2822 - When dumping memory usage, list bytes used in buffer memory
2824 - When running with dmalloc, dump more stats on hup and on exit.
2825 - Directory authorities now fail quickly and (relatively) harmlessly
2826 if they generate a network status document that is somehow
2829 o Traffic load balancing improvements:
2830 - If exit bandwidth ever exceeds one third of total bandwidth, then
2831 use the correct formula to weight exit nodes when choosing paths.
2832 (Based on patch from Mike Perry.)
2833 - Choose perfectly fairly among routers when choosing by bandwidth and
2834 weighting by fraction of bandwidth provided by exits. Previously, we
2835 would choose with only approximate fairness, and correct ourselves
2836 if we ran off the end of the list. [Bugfix on 0.1.2.x]
2838 o Performance improvements:
2839 - Be more aggressive with freeing buffer RAM or putting it on the
2841 - Use Critical Sections rather than Mutexes for synchronizing threads
2842 on win32; Mutexes are heavier-weight, and designed for synchronizing
2845 o Deprecated and removed features:
2846 - RedirectExits is now deprecated.
2847 - Stop allowing address masks that do not correspond to bit prefixes.
2848 We have warned about these for a really long time; now it's time
2849 to reject them. (Patch from croup.)
2851 o Minor bugfixes (directory):
2852 - Fix another crash bug related to extra-info caching. (Bug found by
2853 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
2854 - Directories no longer return a "304 not modified" when they don't
2855 have the networkstatus the client asked for. Also fix a memory
2856 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
2857 - We had accidentally labelled 0.1.2.x directory servers as not
2858 suitable for begin_dir requests, and had labelled no directory
2859 servers as suitable for uploading extra-info documents. [Bugfix
2862 o Minor bugfixes (dns):
2863 - Fix a crash when DNSPort is set more than once. (Patch from Robert
2864 Hogan.) [Bugfix on 0.2.0.2-alpha]
2865 - Add DNSPort connections to the global connection list, so that we
2866 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
2868 - Fix a dangling reference that could lead to a crash when DNSPort is
2869 changed or closed (Patch from Robert Hogan.) [Bugfix on
2872 o Minor bugfixes (controller):
2873 - Provide DNS expiry times in GMT, not in local time. For backward
2874 compatibility, ADDRMAP events only provide GMT expiry in an extended
2875 field. "GETINFO address-mappings" always does the right thing.
2876 - Use CRLF line endings properly in NS events.
2877 - Terminate multi-line control events properly. (Original patch
2878 from tup.) [Bugfix on 0.1.2.x-alpha]
2879 - Do not include spaces in SOURCE_ADDR fields in STREAM
2880 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
2883 Changes in version 0.1.2.15 - 2007-07-17
2884 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
2885 problems, fixes compilation on BSD, and fixes a variety of other
2886 bugs. Everybody should upgrade.
2888 o Major bugfixes (compilation):
2889 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
2891 o Major bugfixes (crashes):
2892 - Try even harder not to dereference the first character after
2893 an mmap(). Reported by lodger.
2894 - Fix a crash bug in directory authorities when we re-number the
2895 routerlist while inserting a new router.
2896 - When the cached-routers file is an even multiple of the page size,
2897 don't run off the end and crash. (Fixes bug 455; based on idea
2899 - Fix eventdns.c behavior on Solaris: It is critical to include
2900 orconfig.h _before_ sys/types.h, so that we can get the expected
2901 definition of _FILE_OFFSET_BITS.
2903 o Major bugfixes (security):
2904 - Fix a possible buffer overrun when using BSD natd support. Bug
2906 - When sending destroy cells from a circuit's origin, don't include
2907 the reason for tearing down the circuit. The spec says we didn't,
2908 and now we actually don't. Reported by lodger.
2909 - Keep streamids from different exits on a circuit separate. This
2910 bug may have allowed other routers on a given circuit to inject
2911 cells into streams. Reported by lodger; fixes bug 446.
2912 - If there's a never-before-connected-to guard node in our list,
2913 never choose any guards past it. This way we don't expand our
2914 guard list unless we need to.
2916 o Minor bugfixes (guard nodes):
2917 - Weight guard selection by bandwidth, so that low-bandwidth nodes
2918 don't get overused as guards.
2920 o Minor bugfixes (directory):
2921 - Correctly count the number of authorities that recommend each
2922 version. Previously, we were under-counting by 1.
2923 - Fix a potential crash bug when we load many server descriptors at
2924 once and some of them make others of them obsolete. Fixes bug 458.
2926 o Minor bugfixes (hidden services):
2927 - Stop tearing down the whole circuit when the user asks for a
2928 connection to a port that the hidden service didn't configure.
2931 o Minor bugfixes (misc):
2932 - On Windows, we were preventing other processes from reading
2933 cached-routers while Tor was running. Reported by janbar.
2934 - Fix a possible (but very unlikely) bug in picking routers by
2935 bandwidth. Add a log message to confirm that it is in fact
2936 unlikely. Patch from lodger.
2937 - Backport a couple of memory leak fixes.
2938 - Backport miscellaneous cosmetic bugfixes.
2941 Changes in version 0.2.0.2-alpha - 2007-06-02
2942 o Major bugfixes on 0.2.0.1-alpha:
2943 - Fix an assertion failure related to servers without extra-info digests.
2944 Resolves bugs 441 and 442.
2946 o Minor features (directory):
2947 - Support "If-Modified-Since" when answering HTTP requests for
2948 directories, running-routers documents, and network-status documents.
2949 (There's no need to support it for router descriptors, since those
2950 are downloaded by descriptor digest.)
2952 o Minor build issues:
2953 - Clear up some MIPSPro compiler warnings.
2954 - When building from a tarball on a machine that happens to have SVK
2955 installed, report the micro-revision as whatever version existed
2956 in the tarball, not as "x".
2959 Changes in version 0.2.0.1-alpha - 2007-06-01
2960 This early development snapshot provides new features for people running
2961 Tor as both a client and a server (check out the new RelayBandwidth
2962 config options); lets Tor run as a DNS proxy; and generally moves us
2963 forward on a lot of fronts.
2965 o Major features, server usability:
2966 - New config options RelayBandwidthRate and RelayBandwidthBurst:
2967 a separate set of token buckets for relayed traffic. Right now
2968 relayed traffic is defined as answers to directory requests, and
2969 OR connections that don't have any local circuits on them.
2971 o Major features, client usability:
2972 - A client-side DNS proxy feature to replace the need for
2973 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
2974 for DNS requests on port 9999, use the Tor network to resolve them
2975 anonymously, and send the reply back like a regular DNS server.
2976 The code still only implements a subset of DNS.
2977 - Make PreferTunneledDirConns and TunnelDirConns work even when
2978 we have no cached directory info. This means Tor clients can now
2979 do all of their connections protected by TLS.
2981 o Major features, performance and efficiency:
2982 - Directory authorities accept and serve "extra info" documents for
2983 routers. These documents contain fields from router descriptors
2984 that aren't usually needed, and that use a lot of excess
2985 bandwidth. Once these fields are removed from router descriptors,
2986 the bandwidth savings should be about 60%. [Partially implements
2988 - Servers upload extra-info documents to any authority that accepts
2989 them. Authorities (and caches that have been configured to download
2990 extra-info documents) download them as needed. [Partially implements
2992 - Change the way that Tor buffers data that it is waiting to write.
2993 Instead of queueing data cells in an enormous ring buffer for each
2994 client->OR or OR->OR connection, we now queue cells on a separate
2995 queue for each circuit. This lets us use less slack memory, and
2996 will eventually let us be smarter about prioritizing different kinds
2998 - Use memory pools to allocate cells with better speed and memory
2999 efficiency, especially on platforms where malloc() is inefficient.
3000 - Stop reading on edge connections when their corresponding circuit
3001 buffers are full; start again as the circuits empty out.
3003 o Major features, other:
3004 - Add an HSAuthorityRecordStats option that hidden service authorities
3005 can use to track statistics of overall hidden service usage without
3006 logging information that would be very useful to an attacker.
3007 - Start work implementing multi-level keys for directory authorities:
3008 Add a standalone tool to generate key certificates. (Proposal 103.)
3011 - Directory authorities now call routers Stable if they have an
3012 uptime of at least 30 days, even if that's not the median uptime
3013 in the network. Implements proposal 107, suggested by Kevin Bauer
3016 o Minor fixes (resource management):
3017 - Count the number of open sockets separately from the number
3018 of active connection_t objects. This will let us avoid underusing
3019 our allocated connection limit.
3020 - We no longer use socket pairs to link an edge connection to an
3021 anonymous directory connection or a DirPort test connection.
3022 Instead, we track the link internally and transfer the data
3023 in-process. This saves two sockets per "linked" connection (at the
3024 client and at the server), and avoids the nasty Windows socketpair()
3026 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
3027 for every single inactive connection_t. Free items from the
3028 4k/16k-buffer free lists when they haven't been used for a while.
3030 o Minor features (build):
3031 - Make autoconf search for libevent, openssl, and zlib consistently.
3032 - Update deprecated macros in configure.in.
3033 - When warning about missing headers, tell the user to let us
3034 know if the compile succeeds anyway, so we can downgrade the
3036 - Include the current subversion revision as part of the version
3037 string: either fetch it directly if we're in an SVN checkout, do
3038 some magic to guess it if we're in an SVK checkout, or use
3039 the last-detected version if we're building from a .tar.gz.
3040 Use this version consistently in log messages.
3042 o Minor features (logging):
3043 - Always prepend "Bug: " to any log message about a bug.
3044 - Put a platform string (e.g. "Linux i686") in the startup log
3045 message, so when people paste just their logs, we know if it's
3046 OpenBSD or Windows or what.
3047 - When logging memory usage, break down memory used in buffers by
3050 o Minor features (directory system):
3051 - New config option V2AuthoritativeDirectory that all directory
3052 authorities should set. This will let future authorities choose
3053 not to serve V2 directory information.
3054 - Directory authorities allow multiple router descriptors and/or extra
3055 info documents to be uploaded in a single go. This will make
3056 implementing proposal 104 simpler.
3058 o Minor features (controller):
3059 - Add a new config option __DisablePredictedCircuits designed for
3060 use by the controller, when we don't want Tor to build any circuits
3062 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
3063 so we can exit from the middle of the circuit.
3064 - Implement "getinfo status/circuit-established".
3065 - Implement "getinfo status/version/..." so a controller can tell
3066 whether the current version is recommended, and whether any versions
3067 are good, and how many authorities agree. (Patch from shibz.)
3069 o Minor features (hidden services):
3070 - Allow multiple HiddenServicePort directives with the same virtual
3071 port; when they occur, the user is sent round-robin to one
3072 of the target ports chosen at random. Partially fixes bug 393 by
3073 adding limited ad-hoc round-robining.
3075 o Minor features (other):
3077 - Add a new AutomapHostsOnResolve option: when it is enabled, any
3078 resolve request for hosts matching a given pattern causes Tor to
3079 generate an internal virtual address mapping for that host. This
3080 allows DNSPort to work sensibly with hidden service users. By
3081 default, .exit and .onion addresses are remapped; the list of
3082 patterns can be reconfigured with AutomapHostsSuffixes.
3083 - Add an "-F" option to tor-resolve to force a resolve for a .onion
3084 address. Thanks to the AutomapHostsOnResolve option, this is no
3085 longer a completely silly thing to do.
3086 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
3087 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
3088 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
3089 minus 1 byte: the actual maximum declared bandwidth.
3092 - Removed support for the old binary "version 0" controller protocol.
3093 This has been deprecated since 0.1.1, and warnings have been issued
3094 since 0.1.2. When we encounter a v0 control message, we now send
3095 back an error and close the connection.
3096 - Remove the old "dns worker" server DNS code: it hasn't been default
3097 since 0.1.2.2-alpha, and all the servers seem to be using the new
3100 o Minor bugfixes (portability):
3101 - Even though Windows is equally happy with / and \ as path separators,
3102 try to use \ consistently on Windows and / consistently on Unix: it
3103 makes the log messages nicer.
3104 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
3105 - Read resolv.conf files correctly on platforms where read() returns
3106 partial results on small file reads.
3108 o Minor bugfixes (directory):
3109 - Correctly enforce that elements of directory objects do not appear
3110 more often than they are allowed to appear.
3111 - When we are reporting the DirServer line we just parsed, we were
3112 logging the second stanza of the key fingerprint, not the first.
3114 o Minor bugfixes (logging):
3115 - When we hit an EOF on a log (probably because we're shutting down),
3116 don't try to remove the log from the list: just mark it as
3117 unusable. (Bulletproofs against bug 222.)
3119 o Minor bugfixes (other):
3120 - In the exitlist script, only consider the most recently published
3121 server descriptor for each server. Also, when the user requests
3122 a list of servers that _reject_ connections to a given address,
3123 explicitly exclude the IPs that also have servers that accept
3124 connections to that address. (Resolves bug 405.)
3125 - Stop allowing hibernating servers to be "stable" or "fast".
3126 - On Windows, we were preventing other processes from reading
3127 cached-routers while Tor was running. (Reported by janbar)
3128 - Make the NodeFamilies config option work. (Reported by
3129 lodger -- it has never actually worked, even though we added it
3131 - Check return values from pthread_mutex functions.
3132 - Don't save non-general-purpose router descriptors to the disk cache,
3133 because we have no way of remembering what their purpose was when
3135 - Add even more asserts to hunt down bug 417.
3136 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
3137 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
3138 Add a log message to confirm that it is in fact unlikely.
3140 o Minor bugfixes (controller):
3141 - Make 'getinfo fingerprint' return a 551 error if we're not a
3142 server, so we match what the control spec claims we do. Reported
3144 - Fix a typo in an error message when extendcircuit fails that
3145 caused us to not follow the \r\n-based delimiter protocol. Reported
3148 o Code simplifications and refactoring:
3149 - Stop passing around circuit_t and crypt_path_t pointers that are
3150 implicit in other procedure arguments.
3151 - Drop the old code to choke directory connections when the
3152 corresponding OR connections got full: thanks to the cell queue
3153 feature, OR conns don't get full any more.
3154 - Make dns_resolve() handle attaching connections to circuits
3155 properly, so the caller doesn't have to.
3156 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
3157 - Keep the connection array as a dynamic smartlist_t, rather than as
3158 a fixed-sized array. This is important, as the number of connections
3159 is becoming increasingly decoupled from the number of sockets.
3162 Changes in version 0.1.2.14 - 2007-05-25
3163 Tor 0.1.2.14 changes the addresses of two directory authorities (this
3164 change especially affects those who serve or use hidden services),
3165 and fixes several other crash- and security-related bugs.
3167 o Directory authority changes:
3168 - Two directory authorities (moria1 and moria2) just moved to new
3169 IP addresses. This change will particularly affect those who serve
3170 or use hidden services.
3172 o Major bugfixes (crashes):
3173 - If a directory server runs out of space in the connection table
3174 as it's processing a begin_dir request, it will free the exit stream
3175 but leave it attached to the circuit, leading to unpredictable
3176 behavior. (Reported by seeess, fixes bug 425.)
3177 - Fix a bug in dirserv_remove_invalid() that would cause authorities
3178 to corrupt memory under some really unlikely scenarios.
3179 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
3180 - Avoid segfaults when reading from mmaped descriptor file. (Reported
3183 o Major bugfixes (security):
3184 - When choosing an entry guard for a circuit, avoid using guards
3185 that are in the same family as the chosen exit -- not just guards
3186 that are exactly the chosen exit. (Reported by lodger.)
3188 o Major bugfixes (resource management):
3189 - If a directory authority is down, skip it when deciding where to get
3190 networkstatus objects or descriptors. Otherwise we keep asking
3191 every 10 seconds forever. Fixes bug 384.
3192 - Count it as a failure if we fetch a valid network-status but we
3193 don't want to keep it. Otherwise we'll keep fetching it and keep
3194 not wanting to keep it. Fixes part of bug 422.
3195 - If all of our dirservers have given us bad or no networkstatuses
3196 lately, then stop hammering them once per minute even when we
3197 think they're failed. Fixes another part of bug 422.
3200 - Actually set the purpose correctly for descriptors inserted with
3202 - When we have k non-v2 authorities in our DirServer config,
3203 we ignored the last k authorities in the list when updating our
3205 - Correctly back-off from requesting router descriptors that we are
3206 having a hard time downloading.
3207 - Read resolv.conf files correctly on platforms where read() returns
3208 partial results on small file reads.
3209 - Don't rebuild the entire router store every time we get 32K of
3210 routers: rebuild it when the journal gets very large, or when
3211 the gaps in the store get very large.
3214 - When routers publish SVN revisions in their router descriptors,
3215 authorities now include those versions correctly in networkstatus
3217 - Warn when using a version of libevent before 1.3b to run a server on
3218 OSX or BSD: these versions interact badly with userspace threads.
3221 Changes in version 0.1.2.13 - 2007-04-24
3222 This release features some major anonymity fixes, such as safer path
3223 selection; better client performance; faster bootstrapping, better
3224 address detection, and better DNS support for servers; write limiting as
3225 well as read limiting to make servers easier to run; and a huge pile of
3226 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
3228 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
3229 of the Freenode IRC network, remembering his patience and vision for
3230 free speech on the Internet.
3233 - Fix a memory leak when we ask for "all" networkstatuses and we
3234 get one we don't recognize.
3235 - Add more asserts to hunt down bug 417.
3236 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
3239 Changes in version 0.1.2.12-rc - 2007-03-16
3241 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
3242 directory information requested inside Tor connections (i.e. via
3243 begin_dir cells). It only triggered when the same connection was
3244 serving other data at the same time. Reported by seeess.
3247 - When creating a circuit via the controller, send a 'launched'
3248 event when we're done, so we follow the spec better.
3251 Changes in version 0.1.2.11-rc - 2007-03-15
3252 o Minor bugfixes (controller), reported by daejees:
3253 - Correct the control spec to match how the code actually responds
3254 to 'getinfo addr-mappings/*'.
3255 - The control spec described a GUARDS event, but the code
3256 implemented a GUARD event. Standardize on GUARD, but let people
3260 Changes in version 0.1.2.10-rc - 2007-03-07
3261 o Major bugfixes (Windows):
3262 - Do not load the NT services library functions (which may not exist)
3263 just to detect if we're a service trying to shut down. Now we run
3264 on Win98 and friends again.
3266 o Minor bugfixes (other):
3267 - Clarify a couple of log messages.
3268 - Fix a misleading socks5 error number.
3271 Changes in version 0.1.2.9-rc - 2007-03-02
3272 o Major bugfixes (Windows):
3273 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
3274 of the usual GCC "%llu". This prevents a bug when saving 64-bit
3275 int configuration values: the high-order 32 bits would get
3276 truncated. In particular, we were being bitten by the default
3277 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
3278 and maybe also bug 397.)
3280 o Minor bugfixes (performance):
3281 - Use OpenSSL's AES implementation on platforms where it's faster.
3282 This could save us as much as 10% CPU usage.
3284 o Minor bugfixes (server):
3285 - Do not rotate onion key immediately after setting it for the first
3288 o Minor bugfixes (directory authorities):
3289 - Stop calling servers that have been hibernating for a long time
3290 "stable". Also, stop letting hibernating or obsolete servers affect
3291 uptime and bandwidth cutoffs.
3292 - Stop listing hibernating servers in the v1 directory.
3294 o Minor bugfixes (hidden services):
3295 - Upload hidden service descriptors slightly less often, to reduce
3296 load on authorities.
3298 o Minor bugfixes (other):
3299 - Fix an assert that could trigger if a controller quickly set then
3300 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
3301 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
3303 - Fix a potential race condition in the rpm installer. Found by
3305 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
3306 of 2 as indicating that the server is completely bad; it sometimes
3307 means that the server is just bad for the request in question. (may fix
3308 the last of bug 326.)
3309 - Disable encrypted directory connections when we don't have a server
3310 descriptor for the destination. We'll get this working again in
3314 Changes in version 0.1.2.8-beta - 2007-02-26
3315 o Major bugfixes (crashes):
3316 - Stop crashing when the controller asks us to resetconf more than
3317 one config option at once. (Vidalia 0.0.11 does this.)
3318 - Fix a crash that happened on Win98 when we're given command-line
3319 arguments: don't try to load NT service functions from advapi32.dll
3320 except when we need them. (Bug introduced in 0.1.2.7-alpha;
3322 - Fix a longstanding obscure crash bug that could occur when
3323 we run out of DNS worker processes. (Resolves bug 390.)
3325 o Major bugfixes (hidden services):
3326 - Correctly detect whether hidden service descriptor downloads are
3327 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
3329 o Major bugfixes (accounting):
3330 - When we start during an accounting interval before it's time to wake
3331 up, remember to wake up at the correct time. (May fix bug 342.)
3333 o Minor bugfixes (controller):
3334 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
3335 clear the corresponding on_circuit variable, and remember later
3336 that we don't need to send a redundant CLOSED event. (Resolves part
3338 - Report events where a resolve succeeded or where we got a socks
3339 protocol error correctly, rather than calling both of them
3341 - Change reported stream target addresses to IP consistently when
3342 we finally get the IP from an exit node.
3343 - Send log messages to the controller even if they happen to be very
3346 o Minor bugfixes (other):
3347 - Display correct results when reporting which versions are
3348 recommended, and how recommended they are. (Resolves bug 383.)
3349 - Improve our estimates for directory bandwidth to be less random:
3350 guess that an unrecognized directory will have the average bandwidth
3351 from all known directories, not that it will have the average
3352 bandwidth from those directories earlier than it on the list.
3353 - If we start a server with ClientOnly 1, then set ClientOnly to 0
3354 and hup, stop triggering an assert based on an empty onion_key.
3355 - On platforms with no working mmap() equivalent, don't warn the
3356 user when cached-routers doesn't exist.
3357 - Warn the user when mmap() [or its equivalent] fails for some reason
3358 other than file-not-found.
3359 - Don't warn the user when cached-routers.new doesn't exist: that's
3360 perfectly fine when starting up for the first time.
3361 - When EntryNodes are configured, rebuild the guard list to contain,
3362 in order: the EntryNodes that were guards before; the rest of the
3363 EntryNodes; the nodes that were guards before.
3364 - Mask out all signals in sub-threads; only the libevent signal
3365 handler should be processing them. This should prevent some crashes
3366 on some machines using pthreads. (Patch from coderman.)
3367 - Fix switched arguments on memset in the implementation of
3368 tor_munmap() for systems with no mmap() call.
3369 - When Tor receives a router descriptor that it asked for, but
3370 no longer wants (because it has received fresh networkstatuses
3371 in the meantime), do not warn the user. Cache the descriptor if
3372 we're a cache; drop it if we aren't.
3373 - Make earlier entry guards _really_ get retried when the network
3375 - On a malformed DNS reply, always give an error to the corresponding
3377 - Build with recent libevents on platforms that do not define the
3378 nonstandard types "u_int8_t" and friends.
3380 o Minor features (controller):
3381 - Warn the user when an application uses the obsolete binary v0
3382 control protocol. We're planning to remove support for it during
3383 the next development series, so it's good to give people some
3385 - Add STREAM_BW events to report per-entry-stream bandwidth
3386 use. (Patch from Robert Hogan.)
3387 - Rate-limit SIGNEWNYM signals in response to controllers that
3388 impolitely generate them for every single stream. (Patch from
3389 mwenge; closes bug 394.)
3390 - Make REMAP stream events have a SOURCE (cache or exit), and
3391 make them generated in every case where we get a successful
3392 connected or resolved cell.
3394 o Minor bugfixes (performance):
3395 - Call router_have_min_dir_info half as often. (This is showing up in
3396 some profiles, but not others.)
3397 - When using GCC, make log_debug never get called at all, and its
3398 arguments never get evaluated, when no debug logs are configured.
3399 (This is showing up in some profiles, but not others.)
3402 - Remove some never-implemented options. Mark PathlenCoinWeight as
3404 - Implement proposal 106: Stop requiring clients to have well-formed
3405 certificates; stop checking nicknames in certificates. (Clients
3406 have certificates so that they can look like Tor servers, but in
3407 the future we might want to allow them to look like regular TLS
3408 clients instead. Nicknames in certificates serve no purpose other
3409 than making our protocol easier to recognize on the wire.)
3410 - Revise messages on handshake failure again to be even more clear about
3411 which are incoming connections and which are outgoing.
3412 - Discard any v1 directory info that's over 1 month old (for
3413 directories) or over 1 week old (for running-routers lists).
3414 - Do not warn when individual nodes in the configuration's EntryNodes,
3415 ExitNodes, etc are down: warn only when all possible nodes
3416 are down. (Fixes bug 348.)
3417 - Always remove expired routers and networkstatus docs before checking
3418 whether we have enough information to build circuits. (Fixes
3420 - Put a lower-bound on MaxAdvertisedBandwidth.
3423 Changes in version 0.1.2.7-alpha - 2007-02-06
3424 o Major bugfixes (rate limiting):
3425 - Servers decline directory requests much more aggressively when
3426 they're low on bandwidth. Otherwise they end up queueing more and
3427 more directory responses, which can't be good for latency.
3428 - But never refuse directory requests from local addresses.
3429 - Fix a memory leak when sending a 503 response for a networkstatus
3431 - Be willing to read or write on local connections (e.g. controller
3432 connections) even when the global rate limiting buckets are empty.
3433 - If our system clock jumps back in time, don't publish a negative
3434 uptime in the descriptor. Also, don't let the global rate limiting
3435 buckets go absurdly negative.
3436 - Flush local controller connection buffers periodically as we're
3437 writing to them, so we avoid queueing 4+ megabytes of data before
3440 o Major bugfixes (NT services):
3441 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
3442 command-line flag so that admins can override the default by saying
3443 "tor --service install --user "SomeUser"". This will not affect
3444 existing installed services. Also, warn the user that the service
3445 will look for its configuration file in the service user's
3446 %appdata% directory. (We can't do the 'hardwire the user's appdata
3447 directory' trick any more, since we may not have read access to that
3450 o Major bugfixes (other):
3451 - Previously, we would cache up to 16 old networkstatus documents
3452 indefinitely, if they came from nontrusted authorities. Now we
3453 discard them if they are more than 10 days old.
3454 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
3456 - Detect and reject malformed DNS responses containing circular
3458 - If exits are rare enough that we're not marking exits as guards,
3459 ignore exit bandwidth when we're deciding the required bandwidth
3461 - When we're handling a directory connection tunneled over Tor,
3462 don't fill up internal memory buffers with all the data we want
3463 to tunnel; instead, only add it if the OR connection that will
3464 eventually receive it has some room for it. (This can lead to
3465 slowdowns in tunneled dir connections; a better solution will have
3468 o Minor bugfixes (dns):
3469 - Add some defensive programming to eventdns.c in an attempt to catch
3470 possible memory-stomping bugs.
3471 - Detect and reject DNS replies containing IPv4 or IPv6 records with
3472 an incorrect number of bytes. (Previously, we would ignore the
3474 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
3475 in the correct order, and doesn't crash.
3476 - Free memory held in recently-completed DNS lookup attempts on exit.
3477 This was not a memory leak, but may have been hiding memory leaks.
3478 - Handle TTL values correctly on reverse DNS lookups.
3479 - Treat failure to parse resolv.conf as an error.
3481 o Minor bugfixes (other):
3482 - Fix crash with "tor --list-fingerprint" (reported by seeess).
3483 - When computing clock skew from directory HTTP headers, consider what
3484 time it was when we finished asking for the directory, not what
3486 - Expire socks connections if they spend too long waiting for the
3487 handshake to finish. Previously we would let them sit around for
3488 days, if the connecting application didn't close them either.
3489 - And if the socks handshake hasn't started, don't send a
3490 "DNS resolve socks failed" handshake reply; just close it.
3491 - Stop using C functions that OpenBSD's linker doesn't like.
3492 - Don't launch requests for descriptors unless we have networkstatuses
3493 from at least half of the authorities. This delays the first
3494 download slightly under pathological circumstances, but can prevent
3495 us from downloading a bunch of descriptors we don't need.
3496 - Do not log IPs with TLS failures for incoming TLS
3497 connections. (Fixes bug 382.)
3498 - If the user asks to use invalid exit nodes, be willing to use
3500 - Stop using the reserved ac_cv namespace in our configure script.
3501 - Call stat() slightly less often; use fstat() when possible.
3502 - Refactor the way we handle pending circuits when an OR connection
3503 completes or fails, in an attempt to fix a rare crash bug.
3504 - Only rewrite a conn's address based on X-Forwarded-For: headers
3505 if it's a parseable public IP address; and stop adding extra quotes
3506 to the resulting address.
3509 - Weight directory requests by advertised bandwidth. Now we can
3510 let servers enable write limiting but still allow most clients to
3511 succeed at their directory requests. (We still ignore weights when
3512 choosing a directory authority; I hope this is a feature.)
3515 - Create a new file ReleaseNotes which was the old ChangeLog. The
3516 new ChangeLog file now includes the summaries for all development
3518 - Check for addresses with invalid characters at the exit as well
3519 as at the client, and warn less verbosely when they fail. You can
3520 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
3521 - Adapt a patch from goodell to let the contrib/exitlist script
3522 take arguments rather than require direct editing.
3523 - Inform the server operator when we decide not to advertise a
3524 DirPort due to AccountingMax enabled or a low BandwidthRate. It
3525 was confusing Zax, so now we're hopefully more helpful.
3526 - Bring us one step closer to being able to establish an encrypted
3527 directory tunnel without knowing a descriptor first. Still not
3528 ready yet. As part of the change, now assume we can use a
3529 create_fast cell if we don't know anything about a router.
3530 - Allow exit nodes to use nameservers running on ports other than 53.
3531 - Servers now cache reverse DNS replies.
3532 - Add an --ignore-missing-torrc command-line option so that we can
3533 get the "use sensible defaults if the configuration file doesn't
3534 exist" behavior even when specifying a torrc location on the command
3537 o Minor features (controller):
3538 - Track reasons for OR connection failure; make these reasons
3539 available via the controller interface. (Patch from Mike Perry.)
3540 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
3541 can learn when clients are sending malformed hostnames to Tor.
3542 - Clean up documentation for controller status events.
3543 - Add a REMAP status to stream events to note that a stream's
3544 address has changed because of a cached address or a MapAddress
3548 Changes in version 0.1.2.6-alpha - 2007-01-09
3550 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
3551 connection handles more than 4 gigs in either direction, we crash.
3552 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
3553 advertised exit node, somebody might try to exit from us when
3554 we're bootstrapping and before we've built our descriptor yet.
3555 Refuse the connection rather than crashing.
3558 - Warn if we (as a server) find that we've resolved an address that we
3559 weren't planning to resolve.
3560 - Warn that using select() on any libevent version before 1.1 will be
3561 unnecessarily slow (even for select()).
3562 - Flush ERR-level controller status events just like we currently
3563 flush ERR-level log events, so that a Tor shutdown doesn't prevent
3564 the controller from learning about current events.
3566 o Minor features (more controller status events):
3567 - Implement EXTERNAL_ADDRESS server status event so controllers can
3568 learn when our address changes.
3569 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
3570 can learn when directories reject our descriptor.
3571 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
3572 can learn when a client application is speaking a non-socks protocol
3574 - Implement DANGEROUS_SOCKS client status event so controllers
3575 can learn when a client application is leaking DNS addresses.
3576 - Implement BUG general status event so controllers can learn when
3577 Tor is unhappy about its internal invariants.
3578 - Implement CLOCK_SKEW general status event so controllers can learn
3579 when Tor thinks the system clock is set incorrectly.
3580 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
3581 server status events so controllers can learn when their descriptors
3582 are accepted by a directory.
3583 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
3584 server status events so controllers can learn about Tor's progress in
3585 deciding whether it's reachable from the outside.
3586 - Implement BAD_LIBEVENT general status event so controllers can learn
3587 when we have a version/method combination in libevent that needs to
3589 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
3590 and DNS_USELESS server status events so controllers can learn
3591 about changes to DNS server status.
3593 o Minor features (directory):
3594 - Authorities no longer recommend exits as guards if this would shift
3595 too much load to the exit nodes.
3598 Changes in version 0.1.2.5-alpha - 2007-01-06
3600 - Enable write limiting as well as read limiting. Now we sacrifice
3601 capacity if we're pushing out lots of directory traffic, rather
3602 than overrunning the user's intended bandwidth limits.
3603 - Include TLS overhead when counting bandwidth usage; previously, we
3604 would count only the bytes sent over TLS, but not the bytes used
3606 - Support running the Tor service with a torrc not in the same
3607 directory as tor.exe and default to using the torrc located in
3608 the %appdata%\Tor\ of the user who installed the service. Patch
3610 - Servers now check for the case when common DNS requests are going to
3611 wildcarded addresses (i.e. all getting the same answer), and change
3612 their exit policy to reject *:* if it's happening.
3613 - Implement BEGIN_DIR cells, so we can connect to the directory
3614 server via TLS to do encrypted directory requests rather than
3615 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
3616 config options if you like.
3618 o Minor features (config and docs):
3619 - Start using the state file to store bandwidth accounting data:
3620 the bw_accounting file is now obsolete. We'll keep generating it
3621 for a while for people who are still using 0.1.2.4-alpha.
3622 - Try to batch changes to the state file so that we do as few
3623 disk writes as possible while still storing important things in
3625 - The state file and the bw_accounting file get saved less often when
3626 the AvoidDiskWrites config option is set.
3627 - Make PIDFile work on Windows (untested).
3628 - Add internal descriptions for a bunch of configuration options:
3629 accessible via controller interface and in comments in saved
3631 - Reject *:563 (NNTPS) in the default exit policy. We already reject
3632 NNTP by default, so this seems like a sensible addition.
3633 - Clients now reject hostnames with invalid characters. This should
3634 avoid some inadvertent info leaks. Add an option
3635 AllowNonRFC953Hostnames to disable this behavior, in case somebody
3636 is running a private network with hosts called @, !, and #.
3637 - Add a maintainer script to tell us which options are missing
3638 documentation: "make check-docs".
3639 - Add a new address-spec.txt document to describe our special-case
3640 addresses: .exit, .onion, and .noconnnect.
3642 o Minor features (DNS):
3643 - Ongoing work on eventdns infrastructure: now it has dns server
3644 and ipv6 support. One day Tor will make use of it.
3645 - Add client-side caching for reverse DNS lookups.
3646 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
3647 - When we change nameservers or IP addresses, reset and re-launch
3648 our tests for DNS hijacking.
3650 o Minor features (directory):
3651 - Authorities now specify server versions in networkstatus. This adds
3652 about 2% to the size of compressed networkstatus docs, and allows
3653 clients to tell which servers support BEGIN_DIR and which don't.
3654 The implementation is forward-compatible with a proposed future
3655 protocol version scheme not tied to Tor versions.
3656 - DirServer configuration lines now have an orport= option so
3657 clients can open encrypted tunnels to the authorities without
3658 having downloaded their descriptors yet. Enabled for moria1,
3659 moria2, tor26, and lefkada now in the default configuration.
3660 - Directory servers are more willing to send a 503 "busy" if they
3661 are near their write limit, especially for v1 directory requests.
3662 Now they can use their limited bandwidth for actual Tor traffic.
3663 - Clients track responses with status 503 from dirservers. After a
3664 dirserver has given us a 503, we try not to use it until an hour has
3665 gone by, or until we have no dirservers that haven't given us a 503.
3666 - When we get a 503 from a directory, and we're not a server, we don't
3667 count the failure against the total number of failures allowed
3668 for the thing we're trying to download.
3669 - Report X-Your-Address-Is correctly from tunneled directory
3670 connections; don't report X-Your-Address-Is when it's an internal
3671 address; and never believe reported remote addresses when they're
3673 - Protect against an unlikely DoS attack on directory servers.
3674 - Add a BadDirectory flag to network status docs so that authorities
3675 can (eventually) tell clients about caches they believe to be
3678 o Minor features (controller):
3679 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
3680 - Reimplement GETINFO so that info/names stays in sync with the
3682 - Implement "GETINFO fingerprint".
3683 - Implement "SETEVENTS GUARD" so controllers can get updates on
3684 entry guard status as it changes.
3686 o Minor features (clean up obsolete pieces):
3687 - Remove some options that have been deprecated since at least
3688 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
3689 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
3691 - We no longer look for identity and onion keys in "identity.key" and
3692 "onion.key" -- these were replaced by secret_id_key and
3693 secret_onion_key in 0.0.8pre1.
3694 - We no longer require unrecognized directory entries to be
3697 o Major bugfixes (security):
3698 - Stop sending the HttpProxyAuthenticator string to directory
3699 servers when directory connections are tunnelled through Tor.
3700 - Clients no longer store bandwidth history in the state file.
3701 - Do not log introduction points for hidden services if SafeLogging
3703 - When generating bandwidth history, round down to the nearest
3704 1k. When storing accounting data, round up to the nearest 1k.
3705 - When we're running as a server, remember when we last rotated onion
3706 keys, so that we will rotate keys once they're a week old even if
3707 we never stay up for a week ourselves.
3709 o Major bugfixes (other):
3710 - Fix a longstanding bug in eventdns that prevented the count of
3711 timed-out resolves from ever being reset. This bug caused us to
3712 give up on a nameserver the third time it timed out, and try it
3713 10 seconds later... and to give up on it every time it timed out
3715 - Take out the '5 second' timeout from the connection retry
3716 schedule. Now the first connect attempt will wait a full 10
3717 seconds before switching to a new circuit. Perhaps this will help
3718 a lot. Based on observations from Mike Perry.
3719 - Fix a bug on the Windows implementation of tor_mmap_file() that
3720 would prevent the cached-routers file from ever loading. Reported
3724 - Fix an assert failure when a directory authority sets
3725 AuthDirRejectUnlisted and then receives a descriptor from an
3726 unlisted router. Reported by seeess.
3727 - Avoid a double-free when parsing malformed DirServer lines.
3728 - Fix a bug when a BSD-style PF socket is first used. Patch from
3730 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
3731 to resolve an address at a given exit node even when they ask for
3733 - Servers no longer ever list themselves in their "family" line,
3734 even if configured to do so. This makes it easier to configure
3735 family lists conveniently.
3736 - When running as a server, don't fall back to 127.0.0.1 when no
3737 nameservers are configured in /etc/resolv.conf; instead, make the
3738 user fix resolv.conf or specify nameservers explicitly. (Resolves
3740 - Stop accepting certain malformed ports in configured exit policies.
3741 - Don't re-write the fingerprint file every restart, unless it has
3743 - Stop warning when a single nameserver fails: only warn when _all_ of
3744 our nameservers have failed. Also, when we only have one nameserver,
3745 raise the threshold for deciding that the nameserver is dead.
3746 - Directory authorities now only decide that routers are reachable
3747 if their identity keys are as expected.
3748 - When the user uses bad syntax in the Log config line, stop
3749 suggesting other bad syntax as a replacement.
3750 - Correctly detect ipv6 DNS capability on OpenBSD.
3752 o Minor bugfixes (controller):
3753 - Report the circuit number correctly in STREAM CLOSED events. Bug
3754 reported by Mike Perry.
3755 - Do not report bizarre values for results of accounting GETINFOs
3756 when the last second's write or read exceeds the allotted bandwidth.
3757 - Report "unrecognized key" rather than an empty string when the
3758 controller tries to fetch a networkstatus that doesn't exist.
3761 Changes in version 0.1.1.26 - 2006-12-14
3762 o Security bugfixes:
3763 - Stop sending the HttpProxyAuthenticator string to directory
3764 servers when directory connections are tunnelled through Tor.
3765 - Clients no longer store bandwidth history in the state file.
3766 - Do not log introduction points for hidden services if SafeLogging
3770 - Fix an assert failure when a directory authority sets
3771 AuthDirRejectUnlisted and then receives a descriptor from an
3772 unlisted router (reported by seeess).
3775 Changes in version 0.1.2.4-alpha - 2006-12-03
3777 - Add support for using natd; this allows FreeBSDs earlier than
3778 5.1.2 to have ipfw send connections through Tor without using
3779 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
3782 - Make all connections to addresses of the form ".noconnect"
3783 immediately get closed. This lets application/controller combos
3784 successfully test whether they're talking to the same Tor by
3785 watching for STREAM events.
3786 - Make cross.sh cross-compilation script work even when autogen.sh
3787 hasn't been run. (Patch from Michael Mohr.)
3788 - Statistics dumped by -USR2 now include a breakdown of public key
3789 operations, for profiling.
3792 - Fix a major leak when directory authorities parse their
3793 approved-routers list, a minor memory leak when we fail to pick
3794 an exit node, and a few rare leaks on errors.
3795 - Handle TransPort connections even when the server sends data before
3796 the client sends data. Previously, the connection would just hang
3797 until the client sent data. (Patch from tup based on patch from
3799 - Avoid assert failure when our cached-routers file is empty on
3803 - Don't log spurious warnings when we see a circuit close reason we
3804 don't recognize; it's probably just from a newer version of Tor.
3805 - Have directory authorities allow larger amounts of drift in uptime
3806 without replacing the server descriptor: previously, a server that
3807 restarted every 30 minutes could have 48 "interesting" descriptors
3809 - Start linking to the Tor specification and Tor reference manual
3810 correctly in the Windows installer.
3811 - Add Vidalia to the OS X uninstaller script, so when we uninstall
3812 Tor/Privoxy we also uninstall Vidalia.
3813 - Resume building on Irix64, and fix a lot of warnings from its
3815 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
3816 when we're running as a client.
3819 Changes in version 0.1.1.25 - 2006-11-04
3821 - When a client asks us to resolve (rather than connect to)
3822 an address, and we have a cached answer, give them the cached
3823 answer. Previously, we would give them no answer at all.
3824 - We were building exactly the wrong circuits when we predict
3825 hidden service requirements, meaning Tor would have to build all
3826 its circuits on demand.
3827 - If none of our live entry guards have a high uptime, but we
3828 require a guard with a high uptime, try adding a new guard before
3829 we give up on the requirement. This patch should make long-lived
3830 connections more stable on average.
3831 - When testing reachability of our DirPort, don't launch new
3832 tests when there's already one in progress -- unreachable
3833 servers were stacking up dozens of testing streams.
3835 o Security bugfixes:
3836 - When the user sends a NEWNYM signal, clear the client-side DNS
3837 cache too. Otherwise we continue to act on previous information.
3840 - Avoid a memory corruption bug when creating a hash table for
3842 - Avoid possibility of controller-triggered crash when misusing
3843 certain commands from a v0 controller on platforms that do not
3844 handle printf("%s",NULL) gracefully.
3845 - Avoid infinite loop on unexpected controller input.
3846 - Don't log spurious warnings when we see a circuit close reason we
3847 don't recognize; it's probably just from a newer version of Tor.
3848 - Add Vidalia to the OS X uninstaller script, so when we uninstall
3849 Tor/Privoxy we also uninstall Vidalia.
3852 Changes in version 0.1.2.3-alpha - 2006-10-29
3854 - Prepare for servers to publish descriptors less often: never
3855 discard a descriptor simply for being too old until either it is
3856 recommended by no authorities, or until we get a better one for
3857 the same router. Make caches consider retaining old recommended
3858 routers for even longer.
3859 - If most authorities set a BadExit flag for a server, clients
3860 don't think of it as a general-purpose exit. Clients only consider
3861 authorities that advertise themselves as listing bad exits.
3862 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
3863 headers for content, so that we can work better in the presence of
3864 caching HTTP proxies.
3865 - Allow authorities to list nodes as bad exits by fingerprint or by
3868 o Minor features, controller:
3869 - Add a REASON field to CIRC events; for backward compatibility, this
3870 field is sent only to controllers that have enabled the extended
3871 event format. Also, add additional reason codes to explain why
3872 a given circuit has been destroyed or truncated. (Patches from
3874 - Add a REMOTE_REASON field to extended CIRC events to tell the
3875 controller about why a remote OR told us to close a circuit.
3876 - Stream events also now have REASON and REMOTE_REASON fields,
3877 working much like those for circuit events.
3878 - There's now a GETINFO ns/... field so that controllers can ask Tor
3879 about the current status of a router.
3880 - A new event type "NS" to inform a controller when our opinion of
3881 a router's status has changed.
3882 - Add a GETINFO events/names and GETINFO features/names so controllers
3883 can tell which events and features are supported.
3884 - A new CLEARDNSCACHE signal to allow controllers to clear the
3885 client-side DNS cache without expiring circuits.
3887 o Security bugfixes:
3888 - When the user sends a NEWNYM signal, clear the client-side DNS
3889 cache too. Otherwise we continue to act on previous information.
3892 - Avoid sending junk to controllers or segfaulting when a controller
3893 uses EVENT_NEW_DESC with verbose nicknames.
3894 - Stop triggering asserts if the controller tries to extend hidden
3895 service circuits (reported by mwenge).
3896 - Avoid infinite loop on unexpected controller input.
3897 - When the controller does a "GETINFO network-status", tell it
3898 about even those routers whose descriptors are very old, and use
3899 long nicknames where appropriate.
3900 - Change NT service functions to be loaded on demand. This lets us
3901 build with MinGW without breaking Tor for Windows 98 users.
3902 - Do DirPort reachability tests less often, since a single test
3903 chews through many circuits before giving up.
3904 - In the hidden service example in torrc.sample, stop recommending
3905 esoteric and discouraged hidden service options.
3906 - When stopping an NT service, wait up to 10 sec for it to actually
3907 stop. (Patch from Matt Edman; resolves bug 295.)
3908 - Fix handling of verbose nicknames with ORCONN controller events:
3909 make them show up exactly when requested, rather than exactly when
3911 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
3912 printing a duplicate "$" in the keys we send (reported by mwenge).
3913 - Correctly set maximum connection limit on Cygwin. (This time
3915 - Try to detect Windows correctly when cross-compiling.
3916 - Detect the size of the routers file correctly even if it is
3917 corrupted (on systems without mmap) or not page-aligned (on systems
3918 with mmap). This bug was harmless.
3919 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
3920 to open a stream fails; now we do in more cases. This should
3921 make clients able to find a good exit faster in some cases, since
3922 unhandleable requests will now get an error rather than timing out.
3923 - Resolve two memory leaks when rebuilding the on-disk router cache
3924 (reported by fookoowa).
3925 - Clean up minor code warnings suggested by the MIPSpro C compiler,
3926 and reported by some Centos users.
3927 - Controller signals now work on non-Unix platforms that don't define
3928 SIGUSR1 and SIGUSR2 the way we expect.
3929 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
3930 values before failing, and always enables eventdns.
3931 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
3932 Try to fix this in configure.in by checking for most functions
3933 before we check for libevent.
3936 Changes in version 0.1.2.2-alpha - 2006-10-07
3938 - Make our async eventdns library on-by-default for Tor servers,
3939 and plan to deprecate the separate dnsworker threads.
3940 - Add server-side support for "reverse" DNS lookups (using PTR
3941 records so clients can determine the canonical hostname for a given
3942 IPv4 address). Only supported by servers using eventdns; servers
3943 now announce in their descriptors whether they support eventdns.
3944 - Specify and implement client-side SOCKS5 interface for reverse DNS
3945 lookups (see doc/socks-extensions.txt).
3946 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
3947 connect to directory servers through Tor. Previously, clients needed
3948 to find Tor exits to make private connections to directory servers.
3949 - Avoid choosing Exit nodes for entry or middle hops when the
3950 total bandwidth available from non-Exit nodes is much higher than
3951 the total bandwidth available from Exit nodes.
3952 - Workaround for name servers (like Earthlink's) that hijack failing
3953 DNS requests and replace the no-such-server answer with a "helpful"
3954 redirect to an advertising-driven search portal. Also work around
3955 DNS hijackers who "helpfully" decline to hijack known-invalid
3956 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
3957 lets you turn it off.
3958 - Send out a burst of long-range padding cells once we've established
3959 that we're reachable. Spread them over 4 circuits, so hopefully
3960 a few will be fast. This exercises our bandwidth and bootstraps
3961 us into the directory more quickly.
3963 o New/improved config options:
3964 - Add new config option "ResolvConf" to let the server operator
3965 choose an alternate resolve.conf file when using eventdns.
3966 - Add an "EnforceDistinctSubnets" option to control our "exclude
3967 servers on the same /16" behavior. It's still on by default; this
3968 is mostly for people who want to operate private test networks with
3969 all the machines on the same subnet.
3970 - If one of our entry guards is on the ExcludeNodes list, or the
3971 directory authorities don't think it's a good guard, treat it as
3972 if it were unlisted: stop using it as a guard, and throw it off
3973 the guards list if it stays that way for a long time.
3974 - Allow directory authorities to be marked separately as authorities
3975 for the v1 directory protocol, the v2 directory protocol, and
3976 as hidden service directories, to make it easier to retire old
3977 authorities. V1 authorities should set "HSAuthoritativeDir 1"
3978 to continue being hidden service authorities too.
3979 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
3981 o Minor features, controller:
3982 - Fix CIRC controller events so that controllers can learn the
3983 identity digests of non-Named servers used in circuit paths.
3984 - Let controllers ask for more useful identifiers for servers. Instead
3985 of learning identity digests for un-Named servers and nicknames
3986 for Named servers, the new identifiers include digest, nickname,
3987 and indication of Named status. Off by default; see control-spec.txt
3988 for more information.
3989 - Add a "getinfo address" controller command so it can display Tor's
3990 best guess to the user.
3991 - New controller event to alert the controller when our server
3992 descriptor has changed.
3993 - Give more meaningful errors on controller authentication failure.
3995 o Minor features, other:
3996 - When asked to resolve a hostname, don't use non-exit servers unless
3997 requested to do so. This allows servers with broken DNS to be
3998 useful to the network.
3999 - Divide eventdns log messages into warn and info messages.
4000 - Reserve the nickname "Unnamed" for routers that can't pick
4001 a hostname: any router can call itself Unnamed; directory
4002 authorities will never allocate Unnamed to any particular router;
4003 clients won't believe that any router is the canonical Unnamed.
4004 - Only include function names in log messages for info/debug messages.
4005 For notice/warn/err, the content of the message should be clear on
4006 its own, and printing the function name only confuses users.
4007 - Avoid some false positives during reachability testing: don't try
4008 to test via a server that's on the same /24 as us.
4009 - If we fail to build a circuit to an intended enclave, and it's
4010 not mandatory that we use that enclave, stop wanting it.
4011 - When eventdns is enabled, allow multithreaded builds on NetBSD and
4012 OpenBSD. (We had previously disabled threads on these platforms
4013 because they didn't have working thread-safe resolver functions.)
4015 o Major bugfixes, anonymity/security:
4016 - If a client asked for a server by name, and there's a named server
4017 in our network-status but we don't have its descriptor yet, we
4018 could return an unnamed server instead.
4019 - Fix NetBSD bug that could allow someone to force uninitialized RAM
4020 to be sent to a server's DNS resolver. This only affects NetBSD
4021 and other platforms that do not bounds-check tolower().
4022 - Reject (most) attempts to use Tor circuits with length one. (If
4023 many people start using Tor as a one-hop proxy, exit nodes become
4024 a more attractive target for compromise.)
4025 - Just because your DirPort is open doesn't mean people should be
4026 able to remotely teach you about hidden service descriptors. Now
4027 only accept rendezvous posts if you've got HSAuthoritativeDir set.
4029 o Major bugfixes, other:
4030 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
4031 - When a client asks the server to resolve (not connect to)
4032 an address, and it has a cached answer, give them the cached answer.
4033 Previously, the server would give them no answer at all.
4034 - Allow really slow clients to not hang up five minutes into their
4035 directory downloads (suggested by Adam J. Richter).
4036 - We were building exactly the wrong circuits when we anticipated
4037 hidden service requirements, meaning Tor would have to build all
4038 its circuits on demand.
4039 - Avoid crashing when we mmap a router cache file of size 0.
4040 - When testing reachability of our DirPort, don't launch new
4041 tests when there's already one in progress -- unreachable
4042 servers were stacking up dozens of testing streams.
4044 o Minor bugfixes, correctness:
4045 - If we're a directory mirror and we ask for "all" network status
4046 documents, we would discard status documents from authorities
4048 - Avoid a memory corruption bug when creating a hash table for
4050 - Avoid controller-triggered crash when misusing certain commands
4051 from a v0 controller on platforms that do not handle
4052 printf("%s",NULL) gracefully.
4053 - Don't crash when a controller sends a third argument to an
4054 "extendcircuit" request.
4055 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
4056 response; fix error code when "getinfo dir/status/" fails.
4057 - Avoid crash when telling controller stream-status and a stream
4059 - Patch from Adam Langley to fix assert() in eventdns.c.
4060 - Fix a debug log message in eventdns to say "X resolved to Y"
4061 instead of "X resolved to X".
4062 - Make eventdns give strings for DNS errors, not just error numbers.
4063 - Track unreachable entry guards correctly: don't conflate
4064 'unreachable by us right now' with 'listed as down by the directory
4065 authorities'. With the old code, if a guard was unreachable by
4066 us but listed as running, it would clog our guard list forever.
4067 - Behave correctly in case we ever have a network with more than
4068 2GB/s total advertised capacity.
4069 - Make TrackExitHosts case-insensitive, and fix the behavior of
4070 ".suffix" TrackExitHosts items to avoid matching in the middle of
4072 - Finally fix the openssl warnings from newer gccs that believe that
4073 ignoring a return value is okay, but casting a return value and
4074 then ignoring it is a sign of madness.
4075 - Prevent the contrib/exitlist script from printing the same
4076 result more than once.
4077 - Patch from Steve Hildrey: Generate network status correctly on
4078 non-versioning dirservers.
4079 - Don't listen to the X-Your-Address-Is hint if you did the lookup
4080 via Tor; otherwise you'll think you're the exit node's IP address.
4082 o Minor bugfixes, performance:
4083 - Two small performance improvements on parsing descriptors.
4084 - Major performance improvement on inserting descriptors: change
4085 algorithm from O(n^2) to O(n).
4086 - Make the common memory allocation path faster on machines where
4087 malloc(0) returns a pointer.
4088 - Start remembering X-Your-Address-Is directory hints even if you're
4089 a client, so you can become a server more smoothly.
4090 - Avoid duplicate entries on MyFamily line in server descriptor.
4092 o Packaging, features:
4093 - Remove architecture from OS X builds. The official builds are
4094 now universal binaries.
4095 - The Debian package now uses --verify-config when (re)starting,
4096 to distinguish configuration errors from other errors.
4097 - Update RPMs to require libevent 1.1b.
4099 o Packaging, bugfixes:
4100 - Patches so Tor builds with MinGW on Windows.
4101 - Patches so Tor might run on Cygwin again.
4102 - Resume building on non-gcc compilers and ancient gcc. Resume
4103 building with the -O0 compile flag. Resume building cleanly on
4105 - Run correctly on OS X platforms with case-sensitive filesystems.
4106 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
4107 - Add autoconf checks so Tor can build on Solaris x86 again.
4110 - Documented (and renamed) ServerDNSSearchDomains and
4111 ServerDNSResolvConfFile options.
4112 - Be clearer that the *ListenAddress directives can be repeated
4116 Changes in version 0.1.1.24 - 2006-09-29
4118 - Allow really slow clients to not hang up five minutes into their
4119 directory downloads (suggested by Adam J. Richter).
4120 - Fix major performance regression from 0.1.0.x: instead of checking
4121 whether we have enough directory information every time we want to
4122 do something, only check when the directory information has changed.
4123 This should improve client CPU usage by 25-50%.
4124 - Don't crash if, after a server has been running for a while,
4125 it can't resolve its hostname.
4128 - Allow Tor to start when RunAsDaemon is set but no logs are set.
4129 - Don't crash when the controller receives a third argument to an
4130 "extendcircuit" request.
4131 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
4132 response; fix error code when "getinfo dir/status/" fails.
4133 - Fix configure.in to not produce broken configure files with
4134 more recent versions of autoconf. Thanks to Clint for his auto*
4136 - Fix security bug on NetBSD that could allow someone to force
4137 uninitialized RAM to be sent to a server's DNS resolver. This
4138 only affects NetBSD and other platforms that do not bounds-check
4140 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
4141 methods: these are known to be buggy.
4142 - If we're a directory mirror and we ask for "all" network status
4143 documents, we would discard status documents from authorities
4147 Changes in version 0.1.2.1-alpha - 2006-08-27
4149 - Add "eventdns" async dns library from Adam Langley, tweaked to
4150 build on OSX and Windows. Only enabled if you pass the
4151 --enable-eventdns argument to configure.
4152 - Allow servers with no hostname or IP address to learn their
4153 IP address by asking the directory authorities. This code only
4154 kicks in when you would normally have exited with a "no address"
4155 error. Nothing's authenticated, so use with care.
4156 - Rather than waiting a fixed amount of time between retrying
4157 application connections, we wait only 5 seconds for the first,
4158 10 seconds for the second, and 15 seconds for each retry after
4159 that. Hopefully this will improve the expected user experience.
4160 - Patch from Tup to add support for transparent AP connections:
4161 this basically bundles the functionality of trans-proxy-tor
4162 into the Tor mainline. Now hosts with compliant pf/netfilter
4163 implementations can redirect TCP connections straight to Tor
4164 without diverting through SOCKS. Needs docs.
4165 - Busy directory servers save lots of memory by spooling server
4166 descriptors, v1 directories, and v2 networkstatus docs to buffers
4167 as needed rather than en masse. Also mmap the cached-routers
4168 files, so we don't need to keep the whole thing in memory too.
4169 - Automatically avoid picking more than one node from the same
4170 /16 network when constructing a circuit.
4171 - Revise and clean up the torrc.sample that we ship with; add
4172 a section for BandwidthRate and BandwidthBurst.
4175 - Split circuit_t into origin_circuit_t and or_circuit_t, and
4176 split connection_t into edge, or, dir, control, and base structs.
4177 These will save quite a bit of memory on busy servers, and they'll
4178 also help us track down bugs in the code and bugs in the spec.
4179 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
4180 or later. Log when we are doing this, so we can diagnose it when
4181 it fails. (Also, recommend libevent 1.1b for kqueue and
4182 win32 methods; deprecate libevent 1.0b harder; make libevent
4183 recommendation system saner.)
4184 - Start being able to build universal binaries on OS X (thanks
4186 - Export the default exit policy via the control port, so controllers
4187 don't need to guess what it is / will be later.
4188 - Add a man page entry for ProtocolWarnings.
4189 - Add TestVia config option to the man page.
4190 - Remove even more protocol-related warnings from Tor server logs,
4191 such as bad TLS handshakes and malformed begin cells.
4192 - Stop fetching descriptors if you're not a dir mirror and you
4193 haven't tried to establish any circuits lately. [This currently
4194 causes some dangerous behavior, because when you start up again
4195 you'll use your ancient server descriptors.]
4196 - New DirPort behavior: if you have your dirport set, you download
4197 descriptors aggressively like a directory mirror, whether or not
4199 - Get rid of the router_retry_connections notion. Now routers
4200 no longer try to rebuild long-term connections to directory
4201 authorities, and directory authorities no longer try to rebuild
4202 long-term connections to all servers. We still don't hang up
4203 connections in these two cases though -- we need to look at it
4204 more carefully to avoid flapping, and we likely need to wait til
4205 0.1.1.x is obsolete.
4206 - Drop compatibility with obsolete Tors that permit create cells
4207 to have the wrong circ_id_type.
4208 - Re-enable per-connection rate limiting. Get rid of the "OP
4209 bandwidth" concept. Lay groundwork for "bandwidth classes" --
4210 separate global buckets that apply depending on what sort of conn
4212 - Start publishing one minute or so after we find our ORPort
4213 to be reachable. This will help reduce the number of descriptors
4214 we have for ourselves floating around, since it's quite likely
4215 other things (e.g. DirPort) will change during that minute too.
4216 - Fork the v1 directory protocol into its own spec document,
4217 and mark dir-spec.txt as the currently correct (v2) spec.
4220 - When we find our DirPort to be reachable, publish a new descriptor
4221 so we'll tell the world (reported by pnx).
4222 - Publish a new descriptor after we hup/reload. This is important
4223 if our config has changed such that we'll want to start advertising
4224 our DirPort now, etc.
4225 - Allow Tor to start when RunAsDaemon is set but no logs are set.
4226 - When we have a state file we cannot parse, tell the user and
4227 move it aside. Now we avoid situations where the user starts
4228 Tor in 1904, Tor writes a state file with that timestamp in it,
4229 the user fixes her clock, and Tor refuses to start.
4230 - Fix configure.in to not produce broken configure files with
4231 more recent versions of autoconf. Thanks to Clint for his auto*
4233 - "tor --verify-config" now exits with -1(255) or 0 depending on
4234 whether the config options are bad or good.
4235 - Resolve bug 321 when using dnsworkers: append a period to every
4236 address we resolve at the exit node, so that we do not accidentally
4237 pick up local addresses, and so that failing searches are retried
4238 in the resolver search domains. (This is already solved for
4239 eventdns.) (This breaks Blossom servers for now.)
4240 - If we are using an exit enclave and we can't connect, e.g. because
4241 its webserver is misconfigured to not listen on localhost, then
4242 back off and try connecting from somewhere else before we fail.
4245 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
4246 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
4247 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
4248 when the IP address is mapped through MapAddress to a hostname.
4249 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
4250 useless IPv6 DNS resolves.
4251 - Patch suggested by Karsten Loesing: respond to SIGNAL command
4252 before we execute the signal, in case the signal shuts us down.
4253 - Clean up AllowInvalidNodes man page entry.
4254 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
4255 - Add more asserts to track down an assert error on a windows Tor
4256 server with connection_add being called with socket == -1.
4257 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
4258 - Fix misleading log messages: an entry guard that is "unlisted",
4259 as well as not known to be "down" (because we've never heard
4260 of it), is not therefore "up".
4261 - Remove code to special-case "-cvs" ending, since it has not
4262 actually mattered since 0.0.9.
4263 - Make our socks5 handling more robust to broken socks clients:
4264 throw out everything waiting on the buffer in between socks
4265 handshake phases, since they can't possibly (so the theory
4266 goes) have predicted what we plan to respond to them.
4269 Changes in version 0.1.1.23 - 2006-07-30
4271 - Fast Tor servers, especially exit nodes, were triggering asserts
4272 due to a bug in handling the list of pending DNS resolves. Some
4273 bugs still remain here; we're hunting them.
4274 - Entry guards could crash clients by sending unexpected input.
4275 - More fixes on reachability testing: if you find yourself reachable,
4276 then don't ever make any client requests (so you stop predicting
4277 circuits), then hup or have your clock jump, then later your IP
4278 changes, you won't think circuits are working, so you won't try to
4279 test reachability, so you won't publish.
4282 - Avoid a crash if the controller does a resetconf firewallports
4283 and then a setconf fascistfirewall=1.
4284 - Avoid an integer underflow when the dir authority decides whether
4285 a router is stable: we might wrongly label it stable, and compute
4286 a slightly wrong median stability, when a descriptor is published
4288 - Fix a place where we might trigger an assert if we can't build our
4289 own server descriptor yet.
4292 Changes in version 0.1.1.22 - 2006-07-05
4294 - Fix a big bug that was causing servers to not find themselves
4295 reachable if they changed IP addresses. Since only 0.1.1.22+
4296 servers can do reachability testing correctly, now we automatically
4297 make sure to test via one of these.
4298 - Fix to allow clients and mirrors to learn directory info from
4299 descriptor downloads that get cut off partway through.
4300 - Directory authorities had a bug in deciding if a newly published
4301 descriptor was novel enough to make everybody want a copy -- a few
4302 servers seem to be publishing new descriptors many times a minute.
4304 - Fix a rare bug that was causing some servers to complain about
4305 "closing wedged cpuworkers" and skip some circuit create requests.
4306 - Make the Exit flag in directory status documents actually work.
4309 Changes in version 0.1.1.21 - 2006-06-10
4310 o Crash and assert fixes from 0.1.1.20:
4311 - Fix a rare crash on Tor servers that have enabled hibernation.
4312 - Fix a seg fault on startup for Tor networks that use only one
4313 directory authority.
4314 - Fix an assert from a race condition that occurs on Tor servers
4315 while exiting, where various threads are trying to log that they're
4316 exiting, and delete the logs, at the same time.
4317 - Make our unit tests pass again on certain obscure platforms.
4320 - Add support for building SUSE RPM packages.
4321 - Speed up initial bootstrapping for clients: if we are making our
4322 first ever connection to any entry guard, then don't mark it down
4324 - When only one Tor server in the network is labelled as a guard,
4325 and we've already picked him, we would cycle endlessly picking him
4326 again, being unhappy about it, etc. Now we specifically exclude
4327 current guards when picking a new guard.
4328 - Servers send create cells more reliably after the TLS connection
4329 is established: we were sometimes forgetting to send half of them
4330 when we had more than one pending.
4331 - If we get a create cell that asks us to extend somewhere, but the
4332 Tor server there doesn't match the expected digest, we now send
4333 a destroy cell back, rather than silently doing nothing.
4334 - Make options->RedirectExit work again.
4335 - Make cookie authentication for the controller work again.
4336 - Stop being picky about unusual characters in the arguments to
4337 mapaddress. It's none of our business.
4338 - Add a new config option "TestVia" that lets you specify preferred
4339 middle hops to use for test circuits. Perhaps this will let me
4340 debug the reachability problems better.
4342 o Log / documentation fixes:
4343 - If we're a server and some peer has a broken TLS certificate, don't
4344 log about it unless ProtocolWarnings is set, i.e., we want to hear
4345 about protocol violations by others.
4346 - Fix spelling of VirtualAddrNetwork in man page.
4347 - Add a better explanation at the top of the autogenerated torrc file
4348 about what happened to our old torrc.
4351 Changes in version 0.1.1.20 - 2006-05-23
4353 - Downgrade a log severity where servers complain that they're
4355 - Avoid a compile warning on FreeBSD.
4356 - Remove string size limit on NEWDESC messages; solve bug 291.
4357 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
4358 more thoroughly when we're running on windows.
4361 Changes in version 0.1.1.19-rc - 2006-05-03
4363 - Regenerate our local descriptor if it's dirty and we try to use
4364 it locally (e.g. if it changes during reachability detection).
4365 - If we setconf our ORPort to 0, we continued to listen on the
4366 old ORPort and receive connections.
4367 - Avoid a second warning about machine/limits.h on Debian
4369 - Be willing to add our own routerinfo into the routerlist.
4370 Now authorities will include themselves in their directories
4371 and network-statuses.
4372 - Stop trying to upload rendezvous descriptors to every
4373 directory authority: only try the v1 authorities.
4374 - Servers no longer complain when they think they're not
4375 registered with the directory authorities. There were too many
4377 - Backport dist-rpm changes so rpms can be built without errors.
4380 - Implement an option, VirtualAddrMask, to set which addresses
4381 get handed out in response to mapaddress requests. This works
4382 around a bug in tsocks where 127.0.0.0/8 is never socksified.
4385 Changes in version 0.1.1.18-rc - 2006-04-10
4387 - Work harder to download live network-statuses from all the
4388 directory authorities we know about. Improve the threshold
4389 decision logic so we're more robust to edge cases.
4390 - When fetching rendezvous descriptors, we were willing to ask
4391 v2 authorities too, which would always return 404.
4394 - Stop listing down or invalid nodes in the v1 directory. This will
4395 reduce its bulk by about 1/3, and reduce load on directory
4397 - When deciding whether a router is Fast or Guard-worthy, consider
4398 his advertised BandwidthRate and not just the BandwidthCapacity.
4399 - No longer ship INSTALL and README files -- they are useless now.
4400 - Force rpmbuild to behave and honor target_cpu.
4401 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
4402 - Start to include translated versions of the tor-doc-*.html
4403 files, along with the screenshots. Still needs more work.
4404 - Start sending back 512 and 451 errors if mapaddress fails,
4405 rather than not sending anything back at all.
4406 - When we fail to bind or listen on an incoming or outgoing
4407 socket, we should close it before failing. otherwise we just
4408 leak it. (thanks to weasel for finding.)
4409 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
4410 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
4411 - Make NoPublish (even though deprecated) work again.
4412 - Fix a minor security flaw where a versioning auth dirserver
4413 could list a recommended version many times in a row to make
4414 clients more convinced that it's recommended.
4415 - Fix crash bug if there are two unregistered servers running
4416 with the same nickname, one of them is down, and you ask for
4417 them by nickname in your EntryNodes or ExitNodes. Also, try
4418 to pick the one that's running rather than an arbitrary one.
4419 - Fix an infinite loop we could hit if we go offline for too long.
4420 - Complain when we hit WSAENOBUFS on recv() or write() too.
4421 Perhaps this will help us hunt the bug.
4422 - If you're not a versioning dirserver, don't put the string
4423 "client-versions \nserver-versions \n" in your network-status.
4424 - Lower the minimum required number of file descriptors to 1000,
4425 so we can have some overhead for Valgrind on Linux, where the
4426 default ulimit -n is 1024.
4429 - Add tor.dizum.com as the fifth authoritative directory server.
4430 - Add a new config option FetchUselessDescriptors, off by default,
4431 for when you plan to run "exitlist" on your client and you want
4432 to know about even the non-running descriptors.
4435 Changes in version 0.1.1.17-rc - 2006-03-28
4437 - Clients and servers since 0.1.1.10-alpha have been expiring
4438 connections whenever they are idle for 5 minutes and they *do*
4439 have circuits on them. Oops. With this new version, clients will
4440 discard their previous entry guard choices and avoid choosing
4441 entry guards running these flawed versions.
4442 - Fix memory leak when uncompressing concatenated zlib streams. This
4443 was causing substantial leaks over time on Tor servers.
4444 - The v1 directory was including servers as much as 48 hours old,
4445 because that's how the new routerlist->routers works. Now only
4446 include them if they're 20 hours old or less.
4449 - Resume building on irix64, netbsd 2.0, etc.
4450 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
4452 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
4453 and it is confusing some users.
4454 - Mirrors stop caching the v1 directory so often.
4455 - Make the max number of old descriptors that a cache will hold
4456 rise with the number of directory authorities, so we can scale.
4457 - Change our win32 uname() hack to be more forgiving about what
4458 win32 versions it thinks it's found.
4461 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
4463 - When the controller's *setconf commands fail, collect an error
4464 message in a string and hand it back to the controller.
4465 - Make the v2 dir's "Fast" flag based on relative capacity, just
4466 like "Stable" is based on median uptime. Name everything in the
4467 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
4468 - Log server fingerprint on startup, so new server operators don't
4469 have to go hunting around their filesystem for it.
4470 - Return a robots.txt on our dirport to discourage google indexing.
4471 - Let the controller ask for GETINFO dir/status/foo so it can ask
4472 directly rather than connecting to the dir port. Only works when
4473 dirport is set for now.
4475 o New config options rather than constants in the code:
4476 - SocksTimeout: How long do we let a socks connection wait
4477 unattached before we fail it?
4478 - CircuitBuildTimeout: Cull non-open circuits that were born
4479 at least this many seconds ago.
4480 - CircuitIdleTimeout: Cull open clean circuits that were born
4481 at least this many seconds ago.
4484 Changes in version 0.1.1.16-rc - 2006-03-18
4485 o Bugfixes on 0.1.1.15-rc:
4486 - Fix assert when the controller asks to attachstream a connect-wait
4487 or resolve-wait stream.
4488 - Now do address rewriting when the controller asks us to attach
4489 to a particular circuit too. This will let Blossom specify
4490 "moria2.exit" without having to learn what moria2's IP address is.
4491 - Make the "tor --verify-config" command-line work again, so people
4492 can automatically check if their torrc will parse.
4493 - Authoritative dirservers no longer require an open connection from
4494 a server to consider him "reachable". We need this change because
4495 when we add new auth dirservers, old servers won't know not to
4497 - Let Tor build on Sun CC again.
4498 - Fix an off-by-one buffer size in dirserv.c that magically never
4499 hit our three authorities but broke sjmurdoch's own tor network.
4500 - If we as a directory mirror don't know of any v1 directory
4501 authorities, then don't try to cache any v1 directories.
4502 - Stop warning about unknown servers in our family when they are
4503 given as hex digests.
4504 - Stop complaining as quickly to the server operator that he
4505 hasn't registered his nickname/key binding.
4506 - Various cleanups so we can add new V2 Auth Dirservers.
4507 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
4508 reflect the updated flags in our v2 dir protocol.
4509 - Resume allowing non-printable characters for exit streams (both
4510 for connecting and for resolving). Now we tolerate applications
4511 that don't follow the RFCs. But continue to block malformed names
4514 o Bugfixes on 0.1.0.x:
4515 - Fix assert bug in close_logs(): when we close and delete logs,
4516 remove them all from the global "logfiles" list.
4517 - Fix minor integer overflow in calculating when we expect to use up
4518 our bandwidth allocation before hibernating.
4519 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
4520 there are multiple SSLs installed with different versions.
4521 - When we try to be a server and Address is not explicitly set and
4522 our hostname resolves to a private IP address, try to use an
4523 interface address if it has a public address. Now Windows machines
4524 that think of themselves as localhost can work by default.
4527 - Let the controller ask for GETINFO dir/server/foo so it can ask
4528 directly rather than connecting to the dir port.
4529 - Let the controller tell us about certain router descriptors
4530 that it doesn't want Tor to use in circuits. Implement
4531 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
4532 - New config option SafeSocks to reject all application connections
4533 using unsafe socks protocols. Defaults to off.
4536 Changes in version 0.1.1.15-rc - 2006-03-11
4537 o Bugfixes and cleanups:
4538 - When we're printing strings from the network, don't try to print
4539 non-printable characters. This protects us against shell escape
4540 sequence exploits, and also against attacks to fool humans into
4541 misreading their logs.
4542 - Fix a bug where Tor would fail to establish any connections if you
4543 left it off for 24 hours and then started it: we were happy with
4544 the obsolete network statuses, but they all referred to router
4545 descriptors that were too old to fetch, so we ended up with no
4546 valid router descriptors.
4547 - Fix a seg fault in the controller's "getinfo orconn-status"
4548 command while listing status on incoming handshaking connections.
4549 Introduce a status name "NEW" for these connections.
4550 - If we get a linelist or linelist_s config option from the torrc
4551 (e.g. ExitPolicy) and it has no value, warn and skip rather than
4552 silently resetting it to its default.
4553 - Don't abandon entry guards until they've been down or gone for
4555 - Cleaner and quieter log messages.
4558 - New controller signal NEWNYM that makes new application requests
4560 - Add a new circuit purpose 'controller' to let the controller ask
4561 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
4562 controller command to let you specify the purpose if you're
4563 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
4564 command to let you change a circuit's purpose after it's been
4566 - Accept "private:*" in routerdesc exit policies; not generated yet
4567 because older Tors do not understand it.
4568 - Add BSD-style contributed startup script "rc.subr" from Peter
4572 Changes in version 0.1.1.14-alpha - 2006-02-20
4573 o Bugfixes on 0.1.1.x:
4574 - Don't die if we ask for a stdout or stderr log (even implicitly)
4575 and we're set to RunAsDaemon -- just warn.
4576 - We still had a few bugs in the OR connection rotation code that
4577 caused directory servers to slowly aggregate connections to other
4578 fast Tor servers. This time for sure!
4579 - Make log entries on Win32 include the name of the function again.
4580 - We were treating a pair of exit policies if they were equal even
4581 if one said accept and the other said reject -- causing us to
4582 not always publish a new descriptor since we thought nothing
4584 - Retry pending server downloads as well as pending networkstatus
4585 downloads when we unexpectedly get a socks request.
4586 - We were ignoring the IS_FAST flag in the directory status,
4587 meaning we were willing to pick trivial-bandwidth nodes for "fast"
4589 - If the controller's SAVECONF command fails (e.g. due to file
4590 permissions), let the controller know that it failed.
4593 - If we're trying to be a Tor server and running Windows 95/98/ME
4594 as a server, explain that we'll likely crash.
4595 - When we're a server, a client asks for an old-style directory,
4596 and our write bucket is empty, don't give it to him. This way
4597 small servers can continue to serve the directory *sometimes*,
4598 without getting overloaded.
4599 - Compress exit policies even more -- look for duplicate lines
4601 - Clients now honor the "guard" flag in the router status when
4602 picking entry guards, rather than looking at is_fast or is_stable.
4603 - Retain unrecognized lines in $DATADIR/state file, so that we can
4604 be forward-compatible.
4605 - Generate 18.0.0.0/8 address policy format in descs when we can;
4606 warn when the mask is not reducible to a bit-prefix.
4607 - Let the user set ControlListenAddress in the torrc. This can be
4608 dangerous, but there are some cases (like a secured LAN) where it
4610 - Split ReachableAddresses into ReachableDirAddresses and
4611 ReachableORAddresses, so we can restrict Dir conns to port 80
4612 and OR conns to port 443.
4613 - Now we can target arch and OS in rpm builds (contributed by
4614 Phobos). Also make the resulting dist-rpm filename match the
4616 - New config options to help controllers: FetchServerDescriptors
4617 and FetchHidServDescriptors for whether to fetch server
4618 info and hidserv info or let the controller do it, and
4619 PublishServerDescriptor and PublishHidServDescriptors.
4620 - Also let the controller set the __AllDirActionsPrivate config
4621 option if you want all directory fetches/publishes to happen via
4622 Tor (it assumes your controller bootstraps your circuits).
4625 Changes in version 0.1.0.17 - 2006-02-17
4626 o Crash bugfixes on 0.1.0.x:
4627 - When servers with a non-zero DirPort came out of hibernation,
4628 sometimes they would trigger an assert.
4630 o Other important bugfixes:
4631 - On platforms that don't have getrlimit (like Windows), we were
4632 artificially constraining ourselves to a max of 1024
4633 connections. Now just assume that we can handle as many as 15000
4634 connections. Hopefully this won't cause other problems.
4636 o Backported features:
4637 - When we're a server, a client asks for an old-style directory,
4638 and our write bucket is empty, don't give it to him. This way
4639 small servers can continue to serve the directory *sometimes*,
4640 without getting overloaded.
4641 - Whenever you get a 503 in response to a directory fetch, try
4642 once more. This will become important once servers start sending
4643 503's whenever they feel busy.
4644 - Fetch a new directory every 120 minutes, not every 40 minutes.
4645 Now that we have hundreds of thousands of users running the old
4646 directory algorithm, it's starting to hurt a lot.
4647 - Bump up the period for forcing a hidden service descriptor upload
4648 from 20 minutes to 1 hour.
4651 Changes in version 0.1.1.13-alpha - 2006-02-09
4652 o Crashes in 0.1.1.x:
4653 - When you tried to setconf ORPort via the controller, Tor would
4654 crash. So people using TorCP to become a server were sad.
4655 - Solve (I hope) the stack-smashing bug that we were seeing on fast
4656 servers. The problem appears to be something do with OpenSSL's
4657 random number generation, or how we call it, or something. Let me
4658 know if the crashes continue.
4659 - Turn crypto hardware acceleration off by default, until we find
4660 somebody smart who can test it for us. (It appears to produce
4661 seg faults in at least some cases.)
4662 - Fix a rare assert error when we've tried all intro points for
4663 a hidden service and we try fetching the service descriptor again:
4664 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
4667 - Fix a major load balance bug: we were round-robining in 16 KB
4668 chunks, and servers with bandwidthrate of 20 KB, while downloading
4669 a 600 KB directory, would starve their other connections. Now we
4670 try to be a bit more fair.
4671 - Dir authorities and mirrors were never expiring the newest
4672 descriptor for each server, causing memory and directory bloat.
4673 - Fix memory-bloating and connection-bloating bug on servers: We
4674 were never closing any connection that had ever had a circuit on
4675 it, because we were checking conn->n_circuits == 0, yet we had a
4676 bug that let it go negative.
4677 - Make Tor work using squid as your http proxy again -- squid
4678 returns an error if you ask for a URL that's too long, and it uses
4679 a really generic error message. Plus, many people are behind a
4680 transparent squid so they don't even realize it.
4681 - On platforms that don't have getrlimit (like Windows), we were
4682 artificially constraining ourselves to a max of 1024
4683 connections. Now just assume that we can handle as many as 15000
4684 connections. Hopefully this won't cause other problems.
4685 - Add a new config option ExitPolicyRejectPrivate which defaults to
4686 1. This means all exit policies will begin with rejecting private
4687 addresses, unless the server operator explicitly turns it off.
4690 - Clients no longer download descriptors for non-running
4692 - Before we add new directory authorities, we should make it
4693 clear that only v1 authorities should receive/publish hidden
4694 service descriptors.
4697 - As soon as we've fetched some more directory info, immediately
4698 try to download more server descriptors. This way we don't have
4699 a 10 second pause during initial bootstrapping.
4700 - Remove even more loud log messages that the server operator can't
4702 - When we're running an obsolete or un-recommended version, make
4703 the log message more clear about what the problem is and what
4704 versions *are* still recommended.
4705 - Provide a more useful warn message when our onion queue gets full:
4706 the CPU is too slow or the exit policy is too liberal.
4707 - Don't warn when we receive a 503 from a dirserver/cache -- this
4708 will pave the way for them being able to refuse if they're busy.
4709 - When we fail to bind a listener, try to provide a more useful
4710 log message: e.g., "Is Tor already running?"
4711 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
4712 Goldberg can prove things about our handshake protocol more
4714 - MaxConn has been obsolete for a while now. Document the ConnLimit
4715 config option, which is a *minimum* number of file descriptors
4716 that must be available else Tor refuses to start.
4717 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
4718 if you log to syslog and want something other than LOG_DAEMON.
4719 - Make dirservers generate a separate "guard" flag to mean,
4720 "would make a good entry guard". Make clients parse it and vote
4721 on it. Not used by clients yet.
4722 - Implement --with-libevent-dir option to ./configure. Also, improve
4723 search techniques to find libevent, and use those for openssl too.
4724 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
4725 - Only start testing reachability once we've established a
4726 circuit. This will make startup on dirservers less noisy.
4727 - Don't try to upload hidden service descriptors until we have
4728 established a circuit.
4729 - Fix the controller's "attachstream 0" command to treat conn like
4730 it just connected, doing address remapping, handling .exit and
4731 .onion idioms, and so on. Now we're more uniform in making sure
4732 that the controller hears about new and closing connections.
4735 Changes in version 0.1.1.12-alpha - 2006-01-11
4736 o Bugfixes on 0.1.1.x:
4737 - The fix to close duplicate server connections was closing all
4738 Tor client connections if they didn't establish a circuit
4739 quickly enough. Oops.
4740 - Fix minor memory issue (double-free) that happened on exit.
4742 o Bugfixes on 0.1.0.x:
4743 - Tor didn't warn when it failed to open a log file.
4746 Changes in version 0.1.1.11-alpha - 2006-01-10
4747 o Crashes in 0.1.1.x:
4748 - Include all the assert/crash fixes from 0.1.0.16.
4749 - If you start Tor and then quit very quickly, there were some
4750 races that tried to free things that weren't allocated yet.
4751 - Fix a rare memory stomp if you're running hidden services.
4752 - Fix segfault when specifying DirServer in config without nickname.
4753 - Fix a seg fault when you finish connecting to a server but at
4754 that moment you dump his server descriptor.
4755 - Extendcircuit and Attachstream controller commands would
4756 assert/crash if you don't give them enough arguments.
4757 - Fix an assert error when we're out of space in the connection_list
4758 and we try to post a hidden service descriptor (reported by weasel).
4759 - If you specify a relative torrc path and you set RunAsDaemon in
4760 your torrc, then it chdir()'s to the new directory. If you HUP,
4761 it tries to load the new torrc location, fails, and exits.
4762 The fix: no longer allow a relative path to torrc using -f.
4765 - Implement "entry guards": automatically choose a handful of entry
4766 nodes and stick with them for all circuits. Only pick new guards
4767 when the ones you have are unsuitable, and if the old guards
4768 become suitable again, switch back. This will increase security
4769 dramatically against certain end-point attacks. The EntryNodes
4770 config option now provides some hints about which entry guards you
4771 want to use most; and StrictEntryNodes means to only use those.
4772 - New directory logic: download by descriptor digest, not by
4773 fingerprint. Caches try to download all listed digests from
4774 authorities; clients try to download "best" digests from caches.
4775 This avoids partitioning and isolating attacks better.
4776 - Make the "stable" router flag in network-status be the median of
4777 the uptimes of running valid servers, and make clients pay
4778 attention to the network-status flags. Thus the cutoff adapts
4779 to the stability of the network as a whole, making IRC, IM, etc
4780 connections more reliable.
4783 - Tor servers with dynamic IP addresses were needing to wait 18
4784 hours before they could start doing reachability testing using
4785 the new IP address and ports. This is because they were using
4786 the internal descriptor to learn what to test, yet they were only
4787 rebuilding the descriptor once they decided they were reachable.
4788 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
4789 to download certain server descriptors, throw them away, and then
4790 fetch them again after 30 minutes. Now mirrors throw away these
4791 server descriptors so clients can't get them.
4792 - We were leaving duplicate connections to other ORs open for a week,
4793 rather than closing them once we detect a duplicate. This only
4794 really affected authdirservers, but it affected them a lot.
4795 - Spread the authdirservers' reachability testing over the entire
4796 testing interval, so we don't try to do 500 TLS's at once every
4800 - If the network is down, and we try to connect to a conn because
4801 we have a circuit in mind, and we timeout (30 seconds) because the
4802 network never answers, we were expiring the circuit, but we weren't
4803 obsoleting the connection or telling the entry_guards functions.
4804 - Some Tor servers process billions of cells per day. These statistics
4805 need to be uint64_t's.
4806 - Check for integer overflows in more places, when adding elements
4807 to smartlists. This could possibly prevent a buffer overflow
4808 on malicious huge inputs. I don't see any, but I haven't looked
4810 - ReachableAddresses kept growing new "reject *:*" lines on every
4812 - When you "setconf log" via the controller, it should remove all
4813 logs. We were automatically adding back in a "log notice stdout".
4814 - Newly bootstrapped Tor networks couldn't establish hidden service
4815 circuits until they had nodes with high uptime. Be more tolerant.
4816 - We were marking servers down when they could not answer every piece
4817 of the directory request we sent them. This was far too harsh.
4818 - Fix the torify (tsocks) config file to not use Tor for localhost
4820 - Directory authorities now go to the proper authority when asking for
4821 a networkstatus, even when they want a compressed one.
4822 - Fix a harmless bug that was causing Tor servers to log
4823 "Got an end because of misc error, but we're not an AP. Closing."
4824 - Authorities were treating their own descriptor changes as cosmetic,
4825 meaning the descriptor available in the network-status and the
4826 descriptor that clients downloaded were different.
4827 - The OS X installer was adding a symlink for tor_resolve but
4828 the binary was called tor-resolve (reported by Thomas Hardly).
4829 - Workaround a problem with some http proxies where they refuse GET
4830 requests that specify "Content-Length: 0" (reported by Adrian).
4831 - Fix wrong log message when you add a "HiddenServiceNodes" config
4832 line without any HiddenServiceDir line (reported by Chris Thomas).
4835 - Write the TorVersion into the state file so we have a prayer of
4836 keeping forward and backward compatibility.
4837 - Revive the FascistFirewall config option rather than eliminating it:
4838 now it's a synonym for ReachableAddresses *:80,*:443.
4839 - Clients choose directory servers from the network status lists,
4840 not from their internal list of router descriptors. Now they can
4841 go to caches directly rather than needing to go to authorities
4843 - Directory authorities ignore router descriptors that have only
4844 cosmetic differences: do this for 0.1.0.x servers now too.
4845 - Add a new flag to network-status indicating whether the server
4846 can answer v2 directory requests too.
4847 - Authdirs now stop whining so loudly about bad descriptors that
4848 they fetch from other dirservers. So when there's a log complaint,
4849 it's for sure from a freshly uploaded descriptor.
4850 - Reduce memory requirements in our structs by changing the order
4852 - There used to be two ways to specify your listening ports in a
4853 server descriptor: on the "router" line and with a separate "ports"
4854 line. Remove support for the "ports" line.
4855 - New config option "AuthDirRejectUnlisted" for auth dirservers as
4856 a panic button: if we get flooded with unusable servers we can
4857 revert to only listing servers in the approved-routers file.
4858 - Auth dir servers can now mark a fingerprint as "!reject" or
4859 "!invalid" in the approved-routers file (as its nickname), to
4860 refuse descriptors outright or include them but marked as invalid.
4861 - Servers store bandwidth history across restarts/crashes.
4862 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
4863 get a better idea of why their circuits failed. Not used yet.
4864 - Directory mirrors now cache up to 16 unrecognized network-status
4865 docs. Now we can add new authdirservers and they'll be cached too.
4866 - When picking a random directory, prefer non-authorities if any
4868 - New controller option "getinfo desc/all-recent" to fetch the
4869 latest server descriptor for every router that Tor knows about.
4872 Changes in version 0.1.0.16 - 2006-01-02
4873 o Crash bugfixes on 0.1.0.x:
4874 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
4875 corrupting the heap, losing FDs, or crashing when we need to resize
4876 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
4877 - It turns out sparc64 platforms crash on unaligned memory access
4878 too -- so detect and avoid this.
4879 - Handle truncated compressed data correctly (by detecting it and
4881 - Fix possible-but-unlikely free(NULL) in control.c.
4882 - When we were closing connections, there was a rare case that
4883 stomped on memory, triggering seg faults and asserts.
4884 - Avoid potential infinite recursion when building a descriptor. (We
4885 don't know that it ever happened, but better to fix it anyway.)
4886 - We were neglecting to unlink marked circuits from soon-to-close OR
4887 connections, which caused some rare scribbling on freed memory.
4888 - Fix a memory stomping race bug when closing the joining point of two
4889 rendezvous circuits.
4890 - Fix an assert in time parsing found by Steven Murdoch.
4892 o Other bugfixes on 0.1.0.x:
4893 - When we're doing reachability testing, provide more useful log
4894 messages so the operator knows what to expect.
4895 - Do not check whether DirPort is reachable when we are suppressing
4896 advertising it because of hibernation.
4897 - When building with -static or on Solaris, we sometimes needed -ldl.
4898 - When we're deciding whether a stream has enough circuits around
4899 that can handle it, count the freshly dirty ones and not the ones
4900 that are so dirty they won't be able to handle it.
4901 - When we're expiring old circuits, we had a logic error that caused
4902 us to close new rendezvous circuits rather than old ones.
4903 - Give a more helpful log message when you try to change ORPort via
4904 the controller: you should upgrade Tor if you want that to work.
4905 - We were failing to parse Tor versions that start with "Tor ".
4906 - Tolerate faulty streams better: when a stream fails for reason
4907 exitpolicy, stop assuming that the router is lying about his exit
4908 policy. When a stream fails for reason misc, allow it to retry just
4909 as if it was resolvefailed. When a stream has failed three times,
4910 reset its failure count so we can try again and get all three tries.
4913 Changes in version 0.1.1.10-alpha - 2005-12-11
4914 o Correctness bugfixes on 0.1.0.x:
4915 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
4916 corrupting the heap, losing FDs, or crashing when we need to resize
4917 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
4918 - Stop doing the complex voodoo overkill checking for insecure
4919 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
4920 - When we were closing connections, there was a rare case that
4921 stomped on memory, triggering seg faults and asserts.
4922 - We were neglecting to unlink marked circuits from soon-to-close OR
4923 connections, which caused some rare scribbling on freed memory.
4924 - When we're deciding whether a stream has enough circuits around
4925 that can handle it, count the freshly dirty ones and not the ones
4926 that are so dirty they won't be able to handle it.
4927 - Recover better from TCP connections to Tor servers that are
4928 broken but don't tell you (it happens!); and rotate TLS
4929 connections once a week.
4930 - When we're expiring old circuits, we had a logic error that caused
4931 us to close new rendezvous circuits rather than old ones.
4932 - Fix a scary-looking but apparently harmless bug where circuits
4933 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
4934 servers, and never switch to state CIRCUIT_STATE_OPEN.
4935 - When building with -static or on Solaris, we sometimes needed to
4937 - Give a useful message when people run Tor as the wrong user,
4938 rather than telling them to start chowning random directories.
4939 - We were failing to inform the controller about new .onion streams.
4941 o Security bugfixes on 0.1.0.x:
4942 - Refuse server descriptors if the fingerprint line doesn't match
4943 the included identity key. Tor doesn't care, but other apps (and
4944 humans) might actually be trusting the fingerprint line.
4945 - We used to kill the circuit when we receive a relay command we
4946 don't recognize. Now we just drop it.
4947 - Start obeying our firewall options more rigorously:
4948 . If we can't get to a dirserver directly, try going via Tor.
4949 . Don't ever try to connect (as a client) to a place our
4950 firewall options forbid.
4951 . If we specify a proxy and also firewall options, obey the
4952 firewall options even when we're using the proxy: some proxies
4953 can only proxy to certain destinations.
4954 - Fix a bug found by Lasse Overlier: when we were making internal
4955 circuits (intended to be cannibalized later for rendezvous and
4956 introduction circuits), we were picking them so that they had
4957 useful exit nodes. There was no need for this, and it actually
4958 aids some statistical attacks.
4959 - Start treating internal circuits and exit circuits separately.
4960 It's important to keep them separate because internal circuits
4961 have their last hops picked like middle hops, rather than like
4962 exit hops. So exiting on them will break the user's expectations.
4964 o Bugfixes on 0.1.1.x:
4965 - Take out the mis-feature where we tried to detect IP address
4966 flapping for people with DynDNS, and chose not to upload a new
4967 server descriptor sometimes.
4968 - Try to be compatible with OpenSSL 0.9.6 again.
4969 - Log fix: when the controller is logging about .onion addresses,
4970 sometimes it didn't include the ".onion" part of the address.
4971 - Don't try to modify options->DirServers internally -- if the
4972 user didn't specify any, just add the default ones directly to
4973 the trusted dirserver list. This fixes a bug where people running
4974 controllers would use SETCONF on some totally unrelated config
4975 option, and Tor would start yelling at them about changing their
4977 - Let the controller's redirectstream command specify a port, in
4978 case the controller wants to change that too.
4979 - When we requested a pile of server descriptors, we sometimes
4980 accidentally launched a duplicate request for the first one.
4981 - Bugfix for trackhostexits: write down the fingerprint of the
4982 chosen exit, not its nickname, because the chosen exit might not
4984 - When parsing foo.exit, if foo is unknown, and we are leaving
4985 circuits unattached, set the chosen_exit field and leave the
4986 address empty. This matters because controllers got confused
4988 - Directory authorities no longer try to download server
4989 descriptors that they know they will reject.
4991 o Features and updates:
4992 - Replace balanced trees with hash tables: this should make stuff
4993 significantly faster.
4994 - Resume using the AES counter-mode implementation that we ship,
4995 rather than OpenSSL's. Ours is significantly faster.
4996 - Many other CPU and memory improvements.
4997 - Add a new config option FastFirstHopPK (on by default) so clients
4998 do a trivial crypto handshake for their first hop, since TLS has
4999 already taken care of confidentiality and authentication.
5000 - Add a new config option TestSocks so people can see if their
5001 applications are using socks4, socks4a, socks5-with-ip, or
5002 socks5-with-hostname. This way they don't have to keep mucking
5003 with tcpdump and wondering if something got cached somewhere.
5004 - Warn when listening on a public address for socks. I suspect a
5005 lot of people are setting themselves up as open socks proxies,
5006 and they have no idea that jerks on the Internet are using them,
5007 since they simply proxy the traffic into the Tor network.
5008 - Add "private:*" as an alias in configuration for policies. Now
5009 you can simplify your exit policy rather than needing to list
5010 every single internal or nonroutable network space.
5011 - Add a new controller event type that allows controllers to get
5012 all server descriptors that were uploaded to a router in its role
5013 as authoritative dirserver.
5014 - Start shipping socks-extensions.txt, tor-doc-unix.html,
5015 tor-doc-server.html, and stylesheet.css in the tarball.
5016 - Stop shipping tor-doc.html in the tarball.
5019 Changes in version 0.1.1.9-alpha - 2005-11-15
5020 o Usability improvements:
5021 - Start calling it FooListenAddress rather than FooBindAddress,
5022 since few of our users know what it means to bind an address
5024 - Reduce clutter in server logs. We're going to try to make
5025 them actually usable now. New config option ProtocolWarnings that
5026 lets you hear about how _other Tors_ are breaking the protocol. Off
5028 - Divide log messages into logging domains. Once we put some sort
5029 of interface on this, it will let people looking at more verbose
5030 log levels specify the topics they want to hear more about.
5031 - Make directory servers return better http 404 error messages
5032 instead of a generic "Servers unavailable".
5033 - Check for even more Windows version flags when writing the platform
5034 string in server descriptors, and note any we don't recognize.
5035 - Clean up more of the OpenSSL memory when exiting, so we can detect
5036 memory leaks better.
5037 - Make directory authorities be non-versioning, non-naming by
5038 default. Now we can add new directory servers without requiring
5039 their operators to pay close attention.
5040 - When logging via syslog, include the pid whenever we provide
5041 a log entry. Suggested by Todd Fries.
5043 o Performance improvements:
5044 - Directory servers now silently throw away new descriptors that
5045 haven't changed much if the timestamps are similar. We do this to
5046 tolerate older Tor servers that upload a new descriptor every 15
5047 minutes. (It seemed like a good idea at the time.)
5048 - Inline bottleneck smartlist functions; use fast versions by default.
5049 - Add a "Map from digest to void*" abstraction digestmap_t so we
5050 can do less hex encoding/decoding. Use it in router_get_by_digest()
5051 to resolve a performance bottleneck.
5052 - Allow tor_gzip_uncompress to extract as much as possible from
5053 truncated compressed data. Try to extract as many
5054 descriptors as possible from truncated http responses (when
5055 DIR_PURPOSE_FETCH_ROUTERDESC).
5056 - Make circ->onionskin a pointer, not a static array. moria2 was using
5057 125000 circuit_t's after it had been up for a few weeks, which
5058 translates to 20+ megs of wasted space.
5059 - The private half of our EDH handshake keys are now chosen out
5060 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
5062 o Security improvements:
5063 - Start making directory caches retain old routerinfos, so soon
5064 clients can start asking by digest of descriptor rather than by
5065 fingerprint of server.
5066 - Add half our entropy from RAND_poll in OpenSSL. This knows how
5067 to use egd (if present), openbsd weirdness (if present), vms/os2
5068 weirdness (if we ever port there), and more in the future.
5070 o Bugfixes on 0.1.0.x:
5071 - Do round-robin writes of at most 16 kB per write. This might be
5072 more fair on loaded Tor servers, and it might resolve our Windows
5073 crash bug. It might also slow things down.
5074 - Our TLS handshakes were generating a single public/private
5075 keypair for the TLS context, rather than making a new one for
5076 each new connections. Oops. (But we were still rotating them
5077 periodically, so it's not so bad.)
5078 - When we were cannibalizing a circuit with a particular exit
5079 node in mind, we weren't checking to see if that exit node was
5080 already present earlier in the circuit. Oops.
5081 - When a Tor server's IP changes (e.g. from a dyndns address),
5082 upload a new descriptor so clients will learn too.
5083 - Really busy servers were keeping enough circuits open on stable
5084 connections that they were wrapping around the circuit_id
5085 space. (It's only two bytes.) This exposed a bug where we would
5086 feel free to reuse a circuit_id even if it still exists but has
5087 been marked for close. Try to fix this bug. Some bug remains.
5088 - If we would close a stream early (e.g. it asks for a .exit that
5089 we know would refuse it) but the LeaveStreamsUnattached config
5090 option is set by the controller, then don't close it.
5092 o Bugfixes on 0.1.1.8-alpha:
5093 - Fix a big pile of memory leaks, some of them serious.
5094 - Do not try to download a routerdesc if we would immediately reject
5096 - Resume inserting a newline between all router descriptors when
5097 generating (old style) signed directories, since our spec says
5099 - When providing content-type application/octet-stream for
5100 server descriptors using .z, we were leaving out the
5101 content-encoding header. Oops. (Everything tolerated this just
5102 fine, but that doesn't mean we need to be part of the problem.)
5103 - Fix a potential seg fault in getconf and getinfo using version 1
5104 of the controller protocol.
5105 - Avoid crash: do not check whether DirPort is reachable when we
5106 are suppressing it because of hibernation.
5107 - Make --hash-password not crash on exit.
5110 Changes in version 0.1.1.8-alpha - 2005-10-07
5111 o New features (major):
5112 - Clients don't download or use the directory anymore. Now they
5113 download and use network-statuses from the trusted dirservers,
5114 and fetch individual server descriptors as needed from mirrors.
5115 See dir-spec.txt for all the gory details.
5116 - Be more conservative about whether to advertise our DirPort.
5117 The main change is to not advertise if we're running at capacity
5118 and either a) we could hibernate or b) our capacity is low and
5119 we're using a default DirPort.
5120 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
5122 o New features (minor):
5123 - Try to be smart about when to retry network-status and
5124 server-descriptor fetches. Still needs some tuning.
5125 - Stop parsing, storing, or using running-routers output (but
5126 mirrors still cache and serve it).
5127 - Consider a threshold of versioning dirservers (dirservers who have
5128 an opinion about which Tor versions are still recommended) before
5129 deciding whether to warn the user that he's obsolete.
5130 - Dirservers can now reject/invalidate by key and IP, with the
5131 config options "AuthDirInvalid" and "AuthDirReject". This is
5132 useful since currently we automatically list servers as running
5133 and usable even if we know they're jerks.
5134 - Provide dire warnings to any users who set DirServer; move it out
5135 of torrc.sample and into torrc.complete.
5136 - Add MyFamily to torrc.sample in the server section.
5137 - Add nicknames to the DirServer line, so we can refer to them
5138 without requiring all our users to memorize their IP addresses.
5139 - When we get an EOF or a timeout on a directory connection, note
5140 how many bytes of serverdesc we are dropping. This will help
5141 us determine whether it is smart to parse incomplete serverdesc
5143 - Add a new function to "change pseudonyms" -- that is, to stop
5144 using any currently-dirty circuits for new streams, so we don't
5145 link new actions to old actions. Currently it's only called on
5146 HUP (or SIGNAL RELOAD).
5147 - On sighup, if UseHelperNodes changed to 1, use new circuits.
5148 - Start using RAND_bytes rather than RAND_pseudo_bytes from
5149 OpenSSL. Also, reseed our entropy every hour, not just at
5150 startup. And entropy in 512-bit chunks, not 160-bit chunks.
5152 o Fixes on 0.1.1.7-alpha:
5153 - Nobody ever implemented EVENT_ADDRMAP for control protocol
5154 version 0, so don't let version 0 controllers ask for it.
5155 - If you requested something with too many newlines via the
5156 v1 controller protocol, you could crash tor.
5157 - Fix a number of memory leaks, including some pretty serious ones.
5158 - Re-enable DirPort testing again, so Tor servers will be willing
5159 to advertise their DirPort if it's reachable.
5160 - On TLS handshake, only check the other router's nickname against
5161 its expected nickname if is_named is set.
5163 o Fixes forward-ported from 0.1.0.15:
5164 - Don't crash when we don't have any spare file descriptors and we
5165 try to spawn a dns or cpu worker.
5166 - Make the numbers in read-history and write-history into uint64s,
5167 so they don't overflow and publish negatives in the descriptor.
5170 - For the OS X package's modified privoxy config file, comment
5171 out the "logfile" line so we don't log everything passed
5173 - We were whining about using socks4 or socks5-with-local-lookup
5174 even when it's an IP in the "virtual" range we designed exactly
5176 - We were leaking some memory every time the client changes IPs.
5177 - Never call free() on tor_malloc()d memory. This will help us
5178 use dmalloc to detect memory leaks.
5179 - Check for named servers when looking them up by nickname;
5180 warn when we'recalling a non-named server by its nickname;
5181 don't warn twice about the same name.
5182 - Try to list MyFamily elements by key, not by nickname, and warn
5183 if we've not heard of the server.
5184 - Make windows platform detection (uname equivalent) smarter.
5185 - It turns out sparc64 doesn't like unaligned access either.
5188 Changes in version 0.1.0.15 - 2005-09-23
5189 o Bugfixes on 0.1.0.x:
5190 - Reject ports 465 and 587 (spam targets) in default exit policy.
5191 - Don't crash when we don't have any spare file descriptors and we
5192 try to spawn a dns or cpu worker.
5193 - Get rid of IgnoreVersion undocumented config option, and make us
5194 only warn, never exit, when we're running an obsolete version.
5195 - Don't try to print a null string when your server finds itself to
5196 be unreachable and the Address config option is empty.
5197 - Make the numbers in read-history and write-history into uint64s,
5198 so they don't overflow and publish negatives in the descriptor.
5199 - Fix a minor memory leak in smartlist_string_remove().
5200 - We were only allowing ourselves to upload a server descriptor at
5201 most every 20 minutes, even if it changed earlier than that.
5202 - Clean up log entries that pointed to old URLs.
5205 Changes in version 0.1.1.7-alpha - 2005-09-14
5206 o Fixes on 0.1.1.6-alpha:
5207 - Exit servers were crashing when people asked them to make a
5208 connection to an address not in their exit policy.
5209 - Looking up a non-existent stream for a v1 control connection would
5211 - Fix a seg fault if we ask a dirserver for a descriptor by
5212 fingerprint but he doesn't know about him.
5213 - SETCONF was appending items to linelists, not clearing them.
5214 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
5215 out and refuse the setconf if it would fail.
5216 - Downgrade the dirserver log messages when whining about
5220 - Add Peter Palfrader's check-tor script to tor/contrib/
5221 It lets you easily check whether a given server (referenced by
5222 nickname) is reachable by you.
5223 - Numerous changes to move towards client-side v2 directories. Not
5227 - If the user gave tor an odd number of command-line arguments,
5228 we were silently ignoring the last one. Now we complain and fail.
5229 [This wins the oldest-bug prize -- this bug has been present since
5230 November 2002, as released in Tor 0.0.0.]
5231 - Do not use unaligned memory access on alpha, mips, or mipsel.
5232 It *works*, but is very slow, so we treat them as if it doesn't.
5233 - Retry directory requests if we fail to get an answer we like
5234 from a given dirserver (we were retrying before, but only if
5235 we fail to connect).
5236 - When writing the RecommendedVersions line, sort them first.
5237 - When the client asked for a rendezvous port that the hidden
5238 service didn't want to provide, we were sending an IP address
5239 back along with the end cell. Fortunately, it was zero. But stop
5241 - Correct "your server is reachable" log entries to indicate that
5242 it was self-testing that told us so.
5245 Changes in version 0.1.1.6-alpha - 2005-09-09
5246 o Fixes on 0.1.1.5-alpha:
5247 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
5248 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
5249 - Fix bug with tor_memmem finding a match at the end of the string.
5250 - Make unit tests run without segfaulting.
5251 - Resolve some solaris x86 compile warnings.
5252 - Handle duplicate lines in approved-routers files without warning.
5253 - Fix bug where as soon as a server refused any requests due to his
5254 exit policy (e.g. when we ask for localhost and he tells us that's
5255 127.0.0.1 and he won't do it), we decided he wasn't obeying his
5256 exit policy using him for any exits.
5257 - Only do openssl hardware accelerator stuff if openssl version is
5260 o New controller features/fixes:
5261 - Add a "RESETCONF" command so you can set config options like
5262 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
5263 a config option in the torrc with no value, then it clears it
5264 entirely (rather than setting it to its default).
5265 - Add a "GETINFO config-file" to tell us where torrc is.
5266 - Avoid sending blank lines when GETINFO replies should be empty.
5267 - Add a QUIT command for the controller (for using it manually).
5268 - Fix a bug in SAVECONF that was adding default dirservers and
5269 other redundant entries to the torrc file.
5271 o Start on the new directory design:
5272 - Generate, publish, cache, serve new network-status format.
5273 - Publish individual descriptors (by fingerprint, by "all", and by
5275 - Publish client and server recommended versions separately.
5276 - Allow tor_gzip_uncompress() to handle multiple concatenated
5277 compressed strings. Serve compressed groups of router
5278 descriptors. The compression logic here could be more
5280 - Distinguish v1 authorities (all currently trusted directories)
5281 from v2 authorities (all trusted directories).
5282 - Change DirServers config line to note which dirs are v1 authorities.
5283 - Add configuration option "V1AuthoritativeDirectory 1" which
5284 moria1, moria2, and tor26 should set.
5285 - Remove option when getting directory cache to see whether they
5286 support running-routers; they all do now. Replace it with one
5287 to see whether caches support v2 stuff.
5290 - Dirservers now do their own external reachability testing of each
5291 Tor server, and only list them as running if they've been found to
5292 be reachable. We also send back warnings to the server's logs if
5293 it uploads a descriptor that we already believe is unreachable.
5294 - Implement exit enclaves: if we know an IP address for the
5295 destination, and there's a running Tor server at that address
5296 which allows exit to the destination, then extend the circuit to
5297 that exit first. This provides end-to-end encryption and end-to-end
5298 authentication. Also, if the user wants a .exit address or enclave,
5299 use 4 hops rather than 3, and cannibalize a general circ for it
5301 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
5302 controller. Also, rotate dns and cpu workers if the controller
5303 changes options that will affect them; and initialize the dns
5304 worker cache tree whether or not we start out as a server.
5305 - Only upload a new server descriptor when options change, 18
5306 hours have passed, uptime is reset, or bandwidth changes a lot.
5307 - Check [X-]Forwarded-For headers in HTTP requests when generating
5308 log messages. This lets people run dirservers (and caches) behind
5309 Apache but still know which IP addresses are causing warnings.
5311 o Config option changes:
5312 - Replace (Fascist)Firewall* config options with a new
5313 ReachableAddresses option that understands address policies.
5314 For example, "ReachableAddresses *:80,*:443"
5315 - Get rid of IgnoreVersion undocumented config option, and make us
5316 only warn, never exit, when we're running an obsolete version.
5317 - Make MonthlyAccountingStart config option truly obsolete now.
5320 - Reject ports 465 and 587 in the default exit policy, since
5321 people have started using them for spam too.
5322 - It turns out we couldn't bootstrap a network since we added
5323 reachability detection in 0.1.0.1-rc. Good thing the Tor network
5324 has never gone down. Add an AssumeReachable config option to let
5325 servers and dirservers bootstrap. When we're trying to build a
5326 high-uptime or high-bandwidth circuit but there aren't enough
5327 suitable servers, try being less picky rather than simply failing.
5328 - Our logic to decide if the OR we connected to was the right guy
5329 was brittle and maybe open to a mitm for unverified routers.
5330 - We weren't cannibalizing circuits correctly for
5331 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
5332 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
5333 build those from scratch. This should make hidden services faster.
5334 - Predict required circuits better, with an eye toward making hidden
5335 services faster on the service end.
5336 - Retry streams if the exit node sends back a 'misc' failure. This
5337 should result in fewer random failures. Also, after failing
5338 from resolve failed or misc, reset the num failures, so we give
5339 it a fair shake next time we try.
5340 - Clean up the rendezvous warn log msgs, and downgrade some to info.
5341 - Reduce severity on logs about dns worker spawning and culling.
5342 - When we're shutting down and we do something like try to post a
5343 server descriptor or rendezvous descriptor, don't complain that
5344 we seem to be unreachable. Of course we are, we're shutting down.
5345 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
5346 We don't use them yet, but maybe one day our DNS resolver will be
5347 able to discover them.
5348 - Make ContactInfo mandatory for authoritative directory servers.
5349 - Require server descriptors to list IPv4 addresses -- hostnames
5350 are no longer allowed. This also fixes some potential security
5351 problems with people providing hostnames as their address and then
5352 preferentially resolving them to partition users.
5353 - Change log line for unreachability to explicitly suggest /etc/hosts
5354 as the culprit. Also make it clearer what IP address and ports we're
5355 testing for reachability.
5356 - Put quotes around user-supplied strings when logging so users are
5357 more likely to realize if they add bad characters (like quotes)
5359 - Let auth dir servers start without specifying an Address config
5361 - Make unit tests (and other invocations that aren't the real Tor)
5362 run without launching listeners, creating subdirectories, and so on.
5365 Changes in version 0.1.1.5-alpha - 2005-08-08
5366 o Bugfixes included in 0.1.0.14.
5368 o Bugfixes on 0.1.0.x:
5369 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
5370 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
5371 it would silently using ignore the 6668.
5374 Changes in version 0.1.0.14 - 2005-08-08
5375 o Bugfixes on 0.1.0.x:
5376 - Fix the other half of the bug with crypto handshakes
5378 - Fix an assert trigger if you send a 'signal term' via the
5379 controller when it's listening for 'event info' messages.
5382 Changes in version 0.1.1.4-alpha - 2005-08-04
5383 o Bugfixes included in 0.1.0.13.
5386 - Improve tor_gettimeofday() granularity on windows.
5387 - Make clients regenerate their keys when their IP address changes.
5388 - Implement some more GETINFO goodness: expose helper nodes, config
5389 options, getinfo keys.
5392 Changes in version 0.1.0.13 - 2005-08-04
5393 o Bugfixes on 0.1.0.x:
5394 - Fix a critical bug in the security of our crypto handshakes.
5395 - Fix a size_t underflow in smartlist_join_strings2() that made
5396 it do bad things when you hand it an empty smartlist.
5397 - Fix Windows installer to ship Tor license (thanks to Aphex for
5398 pointing out this oversight) and put a link to the doc directory
5400 - Explicitly set no-unaligned-access for sparc: it turns out the
5401 new gcc's let you compile broken code, but that doesn't make it
5405 Changes in version 0.1.1.3-alpha - 2005-07-23
5406 o Bugfixes on 0.1.1.2-alpha:
5407 - Fix a bug in handling the controller's "post descriptor"
5409 - Fix several bugs in handling the controller's "extend circuit"
5411 - Fix a bug in handling the controller's "stream status" event.
5412 - Fix an assert failure if we have a controller listening for
5413 circuit events and we go offline.
5414 - Re-allow hidden service descriptors to publish 0 intro points.
5415 - Fix a crash when generating your hidden service descriptor if
5416 you don't have enough intro points already.
5418 o New features on 0.1.1.2-alpha:
5419 - New controller function "getinfo accounting", to ask how
5420 many bytes we've used in this time period.
5421 - Experimental support for helper nodes: a lot of the risk from
5422 a small static adversary comes because users pick new random
5423 nodes every time they rebuild a circuit. Now users will try to
5424 stick to the same small set of entry nodes if they can. Not
5425 enabled by default yet.
5427 o Bugfixes on 0.1.0.12:
5428 - If you're an auth dir server, always publish your dirport,
5429 even if you haven't yet found yourself to be reachable.
5430 - Fix a size_t underflow in smartlist_join_strings2() that made
5431 it do bad things when you hand it an empty smartlist.
5434 Changes in version 0.1.0.12 - 2005-07-18
5435 o New directory servers:
5436 - tor26 has changed IP address.
5438 o Bugfixes on 0.1.0.x:
5439 - Fix a possible double-free in tor_gzip_uncompress().
5440 - When --disable-threads is set, do not search for or link against
5442 - Don't trigger an assert if an authoritative directory server
5443 claims its dirport is 0.
5444 - Fix bug with removing Tor as an NT service: some people were
5445 getting "The service did not return an error." Thanks to Matt
5449 Changes in version 0.1.1.2-alpha - 2005-07-15
5450 o New directory servers:
5451 - tor26 has changed IP address.
5453 o Bugfixes on 0.1.0.x, crashes/leaks:
5454 - Port the servers-not-obeying-their-exit-policies fix from
5456 - Fix an fd leak in start_daemon().
5457 - On Windows, you can't always reopen a port right after you've
5458 closed it. So change retry_listeners() to only close and re-open
5459 ports that have changed.
5460 - Fix a possible double-free in tor_gzip_uncompress().
5462 o Bugfixes on 0.1.0.x, usability:
5463 - When tor_socketpair() fails in Windows, give a reasonable
5464 Windows-style errno back.
5465 - Let people type "tor --install" as well as "tor -install" when
5467 want to make it an NT service.
5468 - NT service patch from Matt Edman to improve error messages.
5469 - When the controller asks for a config option with an abbreviated
5470 name, give the full name in our response.
5471 - Correct the man page entry on TrackHostExitsExpire.
5472 - Looks like we were never delivering deflated (i.e. compressed)
5473 running-routers lists, even when asked. Oops.
5474 - When --disable-threads is set, do not search for or link against
5477 o Bugfixes on 0.1.1.x:
5478 - Fix a seg fault with autodetecting which controller version is
5482 - New hidden service descriptor format: put a version in it, and
5483 let people specify introduction/rendezvous points that aren't
5484 in "the directory" (which is subjective anyway).
5485 - Allow the DEBUG controller event to work again. Mark certain log
5486 entries as "don't tell this to controllers", so we avoid cycles.
5489 Changes in version 0.1.0.11 - 2005-06-30
5490 o Bugfixes on 0.1.0.x:
5491 - Fix major security bug: servers were disregarding their
5492 exit policies if clients behaved unexpectedly.
5493 - Make OS X init script check for missing argument, so we don't
5494 confuse users who invoke it incorrectly.
5495 - Fix a seg fault in "tor --hash-password foo".
5496 - The MAPADDRESS control command was broken.
5499 Changes in version 0.1.1.1-alpha - 2005-06-29
5501 - Make OS X init script check for missing argument, so we don't
5502 confuse users who invoke it incorrectly.
5503 - Fix a seg fault in "tor --hash-password foo".
5504 - Fix a possible way to DoS dirservers.
5505 - When we complain that your exit policy implicitly allows local or
5506 private address spaces, name them explicitly so operators can
5508 - Make the log message less scary when all the dirservers are
5509 temporarily unreachable.
5510 - We were printing the number of idle dns workers incorrectly when
5514 - Revised controller protocol (version 1) that uses ascii rather
5515 than binary. Add supporting libraries in python and java so you
5516 can use the controller from your applications without caring how
5518 - Spiffy new support for crypto hardware accelerators. Can somebody
5522 Changes in version 0.0.9.10 - 2005-06-16
5523 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
5524 - Refuse relay cells that claim to have a length larger than the
5525 maximum allowed. This prevents a potential attack that could read
5526 arbitrary memory (e.g. keys) from an exit server's process
5530 Changes in version 0.1.0.10 - 2005-06-14
5531 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
5532 libevent before 1.1a.
5535 Changes in version 0.1.0.9-rc - 2005-06-09
5537 - Reset buf->highwater every time buf_shrink() is called, not just on
5538 a successful shrink. This was causing significant memory bloat.
5539 - Fix buffer overflow when checking hashed passwords.
5540 - Security fix: if seeding the RNG on Win32 fails, quit.
5541 - Allow seeding the RNG on Win32 even when you're not running as
5543 - Disable threading on Solaris too. Something is wonky with it,
5544 cpuworkers, and reentrant libs.
5545 - Reenable the part of the code that tries to flush as soon as an
5546 OR outbuf has a full TLS record available. Perhaps this will make
5547 OR outbufs not grow as huge except in rare cases, thus saving lots
5548 of CPU time plus memory.
5549 - Reject malformed .onion addresses rather then passing them on as
5550 normal web requests.
5551 - Adapt patch from Adam Langley: fix possible memory leak in
5552 tor_lookup_hostname().
5553 - Initialize libevent later in the startup process, so the logs are
5554 already established by the time we start logging libevent warns.
5555 - Use correct errno on win32 if libevent fails.
5556 - Check and warn about known-bad/slow libevent versions.
5557 - Pay more attention to the ClientOnly config option.
5558 - Have torctl.in/tor.sh.in check for location of su binary (needed
5560 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
5561 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
5562 HttpProxyAuthenticator
5563 - Stop warning about sigpipes in the logs. We're going to
5564 pretend that getting these occassionally is normal and fine.
5565 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
5567 installer screens; and don't put stuff into StartupItems unless
5568 the user asks you to.
5569 - Require servers that use the default dirservers to have public IP
5570 addresses. We have too many servers that are configured with private
5571 IPs and their admins never notice the log entries complaining that
5572 their descriptors are being rejected.
5573 - Add OSX uninstall instructions. An actual uninstall script will
5577 Changes in version 0.1.0.8-rc - 2005-05-23
5579 - It turns out that kqueue on OS X 10.3.9 was causing kernel
5580 panics. Disable kqueue on all OS X Tors.
5581 - Fix RPM: remove duplicate line accidentally added to the rpm
5583 - Disable threads on openbsd too, since its gethostaddr is not
5585 - Tolerate libevent 0.8 since it still works, even though it's
5587 - Enable building on Red Hat 9.0 again.
5588 - Allow the middle hop of the testing circuit to be running any
5589 version, now that most of them have the bugfix to let them connect
5590 to unknown servers. This will allow reachability testing to work
5591 even when 0.0.9.7-0.0.9.9 become obsolete.
5592 - Handle relay cells with rh.length too large. This prevents
5593 a potential attack that could read arbitrary memory (maybe even
5594 keys) from the exit server's process.
5595 - We screwed up the dirport reachability testing when we don't yet
5596 have a cached version of the directory. Hopefully now fixed.
5597 - Clean up router_load_single_router() (used by the controller),
5598 so it doesn't seg fault on error.
5599 - Fix a minor memory leak when somebody establishes an introduction
5600 point at your Tor server.
5601 - If a socks connection ends because read fails, don't warn that
5602 you're not sending a socks reply back.
5605 - Add HttpProxyAuthenticator config option too, that works like
5606 the HttpsProxyAuthenticator config option.
5607 - Encode hashed controller passwords in hex instead of base64,
5608 to make it easier to write controllers.
5611 Changes in version 0.1.0.7-rc - 2005-05-17
5613 - Fix a bug in the OS X package installer that prevented it from
5614 installing on Tiger.
5615 - Fix a script bug in the OS X package installer that made it
5616 complain during installation.
5617 - Find libevent even if it's hiding in /usr/local/ and your
5618 CFLAGS and LDFLAGS don't tell you to look there.
5619 - Be able to link with libevent as a shared library (the default
5620 after 1.0d), even if it's hiding in /usr/local/lib and even
5621 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
5622 assuming you're running gcc. Otherwise fail and give a useful
5624 - Fix a bug in the RPM packager: set home directory for _tor to
5625 something more reasonable when first installing.
5626 - Free a minor amount of memory that is still reachable on exit.
5629 Changes in version 0.1.0.6-rc - 2005-05-14
5631 - Implement --disable-threads configure option. Disable threads on
5632 netbsd by default, because it appears to have no reentrant resolver
5634 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
5635 release (1.1) detects and disables kqueue if it's broken.
5636 - Append default exit policy before checking for implicit internal
5637 addresses. Now we don't log a bunch of complaints on startup
5638 when using the default exit policy.
5639 - Some people were putting "Address " in their torrc, and they had
5640 a buggy resolver that resolved " " to 0.0.0.0. Oops.
5641 - If DataDir is ~/.tor, and that expands to /.tor, then default to
5642 LOCALSTATEDIR/tor instead.
5643 - Fix fragmented-message bug in TorControl.py.
5644 - Resolve a minor bug which would prevent unreachable dirports
5645 from getting suppressed in the published descriptor.
5646 - When the controller gave us a new descriptor, we weren't resolving
5647 it immediately, so Tor would think its address was 0.0.0.0 until
5648 we fetched a new directory.
5649 - Fix an uppercase/lowercase case error in suppressing a bogus
5650 libevent warning on some Linuxes.
5653 - Begin scrubbing sensitive strings from logs by default. Turn off
5654 the config option SafeLogging if you need to do debugging.
5655 - Switch to a new buffer management algorithm, which tries to avoid
5656 reallocing and copying quite as much. In first tests it looks like
5657 it uses *more* memory on average, but less cpu.
5658 - First cut at support for "create-fast" cells. Clients can use
5659 these when extending to their first hop, since the TLS already
5660 provides forward secrecy and authentication. Not enabled on
5662 - When dirservers refuse a router descriptor, we now log its
5663 contactinfo, platform, and the poster's IP address.
5664 - Call tor_free_all instead of connections_free_all after forking, to
5665 save memory on systems that need to fork.
5666 - Whine at you if you're a server and you don't set your contactinfo.
5667 - Implement --verify-config command-line option to check if your torrc
5668 is valid without actually launching Tor.
5669 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
5670 rather than just rejecting it.
5673 Changes in version 0.1.0.5-rc - 2005-04-27
5675 - Stop trying to print a null pointer if an OR conn fails because
5676 we didn't like its cert.
5678 - Switch our internal buffers implementation to use a ring buffer,
5679 to hopefully improve performance for fast servers a lot.
5680 - Add HttpsProxyAuthenticator support (basic auth only), based
5681 on patch from Adam Langley.
5682 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
5683 the fast servers that have been joining lately.
5684 - Give hidden service accesses extra time on the first attempt,
5685 since 60 seconds is often only barely enough. This might improve
5687 - Improve performance for dirservers: stop re-parsing the whole
5688 directory every time you regenerate it.
5689 - Add more debugging info to help us find the weird dns freebsd
5690 pthreads bug; cleaner debug messages to help track future issues.
5693 Changes in version 0.0.9.9 - 2005-04-23
5694 o Bugfixes on 0.0.9.x:
5695 - If unofficial Tor clients connect and send weird TLS certs, our
5696 Tor server triggers an assert. This release contains a minimal
5697 backport from the broader fix that we put into 0.1.0.4-rc.
5700 Changes in version 0.1.0.4-rc - 2005-04-23
5702 - If unofficial Tor clients connect and send weird TLS certs, our
5703 Tor server triggers an assert. Stop asserting, and start handling
5704 TLS errors better in other situations too.
5705 - When the controller asks us to tell it about all the debug-level
5706 logs, it turns out we were generating debug-level logs while
5707 telling it about them, which turns into a bad loop. Now keep
5708 track of whether you're sending a debug log to the controller,
5709 and don't log when you are.
5710 - Fix the "postdescriptor" feature of the controller interface: on
5711 non-complete success, only say "done" once.
5713 - Clients are now willing to load balance over up to 2mB, not 1mB,
5714 of advertised bandwidth capacity.
5715 - Add a NoPublish config option, so you can be a server (e.g. for
5716 testing running Tor servers in other Tor networks) without
5717 publishing your descriptor to the primary dirservers.
5720 Changes in version 0.1.0.3-rc - 2005-04-08
5721 o Improvements on 0.1.0.2-rc:
5722 - Client now retries when streams end early for 'hibernating' or
5723 'resource limit' reasons, rather than failing them.
5724 - More automated handling for dirserver operators:
5725 - Automatically approve nodes running 0.1.0.2-rc or later,
5726 now that the the reachability detection stuff is working.
5727 - Now we allow two unverified servers with the same nickname
5728 but different keys. But if a nickname is verified, only that
5729 nickname+key are allowed.
5730 - If you're an authdirserver connecting to an address:port,
5731 and it's not the OR you were expecting, forget about that
5732 descriptor. If he *was* the one you were expecting, then forget
5733 about all other descriptors for that address:port.
5734 - Allow servers to publish descriptors from 12 hours in the future.
5735 Corollary: only whine about clock skew from the dirserver if
5736 he's a trusted dirserver (since now even verified servers could
5737 have quite wrong clocks).
5738 - Adjust maximum skew and age for rendezvous descriptors: let skew
5739 be 48 hours rather than 90 minutes.
5740 - Efficiency improvements:
5741 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
5742 it much faster to look up a circuit for each relay cell.
5743 - Remove most calls to assert_all_pending_dns_resolves_ok(),
5744 since they're eating our cpu on exit nodes.
5745 - Stop wasting time doing a case insensitive comparison for every
5746 dns name every time we do any lookup. Canonicalize the names to
5747 lowercase and be done with it.
5748 - Start sending 'truncated' cells back rather than destroy cells,
5749 if the circuit closes in front of you. This means we won't have
5750 to abandon partially built circuits.
5751 - Only warn once per nickname from add_nickname_list_to_smartlist
5752 per failure, so an entrynode or exitnode choice that's down won't
5754 - Put a note in the torrc about abuse potential with the default
5756 - Revise control spec and implementation to allow all log messages to
5757 be sent to controller with their severities intact (suggested by
5758 Matt Edman). Update TorControl to handle new log event types.
5759 - Provide better explanation messages when controller's POSTDESCRIPTOR
5761 - Stop putting nodename in the Platform string in server descriptors.
5762 It doesn't actually help, and it is confusing/upsetting some people.
5764 o Bugfixes on 0.1.0.2-rc:
5765 - We were printing the host mask wrong in exit policies in server
5766 descriptors. This isn't a critical bug though, since we were still
5767 obeying the exit policy internally.
5768 - Fix Tor when compiled with libevent but without pthreads: move
5769 connection_unregister() from _connection_free() to
5771 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
5772 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
5773 when we look through the connection array, we'll find any of the
5774 cpu/dnsworkers. This is no good.
5776 o Bugfixes on 0.0.9.8:
5777 - Fix possible bug on threading platforms (e.g. win32) which was
5778 leaking a file descriptor whenever a cpuworker or dnsworker died.
5779 - When using preferred entry or exit nodes, ignore whether the
5780 circuit wants uptime or capacity. They asked for the nodes, they
5782 - chdir() to your datadirectory at the *end* of the daemonize process,
5783 not the beginning. This was a problem because the first time you
5784 run tor, if your datadir isn't there, and you have runasdaemon set
5785 to 1, it will try to chdir to it before it tries to create it. Oops.
5786 - Handle changed router status correctly when dirserver reloads
5787 fingerprint file. We used to be dropping all unverified descriptors
5788 right then. The bug was hidden because we would immediately
5789 fetch a directory from another dirserver, which would include the
5790 descriptors we just dropped.
5791 - When we're connecting to an OR and he's got a different nickname/key
5792 than we were expecting, only complain loudly if we're an OP or a
5793 dirserver. Complaining loudly to the OR admins just confuses them.
5794 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
5795 artificially capped at 500kB.
5798 Changes in version 0.0.9.8 - 2005-04-07
5799 o Bugfixes on 0.0.9.x:
5800 - We have a bug that I haven't found yet. Sometimes, very rarely,
5801 cpuworkers get stuck in the 'busy' state, even though the cpuworker
5802 thinks of itself as idle. This meant that no new circuits ever got
5803 established. Here's a workaround to kill any cpuworker that's been
5804 busy for more than 100 seconds.
5807 Changes in version 0.1.0.2-rc - 2005-04-01
5808 o Bugfixes on 0.1.0.1-rc:
5809 - Fixes on reachability detection:
5810 - Don't check for reachability while hibernating.
5811 - If ORPort is reachable but DirPort isn't, still publish the
5812 descriptor, but zero out DirPort until it's found reachable.
5813 - When building testing circs for ORPort testing, use only
5814 high-bandwidth nodes, so fewer circuits fail.
5815 - Complain about unreachable ORPort separately from unreachable
5816 DirPort, so the user knows what's going on.
5817 - Make sure we only conclude ORPort reachability if we didn't
5818 initiate the conn. Otherwise we could falsely conclude that
5819 we're reachable just because we connected to the guy earlier
5820 and he used that same pipe to extend to us.
5821 - Authdirservers shouldn't do ORPort reachability detection,
5822 since they're in clique mode, so it will be rare to find a
5823 server not already connected to them.
5824 - When building testing circuits, always pick middle hops running
5825 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
5826 bug. (This is a kludge; it will go away when 0.0.9.x becomes
5828 - When we decide we're reachable, actually publish our descriptor
5830 - Fix bug in redirectstream in the controller.
5831 - Fix the state descriptor strings so logs don't claim edge streams
5832 are in a different state than they actually are.
5833 - Use recent libevent features when possible (this only really affects
5834 win32 and osx right now, because the new libevent with these
5835 features hasn't been released yet). Add code to suppress spurious
5837 - Prevent possible segfault in connection_close_unattached_ap().
5838 - Fix newlines on torrc in win32.
5839 - Improve error msgs when tor-resolve fails.
5841 o Improvements on 0.0.9.x:
5842 - New experimental script tor/contrib/ExerciseServer.py (needs more
5843 work) that uses the controller interface to build circuits and
5844 fetch pages over them. This will help us bootstrap servers that
5845 have lots of capacity but haven't noticed it yet.
5846 - New experimental script tor/contrib/PathDemo.py (needs more work)
5847 that uses the controller interface to let you choose whole paths
5849 "<hostname>.<path,separated by dots>.<length of path>.path"
5850 - When we've connected to an OR and handshaked but didn't like
5851 the result, we were closing the conn without sending destroy
5852 cells back for pending circuits. Now send those destroys.
5855 Changes in version 0.0.9.7 - 2005-04-01
5856 o Bugfixes on 0.0.9.x:
5857 - Fix another race crash bug (thanks to Glenn Fink for reporting).
5858 - Compare identity to identity, not to nickname, when extending to
5859 a router not already in the directory. This was preventing us from
5860 extending to unknown routers. Oops.
5861 - Make sure to create OS X Tor user in <500 range, so we aren't
5862 creating actual system users.
5863 - Note where connection-that-hasn't-sent-end was marked, and fix
5864 a few really loud instances of this harmless bug (it's fixed more
5868 Changes in version 0.1.0.1-rc - 2005-03-28
5870 - Add reachability testing. Your Tor server will automatically try
5871 to see if its ORPort and DirPort are reachable from the outside,
5872 and it won't upload its descriptor until it decides they are.
5873 - Handle unavailable hidden services better. Handle slow or busy
5874 hidden services better.
5875 - Add support for CONNECTing through https proxies, with "HttpsProxy"
5877 - New exit policy: accept most low-numbered ports, rather than
5878 rejecting most low-numbered ports.
5879 - More Tor controller support (still experimental). See
5880 http://tor.eff.org/doc/control-spec.txt for all the new features,
5881 including signals to emulate unix signals from any platform;
5882 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
5883 closestream; closecircuit; etc.
5884 - Make nt services work and start on startup on win32 (based on
5885 patch by Matt Edman).
5886 - Add a new AddressMap config directive to rewrite incoming socks
5887 addresses. This lets you, for example, declare an implicit
5888 required exit node for certain sites.
5889 - Add a new TrackHostExits config directive to trigger addressmaps
5890 for certain incoming socks addresses -- for sites that break when
5891 your exit keeps changing (based on patch by Mike Perry).
5892 - Redo the client-side dns cache so it's just an addressmap too.
5893 - Notice when our IP changes, and reset stats/uptime/reachability.
5894 - When an application is using socks5, give him the whole variety of
5895 potential socks5 responses (connect refused, host unreachable, etc),
5896 rather than just "success" or "failure".
5897 - A more sane version numbering system. See
5898 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
5899 - New contributed script "exitlist": a simple python script to
5900 parse directories and find Tor nodes that exit to listed
5902 - New contributed script "privoxy-tor-toggle" to toggle whether
5903 Privoxy uses Tor. Seems to be configured for Debian by default.
5904 - Report HTTP reasons to client when getting a response from directory
5905 servers -- so you can actually know what went wrong.
5906 - New config option MaxAdvertisedBandwidth which lets you advertise
5907 a low bandwidthrate (to not attract as many circuits) while still
5908 allowing a higher bandwidthrate in reality.
5910 o Robustness/stability fixes:
5911 - Make Tor use Niels Provos's libevent instead of its current
5912 poll-but-sometimes-select mess. This will let us use faster async
5913 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
5915 - pthread support now too. This was forced because when we forked,
5916 we ended up wasting a lot of duplicate ram over time. Also switch
5917 to foo_r versions of some library calls to allow reentry and
5919 - Better handling for heterogeneous / unreliable nodes:
5920 - Annotate circuits w/ whether they aim to contain high uptime nodes
5921 and/or high capacity nodes. When building circuits, choose
5923 - This means that every single node in an intro rend circuit,
5924 not just the last one, will have a minimum uptime.
5925 - New config option LongLivedPorts to indicate application streams
5926 that will want high uptime circuits.
5927 - Servers reset uptime when a dir fetch entirely fails. This
5928 hopefully reflects stability of the server's network connectivity.
5929 - If somebody starts his tor server in Jan 2004 and then fixes his
5930 clock, don't make his published uptime be a year.
5931 - Reset published uptime when you wake up from hibernation.
5932 - Introduce a notion of 'internal' circs, which are chosen without
5933 regard to the exit policy of the last hop. Intro and rendezvous
5934 circs must be internal circs, to avoid leaking information. Resolve
5935 and connect streams can use internal circs if they want.
5936 - New circuit pooling algorithm: make sure to have enough circs around
5937 to satisfy any predicted ports, and also make sure to have 2 internal
5938 circs around if we've required internal circs lately (and with high
5939 uptime if we've seen that lately too).
5940 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
5941 which describes how often we retry making new circuits if current
5942 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
5943 how long we're willing to make use of an already-dirty circuit.
5944 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
5945 circ as necessary, if there are any completed ones lying around
5946 when we try to launch one.
5947 - Make hidden services try to establish a rendezvous for 30 seconds,
5948 rather than for n (where n=3) attempts to build a circuit.
5949 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
5950 "ShutdownWaitLength".
5951 - Try to be more zealous about calling connection_edge_end when
5952 things go bad with edge conns in connection.c.
5953 - Revise tor-spec to add more/better stream end reasons.
5954 - Revise all calls to connection_edge_end to avoid sending "misc",
5955 and to take errno into account where possible.
5958 - Fix a race condition that can trigger an assert, when we have a
5959 pending create cell and an OR connection fails right then.
5960 - Fix several double-mark-for-close bugs, e.g. where we were finding
5961 a conn for a cell even if that conn is already marked for close.
5962 - Make sequence of log messages when starting on win32 with no config
5963 file more reasonable.
5964 - When choosing an exit node for a new non-internal circ, don't take
5965 into account whether it'll be useful for any pending x.onion
5966 addresses -- it won't.
5967 - Turn addr_policy_compare from a tristate to a quadstate; this should
5968 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
5969 for google.com" problem.
5970 - Make "platform" string in descriptor more accurate for Win32 servers,
5971 so it's not just "unknown platform".
5972 - Fix an edge case in parsing config options (thanks weasel).
5973 If they say "--" on the commandline, it's not an option.
5974 - Reject odd-looking addresses at the client (e.g. addresses that
5975 contain a colon), rather than having the server drop them because
5977 - tor-resolve requests were ignoring .exit if there was a working circuit
5978 they could use instead.
5979 - REUSEADDR on normal platforms means you can rebind to the port
5980 right after somebody else has let it go. But REUSEADDR on win32
5981 means to let you bind to the port _even when somebody else
5982 already has it bound_! So, don't do that on Win32.
5983 - Change version parsing logic: a version is "obsolete" if it is not
5984 recommended and (1) there is a newer recommended version in the
5985 same series, or (2) there are no recommended versions in the same
5986 series, but there are some recommended versions in a newer series.
5987 A version is "new" if it is newer than any recommended version in
5989 - Stop most cases of hanging up on a socks connection without sending
5993 - Require BandwidthRate to be at least 20kB/s for servers.
5994 - When a dirserver causes you to give a warn, mention which dirserver
5996 - New config option DirAllowPrivateAddresses for authdirservers.
5997 Now by default they refuse router descriptors that have non-IP or
5998 private-IP addresses.
5999 - Stop publishing socksport in the directory, since it's not
6000 actually meant to be public. For compatibility, publish a 0 there
6002 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
6003 smart" value, that is low for servers and high for clients.
6004 - If our clock jumps forward by 100 seconds or more, assume something
6005 has gone wrong with our network and abandon all not-yet-used circs.
6006 - Warn when exit policy implicitly allows local addresses.
6007 - If we get an incredibly skewed timestamp from a dirserver mirror
6008 that isn't a verified OR, don't warn -- it's probably him that's
6010 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
6011 cookies to disk and doesn't log each web request to disk. (Thanks
6012 to Brett Carrington for pointing this out.)
6013 - When a client asks us for a dir mirror and we don't have one,
6014 launch an attempt to get a fresh one.
6015 - If we're hibernating and we get a SIGINT, exit immediately.
6016 - Add --with-dmalloc ./configure option, to track memory leaks.
6017 - And try to free all memory on closing, so we can detect what
6019 - Cache local dns resolves correctly even when they're .exit
6021 - Give a better warning when some other server advertises an
6022 ORPort that is actually an apache running ssl.
6023 - Add "opt hibernating 1" to server descriptor to make it clearer
6024 whether the server is hibernating.
6027 Changes in version 0.0.9.6 - 2005-03-24
6028 o Bugfixes on 0.0.9.x (crashes and asserts):
6029 - Add new end stream reasons to maintainance branch. Fix bug where
6030 reason (8) could trigger an assert. Prevent bug from recurring.
6031 - Apparently win32 stat wants paths to not end with a slash.
6032 - Fix assert triggers in assert_cpath_layer_ok(), where we were
6033 blowing away the circuit that conn->cpath_layer points to, then
6034 checking to see if the circ is well-formed. Backport check to make
6035 sure we dont use the cpath on a closed connection.
6036 - Prevent circuit_resume_edge_reading_helper() from trying to package
6037 inbufs for marked-for-close streams.
6038 - Don't crash on hup if your options->address has become unresolvable.
6039 - Some systems (like OS X) sometimes accept() a connection and tell
6040 you the remote host is 0.0.0.0:0. If this happens, due to some
6041 other mis-features, we get confused; so refuse the conn for now.
6043 o Bugfixes on 0.0.9.x (other):
6044 - Fix harmless but scary "Unrecognized content encoding" warn message.
6045 - Add new stream error reason: TORPROTOCOL reason means "you are not
6046 speaking a version of Tor I understand; say bye-bye to your stream."
6047 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
6048 into the future, now that we are more tolerant of skew. This
6049 resolves a bug where a Tor server would refuse to cache a directory
6050 because all the directories it gets are too far in the future;
6051 yet the Tor server never logs any complaints about clock skew.
6052 - Mac packaging magic: make man pages useable, and do not overwrite
6053 existing torrc files.
6054 - Make OS X log happily to /var/log/tor/tor.log
6057 Changes in version 0.0.9.5 - 2005-02-22
6058 o Bugfixes on 0.0.9.x:
6059 - Fix an assert race at exit nodes when resolve requests fail.
6060 - Stop picking unverified dir mirrors--it only leads to misery.
6061 - Patch from Matt Edman to make NT services work better. Service
6062 support is still not compiled into the executable by default.
6063 - Patch from Dmitri Bely so the Tor service runs better under
6064 the win32 SYSTEM account.
6065 - Make tor-resolve actually work (?) on Win32.
6066 - Fix a sign bug when getrlimit claims to have 4+ billion
6067 file descriptors available.
6068 - Stop refusing to start when bandwidthburst == bandwidthrate.
6069 - When create cells have been on the onion queue more than five
6070 seconds, just send back a destroy and take them off the list.
6073 Changes in version 0.0.9.4 - 2005-02-03
6074 o Bugfixes on 0.0.9:
6075 - Fix an assert bug that took down most of our servers: when
6076 a server claims to have 1 GB of bandwidthburst, don't
6078 - Don't crash as badly if we have spawned the max allowed number
6079 of dnsworkers, or we're out of file descriptors.
6080 - Block more file-sharing ports in the default exit policy.
6081 - MaxConn is now automatically set to the hard limit of max
6082 file descriptors we're allowed (ulimit -n), minus a few for
6084 - Give a clearer message when servers need to raise their
6085 ulimit -n when they start running out of file descriptors.
6086 - SGI Compatibility patches from Jan Schaumann.
6087 - Tolerate a corrupt cached directory better.
6088 - When a dirserver hasn't approved your server, list which one.
6089 - Go into soft hibernation after 95% of the bandwidth is used,
6090 not 99%. This is especially important for daily hibernators who
6091 have a small accounting max. Hopefully it will result in fewer
6092 cut connections when the hard hibernation starts.
6093 - Load-balance better when using servers that claim more than
6094 800kB/s of capacity.
6095 - Make NT services work (experimental, only used if compiled in).
6098 Changes in version 0.0.9.3 - 2005-01-21
6099 o Bugfixes on 0.0.9:
6100 - Backport the cpu use fixes from main branch, so busy servers won't
6101 need as much processor time.
6102 - Work better when we go offline and then come back, or when we
6103 run Tor at boot before the network is up. We do this by
6104 optimistically trying to fetch a new directory whenever an
6105 application request comes in and we think we're offline -- the
6106 human is hopefully a good measure of when the network is back.
6107 - Backport some minimal hidserv bugfixes: keep rend circuits open as
6108 long as you keep using them; actually publish hidserv descriptors
6109 shortly after they change, rather than waiting 20-40 minutes.
6110 - Enable Mac startup script by default.
6111 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
6112 - When you update AllowUnverifiedNodes or FirewallPorts via the
6113 controller's setconf feature, we were always appending, never
6115 - When you update HiddenServiceDir via setconf, it was screwing up
6116 the order of reading the lines, making it fail.
6117 - Do not rewrite a cached directory back to the cache; otherwise we
6118 will think it is recent and not fetch a newer one on startup.
6119 - Workaround for webservers that lie about Content-Encoding: Tor
6120 now tries to autodetect compressed directories and compression
6121 itself. This lets us Proxypass dir fetches through apache.
6124 Changes in version 0.0.9.2 - 2005-01-04
6125 o Bugfixes on 0.0.9 (crashes and asserts):
6126 - Fix an assert on startup when the disk is full and you're logging
6128 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
6129 style address, then we'd crash.
6130 - Fix an assert trigger when the running-routers string we get from
6131 a dirserver is broken.
6132 - Make worker threads start and run on win32. Now win32 servers
6134 - Bandaid (not actually fix, but now it doesn't crash) an assert
6135 where the dns worker dies mysteriously and the main Tor process
6136 doesn't remember anything about the address it was resolving.
6138 o Bugfixes on 0.0.9 (Win32):
6139 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
6140 name out of the warning/assert messages.
6141 - Fix a superficial "unhandled error on read" bug on win32.
6142 - The win32 installer no longer requires a click-through for our
6143 license, since our Free Software license grants rights but does not
6145 - Win32: When connecting to a dirserver fails, try another one
6146 immediately. (This was already working for non-win32 Tors.)
6147 - Stop trying to parse $HOME on win32 when hunting for default
6149 - Make tor-resolve.c work on win32 by calling network_init().
6151 o Bugfixes on 0.0.9 (other):
6152 - Make 0.0.9.x build on Solaris again.
6153 - Due to a fencepost error, we were blowing away the \n when reporting
6154 confvalue items in the controller. So asking for multiple config
6155 values at once couldn't work.
6156 - When listing circuits that are pending on an opening OR connection,
6157 if we're an OR we were listing circuits that *end* at us as
6158 being pending on every listener, dns/cpu worker, etc. Stop that.
6159 - Dirservers were failing to create 'running-routers' or 'directory'
6160 strings if we had more than some threshold of routers. Fix them so
6161 they can handle any number of routers.
6162 - Fix a superficial "Duplicate mark for close" bug.
6163 - Stop checking for clock skew for OR connections, even for servers.
6164 - Fix a fencepost error that was chopping off the last letter of any
6165 nickname that is the maximum allowed nickname length.
6166 - Update URLs in log messages so they point to the new website.
6167 - Fix a potential problem in mangling server private keys while
6168 writing to disk (not triggered yet, as far as we know).
6169 - Include the licenses for other free software we include in Tor,
6170 now that we're shipping binary distributions more regularly.
6173 Changes in version 0.0.9.1 - 2004-12-15
6174 o Bugfixes on 0.0.9:
6175 - Make hibernation actually work.
6176 - Make HashedControlPassword config option work.
6177 - When we're reporting event circuit status to a controller,
6178 don't use the stream status code.
6181 Changes in version 0.0.9 - 2004-12-12
6183 - Clean up manpage and torrc.sample file.
6184 - Clean up severities and text of log warnings.
6186 - Make servers trigger an assert when they enter hibernation.
6189 Changes in version 0.0.9rc7 - 2004-12-08
6190 o Bugfixes on 0.0.9rc:
6191 - Fix a stack-trashing crash when an exit node begins hibernating.
6192 - Avoid looking at unallocated memory while considering which
6193 ports we need to build circuits to cover.
6194 - Stop a sigpipe: when an 'end' cell races with eof from the app,
6195 we shouldn't hold-open-until-flush if the eof arrived first.
6196 - Fix a bug with init_cookie_authentication() in the controller.
6197 - When recommending new-format log lines, if the upper bound is
6198 LOG_ERR, leave it implicit.
6200 o Bugfixes on 0.0.8.1:
6201 - Fix a whole slew of memory leaks.
6202 - Fix isspace() and friends so they still make Solaris happy
6203 but also so they don't trigger asserts on win32.
6204 - Fix parse_iso_time on platforms without strptime (eg win32).
6205 - win32: tolerate extra "readable" events better.
6206 - win32: when being multithreaded, leave parent fdarray open.
6207 - Make unit tests work on win32.
6210 Changes in version 0.0.9rc6 - 2004-12-06
6211 o Bugfixes on 0.0.9pre:
6212 - Clean up some more integer underflow opportunities (not exploitable
6214 - While hibernating, hup should not regrow our listeners.
6215 - Send an end to the streams we close when we hibernate, rather
6216 than just chopping them off.
6217 - React to eof immediately on non-open edge connections.
6219 o Bugfixes on 0.0.8.1:
6220 - Calculate timeout for waiting for a connected cell from the time
6221 we sent the begin cell, not from the time the stream started. If
6222 it took a long time to establish the circuit, we would time out
6223 right after sending the begin cell.
6224 - Fix router_compare_addr_to_addr_policy: it was not treating a port
6225 of * as always matching, so we were picking reject *:* nodes as
6226 exit nodes too. Oops.
6229 - New circuit building strategy: keep a list of ports that we've
6230 used in the past 6 hours, and always try to have 2 circuits open
6231 or on the way that will handle each such port. Seed us with port
6232 80 so web users won't complain that Tor is "slow to start up".
6233 - Make kill -USR1 dump more useful stats about circuits.
6234 - When warning about retrying or giving up, print the address, so
6235 the user knows which one it's talking about.
6236 - If you haven't used a clean circuit in an hour, throw it away,
6237 just to be on the safe side. (This means after 6 hours a totally
6238 unused Tor client will have no circuits open.)
6241 Changes in version 0.0.9rc5 - 2004-12-01
6242 o Bugfixes on 0.0.8.1:
6243 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
6244 - Let resolve conns retry/expire also, rather than sticking around
6246 - If we are using select, make sure we stay within FD_SETSIZE.
6248 o Bugfixes on 0.0.9pre:
6249 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
6250 but doesn't seem to be currently; thanks to Ilja van Sprundel for
6252 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
6253 instead. Impose minima and maxima for all *Period options; impose
6254 even tighter maxima for fetching if we are a caching dirserver.
6255 Clip rather than rejecting.
6256 - Fetch cached running-routers from servers that serve it (that is,
6257 authdirservers and servers running 0.0.9rc5-cvs or later.)
6260 - Accept *:706 (silc) in default exit policy.
6261 - Implement new versioning format for post 0.1.
6262 - Support "foo.nickname.exit" addresses, to let Alice request the
6263 address "foo" as viewed by exit node "nickname". Based on a patch
6265 - Make tor --version --version dump the cvs Id of every file.
6268 Changes in version 0.0.9rc4 - 2004-11-28
6269 o Bugfixes on 0.0.8.1:
6270 - Make windows sockets actually non-blocking (oops), and handle
6271 win32 socket errors better.
6273 o Bugfixes on 0.0.9rc1:
6274 - Actually catch the -USR2 signal.
6277 Changes in version 0.0.9rc3 - 2004-11-25
6278 o Bugfixes on 0.0.8.1:
6279 - Flush the log file descriptor after we print "Tor opening log file",
6280 so we don't see those messages days later.
6282 o Bugfixes on 0.0.9rc1:
6283 - Make tor-resolve work again.
6284 - Avoid infinite loop in tor-resolve if tor hangs up on it.
6285 - Fix an assert trigger for clients/servers handling resolves.
6288 Changes in version 0.0.9rc2 - 2004-11-24
6289 o Bugfixes on 0.0.9rc1:
6290 - I broke socks5 support while fixing the eof bug.
6291 - Allow unitless bandwidths and intervals; they default to bytes
6293 - New servers don't start out hibernating; they are active until
6294 they run out of bytes, so they have a better estimate of how
6295 long it takes, and so their operators can know they're working.
6298 Changes in version 0.0.9rc1 - 2004-11-23
6299 o Bugfixes on 0.0.8.1:
6300 - Finally fix a bug that's been plaguing us for a year:
6301 With high load, circuit package window was reaching 0. Whenever
6302 we got a circuit-level sendme, we were reading a lot on each
6303 socket, but only writing out a bit. So we would eventually reach
6304 eof. This would be noticed and acted on even when there were still
6305 bytes sitting in the inbuf.
6306 - When poll() is interrupted, we shouldn't believe the revents values.
6308 o Bugfixes on 0.0.9pre6:
6309 - Fix hibernate bug that caused pre6 to be broken.
6310 - Don't keep rephist info for routers that haven't had activity for
6311 24 hours. (This matters now that clients have keys, since we track
6313 - Never call close_temp_logs while validating log options.
6314 - Fix backslash-escaping on tor.sh.in and torctl.in.
6317 - Implement weekly/monthly/daily accounting: now you specify your
6318 hibernation properties by
6319 AccountingMax N bytes|KB|MB|GB|TB
6320 AccountingStart day|week|month [day] HH:MM
6321 Defaults to "month 1 0:00".
6322 - Let bandwidth and interval config options be specified as 5 bytes,
6323 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
6324 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
6325 get back to normal.)
6326 - If your requested entry or exit node has advertised bandwidth 0,
6328 - Be more greedy about filling up relay cells -- we try reading again
6329 once we've processed the stuff we read, in case enough has arrived
6330 to fill the last cell completely.
6331 - Apply NT service patch from Osamu Fujino. Still needs more work.
6334 Changes in version 0.0.9pre6 - 2004-11-15
6335 o Bugfixes on 0.0.8.1:
6336 - Fix assert failure on malformed socks4a requests.
6337 - Use identity comparison, not nickname comparison, to choose which
6338 half of circuit-ID-space each side gets to use. This is needed
6339 because sometimes we think of a router as a nickname, and sometimes
6340 as a hex ID, and we can't predict what the other side will do.
6341 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
6342 write() call will fail and we handle it there.
6343 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
6344 and smartlist_len, which are two major profiling offenders.
6346 o Bugfixes on 0.0.9pre5:
6347 - Fix a bug in read_all that was corrupting config files on windows.
6348 - When we're raising the max number of open file descriptors to
6349 'unlimited', don't log that we just raised it to '-1'.
6350 - Include event code with events, as required by control-spec.txt.
6351 - Don't give a fingerprint when clients do --list-fingerprint:
6352 it's misleading, because it will never be the same again.
6353 - Stop using strlcpy in tor_strndup, since it was slowing us
6355 - Remove warn on startup about missing cached-directory file.
6356 - Make kill -USR1 work again.
6357 - Hibernate if we start tor during the "wait for wakeup-time" phase
6358 of an accounting interval. Log our hibernation plans better.
6359 - Authoritative dirservers now also cache their directory, so they
6360 have it on start-up.
6363 - Fetch running-routers; cache running-routers; compress
6364 running-routers; serve compressed running-routers.z
6365 - Add NSI installer script contributed by J Doe.
6366 - Commit VC6 and VC7 workspace/project files.
6367 - Commit a tor.spec for making RPM files, with help from jbash.
6368 - Add contrib/torctl.in contributed by Glenn Fink.
6369 - Implement the control-spec's SAVECONF command, to write your
6370 configuration to torrc.
6371 - Get cookie authentication for the controller closer to working.
6372 - Include control-spec.txt in the tarball.
6373 - When set_conf changes our server descriptor, upload a new copy.
6374 But don't upload it too often if there are frequent changes.
6375 - Document authentication config in man page, and document signals
6377 - Clean up confusing parts of man page and torrc.sample.
6378 - Make expand_filename handle ~ and ~username.
6379 - Use autoconf to enable largefile support where necessary. Use
6380 ftello where available, since ftell can fail at 2GB.
6381 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
6382 log more informatively.
6383 - Give a slightly more useful output for "tor -h".
6384 - Refuse application socks connections to port 0.
6385 - Check clock skew for verified servers, but allow unverified
6386 servers and clients to have any clock skew.
6387 - Break DirFetchPostPeriod into:
6388 - DirFetchPeriod for fetching full directory,
6389 - StatusFetchPeriod for fetching running-routers,
6390 - DirPostPeriod for posting server descriptor,
6391 - RendPostPeriod for posting hidden service descriptors.
6392 - Make sure the hidden service descriptors are at a random offset
6393 from each other, to hinder linkability.
6396 Changes in version 0.0.9pre5 - 2004-11-09
6397 o Bugfixes on 0.0.9pre4:
6398 - Fix a seg fault in unit tests (doesn't affect main program).
6399 - Fix an assert bug where a hidden service provider would fail if
6400 the first hop of his rendezvous circuit was down.
6401 - Hidden service operators now correctly handle version 1 style
6402 INTRODUCE1 cells (nobody generates them still, so not a critical
6404 - If do_hup fails, actually notice.
6405 - Handle more errnos from accept() without closing the listener.
6406 Some OpenBSD machines were closing their listeners because
6407 they ran out of file descriptors.
6408 - Send resolve cells to exit routers that are running a new
6409 enough version of the resolve code to work right.
6410 - Better handling of winsock includes on non-MSV win32 compilers.
6411 - Some people had wrapped their tor client/server in a script
6412 that would restart it whenever it died. This did not play well
6413 with our "shut down if your version is obsolete" code. Now people
6414 don't fetch a new directory if their local cached version is
6416 - Make our autogen.sh work on ksh as well as bash.
6419 - Hibernation: New config option "AccountingMaxKB" lets you
6420 set how many KBytes per month you want to allow your server to
6421 consume. Rather than spreading those bytes out evenly over the
6422 month, we instead hibernate for some of the month and pop up
6423 at a deterministic time, work until the bytes are consumed, then
6424 hibernate again. Config option "MonthlyAccountingStart" lets you
6425 specify which day of the month your billing cycle starts on.
6426 - Control interface: a separate program can now talk to your
6427 client/server over a socket, and get/set config options, receive
6428 notifications of circuits and streams starting/finishing/dying,
6429 bandwidth used, etc. The next step is to get some GUIs working.
6430 Let us know if you want to help out. See doc/control-spec.txt .
6431 - Ship a contrib/tor-control.py as an example script to interact
6432 with the control port.
6433 - "tor --hash-password zzyxz" will output a salted password for
6434 use in authenticating to the control interface.
6435 - New log format in config:
6436 "Log minsev[-maxsev] stdout|stderr|syslog" or
6437 "Log minsev[-maxsev] file /var/foo"
6440 - DirPolicy config option, to let people reject incoming addresses
6441 from their dirserver.
6442 - "tor --list-fingerprint" will list your identity key fingerprint
6444 - Add "pass" target for RedirectExit, to make it easier to break
6445 out of a sequence of RedirectExit rules.
6446 - Clients now generate a TLS cert too, in preparation for having
6447 them act more like real nodes.
6448 - Ship src/win32/ in the tarball, so people can use it to build.
6449 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
6451 - New "router-status" line in directory, to better bind each verified
6452 nickname to its identity key.
6453 - Deprecate unofficial config option abbreviations, and abbreviations
6454 not on the command line.
6455 - Add a pure-C tor-resolve implementation.
6456 - Use getrlimit and friends to ensure we can reach MaxConn (currently
6457 1024) file descriptors.
6459 o Code security improvements, inspired by Ilja:
6460 - Replace sprintf with snprintf. (I think they were all safe, but
6462 - Replace strcpy/strncpy with strlcpy in more places.
6463 - Avoid strcat; use snprintf or strlcat instead.
6464 - snprintf wrapper with consistent (though not C99) overflow behavior.
6467 Changes in version 0.0.9pre4 - 2004-10-17
6468 o Bugfixes on 0.0.9pre3:
6469 - If the server doesn't specify an exit policy, use the real default
6470 exit policy, not reject *:*.
6471 - Ignore fascistfirewall when uploading/downloading hidden service
6472 descriptors, since we go through Tor for those; and when using
6473 an HttpProxy, since we assume it can reach them all.
6474 - When looking for an authoritative dirserver, use only the ones
6475 configured at boot. Don't bother looking in the directory.
6476 - The rest of the fix for get_default_conf_file() on older win32.
6477 - Make 'Routerfile' config option obsolete.
6480 - New 'MyFamily nick1,...' config option for a server to
6481 specify other servers that shouldn't be used in the same circuit
6482 with it. Only believed if nick1 also specifies us.
6483 - New 'NodeFamily nick1,nick2,...' config option for a client to
6484 specify nodes that it doesn't want to use in the same circuit.
6485 - New 'Redirectexit pattern address:port' config option for a
6486 server to redirect exit connections, e.g. to a local squid.
6489 Changes in version 0.0.9pre3 - 2004-10-13
6490 o Bugfixes on 0.0.8.1:
6491 - Better torrc example lines for dirbindaddress and orbindaddress.
6492 - Improved bounds checking on parsed ints (e.g. config options and
6493 the ones we find in directories.)
6494 - Better handling of size_t vs int, so we're more robust on 64
6496 - Fix the rest of the bug where a newly started OR would appear
6497 as unverified even after we've added his fingerprint and hupped
6499 - Fix a bug from 0.0.7: when read() failed on a stream, we would
6500 close it without sending back an end. So 'connection refused'
6501 would simply be ignored and the user would get no response.
6503 o Bugfixes on 0.0.9pre2:
6504 - Serving the cached-on-disk directory to people is bad. We now
6505 provide no directory until we've fetched a fresh one.
6506 - Workaround for bug on windows where cached-directories get crlf
6508 - Make get_default_conf_file() work on older windows too.
6509 - If we write a *:* exit policy line in the descriptor, don't write
6510 any more exit policy lines.
6513 - Use only 0.0.9pre1 and later servers for resolve cells.
6514 - Make the dirservers file obsolete.
6515 - Include a dir-signing-key token in directories to tell the
6516 parsing entity which key is being used to sign.
6517 - Remove the built-in bulky default dirservers string.
6518 - New config option "Dirserver %s:%d [fingerprint]", which can be
6519 repeated as many times as needed. If no dirservers specified,
6520 default to moria1,moria2,tor26.
6521 - Make moria2 advertise a dirport of 80, so people behind firewalls
6522 will be able to get a directory.
6523 - Http proxy support
6524 - Dirservers translate requests for http://%s:%d/x to /x
6525 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
6526 be routed through this host.
6527 - Clients ask for /tor/x rather than /x for new enough dirservers.
6528 This way we can one day coexist peacefully with apache.
6529 - Clients specify a "Host: %s%d" http header, to be compatible
6530 with more proxies, and so running squid on an exit node can work.
6533 Changes in version 0.0.8.1 - 2004-10-13
6535 - Fix a seg fault that can be triggered remotely for Tor
6536 clients/servers with an open dirport.
6537 - Fix a rare assert trigger, where routerinfos for entries in
6538 our cpath would expire while we're building the path.
6539 - Fix a bug in OutboundBindAddress so it (hopefully) works.
6540 - Fix a rare seg fault for people running hidden services on
6541 intermittent connections.
6542 - Fix a bug in parsing opt keywords with objects.
6543 - Fix a stale pointer assert bug when a stream detaches and
6545 - Fix a string format vulnerability (probably not exploitable)
6546 in reporting stats locally.
6547 - Fix an assert trigger: sometimes launching circuits can fail
6548 immediately, e.g. because too many circuits have failed recently.
6549 - Fix a compile warning on 64 bit platforms.
6552 Changes in version 0.0.9pre2 - 2004-10-03
6554 - Make fetching a cached directory work for 64-bit platforms too.
6555 - Make zlib.h a required header, not an optional header.
6558 Changes in version 0.0.9pre1 - 2004-10-01
6560 - Stop using separate defaults for no-config-file and
6561 empty-config-file. Now you have to explicitly turn off SocksPort,
6562 if you don't want it open.
6563 - Fix a bug in OutboundBindAddress so it (hopefully) works.
6564 - Improve man page to mention more of the 0.0.8 features.
6565 - Fix a rare seg fault for people running hidden services on
6566 intermittent connections.
6567 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
6569 - Fix more dns related bugs: send back resolve_failed and end cells
6570 more reliably when the resolve fails, rather than closing the
6571 circuit and then trying to send the cell. Also attach dummy resolve
6572 connections to a circuit *before* calling dns_resolve(), to fix
6573 a bug where cached answers would never be sent in RESOLVED cells.
6574 - When we run out of disk space, or other log writing error, don't
6575 crash. Just stop logging to that log and continue.
6576 - We were starting to daemonize before we opened our logs, so if
6577 there were any problems opening logs, we would complain to stderr,
6578 which wouldn't work, and then mysteriously exit.
6579 - Fix a rare bug where sometimes a verified OR would connect to us
6580 before he'd uploaded his descriptor, which would cause us to
6581 assign conn->nickname as though he's unverified. Now we look through
6582 the fingerprint list to see if he's there.
6583 - Fix a rare assert trigger, where routerinfos for entries in
6584 our cpath would expire while we're building the path.
6587 - Clients can ask dirservers for /dir.z to get a compressed version
6588 of the directory. Only works for servers running 0.0.9, of course.
6589 - Make clients cache directories and use them to seed their router
6590 lists at startup. This means clients have a datadir again.
6591 - Configuration infrastructure support for warning on obsolete
6593 - Respond to content-encoding headers by trying to uncompress as
6595 - Reply with a deflated directory when a client asks for "dir.z".
6596 We could use allow-encodings instead, but allow-encodings isn't
6597 specified in HTTP 1.0.
6598 - Raise the max dns workers from 50 to 100.
6599 - Discourage people from setting their dirfetchpostperiod more often
6600 than once per minute.
6601 - Protect dirservers from overzealous descriptor uploading -- wait
6602 10 seconds after directory gets dirty, before regenerating.
6605 Changes in version 0.0.8 - 2004-08-25
6606 o Port it to SunOS 5.9 / Athena
6609 Changes in version 0.0.8rc2 - 2004-08-20
6610 o Make it compile on cygwin again.
6611 o When picking unverified routers, skip those with low uptime and/or
6612 low bandwidth, depending on what properties you care about.
6615 Changes in version 0.0.8rc1 - 2004-08-18
6616 o Changes from 0.0.7.3:
6618 - Fix assert triggers: if the other side returns an address 0.0.0.0,
6619 don't put it into the client dns cache.
6620 - If a begin failed due to exit policy, but we believe the IP address
6621 should have been allowed, switch that router to exitpolicy reject *:*
6622 until we get our next directory.
6624 - Clients choose nodes proportional to advertised bandwidth.
6625 - Avoid using nodes with low uptime as introduction points.
6626 - Handle servers with dynamic IP addresses: don't replace
6627 options->Address with the resolved one at startup, and
6628 detect our address right before we make a routerinfo each time.
6629 - 'FascistFirewall' option to pick dirservers and ORs on specific
6630 ports; plus 'FirewallPorts' config option to tell FascistFirewall
6631 which ports are open. (Defaults to 80,443)
6632 - Be more aggressive about trying to make circuits when the network
6633 has changed (e.g. when you unsuspend your laptop).
6634 - Check for time skew on http headers; report date in response to
6636 - If the entrynode config line has only one node, don't pick it as
6638 - Add strict{entry|exit}nodes config options. If set to 1, then
6639 we refuse to build circuits that don't include the specified entry
6641 - OutboundBindAddress config option, to bind to a specific
6642 IP address for outgoing connect()s.
6643 - End truncated log entries (e.g. directories) with "[truncated]".
6645 o Patches to 0.0.8preX:
6647 - Patches to compile and run on win32 again (maybe)?
6648 - Fix crash when looking for ~/.torrc with no $HOME set.
6649 - Fix a race bug in the unit tests.
6650 - Handle verified/unverified name collisions better when new
6651 routerinfo's arrive in a directory.
6652 - Sometimes routers were getting entered into the stats before
6653 we'd assigned their identity_digest. Oops.
6654 - Only pick and establish intro points after we've gotten a
6657 - AllowUnverifiedNodes config option to let circuits choose no-name
6658 routers in entry,middle,exit,introduction,rendezvous positions.
6659 Allow middle and rendezvous positions by default.
6660 - Add a man page for tor-resolve.
6663 Changes in version 0.0.7.3 - 2004-08-12
6664 o Stop dnsworkers from triggering an assert failure when you
6665 ask them to resolve the host "".
6668 Changes in version 0.0.8pre3 - 2004-08-09
6669 o Changes from 0.0.7.2:
6670 - Allow multiple ORs with same nickname in routerlist -- now when
6671 people give us one identity key for a nickname, then later
6672 another, we don't constantly complain until the first expires.
6673 - Remember used bandwidth (both in and out), and publish 15-minute
6674 snapshots for the past day into our descriptor.
6675 - You can now fetch $DIRURL/running-routers to get just the
6676 running-routers line, not the whole descriptor list. (But
6677 clients don't use this yet.)
6678 - When people mistakenly use Tor as an http proxy, point them
6679 at the tor-doc.html rather than the INSTALL.
6680 - Remove our mostly unused -- and broken -- hex_encode()
6681 function. Use base16_encode() instead. (Thanks to Timo Lindfors
6682 for pointing out this bug.)
6683 - Rotate onion keys every 12 hours, not every 2 hours, so we have
6684 fewer problems with people using the wrong key.
6685 - Change the default exit policy to reject the default edonkey,
6686 kazaa, gnutella ports.
6687 - Add replace_file() to util.[ch] to handle win32's rename().
6689 o Changes from 0.0.8preX:
6690 - Fix two bugs in saving onion keys to disk when rotating, so
6691 hopefully we'll get fewer people using old onion keys.
6692 - Fix an assert error that was making SocksPolicy not work.
6693 - Be willing to expire routers that have an open dirport -- it's
6694 just the authoritative dirservers we want to not forget.
6695 - Reject tor-resolve requests for .onion addresses early, so we
6696 don't build a whole rendezvous circuit and then fail.
6697 - When you're warning a server that he's unverified, don't cry
6699 - Fix a race condition: don't try to extend onto a connection
6700 that's still handshaking.
6701 - For servers in clique mode, require the conn to be open before
6702 you'll choose it for your path.
6703 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
6704 end relay cell, etc.
6705 - Measure bandwidth capacity over the last 24 hours, not just 12
6706 - Bugfix: authoritative dirservers were making and signing a new
6707 directory for each client, rather than reusing the cached one.
6710 Changes in version 0.0.8pre2 - 2004-08-04
6711 o Changes from 0.0.7.2:
6713 - Check directory signature _before_ you decide whether you're
6714 you're running an obsolete version and should exit.
6715 - Check directory signature _before_ you parse the running-routers
6716 list to decide who's running or verified.
6717 - Bugfixes and features:
6718 - Check return value of fclose while writing to disk, so we don't
6719 end up with broken files when servers run out of disk space.
6720 - Log a warning if the user uses an unsafe socks variant, so people
6721 are more likely to learn about privoxy or socat.
6722 - Dirservers now include RFC1123-style dates in the HTTP headers,
6723 which one day we will use to better detect clock skew.
6725 o Changes from 0.0.8pre1:
6726 - Make it compile without warnings again on win32.
6727 - Log a warning if you're running an unverified server, to let you
6728 know you might want to get it verified.
6729 - Only pick a default nickname if you plan to be a server.
6732 Changes in version 0.0.8pre1 - 2004-07-23
6734 - Made our unit tests compile again on OpenBSD 3.5, and tor
6735 itself compile again on OpenBSD on a sparc64.
6736 - We were neglecting milliseconds when logging on win32, so
6737 everything appeared to happen at the beginning of each second.
6740 - 'Extend' relay cell payloads now include the digest of the
6741 intended next hop's identity key. Now we can verify that we're
6742 extending to the right router, and also extend to routers we
6743 hadn't heard of before.
6746 - Tor nodes can now act as relays (with an advertised ORPort)
6747 without being manually verified by the dirserver operators.
6748 - Uploaded descriptors of unverified routers are now accepted
6749 by the dirservers, and included in the directory.
6750 - Verified routers are listed by nickname in the running-routers
6751 list; unverified routers are listed as "$<fingerprint>".
6752 - We now use hash-of-identity-key in most places rather than
6753 nickname or addr:port, for improved security/flexibility.
6754 - To avoid Sybil attacks, paths still use only verified servers.
6755 But now we have a chance to play around with hybrid approaches.
6756 - Nodes track bandwidth usage to estimate capacity (not used yet).
6757 - ClientOnly option for nodes that never want to become servers.
6758 - Directory caching.
6759 - "AuthoritativeDir 1" option for the official dirservers.
6760 - Now other nodes (clients and servers) will cache the latest
6761 directory they've pulled down.
6762 - They can enable their DirPort to serve it to others.
6763 - Clients will pull down a directory from any node with an open
6764 DirPort, and check the signature/timestamp correctly.
6765 - Authoritative dirservers now fetch directories from other
6766 authdirservers, to stay better synced.
6767 - Running-routers list tells who's down also, along with noting
6768 if they're verified (listed by nickname) or unverified (listed
6770 - Allow dirservers to serve running-router list separately.
6771 This isn't used yet.
6772 - ORs connect-on-demand to other ORs
6773 - If you get an extend cell to an OR you're not connected to,
6774 connect, handshake, and forward the create cell.
6775 - The authoritative dirservers stay connected to everybody,
6776 and everybody stays connected to 0.0.7 servers, but otherwise
6777 clients/servers expire unused connections after 5 minutes.
6778 - When servers get a sigint, they delay 30 seconds (refusing new
6779 connections) then exit. A second sigint causes immediate exit.
6780 - File and name management:
6781 - Look for .torrc if no CONFDIR "torrc" is found.
6782 - If no datadir is defined, then choose, make, and secure ~/.tor
6784 - If torrc not found, exitpolicy reject *:*.
6785 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
6786 - If no nickname is defined, derive default from hostname.
6787 - Rename secret key files, e.g. identity.key -> secret_id_key,
6788 to discourage people from mailing their identity key to tor-ops.
6789 - Refuse to build a circuit before the directory has arrived --
6790 it won't work anyway, since you won't know the right onion keys
6792 - Try other dirservers immediately if the one you try is down. This
6793 should tolerate down dirservers better now.
6794 - Parse tor version numbers so we can do an is-newer-than check
6795 rather than an is-in-the-list check.
6796 - New socks command 'resolve', to let us shim gethostbyname()
6798 - A 'tor_resolve' script to access the socks resolve functionality.
6799 - A new socks-extensions.txt doc file to describe our
6800 interpretation and extensions to the socks protocols.
6801 - Add a ContactInfo option, which gets published in descriptor.
6802 - Publish OR uptime in descriptor (and thus in directory) too.
6803 - Write tor version at the top of each log file
6804 - New docs in the tarball:
6806 - Document that you should proxy your SSL traffic too.
6809 Changes in version 0.0.7.2 - 2004-07-07
6810 o A better fix for the 0.0.0.0 problem, that will hopefully
6811 eliminate the remaining related assertion failures.
6814 Changes in version 0.0.7.1 - 2004-07-04
6815 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
6816 since internally we use 0.0.0.0 to signify "not yet resolved".
6819 Changes in version 0.0.7 - 2004-06-07
6820 o Updated the man page to reflect the new features.
6823 Changes in version 0.0.7rc2 - 2004-06-06
6824 o Changes from 0.0.7rc1:
6825 - Make it build on Win32 again.
6826 o Changes from 0.0.6.2:
6827 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
6831 Changes in version 0.0.7rc1 - 2004-06-02
6833 - On sighup, we were adding another log without removing the first
6834 one. So log messages would get duplicated n times for n sighups.
6835 - Several cases of using a connection after we'd freed it. The
6836 problem was that connections that are pending resolve are in both
6837 the pending_resolve tree, and also the circuit's resolving_streams
6838 list. When you want to remove one, you must remove it from both.
6839 - Fix a double-mark-for-close where an end cell arrived for a
6840 resolving stream, and then the resolve failed.
6841 - Check directory signatures based on name of signer, not on whom
6842 we got the directory from. This will let us cache directories more
6845 - Crank up some of our constants to handle more users.
6848 Changes in version 0.0.7pre1 - 2004-06-02
6849 o Fixes for crashes and other obnoxious bugs:
6850 - Fix an epipe bug: sometimes when directory connections failed
6851 to connect, we would give them a chance to flush before closing
6853 - When we detached from a circuit because of resolvefailed, we
6854 would immediately try the same circuit twice more, and then
6855 give up on the resolve thinking we'd tried three different
6857 - Limit the number of intro circuits we'll attempt to build for a
6858 hidden service per 15-minute period.
6859 - Check recommended-software string *early*, before actually parsing
6860 the directory. Thus we can detect an obsolete version and exit,
6861 even if the new directory format doesn't parse.
6862 o Fixes for security bugs:
6863 - Remember which nodes are dirservers when you startup, and if a
6864 random OR enables his dirport, don't automatically assume he's
6865 a trusted dirserver.
6867 - Directory connections were asking the wrong poll socket to
6868 start writing, and not asking themselves to start writing.
6869 - When we detached from a circuit because we sent a begin but
6870 didn't get a connected, we would use it again the first time;
6871 but after that we would correctly switch to a different one.
6872 - Stop warning when the first onion decrypt attempt fails; they
6873 will sometimes legitimately fail now that we rotate keys.
6874 - Override unaligned-access-ok check when $host_cpu is ia64 or
6875 arm. Apparently they allow it but the kernel whines.
6876 - Dirservers try to reconnect periodically too, in case connections
6878 - Fix some memory leaks in directory servers.
6879 - Allow backslash in Win32 filenames.
6880 - Made Tor build complain-free on FreeBSD, hopefully without
6881 breaking other BSD builds. We'll see.
6883 - Doxygen markup on all functions and global variables.
6884 - Make directory functions update routerlist, not replace it. So
6885 now directory disagreements are not so critical a problem.
6886 - Remove the upper limit on number of descriptors in a dirserver's
6887 directory (not that we were anywhere close).
6888 - Allow multiple logfiles at different severity ranges.
6889 - Allow *BindAddress to specify ":port" rather than setting *Port
6890 separately. Allow multiple instances of each BindAddress config
6891 option, so you can bind to multiple interfaces if you want.
6892 - Allow multiple exit policy lines, which are processed in order.
6893 Now we don't need that huge line with all the commas in it.
6894 - Enable accept/reject policies on SOCKS connections, so you can bind
6895 to 0.0.0.0 but still control who can use your OP.
6898 Changes in version 0.0.6.2 - 2004-05-16
6899 o Our integrity-checking digest was checking only the most recent cell,
6900 not the previous cells like we'd thought.
6901 Thanks to Stefan Mark for finding the flaw!
6904 Changes in version 0.0.6.1 - 2004-05-06
6905 o Fix two bugs in our AES counter-mode implementation (this affected
6906 onion-level stream encryption, but not TLS-level). It turns
6907 out we were doing something much more akin to a 16-character
6908 polyalphabetic cipher. Oops.
6909 Thanks to Stefan Mark for finding the flaw!
6910 o Retire moria3 as a directory server, and add tor26 as a directory
6914 Changes in version 0.0.6 - 2004-05-02
6918 Changes in version 0.0.6rc4 - 2004-05-01
6919 o Update the built-in dirservers list to use the new directory format
6920 o Fix a rare seg fault: if a node offering a hidden service attempts
6921 to build a circuit to Alice's rendezvous point and fails before it
6922 reaches the last hop, it retries with a different circuit, but
6924 o Handle windows socket errors correctly.
6927 Changes in version 0.0.6rc3 - 2004-04-28
6928 o Don't expire non-general excess circuits (if we had enough
6929 circuits open, we were expiring rendezvous circuits -- even
6930 when they had a stream attached. oops.)
6931 o Fetch randomness from /dev/urandom better (not via fopen/fread)
6932 o Better debugging for tls errors
6933 o Some versions of openssl have an SSL_pending function that erroneously
6934 returns bytes when there is a non-application record pending.
6935 o Set Content-Type on the directory and hidserv descriptor.
6936 o Remove IVs from cipher code, since AES-ctr has none.
6937 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
6938 o We were using an array of length zero in a few places.
6939 o win32's gethostbyname can't resolve an IP to an IP.
6940 o win32's close can't close a socket.
6943 Changes in version 0.0.6rc2 - 2004-04-26
6944 o Fix a bug where we were closing tls connections intermittently.
6945 It turns out openssl keeps its errors around -- so if an error
6946 happens, and you don't ask about it, and then another openssl
6947 operation happens and succeeds, and you ask if there was an error,
6948 it tells you about the first error. Fun fun.
6949 o Fix a bug that's been lurking since 27 may 03 (!)
6950 When passing back a destroy cell, we would use the wrong circ id.
6951 'Mostly harmless', but still worth fixing.
6952 o Since we don't support truncateds much, don't bother sending them;
6953 just close the circ.
6954 o check for <machine/limits.h> so we build on NetBSD again (I hope).
6955 o don't crash if a conn that sent a begin has suddenly lost its circuit
6956 (this was quite rare).
6959 Changes in version 0.0.6rc1 - 2004-04-25
6960 o We now rotate link (tls context) keys and onion keys.
6961 o CREATE cells now include oaep padding, so you can tell
6962 if you decrypted them correctly.
6963 o Add bandwidthburst to server descriptor.
6964 o Directories now say which dirserver signed them.
6965 o Use a tor_assert macro that logs failed assertions too.
6968 Changes in version 0.0.6pre5 - 2004-04-18
6969 o changes from 0.0.6pre4:
6970 - make tor build on broken freebsd 5.2 installs
6971 - fix a failed assert when you try an intro point, get a nack, and try
6972 a second one and it works.
6973 - when alice uses a port that the hidden service doesn't accept,
6974 it now sends back an end cell (denied by exit policy). otherwise
6975 alice would just have to wait to time out.
6976 - fix another rare bug: when we had tried all the intro
6977 points for a hidden service, we fetched the descriptor
6978 again, but we left our introcirc thinking it had already
6979 sent an intro, so it kept waiting for a response...
6980 - bugfix: when you sleep your hidden-service laptop, as soon
6981 as it wakes up it tries to upload a service descriptor, but
6982 socketpair fails for some reason (localhost not up yet?).
6983 now we simply give up on that upload, and we'll try again later.
6984 i'd still like to find the bug though.
6985 - if an intro circ waiting for an ack dies before getting one, then
6987 - we were reusing stale service descriptors and refetching usable
6991 Changes in version 0.0.6pre4 - 2004-04-14
6992 o changes from 0.0.6pre3:
6993 - when bob fails to connect to the rendezvous point, and his
6994 circ didn't fail because of the rendezvous point itself, then
6995 he retries a couple of times
6996 - we expire introduction and rendezvous circs more thoroughly
6997 (sometimes they were hanging around forever)
6998 - we expire unattached rendezvous streams that have been around
6999 too long (they were sticking around forever).
7000 - fix a measly fencepost error that was crashing everybody with
7004 Changes in version 0.0.6pre3 - 2004-04-14
7005 o changes from 0.0.6pre2:
7006 - make hup work again
7007 - fix some memory leaks for dirservers
7008 - allow more skew in rendezvous descriptor timestamps, to help
7009 handle people like blanu who don't know what time it is
7010 - normal circs are 3 hops, but some rend/intro circs are 4, if
7011 the initiator doesn't get to choose the last hop
7012 - send acks for introductions, so alice can know whether to try
7014 - bob publishes intro points more correctly
7015 o changes from 0.0.5:
7016 - fix an assert trigger that's been plaguing us since the days
7017 of 0.0.2prexx (thanks weasel!)
7018 - retry stream correctly when we fail to connect because of
7019 exit-policy-reject (should try another) or can't-resolve-address
7020 (also should try another, because dns on random internet servers
7022 - when we hup a dirserver and we've *removed* a server from the
7023 approved-routers list, now we remove that server from the
7024 in-memory directories too
7027 Changes in version 0.0.6pre2 - 2004-04-08
7028 o We fixed our base32 implementation. Now it works on all architectures.
7031 Changes in version 0.0.6pre1 - 2004-04-08
7033 - Hidden services and rendezvous points are implemented. Go to
7034 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
7035 hidden services. (This only works via a socks4a proxy such as
7036 Privoxy, and currently it's quite slow.)
7039 Changes in version 0.0.5 - 2004-03-30
7043 Changes in version 0.0.5rc3 - 2004-03-29
7044 o Install torrc as torrc.sample -- we no longer clobber your
7046 o Re-enable recommendedversion checking (we broke it in rc2, oops)
7047 o Add in a 'notice' log level for things the operator should hear
7048 but that aren't warnings
7051 Changes in version 0.0.5rc2 - 2004-03-29
7052 o Hold socks connection open until reply is flushed (if possible)
7053 o Make exit nodes resolve IPs to IPs immediately, rather than asking
7054 the dns farm to do it.
7055 o Fix c99 aliasing warnings in rephist.c
7056 o Don't include server descriptors that are older than 24 hours in the
7058 o Give socks 'reject' replies their whole 15s to attempt to flush,
7059 rather than seeing the 60s timeout and assuming the flush had failed.
7060 o Clean automake droppings from the cvs repository
7063 Changes in version 0.0.5rc1 - 2004-03-28
7064 o Fix mangled-state bug in directory fetching (was causing sigpipes).
7065 o Only build circuits after we've fetched the directory: clients were
7066 using only the directory servers before they'd fetched a directory.
7067 This also means longer startup time; so it goes.
7068 o Fix an assert trigger where an OP would fail to handshake, and we'd
7069 expect it to have a nickname.
7070 o Work around a tsocks bug: do a socks reject when AP connection dies
7071 early, else tsocks goes into an infinite loop.
7074 Changes in version 0.0.4 - 2004-03-26
7075 o When connecting to a dirserver or OR and the network is down,
7079 Changes in version 0.0.3 - 2004-03-26
7080 o Warn and fail if server chose a nickname with illegal characters
7081 o Port to Solaris and Sparc:
7082 - include missing header fcntl.h
7083 - have autoconf find -lsocket -lnsl automatically
7084 - deal with hardware word alignment
7085 - make uname() work (solaris has a different return convention)
7086 - switch from using signal() to sigaction()
7087 o Preliminary work on reputation system:
7088 - Keep statistics on success/fail of connect attempts; they're published
7089 by kill -USR1 currently.
7090 - Add a RunTesting option to try to learn link state by creating test
7091 circuits, even when SocksPort is off.
7092 - Remove unused open circuits when there are too many.
7095 Changes in version 0.0.2 - 2004-03-19
7096 - Include strlcpy and strlcat for safer string ops
7097 - define INADDR_NONE so we compile (but still not run) on solaris
7100 Changes in version 0.0.2pre27 - 2004-03-14
7102 - Allow internal tor networks (we were rejecting internal IPs,
7103 now we allow them if they're set explicitly).
7104 - And fix a few endian issues.
7107 Changes in version 0.0.2pre26 - 2004-03-14
7109 - If a stream times out after 15s without a connected cell, don't
7110 try that circuit again: try a new one.
7111 - Retry streams at most 4 times. Then give up.
7112 - When a dirserver gets a descriptor from an unknown router, it
7113 logs its fingerprint (so the dirserver operator can choose to
7114 accept it even without mail from the server operator).
7115 - Inform unapproved servers when we reject their descriptors.
7116 - Make tor build on Windows again. It works as a client, who knows
7118 - Clearer instructions in the torrc for how to set up a server.
7119 - Be more efficient about reading fd's when our global token bucket
7120 (used for rate limiting) becomes empty.
7122 - Stop asserting that computers always go forward in time. It's
7124 - When we sent a cell (e.g. destroy) and then marked an OR connection
7125 expired, we might close it before finishing a flush if the other
7126 side isn't reading right then.
7127 - Don't allow dirservers to start if they haven't defined
7129 - We were caching transient dns failures. Oops.
7130 - Prevent servers from publishing an internal IP as their address.
7131 - Address a strcat vulnerability in circuit.c
7134 Changes in version 0.0.2pre25 - 2004-03-04
7136 - Put the OR's IP in its router descriptor, not its fqdn. That way
7137 we'll stop being stalled by gethostbyname for nodes with flaky dns,
7140 - If the user typed in an address that didn't resolve, the server
7144 Changes in version 0.0.2pre24 - 2004-03-03
7146 - Fix an assertion failure in dns.c, where we were trying to dequeue
7147 a pending dns resolve even if it wasn't pending
7148 - Fix a spurious socks5 warning about still trying to write after the
7149 connection is finished.
7150 - Hold certain marked_for_close connections open until they're finished
7151 flushing, rather than losing bytes by closing them too early.
7152 - Correctly report the reason for ending a stream
7153 - Remove some duplicate calls to connection_mark_for_close
7154 - Put switch_id and start_daemon earlier in the boot sequence, so it
7155 will actually try to chdir() to options.DataDirectory
7156 - Make 'make test' exit(1) if a test fails; fix some unit tests
7157 - Make tor fail when you use a config option it doesn't know about,
7158 rather than warn and continue.
7159 - Make --version work
7160 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
7163 Changes in version 0.0.2pre23 - 2004-02-29
7165 - Print a statement when the first circ is finished, so the user
7167 - If a relay cell is unrecognized at the end of the circuit,
7168 send back a destroy. (So attacks to mutate cells are more
7170 - New config option 'excludenodes' to avoid certain nodes for circuits.
7171 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
7172 so you can collect coredumps there.
7174 - Fix a bug in tls flushing where sometimes data got wedged and
7175 didn't flush until more data got sent. Hopefully this bug was
7176 a big factor in the random delays we were seeing.
7177 - Make 'connected' cells include the resolved IP, so the client
7178 dns cache actually gets populated.
7179 - Disallow changing from ORPort=0 to ORPort>0 on hup.
7180 - When we time-out on a stream and detach from the circuit, send an
7181 end cell down it first.
7182 - Only warn about an unknown router (in exitnodes, entrynodes,
7183 excludenodes) after we've fetched a directory.
7186 Changes in version 0.0.2pre22 - 2004-02-26
7188 - Servers publish less revealing uname information in descriptors.
7189 - More memory tracking and assertions, to crash more usefully when
7191 - If the default torrc isn't there, just use some default defaults.
7192 Plus provide an internal dirservers file if they don't have one.
7193 - When the user tries to use Tor as an http proxy, give them an http
7194 501 failure explaining that we're a socks proxy.
7195 - Dump a new router.desc on hup, to help confused people who change
7196 their exit policies and then wonder why router.desc doesn't reflect
7198 - Clean up the generic tor.sh init script that we ship with.
7200 - If the exit stream is pending on the resolve, and a destroy arrives,
7201 then the stream wasn't getting removed from the pending list. I
7202 think this was the one causing recent server crashes.
7203 - Use a more robust poll on OSX 10.3, since their poll is flaky.
7204 - When it couldn't resolve any dirservers, it was useless from then on.
7205 Now it reloads the RouterFile (or default dirservers) if it has no
7207 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
7208 many users don't even *have* a /usr/local/sbin/.
7211 Changes in version 0.0.2pre21 - 2004-02-18
7213 - There's a ChangeLog file that actually reflects the changelog.
7214 - There's a 'torify' wrapper script, with an accompanying
7215 tor-tsocks.conf, that simplifies the process of using tsocks for
7216 tor. It even has a man page.
7217 - The tor binary gets installed to sbin rather than bin now.
7218 - Retry streams where the connected cell hasn't arrived in 15 seconds
7219 - Clean up exit policy handling -- get the default out of the torrc,
7220 so we can update it without forcing each server operator to fix
7222 - Allow imaps and pop3s in default exit policy
7224 - Prevent picking middleman nodes as the last node in the circuit
7227 Changes in version 0.0.2pre20 - 2004-01-30
7229 - We now have a deb package, and it's in debian unstable. Go to
7231 - I've split the TotalBandwidth option into BandwidthRate (how many
7232 bytes per second you want to allow, long-term) and
7233 BandwidthBurst (how many bytes you will allow at once before the cap
7234 kicks in). This better token bucket approach lets you, say, set
7235 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
7236 performance while not exceeding your monthly bandwidth quota.
7237 - Push out a tls record's worth of data once you've got it, rather
7238 than waiting until you've read everything waiting to be read. This
7239 may improve performance by pipelining better. We'll see.
7240 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
7241 from failed circuits (if they haven't been connected yet) and attach
7243 - Expire old streams that haven't managed to connect. Some day we'll
7244 have them reattach to new circuits instead.
7247 - Fix several memory leaks that were causing servers to become bloated
7249 - Fix a few very rare assert triggers. A few more remain.
7250 - Setuid to User _before_ complaining about running as root.
7253 Changes in version 0.0.2pre19 - 2004-01-07
7255 - Fix deadlock condition in dns farm. We were telling a child to die by
7256 closing the parent's file descriptor to him. But newer children were
7257 inheriting the open file descriptor from the parent, and since they
7258 weren't closing it, the socket never closed, so the child never read
7259 eof, so he never knew to exit. Similarly, dns workers were holding
7260 open other sockets, leading to all sorts of chaos.
7261 - New cleaner daemon() code for forking and backgrounding.
7262 - If you log to a file, it now prints an entry at the top of the
7263 logfile so you know it's working.
7264 - The onionskin challenge length was 30 bytes longer than necessary.
7265 - Started to patch up the spec so it's not quite so out of date.
7268 Changes in version 0.0.2pre18 - 2004-01-02
7270 - Fix endian issues with the 'integrity' field in the relay header.
7271 - Fix a potential bug where connections in state
7272 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
7275 Changes in version 0.0.2pre17 - 2003-12-30
7277 - Made --debuglogfile (or any second log file, actually) work.
7278 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
7279 adversary could force us into an infinite loop.
7282 - Each onionskin handshake now includes a hash of the computed key,
7283 to prove the server's identity and help perfect forward secrecy.
7284 - Changed cell size from 256 to 512 bytes (working toward compatibility
7286 - Changed cell length to 2 bytes, and moved it to the relay header.
7287 - Implemented end-to-end integrity checking for the payloads of
7289 - Separated streamid from 'recognized' (otherwise circuits will get
7290 messed up when we try to have streams exit from the middle). We
7291 use the integrity-checking to confirm that a cell is addressed to
7293 - Randomize the initial circid and streamid values, so an adversary who
7294 breaks into a node can't learn how many circuits or streams have
7298 Changes in version 0.0.2pre16 - 2003-12-14
7300 - Fixed a bug that made HUP trigger an assert
7301 - Fixed a bug where a circuit that immediately failed wasn't being
7302 counted as a failed circuit in counting retries.
7305 - Now we close the circuit when we get a truncated cell: otherwise we're
7306 open to an anonymity attack where a bad node in the path truncates
7307 the circuit and then we open streams at him.
7308 - Add port ranges to exit policies
7309 - Add a conservative default exit policy
7310 - Warn if you're running tor as root
7311 - on HUP, retry OR connections and close/rebind listeners
7312 - options.EntryNodes: try these nodes first when picking the first node
7313 - options.ExitNodes: if your best choices happen to include any of
7314 your preferred exit nodes, you choose among just those preferred
7316 - options.ExcludedNodes: nodes that are never picked in path building
7319 Changes in version 0.0.2pre15 - 2003-12-03
7320 o Robustness and bugfixes:
7321 - Sometimes clients would cache incorrect DNS resolves, which would
7322 really screw things up.
7323 - An OP that goes offline would slowly leak all its sockets and stop
7325 - A wide variety of bugfixes in exit node selection, exit policy
7326 handling, and processing pending streams when a new circuit is
7328 - Pick nodes for a path only from those the directory says are up
7329 - Choose randomly from all running dirservers, not always the first one
7330 - Increase allowed http header size for directory fetch.
7331 - Stop writing to stderr (if we're daemonized it will be closed).
7332 - Enable -g always, so cores will be more useful to me.
7333 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
7336 - Wrote a man page. It lists commonly used options.
7339 - Change default loglevel to warn.
7340 - Make PidFile default to null rather than littering in your CWD.
7341 - OnionRouter config option is now obsolete. Instead it just checks
7343 - Moved to a single unified torrc file for both clients and servers.
7346 Changes in version 0.0.2pre14 - 2003-11-29
7347 o Robustness and bugfixes:
7348 - Force the admin to make the DataDirectory himself
7349 - to get ownership/permissions right
7350 - so clients no longer make a DataDirectory and then never use it
7351 - fix bug where a client who was offline for 45 minutes would never
7352 pull down a directory again
7353 - fix (or at least hide really well) the dns assert bug that was
7354 causing server crashes
7355 - warnings and improved robustness wrt clockskew for certs
7356 - use the native daemon(3) to daemonize, when available
7357 - exit if bind() fails
7358 - exit if neither socksport nor orport is defined
7359 - include our own tor_timegm (Win32 doesn't have its own)
7360 - bugfix for win32 with lots of connections
7361 - fix minor bias in PRNG
7362 - make dirserver more robust to corrupt cached directory
7365 - Wrote the design document (woo)
7367 o Circuit building and exit policies:
7368 - Circuits no longer try to use nodes that the directory has told them
7370 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
7371 bitcounts (18.0.0.0/8).
7372 - Make AP connections standby for a circuit if no suitable circuit
7373 exists, rather than failing
7374 - Circuits choose exit node based on addr/port, exit policies, and
7375 which AP connections are standing by
7376 - Bump min pathlen from 2 to 3
7377 - Relay end cells have a payload to describe why the stream ended.
7378 - If the stream failed because of exit policy, try again with a new
7380 - Clients have a dns cache to remember resolved addresses.
7381 - Notice more quickly when we have no working circuits
7384 - APPort is now called SocksPort
7385 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
7387 - RecommendedVersions is now a config variable rather than
7388 hardcoded (for dirservers)
7389 - Reloads config on HUP
7390 - Usage info on -h or --help
7391 - If you set User and Group config vars, it'll setu/gid to them.
7394 Changes in version 0.0.2pre13 - 2003-10-19
7395 o General stability:
7396 - SSL_write no longer fails when it returns WANTWRITE and the number
7397 of bytes in the buf has changed by the next SSL_write call.
7398 - Fix segfault fetching directory when network is down
7399 - Fix a variety of minor memory leaks
7400 - Dirservers reload the fingerprints file on HUP, so I don't have
7401 to take down the network when I approve a new router
7402 - Default server config file has explicit Address line to specify fqdn
7405 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
7406 - Make listener connections not ever alloc bufs
7408 o Autoconf improvements:
7409 - don't clobber an external CFLAGS in ./configure
7410 - Make install now works
7411 - create var/lib/tor on make install
7412 - autocreate a tor.sh initscript to help distribs
7413 - autocreate the torrc and sample-server-torrc with correct paths
7415 o Log files and Daemonizing now work:
7416 - If --DebugLogFile is specified, log to it at -l debug
7417 - If --LogFile is specified, use it instead of commandline
7418 - If --RunAsDaemon is set, tor forks and backgrounds on startup