2 This document summarizes new features and bugfixes in each stable release
3 of Tor. If you want to see more detailed descriptions of the changes in
4 each development snapshot, see the ChangeLog file.
6 Changes in version 0.2.0.33 - 2009-01-21
7 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
8 useful to users. It also finally fixes a bug where a relay or client
9 that's been off for many days would take a long time to bootstrap.
11 This update also fixes an important security-related bug reported by
12 Ilja van Sprundel. You should upgrade. (We'll send out more details
13 about the bug once people have had some time to upgrade.)
16 - Fix a heap-corruption bug that may be remotely triggerable on
17 some platforms. Reported by Ilja van Sprundel.
20 - When a stream at an exit relay is in state "resolving" or
21 "connecting" and it receives an "end" relay cell, the exit relay
22 would silently ignore the end cell and not close the stream. If
23 the client never closes the circuit, then the exit relay never
24 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
26 - When sending CREATED cells back for a given circuit, use a 64-bit
27 connection ID to find the right connection, rather than an addr:port
28 combination. Now that we can have multiple OR connections between
29 the same ORs, it is no longer possible to use addr:port to uniquely
30 identify a connection.
31 - Bridge relays that had DirPort set to 0 would stop fetching
32 descriptors shortly after startup, and then briefly resume
33 after a new bandwidth test and/or after publishing a new bridge
34 descriptor. Bridge users that try to bootstrap from them would
35 get a recent networkstatus but would get descriptors from up to
36 18 hours earlier, meaning most of the descriptors were obsolete
37 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
38 - Prevent bridge relays from serving their 'extrainfo' document
39 to anybody who asks, now that extrainfo docs include potentially
40 sensitive aggregated client geoip summaries. Bugfix on
42 - If the cached networkstatus consensus is more than five days old,
43 discard it rather than trying to use it. In theory it could be
44 useful because it lists alternate directory mirrors, but in practice
45 it just means we spend many minutes trying directory mirrors that
46 are long gone from the network. Also discard router descriptors as
47 we load them if they are more than five days old, since the onion
48 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
51 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
52 could make gcc generate non-functional binary search code. Bugfix
54 - Build correctly on platforms without socklen_t.
55 - Compile without warnings on solaris.
56 - Avoid potential crash on internal error during signature collection.
57 Fixes bug 864. Patch from rovv.
58 - Correct handling of possible malformed authority signing key
59 certificates with internal signature types. Fixes bug 880.
60 Bugfix on 0.2.0.3-alpha.
61 - Fix a hard-to-trigger resource leak when logging credential status.
63 - When we can't initialize DNS because the network is down, do not
64 automatically stop Tor from starting. Instead, we retry failed
65 dns_init() every 10 minutes, and change the exit policy to reject
66 *:* until one succeeds. Fixes bug 691.
67 - Use 64 bits instead of 32 bits for connection identifiers used with
68 the controller protocol, to greatly reduce risk of identifier reuse.
69 - When we're choosing an exit node for a circuit, and we have
70 no pending streams, choose a good general exit rather than one that
71 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
72 - Fix another case of assuming, when a specific exit is requested,
73 that we know more than the user about what hosts it allows.
74 Fixes one case of bug 752. Patch from rovv.
75 - Clip the MaxCircuitDirtiness config option to a minimum of 10
76 seconds. Warn the user if lower values are given in the
77 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
78 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
79 user if lower values are given in the configuration. Bugfix on
80 0.1.1.17-rc. Patch by Sebastian.
81 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
82 the cache because we already had a v0 descriptor with the same ID.
83 Bugfix on 0.2.0.18-alpha.
84 - Fix a race condition when freeing keys shared between main thread
85 and CPU workers that could result in a memory leak. Bugfix on
86 0.1.0.1-rc. Fixes bug 889.
87 - Send a valid END cell back when a client tries to connect to a
88 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
90 - Check which hops rendezvous stream cells are associated with to
91 prevent possible guess-the-streamid injection attacks from
92 intermediate hops. Fixes another case of bug 446. Based on patch
94 - If a broken client asks a non-exit router to connect somewhere,
95 do not even do the DNS lookup before rejecting the connection.
96 Fixes another case of bug 619. Patch from rovv.
97 - When a relay gets a create cell it can't decrypt (e.g. because it's
98 using the wrong onion key), we were dropping it and letting the
99 client time out. Now actually answer with a destroy cell. Fixes
100 bug 904. Bugfix on 0.0.2pre8.
102 o Minor bugfixes (hidden services):
103 - Do not throw away existing introduction points on SIGHUP. Bugfix on
104 0.0.6pre1. Patch by Karsten. Fixes bug 874.
107 - Report the case where all signatures in a detached set are rejected
108 differently than the case where there is an error handling the
110 - When we realize that another process has modified our cached
111 descriptors, print out a more useful error message rather than
112 triggering an assertion. Fixes bug 885. Patch from Karsten.
113 - Implement the 0x20 hack to better resist DNS poisoning: set the
114 case on outgoing DNS requests randomly, and reject responses that do
115 not match the case correctly. This logic can be disabled with the
116 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
117 of servers that do not reliably preserve case in replies. See
118 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
120 - Check DNS replies for more matching fields to better resist DNS
122 - Never use OpenSSL compression: it wastes RAM and CPU trying to
123 compress cells, which are basically all encrypted, compressed, or
127 Changes in version 0.2.0.32 - 2008-11-20
128 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
129 packages (and maybe other packages) noticed by Theo de Raadt, fixes
130 a smaller security flaw that might allow an attacker to access local
131 services, further improves hidden service performance, and fixes a
132 variety of other issues.
135 - The "User" and "Group" config options did not clear the
136 supplementary group entries for the Tor process. The "User" option
137 is now more robust, and we now set the groups to the specified
138 user's primary group. The "Group" option is now ignored. For more
139 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
140 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
141 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
142 - The "ClientDNSRejectInternalAddresses" config option wasn't being
143 consistently obeyed: if an exit relay refuses a stream because its
144 exit policy doesn't allow it, we would remember what IP address
145 the relay said the destination address resolves to, even if it's
146 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
149 - Fix a DOS opportunity during the voting signature collection process
150 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
152 o Major bugfixes (hidden services):
153 - When fetching v0 and v2 rendezvous service descriptors in parallel,
154 we were failing the whole hidden service request when the v0
155 descriptor fetch fails, even if the v2 fetch is still pending and
156 might succeed. Similarly, if the last v2 fetch fails, we were
157 failing the whole hidden service request even if a v0 fetch is
158 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
159 - When extending a circuit to a hidden service directory to upload a
160 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
161 requests failed, because the router descriptor has not been
162 downloaded yet. In these cases, do not attempt to upload the
163 rendezvous descriptor, but wait until the router descriptor is
164 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
165 descriptor from a hidden service directory for which the router
166 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
170 - Fix several infrequent memory leaks spotted by Coverity.
171 - When testing for libevent functions, set the LDFLAGS variable
172 correctly. Found by Riastradh.
173 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
174 bootstrapping with tunneled directory connections. Bugfix on
175 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
176 - When asked to connect to A.B.exit:80, if we don't know the IP for A
177 and we know that server B rejects most-but-not all connections to
178 port 80, we would previously reject the connection. Now, we assume
179 the user knows what they were asking for. Fixes bug 752. Bugfix
180 on 0.0.9rc5. Diagnosed by BarkerJr.
181 - If we overrun our per-second write limits a little, count this as
182 having used up our write allocation for the second, and choke
183 outgoing directory writes. Previously, we had only counted this when
184 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
185 Bugfix on 0.2.0.x (??).
186 - Remove the old v2 directory authority 'lefkada' from the default
187 list. It has been gone for many months.
188 - Stop doing unaligned memory access that generated bus errors on
189 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
190 - Make USR2 log-level switch take effect immediately. Bugfix on
193 o Minor bugfixes (controller):
194 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
195 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
198 Changes in version 0.2.0.31 - 2008-09-03
199 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
200 a big bug we're seeing where in rare cases traffic from one Tor stream
201 gets mixed into another stream, and fixes a variety of smaller issues.
204 - Make sure that two circuits can never exist on the same connection
205 with the same circuit ID, even if one is marked for close. This
206 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
207 - Relays now reject risky extend cells: if the extend cell includes
208 a digest of all zeroes, or asks to extend back to the relay that
209 sent the extend cell, tear down the circuit. Ideas suggested
211 - If not enough of our entry guards are available so we add a new
212 one, we might use the new one even if it overlapped with the
213 current circuit's exit relay (or its family). Anonymity bugfix
217 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
218 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
219 - Correctly detect the presence of the linux/netfilter_ipv4.h header
220 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
221 - Pick size of default geoip filename string correctly on windows.
222 Fixes bug 806. Bugfix on 0.2.0.30.
223 - Make the autoconf script accept the obsolete --with-ssl-dir
224 option as an alias for the actually-working --with-openssl-dir
225 option. Fix the help documentation to recommend --with-openssl-dir.
226 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
227 - Disallow session resumption attempts during the renegotiation
228 stage of the v2 handshake protocol. Clients should never be trying
229 session resumption at this point, but apparently some did, in
230 ways that caused the handshake to fail. Bug found by Geoff Goodell.
231 Bugfix on 0.2.0.20-rc.
232 - When using the TransPort option on OpenBSD, and using the User
233 option to change UID and drop privileges, make sure to open
234 /dev/pf before dropping privileges. Fixes bug 782. Patch from
235 Christopher Davis. Bugfix on 0.1.2.1-alpha.
236 - Try to attach connections immediately upon receiving a RENDEZVOUS2
237 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
238 on the client side when connecting to a hidden service. Bugfix
239 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
240 - When closing an application-side connection because its circuit is
241 getting torn down, generate the stream event correctly. Bugfix on
242 0.1.2.x. Anonymous patch.
245 Changes in version 0.2.0.30 - 2008-07-15
246 This new stable release switches to a more efficient directory
247 distribution design, adds features to make connections to the Tor
248 network harder to block, allows Tor to act as a DNS proxy, adds separate
249 rate limiting for relayed traffic to make it easier for clients to
250 become relays, fixes a variety of potential anonymity problems, and
251 includes the usual huge pile of other features and bug fixes.
253 o New v3 directory design:
254 - Tor now uses a new way to learn about and distribute information
255 about the network: the directory authorities vote on a common
256 network status document rather than each publishing their own
257 opinion. Now clients and caches download only one networkstatus
258 document to bootstrap, rather than downloading one for each
259 authority. Clients only download router descriptors listed in
260 the consensus. Implements proposal 101; see doc/spec/dir-spec.txt
262 - Set up moria1, tor26, and dizum as v3 directory authorities
263 in addition to being v2 authorities. Also add three new ones:
264 ides (run by Mike Perry), gabelmoo (run by Karsten Loesing), and
265 dannenberg (run by CCC).
266 - Switch to multi-level keys for directory authorities: now their
267 long-term identity key can be kept offline, and they periodically
268 generate a new signing key. Clients fetch the "key certificates"
269 to keep up to date on the right keys. Add a standalone tool
270 "tor-gencert" to generate key certificates. Implements proposal 103.
271 - Add a new V3AuthUseLegacyKey config option to make it easier for
272 v3 authorities to change their identity keys if another bug like
273 Debian's OpenSSL RNG flaw appears.
274 - Authorities and caches fetch the v2 networkstatus documents
275 less often, now that v3 is recommended.
277 o Make Tor connections stand out less on the wire:
278 - Use an improved TLS handshake designed by Steven Murdoch in proposal
279 124, as revised in proposal 130. The new handshake is meant to
280 be harder for censors to fingerprint, and it adds the ability
281 to detect certain kinds of man-in-the-middle traffic analysis
282 attacks. The new handshake format includes version negotiation for
283 OR connections as described in proposal 105, which will allow us
284 to improve Tor's link protocol more safely in the future.
285 - Enable encrypted directory connections by default for non-relays,
286 so censor tools that block Tor directory connections based on their
287 plaintext patterns will no longer work. This means Tor works in
288 certain censored countries by default again.
289 - Stop including recognizeable strings in the commonname part of
290 Tor's x509 certificates.
292 o Implement bridge relays:
293 - Bridge relays (or "bridges" for short) are Tor relays that aren't
294 listed in the main Tor directory. Since there is no complete public
295 list of them, even an ISP that is filtering connections to all the
296 known Tor relays probably won't be able to block all the bridges.
297 See doc/design-paper/blocking.pdf and proposal 125 for details.
298 - New config option BridgeRelay that specifies you want to be a
299 bridge relay rather than a normal relay. When BridgeRelay is set
300 to 1, then a) you cache dir info even if your DirPort ins't on,
301 and b) the default for PublishServerDescriptor is now "bridge"
303 - New config option "UseBridges 1" for clients that want to use bridge
304 relays instead of ordinary entry guards. Clients then specify
305 bridge relays by adding "Bridge" lines to their config file. Users
306 can learn about a bridge relay either manually through word of
307 mouth, or by one of our rate-limited mechanisms for giving out
308 bridge addresses without letting an attacker easily enumerate them
309 all. See https://www.torproject.org/bridges for details.
310 - Bridge relays behave like clients with respect to time intervals
311 for downloading new v3 consensus documents -- otherwise they
312 stand out. Bridge users now wait until the end of the interval,
313 so their bridge relay will be sure to have a new consensus document.
315 o Implement bridge directory authorities:
316 - Bridge authorities are like normal directory authorities, except
317 they don't serve a list of known bridges. Therefore users that know
318 a bridge's fingerprint can fetch a relay descriptor for that bridge,
319 including fetching updates e.g. if the bridge changes IP address,
320 yet an attacker can't just fetch a list of all the bridges.
321 - Set up Tonga as the default bridge directory authority.
322 - Bridge authorities refuse to serve bridge descriptors or other
323 bridge information over unencrypted connections (that is, when
324 responding to direct DirPort requests rather than begin_dir cells.)
325 - Bridge directory authorities do reachability testing on the
326 bridges they know. They provide router status summaries to the
327 controller via "getinfo ns/purpose/bridge", and also dump summaries
328 to a file periodically, so we can keep internal stats about which
329 bridges are functioning.
330 - If bridge users set the UpdateBridgesFromAuthority config option,
331 but the digest they ask for is a 404 on the bridge authority,
332 they fall back to contacting the bridge directly.
333 - Bridges always use begin_dir to publish their server descriptor to
334 the bridge authority using an anonymous encrypted tunnel.
335 - Early work on a "bridge community" design: if bridge authorities set
336 the BridgePassword config option, they will serve a snapshot of
337 known bridge routerstatuses from their DirPort to anybody who
338 knows that password. Unset by default.
339 - Tor now includes an IP-to-country GeoIP file, so bridge relays can
340 report sanitized aggregated summaries in their extra-info documents
341 privately to the bridge authority, listing which countries are
342 able to reach them. We hope this mechanism will let us learn when
343 certain countries start trying to block bridges.
344 - Bridge authorities write bridge descriptors to disk, so they can
345 reload them after a reboot. They can also export the descriptors
346 to other programs, so we can distribute them to blocked users via
347 the BridgeDB interface, e.g. via https://bridges.torproject.org/
348 and bridges@torproject.org.
350 o Tor can be a DNS proxy:
351 - The new client-side DNS proxy feature replaces the need for
352 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
353 for DNS requests on port 9999, use the Tor network to resolve them
354 anonymously, and send the reply back like a regular DNS server.
355 The code still only implements a subset of DNS.
356 - Add a new AutomapHostsOnResolve option: when it is enabled, any
357 resolve request for hosts matching a given pattern causes Tor to
358 generate an internal virtual address mapping for that host. This
359 allows DNSPort to work sensibly with hidden service users. By
360 default, .exit and .onion addresses are remapped; the list of
361 patterns can be reconfigured with AutomapHostsSuffixes.
362 - Add an "-F" option to tor-resolve to force a resolve for a .onion
363 address. Thanks to the AutomapHostsOnResolve option, this is no
364 longer a completely silly thing to do.
366 o Major features (relay usability):
367 - New config options RelayBandwidthRate and RelayBandwidthBurst:
368 a separate set of token buckets for relayed traffic. Right now
369 relayed traffic is defined as answers to directory requests, and
370 OR connections that don't have any local circuits on them. See
371 proposal 111 for details.
372 - Create listener connections before we setuid to the configured
373 User and Group. Now non-Windows users can choose port values
374 under 1024, start Tor as root, and have Tor bind those ports
375 before it changes to another UID. (Windows users could already
377 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
378 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
379 on "vserver" accounts. Patch from coderman.
381 o Major features (directory authorities):
382 - Directory authorities track weighted fractional uptime and weighted
383 mean-time-between failures for relays. WFU is suitable for deciding
384 whether a node is "usually up", while MTBF is suitable for deciding
385 whether a node is "likely to stay up." We need both, because
386 "usually up" is a good requirement for guards, while "likely to
387 stay up" is a good requirement for long-lived connections.
388 - Directory authorities use a new formula for selecting which relays
389 to advertise as Guards: they must be in the top 7/8 in terms of
390 how long we have known about them, and above the median of those
391 nodes in terms of weighted fractional uptime.
392 - Directory authorities use a new formula for selecting which relays
393 to advertise as Stable: when we have 4 or more days of data, use
394 median measured MTBF rather than median declared uptime. Implements
396 - Directory authorities accept and serve "extra info" documents for
397 routers. Routers now publish their bandwidth-history lines in the
398 extra-info docs rather than the main descriptor. This step saves
399 60% (!) on compressed router descriptor downloads. Servers upload
400 extra-info docs to any authority that accepts them; directory
401 authorities now allow multiple router descriptors and/or extra
402 info documents to be uploaded in a single go. Authorities, and
403 caches that have been configured to download extra-info documents,
404 download them as needed. Implements proposal 104.
405 - Authorities now list relays who have the same nickname as
406 a different named relay, but list them with a new flag:
407 "Unnamed". Now we can make use of relays that happen to pick the
408 same nickname as a server that registered two years ago and then
409 disappeared. Implements proposal 122.
410 - Store routers in a file called cached-descriptors instead of in
411 cached-routers. Initialize cached-descriptors from cached-routers
412 if the old format is around. The new format allows us to store
413 annotations along with descriptors, to record the time we received
414 each descriptor, its source, and its purpose: currently one of
415 general, controller, or bridge.
417 o Major features (other):
418 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
419 Tor can warn and/or refuse connections to ports commonly used with
420 vulnerable-plaintext protocols. Currently we warn on ports 23,
421 109, 110, and 143, but we don't reject any. Based on proposal 129
422 by Kevin Bauer and Damon McCoy.
423 - Integrate Karsten Loesing's Google Summer of Code project to publish
424 hidden service descriptors on a set of redundant relays that are a
425 function of the hidden service address. Now we don't have to rely
426 on three central hidden service authorities for publishing and
427 fetching every hidden service descriptor. Implements proposal 114.
428 - Allow tunnelled directory connections to ask for an encrypted
429 "begin_dir" connection or an anonymized "uses a full Tor circuit"
430 connection independently. Now we can make anonymized begin_dir
431 connections for (e.g.) more secure hidden service posting and
434 o Major bugfixes (crashes and assert failures):
435 - Stop imposing an arbitrary maximum on the number of file descriptors
436 used for busy servers. Bug reported by Olaf Selke; patch from
438 - Avoid possible failures when generating a directory with routers
439 with over-long versions strings, or too many flags set.
440 - Fix a rare assert error when we're closing one of our threads:
441 use a mutex to protect the list of logs, so we never write to the
442 list as it's being freed. Fixes the very rare bug 575, which is
443 kind of the revenge of bug 222.
444 - Avoid segfault in the case where a badly behaved v2 versioning
445 directory sends a signed networkstatus with missing client-versions.
446 - When we hit an EOF on a log (probably because we're shutting down),
447 don't try to remove the log from the list: just mark it as
448 unusable. (Bulletproofs against bug 222.)
450 o Major bugfixes (code security fixes):
451 - Detect size overflow in zlib code. Reported by Justin Ferguson and
453 - Rewrite directory tokenization code to never run off the end of
454 a string. Fixes bug 455. Patch from croup.
455 - Be more paranoid about overwriting sensitive memory on free(),
456 as a defensive programming tactic to ensure forward secrecy.
458 o Major bugfixes (anonymity fixes):
459 - Reject requests for reverse-dns lookup of names that are in
460 a private address space. Patch from lodger.
461 - Never report that we've used more bandwidth than we're willing to
462 relay: it leaks how much non-relay traffic we're using. Resolves
464 - As a client, do not believe any server that tells us that an
465 address maps to an internal address space.
466 - Warn about unsafe ControlPort configurations.
467 - Directory authorities now call routers Fast if their bandwidth is
468 at least 100KB/s, and consider their bandwidth adequate to be a
469 Guard if it is at least 250KB/s, no matter the medians. This fix
470 complements proposal 107.
471 - Directory authorities now never mark more than 2 servers per IP as
472 Valid and Running (or 5 on addresses shared by authorities).
473 Implements proposal 109, by Kevin Bauer and Damon McCoy.
474 - If we're a relay, avoid picking ourselves as an introduction point,
475 a rendezvous point, or as the final hop for internal circuits. Bug
476 reported by taranis and lodger.
477 - Exit relays that are used as a client can now reach themselves
478 using the .exit notation, rather than just launching an infinite
479 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
480 - Fix a bug where, when we were choosing the 'end stream reason' to
481 put in our relay end cell that we send to the exit relay, Tor
482 clients on Windows were sometimes sending the wrong 'reason'. The
483 anonymity problem is that exit relays may be able to guess whether
484 the client is running Windows, thus helping partition the anonymity
485 set. Down the road we should stop sending reasons to exit relays,
486 or otherwise prevent future versions of this bug.
487 - Only update guard status (usable / not usable) once we have
488 enough directory information. This was causing us to discard all our
489 guards on startup if we hadn't been running for a few weeks. Fixes
491 - When our directory information has been expired for a while, stop
492 being willing to build circuits using it. Fixes bug 401.
494 o Major bugfixes (peace of mind for relay operators)
495 - Non-exit relays no longer answer "resolve" relay cells, so they
496 can't be induced to do arbitrary DNS requests. (Tor clients already
497 avoid using non-exit relays for resolve cells, but now servers
498 enforce this too.) Fixes bug 619. Patch from lodger.
499 - When we setconf ClientOnly to 1, close any current OR and Dir
500 listeners. Reported by mwenge.
502 o Major bugfixes (other):
503 - If we only ever used Tor for hidden service lookups or posts, we
504 would stop building circuits and start refusing connections after
505 24 hours, since we falsely believed that Tor was dormant. Reported
507 - Add a new __HashedControlSessionPassword option for controllers
508 to use for one-off session password hashes that shouldn't get
509 saved to disk by SAVECONF --- Vidalia users were accumulating a
510 pile of HashedControlPassword lines in their torrc files, one for
511 each time they had restarted Tor and then clicked Save. Make Tor
512 automatically convert "HashedControlPassword" to this new option but
513 only when it's given on the command line. Partial fix for bug 586.
514 - Patch from "Andrew S. Lists" to catch when we contact a directory
515 mirror at IP address X and he says we look like we're coming from
516 IP address X. Otherwise this would screw up our address detection.
517 - Reject uploaded descriptors and extrainfo documents if they're
518 huge. Otherwise we'll cache them all over the network and it'll
519 clog everything up. Suggested by Aljosha Judmayer.
520 - When a hidden service was trying to establish an introduction point,
521 and Tor *did* manage to reuse one of the preemptively built
522 circuits, it didn't correctly remember which one it used,
523 so it asked for another one soon after, until there were no
524 more preemptive circuits, at which point it launched one from
525 scratch. Bugfix on 0.0.9.x.
527 o Rate limiting and load balancing improvements:
528 - When we add data to a write buffer in response to the data on that
529 write buffer getting low because of a flush, do not consider the
530 newly added data as a candidate for immediate flushing, but rather
531 make it wait until the next round of writing. Otherwise, we flush
532 and refill recursively, and a single greedy TLS connection can
533 eat all of our bandwidth.
534 - When counting the number of bytes written on a TLS connection,
535 look at the BIO actually used for writing to the network, not
536 at the BIO used (sometimes) to buffer data for the network.
537 Looking at different BIOs could result in write counts on the
538 order of ULONG_MAX. Fixes bug 614.
539 - If we change our MaxAdvertisedBandwidth and then reload torrc,
540 Tor won't realize it should publish a new relay descriptor. Fixes
541 bug 688, reported by mfr.
542 - Avoid using too little bandwidth when our clock skips a few seconds.
543 - Choose which bridge to use proportional to its advertised bandwidth,
544 rather than uniformly at random. This should speed up Tor for
545 bridge users. Also do this for people who set StrictEntryNodes.
547 o Bootstrapping faster and building circuits more intelligently:
548 - Fix bug 660 that was preventing us from knowing that we should
549 preemptively build circuits to handle expected directory requests.
550 - When we're checking if we have enough dir info for each relay
551 to begin establishing circuits, make sure that we actually have
552 the descriptor listed in the consensus, not just any descriptor.
553 - Correctly notify one-hop connections when a circuit build has
554 failed. Possible fix for bug 669. Found by lodger.
555 - Clients now hold circuitless TLS connections open for 1.5 times
556 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
557 rebuild a new circuit over them within that timeframe. Previously,
558 they held them open only for KeepalivePeriod (5 minutes).
560 o Performance improvements (memory):
561 - Add OpenBSD malloc code from "phk" as an optional malloc
562 replacement on Linux: some glibc libraries do very poorly with
563 Tor's memory allocation patterns. Pass --enable-openbsd-malloc to
564 ./configure to get the replacement malloc code.
565 - Switch our old ring buffer implementation for one more like that
566 used by free Unix kernels. The wasted space in a buffer with 1mb
567 of data will now be more like 8k than 1mb. The new implementation
568 also avoids realloc();realloc(); patterns that can contribute to
569 memory fragmentation.
570 - Change the way that Tor buffers data that it is waiting to write.
571 Instead of queueing data cells in an enormous ring buffer for each
572 client->OR or OR->OR connection, we now queue cells on a separate
573 queue for each circuit. This lets us use less slack memory, and
574 will eventually let us be smarter about prioritizing different kinds
576 - Reference-count and share copies of address policy entries; only 5%
577 of them were actually distinct.
578 - Tune parameters for cell pool allocation to minimize amount of
580 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
581 for every single inactive connection_t. Free items from the
582 4k/16k-buffer free lists when they haven't been used for a while.
583 - Make memory debugging information describe more about history
584 of cell allocation, so we can help reduce our memory use.
585 - Be even more aggressive about releasing RAM from small
586 empty buffers. Thanks to our free-list code, this shouldn't be too
587 performance-intensive.
588 - Log malloc statistics from mallinfo() on platforms where it exists.
589 - Use memory pools to allocate cells with better speed and memory
590 efficiency, especially on platforms where malloc() is inefficient.
591 - Add a --with-tcmalloc option to the configure script to link
592 against tcmalloc (if present). Does not yet search for non-system
595 o Performance improvements (socket management):
596 - Count the number of open sockets separately from the number of
597 active connection_t objects. This will let us avoid underusing
598 our allocated connection limit.
599 - We no longer use socket pairs to link an edge connection to an
600 anonymous directory connection or a DirPort test connection.
601 Instead, we track the link internally and transfer the data
602 in-process. This saves two sockets per "linked" connection (at the
603 client and at the server), and avoids the nasty Windows socketpair()
605 - We were leaking a file descriptor if Tor started with a zero-length
606 cached-descriptors file. Patch by "freddy77".
608 o Performance improvements (CPU use):
609 - Never walk through the list of logs if we know that no log target
610 is interested in a given message.
611 - Call routerlist_remove_old_routers() much less often. This should
612 speed startup, especially on directory caches.
613 - Base64 decoding was actually showing up on our profile when parsing
614 the initial descriptor file; switch to an in-process all-at-once
615 implementation that's about 3.5x times faster than calling out to
617 - Use a slightly simpler string hashing algorithm (copying Python's
618 instead of Java's) and optimize our digest hashing algorithm to take
619 advantage of 64-bit platforms and to remove some possibly-costly
621 - When implementing AES counter mode, update only the portions of the
622 counter buffer that need to change, and don't keep separate
623 network-order and host-order counters on big-endian hosts (where
625 - Add an in-place version of aes_crypt() so that we can avoid doing a
626 needless memcpy() call on each cell payload.
627 - Use Critical Sections rather than Mutexes for synchronizing threads
628 on win32; Mutexes are heavier-weight, and designed for synchronizing
631 o Performance improvements (bandwidth use):
632 - Don't try to launch new descriptor downloads quite so often when we
633 already have enough directory information to build circuits.
634 - Version 1 directories are no longer generated in full. Instead,
635 authorities generate and serve "stub" v1 directories that list
636 no servers. This will stop Tor versions 0.1.0.x and earlier from
637 working, but (for security reasons) nobody should be running those
639 - Avoid going directly to the directory authorities even if you're a
640 relay, if you haven't found yourself reachable yet or if you've
641 decided not to advertise your dirport yet. Addresses bug 556.
642 - If we've gone 12 hours since our last bandwidth check, and we
643 estimate we have less than 50KB bandwidth capacity but we could
644 handle more, do another bandwidth test.
645 - Support "If-Modified-Since" when answering HTTP requests for
646 directories, running-routers documents, and v2 and v3 networkstatus
647 documents. (There's no need to support it for router descriptors,
648 since those are downloaded by descriptor digest.)
649 - Stop fetching directory info so aggressively if your DirPort is
650 on but your ORPort is off; stop fetching v2 dir info entirely.
651 You can override these choices with the new FetchDirInfoEarly
654 o Changed config option behavior (features):
655 - Configuration files now accept C-style strings as values. This
656 helps encode characters not allowed in the current configuration
657 file format, such as newline or #. Addresses bug 557.
658 - Add hidden services and DNSPorts to the list of things that make
659 Tor accept that it has running ports. Change starting Tor with no
660 ports from a fatal error to a warning; we might change it back if
661 this turns out to confuse anybody. Fixes bug 579.
662 - Make PublishServerDescriptor default to 1, so the default doesn't
663 have to change as we invent new directory protocol versions.
664 - Allow people to say PreferTunnelledDirConns rather than
665 PreferTunneledDirConns, for those alternate-spellers out there.
666 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
667 accommodate the growing number of servers that use the default
669 - Make it possible to enable HashedControlPassword and
670 CookieAuthentication at the same time.
671 - When a TrackHostExits-chosen exit fails too many times in a row,
672 stop using it. Fixes bug 437.
674 o Changed config option behavior (bugfixes):
675 - Do not read the configuration file when we've only been told to
676 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
677 based on patch from Sebastian Hahn.
678 - Actually validate the options passed to AuthDirReject,
679 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
680 - Make "ClientOnly 1" config option disable directory ports too.
681 - Don't stop fetching descriptors when FetchUselessDescriptors is
682 set, even if we stop asking for circuits. Bug reported by tup
684 - Servers used to decline to publish their DirPort if their
685 BandwidthRate or MaxAdvertisedBandwidth were below a threshold. Now
686 they look only at BandwidthRate and RelayBandwidthRate.
687 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
688 minus 1 byte: the actual maximum declared bandwidth.
689 - Make "TrackHostExits ." actually work. Bugfix on 0.1.0.x.
690 - Make the NodeFamilies config option work. (Reported by
691 lodger -- it has never actually worked, even though we added it
693 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
694 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
696 o New config options:
697 - New configuration options AuthDirMaxServersPerAddr and
698 AuthDirMaxServersperAuthAddr to override default maximum number
699 of servers allowed on a single IP address. This is important for
700 running a test network on a single host.
701 - Three new config options (AlternateDirAuthority,
702 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
703 user selectively replace the default directory authorities by type,
704 rather than the all-or-nothing replacement that DirServer offers.
705 - New config options AuthDirBadDir and AuthDirListBadDirs for
706 authorities to mark certain relays as "bad directories" in the
707 networkstatus documents. Also supports the "!baddir" directive in
708 the approved-routers file.
709 - New config option V2AuthoritativeDirectory that all v2 directory
710 authorities must set. This lets v3 authorities choose not to serve
711 v2 directory information.
713 o Minor features (other):
714 - When we're not serving v2 directory information, there is no reason
715 to actually keep any around. Remove the obsolete files and directory
716 on startup if they are very old and we aren't going to serve them.
717 - When we negotiate a v2 link-layer connection (not yet implemented),
718 accept RELAY_EARLY cells and turn them into RELAY cells if we've
719 negotiated a v1 connection for their next step. Initial steps for
721 - When we have no consensus, check FallbackNetworkstatusFile (defaults
722 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
723 we can start out knowing some directory caches. We don't ship with
724 a fallback consensus by default though, because it was making
725 bootstrapping take too long while we tried many down relays.
726 - Authorities send back an X-Descriptor-Not-New header in response to
727 an accepted-but-discarded descriptor upload. Partially implements
729 - If we find a cached-routers file that's been sitting around for more
730 than 28 days unmodified, then most likely it's a leftover from
731 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
733 - When we (as a cache) download a descriptor because it was listed
734 in a consensus, remember when the consensus was supposed to expire,
735 and don't expire the descriptor until then.
736 - Optionally (if built with -DEXPORTMALLINFO) export the output
737 of mallinfo via http, as tor/mallinfo.txt. Only accessible
739 - Tag every guard node in our state file with the version that
740 we believe added it, or with our own version if we add it. This way,
741 if a user temporarily runs an old version of Tor and then switches
742 back to a new one, she doesn't automatically lose her guards.
743 - When somebody requests a list of statuses or servers, and we have
744 none of those, return a 404 rather than an empty 200.
745 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
747 - Add an HSAuthorityRecordStats option that hidden service authorities
748 can use to track statistics of overall hidden service usage without
749 logging information that would be as useful to an attacker.
750 - Allow multiple HiddenServicePort directives with the same virtual
751 port; when they occur, the user is sent round-robin to one
752 of the target ports chosen at random. Partially fixes bug 393 by
753 adding limited ad-hoc round-robining.
754 - Revamp file-writing logic so we don't need to have the entire
755 contents of a file in memory at once before we write to disk. Tor,
758 o Minor bugfixes (other):
759 - Alter the code that tries to recover from unhandled write
760 errors, to not try to flush onto a socket that's given us
762 - Directory mirrors no longer include a guess at the client's IP
763 address if the connection appears to be coming from the same /24
764 network; it was producing too many wrong guesses.
765 - If we're trying to flush the last bytes on a connection (for
766 example, when answering a directory request), reset the
767 time-to-give-up timeout every time we manage to write something
769 - Reject router descriptors with out-of-range bandwidthcapacity or
770 bandwidthburst values.
771 - If we can't expand our list of entry guards (e.g. because we're
772 using bridges or we have StrictEntryNodes set), don't mark relays
773 down when they fail a directory request. Otherwise we're too quick
774 to mark all our entry points down.
775 - Authorities no longer send back "400 you're unreachable please fix
776 it" errors to Tor servers that aren't online all the time. We're
777 supposed to tolerate these servers now.
778 - Let directory authorities startup even when they can't generate
779 a descriptor immediately, e.g. because they don't know their
781 - Correctly enforce that elements of directory objects do not appear
782 more often than they are allowed to appear.
783 - Stop allowing hibernating servers to be "stable" or "fast".
784 - On Windows, we were preventing other processes from reading
785 cached-routers while Tor was running. (Reported by janbar)
786 - Check return values from pthread_mutex functions.
787 - When opening /dev/null in finish_daemonize(), do not pass the
788 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
789 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
791 o Controller features:
792 - The GETCONF command now escapes and quotes configuration values
793 that don't otherwise fit into the torrc file.
794 - The SETCONF command now handles quoted values correctly.
795 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
796 ask about source, timestamp of arrival, purpose, etc. We need
797 something like this to help Vidalia not do GeoIP lookups on bridge
799 - Allow multiple HashedControlPassword config lines, to support
800 multiple controller passwords.
801 - Accept LF instead of CRLF on controller, since some software has a
802 hard time generating real Internet newlines.
803 - Add GETINFO values for the server status events
804 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
806 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
807 GETINFO for Torstat to use until it can switch to using extrainfos.
808 - New config option CookieAuthFile to choose a new location for the
809 cookie authentication file, and config option
810 CookieAuthFileGroupReadable to make it group-readable.
811 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
812 match requests to applications. Patch from Robert Hogan.
813 - Add a RESOLVE command to launch hostname lookups. Original patch
815 - Add GETINFO status/enough-dir-info to let controllers tell whether
816 Tor has downloaded sufficient directory information. Patch from Tup.
817 - You can now use the ControlSocket option to tell Tor to listen for
818 controller connections on Unix domain sockets on systems that
819 support them. Patch from Peter Palfrader.
820 - New "GETINFO address-mappings/*" command to get address mappings
821 with expiry information. "addr-mappings/*" is now deprecated.
823 - Add a new config option __DisablePredictedCircuits designed for
824 use by the controller, when we don't want Tor to build any circuits
826 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
827 so we can exit from the middle of the circuit.
828 - Implement "getinfo status/circuit-established".
829 - Implement "getinfo status/version/..." so a controller can tell
830 whether the current version is recommended, and whether any versions
831 are good, and how many authorities agree. Patch from "shibz".
832 - Controllers should now specify cache=no or cache=yes when using
833 the +POSTDESCRIPTOR command.
834 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
835 Robert Hogan. Fixes the first part of bug 681.
836 - When reporting clock skew, and we know that the clock is _at least
837 as skewed_ as some value, but we don't know the actual value,
838 report the value as a "minimum skew."
840 o Controller bugfixes:
841 - Generate "STATUS_SERVER" events rather than misspelled
842 "STATUS_SEVER" events. Caught by mwenge.
843 - Reject controller commands over 1MB in length, so rogue
844 processes can't run us out of memory.
845 - Change the behavior of "getinfo status/good-server-descriptor"
846 so it doesn't return failure when any authority disappears.
847 - Send NAMESERVER_STATUS messages for a single failed nameserver
849 - When the DANGEROUS_VERSION controller status event told us we're
850 running an obsolete version, it used the string "OLD" to describe
851 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
852 "OBSOLETE" in both cases.
853 - Respond to INT and TERM SIGNAL commands before we execute the
854 signal, in case the signal shuts us down. We had a patch in
855 0.1.2.1-alpha that tried to do this by queueing the response on
856 the connection's buffer before shutting down, but that really
857 isn't the same thing at all. Bug located by Matt Edman.
858 - Provide DNS expiry times in GMT, not in local time. For backward
859 compatibility, ADDRMAP events only provide GMT expiry in an extended
860 field. "GETINFO address-mappings" always does the right thing.
861 - Use CRLF line endings properly in NS events.
862 - Make 'getinfo fingerprint' return a 551 error if we're not a
863 server, so we match what the control spec claims we do. Reported
865 - Fix a typo in an error message when extendcircuit fails that
866 caused us to not follow the \r\n-based delimiter protocol. Reported
868 - When tunneling an encrypted directory connection, and its first
869 circuit fails, do not leave it unattached and ask the controller
870 to deal. Fixes the second part of bug 681.
871 - Treat some 403 responses from directory servers as INFO rather than
872 WARN-severity events.
874 o Portability / building / compiling:
875 - When building with --enable-gcc-warnings, check for whether Apple's
876 warning "-Wshorten-64-to-32" is available.
877 - Support compilation to target iPhone; patch from cjacker huang.
878 To build for iPhone, pass the --enable-iphone option to configure.
879 - Detect non-ASCII platforms (if any still exist) and refuse to
880 build there: some of our code assumes that 'A' is 65 and so on.
881 - Clear up some MIPSPro compiler warnings.
882 - Make autoconf search for libevent, openssl, and zlib consistently.
883 - Update deprecated macros in configure.in.
884 - When warning about missing headers, tell the user to let us
885 know if the compile succeeds anyway, so we can downgrade the
887 - Include the current subversion revision as part of the version
888 string: either fetch it directly if we're in an SVN checkout, do
889 some magic to guess it if we're in an SVK checkout, or use
890 the last-detected version if we're building from a .tar.gz.
891 Use this version consistently in log messages.
892 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
893 - Read resolv.conf files correctly on platforms where read() returns
894 partial results on small file reads.
895 - Build without verbose warnings even on gcc 4.2 and 4.3.
896 - On Windows, correctly detect errors when listing the contents of
897 a directory. Fix from lodger.
898 - Run 'make test' as part of 'make dist', so we stop releasing so
899 many development snapshots that fail their unit tests.
900 - Add support to detect Libevent versions in the 1.4.x series
902 - Add command-line arguments to unit-test executable so that we can
903 invoke any chosen test from the command line rather than having
904 to run the whole test suite at once; and so that we can turn on
905 logging for the unit tests.
906 - Do not automatically run configure from autogen.sh. This
907 non-standard behavior tended to annoy people who have built other
909 - Fix a macro/CPP interaction that was confusing some compilers:
910 some GCCs don't like #if/#endif pairs inside macro arguments.
912 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
913 Fixes bug 704; fix from Steven Murdoch.
914 - Correctly detect transparent proxy support on Linux hosts that
915 require in.h to be included before netfilter_ipv4.h. Patch
918 o Logging improvements:
919 - When we haven't had any application requests lately, don't bother
920 logging that we have expired a bunch of descriptors.
921 - When attempting to open a logfile fails, tell us why.
922 - Only log guard node status when guard node status has changed.
923 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
924 make "INFO" 75% less verbose.
925 - When SafeLogging is disabled, log addresses along with all TLS
927 - Report TLS "zero return" case as a "clean close" and "IO error"
928 as a "close". Stop calling closes "unexpected closes": existing
929 Tors don't use SSL_close(), so having a connection close without
930 the TLS shutdown handshake is hardly unexpected.
931 - When we receive a consensus from the future, warn about skew.
932 - Make "not enough dir info yet" warnings describe *why* Tor feels
933 it doesn't have enough directory info yet.
934 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
935 consumers. (We already do this on HUP.)
936 - Give more descriptive well-formedness errors for out-of-range
937 hidden service descriptor/protocol versions.
938 - Stop recommending that every server operator send mail to tor-ops.
939 Resolves bug 597. Bugfix on 0.1.2.x.
940 - Improve skew reporting: try to give the user a better log message
941 about how skewed they are, and how much this matters.
942 - New --quiet command-line option to suppress the default console log.
943 Good in combination with --hash-password.
944 - Don't complain that "your server has not managed to confirm that its
945 ports are reachable" if we haven't been able to build any circuits
947 - Detect the reason for failing to mmap a descriptor file we just
948 wrote, and give a more useful log message. Fixes bug 533.
949 - Always prepend "Bug: " to any log message about a bug.
950 - When dumping memory usage, list bytes used in buffer memory
952 - When running with dmalloc, dump more stats on hup and on exit.
953 - Put a platform string (e.g. "Linux i686") in the startup log
954 message, so when people paste just their logs, we know if it's
955 OpenBSD or Windows or what.
956 - When logging memory usage, break down memory used in buffers by
958 - When we are reporting the DirServer line we just parsed, we were
959 logging the second stanza of the key fingerprint, not the first.
960 - Even though Windows is equally happy with / and \ as path separators,
961 try to use \ consistently on Windows and / consistently on Unix: it
962 makes the log messages nicer.
963 - On OSX, stop warning the user that kqueue support in libevent is
964 "experimental", since it seems to have worked fine for ages.
966 o Contributed scripts and tools:
967 - Update linux-tor-prio.sh script to allow QoS based on the uid of
968 the Tor process. Patch from Marco Bonetti with tweaks from Mike
970 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
971 Unix users an easy way to script their Tor process (e.g. by
972 adjusting bandwidth based on the time of the day).
973 - In the exitlist script, only consider the most recently published
974 server descriptor for each server. Also, when the user requests
975 a list of servers that _reject_ connections to a given address,
976 explicitly exclude the IPs that also have servers that accept
977 connections to that address. Resolves bug 405.
978 - Include a new contrib/tor-exit-notice.html file that exit relay
979 operators can put on their website to help reduce abuse queries.
981 o Newly deprecated features:
982 - The status/version/num-versioning and status/version/num-concurring
983 GETINFO controller options are no longer useful in the v3 directory
984 protocol: treat them as deprecated, and warn when they're used.
985 - The RedirectExits config option is now deprecated.
988 - Drop the old code to choke directory connections when the
989 corresponding OR connections got full: thanks to the cell queue
990 feature, OR conns don't get full any more.
991 - Remove the old "dns worker" server DNS code: it hasn't been default
992 since 0.1.2.2-alpha, and all the servers are using the new
994 - Remove the code to generate the oldest (v1) directory format.
995 - Remove support for the old bw_accounting file: we've been storing
996 bandwidth accounting information in the state file since
997 0.1.2.5-alpha. This may result in bandwidth accounting errors
998 if you try to upgrade from 0.1.1.x or earlier, or if you try to
999 downgrade to 0.1.1.x or earlier.
1000 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
1001 it, it had no AES, and it hasn't seen any security patches since
1003 - Stop overloading the circuit_t.onionskin field for both "onionskin
1004 from a CREATE cell that we are waiting for a cpuworker to be
1005 assigned" and "onionskin from an EXTEND cell that we are going to
1006 send to an OR as soon as we are connected". Might help with bug 600.
1007 - Remove the tor_strpartition() function: its logic was confused,
1008 and it was only used for one thing that could be implemented far
1010 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
1011 and TorControl.py, as they use the old v0 controller protocol,
1012 and are obsoleted by TorFlow anyway.
1013 - Drop support for v1 rendezvous descriptors, since we never used
1014 them anyway, and the code has probably rotted by now. Based on
1015 patch from Karsten Loesing.
1016 - Stop allowing address masks that do not correspond to bit prefixes.
1017 We have warned about these for a really long time; now it's time
1018 to reject them. (Patch from croup.)
1019 - Remove an optimization in the AES counter-mode code that assumed
1020 that the counter never exceeded 2^68. When the counter can be set
1021 arbitrarily as an IV (as it is by Karsten's new hidden services
1022 code), this assumption no longer holds.
1023 - Disable the SETROUTERPURPOSE controller command: it is now
1027 Changes in version 0.1.2.19 - 2008-01-17
1028 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
1029 exit policy a little bit more conservative so it's safer to run an
1030 exit relay on a home system, and fixes a variety of smaller issues.
1033 - Exit policies now reject connections that are addressed to a
1034 relay's public (external) IP address too, unless
1035 ExitPolicyRejectPrivate is turned off. We do this because too
1036 many relays are running nearby to services that trust them based
1040 - When the clock jumps forward a lot, do not allow the bandwidth
1041 buckets to become negative. Fixes bug 544.
1042 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
1043 on every successful resolve. Reported by Mike Perry.
1044 - Purge old entries from the "rephist" database and the hidden
1045 service descriptor database even when DirPort is zero.
1046 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
1047 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
1048 crashing or mis-answering these requests.
1049 - When we decide to send a 503 response to a request for servers, do
1050 not then also send the server descriptors: this defeats the whole
1051 purpose. Fixes bug 539.
1054 - Changing the ExitPolicyRejectPrivate setting should cause us to
1055 rebuild our server descriptor.
1056 - Fix handling of hex nicknames when answering controller requests for
1057 networkstatus by name, or when deciding whether to warn about
1058 unknown routers in a config option. (Patch from mwenge.)
1059 - Fix a couple of hard-to-trigger autoconf problems that could result
1060 in really weird results on platforms whose sys/types.h files define
1061 nonstandard integer types.
1062 - Don't try to create the datadir when running --verify-config or
1063 --hash-password. Resolves bug 540.
1064 - If we were having problems getting a particular descriptor from the
1065 directory caches, and then we learned about a new descriptor for
1066 that router, we weren't resetting our failure count. Reported
1068 - Although we fixed bug 539 (where servers would send HTTP status 503
1069 responses _and_ send a body too), there are still servers out there
1070 that haven't upgraded. Therefore, make clients parse such bodies
1071 when they receive them.
1072 - Run correctly on systems where rlim_t is larger than unsigned long.
1073 This includes some 64-bit systems.
1074 - Run correctly on platforms (like some versions of OS X 10.5) where
1075 the real limit for number of open files is OPEN_FILES, not rlim_max
1076 from getrlimit(RLIMIT_NOFILES).
1077 - Avoid a spurious free on base64 failure.
1078 - Avoid segfaults on certain complex invocations of
1079 router_get_by_hexdigest().
1080 - Fix rare bug on REDIRECTSTREAM control command when called with no
1081 port set: it could erroneously report an error when none had
1085 Changes in version 0.1.2.18 - 2007-10-28
1086 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
1087 hidden service introduction that were causing huge delays, and a big
1088 bug that was causing some servers to disappear from the network status
1089 lists for a few hours each day.
1091 o Major bugfixes (crashes):
1092 - If a connection is shut down abruptly because of something that
1093 happened inside connection_flushed_some(), do not call
1094 connection_finished_flushing(). Should fix bug 451:
1095 "connection_stop_writing: Assertion conn->write_event failed"
1096 Bugfix on 0.1.2.7-alpha.
1097 - Fix possible segfaults in functions called from
1098 rend_process_relay_cell().
1100 o Major bugfixes (hidden services):
1101 - Hidden services were choosing introduction points uniquely by
1102 hexdigest, but when constructing the hidden service descriptor
1103 they merely wrote the (potentially ambiguous) nickname.
1104 - Clients now use the v2 intro format for hidden service
1105 connections: they specify their chosen rendezvous point by identity
1106 digest rather than by (potentially ambiguous) nickname. These
1107 changes could speed up hidden service connections dramatically.
1109 o Major bugfixes (other):
1110 - Stop publishing a new server descriptor just because we get a
1111 HUP signal. This led (in a roundabout way) to some servers getting
1112 dropped from the networkstatus lists for a few hours each day.
1113 - When looking for a circuit to cannibalize, consider family as well
1114 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
1115 circuit cannibalization).
1116 - When a router wasn't listed in a new networkstatus, we were leaving
1117 the flags for that router alone -- meaning it remained Named,
1118 Running, etc -- even though absence from the networkstatus means
1119 that it shouldn't be considered to exist at all anymore. Now we
1120 clear all the flags for routers that fall out of the networkstatus
1121 consensus. Fixes bug 529.
1124 - Don't try to access (or alter) the state file when running
1125 --list-fingerprint or --verify-config or --hash-password. Resolves
1127 - When generating information telling us how to extend to a given
1128 router, do not try to include the nickname if it is
1129 absent. Resolves bug 467.
1130 - Fix a user-triggerable segfault in expand_filename(). (There isn't
1131 a way to trigger this remotely.)
1132 - When sending a status event to the controller telling it that an
1133 OR address is reachable, set the port correctly. (Previously we
1134 were reporting the dir port.)
1135 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
1136 command. Bugfix on 0.1.2.17.
1137 - When loading bandwidth history, do not believe any information in
1138 the future. Fixes bug 434.
1139 - When loading entry guard information, do not believe any information
1141 - When we have our clock set far in the future and generate an
1142 onion key, then re-set our clock to be correct, we should not stop
1143 the onion key from getting rotated.
1144 - On some platforms, accept() can return a broken address. Detect
1145 this more quietly, and deal accordingly. Fixes bug 483.
1146 - It's not actually an error to find a non-pending entry in the DNS
1147 cache when canceling a pending resolve. Don't log unless stuff
1148 is fishy. Resolves bug 463.
1149 - Don't reset trusted dir server list when we set a configuration
1150 option. Patch from Robert Hogan.
1153 Changes in version 0.1.2.17 - 2007-08-30
1154 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
1155 X bundles. Vidalia 0.0.14 makes authentication required for the
1156 ControlPort in the default configuration, which addresses important
1157 security risks. Everybody who uses Vidalia (or another controller)
1160 In addition, this Tor update fixes major load balancing problems with
1161 path selection, which should speed things up a lot once many people
1164 o Major bugfixes (security):
1165 - We removed support for the old (v0) control protocol. It has been
1166 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
1167 become more of a headache than it's worth.
1169 o Major bugfixes (load balancing):
1170 - When choosing nodes for non-guard positions, weight guards
1171 proportionally less, since they already have enough load. Patch
1173 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
1174 will allow fast Tor servers to get more attention.
1175 - When we're upgrading from an old Tor version, forget our current
1176 guards and pick new ones according to the new weightings. These
1177 three load balancing patches could raise effective network capacity
1178 by a factor of four. Thanks to Mike Perry for measurements.
1180 o Major bugfixes (stream expiration):
1181 - Expire not-yet-successful application streams in all cases if
1182 they've been around longer than SocksTimeout. Right now there are
1183 some cases where the stream will live forever, demanding a new
1184 circuit every 15 seconds. Fixes bug 454; reported by lodger.
1186 o Minor features (controller):
1187 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
1188 is valid before any authentication has been received. It tells
1189 a controller what kind of authentication is expected, and what
1190 protocol is spoken. Implements proposal 119.
1192 o Minor bugfixes (performance):
1193 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
1194 greatly speeding up loading cached-routers from disk on startup.
1195 - Disable sentinel-based debugging for buffer code: we squashed all
1196 the bugs that this was supposed to detect a long time ago, and now
1197 its only effect is to change our buffer sizes from nice powers of
1198 two (which platform mallocs tend to like) to values slightly over
1199 powers of two (which make some platform mallocs sad).
1201 o Minor bugfixes (misc):
1202 - If exit bandwidth ever exceeds one third of total bandwidth, then
1203 use the correct formula to weight exit nodes when choosing paths.
1204 Based on patch from Mike Perry.
1205 - Choose perfectly fairly among routers when choosing by bandwidth and
1206 weighting by fraction of bandwidth provided by exits. Previously, we
1207 would choose with only approximate fairness, and correct ourselves
1208 if we ran off the end of the list.
1209 - If we require CookieAuthentication but we fail to write the
1210 cookie file, we would warn but not exit, and end up in a state
1211 where no controller could authenticate. Now we exit.
1212 - If we require CookieAuthentication, stop generating a new cookie
1213 every time we change any piece of our config.
1214 - Refuse to start with certain directory authority keys, and
1215 encourage people using them to stop.
1216 - Terminate multi-line control events properly. Original patch
1218 - Fix a minor memory leak when we fail to find enough suitable
1219 servers to choose a circuit.
1220 - Stop leaking part of the descriptor when we run into a particularly
1221 unparseable piece of it.
1224 Changes in version 0.1.2.16 - 2007-08-01
1225 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
1226 remote attacker in certain situations to rewrite the user's torrc
1227 configuration file. This can completely compromise anonymity of users
1228 in most configurations, including those running the Vidalia bundles,
1229 TorK, etc. Or worse.
1231 o Major security fixes:
1232 - Close immediately after missing authentication on control port;
1233 do not allow multiple authentication attempts.
1236 Changes in version 0.1.2.15 - 2007-07-17
1237 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
1238 problems, fixes compilation on BSD, and fixes a variety of other
1239 bugs. Everybody should upgrade.
1241 o Major bugfixes (compilation):
1242 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
1244 o Major bugfixes (crashes):
1245 - Try even harder not to dereference the first character after
1246 an mmap(). Reported by lodger.
1247 - Fix a crash bug in directory authorities when we re-number the
1248 routerlist while inserting a new router.
1249 - When the cached-routers file is an even multiple of the page size,
1250 don't run off the end and crash. (Fixes bug 455; based on idea
1252 - Fix eventdns.c behavior on Solaris: It is critical to include
1253 orconfig.h _before_ sys/types.h, so that we can get the expected
1254 definition of _FILE_OFFSET_BITS.
1256 o Major bugfixes (security):
1257 - Fix a possible buffer overrun when using BSD natd support. Bug
1259 - When sending destroy cells from a circuit's origin, don't include
1260 the reason for tearing down the circuit. The spec says we didn't,
1261 and now we actually don't. Reported by lodger.
1262 - Keep streamids from different exits on a circuit separate. This
1263 bug may have allowed other routers on a given circuit to inject
1264 cells into streams. Reported by lodger; fixes bug 446.
1265 - If there's a never-before-connected-to guard node in our list,
1266 never choose any guards past it. This way we don't expand our
1267 guard list unless we need to.
1269 o Minor bugfixes (guard nodes):
1270 - Weight guard selection by bandwidth, so that low-bandwidth nodes
1271 don't get overused as guards.
1273 o Minor bugfixes (directory):
1274 - Correctly count the number of authorities that recommend each
1275 version. Previously, we were under-counting by 1.
1276 - Fix a potential crash bug when we load many server descriptors at
1277 once and some of them make others of them obsolete. Fixes bug 458.
1279 o Minor bugfixes (hidden services):
1280 - Stop tearing down the whole circuit when the user asks for a
1281 connection to a port that the hidden service didn't configure.
1284 o Minor bugfixes (misc):
1285 - On Windows, we were preventing other processes from reading
1286 cached-routers while Tor was running. Reported by janbar.
1287 - Fix a possible (but very unlikely) bug in picking routers by
1288 bandwidth. Add a log message to confirm that it is in fact
1289 unlikely. Patch from lodger.
1290 - Backport a couple of memory leak fixes.
1291 - Backport miscellaneous cosmetic bugfixes.
1294 Changes in version 0.1.2.14 - 2007-05-25
1295 Tor 0.1.2.14 changes the addresses of two directory authorities (this
1296 change especially affects those who serve or use hidden services),
1297 and fixes several other crash- and security-related bugs.
1299 o Directory authority changes:
1300 - Two directory authorities (moria1 and moria2) just moved to new
1301 IP addresses. This change will particularly affect those who serve
1302 or use hidden services.
1304 o Major bugfixes (crashes):
1305 - If a directory server runs out of space in the connection table
1306 as it's processing a begin_dir request, it will free the exit stream
1307 but leave it attached to the circuit, leading to unpredictable
1308 behavior. (Reported by seeess, fixes bug 425.)
1309 - Fix a bug in dirserv_remove_invalid() that would cause authorities
1310 to corrupt memory under some really unlikely scenarios.
1311 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
1312 - Avoid segfaults when reading from mmaped descriptor file. (Reported
1315 o Major bugfixes (security):
1316 - When choosing an entry guard for a circuit, avoid using guards
1317 that are in the same family as the chosen exit -- not just guards
1318 that are exactly the chosen exit. (Reported by lodger.)
1320 o Major bugfixes (resource management):
1321 - If a directory authority is down, skip it when deciding where to get
1322 networkstatus objects or descriptors. Otherwise we keep asking
1323 every 10 seconds forever. Fixes bug 384.
1324 - Count it as a failure if we fetch a valid network-status but we
1325 don't want to keep it. Otherwise we'll keep fetching it and keep
1326 not wanting to keep it. Fixes part of bug 422.
1327 - If all of our dirservers have given us bad or no networkstatuses
1328 lately, then stop hammering them once per minute even when we
1329 think they're failed. Fixes another part of bug 422.
1332 - Actually set the purpose correctly for descriptors inserted with
1334 - When we have k non-v2 authorities in our DirServer config,
1335 we ignored the last k authorities in the list when updating our
1337 - Correctly back-off from requesting router descriptors that we are
1338 having a hard time downloading.
1339 - Read resolv.conf files correctly on platforms where read() returns
1340 partial results on small file reads.
1341 - Don't rebuild the entire router store every time we get 32K of
1342 routers: rebuild it when the journal gets very large, or when
1343 the gaps in the store get very large.
1346 - When routers publish SVN revisions in their router descriptors,
1347 authorities now include those versions correctly in networkstatus
1349 - Warn when using a version of libevent before 1.3b to run a server on
1350 OSX or BSD: these versions interact badly with userspace threads.
1353 Changes in version 0.1.2.13 - 2007-04-24
1354 This release features some major anonymity fixes, such as safer path
1355 selection; better client performance; faster bootstrapping, better
1356 address detection, and better DNS support for servers; write limiting as
1357 well as read limiting to make servers easier to run; and a huge pile of
1358 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
1360 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
1361 of the Freenode IRC network, remembering his patience and vision for
1362 free speech on the Internet.
1364 o Major features, client performance:
1365 - Weight directory requests by advertised bandwidth. Now we can
1366 let servers enable write limiting but still allow most clients to
1367 succeed at their directory requests. (We still ignore weights when
1368 choosing a directory authority; I hope this is a feature.)
1369 - Stop overloading exit nodes -- avoid choosing them for entry or
1370 middle hops when the total bandwidth available from non-exit nodes
1371 is much higher than the total bandwidth available from exit nodes.
1372 - Rather than waiting a fixed amount of time between retrying
1373 application connections, we wait only 10 seconds for the first,
1374 10 seconds for the second, and 15 seconds for each retry after
1375 that. Hopefully this will improve the expected user experience.
1376 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
1377 to open a stream fails; now we do in more cases. This should
1378 make clients able to find a good exit faster in some cases, since
1379 unhandleable requests will now get an error rather than timing out.
1381 o Major features, client functionality:
1382 - Implement BEGIN_DIR cells, so we can connect to a directory
1383 server via TLS to do encrypted directory requests rather than
1384 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
1385 config options if you like. For now, this feature only works if
1386 you already have a descriptor for the destination dirserver.
1387 - Add support for transparent application connections: this basically
1388 bundles the functionality of trans-proxy-tor into the Tor
1389 mainline. Now hosts with compliant pf/netfilter implementations
1390 can redirect TCP connections straight to Tor without diverting
1391 through SOCKS. (Based on patch from tup.)
1392 - Add support for using natd; this allows FreeBSDs earlier than
1393 5.1.2 to have ipfw send connections through Tor without using
1394 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
1396 o Major features, servers:
1397 - Setting up a dyndns name for your server is now optional: servers
1398 with no hostname or IP address will learn their IP address by
1399 asking the directory authorities. This code only kicks in when you
1400 would normally have exited with a "no address" error. Nothing's
1401 authenticated, so use with care.
1402 - Directory servers now spool server descriptors, v1 directories,
1403 and v2 networkstatus objects to buffers as needed rather than en
1404 masse. They also mmap the cached-routers files. These steps save
1406 - Stop requiring clients to have well-formed certificates, and stop
1407 checking nicknames in certificates. (Clients have certificates so
1408 that they can look like Tor servers, but in the future we might want
1409 to allow them to look like regular TLS clients instead. Nicknames
1410 in certificates serve no purpose other than making our protocol
1411 easier to recognize on the wire.) Implements proposal 106.
1413 o Improvements on DNS support:
1414 - Add "eventdns" asynchronous dns library originally based on code
1415 from Adam Langley. Now we can discard the old rickety dnsworker
1416 concept, and support a wider variety of DNS functions. Allows
1417 multithreaded builds on NetBSD and OpenBSD again.
1418 - Add server-side support for "reverse" DNS lookups (using PTR
1419 records so clients can determine the canonical hostname for a given
1420 IPv4 address). Only supported by servers using eventdns; servers
1421 now announce in their descriptors if they don't support eventdns.
1422 - Workaround for name servers (like Earthlink's) that hijack failing
1423 DNS requests and replace the no-such-server answer with a "helpful"
1424 redirect to an advertising-driven search portal. Also work around
1425 DNS hijackers who "helpfully" decline to hijack known-invalid
1426 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
1427 lets you turn it off.
1428 - Servers now check for the case when common DNS requests are going to
1429 wildcarded addresses (i.e. all getting the same answer), and change
1430 their exit policy to reject *:* if it's happening.
1431 - When asked to resolve a hostname, don't use non-exit servers unless
1432 requested to do so. This allows servers with broken DNS to be
1433 useful to the network.
1434 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
1435 useless IPv6 DNS resolves.
1436 - Specify and implement client-side SOCKS5 interface for reverse DNS
1437 lookups (see doc/socks-extensions.txt). Also cache them.
1438 - When we change nameservers or IP addresses, reset and re-launch
1439 our tests for DNS hijacking.
1441 o Improvements on reachability testing:
1442 - Servers send out a burst of long-range padding cells once they've
1443 established that they're reachable. Spread them over 4 circuits,
1444 so hopefully a few will be fast. This exercises bandwidth and
1445 bootstraps them into the directory more quickly.
1446 - When we find our DirPort to be reachable, publish a new descriptor
1447 so we'll tell the world (reported by pnx).
1448 - Directory authorities now only decide that routers are reachable
1449 if their identity keys are as expected.
1450 - Do DirPort reachability tests less often, since a single test
1451 chews through many circuits before giving up.
1452 - Avoid some false positives during reachability testing: don't try
1453 to test via a server that's on the same /24 network as us.
1454 - Start publishing one minute or so after we find our ORPort
1455 to be reachable. This will help reduce the number of descriptors
1456 we have for ourselves floating around, since it's quite likely
1457 other things (e.g. DirPort) will change during that minute too.
1458 - Routers no longer try to rebuild long-term connections to directory
1459 authorities, and directory authorities no longer try to rebuild
1460 long-term connections to all servers. We still don't hang up
1461 connections in these two cases though -- we need to look at it
1462 more carefully to avoid flapping, and we likely need to wait til
1463 0.1.1.x is obsolete.
1465 o Improvements on rate limiting:
1466 - Enable write limiting as well as read limiting. Now we sacrifice
1467 capacity if we're pushing out lots of directory traffic, rather
1468 than overrunning the user's intended bandwidth limits.
1469 - Include TLS overhead when counting bandwidth usage; previously, we
1470 would count only the bytes sent over TLS, but not the bytes used
1472 - Servers decline directory requests much more aggressively when
1473 they're low on bandwidth. Otherwise they end up queueing more and
1474 more directory responses, which can't be good for latency.
1475 - But never refuse directory requests from local addresses.
1476 - Be willing to read or write on local connections (e.g. controller
1477 connections) even when the global rate limiting buckets are empty.
1478 - Flush local controller connection buffers periodically as we're
1479 writing to them, so we avoid queueing 4+ megabytes of data before
1481 - Revise and clean up the torrc.sample that we ship with; add
1482 a section for BandwidthRate and BandwidthBurst.
1484 o Major features, NT services:
1485 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
1486 command-line flag so that admins can override the default by saying
1487 "tor --service install --user "SomeUser"". This will not affect
1488 existing installed services. Also, warn the user that the service
1489 will look for its configuration file in the service user's
1490 %appdata% directory. (We can't do the "hardwire the user's appdata
1491 directory" trick any more, since we may not have read access to that
1493 - Support running the Tor service with a torrc not in the same
1494 directory as tor.exe and default to using the torrc located in
1495 the %appdata%\Tor\ of the user who installed the service. Patch
1497 - Add an --ignore-missing-torrc command-line option so that we can
1498 get the "use sensible defaults if the configuration file doesn't
1499 exist" behavior even when specifying a torrc location on the
1501 - When stopping an NT service, wait up to 10 sec for it to actually
1502 stop. (Patch from Matt Edman; resolves bug 295.)
1504 o Directory authority improvements:
1505 - Stop letting hibernating or obsolete servers affect uptime and
1507 - Stop listing hibernating servers in the v1 directory.
1508 - Authorities no longer recommend exits as guards if this would shift
1509 too much load to the exit nodes.
1510 - Authorities now specify server versions in networkstatus. This adds
1511 about 2% to the size of compressed networkstatus docs, and allows
1512 clients to tell which servers support BEGIN_DIR and which don't.
1513 The implementation is forward-compatible with a proposed future
1514 protocol version scheme not tied to Tor versions.
1515 - DirServer configuration lines now have an orport= option so
1516 clients can open encrypted tunnels to the authorities without
1517 having downloaded their descriptors yet. Enabled for moria1,
1518 moria2, tor26, and lefkada now in the default configuration.
1519 - Add a BadDirectory flag to network status docs so that authorities
1520 can (eventually) tell clients about caches they believe to be
1521 broken. Not used yet.
1522 - Allow authorities to list nodes as bad exits in their
1523 approved-routers file by fingerprint or by address. If most
1524 authorities set a BadExit flag for a server, clients don't think
1525 of it as a general-purpose exit. Clients only consider authorities
1526 that advertise themselves as listing bad exits.
1527 - Patch from Steve Hildrey: Generate network status correctly on
1528 non-versioning dirservers.
1529 - Have directory authorities allow larger amounts of drift in uptime
1530 without replacing the server descriptor: previously, a server that
1531 restarted every 30 minutes could have 48 "interesting" descriptors
1533 - Reserve the nickname "Unnamed" for routers that can't pick
1534 a hostname: any router can call itself Unnamed; directory
1535 authorities will never allocate Unnamed to any particular router;
1536 clients won't believe that any router is the canonical Unnamed.
1538 o Directory mirrors and clients:
1539 - Discard any v1 directory info that's over 1 month old (for
1540 directories) or over 1 week old (for running-routers lists).
1541 - Clients track responses with status 503 from dirservers. After a
1542 dirserver has given us a 503, we try not to use it until an hour has
1543 gone by, or until we have no dirservers that haven't given us a 503.
1544 - When we get a 503 from a directory, and we're not a server, we no
1545 longer count the failure against the total number of failures
1546 allowed for the object we're trying to download.
1547 - Prepare for servers to publish descriptors less often: never
1548 discard a descriptor simply for being too old until either it is
1549 recommended by no authorities, or until we get a better one for
1550 the same router. Make caches consider retaining old recommended
1551 routers for even longer.
1552 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
1553 headers for content, so that we can work better in the presence of
1554 caching HTTP proxies.
1555 - Stop fetching descriptors if you're not a dir mirror and you
1556 haven't tried to establish any circuits lately. (This currently
1557 causes some dangerous behavior, because when you start up again
1558 you'll use your ancient server descriptors.)
1560 o Major fixes, crashes:
1561 - Stop crashing when the controller asks us to resetconf more than
1562 one config option at once. (Vidalia 0.0.11 does this.)
1563 - Fix a longstanding obscure crash bug that could occur when we run
1564 out of DNS worker processes, if we're not using eventdns. (Resolves
1566 - Fix an assert that could trigger if a controller quickly set then
1567 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
1568 - Avoid crash when telling controller about stream-status and a
1570 - Avoid sending junk to controllers or segfaulting when a controller
1571 uses EVENT_NEW_DESC with verbose nicknames.
1572 - Stop triggering asserts if the controller tries to extend hidden
1573 service circuits (reported by mwenge).
1574 - If we start a server with ClientOnly 1, then set ClientOnly to 0
1575 and hup, stop triggering an assert based on an empty onion_key.
1576 - Mask out all signals in sub-threads; only the libevent signal
1577 handler should be processing them. This should prevent some crashes
1578 on some machines using pthreads. (Patch from coderman.)
1579 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
1581 o Major fixes, anonymity/security:
1582 - Automatically avoid picking more than one node from the same
1583 /16 network when constructing a circuit. Add an
1584 "EnforceDistinctSubnets" option to let people disable it if they
1585 want to operate private test networks on a single subnet.
1586 - When generating bandwidth history, round down to the nearest
1587 1k. When storing accounting data, round up to the nearest 1k.
1588 - When we're running as a server, remember when we last rotated onion
1589 keys, so that we will rotate keys once they're a week old even if
1590 we never stay up for a week ourselves.
1591 - If a client asked for a server by name, and there's a named server
1592 in our network-status but we don't have its descriptor yet, we
1593 could return an unnamed server instead.
1594 - Reject (most) attempts to use Tor circuits with length one. (If
1595 many people start using Tor as a one-hop proxy, exit nodes become
1596 a more attractive target for compromise.)
1597 - Just because your DirPort is open doesn't mean people should be
1598 able to remotely teach you about hidden service descriptors. Now
1599 only accept rendezvous posts if you've got HSAuthoritativeDir set.
1600 - Fix a potential race condition in the rpm installer. Found by
1602 - Do not log IPs with TLS failures for incoming TLS
1603 connections. (Fixes bug 382.)
1605 o Major fixes, other:
1606 - If our system clock jumps back in time, don't publish a negative
1607 uptime in the descriptor.
1608 - When we start during an accounting interval before it's time to wake
1609 up, remember to wake up at the correct time. (May fix bug 342.)
1610 - Previously, we would cache up to 16 old networkstatus documents
1611 indefinitely, if they came from nontrusted authorities. Now we
1612 discard them if they are more than 10 days old.
1613 - When we have a state file we cannot parse, tell the user and
1614 move it aside. Now we avoid situations where the user starts
1615 Tor in 1904, Tor writes a state file with that timestamp in it,
1616 the user fixes her clock, and Tor refuses to start.
1617 - Publish a new descriptor after we hup/reload. This is important
1618 if our config has changed such that we'll want to start advertising
1619 our DirPort now, etc.
1620 - If we are using an exit enclave and we can't connect, e.g. because
1621 its webserver is misconfigured to not listen on localhost, then
1622 back off and try connecting from somewhere else before we fail.
1624 o New config options or behaviors:
1625 - When EntryNodes are configured, rebuild the guard list to contain,
1626 in order: the EntryNodes that were guards before; the rest of the
1627 EntryNodes; the nodes that were guards before.
1628 - Do not warn when individual nodes in the configuration's EntryNodes,
1629 ExitNodes, etc are down: warn only when all possible nodes
1630 are down. (Fixes bug 348.)
1631 - Put a lower-bound on MaxAdvertisedBandwidth.
1632 - Start using the state file to store bandwidth accounting data:
1633 the bw_accounting file is now obsolete. We'll keep generating it
1634 for a while for people who are still using 0.1.2.4-alpha.
1635 - Try to batch changes to the state file so that we do as few
1636 disk writes as possible while still storing important things in
1638 - The state file and the bw_accounting file get saved less often when
1639 the AvoidDiskWrites config option is set.
1640 - Make PIDFile work on Windows.
1641 - Add internal descriptions for a bunch of configuration options:
1642 accessible via controller interface and in comments in saved
1644 - Reject *:563 (NNTPS) in the default exit policy. We already reject
1645 NNTP by default, so this seems like a sensible addition.
1646 - Clients now reject hostnames with invalid characters. This should
1647 avoid some inadvertent info leaks. Add an option
1648 AllowNonRFC953Hostnames to disable this behavior, in case somebody
1649 is running a private network with hosts called @, !, and #.
1650 - Check for addresses with invalid characters at the exit as well,
1651 and warn less verbosely when they fail. You can override this by
1652 setting ServerDNSAllowNonRFC953Addresses to 1.
1653 - Remove some options that have been deprecated since at least
1654 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
1655 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
1656 to set log options. Mark PathlenCoinWeight as obsolete.
1657 - Stop accepting certain malformed ports in configured exit policies.
1658 - When the user uses bad syntax in the Log config line, stop
1659 suggesting other bad syntax as a replacement.
1660 - Add new config option "ResolvConf" to let the server operator
1661 choose an alternate resolve.conf file when using eventdns.
1662 - If one of our entry guards is on the ExcludeNodes list, or the
1663 directory authorities don't think it's a good guard, treat it as
1664 if it were unlisted: stop using it as a guard, and throw it off
1665 the guards list if it stays that way for a long time.
1666 - Allow directory authorities to be marked separately as authorities
1667 for the v1 directory protocol, the v2 directory protocol, and
1668 as hidden service directories, to make it easier to retire old
1669 authorities. V1 authorities should set "HSAuthoritativeDir 1"
1670 to continue being hidden service authorities too.
1671 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
1672 - Make TrackExitHosts case-insensitive, and fix the behavior of
1673 ".suffix" TrackExitHosts items to avoid matching in the middle of
1675 - New DirPort behavior: if you have your dirport set, you download
1676 descriptors aggressively like a directory mirror, whether or not
1680 - Create a new file ReleaseNotes which was the old ChangeLog. The
1681 new ChangeLog file now includes the notes for all development
1683 - Add a new address-spec.txt document to describe our special-case
1684 addresses: .exit, .onion, and .noconnnect.
1685 - Fork the v1 directory protocol into its own spec document,
1686 and mark dir-spec.txt as the currently correct (v2) spec.
1688 o Packaging, porting, and contrib
1689 - "tor --verify-config" now exits with -1(255) or 0 depending on
1690 whether the config options are bad or good.
1691 - The Debian package now uses --verify-config when (re)starting,
1692 to distinguish configuration errors from other errors.
1693 - Adapt a patch from goodell to let the contrib/exitlist script
1694 take arguments rather than require direct editing.
1695 - Prevent the contrib/exitlist script from printing the same
1696 result more than once.
1697 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
1698 - In the hidden service example in torrc.sample, stop recommending
1699 esoteric and discouraged hidden service options.
1700 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
1701 values before failing, and always enables eventdns.
1702 - Try to detect Windows correctly when cross-compiling.
1703 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
1704 Try to fix this in configure.in by checking for most functions
1705 before we check for libevent.
1706 - Update RPMs to require libevent 1.2.
1707 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
1708 or later. Log when we are doing this, so we can diagnose it when
1709 it fails. (Also, recommend libevent 1.1b for kqueue and
1710 win32 methods; deprecate libevent 1.0b harder; make libevent
1711 recommendation system saner.)
1712 - Build with recent (1.3+) libevents on platforms that do not
1713 define the nonstandard types "u_int8_t" and friends.
1714 - Remove architecture from OS X builds. The official builds are
1715 now universal binaries.
1716 - Run correctly on OS X platforms with case-sensitive filesystems.
1717 - Correctly set maximum connection limit on Cygwin. (This time
1719 - Start compiling on MinGW on Windows (patches from Mike Chiussi
1721 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
1722 - Finally fix the openssl warnings from newer gccs that believe that
1723 ignoring a return value is okay, but casting a return value and
1724 then ignoring it is a sign of madness.
1725 - On architectures where sizeof(int)>4, still clamp declarable
1726 bandwidth to INT32_MAX.
1728 o Minor features, controller:
1729 - Warn the user when an application uses the obsolete binary v0
1730 control protocol. We're planning to remove support for it during
1731 the next development series, so it's good to give people some
1733 - Add STREAM_BW events to report per-entry-stream bandwidth
1734 use. (Patch from Robert Hogan.)
1735 - Rate-limit SIGNEWNYM signals in response to controllers that
1736 impolitely generate them for every single stream. (Patch from
1737 mwenge; closes bug 394.)
1738 - Add a REMAP status to stream events to note that a stream's
1739 address has changed because of a cached address or a MapAddress
1741 - Make REMAP stream events have a SOURCE (cache or exit), and
1742 make them generated in every case where we get a successful
1743 connected or resolved cell.
1744 - Track reasons for OR connection failure; make these reasons
1745 available via the controller interface. (Patch from Mike Perry.)
1746 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
1747 can learn when clients are sending malformed hostnames to Tor.
1748 - Specify and implement some of the controller status events.
1749 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
1750 - Reimplement GETINFO so that info/names stays in sync with the
1752 - Implement "GETINFO fingerprint".
1753 - Implement "SETEVENTS GUARD" so controllers can get updates on
1754 entry guard status as it changes.
1755 - Make all connections to addresses of the form ".noconnect"
1756 immediately get closed. This lets application/controller combos
1757 successfully test whether they're talking to the same Tor by
1758 watching for STREAM events.
1759 - Add a REASON field to CIRC events; for backward compatibility, this
1760 field is sent only to controllers that have enabled the extended
1761 event format. Also, add additional reason codes to explain why
1762 a given circuit has been destroyed or truncated. (Patches from
1764 - Add a REMOTE_REASON field to extended CIRC events to tell the
1765 controller why a remote OR told us to close a circuit.
1766 - Stream events also now have REASON and REMOTE_REASON fields,
1767 working much like those for circuit events.
1768 - There's now a GETINFO ns/... field so that controllers can ask Tor
1769 about the current status of a router.
1770 - A new event type "NS" to inform a controller when our opinion of
1771 a router's status has changed.
1772 - Add a GETINFO events/names and GETINFO features/names so controllers
1773 can tell which events and features are supported.
1774 - A new CLEARDNSCACHE signal to allow controllers to clear the
1775 client-side DNS cache without expiring circuits.
1776 - Fix CIRC controller events so that controllers can learn the
1777 identity digests of non-Named servers used in circuit paths.
1778 - Let controllers ask for more useful identifiers for servers. Instead
1779 of learning identity digests for un-Named servers and nicknames
1780 for Named servers, the new identifiers include digest, nickname,
1781 and indication of Named status. Off by default; see control-spec.txt
1782 for more information.
1783 - Add a "getinfo address" controller command so it can display Tor's
1784 best guess to the user.
1785 - New controller event to alert the controller when our server
1786 descriptor has changed.
1787 - Give more meaningful errors on controller authentication failure.
1788 - Export the default exit policy via the control port, so controllers
1789 don't need to guess what it is / will be later.
1791 o Minor bugfixes, controller:
1792 - When creating a circuit via the controller, send a 'launched'
1793 event when we're done, so we follow the spec better.
1794 - Correct the control spec to match how the code actually responds
1795 to 'getinfo addr-mappings/*'. Reported by daejees.
1796 - The control spec described a GUARDS event, but the code
1797 implemented a GUARD event. Standardize on GUARD, but let people
1798 ask for GUARDS too. Reported by daejees.
1799 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
1800 clear the corresponding on_circuit variable, and remember later
1801 that we don't need to send a redundant CLOSED event. (Resolves part
1803 - Report events where a resolve succeeded or where we got a socks
1804 protocol error correctly, rather than calling both of them
1806 - Change reported stream target addresses to IP consistently when
1807 we finally get the IP from an exit node.
1808 - Send log messages to the controller even if they happen to be very
1810 - Flush ERR-level controller status events just like we currently
1811 flush ERR-level log events, so that a Tor shutdown doesn't prevent
1812 the controller from learning about current events.
1813 - Report the circuit number correctly in STREAM CLOSED events. Bug
1814 reported by Mike Perry.
1815 - Do not report bizarre values for results of accounting GETINFOs
1816 when the last second's write or read exceeds the allotted bandwidth.
1817 - Report "unrecognized key" rather than an empty string when the
1818 controller tries to fetch a networkstatus that doesn't exist.
1819 - When the controller does a "GETINFO network-status", tell it
1820 about even those routers whose descriptors are very old, and use
1821 long nicknames where appropriate.
1822 - Fix handling of verbose nicknames with ORCONN controller events:
1823 make them show up exactly when requested, rather than exactly when
1825 - Controller signals now work on non-Unix platforms that don't define
1826 SIGUSR1 and SIGUSR2 the way we expect.
1827 - Respond to SIGNAL command before we execute the signal, in case
1828 the signal shuts us down. Suggested by Karsten Loesing.
1829 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
1831 o Minor features, code performance:
1832 - Major performance improvement on inserting descriptors: change
1833 algorithm from O(n^2) to O(n).
1834 - Do not rotate onion key immediately after setting it for the first
1836 - Call router_have_min_dir_info half as often. (This is showing up in
1837 some profiles, but not others.)
1838 - When using GCC, make log_debug never get called at all, and its
1839 arguments never get evaluated, when no debug logs are configured.
1840 (This is showing up in some profiles, but not others.)
1841 - Statistics dumped by -USR2 now include a breakdown of public key
1842 operations, for profiling.
1843 - Make the common memory allocation path faster on machines where
1844 malloc(0) returns a pointer.
1845 - Split circuit_t into origin_circuit_t and or_circuit_t, and
1846 split connection_t into edge, or, dir, control, and base structs.
1847 These will save quite a bit of memory on busy servers, and they'll
1848 also help us track down bugs in the code and bugs in the spec.
1849 - Use OpenSSL's AES implementation on platforms where it's faster.
1850 This could save us as much as 10% CPU usage.
1852 o Minor features, descriptors and descriptor handling:
1853 - Avoid duplicate entries on MyFamily line in server descriptor.
1854 - When Tor receives a router descriptor that it asked for, but
1855 no longer wants (because it has received fresh networkstatuses
1856 in the meantime), do not warn the user. Cache the descriptor if
1857 we're a cache; drop it if we aren't.
1858 - Servers no longer ever list themselves in their "family" line,
1859 even if configured to do so. This makes it easier to configure
1860 family lists conveniently.
1862 o Minor fixes, confusing/misleading log messages:
1863 - Display correct results when reporting which versions are
1864 recommended, and how recommended they are. (Resolves bug 383.)
1865 - Inform the server operator when we decide not to advertise a
1866 DirPort due to AccountingMax enabled or a low BandwidthRate.
1867 - Only include function names in log messages for info/debug messages.
1868 For notice/warn/err, the content of the message should be clear on
1869 its own, and printing the function name only confuses users.
1870 - Remove even more protocol-related warnings from Tor server logs,
1871 such as bad TLS handshakes and malformed begin cells.
1872 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
1873 when the IP address is mapped through MapAddress to a hostname.
1874 - Fix misleading log messages: an entry guard that is "unlisted",
1875 as well as not known to be "down" (because we've never heard
1876 of it), is not therefore "up".
1878 o Minor fixes, old/obsolete behavior:
1879 - Start assuming we can use a create_fast cell if we don't know
1880 what version a router is running.
1881 - We no longer look for identity and onion keys in "identity.key" and
1882 "onion.key" -- these were replaced by secret_id_key and
1883 secret_onion_key in 0.0.8pre1.
1884 - We no longer require unrecognized directory entries to be
1886 - Drop compatibility with obsolete Tors that permit create cells
1887 to have the wrong circ_id_type.
1888 - Remove code to special-case "-cvs" ending, since it has not
1889 actually mattered since 0.0.9.
1890 - Don't re-write the fingerprint file every restart, unless it has
1893 o Minor fixes, misc client-side behavior:
1894 - Always remove expired routers and networkstatus docs before checking
1895 whether we have enough information to build circuits. (Fixes
1897 - When computing clock skew from directory HTTP headers, consider what
1898 time it was when we finished asking for the directory, not what
1900 - Make our socks5 handling more robust to broken socks clients:
1901 throw out everything waiting on the buffer in between socks
1902 handshake phases, since they can't possibly (so the theory
1903 goes) have predicted what we plan to respond to them.
1904 - Expire socks connections if they spend too long waiting for the
1905 handshake to finish. Previously we would let them sit around for
1906 days, if the connecting application didn't close them either.
1907 - And if the socks handshake hasn't started, don't send a
1908 "DNS resolve socks failed" handshake reply; just close it.
1909 - If the user asks to use invalid exit nodes, be willing to use
1911 - Track unreachable entry guards correctly: don't conflate
1912 'unreachable by us right now' with 'listed as down by the directory
1913 authorities'. With the old code, if a guard was unreachable by us
1914 but listed as running, it would clog our guard list forever.
1915 - Behave correctly in case we ever have a network with more than
1916 2GB/s total advertised capacity.
1917 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
1918 - Fix a memory leak when we ask for "all" networkstatuses and we
1919 get one we don't recognize.
1922 Changes in version 0.1.1.26 - 2006-12-14
1923 o Security bugfixes:
1924 - Stop sending the HttpProxyAuthenticator string to directory
1925 servers when directory connections are tunnelled through Tor.
1926 - Clients no longer store bandwidth history in the state file.
1927 - Do not log introduction points for hidden services if SafeLogging
1931 - Fix an assert failure when a directory authority sets
1932 AuthDirRejectUnlisted and then receives a descriptor from an
1933 unlisted router (reported by seeess).
1936 Changes in version 0.1.1.25 - 2006-11-04
1938 - When a client asks us to resolve (rather than connect to)
1939 an address, and we have a cached answer, give them the cached
1940 answer. Previously, we would give them no answer at all.
1941 - We were building exactly the wrong circuits when we predict
1942 hidden service requirements, meaning Tor would have to build all
1943 its circuits on demand.
1944 - If none of our live entry guards have a high uptime, but we
1945 require a guard with a high uptime, try adding a new guard before
1946 we give up on the requirement. This patch should make long-lived
1947 connections more stable on average.
1948 - When testing reachability of our DirPort, don't launch new
1949 tests when there's already one in progress -- unreachable
1950 servers were stacking up dozens of testing streams.
1952 o Security bugfixes:
1953 - When the user sends a NEWNYM signal, clear the client-side DNS
1954 cache too. Otherwise we continue to act on previous information.
1957 - Avoid a memory corruption bug when creating a hash table for
1959 - Avoid possibility of controller-triggered crash when misusing
1960 certain commands from a v0 controller on platforms that do not
1961 handle printf("%s",NULL) gracefully.
1962 - Avoid infinite loop on unexpected controller input.
1963 - Don't log spurious warnings when we see a circuit close reason we
1964 don't recognize; it's probably just from a newer version of Tor.
1965 - Add Vidalia to the OS X uninstaller script, so when we uninstall
1966 Tor/Privoxy we also uninstall Vidalia.
1969 Changes in version 0.1.1.24 - 2006-09-29
1971 - Allow really slow clients to not hang up five minutes into their
1972 directory downloads (suggested by Adam J. Richter).
1973 - Fix major performance regression from 0.1.0.x: instead of checking
1974 whether we have enough directory information every time we want to
1975 do something, only check when the directory information has changed.
1976 This should improve client CPU usage by 25-50%.
1977 - Don't crash if, after a server has been running for a while,
1978 it can't resolve its hostname.
1979 - When a client asks us to resolve (not connect to) an address,
1980 and we have a cached answer, give them the cached answer.
1981 Previously, we would give them no answer at all.
1984 - Allow Tor to start when RunAsDaemon is set but no logs are set.
1985 - Don't crash when the controller receives a third argument to an
1986 "extendcircuit" request.
1987 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
1988 response; fix error code when "getinfo dir/status/" fails.
1989 - Fix configure.in to not produce broken configure files with
1990 more recent versions of autoconf. Thanks to Clint for his auto*
1992 - Fix security bug on NetBSD that could allow someone to force
1993 uninitialized RAM to be sent to a server's DNS resolver. This
1994 only affects NetBSD and other platforms that do not bounds-check
1996 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
1997 methods: these are known to be buggy.
1998 - If we're a directory mirror and we ask for "all" network status
1999 documents, we would discard status documents from authorities
2003 Changes in version 0.1.1.23 - 2006-07-30
2005 - Fast Tor servers, especially exit nodes, were triggering asserts
2006 due to a bug in handling the list of pending DNS resolves. Some
2007 bugs still remain here; we're hunting them.
2008 - Entry guards could crash clients by sending unexpected input.
2009 - More fixes on reachability testing: if you find yourself reachable,
2010 then don't ever make any client requests (so you stop predicting
2011 circuits), then hup or have your clock jump, then later your IP
2012 changes, you won't think circuits are working, so you won't try to
2013 test reachability, so you won't publish.
2016 - Avoid a crash if the controller does a resetconf firewallports
2017 and then a setconf fascistfirewall=1.
2018 - Avoid an integer underflow when the dir authority decides whether
2019 a router is stable: we might wrongly label it stable, and compute
2020 a slightly wrong median stability, when a descriptor is published
2022 - Fix a place where we might trigger an assert if we can't build our
2023 own server descriptor yet.
2026 Changes in version 0.1.1.22 - 2006-07-05
2028 - Fix a big bug that was causing servers to not find themselves
2029 reachable if they changed IP addresses. Since only 0.1.1.22+
2030 servers can do reachability testing correctly, now we automatically
2031 make sure to test via one of these.
2032 - Fix to allow clients and mirrors to learn directory info from
2033 descriptor downloads that get cut off partway through.
2034 - Directory authorities had a bug in deciding if a newly published
2035 descriptor was novel enough to make everybody want a copy -- a few
2036 servers seem to be publishing new descriptors many times a minute.
2038 - Fix a rare bug that was causing some servers to complain about
2039 "closing wedged cpuworkers" and skip some circuit create requests.
2040 - Make the Exit flag in directory status documents actually work.
2043 Changes in version 0.1.1.21 - 2006-06-10
2044 o Crash and assert fixes from 0.1.1.20:
2045 - Fix a rare crash on Tor servers that have enabled hibernation.
2046 - Fix a seg fault on startup for Tor networks that use only one
2047 directory authority.
2048 - Fix an assert from a race condition that occurs on Tor servers
2049 while exiting, where various threads are trying to log that they're
2050 exiting, and delete the logs, at the same time.
2051 - Make our unit tests pass again on certain obscure platforms.
2054 - Add support for building SUSE RPM packages.
2055 - Speed up initial bootstrapping for clients: if we are making our
2056 first ever connection to any entry guard, then don't mark it down
2058 - When only one Tor server in the network is labelled as a guard,
2059 and we've already picked him, we would cycle endlessly picking him
2060 again, being unhappy about it, etc. Now we specifically exclude
2061 current guards when picking a new guard.
2062 - Servers send create cells more reliably after the TLS connection
2063 is established: we were sometimes forgetting to send half of them
2064 when we had more than one pending.
2065 - If we get a create cell that asks us to extend somewhere, but the
2066 Tor server there doesn't match the expected digest, we now send
2067 a destroy cell back, rather than silently doing nothing.
2068 - Make options->RedirectExit work again.
2069 - Make cookie authentication for the controller work again.
2070 - Stop being picky about unusual characters in the arguments to
2071 mapaddress. It's none of our business.
2072 - Add a new config option "TestVia" that lets you specify preferred
2073 middle hops to use for test circuits. Perhaps this will let me
2074 debug the reachability problems better.
2076 o Log / documentation fixes:
2077 - If we're a server and some peer has a broken TLS certificate, don't
2078 log about it unless ProtocolWarnings is set, i.e., we want to hear
2079 about protocol violations by others.
2080 - Fix spelling of VirtualAddrNetwork in man page.
2081 - Add a better explanation at the top of the autogenerated torrc file
2082 about what happened to our old torrc.
2085 Changes in version 0.1.1.20 - 2006-05-23
2086 o Crash and assert fixes from 0.1.0.17:
2087 - Fix assert bug in close_logs() on exit: when we close and delete
2088 logs, remove them all from the global "logfiles" list.
2089 - Fix an assert error when we're out of space in the connection_list
2090 and we try to post a hidden service descriptor (reported by Peter
2092 - Fix a rare assert error when we've tried all intro points for
2093 a hidden service and we try fetching the service descriptor again:
2094 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed".
2095 - Setconf SocksListenAddress kills Tor if it fails to bind. Now back
2096 out and refuse the setconf if it would fail.
2097 - If you specify a relative torrc path and you set RunAsDaemon in
2098 your torrc, then it chdir()'s to the new directory. If you then
2099 HUP, it tries to load the new torrc location, fails, and exits.
2100 The fix: no longer allow a relative path to torrc when using -f.
2101 - Check for integer overflows in more places, when adding elements
2102 to smartlists. This could possibly prevent a buffer overflow
2103 on malicious huge inputs.
2105 o Security fixes, major:
2106 - When we're printing strings from the network, don't try to print
2107 non-printable characters. Now we're safer against shell escape
2108 sequence exploits, and also against attacks to fool users into
2109 misreading their logs.
2110 - Implement entry guards: automatically choose a handful of entry
2111 nodes and stick with them for all circuits. Only pick new guards
2112 when the ones you have are unsuitable, and if the old guards
2113 become suitable again, switch back. This will increase security
2114 dramatically against certain end-point attacks. The EntryNodes
2115 config option now provides some hints about which entry guards you
2116 want to use most; and StrictEntryNodes means to only use those.
2117 Fixes CVE-2006-0414.
2118 - Implement exit enclaves: if we know an IP address for the
2119 destination, and there's a running Tor server at that address
2120 which allows exit to the destination, then extend the circuit to
2121 that exit first. This provides end-to-end encryption and end-to-end
2122 authentication. Also, if the user wants a .exit address or enclave,
2123 use 4 hops rather than 3, and cannibalize a general circ for it
2125 - Obey our firewall options more faithfully:
2126 . If we can't get to a dirserver directly, try going via Tor.
2127 . Don't ever try to connect (as a client) to a place our
2128 firewall options forbid.
2129 . If we specify a proxy and also firewall options, obey the
2130 firewall options even when we're using the proxy: some proxies
2131 can only proxy to certain destinations.
2132 - Make clients regenerate their keys when their IP address changes.
2133 - For the OS X package's modified privoxy config file, comment
2134 out the "logfile" line so we don't log everything passed
2136 - Our TLS handshakes were generating a single public/private
2137 keypair for the TLS context, rather than making a new one for
2138 each new connection. Oops. (But we were still rotating them
2139 periodically, so it's not so bad.)
2140 - When we were cannibalizing a circuit with a particular exit
2141 node in mind, we weren't checking to see if that exit node was
2142 already present earlier in the circuit. Now we are.
2143 - Require server descriptors to list IPv4 addresses -- hostnames
2144 are no longer allowed. This also fixes potential vulnerabilities
2145 to servers providing hostnames as their address and then
2146 preferentially resolving them so they can partition users.
2147 - Our logic to decide if the OR we connected to was the right guy
2148 was brittle and maybe open to a mitm for invalid routers.
2150 o Security fixes, minor:
2151 - Adjust tor-spec.txt to parameterize cell and key lengths. Now
2152 Ian Goldberg can prove things about our handshake protocol more
2154 - Make directory authorities generate a separate "guard" flag to
2155 mean "would make a good entry guard". Clients now honor the
2156 is_guard flag rather than looking at is_fast or is_stable.
2157 - Try to list MyFamily elements by key, not by nickname, and warn
2158 if we've not heard of a server.
2159 - Start using RAND_bytes rather than RAND_pseudo_bytes from
2160 OpenSSL. Also, reseed our entropy every hour, not just at
2161 startup. And add entropy in 512-bit chunks, not 160-bit chunks.
2162 - Refuse server descriptors where the fingerprint line doesn't match
2163 the included identity key. Tor doesn't care, but other apps (and
2164 humans) might actually be trusting the fingerprint line.
2165 - We used to kill the circuit when we receive a relay command we
2166 don't recognize. Now we just drop that cell.
2167 - Fix a bug found by Lasse Overlier: when we were making internal
2168 circuits (intended to be cannibalized later for rendezvous and
2169 introduction circuits), we were picking them so that they had
2170 useful exit nodes. There was no need for this, and it actually
2171 aids some statistical attacks.
2172 - Start treating internal circuits and exit circuits separately.
2173 It's important to keep them separate because internal circuits
2174 have their last hops picked like middle hops, rather than like
2175 exit hops. So exiting on them will break the user's expectations.
2176 - Fix a possible way to DoS dirservers.
2177 - When the client asked for a rendezvous port that the hidden
2178 service didn't want to provide, we were sending an IP address
2179 back along with the end cell. Fortunately, it was zero. But stop
2182 o Packaging improvements:
2183 - Implement --with-libevent-dir option to ./configure. Improve
2184 search techniques to find libevent, and use those for openssl too.
2185 - Fix a couple of bugs in OpenSSL detection. Deal better when
2186 there are multiple SSLs installed with different versions.
2187 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
2188 - On non-gcc compilers (e.g. Solaris's cc), use "-g -O" instead of
2190 - Make unit tests (and other invocations that aren't the real Tor)
2191 run without launching listeners, creating subdirectories, and so on.
2192 - The OS X installer was adding a symlink for tor_resolve but
2193 the binary was called tor-resolve (reported by Thomas Hardly).
2194 - Now we can target arch and OS in rpm builds (contributed by
2195 Phobos). Also make the resulting dist-rpm filename match the
2197 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
2198 if you log to syslog and want something other than LOG_DAEMON.
2199 - Fix the torify (tsocks) config file to not use Tor for localhost
2201 - Start shipping socks-extensions.txt, tor-doc-unix.html,
2202 tor-doc-server.html, and stylesheet.css in the tarball.
2203 - Stop shipping tor-doc.html, INSTALL, and README in the tarball.
2204 They are useless now.
2205 - Add Peter Palfrader's contributed check-tor script. It lets you
2206 easily check whether a given server (referenced by nickname)
2207 is reachable by you.
2208 - Add BSD-style contributed startup script "rc.subr" from Peter
2211 o Directory improvements -- new directory protocol:
2212 - See tor/doc/dir-spec.txt for all the juicy details. Key points:
2213 - Authorities and caches publish individual descriptors (by
2214 digest, by fingerprint, by "all", and by "tell me yours").
2215 - Clients don't download or use the old directory anymore. Now they
2216 download network-statuses from the directory authorities, and
2217 fetch individual server descriptors as needed from mirrors.
2218 - Clients don't download descriptors of non-running servers.
2219 - Download descriptors by digest, not by fingerprint. Caches try to
2220 download all listed digests from authorities; clients try to
2221 download "best" digests from caches. This avoids partitioning
2222 and isolating attacks better.
2223 - Only upload a new server descriptor when options change, 18
2224 hours have passed, uptime is reset, or bandwidth changes a lot.
2225 - Directory authorities silently throw away new descriptors that
2226 haven't changed much if the timestamps are similar. We do this to
2227 tolerate older Tor servers that upload a new descriptor every 15
2228 minutes. (It seemed like a good idea at the time.)
2229 - Clients choose directory servers from the network status lists,
2230 not from their internal list of router descriptors. Now they can
2231 go to caches directly rather than needing to go to authorities
2232 to bootstrap the first set of descriptors.
2233 - When picking a random directory, prefer non-authorities if any
2235 - Add a new flag to network-status indicating whether the server
2236 can answer v2 directory requests too.
2237 - Directory mirrors now cache up to 16 unrecognized network-status
2238 docs, so new directory authorities will be cached too.
2239 - Stop parsing, storing, or using running-routers output (but
2240 mirrors still cache and serve it).
2241 - Clients consider a threshold of "versioning" directory authorities
2242 before deciding whether to warn the user that he's obsolete.
2243 - Authorities publish separate sorted lists of recommended versions
2244 for clients and for servers.
2245 - Change DirServers config line to note which dirs are v1 authorities.
2246 - Put nicknames on the DirServer line, so we can refer to them
2247 without requiring all our users to memorize their IP addresses.
2248 - Remove option when getting directory cache to see whether they
2249 support running-routers; they all do now. Replace it with one
2250 to see whether caches support v2 stuff.
2251 - Stop listing down or invalid nodes in the v1 directory. This
2252 reduces its bulk by about 1/3, and reduces load on mirrors.
2253 - Mirrors no longer cache the v1 directory as often.
2254 - If we as a directory mirror don't know of any v1 directory
2255 authorities, then don't try to cache any v1 directories.
2257 o Other directory improvements:
2258 - Add lefkada.eecs.harvard.edu and tor.dizum.com as fourth and
2259 fifth authoritative directory servers.
2260 - Directory authorities no longer require an open connection from
2261 a server to consider him "reachable". We need this change because
2262 when we add new directory authorities, old servers won't know not
2264 - Dir authorities now do their own external reachability testing
2265 of each server, and only list as running the ones they found to
2266 be reachable. We also send back warnings to the server's logs if
2267 it uploads a descriptor that we already believe is unreachable.
2268 - Spread the directory authorities' reachability testing over the
2269 entire testing interval, so we don't try to do 500 TLS's at once
2271 - Make the "stable" router flag in network-status be the median of
2272 the uptimes of running valid servers, and make clients pay
2273 attention to the network-status flags. Thus the cutoff adapts
2274 to the stability of the network as a whole, making IRC, IM, etc
2275 connections more reliable.
2276 - Make the v2 dir's "Fast" flag based on relative capacity, just
2277 like "Stable" is based on median uptime. Name everything in the
2278 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
2279 - Retry directory requests if we fail to get an answer we like
2280 from a given dirserver (we were retrying before, but only if
2281 we fail to connect).
2282 - Return a robots.txt on our dirport to discourage google indexing.
2284 o Controller protocol improvements:
2285 - Revised controller protocol (version 1) that uses ascii rather
2286 than binary: tor/doc/control-spec.txt. Add supporting libraries
2287 in python and java and c# so you can use the controller from your
2288 applications without caring how our protocol works.
2289 - Allow the DEBUG controller event to work again. Mark certain log
2290 entries as "don't tell this to controllers", so we avoid cycles.
2291 - New controller function "getinfo accounting", to ask how
2292 many bytes we've used in this time period.
2293 - Add a "resetconf" command so you can set config options like
2294 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
2295 a config option in the torrc with no value, then it clears it
2296 entirely (rather than setting it to its default).
2297 - Add a "getinfo config-file" to tell us where torrc is. Also
2298 expose guard nodes, config options/names.
2299 - Add a "quit" command (when when using the controller manually).
2300 - Add a new signal "newnym" to "change pseudonyms" -- that is, to
2301 stop using any currently-dirty circuits for new streams, so we
2302 don't link new actions to old actions. This also occurs on HUP
2304 - If we would close a stream early (e.g. it asks for a .exit that
2305 we know would refuse it) but the LeaveStreamsUnattached config
2306 option is set by the controller, then don't close it.
2307 - Add a new controller event type "authdir_newdescs" that allows
2308 controllers to get all server descriptors that were uploaded to
2309 a router in its role as directory authority.
2310 - New controller option "getinfo desc/all-recent" to fetch the
2311 latest server descriptor for every router that Tor knows about.
2312 - Fix the controller's "attachstream 0" command to treat conn like
2313 it just connected, doing address remapping, handling .exit and
2314 .onion idioms, and so on. Now we're more uniform in making sure
2315 that the controller hears about new and closing connections.
2316 - Permit transitioning from ORPort==0 to ORPort!=0, and back, from
2317 the controller. Also, rotate dns and cpu workers if the controller
2318 changes options that will affect them; and initialize the dns
2319 worker cache tree whether or not we start out as a server.
2320 - Add a new circuit purpose 'controller' to let the controller ask
2321 for a circuit that Tor won't try to use. Extend the "extendcircuit"
2322 controller command to let you specify the purpose if you're starting
2323 a new circuit. Add a new "setcircuitpurpose" controller command to
2324 let you change a circuit's purpose after it's been created.
2325 - Let the controller ask for "getinfo dir/server/foo" so it can ask
2326 directly rather than connecting to the dir port. "getinfo
2327 dir/status/foo" also works, but currently only if your DirPort
2329 - Let the controller tell us about certain router descriptors
2330 that it doesn't want Tor to use in circuits. Implement
2331 "setrouterpurpose" and modify "+postdescriptor" to do this.
2332 - If the controller's *setconf commands fail, collect an error
2333 message in a string and hand it back to the controller -- don't
2334 just tell them to go read their logs.
2336 o Scalability, resource management, and performance:
2337 - Fix a major load balance bug: we were round-robin reading in 16 KB
2338 chunks, and servers with bandwidthrate of 20 KB, while downloading
2339 a 600 KB directory, would starve their other connections. Now we
2340 try to be a bit more fair.
2341 - Be more conservative about whether to advertise our DirPort.
2342 The main change is to not advertise if we're running at capacity
2343 and either a) we could hibernate ever or b) our capacity is low
2344 and we're using a default DirPort.
2345 - We weren't cannibalizing circuits correctly for
2346 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
2347 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
2348 build those from scratch. This should make hidden services faster.
2349 - Predict required circuits better, with an eye toward making hidden
2350 services faster on the service end.
2351 - Compress exit policies even more: look for duplicate lines and
2353 - Generate 18.0.0.0/8 address policy format in descs when we can;
2354 warn when the mask is not reducible to a bit-prefix.
2355 - There used to be two ways to specify your listening ports in a
2356 server descriptor: on the "router" line and with a separate "ports"
2357 line. Remove support for the "ports" line.
2358 - Reduce memory requirements in our structs by changing the order
2359 of fields. Replace balanced trees with hash tables. Inline
2360 bottleneck smartlist functions. Add a "Map from digest to void*"
2361 abstraction so we can do less hex encoding/decoding, and use it
2362 in router_get_by_digest(). Many other CPU and memory improvements.
2363 - Allow tor_gzip_uncompress to extract as much as possible from
2364 truncated compressed data. Try to extract as many
2365 descriptors as possible from truncated http responses (when
2366 purpose is DIR_PURPOSE_FETCH_ROUTERDESC).
2367 - Make circ->onionskin a pointer, not a static array. moria2 was using
2368 125000 circuit_t's after it had been up for a few weeks, which
2369 translates to 20+ megs of wasted space.
2370 - The private half of our EDH handshake keys are now chosen out
2371 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
2372 - Stop doing the complex voodoo overkill checking for insecure
2373 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
2374 - Do round-robin writes for TLS of at most 16 kB per write. This
2375 might be more fair on loaded Tor servers.
2376 - Do not use unaligned memory access on alpha, mips, or mipsel.
2377 It *works*, but is very slow, so we treat them as if it doesn't.
2379 o Other bugfixes and improvements:
2380 - Start storing useful information to $DATADIR/state, so we can
2381 remember things across invocations of Tor. Retain unrecognized
2382 lines so we can be forward-compatible, and write a TorVersion line
2383 so we can be backward-compatible.
2384 - If ORPort is set, Address is not explicitly set, and our hostname
2385 resolves to a private IP address, try to use an interface address
2386 if it has a public address. Now Windows machines that think of
2387 themselves as localhost can guess their address.
2388 - Regenerate our local descriptor if it's dirty and we try to use
2389 it locally (e.g. if it changes during reachability detection).
2390 This was causing some Tor servers to keep publishing the same
2391 initial descriptor forever.
2392 - Tor servers with dynamic IP addresses were needing to wait 18
2393 hours before they could start doing reachability testing using
2394 the new IP address and ports. This is because they were using
2395 the internal descriptor to learn what to test, yet they were only
2396 rebuilding the descriptor once they decided they were reachable.
2397 - It turns out we couldn't bootstrap a network since we added
2398 reachability detection in 0.1.0.1-rc. Good thing the Tor network
2399 has never gone down. Add an AssumeReachable config option to let
2400 servers and authorities bootstrap. When we're trying to build a
2401 high-uptime or high-bandwidth circuit but there aren't enough
2402 suitable servers, try being less picky rather than simply failing.
2403 - Newly bootstrapped Tor networks couldn't establish hidden service
2404 circuits until they had nodes with high uptime. Be more tolerant.
2405 - Really busy servers were keeping enough circuits open on stable
2406 connections that they were wrapping around the circuit_id
2407 space. (It's only two bytes.) This exposed a bug where we would
2408 feel free to reuse a circuit_id even if it still exists but has
2409 been marked for close. Try to fix this bug. Some bug remains.
2410 - When we fail to bind or listen on an incoming or outgoing
2411 socket, we now close it before refusing, rather than just
2412 leaking it. (Thanks to Peter Palfrader for finding.)
2413 - Fix a file descriptor leak in start_daemon().
2414 - On Windows, you can't always reopen a port right after you've
2415 closed it. So change retry_listeners() to only close and re-open
2416 ports that have changed.
2417 - Workaround a problem with some http proxies that refuse GET
2418 requests that specify "Content-Length: 0". Reported by Adrian.
2419 - Recover better from TCP connections to Tor servers that are
2420 broken but don't tell you (it happens!); and rotate TLS
2421 connections once a week.
2422 - Fix a scary-looking but apparently harmless bug where circuits
2423 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
2424 servers, and never switch to state CIRCUIT_STATE_OPEN.
2425 - Check for even more Windows version flags when writing the platform
2426 string in server descriptors, and note any we don't recognize.
2427 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
2428 get a better idea of why their circuits failed. Not used yet.
2429 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
2430 We don't use them yet, but maybe one day our DNS resolver will be
2431 able to discover them.
2432 - Let people type "tor --install" as well as "tor -install" when they
2433 want to make it an NT service.
2434 - Looks like we were never delivering deflated (i.e. compressed)
2435 running-routers lists, even when asked. Oops.
2436 - We were leaking some memory every time the client changed IPs.
2437 - Clean up more of the OpenSSL memory when exiting, so we can detect
2438 memory leaks better.
2439 - Never call free() on tor_malloc()d memory. This will help us
2440 use dmalloc to detect memory leaks.
2441 - Some Tor servers process billions of cells per day. These
2442 statistics are now uint64_t's.
2443 - Check [X-]Forwarded-For headers in HTTP requests when generating
2444 log messages. This lets people run dirservers (and caches) behind
2445 Apache but still know which IP addresses are causing warnings.
2446 - Fix minor integer overflow in calculating when we expect to use up
2447 our bandwidth allocation before hibernating.
2448 - Lower the minimum required number of file descriptors to 1000,
2449 so we can have some overhead for Valgrind on Linux, where the
2450 default ulimit -n is 1024.
2451 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
2452 and its existence is confusing some users.
2454 o Config option fixes:
2455 - Add a new config option ExitPolicyRejectPrivate which defaults
2456 to on. Now all exit policies will begin with rejecting private
2457 addresses, unless the server operator explicitly turns it off.
2458 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB.
2459 - Add new ReachableORAddresses and ReachableDirAddresses options
2460 that understand address policies. FascistFirewall is now a synonym
2461 for "ReachableORAddresses *:443", "ReachableDirAddresses *:80".
2462 - Start calling it FooListenAddress rather than FooBindAddress,
2463 since few of our users know what it means to bind an address
2465 - If the user gave Tor an odd number of command-line arguments,
2466 we were silently ignoring the last one. Now we complain and fail.
2467 This wins the oldest-bug prize -- this bug has been present since
2468 November 2002, as released in Tor 0.0.0.
2469 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
2470 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
2471 it would silently ignore the 6668.
2472 - If we get a linelist or linelist_s config option from the torrc,
2473 e.g. ExitPolicy, and it has no value, warn and skip rather than
2474 silently resetting it to its default.
2475 - Setconf was appending items to linelists, not clearing them.
2476 - Add MyFamily to torrc.sample in the server section, so operators
2477 will be more likely to learn that it exists.
2478 - Make ContactInfo mandatory for authoritative directory servers.
2479 - MaxConn has been obsolete for a while now. Document the ConnLimit
2480 config option, which is a *minimum* number of file descriptors
2481 that must be available else Tor refuses to start.
2482 - Get rid of IgnoreVersion undocumented config option, and make us
2483 only warn, never exit, when we're running an obsolete version.
2484 - Make MonthlyAccountingStart config option truly obsolete now.
2485 - Correct the man page entry on TrackHostExitsExpire.
2486 - Let directory authorities start even if they don't specify an
2487 Address config option.
2488 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
2489 reflect the updated flags in our v2 dir protocol.
2491 o Config option features:
2492 - Add a new config option FastFirstHopPK (on by default) so clients
2493 do a trivial crypto handshake for their first hop, since TLS has
2494 already taken care of confidentiality and authentication.
2495 - Let the user set ControlListenAddress in the torrc. This can be
2496 dangerous, but there are some cases (like a secured LAN) where it
2498 - New config options to help controllers: FetchServerDescriptors
2499 and FetchHidServDescriptors for whether to fetch server
2500 info and hidserv info or let the controller do it, and
2501 PublishServerDescriptor and PublishHidServDescriptors.
2502 - Also let the controller set the __AllDirActionsPrivate config
2503 option if you want all directory fetches/publishes to happen via
2504 Tor (it assumes your controller bootstraps your circuits).
2505 - Add "HardwareAccel" config option: support for crypto hardware
2506 accelerators via OpenSSL. Off by default, until we find somebody
2507 smart who can test it for us. (It appears to produce seg faults
2508 in at least some cases.)
2509 - New config option "AuthDirRejectUnlisted" for directory authorities
2510 as a panic button: if we get flooded with unusable servers we can
2511 revert to only listing servers in the approved-routers file.
2512 - Directory authorities can now reject/invalidate by key and IP,
2513 with the config options "AuthDirInvalid" and "AuthDirReject", or
2514 by marking a fingerprint as "!reject" or "!invalid" (as its
2515 nickname) in the approved-routers file. This is useful since
2516 currently we automatically list servers as running and usable
2517 even if we know they're jerks.
2518 - Add a new config option TestSocks so people can see whether their
2519 applications are using socks4, socks4a, socks5-with-ip, or
2520 socks5-with-fqdn. This way they don't have to keep mucking
2521 with tcpdump and wondering if something got cached somewhere.
2522 - Add "private:*" as an alias in configuration for policies. Now
2523 you can simplify your exit policy rather than needing to list
2524 every single internal or nonroutable network space.
2525 - Accept "private:*" in routerdesc exit policies; not generated yet
2526 because older Tors do not understand it.
2527 - Add configuration option "V1AuthoritativeDirectory 1" which
2528 moria1, moria2, and tor26 have set.
2529 - Implement an option, VirtualAddrMask, to set which addresses
2530 get handed out in response to mapaddress requests. This works
2531 around a bug in tsocks where 127.0.0.0/8 is never socksified.
2532 - Add a new config option FetchUselessDescriptors, off by default,
2533 for when you plan to run "exitlist" on your client and you want
2534 to know about even the non-running descriptors.
2535 - SocksTimeout: How long do we let a socks connection wait
2536 unattached before we fail it?
2537 - CircuitBuildTimeout: Cull non-open circuits that were born
2538 at least this many seconds ago.
2539 - CircuitIdleTimeout: Cull open clean circuits that were born
2540 at least this many seconds ago.
2541 - New config option SafeSocks to reject all application connections
2542 using unsafe socks protocols. Defaults to off.
2544 o Improved and clearer log messages:
2545 - Reduce clutter in server logs. We're going to try to make
2546 them actually usable now. New config option ProtocolWarnings that
2547 lets you hear about how _other Tors_ are breaking the protocol. Off
2549 - Divide log messages into logging domains. Once we put some sort
2550 of interface on this, it will let people looking at more verbose
2551 log levels specify the topics they want to hear more about.
2552 - Log server fingerprint on startup, so new server operators don't
2553 have to go hunting around their filesystem for it.
2554 - Provide dire warnings to any users who set DirServer manually;
2555 move it out of torrc.sample and into torrc.complete.
2556 - Make the log message less scary when all the dirservers are
2557 temporarily unreachable.
2558 - When tor_socketpair() fails in Windows, give a reasonable
2559 Windows-style errno back.
2560 - Improve tor_gettimeofday() granularity on windows.
2561 - We were printing the number of idle dns workers incorrectly when
2563 - Handle duplicate lines in approved-routers files without warning.
2564 - We were whining about using socks4 or socks5-with-local-lookup
2565 even when it's an IP address in the "virtual" range we designed
2566 exactly for this case.
2567 - Check for named servers when looking them up by nickname;
2568 warn when we're calling a non-named server by its nickname;
2569 don't warn twice about the same name.
2570 - Downgrade the dirserver log messages when whining about
2572 - Correct "your server is reachable" log entries to indicate that
2573 it was self-testing that told us so.
2574 - If we're trying to be a Tor server and running Windows 95/98/ME
2575 as a server, explain that we'll likely crash.
2576 - Provide a more useful warn message when our onion queue gets full:
2577 the CPU is too slow or the exit policy is too liberal.
2578 - Don't warn when we receive a 503 from a dirserver/cache -- this
2579 will pave the way for them being able to refuse if they're busy.
2580 - When we fail to bind a listener, try to provide a more useful
2581 log message: e.g., "Is Tor already running?"
2582 - Only start testing reachability once we've established a
2583 circuit. This will make startup on dir authorities less noisy.
2584 - Don't try to upload hidden service descriptors until we have
2585 established a circuit.
2586 - Tor didn't warn when it failed to open a log file.
2587 - Warn when listening on a public address for socks. We suspect a
2588 lot of people are setting themselves up as open socks proxies,
2589 and they have no idea that jerks on the Internet are using them,
2590 since they simply proxy the traffic into the Tor network.
2591 - Give a useful message when people run Tor as the wrong user,
2592 rather than telling them to start chowning random directories.
2593 - Fix a harmless bug that was causing Tor servers to log
2594 "Got an end because of misc error, but we're not an AP. Closing."
2595 - Fix wrong log message when you add a "HiddenServiceNodes" config
2596 line without any HiddenServiceDir line (reported by Chris Thomas).
2597 - Directory authorities now stop whining so loudly about bad
2598 descriptors that they fetch from other dirservers. So when there's
2599 a log complaint, it's for sure from a freshly uploaded descriptor.
2600 - When logging via syslog, include the pid whenever we provide
2601 a log entry. Suggested by Todd Fries.
2602 - When we're shutting down and we do something like try to post a
2603 server descriptor or rendezvous descriptor, don't complain that
2604 we seem to be unreachable. Of course we are, we're shutting down.
2605 - Change log line for unreachability to explicitly suggest /etc/hosts
2606 as the culprit. Also make it clearer what IP address and ports we're
2607 testing for reachability.
2608 - Put quotes around user-supplied strings when logging so users are
2609 more likely to realize if they add bad characters (like quotes)
2611 - NT service patch from Matt Edman to improve error messages on Win32.
2614 Changes in version 0.1.0.17 - 2006-02-17
2615 o Crash bugfixes on 0.1.0.x:
2616 - When servers with a non-zero DirPort came out of hibernation,
2617 sometimes they would trigger an assert.
2619 o Other important bugfixes:
2620 - On platforms that don't have getrlimit (like Windows), we were
2621 artificially constraining ourselves to a max of 1024
2622 connections. Now just assume that we can handle as many as 15000
2623 connections. Hopefully this won't cause other problems.
2625 o Backported features:
2626 - When we're a server, a client asks for an old-style directory,
2627 and our write bucket is empty, don't give it to him. This way
2628 small servers can continue to serve the directory *sometimes*,
2629 without getting overloaded.
2630 - Whenever you get a 503 in response to a directory fetch, try
2631 once more. This will become important once servers start sending
2632 503's whenever they feel busy.
2633 - Fetch a new directory every 120 minutes, not every 40 minutes.
2634 Now that we have hundreds of thousands of users running the old
2635 directory algorithm, it's starting to hurt a lot.
2636 - Bump up the period for forcing a hidden service descriptor upload
2637 from 20 minutes to 1 hour.
2640 Changes in version 0.1.0.16 - 2006-01-02
2641 o Crash bugfixes on 0.1.0.x:
2642 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
2643 corrupting the heap, losing FDs, or crashing when we need to resize
2644 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
2645 - It turns out sparc64 platforms crash on unaligned memory access
2646 too -- so detect and avoid this.
2647 - Handle truncated compressed data correctly (by detecting it and
2649 - Fix possible-but-unlikely free(NULL) in control.c.
2650 - When we were closing connections, there was a rare case that
2651 stomped on memory, triggering seg faults and asserts.
2652 - Avoid potential infinite recursion when building a descriptor. (We
2653 don't know that it ever happened, but better to fix it anyway.)
2654 - We were neglecting to unlink marked circuits from soon-to-close OR
2655 connections, which caused some rare scribbling on freed memory.
2656 - Fix a memory stomping race bug when closing the joining point of two
2657 rendezvous circuits.
2658 - Fix an assert in time parsing found by Steven Murdoch.
2660 o Other bugfixes on 0.1.0.x:
2661 - When we're doing reachability testing, provide more useful log
2662 messages so the operator knows what to expect.
2663 - Do not check whether DirPort is reachable when we are suppressing
2664 advertising it because of hibernation.
2665 - When building with -static or on Solaris, we sometimes needed -ldl.
2666 - One of the dirservers (tor26) changed its IP address.
2667 - When we're deciding whether a stream has enough circuits around
2668 that can handle it, count the freshly dirty ones and not the ones
2669 that are so dirty they won't be able to handle it.
2670 - When we're expiring old circuits, we had a logic error that caused
2671 us to close new rendezvous circuits rather than old ones.
2672 - Give a more helpful log message when you try to change ORPort via
2673 the controller: you should upgrade Tor if you want that to work.
2674 - We were failing to parse Tor versions that start with "Tor ".
2675 - Tolerate faulty streams better: when a stream fails for reason
2676 exitpolicy, stop assuming that the router is lying about his exit
2677 policy. When a stream fails for reason misc, allow it to retry just
2678 as if it was resolvefailed. When a stream has failed three times,
2679 reset its failure count so we can try again and get all three tries.
2682 Changes in version 0.1.0.15 - 2005-09-23
2683 o Bugfixes on 0.1.0.x:
2684 - Reject ports 465 and 587 (spam targets) in default exit policy.
2685 - Don't crash when we don't have any spare file descriptors and we
2686 try to spawn a dns or cpu worker.
2687 - Get rid of IgnoreVersion undocumented config option, and make us
2688 only warn, never exit, when we're running an obsolete version.
2689 - Don't try to print a null string when your server finds itself to
2690 be unreachable and the Address config option is empty.
2691 - Make the numbers in read-history and write-history into uint64s,
2692 so they don't overflow and publish negatives in the descriptor.
2693 - Fix a minor memory leak in smartlist_string_remove().
2694 - We were only allowing ourselves to upload a server descriptor at
2695 most every 20 minutes, even if it changed earlier than that.
2696 - Clean up log entries that pointed to old URLs.
2699 Changes in version 0.1.0.14 - 2005-08-08
2700 o Bugfixes on 0.1.0.x:
2701 - Fix the other half of the bug with crypto handshakes
2703 - Fix an assert trigger if you send a 'signal term' via the
2704 controller when it's listening for 'event info' messages.
2707 Changes in version 0.1.0.13 - 2005-08-04
2708 o Bugfixes on 0.1.0.x:
2709 - Fix a critical bug in the security of our crypto handshakes.
2710 - Fix a size_t underflow in smartlist_join_strings2() that made
2711 it do bad things when you hand it an empty smartlist.
2712 - Fix Windows installer to ship Tor license (thanks to Aphex for
2713 pointing out this oversight) and put a link to the doc directory
2715 - Explicitly set no-unaligned-access for sparc: it turns out the
2716 new gcc's let you compile broken code, but that doesn't make it
2720 Changes in version 0.1.0.12 - 2005-07-18
2721 o New directory servers:
2722 - tor26 has changed IP address.
2724 o Bugfixes on 0.1.0.x:
2725 - Fix a possible double-free in tor_gzip_uncompress().
2726 - When --disable-threads is set, do not search for or link against
2728 - Don't trigger an assert if an authoritative directory server
2729 claims its dirport is 0.
2730 - Fix bug with removing Tor as an NT service: some people were
2731 getting "The service did not return an error." Thanks to Matt
2735 Changes in version 0.1.0.11 - 2005-06-30
2736 o Bugfixes on 0.1.0.x:
2737 - Fix major security bug: servers were disregarding their
2738 exit policies if clients behaved unexpectedly.
2739 - Make OS X init script check for missing argument, so we don't
2740 confuse users who invoke it incorrectly.
2741 - Fix a seg fault in "tor --hash-password foo".
2742 - The MAPADDRESS control command was broken.
2745 Changes in version 0.1.0.10 - 2005-06-14
2747 - Make NT services work and start on startup on Win32 (based on
2748 patch by Matt Edman). See the FAQ entry for details.
2749 - Make 'platform' string in descriptor more accurate for Win32
2750 servers, so it's not just "unknown platform".
2751 - REUSEADDR on normal platforms means you can rebind to the port
2752 right after somebody else has let it go. But REUSEADDR on Win32
2753 means you can bind to the port _even when somebody else already
2754 has it bound_! So, don't do that on Win32.
2755 - Clean up the log messages when starting on Win32 with no config
2757 - Allow seeding the RNG on Win32 even when you're not running as
2758 Administrator. If seeding the RNG on Win32 fails, quit.
2760 o Assert / crash bugs:
2761 - Refuse relay cells that claim to have a length larger than the
2762 maximum allowed. This prevents a potential attack that could read
2763 arbitrary memory (e.g. keys) from an exit server's process
2765 - If unofficial Tor clients connect and send weird TLS certs, our
2766 Tor server triggers an assert. Stop asserting, and start handling
2767 TLS errors better in other situations too.
2768 - Fix a race condition that can trigger an assert when we have a
2769 pending create cell and an OR connection attempt fails.
2772 - Use pthreads for worker processes rather than forking. This was
2773 forced because when we forked, we ended up wasting a lot of
2774 duplicate ram over time.
2775 - Also switch to foo_r versions of some library calls to allow
2776 reentry and threadsafeness.
2777 - Implement --disable-threads configure option. Disable threads on
2778 netbsd and openbsd by default, because they have no reentrant
2779 resolver functions (!), and on solaris since it has other
2781 - Fix possible bug on threading platforms (e.g. win32) which was
2782 leaking a file descriptor whenever a cpuworker or dnsworker died.
2783 - Fix a minor memory leak when somebody establishes an introduction
2784 point at your Tor server.
2785 - Fix possible memory leak in tor_lookup_hostname(). (Thanks to
2787 - Add ./configure --with-dmalloc option, to track memory leaks.
2788 - And try to free all memory on closing, so we can detect what
2791 o Protocol correctness:
2792 - When we've connected to an OR and handshaked but didn't like
2793 the result, we were closing the conn without sending destroy
2794 cells back for pending circuits. Now send those destroys.
2795 - Start sending 'truncated' cells back rather than destroy cells
2796 if the circuit closes in front of you. This means we won't have
2797 to abandon partially built circuits.
2798 - Handle changed router status correctly when dirserver reloads
2799 fingerprint file. We used to be dropping all unverified descriptors
2800 right then. The bug was hidden because we would immediately
2801 fetch a directory from another dirserver, which would include the
2802 descriptors we just dropped.
2803 - Revise tor-spec to add more/better stream end reasons.
2804 - Revise all calls to connection_edge_end to avoid sending 'misc',
2805 and to take errno into account where possible.
2806 - Client now retries when streams end early for 'hibernating' or
2807 'resource limit' reasons, rather than failing them.
2808 - Try to be more zealous about calling connection_edge_end when
2809 things go bad with edge conns in connection.c.
2811 o Robustness improvements:
2812 - Better handling for heterogeneous / unreliable nodes:
2813 - Annotate circuits with whether they aim to contain high uptime
2814 nodes and/or high capacity nodes. When building circuits, choose
2816 - This means that every single node in an intro rend circuit,
2817 not just the last one, will have a minimum uptime.
2818 - New config option LongLivedPorts to indicate application streams
2819 that will want high uptime circuits.
2820 - Servers reset uptime when a dir fetch entirely fails. This
2821 hopefully reflects stability of the server's network connectivity.
2822 - If somebody starts his tor server in Jan 2004 and then fixes his
2823 clock, don't make his published uptime be a year.
2824 - Reset published uptime when we wake up from hibernation.
2825 - Introduce a notion of 'internal' circs, which are chosen without
2826 regard to the exit policy of the last hop. Intro and rendezvous
2827 circs must be internal circs, to avoid leaking information. Resolve
2828 and connect streams can use internal circs if they want.
2829 - New circuit pooling algorithm: keep track of what destination ports
2830 we've used recently (start out assuming we'll want to use 80), and
2831 make sure to have enough circs around to satisfy these ports. Also
2832 make sure to have 2 internal circs around if we've required internal
2833 circs lately (and with high uptime if we've seen that lately too).
2834 - Turn addr_policy_compare from a tristate to a quadstate; this should
2835 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
2836 for google.com" problem.
2837 - When a client asks us for a dir mirror and we don't have one,
2838 launch an attempt to get a fresh one.
2839 - First cut at support for "create-fast" cells. Clients can use
2840 these when extending to their first hop, since the TLS already
2841 provides forward secrecy and authentication. Not enabled on
2844 o Reachability testing.
2845 - Your Tor server will automatically try to see if its ORPort and
2846 DirPort are reachable from the outside, and it won't upload its
2847 descriptor until it decides at least ORPort is reachable (when
2848 DirPort is not yet found reachable, publish it as zero).
2849 - When building testing circs for ORPort testing, use only
2850 high-bandwidth nodes, so fewer circuits fail.
2851 - Notice when our IP changes, and reset stats/uptime/reachability.
2852 - Authdirservers don't do ORPort reachability detection, since
2853 they're in clique mode, so it will be rare to find a server not
2854 already connected to them.
2855 - Authdirservers now automatically approve nodes running 0.1.0.2-rc
2859 - Now we allow two unverified servers with the same nickname
2860 but different keys. But if a nickname is verified, only that
2861 nickname+key are allowed.
2862 - If you're an authdirserver connecting to an address:port,
2863 and it's not the OR you were expecting, forget about that
2864 descriptor. If he *was* the one you were expecting, then forget
2865 about all other descriptors for that address:port.
2866 - Allow servers to publish descriptors from 12 hours in the future.
2867 Corollary: only whine about clock skew from the dirserver if
2868 he's a trusted dirserver (since now even verified servers could
2869 have quite wrong clocks).
2870 - Require servers that use the default dirservers to have public IP
2871 addresses. We have too many servers that are configured with private
2872 IPs and their admins never notice the log entries complaining that
2873 their descriptors are being rejected.
2875 o Efficiency improvements:
2876 - Use libevent. Now we can use faster async cores (like epoll, kpoll,
2877 and /dev/poll), and hopefully work better on Windows too.
2878 - Apple's OS X 10.4.0 ships with a broken kqueue API, and using
2879 kqueue on 10.3.9 causes kernel panics. Don't use kqueue on OS X.
2880 - Find libevent even if it's hiding in /usr/local/ and your
2881 CFLAGS and LDFLAGS don't tell you to look there.
2882 - Be able to link with libevent as a shared library (the default
2883 after 1.0d), even if it's hiding in /usr/local/lib and even
2884 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
2885 assuming you're running gcc. Otherwise fail and give a useful
2887 - Switch to a new buffer management algorithm, which tries to avoid
2888 reallocing and copying quite as much. In first tests it looks like
2889 it uses *more* memory on average, but less cpu.
2890 - Switch our internal buffers implementation to use a ring buffer,
2891 to hopefully improve performance for fast servers a lot.
2892 - Reenable the part of the code that tries to flush as soon as an
2893 OR outbuf has a full TLS record available. Perhaps this will make
2894 OR outbufs not grow as huge except in rare cases, thus saving lots
2895 of CPU time plus memory.
2896 - Improve performance for dirservers: stop re-parsing the whole
2897 directory every time you regenerate it.
2898 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
2899 it much faster to look up a circuit for each relay cell.
2900 - Remove most calls to assert_all_pending_dns_resolves_ok(),
2901 since they're eating our cpu on exit nodes.
2902 - Stop wasting time doing a case insensitive comparison for every
2903 dns name every time we do any lookup. Canonicalize the names to
2904 lowercase when you first see them.
2907 - Handle unavailable hidden services better. Handle slow or busy
2908 hidden services better.
2909 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
2910 circ as necessary, if there are any completed ones lying around
2911 when we try to launch one.
2912 - Make hidden services try to establish a rendezvous for 30 seconds
2913 after fetching the descriptor, rather than for n (where n=3)
2914 attempts to build a circuit.
2915 - Adjust maximum skew and age for rendezvous descriptors: let skew
2916 be 48 hours rather than 90 minutes.
2917 - Reject malformed .onion addresses rather then passing them on as
2918 normal web requests.
2921 - More Tor controller support. See
2922 http://tor.eff.org/doc/control-spec.txt for all the new features,
2923 including signals to emulate unix signals from any platform;
2924 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
2925 closestream; closecircuit; etc.
2926 - Encode hashed controller passwords in hex instead of base64,
2927 to make it easier to write controllers.
2928 - Revise control spec and implementation to allow all log messages to
2929 be sent to controller with their severities intact (suggested by
2930 Matt Edman). Disable debug-level logs while delivering a debug-level
2931 log to the controller, to prevent loop. Update TorControl to handle
2932 new log event types.
2934 o New config options/defaults:
2935 - Begin scrubbing sensitive strings from logs by default. Turn off
2936 the config option SafeLogging if you need to do debugging.
2937 - New exit policy: accept most low-numbered ports, rather than
2938 rejecting most low-numbered ports.
2939 - Put a note in the torrc about abuse potential with the default
2941 - Add support for CONNECTing through https proxies, with "HttpsProxy"
2943 - Add HttpProxyAuthenticator and HttpsProxyAuthenticator support
2944 based on patch from Adam Langley (basic auth only).
2945 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
2946 the fast servers that have been joining lately. (Clients are now
2947 willing to load balance over up to 2 MB of advertised bandwidth
2949 - New config option MaxAdvertisedBandwidth which lets you advertise
2950 a low bandwidthrate (to not attract as many circuits) while still
2951 allowing a higher bandwidthrate in reality.
2952 - Require BandwidthRate to be at least 20kB/s for servers.
2953 - Add a NoPublish config option, so you can be a server (e.g. for
2954 testing running Tor servers in other Tor networks) without
2955 publishing your descriptor to the primary dirservers.
2956 - Add a new AddressMap config directive to rewrite incoming socks
2957 addresses. This lets you, for example, declare an implicit
2958 required exit node for certain sites.
2959 - Add a new TrackHostExits config directive to trigger addressmaps
2960 for certain incoming socks addresses -- for sites that break when
2961 your exit keeps changing (based on patch from Mike Perry).
2962 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
2963 which describes how often we retry making new circuits if current
2964 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
2965 how long we're willing to make use of an already-dirty circuit.
2966 - Change compiled-in SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to
2967 a config option "ShutdownWaitLength" (when using kill -INT on
2969 - Fix an edge case in parsing config options: if they say "--"
2970 on the commandline, it's not a config option (thanks weasel).
2971 - New config option DirAllowPrivateAddresses for authdirservers.
2972 Now by default they refuse router descriptors that have non-IP or
2973 private-IP addresses.
2974 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
2975 smart" default value: low for servers and high for clients.
2976 - Some people were putting "Address " in their torrc, and they had
2977 a buggy resolver that resolved " " to 0.0.0.0. Oops.
2978 - If DataDir is ~/.tor, and that expands to /.tor, then default to
2979 LOCALSTATEDIR/tor instead.
2980 - Implement --verify-config command-line option to check if your torrc
2981 is valid without actually launching Tor.
2983 o Logging improvements:
2984 - When dirservers refuse a server descriptor, we now log its
2985 contactinfo, platform, and the poster's IP address.
2986 - Only warn once per nickname from add_nickname_list_to_smartlist()
2987 per failure, so an entrynode or exitnode choice that's down won't
2989 - When we're connecting to an OR and he's got a different nickname/key
2990 than we were expecting, only complain loudly if we're an OP or a
2991 dirserver. Complaining loudly to the OR admins just confuses them.
2992 - Whine at you if you're a server and you don't set your contactinfo.
2993 - Warn when exit policy implicitly allows local addresses.
2994 - Give a better warning when some other server advertises an
2995 ORPort that is actually an apache running ssl.
2996 - If we get an incredibly skewed timestamp from a dirserver mirror
2997 that isn't a verified OR, don't warn -- it's probably him that's
2999 - When a dirserver causes you to give a warn, mention which dirserver
3001 - Initialize libevent later in the startup process, so the logs are
3002 already established by the time we start logging libevent warns.
3003 - Use correct errno on win32 if libevent fails.
3004 - Check and warn about known-bad/slow libevent versions.
3005 - Stop warning about sigpipes in the logs. We're going to
3006 pretend that getting these occassionally is normal and fine.
3008 o New contrib scripts:
3009 - New experimental script tor/contrib/exitlist: a simple python
3010 script to parse directories and find Tor nodes that exit to listed
3012 - New experimental script tor/contrib/ExerciseServer.py (needs more
3013 work) that uses the controller interface to build circuits and
3014 fetch pages over them. This will help us bootstrap servers that
3015 have lots of capacity but haven't noticed it yet.
3016 - New experimental script tor/contrib/PathDemo.py (needs more work)
3017 that uses the controller interface to let you choose whole paths
3019 "<hostname>.<path,separated by dots>.<length of path>.path"
3020 - New contributed script "privoxy-tor-toggle" to toggle whether
3021 Privoxy uses Tor. Seems to be configured for Debian by default.
3022 - Have torctl.in/tor.sh.in check for location of su binary (needed
3026 - chdir() to your datadirectory at the *end* of the daemonize process,
3027 not the beginning. This was a problem because the first time you
3028 run tor, if your datadir isn't there, and you have runasdaemon set
3029 to 1, it will try to chdir to it before it tries to create it. Oops.
3030 - Fix several double-mark-for-close bugs, e.g. where we were finding
3031 a conn for a cell even if that conn is already marked for close.
3032 - Stop most cases of hanging up on a socks connection without sending
3034 - Fix a bug in the RPM package: set home directory for _tor to
3035 something more reasonable when first installing.
3036 - Stop putting nodename in the Platform string in server descriptors.
3037 It doesn't actually help, and it is confusing/upsetting some people.
3038 - When using preferred entry or exit nodes, ignore whether the
3039 circuit wants uptime or capacity. They asked for the nodes, they
3041 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
3042 artificially capped at 500kB.
3043 - Cache local dns resolves correctly even when they're .exit
3045 - If we're hibernating and we get a SIGINT, exit immediately.
3046 - tor-resolve requests were ignoring .exit if there was a working circuit
3047 they could use instead.
3048 - Pay more attention to the ClientOnly config option.
3049 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in certain
3050 installer screens; and don't put stuff into StartupItems unless
3051 the user asks you to.
3054 - Rewrite address "serifos.exit" to "externalIP.serifos.exit"
3055 rather than just rejecting it.
3056 - If our clock jumps forward by 100 seconds or more, assume something
3057 has gone wrong with our network and abandon all not-yet-used circs.
3058 - When an application is using socks5, give him the whole variety of
3059 potential socks5 responses (connect refused, host unreachable, etc),
3060 rather than just "success" or "failure".
3061 - A more sane version numbering system. See
3062 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
3063 - Change version parsing logic: a version is "obsolete" if it is not
3064 recommended and (1) there is a newer recommended version in the
3065 same series, or (2) there are no recommended versions in the same
3066 series, but there are some recommended versions in a newer series.
3067 A version is "new" if it is newer than any recommended version in
3069 - Report HTTP reasons to client when getting a response from directory
3070 servers -- so you can actually know what went wrong.
3071 - Reject odd-looking addresses at the client (e.g. addresses that
3072 contain a colon), rather than having the server drop them because
3074 - Stop publishing socksport in the directory, since it's not
3075 actually meant to be public. For compatibility, publish a 0 there
3077 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
3078 cookies to disk and doesn't log each web request to disk. (Thanks
3079 to Brett Carrington for pointing this out.)
3080 - Add OSX uninstall instructions. An actual uninstall script will
3082 - Add "opt hibernating 1" to server descriptor to make it clearer
3083 whether the server is hibernating.
3086 Changes in version 0.0.9.10 - 2005-06-16
3087 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
3088 - Refuse relay cells that claim to have a length larger than the
3089 maximum allowed. This prevents a potential attack that could read
3090 arbitrary memory (e.g. keys) from an exit server's process
3094 Changes in version 0.0.9.9 - 2005-04-23
3095 o Bugfixes on 0.0.9.x:
3096 - If unofficial Tor clients connect and send weird TLS certs, our
3097 Tor server triggers an assert. This release contains a minimal
3098 backport from the broader fix that we put into 0.1.0.4-rc.
3101 Changes in version 0.0.9.8 - 2005-04-07
3102 o Bugfixes on 0.0.9.x:
3103 - We have a bug that I haven't found yet. Sometimes, very rarely,
3104 cpuworkers get stuck in the 'busy' state, even though the cpuworker
3105 thinks of itself as idle. This meant that no new circuits ever got
3106 established. Here's a workaround to kill any cpuworker that's been
3107 busy for more than 100 seconds.
3110 Changes in version 0.0.9.7 - 2005-04-01
3111 o Bugfixes on 0.0.9.x:
3112 - Fix another race crash bug (thanks to Glenn Fink for reporting).
3113 - Compare identity to identity, not to nickname, when extending to
3114 a router not already in the directory. This was preventing us from
3115 extending to unknown routers. Oops.
3116 - Make sure to create OS X Tor user in <500 range, so we aren't
3117 creating actual system users.
3118 - Note where connection-that-hasn't-sent-end was marked, and fix
3119 a few really loud instances of this harmless bug (it's fixed more
3123 Changes in version 0.0.9.6 - 2005-03-24
3124 o Bugfixes on 0.0.9.x (crashes and asserts):
3125 - Add new end stream reasons to maintainance branch. Fix bug where
3126 reason (8) could trigger an assert. Prevent bug from recurring.
3127 - Apparently win32 stat wants paths to not end with a slash.
3128 - Fix assert triggers in assert_cpath_layer_ok(), where we were
3129 blowing away the circuit that conn->cpath_layer points to, then
3130 checking to see if the circ is well-formed. Backport check to make
3131 sure we dont use the cpath on a closed connection.
3132 - Prevent circuit_resume_edge_reading_helper() from trying to package
3133 inbufs for marked-for-close streams.
3134 - Don't crash on hup if your options->address has become unresolvable.
3135 - Some systems (like OS X) sometimes accept() a connection and tell
3136 you the remote host is 0.0.0.0:0. If this happens, due to some
3137 other mis-features, we get confused; so refuse the conn for now.
3139 o Bugfixes on 0.0.9.x (other):
3140 - Fix harmless but scary "Unrecognized content encoding" warn message.
3141 - Add new stream error reason: TORPROTOCOL reason means "you are not
3142 speaking a version of Tor I understand; say bye-bye to your stream."
3143 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
3144 into the future, now that we are more tolerant of skew. This
3145 resolves a bug where a Tor server would refuse to cache a directory
3146 because all the directories it gets are too far in the future;
3147 yet the Tor server never logs any complaints about clock skew.
3148 - Mac packaging magic: make man pages useable, and do not overwrite
3149 existing torrc files.
3150 - Make OS X log happily to /var/log/tor/tor.log
3153 Changes in version 0.0.9.5 - 2005-02-22
3154 o Bugfixes on 0.0.9.x:
3155 - Fix an assert race at exit nodes when resolve requests fail.
3156 - Stop picking unverified dir mirrors--it only leads to misery.
3157 - Patch from Matt Edman to make NT services work better. Service
3158 support is still not compiled into the executable by default.
3159 - Patch from Dmitri Bely so the Tor service runs better under
3160 the win32 SYSTEM account.
3161 - Make tor-resolve actually work (?) on Win32.
3162 - Fix a sign bug when getrlimit claims to have 4+ billion
3163 file descriptors available.
3164 - Stop refusing to start when bandwidthburst == bandwidthrate.
3165 - When create cells have been on the onion queue more than five
3166 seconds, just send back a destroy and take them off the list.
3169 Changes in version 0.0.9.4 - 2005-02-03
3170 o Bugfixes on 0.0.9:
3171 - Fix an assert bug that took down most of our servers: when
3172 a server claims to have 1 GB of bandwidthburst, don't
3174 - Don't crash as badly if we have spawned the max allowed number
3175 of dnsworkers, or we're out of file descriptors.
3176 - Block more file-sharing ports in the default exit policy.
3177 - MaxConn is now automatically set to the hard limit of max
3178 file descriptors we're allowed (ulimit -n), minus a few for
3180 - Give a clearer message when servers need to raise their
3181 ulimit -n when they start running out of file descriptors.
3182 - SGI Compatibility patches from Jan Schaumann.
3183 - Tolerate a corrupt cached directory better.
3184 - When a dirserver hasn't approved your server, list which one.
3185 - Go into soft hibernation after 95% of the bandwidth is used,
3186 not 99%. This is especially important for daily hibernators who
3187 have a small accounting max. Hopefully it will result in fewer
3188 cut connections when the hard hibernation starts.
3189 - Load-balance better when using servers that claim more than
3190 800kB/s of capacity.
3191 - Make NT services work (experimental, only used if compiled in).
3194 Changes in version 0.0.9.3 - 2005-01-21
3195 o Bugfixes on 0.0.9:
3196 - Backport the cpu use fixes from main branch, so busy servers won't
3197 need as much processor time.
3198 - Work better when we go offline and then come back, or when we
3199 run Tor at boot before the network is up. We do this by
3200 optimistically trying to fetch a new directory whenever an
3201 application request comes in and we think we're offline -- the
3202 human is hopefully a good measure of when the network is back.
3203 - Backport some minimal hidserv bugfixes: keep rend circuits open as
3204 long as you keep using them; actually publish hidserv descriptors
3205 shortly after they change, rather than waiting 20-40 minutes.
3206 - Enable Mac startup script by default.
3207 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
3208 - When you update AllowUnverifiedNodes or FirewallPorts via the
3209 controller's setconf feature, we were always appending, never
3211 - When you update HiddenServiceDir via setconf, it was screwing up
3212 the order of reading the lines, making it fail.
3213 - Do not rewrite a cached directory back to the cache; otherwise we
3214 will think it is recent and not fetch a newer one on startup.
3215 - Workaround for webservers that lie about Content-Encoding: Tor
3216 now tries to autodetect compressed directories and compression
3217 itself. This lets us Proxypass dir fetches through apache.
3220 Changes in version 0.0.9.2 - 2005-01-04
3221 o Bugfixes on 0.0.9 (crashes and asserts):
3222 - Fix an assert on startup when the disk is full and you're logging
3224 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
3225 style address, then we'd crash.
3226 - Fix an assert trigger when the running-routers string we get from
3227 a dirserver is broken.
3228 - Make worker threads start and run on win32. Now win32 servers
3230 - Bandaid (not actually fix, but now it doesn't crash) an assert
3231 where the dns worker dies mysteriously and the main Tor process
3232 doesn't remember anything about the address it was resolving.
3234 o Bugfixes on 0.0.9 (Win32):
3235 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
3236 name out of the warning/assert messages.
3237 - Fix a superficial "unhandled error on read" bug on win32.
3238 - The win32 installer no longer requires a click-through for our
3239 license, since our Free Software license grants rights but does not
3241 - Win32: When connecting to a dirserver fails, try another one
3242 immediately. (This was already working for non-win32 Tors.)
3243 - Stop trying to parse $HOME on win32 when hunting for default
3245 - Make tor-resolve.c work on win32 by calling network_init().
3247 o Bugfixes on 0.0.9 (other):
3248 - Make 0.0.9.x build on Solaris again.
3249 - Due to a fencepost error, we were blowing away the \n when reporting
3250 confvalue items in the controller. So asking for multiple config
3251 values at once couldn't work.
3252 - When listing circuits that are pending on an opening OR connection,
3253 if we're an OR we were listing circuits that *end* at us as
3254 being pending on every listener, dns/cpu worker, etc. Stop that.
3255 - Dirservers were failing to create 'running-routers' or 'directory'
3256 strings if we had more than some threshold of routers. Fix them so
3257 they can handle any number of routers.
3258 - Fix a superficial "Duplicate mark for close" bug.
3259 - Stop checking for clock skew for OR connections, even for servers.
3260 - Fix a fencepost error that was chopping off the last letter of any
3261 nickname that is the maximum allowed nickname length.
3262 - Update URLs in log messages so they point to the new website.
3263 - Fix a potential problem in mangling server private keys while
3264 writing to disk (not triggered yet, as far as we know).
3265 - Include the licenses for other free software we include in Tor,
3266 now that we're shipping binary distributions more regularly.
3269 Changes in version 0.0.9.1 - 2004-12-15
3270 o Bugfixes on 0.0.9:
3271 - Make hibernation actually work.
3272 - Make HashedControlPassword config option work.
3273 - When we're reporting event circuit status to a controller,
3274 don't use the stream status code.
3277 Changes in version 0.0.9 - 2004-12-12
3278 o Bugfixes on 0.0.8.1 (Crashes and asserts):
3279 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
3280 write() call will fail and we handle it there.
3281 - When we run out of disk space, or other log writing error, don't
3282 crash. Just stop logging to that log and continue.
3283 - Fix isspace() and friends so they still make Solaris happy
3284 but also so they don't trigger asserts on win32.
3285 - Fix assert failure on malformed socks4a requests.
3286 - Fix an assert bug where a hidden service provider would fail if
3287 the first hop of his rendezvous circuit was down.
3288 - Better handling of size_t vs int, so we're more robust on 64
3291 o Bugfixes on 0.0.8.1 (Win32):
3292 - Make windows sockets actually non-blocking (oops), and handle
3293 win32 socket errors better.
3294 - Fix parse_iso_time on platforms without strptime (eg win32).
3295 - win32: when being multithreaded, leave parent fdarray open.
3296 - Better handling of winsock includes on non-MSV win32 compilers.
3297 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
3299 - Make unit tests work on win32.
3301 o Bugfixes on 0.0.8.1 (Path selection and streams):
3302 - Calculate timeout for waiting for a connected cell from the time
3303 we sent the begin cell, not from the time the stream started. If
3304 it took a long time to establish the circuit, we would time out
3305 right after sending the begin cell.
3306 - Fix router_compare_addr_to_addr_policy: it was not treating a port
3307 of * as always matching, so we were picking reject *:* nodes as
3308 exit nodes too. Oops.
3309 - When read() failed on a stream, we would close it without sending
3310 back an end. So 'connection refused' would simply be ignored and
3311 the user would get no response.
3312 - Stop a sigpipe: when an 'end' cell races with eof from the app,
3313 we shouldn't hold-open-until-flush if the eof arrived first.
3314 - Let resolve conns retry/expire also, rather than sticking around
3316 - Fix more dns related bugs: send back resolve_failed and end cells
3317 more reliably when the resolve fails, rather than closing the
3318 circuit and then trying to send the cell. Also attach dummy resolve
3319 connections to a circuit *before* calling dns_resolve(), to fix
3320 a bug where cached answers would never be sent in RESOLVED cells.
3322 o Bugfixes on 0.0.8.1 (Circuits):
3323 - Finally fix a bug that's been plaguing us for a year:
3324 With high load, circuit package window was reaching 0. Whenever
3325 we got a circuit-level sendme, we were reading a lot on each
3326 socket, but only writing out a bit. So we would eventually reach
3327 eof. This would be noticed and acted on even when there were still
3328 bytes sitting in the inbuf.
3329 - Use identity comparison, not nickname comparison, to choose which
3330 half of circuit-ID-space each side gets to use. This is needed
3331 because sometimes we think of a router as a nickname, and sometimes
3332 as a hex ID, and we can't predict what the other side will do.
3334 o Bugfixes on 0.0.8.1 (Other):
3335 - Fix a whole slew of memory leaks.
3336 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
3337 - If we are using select, make sure we stay within FD_SETSIZE.
3338 - When poll() is interrupted, we shouldn't believe the revents values.
3339 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
3340 and smartlist_len, which are two major profiling offenders.
3341 - If do_hup fails, actually notice.
3342 - Flush the log file descriptor after we print "Tor opening log file",
3343 so we don't see those messages days later.
3344 - Hidden service operators now correctly handle version 1 style
3345 INTRODUCE1 cells (nobody generates them still, so not a critical
3347 - Handle more errnos from accept() without closing the listener.
3348 Some OpenBSD machines were closing their listeners because
3349 they ran out of file descriptors.
3350 - Some people had wrapped their tor client/server in a script
3351 that would restart it whenever it died. This did not play well
3352 with our "shut down if your version is obsolete" code. Now people
3353 don't fetch a new directory if their local cached version is
3355 - Make our autogen.sh work on ksh as well as bash.
3356 - Better torrc example lines for dirbindaddress and orbindaddress.
3357 - Improved bounds checking on parsed ints (e.g. config options and
3358 the ones we find in directories.)
3359 - Stop using separate defaults for no-config-file and
3360 empty-config-file. Now you have to explicitly turn off SocksPort,
3361 if you don't want it open.
3362 - We were starting to daemonize before we opened our logs, so if
3363 there were any problems opening logs, we would complain to stderr,
3364 which wouldn't work, and then mysteriously exit.
3365 - If a verified OR connects to us before he's uploaded his descriptor,
3366 or we verify him and hup but he still has the original TLS
3367 connection, then conn->nickname is still set like he's unverified.
3369 o Code security improvements, inspired by Ilja:
3370 - tor_snprintf wrapper over snprintf with consistent (though not C99)
3372 - Replace sprintf with tor_snprintf. (I think they were all safe, but
3374 - Replace strcpy/strncpy with strlcpy in more places.
3375 - Avoid strcat; use tor_snprintf or strlcat instead.
3377 o Features (circuits and streams):
3378 - New circuit building strategy: keep a list of ports that we've
3379 used in the past 6 hours, and always try to have 2 circuits open
3380 or on the way that will handle each such port. Seed us with port
3381 80 so web users won't complain that Tor is "slow to start up".
3382 - Make kill -USR1 dump more useful stats about circuits.
3383 - When warning about retrying or giving up, print the address, so
3384 the user knows which one it's talking about.
3385 - If you haven't used a clean circuit in an hour, throw it away,
3386 just to be on the safe side. (This means after 6 hours a totally
3387 unused Tor client will have no circuits open.)
3388 - Support "foo.nickname.exit" addresses, to let Alice request the
3389 address "foo" as viewed by exit node "nickname". Based on a patch
3391 - If your requested entry or exit node has advertised bandwidth 0,
3393 - Be more greedy about filling up relay cells -- we try reading again
3394 once we've processed the stuff we read, in case enough has arrived
3395 to fill the last cell completely.
3396 - Refuse application socks connections to port 0.
3397 - Use only 0.0.9pre1 and later servers for resolve cells.
3399 o Features (bandwidth):
3400 - Hibernation: New config option "AccountingMax" lets you
3401 set how many bytes per month (in each direction) you want to
3402 allow your server to consume. Rather than spreading those
3403 bytes out evenly over the month, we instead hibernate for some
3404 of the month and pop up at a deterministic time, work until
3405 the bytes are consumed, then hibernate again. Config option
3406 "MonthlyAccountingStart" lets you specify which day of the month
3407 your billing cycle starts on.
3408 - Implement weekly/monthly/daily accounting: now you specify your
3409 hibernation properties by
3410 AccountingMax N bytes|KB|MB|GB|TB
3411 AccountingStart day|week|month [day] HH:MM
3412 Defaults to "month 1 0:00".
3413 - Let bandwidth and interval config options be specified as 5 bytes,
3414 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
3416 o Features (directories):
3417 - New "router-status" line in directory, to better bind each verified
3418 nickname to its identity key.
3419 - Clients can ask dirservers for /dir.z to get a compressed version
3420 of the directory. Only works for servers running 0.0.9, of course.
3421 - Make clients cache directories and use them to seed their router
3422 lists at startup. This means clients have a datadir again.
3423 - Respond to content-encoding headers by trying to uncompress as
3425 - Clients and servers now fetch running-routers; cache
3426 running-routers; compress running-routers; serve compressed
3428 - Make moria2 advertise a dirport of 80, so people behind firewalls
3429 will be able to get a directory.
3430 - Http proxy support
3431 - Dirservers translate requests for http://%s:%d/x to /x
3432 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
3433 be routed through this host.
3434 - Clients ask for /tor/x rather than /x for new enough dirservers.
3435 This way we can one day coexist peacefully with apache.
3436 - Clients specify a "Host: %s%d" http header, to be compatible
3437 with more proxies, and so running squid on an exit node can work.
3438 - Protect dirservers from overzealous descriptor uploading -- wait
3439 10 seconds after directory gets dirty, before regenerating.
3441 o Features (packages and install):
3442 - Add NSI installer contributed by J Doe.
3443 - Apply NT service patch from Osamu Fujino. Still needs more work.
3444 - Commit VC6 and VC7 workspace/project files.
3445 - Commit a tor.spec for making RPM files, with help from jbash.
3446 - Add contrib/torctl.in contributed by Glenn Fink.
3447 - Make expand_filename handle ~ and ~username.
3448 - Use autoconf to enable largefile support where necessary. Use
3449 ftello where available, since ftell can fail at 2GB.
3450 - Ship src/win32/ in the tarball, so people can use it to build.
3451 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
3454 o Features (ui controller):
3455 - Control interface: a separate program can now talk to your
3456 client/server over a socket, and get/set config options, receive
3457 notifications of circuits and streams starting/finishing/dying,
3458 bandwidth used, etc. The next step is to get some GUIs working.
3459 Let us know if you want to help out. See doc/control-spec.txt .
3460 - Ship a contrib/tor-control.py as an example script to interact
3461 with the control port.
3462 - "tor --hash-password zzyxz" will output a salted password for
3463 use in authenticating to the control interface.
3464 - Implement the control-spec's SAVECONF command, to write your
3465 configuration to torrc.
3466 - Get cookie authentication for the controller closer to working.
3467 - When set_conf changes our server descriptor, upload a new copy.
3468 But don't upload it too often if there are frequent changes.
3470 o Features (config and command-line):
3471 - Deprecate unofficial config option abbreviations, and abbreviations
3472 not on the command line.
3473 - Configuration infrastructure support for warning on obsolete
3475 - Give a slightly more useful output for "tor -h".
3476 - Break DirFetchPostPeriod into:
3477 - DirFetchPeriod for fetching full directory,
3478 - StatusFetchPeriod for fetching running-routers,
3479 - DirPostPeriod for posting server descriptor,
3480 - RendPostPeriod for posting hidden service descriptors.
3481 - New log format in config:
3482 "Log minsev[-maxsev] stdout|stderr|syslog" or
3483 "Log minsev[-maxsev] file /var/foo"
3484 - DirPolicy config option, to let people reject incoming addresses
3485 from their dirserver.
3486 - "tor --list-fingerprint" will list your identity key fingerprint
3488 - Make tor --version --version dump the cvs Id of every file.
3489 - New 'MyFamily nick1,...' config option for a server to
3490 specify other servers that shouldn't be used in the same circuit
3491 with it. Only believed if nick1 also specifies us.
3492 - New 'NodeFamily nick1,nick2,...' config option for a client to
3493 specify nodes that it doesn't want to use in the same circuit.
3494 - New 'Redirectexit pattern address:port' config option for a
3495 server to redirect exit connections, e.g. to a local squid.
3496 - Add "pass" target for RedirectExit, to make it easier to break
3497 out of a sequence of RedirectExit rules.
3498 - Make the dirservers file obsolete.
3499 - Include a dir-signing-key token in directories to tell the
3500 parsing entity which key is being used to sign.
3501 - Remove the built-in bulky default dirservers string.
3502 - New config option "Dirserver %s:%d [fingerprint]", which can be
3503 repeated as many times as needed. If no dirservers specified,
3504 default to moria1,moria2,tor26.
3505 - Make 'Routerfile' config option obsolete.
3506 - Discourage people from setting their dirfetchpostperiod more often
3507 than once per minute.
3510 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
3511 get back to normal.)
3512 - Accept *:706 (silc) in default exit policy.
3513 - Implement new versioning format for post 0.1.
3514 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
3515 log more informatively.
3516 - Check clock skew for verified servers, but allow unverified
3517 servers and clients to have any clock skew.
3518 - Make sure the hidden service descriptors are at a random offset
3519 from each other, to hinder linkability.
3520 - Clients now generate a TLS cert too, in preparation for having
3521 them act more like real nodes.
3522 - Add a pure-C tor-resolve implementation.
3523 - Use getrlimit and friends to ensure we can reach MaxConn (currently
3524 1024) file descriptors.
3525 - Raise the max dns workers from 50 to 100.
3528 Changes in version 0.0.8.1 - 2004-10-13
3530 - Fix a seg fault that can be triggered remotely for Tor
3531 clients/servers with an open dirport.
3532 - Fix a rare assert trigger, where routerinfos for entries in
3533 our cpath would expire while we're building the path.
3534 - Fix a bug in OutboundBindAddress so it (hopefully) works.
3535 - Fix a rare seg fault for people running hidden services on
3536 intermittent connections.
3537 - Fix a bug in parsing opt keywords with objects.
3538 - Fix a stale pointer assert bug when a stream detaches and
3540 - Fix a string format vulnerability (probably not exploitable)
3541 in reporting stats locally.
3542 - Fix an assert trigger: sometimes launching circuits can fail
3543 immediately, e.g. because too many circuits have failed recently.
3544 - Fix a compile warning on 64 bit platforms.
3547 Changes in version 0.0.8 - 2004-08-25
3549 - Made our unit tests compile again on OpenBSD 3.5, and tor
3550 itself compile again on OpenBSD on a sparc64.
3551 - We were neglecting milliseconds when logging on win32, so
3552 everything appeared to happen at the beginning of each second.
3553 - Check directory signature _before_ you decide whether you're
3554 you're running an obsolete version and should exit.
3555 - Check directory signature _before_ you parse the running-routers
3556 list to decide who's running.
3557 - Check return value of fclose while writing to disk, so we don't
3558 end up with broken files when servers run out of disk space.
3559 - Port it to SunOS 5.9 / Athena
3560 - Fix two bugs in saving onion keys to disk when rotating, so
3561 hopefully we'll get fewer people using old onion keys.
3562 - Remove our mostly unused -- and broken -- hex_encode()
3563 function. Use base16_encode() instead. (Thanks to Timo Lindfors
3564 for pointing out this bug.)
3565 - Only pick and establish intro points after we've gotten a
3567 - Fix assert triggers: if the other side returns an address 0.0.0.0,
3568 don't put it into the client dns cache.
3569 - If a begin failed due to exit policy, but we believe the IP
3570 address should have been allowed, switch that router to exitpolicy
3571 reject *:* until we get our next directory.
3574 - 'Extend' relay cell payloads now include the digest of the
3575 intended next hop's identity key. Now we can verify that we're
3576 extending to the right router, and also extend to routers we
3577 hadn't heard of before.
3580 - Tor nodes can now act as relays (with an advertised ORPort)
3581 without being manually verified by the dirserver operators.
3582 - Uploaded descriptors of unverified routers are now accepted
3583 by the dirservers, and included in the directory.
3584 - Verified routers are listed by nickname in the running-routers
3585 list; unverified routers are listed as "$<fingerprint>".
3586 - We now use hash-of-identity-key in most places rather than
3587 nickname or addr:port, for improved security/flexibility.
3588 - AllowUnverifiedNodes config option to let circuits choose no-name
3589 routers in entry,middle,exit,introduction,rendezvous positions.
3590 Allow middle and rendezvous positions by default.
3591 - When picking unverified routers, skip those with low uptime and/or
3592 low bandwidth, depending on what properties you care about.
3593 - ClientOnly option for nodes that never want to become servers.
3594 - Directory caching.
3595 - "AuthoritativeDir 1" option for the official dirservers.
3596 - Now other nodes (clients and servers) will cache the latest
3597 directory they've pulled down.
3598 - They can enable their DirPort to serve it to others.
3599 - Clients will pull down a directory from any node with an open
3600 DirPort, and check the signature/timestamp correctly.
3601 - Authoritative dirservers now fetch directories from other
3602 authdirservers, to stay better synced.
3603 - Running-routers list tells who's down also, along with noting
3604 if they're verified (listed by nickname) or unverified (listed
3606 - Allow dirservers to serve running-router list separately.
3607 This isn't used yet.
3608 - You can now fetch $DIRURL/running-routers to get just the
3609 running-routers line, not the whole descriptor list. (But
3610 clients don't use this yet.)
3611 - Clients choose nodes proportional to advertised bandwidth.
3612 - Clients avoid using nodes with low uptime as introduction points.
3613 - Handle servers with dynamic IP addresses: don't just replace
3614 options->Address with the resolved one at startup, and
3615 detect our address right before we make a routerinfo each time.
3616 - 'FascistFirewall' option to pick dirservers and ORs on specific
3617 ports; plus 'FirewallPorts' config option to tell FascistFirewall
3618 which ports are open. (Defaults to 80,443)
3619 - Try other dirservers immediately if the one you try is down. This
3620 should tolerate down dirservers better now.
3621 - ORs connect-on-demand to other ORs
3622 - If you get an extend cell to an OR you're not connected to,
3623 connect, handshake, and forward the create cell.
3624 - The authoritative dirservers stay connected to everybody,
3625 and everybody stays connected to 0.0.7 servers, but otherwise
3626 clients/servers expire unused connections after 5 minutes.
3627 - When servers get a sigint, they delay 30 seconds (refusing new
3628 connections) then exit. A second sigint causes immediate exit.
3629 - File and name management:
3630 - Look for .torrc if no CONFDIR "torrc" is found.
3631 - If no datadir is defined, then choose, make, and secure ~/.tor
3633 - If torrc not found, exitpolicy reject *:*.
3634 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
3635 - If no nickname is defined, derive default from hostname.
3636 - Rename secret key files, e.g. identity.key -> secret_id_key,
3637 to discourage people from mailing their identity key to tor-ops.
3638 - Refuse to build a circuit before the directory has arrived --
3639 it won't work anyway, since you won't know the right onion keys
3641 - Parse tor version numbers so we can do an is-newer-than check
3642 rather than an is-in-the-list check.
3643 - New socks command 'resolve', to let us shim gethostbyname()
3645 - A 'tor_resolve' script to access the socks resolve functionality.
3646 - A new socks-extensions.txt doc file to describe our
3647 interpretation and extensions to the socks protocols.
3648 - Add a ContactInfo option, which gets published in descriptor.
3649 - Write tor version at the top of each log file
3650 - New docs in the tarball:
3652 - Document that you should proxy your SSL traffic too.
3653 - Log a warning if the user uses an unsafe socks variant, so people
3654 are more likely to learn about privoxy or socat.
3655 - Log a warning if you're running an unverified server, to let you
3656 know you might want to get it verified.
3657 - Change the default exit policy to reject the default edonkey,
3658 kazaa, gnutella ports.
3659 - Add replace_file() to util.[ch] to handle win32's rename().
3660 - Publish OR uptime in descriptor (and thus in directory) too.
3661 - Remember used bandwidth (both in and out), and publish 15-minute
3662 snapshots for the past day into our descriptor.
3663 - Be more aggressive about trying to make circuits when the network
3664 has changed (e.g. when you unsuspend your laptop).
3665 - Check for time skew on http headers; report date in response to
3667 - If the entrynode config line has only one node, don't pick it as
3669 - Add strict{entry|exit}nodes config options. If set to 1, then
3670 we refuse to build circuits that don't include the specified entry
3672 - OutboundBindAddress config option, to bind to a specific
3673 IP address for outgoing connect()s.
3674 - End truncated log entries (e.g. directories) with "[truncated]".
3677 Changes in version 0.0.7.3 - 2004-08-12
3678 o Stop dnsworkers from triggering an assert failure when you
3679 ask them to resolve the host "".
3682 Changes in version 0.0.7.2 - 2004-07-07
3683 o A better fix for the 0.0.0.0 problem, that will hopefully
3684 eliminate the remaining related assertion failures.
3687 Changes in version 0.0.7.1 - 2004-07-04
3688 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
3689 since internally we use 0.0.0.0 to signify "not yet resolved".
3692 Changes in version 0.0.7 - 2004-06-07
3693 o Fixes for crashes and other obnoxious bugs:
3694 - Fix an epipe bug: sometimes when directory connections failed
3695 to connect, we would give them a chance to flush before closing
3697 - When we detached from a circuit because of resolvefailed, we
3698 would immediately try the same circuit twice more, and then
3699 give up on the resolve thinking we'd tried three different
3701 - Limit the number of intro circuits we'll attempt to build for a
3702 hidden service per 15-minute period.
3703 - Check recommended-software string *early*, before actually parsing
3704 the directory. Thus we can detect an obsolete version and exit,
3705 even if the new directory format doesn't parse.
3706 o Fixes for security bugs:
3707 - Remember which nodes are dirservers when you startup, and if a
3708 random OR enables his dirport, don't automatically assume he's
3709 a trusted dirserver.
3711 - Directory connections were asking the wrong poll socket to
3712 start writing, and not asking themselves to start writing.
3713 - When we detached from a circuit because we sent a begin but
3714 didn't get a connected, we would use it again the first time;
3715 but after that we would correctly switch to a different one.
3716 - Stop warning when the first onion decrypt attempt fails; they
3717 will sometimes legitimately fail now that we rotate keys.
3718 - Override unaligned-access-ok check when $host_cpu is ia64 or
3719 arm. Apparently they allow it but the kernel whines.
3720 - Dirservers try to reconnect periodically too, in case connections
3722 - Fix some memory leaks in directory servers.
3723 - Allow backslash in Win32 filenames.
3724 - Made Tor build complain-free on FreeBSD, hopefully without
3725 breaking other BSD builds. We'll see.
3726 - Check directory signatures based on name of signer, not on whom
3727 we got the directory from. This will let us cache directories more
3729 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
3732 - Doxygen markup on all functions and global variables.
3733 - Make directory functions update routerlist, not replace it. So
3734 now directory disagreements are not so critical a problem.
3735 - Remove the upper limit on number of descriptors in a dirserver's
3736 directory (not that we were anywhere close).
3737 - Allow multiple logfiles at different severity ranges.
3738 - Allow *BindAddress to specify ":port" rather than setting *Port
3739 separately. Allow multiple instances of each BindAddress config
3740 option, so you can bind to multiple interfaces if you want.
3741 - Allow multiple exit policy lines, which are processed in order.
3742 Now we don't need that huge line with all the commas in it.
3743 - Enable accept/reject policies on SOCKS connections, so you can bind
3744 to 0.0.0.0 but still control who can use your OP.
3745 - Updated the man page to reflect these features.
3748 Changes in version 0.0.6.2 - 2004-05-16
3749 o Our integrity-checking digest was checking only the most recent cell,
3750 not the previous cells like we'd thought.
3751 Thanks to Stefan Mark for finding the flaw!
3754 Changes in version 0.0.6.1 - 2004-05-06
3755 o Fix two bugs in our AES counter-mode implementation (this affected
3756 onion-level stream encryption, but not TLS-level). It turns
3757 out we were doing something much more akin to a 16-character
3758 polyalphabetic cipher. Oops.
3759 Thanks to Stefan Mark for finding the flaw!
3760 o Retire moria3 as a directory server, and add tor26 as a directory
3764 Changes in version 0.0.6 - 2004-05-02
3766 - Hidden services and rendezvous points are implemented. Go to
3767 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
3768 hidden services. (This only works via a socks4a proxy such as
3769 Privoxy, and currently it's quite slow.)
3770 - We now rotate link (tls context) keys and onion keys.
3771 - CREATE cells now include oaep padding, so you can tell
3772 if you decrypted them correctly.
3773 - Retry stream correctly when we fail to connect because of
3774 exit-policy-reject (should try another) or can't-resolve-address.
3775 - When we hup a dirserver and we've *removed* a server from the
3776 approved-routers list, now we remove that server from the
3777 in-memory directories too.
3778 - Add bandwidthburst to server descriptor.
3779 - Directories now say which dirserver signed them.
3780 - Use a tor_assert macro that logs failed assertions too.
3781 - Since we don't support truncateds much, don't bother sending them;
3782 just close the circ.
3783 - Fetch randomness from /dev/urandom better (not via fopen/fread)
3784 - Better debugging for tls errors
3785 - Set Content-Type on the directory and hidserv descriptor.
3786 - Remove IVs from cipher code, since AES-ctr has none.
3788 - Fix an assert trigger for exit nodes that's been plaguing us since
3789 the days of 0.0.2prexx (thanks weasel!)
3790 - Fix a bug where we were closing tls connections intermittently.
3791 It turns out openssl keeps its errors around -- so if an error
3792 happens, and you don't ask about it, and then another openssl
3793 operation happens and succeeds, and you ask if there was an error,
3794 it tells you about the first error.
3795 - Fix a bug that's been lurking since 27 may 03 (!)
3796 When passing back a destroy cell, we would use the wrong circ id.
3797 - Don't crash if a conn that sent a begin has suddenly lost its circuit.
3798 - Some versions of openssl have an SSL_pending function that erroneously
3799 returns bytes when there is a non-application record pending.
3800 - Win32 fixes. Tor now compiles on win32 with no warnings/errors.
3801 o We were using an array of length zero in a few places.
3802 o Win32's gethostbyname can't resolve an IP to an IP.
3803 o Win32's close can't close a socket.
3804 o Handle windows socket errors correctly.
3806 - check for <sys/limits.h> so we build on FreeBSD again, and
3807 <machine/limits.h> for NetBSD.
3810 Changes in version 0.0.5 - 2004-03-30
3811 o Install torrc as torrc.sample -- we no longer clobber your
3813 o Fix mangled-state bug in directory fetching (was causing sigpipes).
3814 o Only build circuits after we've fetched the directory: clients were
3815 using only the directory servers before they'd fetched a directory.
3816 This also means longer startup time; so it goes.
3817 o Fix an assert trigger where an OP would fail to handshake, and we'd
3818 expect it to have a nickname.
3819 o Work around a tsocks bug: do a socks reject when AP connection dies
3820 early, else tsocks goes into an infinite loop.
3821 o Hold socks connection open until reply is flushed (if possible)
3822 o Make exit nodes resolve IPs to IPs immediately, rather than asking
3823 the dns farm to do it.
3824 o Fix c99 aliasing warnings in rephist.c
3825 o Don't include server descriptors that are older than 24 hours in the
3827 o Give socks 'reject' replies their whole 15s to attempt to flush,
3828 rather than seeing the 60s timeout and assuming the flush had failed.
3829 o Clean automake droppings from the cvs repository
3830 o Add in a 'notice' log level for things the operator should hear
3831 but that aren't warnings
3834 Changes in version 0.0.4 - 2004-03-26
3835 o When connecting to a dirserver or OR and the network is down,
3839 Changes in version 0.0.3 - 2004-03-26
3840 o Warn and fail if server chose a nickname with illegal characters
3841 o Port to Solaris and Sparc:
3842 - include missing header fcntl.h
3843 - have autoconf find -lsocket -lnsl automatically
3844 - deal with hardware word alignment
3845 - make uname() work (solaris has a different return convention)
3846 - switch from using signal() to sigaction()
3847 o Preliminary work on reputation system:
3848 - Keep statistics on success/fail of connect attempts; they're published
3849 by kill -USR1 currently.
3850 - Add a RunTesting option to try to learn link state by creating test
3851 circuits, even when SocksPort is off.
3852 - Remove unused open circuits when there are too many.
3855 Changes in version 0.0.2 - 2004-03-19
3856 - Include strlcpy and strlcat for safer string ops
3857 - define INADDR_NONE so we compile (but still not run) on solaris
3860 Changes in version 0.0.2pre27 - 2004-03-14
3862 - Allow internal tor networks (we were rejecting internal IPs,
3863 now we allow them if they're set explicitly).
3864 - And fix a few endian issues.
3867 Changes in version 0.0.2pre26 - 2004-03-14
3869 - If a stream times out after 15s without a connected cell, don't
3870 try that circuit again: try a new one.
3871 - Retry streams at most 4 times. Then give up.
3872 - When a dirserver gets a descriptor from an unknown router, it
3873 logs its fingerprint (so the dirserver operator can choose to
3874 accept it even without mail from the server operator).
3875 - Inform unapproved servers when we reject their descriptors.
3876 - Make tor build on Windows again. It works as a client, who knows
3878 - Clearer instructions in the torrc for how to set up a server.
3879 - Be more efficient about reading fd's when our global token bucket
3880 (used for rate limiting) becomes empty.
3882 - Stop asserting that computers always go forward in time. It's
3884 - When we sent a cell (e.g. destroy) and then marked an OR connection
3885 expired, we might close it before finishing a flush if the other
3886 side isn't reading right then.
3887 - Don't allow dirservers to start if they haven't defined
3889 - We were caching transient dns failures. Oops.
3890 - Prevent servers from publishing an internal IP as their address.
3891 - Address a strcat vulnerability in circuit.c
3894 Changes in version 0.0.2pre25 - 2004-03-04
3896 - Put the OR's IP in its router descriptor, not its fqdn. That way
3897 we'll stop being stalled by gethostbyname for nodes with flaky dns,
3900 - If the user typed in an address that didn't resolve, the server
3904 Changes in version 0.0.2pre24 - 2004-03-03
3906 - Fix an assertion failure in dns.c, where we were trying to dequeue
3907 a pending dns resolve even if it wasn't pending
3908 - Fix a spurious socks5 warning about still trying to write after the
3909 connection is finished.
3910 - Hold certain marked_for_close connections open until they're finished
3911 flushing, rather than losing bytes by closing them too early.
3912 - Correctly report the reason for ending a stream
3913 - Remove some duplicate calls to connection_mark_for_close
3914 - Put switch_id and start_daemon earlier in the boot sequence, so it
3915 will actually try to chdir() to options.DataDirectory
3916 - Make 'make test' exit(1) if a test fails; fix some unit tests
3917 - Make tor fail when you use a config option it doesn't know about,
3918 rather than warn and continue.
3919 - Make --version work
3920 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
3923 Changes in version 0.0.2pre23 - 2004-02-29
3925 - Print a statement when the first circ is finished, so the user
3927 - If a relay cell is unrecognized at the end of the circuit,
3928 send back a destroy. (So attacks to mutate cells are more
3930 - New config option 'excludenodes' to avoid certain nodes for circuits.
3931 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
3932 so you can collect coredumps there.
3934 - Fix a bug in tls flushing where sometimes data got wedged and
3935 didn't flush until more data got sent. Hopefully this bug was
3936 a big factor in the random delays we were seeing.
3937 - Make 'connected' cells include the resolved IP, so the client
3938 dns cache actually gets populated.
3939 - Disallow changing from ORPort=0 to ORPort>0 on hup.
3940 - When we time-out on a stream and detach from the circuit, send an
3941 end cell down it first.
3942 - Only warn about an unknown router (in exitnodes, entrynodes,
3943 excludenodes) after we've fetched a directory.
3946 Changes in version 0.0.2pre22 - 2004-02-26
3948 - Servers publish less revealing uname information in descriptors.
3949 - More memory tracking and assertions, to crash more usefully when
3951 - If the default torrc isn't there, just use some default defaults.
3952 Plus provide an internal dirservers file if they don't have one.
3953 - When the user tries to use Tor as an http proxy, give them an http
3954 501 failure explaining that we're a socks proxy.
3955 - Dump a new router.desc on hup, to help confused people who change
3956 their exit policies and then wonder why router.desc doesn't reflect
3958 - Clean up the generic tor.sh init script that we ship with.
3960 - If the exit stream is pending on the resolve, and a destroy arrives,
3961 then the stream wasn't getting removed from the pending list. I
3962 think this was the one causing recent server crashes.
3963 - Use a more robust poll on OSX 10.3, since their poll is flaky.
3964 - When it couldn't resolve any dirservers, it was useless from then on.
3965 Now it reloads the RouterFile (or default dirservers) if it has no
3967 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
3968 many users don't even *have* a /usr/local/sbin/.
3971 Changes in version 0.0.2pre21 - 2004-02-18
3973 - There's a ChangeLog file that actually reflects the changelog.
3974 - There's a 'torify' wrapper script, with an accompanying
3975 tor-tsocks.conf, that simplifies the process of using tsocks for
3976 tor. It even has a man page.
3977 - The tor binary gets installed to sbin rather than bin now.
3978 - Retry streams where the connected cell hasn't arrived in 15 seconds
3979 - Clean up exit policy handling -- get the default out of the torrc,
3980 so we can update it without forcing each server operator to fix
3982 - Allow imaps and pop3s in default exit policy
3984 - Prevent picking middleman nodes as the last node in the circuit
3987 Changes in version 0.0.2pre20 - 2004-01-30
3989 - We now have a deb package, and it's in debian unstable. Go to
3991 - I've split the TotalBandwidth option into BandwidthRate (how many
3992 bytes per second you want to allow, long-term) and
3993 BandwidthBurst (how many bytes you will allow at once before the cap
3994 kicks in). This better token bucket approach lets you, say, set
3995 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
3996 performance while not exceeding your monthly bandwidth quota.
3997 - Push out a tls record's worth of data once you've got it, rather
3998 than waiting until you've read everything waiting to be read. This
3999 may improve performance by pipelining better. We'll see.
4000 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
4001 from failed circuits (if they haven't been connected yet) and attach
4003 - Expire old streams that haven't managed to connect. Some day we'll
4004 have them reattach to new circuits instead.
4007 - Fix several memory leaks that were causing servers to become bloated
4009 - Fix a few very rare assert triggers. A few more remain.
4010 - Setuid to User _before_ complaining about running as root.
4013 Changes in version 0.0.2pre19 - 2004-01-07
4015 - Fix deadlock condition in dns farm. We were telling a child to die by
4016 closing the parent's file descriptor to him. But newer children were
4017 inheriting the open file descriptor from the parent, and since they
4018 weren't closing it, the socket never closed, so the child never read
4019 eof, so he never knew to exit. Similarly, dns workers were holding
4020 open other sockets, leading to all sorts of chaos.
4021 - New cleaner daemon() code for forking and backgrounding.
4022 - If you log to a file, it now prints an entry at the top of the
4023 logfile so you know it's working.
4024 - The onionskin challenge length was 30 bytes longer than necessary.
4025 - Started to patch up the spec so it's not quite so out of date.
4028 Changes in version 0.0.2pre18 - 2004-01-02
4030 - Fix endian issues with the 'integrity' field in the relay header.
4031 - Fix a potential bug where connections in state
4032 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
4035 Changes in version 0.0.2pre17 - 2003-12-30
4037 - Made --debuglogfile (or any second log file, actually) work.
4038 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
4039 adversary could force us into an infinite loop.
4042 - Each onionskin handshake now includes a hash of the computed key,
4043 to prove the server's identity and help perfect forward secrecy.
4044 - Changed cell size from 256 to 512 bytes (working toward compatibility
4046 - Changed cell length to 2 bytes, and moved it to the relay header.
4047 - Implemented end-to-end integrity checking for the payloads of
4049 - Separated streamid from 'recognized' (otherwise circuits will get
4050 messed up when we try to have streams exit from the middle). We
4051 use the integrity-checking to confirm that a cell is addressed to
4053 - Randomize the initial circid and streamid values, so an adversary who
4054 breaks into a node can't learn how many circuits or streams have
4058 Changes in version 0.0.2pre16 - 2003-12-14
4060 - Fixed a bug that made HUP trigger an assert
4061 - Fixed a bug where a circuit that immediately failed wasn't being
4062 counted as a failed circuit in counting retries.
4065 - Now we close the circuit when we get a truncated cell: otherwise we're
4066 open to an anonymity attack where a bad node in the path truncates
4067 the circuit and then we open streams at him.
4068 - Add port ranges to exit policies
4069 - Add a conservative default exit policy
4070 - Warn if you're running tor as root
4071 - on HUP, retry OR connections and close/rebind listeners
4072 - options.EntryNodes: try these nodes first when picking the first node
4073 - options.ExitNodes: if your best choices happen to include any of
4074 your preferred exit nodes, you choose among just those preferred
4076 - options.ExcludedNodes: nodes that are never picked in path building
4079 Changes in version 0.0.2pre15 - 2003-12-03
4080 o Robustness and bugfixes:
4081 - Sometimes clients would cache incorrect DNS resolves, which would
4082 really screw things up.
4083 - An OP that goes offline would slowly leak all its sockets and stop
4085 - A wide variety of bugfixes in exit node selection, exit policy
4086 handling, and processing pending streams when a new circuit is
4088 - Pick nodes for a path only from those the directory says are up
4089 - Choose randomly from all running dirservers, not always the first one
4090 - Increase allowed http header size for directory fetch.
4091 - Stop writing to stderr (if we're daemonized it will be closed).
4092 - Enable -g always, so cores will be more useful to me.
4093 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
4096 - Wrote a man page. It lists commonly used options.
4099 - Change default loglevel to warn.
4100 - Make PidFile default to null rather than littering in your CWD.
4101 - OnionRouter config option is now obsolete. Instead it just checks
4103 - Moved to a single unified torrc file for both clients and servers.
4106 Changes in version 0.0.2pre14 - 2003-11-29
4107 o Robustness and bugfixes:
4108 - Force the admin to make the DataDirectory himself
4109 - to get ownership/permissions right
4110 - so clients no longer make a DataDirectory and then never use it
4111 - fix bug where a client who was offline for 45 minutes would never
4112 pull down a directory again
4113 - fix (or at least hide really well) the dns assert bug that was
4114 causing server crashes
4115 - warnings and improved robustness wrt clockskew for certs
4116 - use the native daemon(3) to daemonize, when available
4117 - exit if bind() fails
4118 - exit if neither socksport nor orport is defined
4119 - include our own tor_timegm (Win32 doesn't have its own)
4120 - bugfix for win32 with lots of connections
4121 - fix minor bias in PRNG
4122 - make dirserver more robust to corrupt cached directory
4125 - Wrote the design document (woo)
4127 o Circuit building and exit policies:
4128 - Circuits no longer try to use nodes that the directory has told them
4130 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
4131 bitcounts (18.0.0.0/8).
4132 - Make AP connections standby for a circuit if no suitable circuit
4133 exists, rather than failing
4134 - Circuits choose exit node based on addr/port, exit policies, and
4135 which AP connections are standing by
4136 - Bump min pathlen from 2 to 3
4137 - Relay end cells have a payload to describe why the stream ended.
4138 - If the stream failed because of exit policy, try again with a new
4140 - Clients have a dns cache to remember resolved addresses.
4141 - Notice more quickly when we have no working circuits
4144 - APPort is now called SocksPort
4145 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
4147 - RecommendedVersions is now a config variable rather than
4148 hardcoded (for dirservers)
4149 - Reloads config on HUP
4150 - Usage info on -h or --help
4151 - If you set User and Group config vars, it'll setu/gid to them.
4153 Changes in version 0.0.2pre13 - 2003-10-19
4154 o General stability:
4155 - SSL_write no longer fails when it returns WANTWRITE and the number
4156 of bytes in the buf has changed by the next SSL_write call.
4157 - Fix segfault fetching directory when network is down
4158 - Fix a variety of minor memory leaks
4159 - Dirservers reload the fingerprints file on HUP, so I don't have
4160 to take down the network when I approve a new router
4161 - Default server config file has explicit Address line to specify fqdn
4164 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
4165 - Make listener connections not ever alloc bufs
4167 o Autoconf improvements:
4168 - don't clobber an external CFLAGS in ./configure
4169 - Make install now works
4170 - create var/lib/tor on make install
4171 - autocreate a tor.sh initscript to help distribs
4172 - autocreate the torrc and sample-server-torrc with correct paths
4174 o Log files and Daemonizing now work:
4175 - If --DebugLogFile is specified, log to it at -l debug
4176 - If --LogFile is specified, use it instead of commandline
4177 - If --RunAsDaemon is set, tor forks and backgrounds on startup