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