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