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