1 Changes in version 0.2.3.16-alpha - 2012-06-05
2 o Major bugfixes (general):
3 - Work around a bug in OpenSSL that broke renegotiation with TLS
4 1.1 and TLS 1.2. Without this workaround, all attempts to speak
5 the v2 Tor connection protocol when both sides were using OpenSSL
6 1.0.1 would fail. Resolves ticket 6033.
7 - When waiting for a client to renegotiate, don't allow it to add
8 any bytes to the input buffer. This fixes a potential DoS issue.
9 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
10 - Pass correct OR address to managed proxies (like obfsproxy),
11 even when ORListenAddress is used. Fixes bug 4865; bugfix on
13 - The advertised platform of a router now includes only its operating
14 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
15 service pack level (for Windows) or its CPU architecture (for Unix).
16 We also no longer include the "git-XYZ" tag in the version. Resolves
19 o Major bugfixes (clients):
20 - If we are unable to find any exit that supports our predicted ports,
21 stop calling them predicted, so that we don't loop and build
22 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
23 which introduced predicted ports.
24 - Fix an edge case where if we fetch or publish a hidden service
25 descriptor, we might build a 4-hop circuit and then use that circuit
26 for exiting afterwards -- even if the new last hop doesn't obey our
27 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
28 - Check at each new consensus whether our entry guards were picked
29 long enough ago that we should rotate them. Previously, we only
30 did this check at startup, which could lead to us holding a guard
31 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
32 - When fetching a bridge descriptor from a bridge authority,
33 always do so anonymously, whether we have been able to open
34 circuits or not. Partial fix for bug 1938; bugfix on 2.0.7-alpha.
35 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
36 but we'll need to wait for bug 6010 before it's actually usable.
38 o Major bugfixes (directory authorities):
39 - When computing weight parameters, behave more robustly in the
40 presence of a bad bwweightscale value. Previously, the authorities
41 would crash if they agreed on a sufficiently broken weight_scale
42 value: now, they use a reasonable default and carry on. Partial
43 fix for 5786; bugfix on 0.2.2.17-alpha.
44 - Check more thoroughly to prevent a rogue authority from
45 double-voting on any consensus directory parameter. Previously,
46 authorities would crash in this case if the total number of
47 votes for any parameter exceeded the number of active voters,
48 but would let it pass otherwise. Partial fix for bug 5786; bugfix
52 - Rate-limit log messages when asked to connect anonymously to
53 a private address. When these hit, they tended to hit fast and
54 often. Also, don't bother trying to connect to addresses that we
55 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
56 reply makes us think we have been lied to, even when the address the
57 client tried to connect to was "localhost." Resolves ticket 2822.
58 - Allow packagers to insert an extra string in server descriptor
59 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
60 Resolves the rest of ticket 2988.
61 - Raise the threshold of server descriptors needed (75%) and exit
62 server descriptors needed (50%) before we will declare ourselves
63 bootstrapped. This will make clients start building circuits a
64 little later, but makes the initially constructed circuits less
65 skewed and less in conflict with further directory fetches. Fixes
67 - Close any connection that sends unrecognized junk before the
68 handshake. Solves an issue noted in bug 4369.
69 - Improve log messages about managed transports. Resolves ticket 5070.
70 - Tag a bridge's descriptor as "never to be sent unencrypted".
71 This shouldn't matter, since bridges don't open non-anonymous
72 connections to the bridge authority and don't allow unencrypted
73 directory connections from clients, but we might as well make
74 sure. Closes bug 5139.
75 - Expose our view of whether we have gone dormant to the controller,
76 via a new "GETINFO dormant" value. Torbutton and other controllers
77 can use this to avoid doing periodic requests through Tor while
78 it's dormant (bug 4718). Fixes bug 5954.
79 - Tell GCC and Clang to check for any errors in format strings passed
80 to the tor_v*(print|scan)f functions.
81 - Update to the May 1 2012 Maxmind GeoLite Country database.
83 o Minor bugfixes (already included in 0.2.2.36):
84 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
85 Fixes bug 5346; bugfix on 0.0.8pre3.
86 - Correct parsing of certain date types in parse_http_time().
87 Without this patch, If-Modified-Since would behave
88 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
89 Esteban Manchado Velázques.
90 - Make our number-parsing functions always treat too-large values
91 as an error, even when those values exceed the width of the
92 underlying type. Previously, if the caller provided these
93 functions with minima or maxima set to the extreme values of the
94 underlying integer type, these functions would return those
95 values on overflow rather than treating overflow as an error.
96 Fixes part of bug 5786; bugfix on 0.0.9.
97 - If we hit the error case where routerlist_insert() replaces an
98 existing (old) server descriptor, make sure to remove that
99 server descriptor from the old_routers list. Fix related to bug
100 1776. Bugfix on 0.2.2.18-alpha.
101 - Clarify the behavior of MaxCircuitDirtiness with hidden service
102 circuits. Fixes issue 5259.
104 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
105 - Prevent a null-pointer dereference when receiving a data cell
106 for a nonexistent stream when the circuit in question has an
107 empty deliver window. We don't believe this is triggerable,
108 since we don't currently allow deliver windows to become empty,
109 but the logic is tricky enough that it's better to make the code
110 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
111 - Fix a memory leak when trying to launch a DNS request when the
112 network is disabled or the nameservers are unconfigurable. Fixes
113 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
114 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
115 - Don't hold a windows file handle open for every file mapping;
116 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
118 - Avoid O(n^2) performance characteristics when parsing a large
119 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
120 - Format more doubles with %f, not %lf. Patch from grarpamp to make
121 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
123 - Make our replacement implementation of strtok_r() compatible with
124 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
125 bugfix on 0.2.2.1-alpha.
126 - Fix a NULL-pointer dereference on a badly formed
127 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
128 bugfix on 0.2.2.9-alpha.
129 - Fix a build warning with Clang 3.1 related to our use of vasprint.
130 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
131 - Defensively refactor rend_mid_rendezvous() so that protocol
132 violations and length checks happen in the beginning. Fixes
134 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
135 that IPv6 stuff will compile on MSVC, and compilation issues
136 will be easier to track down. Fixes bug 5861.
138 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
139 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
140 resource exhaustion, so that clients can adjust their load to
141 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
142 started using END_STREAM_REASON_RESOURCELIMIT.
143 - Don't check for whether the address we're using for outbound
144 connections has changed until after the outbound connection has
145 completed. On Windows, getsockname() doesn't succeed until the
146 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
147 - If the configuration tries to set MyFamily on a bridge, refuse to
148 do so, and warn about the security implications. Fixes bug 4657;
149 bugfix on 0.2.0.3-alpha.
150 - If the client fails to set a reasonable set of ciphersuites
151 during its v2 handshake renegotiation, allow the renegotiation to
152 continue nevertheless (i.e. send all the required certificates).
153 Fixes bug 4591; bugfix on 0.2.0.20-rc.
154 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
155 option is set to 0 (which Vidalia version 0.2.16 now does when
156 a SAVECONF attempt fails), perform other actions that SIGHUP
157 usually causes (like reopening the logs). Fixes bug 5095; bugfix
159 - If we fail to write a microdescriptor to the disk cache, do not
160 continue replacing the old microdescriptor file. Fixes bug 2954;
161 bugfix on 0.2.2.6-alpha.
162 - Exit nodes don't need to fetch certificates for authorities that
163 they don't recognize; only directory authorities, bridges,
164 and caches need to do that. Fixes part of bug 2297; bugfix on
166 - Correctly handle checking the permissions on the parent
167 directory of a control socket in the root directory. Bug found
168 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
170 - When told to add a bridge with the same digest as a preexisting
171 bridge but a different addr:port, change the addr:port as
172 requested. Previously we would not notice the change. Fixes half
173 of bug 5603; fix on 0.2.2.26-beta.
174 - End AUTHCHALLENGE error messages (in the control protocol) with
175 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
177 o Minor bugfixes (on 0.2.3.x):
178 - Turn an assertion (that the number of handshakes received as a
179 server is not < 1) into a warning. Fixes bug 4873; bugfix on
181 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
182 we had reversed them when the answer was cached.) Fixes bug
183 5723; bugfix on 0.2.3.1-alpha.
184 - Work correctly on Linux systems with accept4 support advertised in
185 their headers, but without accept4 support in the kernel. Fix
186 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
187 - When told to add a bridge with the same addr:port as a preexisting
188 bridge but a different transport, change the transport as
189 requested. Previously we would not notice the change. Fixes half
190 of bug 5603; fix on 0.2.3.2-alpha.
191 - Avoid a "double-reply" warning when replying to a SOCKS request
192 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
193 bugfix on 0.2.3.4-alpha.
194 - Fix a bug where a bridge authority crashes if it has seen no
195 directory requests when it's time to write statistics to disk.
196 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
198 - Don't try to open non-control listeners when DisableNetwork is set.
199 Previousy, we'd open all listeners, then immediately close them.
200 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
201 - Don't abort the managed proxy protocol if the managed proxy
202 sends us an unrecognized line; ignore it instead. Fixes bug
203 5910; bugfix on 0.2.3.9-alpha.
204 - Fix a compile warning in crypto.c when compiling with clang 3.1.
205 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
206 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
207 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
208 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
209 unbreak the MSVC build. Fies bug 5858; bugfix on 0.2.3.12-alpha.
210 - Resolve numerous small warnings and build issues with MSVC. Resolves
213 o Documentation fixes:
214 - Improve the manual's documentation for the NT Service command-line
215 options. Addresses ticket 3964.
216 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
217 - Document the changes to the ORPort and DirPort options, and the
218 fact that {OR/Dir}ListenAddress is now unnecessary (and
219 therefore deprecated). Resolves ticket 5597.
222 - Remove the torrc.bridge file: we don't use it for anything, and
223 it had become badly desynchronized from torrc.sample. Resolves
227 Changes in version 0.2.2.36 - 2012-05-24
228 Tor 0.2.2.36 updates the addresses for two of the eight directory
229 authorities, fixes some potential anonymity and security issues,
230 and fixes several crash bugs.
232 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
233 known flaws, and nobody should be using them. You should upgrade. If
234 you're using a Linux or BSD and its packages are obsolete, stop using
235 those packages and upgrade anyway.
237 o Directory authority changes:
238 - Change IP address for maatuska (v3 directory authority).
239 - Change IP address for ides (v3 directory authority), and rename
243 - When building or running with any version of OpenSSL earlier
244 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
245 versions have a bug (CVE-2011-4576) in which their block cipher
246 padding includes uninitialized data, potentially leaking sensitive
247 information to any peer with whom they make a SSLv3 connection. Tor
248 does not use SSL v3 by default, but a hostile client or server
249 could force an SSLv3 connection in order to gain information that
250 they shouldn't have been able to get. The best solution here is to
251 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
252 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
253 to make sure that the bug can't happen.
254 - Never use a bridge or a controller-supplied node as an exit, even
255 if its exit policy allows it. Found by wanoskarnet. Fixes bug
256 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
257 and 0.2.0.3-alpha (for bridge-purpose descriptors).
258 - Only build circuits if we have a sufficient threshold of the total
259 descriptors that are marked in the consensus with the "Exit"
260 flag. This mitigates an attack proposed by wanoskarnet, in which
261 all of a client's bridges collude to restrict the exit nodes that
262 the client knows about. Fixes bug 5343.
263 - Provide controllers with a safer way to implement the cookie
264 authentication mechanism. With the old method, if another locally
265 running program could convince a controller that it was the Tor
266 process, then that program could trick the contoller into telling
267 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
268 authentication method uses a challenge-response approach to prevent
269 this attack. Fixes bug 5185; implements proposal 193.
272 - Avoid logging uninitialized data when unable to decode a hidden
273 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
274 - Avoid a client-side assertion failure when receiving an INTRODUCE2
275 cell on a general purpose circuit. Fixes bug 5644; bugfix on
277 - Fix builds when the path to sed, openssl, or sha1sum contains
278 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
280 - Correct our replacements for the timeradd() and timersub() functions
281 on platforms that lack them (for example, Windows). The timersub()
282 function is used when expiring circuits, while timeradd() is
283 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
284 bugfix on 0.2.2.24-alpha.
285 - Fix the SOCKET_OK test that we use to tell when socket
286 creation fails so that it works on Win64. Fixes part of bug 4533;
287 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
290 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
291 Fixes bug 5346; bugfix on 0.0.8pre3.
292 - Make our number-parsing functions always treat too-large values
293 as an error, even when those values exceed the width of the
294 underlying type. Previously, if the caller provided these
295 functions with minima or maxima set to the extreme values of the
296 underlying integer type, these functions would return those
297 values on overflow rather than treating overflow as an error.
298 Fixes part of bug 5786; bugfix on 0.0.9.
299 - Older Linux kernels erroneously respond to strange nmap behavior
300 by having accept() return successfully with a zero-length
301 socket. When this happens, just close the connection. Previously,
302 we would try harder to learn the remote address: but there was
303 no such remote address to learn, and our method for trying to
304 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
305 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
306 - Correct parsing of certain date types in parse_http_time().
307 Without this patch, If-Modified-Since would behave
308 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
309 Esteban Manchado Velázques.
310 - Change the BridgePassword feature (part of the "bridge community"
311 design, which is not yet implemented) to use a time-independent
312 comparison. The old behavior might have allowed an adversary
313 to use timing to guess the BridgePassword value. Fixes bug 5543;
314 bugfix on 0.2.0.14-alpha.
315 - Detect and reject certain misformed escape sequences in
316 configuration values. Previously, these values would cause us
317 to crash if received in a torrc file or over an authenticated
318 control port. Bug found by Esteban Manchado Velázquez, and
319 independently by Robert Connolly from Matta Consulting who further
320 noted that it allows a post-authentication heap overflow. Patch
321 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
322 bugfix on 0.2.0.16-alpha.
323 - Fix a compile warning when using the --enable-openbsd-malloc
324 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
325 - During configure, detect when we're building with clang version
326 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
327 CFLAGS. clang doesn't support them yet.
328 - When sending an HTTP/1.1 proxy request, include a Host header.
329 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
330 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
331 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
332 - If we hit the error case where routerlist_insert() replaces an
333 existing (old) server descriptor, make sure to remove that
334 server descriptor from the old_routers list. Fix related to bug
335 1776. Bugfix on 0.2.2.18-alpha.
337 o Minor bugfixes (documentation and log messages):
338 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
339 Fixes bug 4856; bugfix on Tor 0.0.6.
340 - Update "ClientOnly" man page entry to explain that there isn't
341 really any point to messing with it. Resolves ticket 5005.
342 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
343 directory authority option (introduced in Tor 0.2.2.34).
344 - Downgrade the "We're missing a certificate" message from notice
345 to info: people kept mistaking it for a real problem, whereas it
346 is seldom the problem even when we are failing to bootstrap. Fixes
347 bug 5067; bugfix on 0.2.0.10-alpha.
348 - Correctly spell "connect" in a log message on failure to create a
349 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
350 - Clarify the behavior of MaxCircuitDirtiness with hidden service
351 circuits. Fixes issue 5259.
354 - Directory authorities now reject versions of Tor older than
355 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
356 inclusive. These versions accounted for only a small fraction of
357 the Tor network, and have numerous known security issues. Resolves
359 - Update to the May 1 2012 Maxmind GeoLite Country database.
362 - When sending or relaying a RELAY_EARLY cell, we used to convert
363 it to a RELAY cell if the connection was using the v1 link
364 protocol. This was a workaround for older versions of Tor, which
365 didn't handle RELAY_EARLY cells properly. Now that all supported
366 versions can handle RELAY_EARLY cells, and now that we're enforcing
367 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
368 remove this workaround. Addresses bug 4786.
371 Changes in version 0.2.3.15-alpha - 2012-04-30
372 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
373 the development branch build on Windows again.
375 o Minor bugfixes (on 0.2.2.x and earlier):
376 - Make sure that there are no unhandled pending TLS errors before
377 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
378 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
379 Bugfix on 0.1.0.5-rc; fixes bug 4528.
380 - Fix an assert that directory authorities could trigger on sighup
381 during some configuration state transitions. We now don't treat
382 it as a fatal error when the new descriptor we just generated in
383 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
384 - After we pick a directory mirror, we would refuse to use it if
385 it's in our ExcludeExitNodes list, resulting in mysterious failures
386 to bootstrap for people who just wanted to avoid exiting from
387 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
388 - When building with --enable-static-tor on OpenBSD, do not
389 erroneously attempt to link -lrt. Fixes bug 5103.
391 o Minor bugfixes (on 0.2.3.x):
392 - When Tor is built with kernel headers from a recent (last few
393 years) Linux kernel, do not fail to run on older (pre-2.6.28
394 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
395 - Fix cross-compilation isssues with mingw. Bugfixes on 0.2.3.6-alpha
397 - Fix compilation with miniupnpc version 1.6; patch from
398 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
399 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
400 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
401 - Fix compilation on platforms without unistd.h, or where environ
402 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
405 - Directory authorities are now a little more lenient at accepting
406 older router descriptors, or newer router descriptors that don't
407 make big changes. This should help ameliorate past and future
408 issues where routers think they have uploaded valid descriptors,
409 but the authorities don't think so. Fix for ticket 2479.
410 - Make the code that clients use to detect an address change be
411 IPv6-aware, so that it won't fill clients' logs with error
412 messages when trying to get the IPv4 address of an IPv6
413 connection. Implements ticket 5537.
416 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
417 authorities needed to use it for a while to keep the network working
418 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
419 that was six months ago. As of now, it should no longer be needed
423 Changes in version 0.2.3.14-alpha - 2012-04-23
424 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
425 candidate. It also dramatically speeds up AES: fast relays should
426 consider switching to the newer OpenSSL library.
428 o Directory authority changes:
429 - Change IP address for ides (v3 directory authority), and rename
433 - Avoid logging uninitialized data when unable to decode a hidden
434 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
435 - Avoid a client-side assertion failure when receiving an INTRODUCE2
436 cell on a general purpose circuit. Fixes bug 5644; bugfix on
438 - If authorities are unable to get a v2 consensus document from other
439 directory authorities, they no longer fall back to fetching
440 them from regular directory caches. Fixes bug 5635; bugfix on
441 0.2.2.26-beta, where routers stopped downloading v2 consensus
443 - When we start a Tor client with a normal consensus already cached,
444 be willing to download a microdescriptor consensus. Fixes bug 4011;
445 fix on 0.2.3.1-alpha.
447 o Major features (performance):
448 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
449 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
450 vectorized AES implementations as appropriate. These can be much,
451 much faster than other AES implementations.
453 o Minor bugfixes (0.2.2.x and earlier):
454 - Don't launch more than 10 service-side introduction-point circuits
455 for a hidden service in five minutes. Previously, we would consider
456 launching more introduction-point circuits if at least one second
457 had passed without any introduction-point circuits failing. Fixes
458 bug 4607; bugfix on 0.0.7pre1.
459 - Change the BridgePassword feature (part of the "bridge community"
460 design, which is not yet implemented) to use a time-independent
461 comparison. The old behavior might have allowed an adversary
462 to use timing to guess the BridgePassword value. Fixes bug 5543;
463 bugfix on 0.2.0.14-alpha.
464 - Enforce correct return behavior of tor_vsscanf() when the '%%'
465 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
466 - When sending an HTTP/1.1 proxy request, include a Host header.
467 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
468 - Don't log that we have "decided to publish new relay descriptor"
469 unless we are actually publishing a descriptor. Fixes bug 3942;
470 bugfix on 0.2.2.28-beta.
472 o Minor bugfixes (0.2.3.x):
473 - Fix a bug where a bridge authority crashes (on a failed assert)
474 if it has seen no directory requests when it's time to write
475 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
476 - Fix bug stomping on ORPort option NoListen and ignoring option
477 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
478 - In the testsuite, provide a large enough buffer in the tor_sscanf
479 unit test. Otherwise we'd overrun that buffer and crash during
480 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
482 - Make sure we create the keys directory if it doesn't exist and we're
483 about to store the dynamic Diffie-Hellman parameters. Fixes bug
484 5572; bugfix on 0.2.3.13-alpha.
485 - Fix a small memory leak when trying to decode incorrect base16
486 authenticator during SAFECOOKIE authentication. Found by
487 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
490 - Add more information to a log statement that might help track down
491 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
492 non-IP address" messages (or any Bug messages, for that matter!),
493 please let us know about it.
494 - Relays now understand an IPv6 address when they get one from a
495 directory server. Resolves ticket 4875.
496 - Resolve IPv6 addresses in bridge and entry statistics to country
497 code "??" which means we at least count them. Resolves ticket 5053;
498 improves on 0.2.3.9-alpha.
499 - Update to the April 3 2012 Maxmind GeoLite Country database.
500 - Begin a doc/state-contents.txt file to explain the contents of
501 the Tor state file. Fixes bug 2987.
503 o Default torrc changes:
504 - Stop listing "socksport 9050" in torrc.sample. We open a socks
505 port on 9050 by default anyway, so this should not change anything
507 - Stop mentioning the deprecated *ListenAddress options in
508 torrc.sample. Fixes bug 5438.
509 - Document unit of bandwidth related options in sample torrc.
513 - The "torify" script no longer supports the "tsocks" socksifier
514 tool, since tsocks doesn't support DNS and UDP right for Tor.
515 Everyone should be using torsocks instead. Fixes bugs 3530 and
516 5180. Based on a patch by "ugh".
519 - Change the symmetric cipher interface so that creating and
520 initializing a stream cipher are no longer separate functions.
521 - Remove all internal support for unpadded RSA. We never used it, and
522 it would be a bad idea to start.
525 Changes in version 0.2.3.13-alpha - 2012-03-26
526 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
527 in managed pluggable transports, as well as providing other cleanups
528 that get us closer to a release candidate.
530 o Directory authority changes:
531 - Change IP address for maatuska (v3 directory authority).
534 - Provide controllers with a safer way to implement the cookie
535 authentication mechanism. With the old method, if another locally
536 running program could convince a controller that it was the Tor
537 process, then that program could trick the contoller into telling
538 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
539 authentication method uses a challenge-response approach to prevent
540 this attack. Fixes bug 5185, implements proposal 193.
541 - Never use a bridge or a controller-supplied node as an exit, even
542 if its exit policy allows it. Found by wanoskarnet. Fixes bug
543 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
544 and 0.2.0.3-alpha (for bridge-purpose descriptors).
545 - Only build circuits if we have a sufficient threshold of the total
546 descriptors that are marked in the consensus with the "Exit"
547 flag. This mitigates an attack proposed by wanoskarnet, in which
548 all of a client's bridges collude to restrict the exit nodes that
549 the client knows about. Fixes bug 5343.
551 o Major bugfixes (on Tor 0.2.3.x):
552 - Avoid an assert when managed proxies like obfsproxy are configured,
553 and we receive HUP signals or setconf attempts too rapidly. This
554 situation happens most commonly when Vidalia tries to attach to
555 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
556 bugfix on 0.2.3.6-alpha.
557 - Fix a relay-side pluggable transports bug where managed proxies were
558 unreachable from the Internet, because Tor asked them to bind on
559 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
560 - Stop discarding command-line arguments when TestingTorNetwork
561 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
562 0.2.3.9-alpha, where task 4552 added support for two layers of
564 - Resume allowing the unit tests to run in gdb. This was accidentally
565 made impossible when the DisableDebuggerAttachment option was
566 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
567 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
568 0.2.3.11-alpha. Reported by Anthony G. Basile.
570 o Minor bugfixes (on 0.2.2.x and earlier):
571 - Ensure we don't cannibalize circuits that are longer than three hops
572 already, so we don't end up making circuits with 5 or more
573 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
574 0.1.0.1-rc which introduced cannibalization.
575 - Detect and reject certain misformed escape sequences in
576 configuration values. Previously, these values would cause us
577 to crash if received in a torrc file or over an authenticated
578 control port. Bug found by Esteban Manchado Velázquez, and
579 independently by Robert Connolly from Matta Consulting who further
580 noted that it allows a post-authentication heap overflow. Patch
581 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
582 bugfix on 0.2.0.16-alpha.
583 - Fix a compile warning when using the --enable-openbsd-malloc
584 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
585 - Directory caches no longer refuse to clean out descriptors because
586 of missing v2 networkstatus documents, unless they're configured
587 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
588 0.2.2.26-beta. Patch by Daniel Bryg.
589 - Update to the latest version of the tinytest unit testing framework.
590 This includes a couple of bugfixes that can be relevant for
591 running forked unit tests on Windows, and removes all reserved
594 o Minor bugfixes (on 0.2.3.x):
595 - On a failed pipe() call, don't leak file descriptors. Fixes bug
596 4296; bugfix on 0.2.3.1-alpha.
597 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
598 until after we have received a CERTS cell. Fixes bug 4361; bugfix
599 on 0.2.3.6-alpha. Patch by "frosty".
600 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
601 option, so that the IP stack doesn't decide to use it for IPv4
602 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
603 - Ensure that variables set in Tor's environment cannot override
604 environment variables that Tor passes to a managed
605 pluggable-transport proxy. Previously, Tor would pass every
606 variable in its environment to managed proxies along with the new
607 ones, in such a way that on many operating systems, the inherited
608 environment variables would override those which Tor tried to
609 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
610 bugfix on 0.2.3.9-alpha for Windows.
613 - A wide variety of new unit tests by Esteban Manchado Velázquez.
614 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
615 - Update to the March 6 2012 Maxmind GeoLite Country database.
618 Changes in version 0.2.3.12-alpha - 2012-02-13
619 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
620 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
621 when Tor is configured to use a pluggable transport like obfsproxy.
624 - Fix builds when the path to sed, openssl, or sha1sum contains
625 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
627 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
628 connections. This change should allow busy exit relays to stop
629 running out of available sockets as quickly. Fixes bug 4950;
630 bugfix on 0.2.2.26-beta.
631 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
632 would ask the bridge for microdescriptors, which are only supported
633 in 0.2.3.x, and then fail to bootstrap when it didn't get the
634 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
635 - Properly set up obfsproxy's environment when in managed mode. The
636 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
637 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
638 5076 and 5082; bugfix on 0.2.3.6-alpha.
641 - Use the dead_strip option when building Tor on OS X. This reduces
642 binary size by almost 19% when linking openssl and libevent
643 statically, which we do for Tor Browser Bundle.
644 - Fix broken URLs in the sample torrc file, and tell readers about
645 the OutboundBindAddress, ExitPolicyRejectPrivate, and
646 PublishServerDescriptor options. Addresses bug 4652.
647 - Update to the February 7 2012 Maxmind GeoLite Country database.
650 - Downgrade the "We're missing a certificate" message from notice
651 to info: people kept mistaking it for a real problem, whereas it
652 is seldom the problem even when we are failing to bootstrap. Fixes
653 bug 5067; bugfix on 0.2.0.10-alpha.
654 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
655 managed pluggable transport server proxy's environment.
656 Previously, we would put it there, even though Tor doesn't
657 implement an 'extended server port' yet, and even though Tor
658 almost certainly isn't listening at that address. For now, we set
659 it to an empty string to avoid crashing older obfsproxies. Bugfix
661 - Log the heartbeat message every HeartbeatPeriod seconds, not every
662 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
663 0.2.3.1-alpha. Bug reported by Scott Bennett.
664 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
665 bugfix on 0.2.3.11-alpha.
666 - Update "ClientOnly" man page entry to explain that there isn't
667 really any point to messing with it. Resolves ticket 5005.
668 - Use the correct CVE number for CVE-2011-4576 in our comments and
669 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
672 o Code simplifications and refactoring:
673 - Use the _WIN32 macro throughout our code to detect Windows.
674 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
678 Changes in version 0.2.3.11-alpha - 2012-01-22
679 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
680 the last step of the plan to limit maximum circuit length, includes
681 a wide variety of hidden service performance and correctness fixes,
682 works around an OpenSSL security flaw if your distro is too stubborn
683 to upgrade, and fixes a bunch of smaller issues.
686 - Now that Tor 0.2.0.x is completely deprecated, enable the final
687 part of "Proposal 110: Avoiding infinite length circuits" by
688 refusing all circuit-extend requests that do not use a relay_early
689 cell. This change helps Tor resist a class of denial-of-service
690 attacks by limiting the maximum circuit length.
691 - Adjust the number of introduction points that a hidden service
692 will try to maintain based on how long its introduction points
693 remain in use and how many introductions they handle. Fixes
695 - Try to use system facilities for enumerating local interface
696 addresses, before falling back to our old approach (which was
697 binding a UDP socket, and calling getsockname() on it). That
698 approach was scaring OS X users whose draconian firewall
699 software warned about binding to UDP sockets, regardless of
700 whether packets were sent. Now we try to use getifaddrs(),
701 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
702 system supports. Resolves ticket 1827.
704 o Major security workaround:
705 - When building or running with any version of OpenSSL earlier
706 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
707 versions have a bug (CVE-2011-4576) in which their block cipher
708 padding includes uninitialized data, potentially leaking sensitive
709 information to any peer with whom they make a SSLv3 connection. Tor
710 does not use SSL v3 by default, but a hostile client or server
711 could force an SSLv3 connection in order to gain information that
712 they shouldn't have been able to get. The best solution here is to
713 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
714 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
715 to make sure that the bug can't happen.
718 - Fix the SOCKET_OK test that we use to tell when socket
719 creation fails so that it works on Win64. Fixes part of bug 4533;
720 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
721 - Correct our replacements for the timeradd() and timersub() functions
722 on platforms that lack them (for example, Windows). The timersub()
723 function is used when expiring circuits, while timeradd() is
724 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
725 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
726 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
727 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
728 bug at runtime, not compile time, because some distributions hack
729 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
730 on 0.2.3.9-alpha. Found by Pascal.
732 o Minor features (controller):
733 - Use absolute path names when reporting the torrc filename in the
734 control protocol, so a controller can more easily find the torrc
735 file. Resolves bug 1101.
736 - Extend the control protocol to report flags that control a circuit's
737 path selection in CIRC events and in replies to 'GETINFO
738 circuit-status'. Implements part of ticket 2411.
739 - Extend the control protocol to report the hidden service address
740 and current state of a hidden-service-related circuit in CIRC
741 events and in replies to 'GETINFO circuit-status'. Implements part
743 - When reporting the path to the cookie file to the controller,
744 give an absolute path. Resolves ticket 4881.
745 - Allow controllers to request an event notification whenever a
746 circuit is cannibalized or its purpose is changed. Implements
748 - Include the creation time of a circuit in CIRC and CIRC2
749 control-port events and the list produced by the 'GETINFO
750 circuit-status' control-port command.
752 o Minor features (directory authorities):
753 - Directory authorities now reject versions of Tor older than
754 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
755 inclusive. These versions accounted for only a small fraction of
756 the Tor network, and have numerous known security issues. Resolves
758 - Authority operators can now vote for all relays in a given
759 set of countries to be BadDir/BadExit/Invalid/Rejected.
760 - Provide two consensus parameters (FastFlagMinThreshold and
761 FastFlagMaxThreshold) to control the range of allowable bandwidths
762 for the Fast directory flag. These allow authorities to run
763 experiments on appropriate requirements for being a "Fast" node.
764 The AuthDirFastGuarantee config value still applies.
765 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
766 directory authority option (introduced in Tor 0.2.2.34).
768 o Minor features (other):
769 - Don't disable the DirPort when we cannot exceed our AccountingMax
770 limit during this interval because the effective bandwidthrate is
771 low enough. This is useful in a situation where AccountMax is only
772 used as an additional safeguard or to provide statistics.
773 - Prepend an informative header to generated dynamic_dh_params files.
774 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
775 EntryNodes will have no effect. Resolves issue 2571.
776 - Log more useful messages when we fail to disable debugger
778 - Log which authority we're missing votes from when we go to fetch
779 them from the other auths.
780 - Log (at debug level) whenever a circuit's purpose is changed.
781 - Add missing documentation for the MaxClientCircuitsPending,
782 UseMicrodescriptors, UserspaceIOCPBuffers, and
783 _UseFilteringSSLBufferevents options, all introduced during
785 - Update to the January 3 2012 Maxmind GeoLite Country database.
787 o Minor bugfixes (hidden services):
788 - Don't close hidden service client circuits which have almost
789 finished connecting to their destination when they reach
790 the normal circuit-build timeout. Previously, we would close
791 introduction circuits which are waiting for an acknowledgement
792 from the introduction point, and rendezvous circuits which have
793 been specified in an INTRODUCE1 cell sent to a hidden service,
794 after the normal CBT. Now, we mark them as 'timed out', and launch
795 another rendezvous attempt in parallel. This behavior change can
796 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
797 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
798 - Don't close hidden-service-side rendezvous circuits when they
799 reach the normal circuit-build timeout. This behaviour change can
800 be disabled using the new
801 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
802 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
803 - Make sure we never mark the wrong rendezvous circuit as having
804 had its introduction cell acknowleged by the introduction-point
805 relay. Previously, when we received an INTRODUCE_ACK cell on a
806 client-side hidden-service introduction circuit, we might have
807 marked a rendezvous circuit other than the one we specified in
808 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
809 a warning message and interfered with the hidden service
810 connection-establishment process. Fixes bug 4759; bugfix on
811 0.2.3.3-alpha, when we added the stream-isolation feature which
812 might cause Tor to open multiple rendezvous circuits for the same
814 - Don't trigger an assertion failure when we mark a new client-side
815 hidden-service introduction circuit for close during the process
816 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
819 o Minor bugfixes (log messages):
820 - Correctly spell "connect" in a log message on failure to create a
821 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
823 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
824 Fixes bug 4856; bugfix on Tor 0.0.6.
825 - Fix the log message describing how we work around discovering
826 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
827 4837; bugfix on 0.2.2.9-alpha.
828 - When logging about a disallowed .exit name, do not also call it
829 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
831 o Minor bugfixes (build fixes):
832 - During configure, detect when we're building with clang version
833 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
834 CFLAGS. clang doesn't support them yet.
835 - During configure, search for library containing cos function as
836 libm lives in libcore on some platforms (BeOS/Haiku). Linking
837 against libm was hard-coded before. Fixes the first part of bug
838 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
840 - Detect attempts to build Tor on (as yet hypothetical) versions
841 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
842 fix for bug 4533. Bugfix on 0.2.2.28-beta.
843 - Preprocessor directives should not be put inside the arguments
844 of a macro. This would break compilation with GCC releases prior
845 to version 3.3. We would never recommend such an old GCC version,
846 but it is apparently required for binary compatibility on some
847 platforms (namely, certain builds of Haiku). Fixes the other part
848 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
851 o Minor bugfixes (other):
852 - Older Linux kernels erroneously respond to strange nmap behavior
853 by having accept() return successfully with a zero-length
854 socket. When this happens, just close the connection. Previously,
855 we would try harder to learn the remote address: but there was
856 no such remote address to learn, and our method for trying to
857 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
858 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
859 - Fix null-pointer access that could occur if TLS allocation failed.
860 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
861 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
862 accidentally been reverted.
863 - Fix our implementation of crypto_random_hostname() so it can't
864 overflow on ridiculously large inputs. (No Tor version has ever
865 provided this kind of bad inputs, but let's be correct in depth.)
866 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
867 - Find more places in the code that should have been testing for
868 invalid sockets using the SOCKET_OK macro. Required for a fix
869 for bug 4533. Bugfix on 0.2.2.28-beta.
870 - Fix an assertion failure when, while running with bufferevents, a
871 connection finishes connecting after it is marked for close, but
872 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
873 - test_util_spawn_background_ok() hardcoded the expected value
874 for ENOENT to 2. This isn't portable as error numbers are
875 platform specific, and particularly the hurd has ENOENT at
876 0x40000002. Construct expected string at runtime, using the correct
877 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
878 - Reject attempts to disable DisableDebuggerAttachment while Tor is
879 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
880 - Use an appropriate-width type for sockets in tor-fw-helper on
881 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
884 - When sending or relaying a RELAY_EARLY cell, we used to convert
885 it to a RELAY cell if the connection was using the v1 link
886 protocol. This was a workaround for older versions of Tor, which
887 didn't handle RELAY_EARLY cells properly. Now that all supported
888 versions can handle RELAY_EARLY cells, and now that we're enforcing
889 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
890 remove this workaround. Addresses bug 4786.
892 o Code simplifications and refactoring:
893 - Use OpenSSL's built-in SSL_state_string_long() instead of our
894 own homebrewed ssl_state_to_string() replacement. Patch from
895 Emile Snyder. Fixes bug 4653.
896 - Use macros to indicate OpenSSL versions, so we don't need to worry
897 about accidental hexadecimal bit shifts.
898 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
900 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
901 - Use the smartlist_add_asprintf() alias more consistently.
902 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
903 invalid value, rather than just -1.
904 - Rename a handful of old identifiers, mostly related to crypto
905 structures and crypto functions. By convention, our "create an
906 object" functions are called "type_new()", our "free an object"
907 functions are called "type_free()", and our types indicate that
908 they are types only with a final "_t". But a handful of older
909 types and functions broke these rules, with function names like
910 "type_create" or "subsystem_op_type", or with type names like
914 Changes in version 0.2.3.10-alpha - 2011-12-16
915 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
916 Tor's buffers code. Absolutely everybody should upgrade.
918 The bug relied on an incorrect calculation when making data continuous
919 in one of our IO buffers, if the first chunk of the buffer was
920 misaligned by just the wrong amount. The miscalculation would allow an
921 attacker to overflow a piece of heap-allocated memory. To mount this
922 attack, the attacker would need to either open a SOCKS connection to
923 Tor's SocksPort (usually restricted to localhost), or target a Tor
924 instance configured to make its connections through a SOCKS proxy
925 (which Tor does not do by default).
927 Good security practice requires that all heap-overflow bugs should be
928 presumed to be exploitable until proven otherwise, so we are treating
929 this as a potential code execution attack. Please upgrade immediately!
930 This bug does not affect bufferevents-based builds of Tor. Special
931 thanks to "Vektor" for reporting this issue to us!
933 This release also contains a few minor bugfixes for issues discovered
937 - Fix a heap overflow bug that could occur when trying to pull
938 data into the first chunk of a buffer, when that chunk had
939 already had some data drained from it. Fixes CVE-2011-2778;
940 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
943 - If we can't attach streams to a rendezvous circuit when we
944 finish connecting to a hidden service, clear the rendezvous
945 circuit's stream-isolation state and try to attach streams
946 again. Previously, we cleared rendezvous circuits' isolation
947 state either too early (if they were freshly built) or not at all
948 (if they had been built earlier and were cannibalized). Bugfix on
949 0.2.3.3-alpha; fixes bug 4655.
950 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
951 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
952 - Fix an assertion failure when a relay with accounting enabled
953 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
956 - Update to the December 6 2011 Maxmind GeoLite Country database.
959 Changes in version 0.2.2.35 - 2011-12-16
960 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
961 buffers code. Absolutely everybody should upgrade.
963 The bug relied on an incorrect calculation when making data continuous
964 in one of our IO buffers, if the first chunk of the buffer was
965 misaligned by just the wrong amount. The miscalculation would allow an
966 attacker to overflow a piece of heap-allocated memory. To mount this
967 attack, the attacker would need to either open a SOCKS connection to
968 Tor's SocksPort (usually restricted to localhost), or target a Tor
969 instance configured to make its connections through a SOCKS proxy
970 (which Tor does not do by default).
972 Good security practice requires that all heap-overflow bugs should be
973 presumed to be exploitable until proven otherwise, so we are treating
974 this as a potential code execution attack. Please upgrade immediately!
975 This bug does not affect bufferevents-based builds of Tor. Special
976 thanks to "Vektor" for reporting this issue to us!
978 Tor 0.2.2.35 also fixes several bugs in previous versions, including
979 crash bugs for unusual configurations, and a long-term bug that
980 would prevent Tor from starting on Windows machines with draconian
983 With this release, we remind everyone that 0.2.0.x has reached its
984 formal end-of-life. Those Tor versions have many known flaws, and
985 nobody should be using them. You should upgrade -- ideally to the
986 0.2.2.x series. If you're using a Linux or BSD and its packages are
987 obsolete, stop using those packages and upgrade anyway.
989 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
990 longer receive support after some time in early 2012.
993 - Fix a heap overflow bug that could occur when trying to pull
994 data into the first chunk of a buffer, when that chunk had
995 already had some data drained from it. Fixes CVE-2011-2778;
996 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
997 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
998 that it doesn't attempt to allocate a socketpair. This could cause
999 some problems on Windows systems with overzealous firewalls. Fix for
1000 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1002 - If we mark an OR connection for close based on a cell we process,
1003 don't process any further cells on it. We already avoid further
1004 reads on marked-for-close connections, but now we also discard the
1005 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1006 which was the first version where we might mark a connection for
1007 close based on processing a cell on it.
1008 - Correctly sanity-check that we don't underflow on a memory
1009 allocation (and then assert) for hidden service introduction
1010 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1011 bugfix on 0.2.1.5-alpha.
1012 - Fix a memory leak when we check whether a hidden service
1013 descriptor has any usable introduction points left. Fixes bug
1014 4424. Bugfix on 0.2.2.25-alpha.
1015 - Don't crash when we're running as a relay and don't have a GeoIP
1016 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
1017 we've had in the 0.2.3.x branch already.
1018 - When running as a client, do not print a misleading (and plain
1019 wrong) log message that we're collecting "directory request"
1020 statistics: clients don't collect statistics. Also don't create a
1021 useless (because empty) stats file in the stats/ directory. Fixes
1022 bug 4353; bugfix on 0.2.2.34.
1025 - Detect failure to initialize Libevent. This fix provides better
1026 detection for future instances of bug 4457.
1027 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1028 function. This was eating up hideously large amounts of time on some
1029 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1030 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1031 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1033 - Don't warn about unused log_mutex in log.c when building with
1034 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1035 0.1.0.6-rc which introduced --disable-threads.
1036 - When configuring, starting, or stopping an NT service, stop
1037 immediately after the service configuration attempt has succeeded
1038 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1039 - When sending a NETINFO cell, include the original address
1040 received for the other side, not its canonical address. Found
1041 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1042 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
1043 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1044 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1045 occurred when a client tried to fetch a descriptor for a bridge
1046 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1047 - Backport fixes for a pair of compilation warnings on Windows.
1048 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
1049 - If we had ever tried to call tor_addr_to_str on an address of
1050 unknown type, we would have done a strdup on an uninitialized
1051 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1052 Reported by "troll_un".
1053 - Correctly detect and handle transient lookup failures from
1054 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1055 Reported by "troll_un".
1056 - Fix null-pointer access that could occur if TLS allocation failed.
1057 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1058 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1059 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1062 - Add two new config options for directory authorities:
1063 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
1064 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
1065 that is always sufficient to satisfy the bandwidth requirement for
1066 the Guard flag. Now it will be easier for researchers to simulate
1067 Tor networks with different values. Resolves ticket 4484.
1068 - When Tor ignores a hidden service specified in its configuration,
1069 include the hidden service's directory in the warning message.
1070 Previously, we would only tell the user that some hidden service
1071 was ignored. Bugfix on 0.0.6; fixes bug 4426.
1072 - Update to the December 6 2011 Maxmind GeoLite Country database.
1074 o Packaging changes:
1075 - Make it easier to automate expert package builds on Windows,
1076 by removing an absolute path from makensis.exe command.
1079 Changes in version 0.2.3.9-alpha - 2011-12-08
1080 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
1081 a "DisableNetwork" security feature that bundles can use to avoid
1082 touching the network until bridges are configured, moves forward on
1083 the pluggable transport design, fixes a flaw in the hidden service
1084 design that unnecessarily prevented clients with wrong clocks from
1085 reaching hidden services, and fixes a wide variety of other issues.
1088 - Clients can now connect to private bridges over IPv6. Bridges
1089 still need at least one IPv4 address in order to connect to
1090 other relays. Note that we don't yet handle the case where the
1091 user has two bridge lines for the same bridge (one IPv4, one
1092 IPv6). Implements parts of proposal 186.
1093 - New "DisableNetwork" config option to prevent Tor from launching any
1094 connections or accepting any connections except on a control port.
1095 Bundles and controllers can set this option before letting Tor talk
1096 to the rest of the network, for example to prevent any connections
1097 to a non-bridge address. Packages like Orbot can also use this
1098 option to instruct Tor to save power when the network is off.
1099 - Clients and bridges can now be configured to use a separate
1100 "transport" proxy. This approach makes the censorship arms race
1101 easier by allowing bridges to use protocol obfuscation plugins. It
1102 implements the "managed proxy" part of proposal 180 (ticket 3472).
1103 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
1104 implementation. It makes AES_CTR about 7% faster than our old one
1105 (which was about 10% faster than the one OpenSSL used to provide).
1106 Resolves ticket 4526.
1107 - Add a "tor2web mode" for clients that want to connect to hidden
1108 services non-anonymously (and possibly more quickly). As a safety
1109 measure to try to keep users from turning this on without knowing
1110 what they are doing, tor2web mode must be explicitly enabled at
1111 compile time, and a copy of Tor compiled to run in tor2web mode
1112 cannot be used as a normal Tor client. Implements feature 2553.
1113 - Add experimental support for running on Windows with IOCP and no
1114 kernel-space socket buffers. This feature is controlled by a new
1115 "UserspaceIOCPBuffers" config option (off by default), which has
1116 no effect unless Tor has been built with support for bufferevents,
1117 is running on Windows, and has enabled IOCP. This may, in the long
1118 run, help solve or mitigate bug 98.
1119 - Use a more secure consensus parameter voting algorithm. Now at
1120 least three directory authorities or a majority of them must
1121 vote on a given parameter before it will be included in the
1122 consensus. Implements proposal 178.
1125 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
1126 They used to check that the timestamp was within 30 minutes
1127 of their system clock, so they could cap the size of their
1128 replay-detection cache, but that approach unnecessarily refused
1129 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
1130 the v3 intro-point protocol (the first one which sent a timestamp
1131 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
1132 - Only use the EVP interface when AES acceleration is enabled,
1133 to avoid a 5-7% performance regression. Resolves issue 4525;
1134 bugfix on 0.2.3.8-alpha.
1136 o Privacy/anonymity features (bridge detection):
1137 - Make bridge SSL certificates a bit more stealthy by using random
1138 serial numbers, in the same fashion as OpenSSL when generating
1139 self-signed certificates. Implements ticket 4584.
1140 - Introduce a new config option "DynamicDHGroups", enabled by
1141 default, which provides each bridge with a unique prime DH modulus
1142 to be used during SSL handshakes. This option attempts to help
1143 against censors who might use the Apache DH modulus as a static
1144 identifier for bridges. Addresses ticket 4548.
1146 o Minor features (new/different config options):
1147 - New configuration option "DisableDebuggerAttachment" (on by default)
1148 to prevent basic debugging attachment attempts by other processes.
1149 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
1150 - Allow MapAddress directives to specify matches against super-domains,
1151 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
1152 Implements issue 933.
1153 - Slightly change behavior of "list" options (that is, config
1154 options that can appear more than once) when they appear both in
1155 torrc and on the command line. Previously, the command-line options
1156 would be appended to the ones from torrc. Now, the command-line
1157 options override the torrc options entirely. This new behavior
1158 allows the user to override list options (like exit policies and
1159 ports to listen on) from the command line, rather than simply
1160 appending to the list.
1161 - You can get the old (appending) command-line behavior for "list"
1162 options by prefixing the option name with a "+".
1163 - You can remove all the values for a "list" option from the command
1164 line without adding any new ones by prefixing the option name
1166 - Add experimental support for a "defaults" torrc file to be parsed
1167 before the regular torrc. Torrc options override the defaults file's
1168 options in the same way that the command line overrides the torrc.
1169 The SAVECONF controller command saves only those options which
1170 differ between the current configuration and the defaults file. HUP
1171 reloads both files. (Note: This is an experimental feature; its
1172 behavior will probably be refined in future 0.2.3.x-alpha versions
1173 to better meet packagers' needs.) Implements task 4552.
1176 - Try to make the introductory warning message that Tor prints on
1177 startup more useful for actually finding help and information.
1178 Resolves ticket 2474.
1179 - Running "make version" now displays the version of Tor that
1180 we're about to build. Idea from katmagic; resolves issue 4400.
1181 - Expire old or over-used hidden service introduction points.
1182 Required by fix for bug 3460.
1183 - Move the replay-detection cache for the RSA-encrypted parts of
1184 INTRODUCE2 cells to the introduction point data structures.
1185 Previously, we would use one replay-detection cache per hidden
1186 service. Required by fix for bug 3460.
1187 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
1188 public key replay-detection cache from 60 minutes to 5 minutes. This
1189 replay-detection cache is now used only to detect multiple
1190 INTRODUCE2 cells specifying the same rendezvous point, so we can
1191 avoid launching multiple simultaneous attempts to connect to it.
1193 o Minor bugfixes (on Tor 0.2.2.x and earlier):
1194 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1195 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1197 - Fix a minor formatting issue in one of tor-gencert's error messages.
1199 - Prevent a false positive from the check-spaces script, by disabling
1200 the "whitespace between function name and (" check for functions
1202 - Fix a log message suggesting that people contact a non-existent
1203 email address. Fixes bug 3448.
1204 - Fix null-pointer access that could occur if TLS allocation failed.
1205 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1206 - Report a real bootstrap problem to the controller on router
1207 identity mismatch. Previously we just said "foo", which probably
1208 made a lot of sense at the time. Fixes bug 4169; bugfix on
1210 - If we had ever tried to call tor_addr_to_str() on an address of
1211 unknown type, we would have done a strdup() on an uninitialized
1212 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1213 Reported by "troll_un".
1214 - Correctly detect and handle transient lookup failures from
1215 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1216 Reported by "troll_un".
1217 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1218 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1219 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
1220 bug 4532; found by "troll_un".
1222 o Minor bugfixes (on Tor 0.2.3.x):
1223 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
1225 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
1226 circuit for use as a hidden service client's rendezvous point.
1227 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
1228 with help from wanoskarnet.
1229 - Restore behavior of overriding SocksPort, ORPort, and similar
1230 options from the command line. Bugfix on 0.2.3.3-alpha.
1233 - Properly handle the case where the build-tree is not the same
1234 as the source tree when generating src/common/common_sha1.i,
1235 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
1236 bugfix on 0.2.0.1-alpha.
1238 o Code simplifications, cleanups, and refactorings:
1239 - Remove the pure attribute from all functions that used it
1240 previously. In many cases we assigned it incorrectly, because the
1241 functions might assert or call impure functions, and we don't have
1242 evidence that keeping the pure attribute is worthwhile. Implements
1243 changes suggested in ticket 4421.
1244 - Remove some dead code spotted by coverity. Fixes cid 432.
1245 Bugfix on 0.2.3.1-alpha, closes bug 4637.
1248 Changes in version 0.2.3.8-alpha - 2011-11-22
1249 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
1250 socketpair-related bug that has been bothering Windows users. It adds
1251 support to serve microdescriptors to controllers, so Vidalia's network
1252 map can resume listing relays (once Vidalia implements its side),
1253 and adds better support for hardware AES acceleration. Finally, it
1254 starts the process of adjusting the bandwidth cutoff for getting the
1255 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
1256 that tiny relays harm performance more than they help network capacity.
1259 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1260 that it doesn't attempt to allocate a socketpair. This could cause
1261 some problems on Windows systems with overzealous firewalls. Fix for
1262 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1264 - Correctly sanity-check that we don't underflow on a memory
1265 allocation (and then assert) for hidden service introduction
1266 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1267 bugfix on 0.2.1.5-alpha.
1268 - Remove the artificially low cutoff of 20KB to guarantee the Fast
1269 flag. In the past few years the average relay speed has picked
1270 up, and while the "top 7/8 of the network get the Fast flag" and
1271 "all relays with 20KB or more of capacity get the Fast flag" rules
1272 used to have the same result, now the top 7/8 of the network has
1273 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
1274 - Fix a rare assertion failure when checking whether a v0 hidden
1275 service descriptor has any usable introduction points left, and
1276 we don't have enough information to build a circuit to the first
1277 intro point named in the descriptor. The HS client code in
1278 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
1279 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
1280 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
1281 - Make bridge authorities not crash when they are asked for their own
1282 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
1283 - When running as a client, do not print a misleading (and plain
1284 wrong) log message that we're collecting "directory request"
1285 statistics: clients don't collect statistics. Also don't create a
1286 useless (because empty) stats file in the stats/ directory. Fixes
1287 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
1290 - Allow Tor controllers like Vidalia to obtain the microdescriptor
1291 for a relay by identity digest or nickname. Previously,
1292 microdescriptors were only available by their own digests, so a
1293 controller would have to ask for and parse the whole microdescriptor
1294 consensus in order to look up a single relay's microdesc. Fixes
1295 bug 3832; bugfix on 0.2.3.1-alpha.
1296 - Use OpenSSL's EVP interface for AES encryption, so that all AES
1297 operations can use hardware acceleration (if present). Resolves
1300 o Minor bugfixes (on 0.2.2.x and earlier):
1301 - Detect failure to initialize Libevent. This fix provides better
1302 detection for future instances of bug 4457.
1303 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1304 function. This was eating up hideously large amounts of time on some
1305 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1306 - Don't warn about unused log_mutex in log.c when building with
1307 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1308 0.1.0.6-rc which introduced --disable-threads.
1309 - Allow manual 'authenticate' commands to the controller interface
1310 from netcat (nc) as well as telnet. We were rejecting them because
1311 they didn't come with the expected whitespace at the end of the
1312 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
1313 - Fix some (not actually triggerable) buffer size checks in usage of
1314 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
1316 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
1317 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
1318 - When configuring, starting, or stopping an NT service, stop
1319 immediately after the service configuration attempt has succeeded
1320 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1321 - When sending a NETINFO cell, include the original address
1322 received for the other side, not its canonical address. Found
1323 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1324 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
1325 can pick them up when the tests aren't disabled. Bugfix on
1326 0.2.2.4-alpha which introduced tinytest.
1327 - Fix a memory leak when we check whether a hidden service
1328 descriptor has any usable introduction points left. Fixes bug
1329 4424. Bugfix on 0.2.2.25-alpha.
1330 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1331 occurred when a client tried to fetch a descriptor for a bridge
1332 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1334 o Minor bugfixes (on 0.2.3.x):
1335 - Make util unit tests build correctly with MSVC. Bugfix on
1336 0.2.3.3-alpha. Patch by Gisle Vanem.
1337 - Successfully detect AUTH_CHALLENGE cells with no recognized
1338 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
1340 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
1341 it should still send a NETINFO cell to allow the connection to
1342 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
1344 - Log less loudly when we get an invalid authentication certificate
1345 from a source other than a directory authority: it's not unusual
1346 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
1348 - Tolerate servers with more clock skew in their authentication
1349 certificates than previously. Fixes bug 4371; bugfix on
1351 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
1352 on 0.2.3.4-alpha and 0.2.3.6-alpha.
1355 - Add two new config options for directory authorities:
1356 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
1357 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
1358 that is always sufficient to satisfy the bandwidth requirement for
1359 the Guard flag. Now it will be easier for researchers to simulate
1360 Tor networks with different values. Resolves ticket 4484.
1361 - When Tor ignores a hidden service specified in its configuration,
1362 include the hidden service's directory in the warning message.
1363 Previously, we would only tell the user that some hidden service
1364 was ignored. Bugfix on 0.0.6; fixes bug 4426.
1365 - When we fail to initialize Libevent, retry with IOCP disabled so we
1366 don't need to turn on multi-threading support in Libevent, which in
1367 turn requires a working socketpair(). This is a workaround for bug
1368 4457, which affects Libevent versions from 2.0.1-alpha through
1370 - Detect when we try to build on a platform that doesn't define
1371 AF_UNSPEC to 0. We don't work there, so refuse to compile.
1372 - Update to the November 1 2011 Maxmind GeoLite Country database.
1374 o Packaging changes:
1375 - Make it easier to automate expert package builds on Windows,
1376 by removing an absolute path from makensis.exe command.
1378 o Code simplifications and refactoring:
1379 - Remove some redundant #include directives throughout the code.
1380 Patch from Andrea Gelmini.
1381 - Unconditionally use OpenSSL's AES implementation instead of our
1382 old built-in one. OpenSSL's AES has been better for a while, and
1383 relatively few servers should still be on any version of OpenSSL
1384 that doesn't have good optimized assembly AES.
1385 - Use the name "CERTS" consistently to refer to the new cell type;
1386 we were calling it CERT in some places and CERTS in others.
1389 - Numerous new unit tests for functions in util.c and address.c by
1391 - The long-disabled benchmark tests are now split into their own
1392 ./src/test/bench binary.
1393 - The benchmark tests can now use more accurate timers than
1394 gettimeofday() when such timers are available.
1397 Changes in version 0.2.3.7-alpha - 2011-10-30
1398 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
1399 the new v3 handshake. It also resolves yet another bridge address
1403 - If we mark an OR connection for close based on a cell we process,
1404 don't process any further cells on it. We already avoid further
1405 reads on marked-for-close connections, but now we also discard the
1406 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1407 which was the first version where we might mark a connection for
1408 close based on processing a cell on it.
1409 - Fix a double-free bug that would occur when we received an invalid
1410 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
1411 bugfix on 0.2.3.6-alpha.
1412 - Bridges no longer include their address in NETINFO cells on outgoing
1413 OR connections, to allow them to blend in better with clients.
1414 Removes another avenue for enumerating bridges. Reported by
1415 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
1416 cells were introduced.
1419 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
1420 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1423 Changes in version 0.2.3.6-alpha - 2011-10-26
1424 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
1425 anonymity vulnerability where an attacker can deanonymize Tor
1426 users. Everybody should upgrade.
1428 This release also features support for a new v3 connection handshake
1429 protocol, and fixes to make hidden service connections more robust.
1432 - Implement a new handshake protocol (v3) for authenticating Tors to
1433 each other over TLS. It should be more resistant to fingerprinting
1434 than previous protocols, and should require less TLS hacking for
1435 future Tor implementations. Implements proposal 176.
1436 - Allow variable-length padding cells to disguise the length of
1437 Tor's TLS records. Implements part of proposal 184.
1439 o Privacy/anonymity fixes (clients):
1440 - Clients and bridges no longer send TLS certificate chains on
1441 outgoing OR connections. Previously, each client or bridge would
1442 use the same cert chain for all outgoing OR connections until
1443 its IP address changes, which allowed any relay that the client
1444 or bridge contacted to determine which entry guards it is using.
1445 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1446 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1447 no longer considers that connection as suitable for satisfying a
1448 circuit EXTEND request. Now relays can protect clients from the
1449 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1450 - Directory authorities no longer assign the Guard flag to relays
1451 that haven't upgraded to the above "refuse EXTEND requests
1452 to client connections" fix. Now directory authorities can
1453 protect clients from the CVE-2011-2768 issue even if neither
1454 the clients nor the relays have upgraded yet. There's a new
1455 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1456 to let us transition smoothly, else tomorrow there would be no
1459 o Major bugfixes (hidden services):
1460 - Improve hidden service robustness: when an attempt to connect to
1461 a hidden service ends, be willing to refetch its hidden service
1462 descriptors from each of the HSDir relays responsible for them
1463 immediately. Previously, we would not consider refetching the
1464 service's descriptors from each HSDir for 15 minutes after the last
1465 fetch, which was inconvenient if the hidden service was not running
1466 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
1467 - When one of a hidden service's introduction points appears to be
1468 unreachable, stop trying it. Previously, we would keep trying
1469 to build circuits to the introduction point until we lost the
1470 descriptor, usually because the user gave up and restarted Tor.
1471 Partly fixes bug 3825.
1472 - Don't launch a useless circuit after failing to use one of a
1473 hidden service's introduction points. Previously, we would
1474 launch a new introduction circuit, but not set the hidden service
1475 which that circuit was intended to connect to, so it would never
1476 actually be used. A different piece of code would then create a
1477 new introduction circuit correctly. Bug reported by katmagic and
1478 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1480 o Major bugfixes (other):
1481 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1482 that they initiated. Relays could distinguish incoming bridge
1483 connections from client connections, creating another avenue for
1484 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1485 Found by "frosty_un".
1486 - Don't update the AccountingSoftLimitHitAt state file entry whenever
1487 tor gets started. This prevents a wrong average bandwidth
1488 estimate, which would cause relays to always start a new accounting
1489 interval at the earliest possible moment. Fixes bug 2003; bugfix
1490 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
1491 immensely in tracking this bug down.
1492 - Fix a crash bug when changing node restrictions while a DNS lookup
1493 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
1496 o Minor bugfixes (on 0.2.2.x and earlier):
1497 - When a hidden service turns an extra service-side introduction
1498 circuit into a general-purpose circuit, free the rend_data and
1499 intro_key fields first, so we won't leak memory if the circuit
1500 is cannibalized for use as another service-side introduction
1501 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
1502 - Rephrase the log message emitted if the TestSocks check is
1503 successful. Patch from Fabian Keil; fixes bug 4094.
1504 - Bridges now skip DNS self-tests, to act a little more stealthily.
1505 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
1506 bridges. Patch by "warms0x".
1507 - Remove a confusing dollar sign from the example fingerprint in the
1508 man page, and also make the example fingerprint a valid one. Fixes
1509 bug 4309; bugfix on 0.2.1.3-alpha.
1510 - Fix internal bug-checking logic that was supposed to catch
1511 failures in digest generation so that it will fail more robustly
1512 if we ask for a nonexistent algorithm. Found by Coverity Scan.
1513 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
1514 - Report any failure in init_keys() calls launched because our
1515 IP address has changed. Spotted by Coverity Scan. Bugfix on
1516 0.1.1.4-alpha; fixes CID 484.
1518 o Minor bugfixes (on 0.2.3.x):
1519 - Fix a bug in configure.in that kept it from building a configure
1520 script with autoconf versions earlier than 2.61. Fixes bug 2430;
1521 bugfix on 0.2.3.1-alpha.
1522 - Don't warn users that they are exposing a client port to the
1523 Internet if they have specified an RFC1918 address. Previously,
1524 we would warn if the user had specified any non-loopback
1525 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
1526 - Fix memory leaks in the failing cases of the new SocksPort and
1527 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
1528 fixes coverity CIDs 485, 486, and 487.
1531 - When a hidden service's introduction point times out, consider
1532 trying it again during the next attempt to connect to the
1533 HS. Previously, we would not try it again unless a newly fetched
1534 descriptor contained it. Required by fixes for bugs 1297 and 3825.
1535 - The next version of Windows will be called Windows 8, and it has
1536 a major version of 6, minor version of 2. Correctly identify that
1537 version instead of calling it "Very recent version". Resolves
1538 ticket 4153; reported by funkstar.
1539 - The Bridge Authority now writes statistics on how many bridge
1540 descriptors it gave out in total, and how many unique descriptors
1541 it gave out. It also lists how often the most and least commonly
1542 fetched descriptors were given out, as well as the median and
1543 25th/75th percentile. Implements tickets 4200 and 4294.
1544 - Update to the October 4 2011 Maxmind GeoLite Country database.
1546 o Code simplifications and refactoring:
1547 - Remove some old code to remember statistics about which descriptors
1548 we've served as a directory mirror. The feature wasn't used and
1549 is outdated now that microdescriptors are around.
1550 - Rename Tor functions that turn strings into addresses, so that
1551 "parse" indicates that no hostname resolution occurs, and
1552 "lookup" indicates that hostname resolution may occur. This
1553 should help prevent mistakes in the future. Fixes bug 3512.
1556 Changes in version 0.2.2.34 - 2011-10-26
1557 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
1558 can deanonymize Tor users. Everybody should upgrade.
1560 The attack relies on four components: 1) Clients reuse their TLS cert
1561 when talking to different relays, so relays can recognize a user by
1562 the identity key in her cert. 2) An attacker who knows the client's
1563 identity key can probe each guard relay to see if that identity key
1564 is connected to that guard relay right now. 3) A variety of active
1565 attacks in the literature (starting from "Low-Cost Traffic Analysis
1566 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
1567 discover the guard relays that a Tor user visiting the website is using.
1568 4) Clients typically pick three guards at random, so the set of guards
1569 for a given user could well be a unique fingerprint for her. This
1570 release fixes components #1 and #2, which is enough to block the attack;
1571 the other two remain as open research problems. Special thanks to
1572 "frosty_un" for reporting the issue to us!
1574 Clients should upgrade so they are no longer recognizable by the TLS
1575 certs they present. Relays should upgrade so they no longer allow a
1576 remote attacker to probe them to test whether unpatched clients are
1577 currently connected to them.
1579 This release also fixes several vulnerabilities that allow an attacker
1580 to enumerate bridge relays. Some bridge enumeration attacks still
1581 remain; see for example proposal 188.
1583 o Privacy/anonymity fixes (clients):
1584 - Clients and bridges no longer send TLS certificate chains on
1585 outgoing OR connections. Previously, each client or bridge would
1586 use the same cert chain for all outgoing OR connections until
1587 its IP address changes, which allowed any relay that the client
1588 or bridge contacted to determine which entry guards it is using.
1589 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1590 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1591 no longer considers that connection as suitable for satisfying a
1592 circuit EXTEND request. Now relays can protect clients from the
1593 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1594 - Directory authorities no longer assign the Guard flag to relays
1595 that haven't upgraded to the above "refuse EXTEND requests
1596 to client connections" fix. Now directory authorities can
1597 protect clients from the CVE-2011-2768 issue even if neither
1598 the clients nor the relays have upgraded yet. There's a new
1599 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1600 to let us transition smoothly, else tomorrow there would be no
1603 o Privacy/anonymity fixes (bridge enumeration):
1604 - Bridge relays now do their directory fetches inside Tor TLS
1605 connections, like all the other clients do, rather than connecting
1606 directly to the DirPort like public relays do. Removes another
1607 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
1608 - Bridges relays now build circuits for themselves in a more similar
1609 way to how clients build them. Removes another avenue for
1610 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
1611 when bridges were introduced.
1612 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1613 that they initiated. Relays could distinguish incoming bridge
1614 connections from client connections, creating another avenue for
1615 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1616 Found by "frosty_un".
1619 - Fix a crash bug when changing node restrictions while a DNS lookup
1620 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
1622 - Don't launch a useless circuit after failing to use one of a
1623 hidden service's introduction points. Previously, we would
1624 launch a new introduction circuit, but not set the hidden service
1625 which that circuit was intended to connect to, so it would never
1626 actually be used. A different piece of code would then create a
1627 new introduction circuit correctly. Bug reported by katmagic and
1628 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1631 - Change an integer overflow check in the OpenBSD_Malloc code so
1632 that GCC is less likely to eliminate it as impossible. Patch
1633 from Mansour Moufid. Fixes bug 4059.
1634 - When a hidden service turns an extra service-side introduction
1635 circuit into a general-purpose circuit, free the rend_data and
1636 intro_key fields first, so we won't leak memory if the circuit
1637 is cannibalized for use as another service-side introduction
1638 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
1639 - Bridges now skip DNS self-tests, to act a little more stealthily.
1640 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
1641 bridges. Patch by "warms0x".
1642 - Fix internal bug-checking logic that was supposed to catch
1643 failures in digest generation so that it will fail more robustly
1644 if we ask for a nonexistent algorithm. Found by Coverity Scan.
1645 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
1646 - Report any failure in init_keys() calls launched because our
1647 IP address has changed. Spotted by Coverity Scan. Bugfix on
1648 0.1.1.4-alpha; fixes CID 484.
1650 o Minor bugfixes (log messages and documentation):
1651 - Remove a confusing dollar sign from the example fingerprint in the
1652 man page, and also make the example fingerprint a valid one. Fixes
1653 bug 4309; bugfix on 0.2.1.3-alpha.
1654 - The next version of Windows will be called Windows 8, and it has
1655 a major version of 6, minor version of 2. Correctly identify that
1656 version instead of calling it "Very recent version". Resolves
1657 ticket 4153; reported by funkstar.
1658 - Downgrade log messages about circuit timeout calibration from
1659 "notice" to "info": they don't require or suggest any human
1660 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
1661 bugfix on 0.2.2.14-alpha.
1664 - Turn on directory request statistics by default and include them in
1665 extra-info descriptors. Don't break if we have no GeoIP database.
1666 Backported from 0.2.3.1-alpha; implements ticket 3951.
1667 - Update to the October 4 2011 Maxmind GeoLite Country database.
1670 Changes in version 0.2.1.31 - 2011-10-26
1671 Tor 0.2.1.31 backports important security and privacy fixes for
1672 oldstable. This release is intended only for package maintainers and
1673 others who cannot use the 0.2.2 stable series. All others should be
1674 using Tor 0.2.2.x or newer.
1676 o Security fixes (also included in 0.2.2.x):
1677 - Replace all potentially sensitive memory comparison operations
1678 with versions whose runtime does not depend on the data being
1679 compared. This will help resist a class of attacks where an
1680 adversary can use variations in timing information to learn
1681 sensitive data. Fix for one case of bug 3122. (Safe memcmp
1682 implementation by Robert Ransom based partially on code by DJB.)
1683 - Fix an assert in parsing router descriptors containing IPv6
1684 addresses. This one took down the directory authorities when
1685 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
1687 o Privacy/anonymity fixes (also included in 0.2.2.x):
1688 - Clients and bridges no longer send TLS certificate chains on
1689 outgoing OR connections. Previously, each client or bridge would
1690 use the same cert chain for all outgoing OR connections until
1691 its IP address changes, which allowed any relay that the client
1692 or bridge contacted to determine which entry guards it is using.
1693 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1694 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1695 no longer considers that connection as suitable for satisfying a
1696 circuit EXTEND request. Now relays can protect clients from the
1697 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1698 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1699 that they initiated. Relays could distinguish incoming bridge
1700 connections from client connections, creating another avenue for
1701 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1702 Found by "frosty_un".
1703 - When receiving a hidden service descriptor, check that it is for
1704 the hidden service we wanted. Previously, Tor would store any
1705 hidden service descriptors that a directory gave it, whether it
1706 wanted them or not. This wouldn't have let an attacker impersonate
1707 a hidden service, but it did let directories pre-seed a client
1708 with descriptors that it didn't want. Bugfix on 0.0.6.
1709 - Avoid linkability based on cached hidden service descriptors: forget
1710 all hidden service descriptors cached as a client when processing a
1711 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
1712 - Make the bridge directory authority refuse to answer directory
1713 requests for "all" descriptors. It used to include bridge
1714 descriptors in its answer, which was a major information leak.
1715 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
1716 - Don't attach new streams to old rendezvous circuits after SIGNAL
1717 NEWNYM. Previously, we would keep using an existing rendezvous
1718 circuit if it remained open (i.e. if it were kept open by a
1719 long-lived stream, or if a new stream were attached to it before
1720 Tor could notice that it was old and no longer in use). Bugfix on
1721 0.1.1.15-rc; fixes bug 3375.
1723 o Minor bugfixes (also included in 0.2.2.x):
1724 - When we restart our relay, we might get a successful connection
1725 from the outside before we've started our reachability tests,
1726 triggering a warning: "ORPort found reachable, but I have no
1727 routerinfo yet. Failing to inform controller of success." This
1728 bug was harmless unless Tor is running under a controller
1729 like Vidalia, in which case the controller would never get a
1730 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
1732 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
1733 enabled. Fixes bug 1526.
1734 - Remove undocumented option "-F" from tor-resolve: it hasn't done
1735 anything since 0.2.1.16-rc.
1736 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
1737 None of the cases where we did this before were wrong, but by making
1738 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
1739 - Fix a rare crash bug that could occur when a client was configured
1740 with a large number of bridges. Fixes bug 2629; bugfix on
1741 0.2.1.2-alpha. Bugfix by trac user "shitlei".
1742 - Correct the warning displayed when a rendezvous descriptor exceeds
1743 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
1745 - Fix an uncommon assertion failure when running with DNSPort under
1746 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
1747 - When warning about missing zlib development packages during compile,
1748 give the correct package names. Bugfix on 0.2.0.1-alpha.
1749 - Require that introduction point keys and onion keys have public
1750 exponent 65537. Bugfix on 0.2.0.10-alpha.
1751 - Do not crash when our configuration file becomes unreadable, for
1752 example due to a permissions change, between when we start up
1753 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
1755 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
1757 - Always NUL-terminate the sun_path field of a sockaddr_un before
1758 passing it to the kernel. (Not a security issue: kernels are
1759 smart enough to reject bad sockaddr_uns.) Found by Coverity;
1760 CID #428. Bugfix on Tor 0.2.0.3-alpha.
1761 - Don't stack-allocate the list of supplementary GIDs when we're
1762 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
1763 could take up to 256K, which is way too much stack. Found by
1764 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
1766 o Minor bugfixes (only in 0.2.1.x):
1767 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
1768 rely on them. Bugfix on 0.2.1.30.
1769 - Use git revisions instead of svn revisions when generating our
1770 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
1772 o Minor features (also included in 0.2.2.x):
1773 - Adjust the expiration time on our SSL session certificates to
1774 better match SSL certs seen in the wild. Resolves ticket 4014.
1775 - Allow nameservers with IPv6 address. Resolves bug 2574.
1776 - Update to the October 4 2011 Maxmind GeoLite Country database.
1779 Changes in version 0.2.3.5-alpha - 2011-09-28
1780 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
1781 bridge relays; fixes an assertion error that many users started hitting
1782 today; and adds the ability to refill token buckets more often than
1783 once per second, allowing significant performance improvements.
1786 - Bridge relays now do their directory fetches inside Tor TLS
1787 connections, like all the other clients do, rather than connecting
1788 directly to the DirPort like public relays do. Removes another
1789 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
1790 - Bridges relays now build circuits for themselves in a more similar
1791 way to how clients build them. Removes another avenue for
1792 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
1793 when bridges were introduced.
1796 - Fix an "Assertion md->held_by_node == 1 failed" error that could
1797 occur when the same microdescriptor was referenced by two node_t
1798 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
1800 o Major features (networking):
1801 - Add a new TokenBucketRefillInterval option to refill token buckets
1802 more frequently than once per second. This should improve network
1803 performance, alleviate queueing problems, and make traffic less
1804 bursty. Implements proposal 183; closes ticket 3630. Design by
1805 Florian Tschorsch and Björn Scheuermann; implementation by
1809 - Change an integer overflow check in the OpenBSD_Malloc code so
1810 that GCC is less likely to eliminate it as impossible. Patch
1811 from Mansour Moufid. Fixes bug 4059.
1813 o Minor bugfixes (usability):
1814 - Downgrade log messages about circuit timeout calibration from
1815 "notice" to "info": they don't require or suggest any human
1816 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
1817 bugfix on 0.2.2.14-alpha.
1819 o Minor features (diagnostics):
1820 - When the system call to create a listener socket fails, log the
1821 error message explaining why. This may help diagnose bug 4027.
1824 Changes in version 0.2.3.4-alpha - 2011-09-13
1825 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
1826 tweak to Tor's TLS handshake that makes relays and bridges that run
1827 this new version reachable from Iran again. It also fixes a few new
1828 bugs in 0.2.3.x, and teaches relays to recognize when they're not
1829 listed in the network consensus and republish.
1831 o Major bugfixes (also part of 0.2.2.33):
1832 - Avoid an assertion failure when reloading a configuration with
1833 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
1834 3923; bugfix on 0.2.2.25-alpha.
1836 o Minor features (security, also part of 0.2.2.33):
1837 - Check for replays of the public-key encrypted portion of an
1838 INTRODUCE1 cell, in addition to the current check for replays of
1839 the g^x value. This prevents a possible class of active attacks
1840 by an attacker who controls both an introduction point and a
1841 rendezvous point, and who uses the malleability of AES-CTR to
1842 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
1843 that these attacks is infeasible (requiring the attacker to send
1844 on the order of zettabytes of altered cells in a short interval),
1845 but we'd rather block them off in case there are any classes of
1846 this attack that we missed. Reported by Willem Pinckaers.
1848 o Minor features (also part of 0.2.2.33):
1849 - Adjust the expiration time on our SSL session certificates to
1850 better match SSL certs seen in the wild. Resolves ticket 4014.
1851 - Change the default required uptime for a relay to be accepted as
1852 a HSDir (hidden service directory) from 24 hours to 25 hours.
1853 Improves on 0.2.0.10-alpha; resolves ticket 2649.
1854 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
1855 authorities to abstain from voting on assignment of the HSDir
1856 consensus flag. Related to bug 2649.
1857 - Update to the September 6 2011 Maxmind GeoLite Country database.
1859 o Minor bugfixes (also part of 0.2.2.33):
1860 - Demote the 'replay detected' log message emitted when a hidden
1861 service receives the same Diffie-Hellman public key in two different
1862 INTRODUCE2 cells to info level. A normal Tor client can cause that
1863 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
1864 fixes part of bug 2442.
1865 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
1866 level. There is nothing that a hidden service's operator can do
1867 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
1869 - Clarify a log message specifying the characters permitted in
1870 HiddenServiceAuthorizeClient client names. Previously, the log
1871 message said that "[A-Za-z0-9+-_]" were permitted; that could have
1872 given the impression that every ASCII character between "+" and "_"
1873 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
1875 o Build fixes (also part of 0.2.2.33):
1876 - Clean up some code issues that prevented Tor from building on older
1877 BSDs. Fixes bug 3894; reported by "grarpamp".
1878 - Search for a platform-specific version of "ar" when cross-compiling.
1879 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
1882 - Fix a bug where the SocksPort option (for example) would get
1883 ignored and replaced by the default if a SocksListenAddress
1884 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
1888 - Relays now try regenerating and uploading their descriptor more
1889 frequently if they are not listed in the consensus, or if the
1890 version of their descriptor listed in the consensus is too
1891 old. This fix should prevent situations where a server declines
1892 to re-publish itself because it has done so too recently, even
1893 though the authorities decided not to list its recent-enough
1894 descriptor. Fix for bug 3327.
1897 - Relays now include a reason for regenerating their descriptors
1898 in an HTTP header when uploading to the authorities. This will
1899 make it easier to debug descriptor-upload issues in the future.
1900 - When starting as root and then changing our UID via the User
1901 control option, and we have a ControlSocket configured, make sure
1902 that the ControlSocket is owned by the same account that Tor will
1903 run under. Implements ticket 3421; fix by Jérémy Bobbio.
1906 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
1907 utility function used in the control-port code). This shouldn't
1908 ever happen unless Tor is completely out of memory, but if it did
1909 happen and Tor somehow recovered from it, Tor could have sent a log
1910 message to a control port in the middle of a reply to a controller
1911 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
1912 - Make 'FetchUselessDescriptors' cause all descriptor types and
1913 all consensus types (including microdescriptors) to get fetched.
1914 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
1917 - Make a new "entry connection" struct as an internal subtype of "edge
1918 connection", to simplify the code and make exit connections smaller.
1921 Changes in version 0.2.2.33 - 2011-09-13
1922 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
1923 TLS handshake that makes relays and bridges that run this new version
1924 reachable from Iran again.
1927 - Avoid an assertion failure when reloading a configuration with
1928 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
1929 3923; bugfix on 0.2.2.25-alpha.
1931 o Minor features (security):
1932 - Check for replays of the public-key encrypted portion of an
1933 INTRODUCE1 cell, in addition to the current check for replays of
1934 the g^x value. This prevents a possible class of active attacks
1935 by an attacker who controls both an introduction point and a
1936 rendezvous point, and who uses the malleability of AES-CTR to
1937 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
1938 that these attacks are infeasible (requiring the attacker to send
1939 on the order of zettabytes of altered cells in a short interval),
1940 but we'd rather block them off in case there are any classes of
1941 this attack that we missed. Reported by Willem Pinckaers.
1944 - Adjust the expiration time on our SSL session certificates to
1945 better match SSL certs seen in the wild. Resolves ticket 4014.
1946 - Change the default required uptime for a relay to be accepted as
1947 a HSDir (hidden service directory) from 24 hours to 25 hours.
1948 Improves on 0.2.0.10-alpha; resolves ticket 2649.
1949 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
1950 authorities to abstain from voting on assignment of the HSDir
1951 consensus flag. Related to bug 2649.
1952 - Update to the September 6 2011 Maxmind GeoLite Country database.
1954 o Minor bugfixes (documentation and log messages):
1955 - Correct the man page to explain that HashedControlPassword and
1956 CookieAuthentication can both be set, in which case either method
1957 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
1958 when we decided to allow these config options to both be set. Issue
1960 - Demote the 'replay detected' log message emitted when a hidden
1961 service receives the same Diffie-Hellman public key in two different
1962 INTRODUCE2 cells to info level. A normal Tor client can cause that
1963 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
1964 fixes part of bug 2442.
1965 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
1966 level. There is nothing that a hidden service's operator can do
1967 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
1969 - Clarify a log message specifying the characters permitted in
1970 HiddenServiceAuthorizeClient client names. Previously, the log
1971 message said that "[A-Za-z0-9+-_]" were permitted; that could have
1972 given the impression that every ASCII character between "+" and "_"
1973 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
1976 - Provide a substitute implementation of lround() for MSVC, which
1977 apparently lacks it. Patch from Gisle Vanem.
1978 - Clean up some code issues that prevented Tor from building on older
1979 BSDs. Fixes bug 3894; reported by "grarpamp".
1980 - Search for a platform-specific version of "ar" when cross-compiling.
1981 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
1984 Changes in version 0.2.3.3-alpha - 2011-09-01
1985 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
1986 security, and provides client-side support for the microdescriptor
1987 and optimistic data features introduced earlier in the 0.2.3.x
1988 series. It also includes numerous critical bugfixes in the (optional)
1989 bufferevent-based networking backend.
1991 o Major features (stream isolation):
1992 - You can now configure Tor so that streams from different
1993 applications are isolated on different circuits, to prevent an
1994 attacker who sees your streams as they leave an exit node from
1995 linking your sessions to one another. To do this, choose some way
1996 to distinguish the applications: have them connect to different
1997 SocksPorts, or have one of them use SOCKS4 while the other uses
1998 SOCKS5, or have them pass different authentication strings to the
1999 SOCKS proxy. Then, use the new SocksPort syntax to configure the
2000 degree of isolation you need. This implements Proposal 171.
2001 - There's a new syntax for specifying multiple client ports (such as
2002 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
2003 multiple *Port entries with full addr:port syntax on each.
2004 The old *ListenAddress format is still supported, but you can't
2005 mix it with the new *Port syntax.
2007 o Major features (other):
2008 - Enable microdescriptor fetching by default for clients. This allows
2009 clients to download a much smaller amount of directory information.
2010 To disable it (and go back to the old-style consensus and
2011 descriptors), set "UseMicrodescriptors 0" in your torrc file.
2012 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
2013 "PortForwarding" config option), now supports Windows.
2014 - When using an exit relay running 0.2.3.x, clients can now
2015 "optimistically" send data before the exit relay reports that
2016 the stream has opened. This saves a round trip when starting
2017 connections where the client speaks first (such as web browsing).
2018 This behavior is controlled by a consensus parameter (currently
2019 disabled). To turn it on or off manually, use the "OptimisticData"
2020 torrc option. Implements proposal 181; code by Ian Goldberg.
2022 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
2023 - When using IOCP on Windows, we need to enable Libevent windows
2025 - The IOCP backend now works even when the user has not specified
2026 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
2027 Fixes part of bug 3752.
2028 - Correctly record the bytes we've read and written when using
2029 bufferevents, so that we can include them in our bandwidth history
2030 and advertised bandwidth. Fixes bug 3803.
2031 - Apply rate-limiting only at the bottom of a chain of filtering
2032 bufferevents. This prevents us from filling up internal read
2033 buffers and violating rate-limits when filtering bufferevents
2034 are enabled. Fixes part of bug 3804.
2035 - Add high-watermarks to the output buffers for filtered
2036 bufferevents. This prevents us from filling up internal write
2037 buffers and wasting CPU cycles when filtering bufferevents are
2038 enabled. Fixes part of bug 3804.
2039 - Correctly notice when data has been written from a bufferevent
2040 without flushing it completely. Fixes bug 3805.
2041 - Fix a bug where server-side tunneled bufferevent-based directory
2042 streams would get closed prematurely. Fixes bug 3814.
2043 - Fix a use-after-free error with per-connection rate-limiting
2044 buckets. Fixes bug 3888.
2046 o Major bugfixes (also part of 0.2.2.31-rc):
2047 - If we're configured to write our ControlPorts to disk, only write
2048 them after switching UID and creating the data directory. This way,
2049 we don't fail when starting up with a nonexistent DataDirectory
2050 and a ControlPortWriteToFile setting based on that directory. Fixes
2051 bug 3747; bugfix on Tor 0.2.2.26-beta.
2054 - Added a new CONF_CHANGED event so that controllers can be notified
2055 of any configuration changes made by other controllers, or by the
2056 user. Implements ticket 1692.
2057 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
2058 leak when using bufferevents, and lets Libevent worry about how to
2059 best copy data out of a buffer.
2060 - Replace files in stats/ rather than appending to them. Now that we
2061 include statistics in extra-info descriptors, it makes no sense to
2062 keep old statistics forever. Implements ticket 2930.
2064 o Minor features (build compatibility):
2065 - Limited, experimental support for building with nmake and MSVC.
2066 - Provide a substitute implementation of lround() for MSVC, which
2067 apparently lacks it. Patch from Gisle Vanem.
2069 o Minor features (also part of 0.2.2.31-rc):
2070 - Update to the August 2 2011 Maxmind GeoLite Country database.
2072 o Minor bugfixes (on 0.2.3.x-alpha):
2073 - Fix a spurious warning when parsing SOCKS requests with
2074 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
2075 - Get rid of a harmless warning that could happen on relays running
2076 with bufferevents. The warning was caused by someone doing an http
2077 request to a relay's orport. Also don't warn for a few related
2078 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
2080 o Minor bugfixes (on 2.2.x and earlier):
2081 - Correct the man page to explain that HashedControlPassword and
2082 CookieAuthentication can both be set, in which case either method
2083 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2084 when we decided to allow these config options to both be set. Issue
2086 - The "--quiet" and "--hush" options now apply not only to Tor's
2087 behavior before logs are configured, but also to Tor's behavior in
2088 the absense of configured logs. Fixes bug 3550; bugfix on
2091 o Minor bugfixes (also part of 0.2.2.31-rc):
2092 - Write several files in text mode, on OSes that distinguish text
2093 mode from binary mode (namely, Windows). These files are:
2094 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2095 that collect those statistics; 'client_keys' and 'hostname' for
2096 hidden services that use authentication; and (in the tor-gencert
2097 utility) newly generated identity and signing keys. Previously,
2098 we wouldn't specify text mode or binary mode, leading to an
2099 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2100 the DirRecordUsageByCountry option which would have triggered
2101 the assertion failure was added), although this assertion failure
2102 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2103 - Selectively disable deprecation warnings on OS X because Lion
2104 started deprecating the shipped copy of openssl. Fixes bug 3643.
2105 - Remove an extra pair of quotation marks around the error
2106 message in control-port STATUS_GENERAL BUG events. Bugfix on
2107 0.1.2.6-alpha; fixes bug 3732.
2108 - When unable to format an address as a string, report its value
2109 as "???" rather than reusing the last formatted address. Bugfix
2112 o Code simplifications and refactoring:
2113 - Rewrite the listener-selection logic so that parsing which ports
2114 we want to listen on is now separate from binding to the ports
2118 - Building Tor with bufferevent support now requires Libevent
2119 2.0.13-stable or later. Previous versions of Libevent had bugs in
2120 SSL-related bufferevents and related issues that would make Tor
2121 work badly with bufferevents. Requiring 2.0.13-stable also allows
2122 Tor with bufferevents to take advantage of Libevent APIs
2123 introduced after 2.0.8-rc.
2126 Changes in version 0.2.2.32 - 2011-08-27
2127 The Tor 0.2.2 release series is dedicated to the memory of Andreas
2128 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
2129 a founder of the PETS community, a leader in our field, a mentor,
2130 and a friend. He left us with these words: "I had the possibility
2131 to contribute to this world that is not as it should be. I hope I
2132 could help in some areas to make the world a better place, and that
2133 I could also encourage other people to be engaged in improving the
2134 world. Please, stay engaged. This world needs you, your love, your
2135 initiative -- now I cannot be part of that anymore."
2137 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
2138 ready. More than two years in the making, this release features improved
2139 client performance and hidden service reliability, better compatibility
2140 for Android, correct behavior for bridges that listen on more than
2141 one address, more extensible and flexible directory object handling,
2142 better reporting of network statistics, improved code security, and
2143 many many other features and bugfixes.
2146 Changes in version 0.2.2.31-rc - 2011-08-17
2147 Tor 0.2.2.31-rc is the second and hopefully final release candidate
2148 for the Tor 0.2.2.x series.
2151 - Remove an extra pair of quotation marks around the error
2152 message in control-port STATUS_GENERAL BUG events. Bugfix on
2153 0.1.2.6-alpha; fixes bug 3732.
2154 - If we're configured to write our ControlPorts to disk, only write
2155 them after switching UID and creating the data directory. This way,
2156 we don't fail when starting up with a nonexistent DataDirectory
2157 and a ControlPortWriteToFile setting based on that directory. Fixes
2158 bug 3747; bugfix on Tor 0.2.2.26-beta.
2161 - Update to the August 2 2011 Maxmind GeoLite Country database.
2164 - Allow GETINFO fingerprint to return a fingerprint even when
2165 we have not yet built a router descriptor. Fixes bug 3577;
2166 bugfix on 0.2.0.1-alpha.
2167 - Write several files in text mode, on OSes that distinguish text
2168 mode from binary mode (namely, Windows). These files are:
2169 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2170 that collect those statistics; 'client_keys' and 'hostname' for
2171 hidden services that use authentication; and (in the tor-gencert
2172 utility) newly generated identity and signing keys. Previously,
2173 we wouldn't specify text mode or binary mode, leading to an
2174 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2175 the DirRecordUsageByCountry option which would have triggered
2176 the assertion failure was added), although this assertion failure
2177 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2178 - Selectively disable deprecation warnings on OS X because Lion
2179 started deprecating the shipped copy of openssl. Fixes bug 3643.
2180 - When unable to format an address as a string, report its value
2181 as "???" rather than reusing the last formatted address. Bugfix
2185 Changes in version 0.2.3.2-alpha - 2011-07-18
2186 Tor 0.2.3.2-alpha introduces two new experimental features:
2187 microdescriptors and pluggable transports. It also continues cleaning
2188 up a variety of recently introduced features.
2191 - Clients can now use microdescriptors instead of regular descriptors
2192 to build circuits. Microdescriptors are authority-generated
2193 summaries of regular descriptors' contents, designed to change
2194 very rarely (see proposal 158 for details). This feature is
2195 designed to save bandwidth, especially for clients on slow internet
2196 connections. It's off by default for now, since nearly no caches
2197 support it, but it will be on-by-default for clients in a future
2198 version. You can use the UseMicrodescriptors option to turn it on.
2199 - Tor clients using bridges can now be configured to use a separate
2200 'transport' proxy for each bridge. This approach helps to resist
2201 censorship by allowing bridges to use protocol obfuscation
2202 plugins. It implements part of proposal 180. Implements ticket 2841.
2203 - While we're trying to bootstrap, record how many TLS connections
2204 fail in each state, and report which states saw the most failures
2205 in response to any bootstrap failures. This feature may speed up
2206 diagnosis of censorship events. Implements ticket 3116.
2208 o Major bugfixes (on 0.2.3.1-alpha):
2209 - When configuring a large set of nodes in EntryNodes (as with
2210 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
2211 random subset to be guards, and choose them in random
2212 order. Fixes bug 2798.
2213 - Tor could crash when remembering a consensus in a non-used consensus
2214 flavor without having a current consensus set. Fixes bug 3361.
2215 - Comparing an unknown address to a microdescriptor's shortened exit
2216 policy would always give a "rejected" result. Fixes bug 3599.
2217 - Using microdescriptors as a client no longer prevents Tor from
2218 uploading and downloading hidden service descriptors. Fixes
2222 - Allow nameservers with IPv6 address. Resolves bug 2574.
2223 - Accept attempts to include a password authenticator in the
2224 handshake, as supported by SOCKS5. This handles SOCKS clients that
2225 don't know how to omit a password when authenticating. Resolves
2227 - When configuring a large set of nodes in EntryNodes, and there are
2228 enough of them listed as Guard so that we don't need to consider
2229 the non-guard entries, prefer the ones listed with the Guard flag.
2230 - Check for and recover from inconsistency in the microdescriptor
2231 cache. This will make it harder for us to accidentally free a
2232 microdescriptor without removing it from the appropriate data
2233 structures. Fixes issue 3135; issue noted by "wanoskarnet".
2234 - Log SSL state transitions at log level DEBUG, log domain
2235 HANDSHAKE. This can be useful for debugging censorship events.
2236 Implements ticket 3264.
2237 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
2238 implements ticket 3439.
2240 o Minor bugfixes (on 0.2.3.1-alpha):
2241 - Do not free all general-purpose regular descriptors just
2242 because microdescriptor use is enabled. Fixes bug 3113.
2243 - Correctly link libevent_openssl when --enable-static-libevent
2244 is passed to configure. Fixes bug 3118.
2245 - Bridges should not complain during their heartbeat log messages that
2246 they are unlisted in the consensus: that's more or less the point
2247 of being a bridge. Fixes bug 3183.
2248 - Report a SIGNAL event to controllers when acting on a delayed
2249 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
2250 event to the controller if we acted on a SIGNAL NEWNYM command
2251 immediately, and otherwise not report a SIGNAL event for the
2252 command at all. Fixes bug 3349.
2253 - Fix a crash when handling the SIGNAL controller command or
2254 reporting ERR-level status events with bufferevents enabled. Found
2255 by Robert Ransom. Fixes bug 3367.
2256 - Always ship the tor-fw-helper manpage in our release tarballs.
2257 Fixes bug 3389. Reported by Stephen Walker.
2258 - Fix a class of double-mark-for-close bugs when bufferevents
2259 are enabled. Fixes bug 3403.
2260 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
2261 - Add SIGNAL to the list returned by the 'GETINFO events/names'
2262 control-port command. Fixes part of bug 3465.
2263 - Prevent using negative indices during unit test runs when read_all()
2264 fails. Spotted by coverity.
2265 - Fix a rare memory leak when checking the nodelist without it being
2266 present. Found by coverity.
2267 - Only try to download a microdescriptor-flavored consensus from
2268 a directory cache that provides them.
2270 o Minor bugfixes (on 0.2.2.x and earlier):
2271 - Assert that hidden-service-related operations are not performed
2272 using single-hop circuits. Previously, Tor would assert that
2273 client-side streams are not attached to single-hop circuits,
2274 but not that other sensitive operations on the client and service
2275 side are not performed using single-hop circuits. Fixes bug 3332;
2277 - Don't publish a new relay descriptor when we reload our onion key,
2278 unless the onion key has actually changed. Fixes bug 3263 and
2279 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
2280 - Allow GETINFO fingerprint to return a fingerprint even when
2281 we have not yet built a router descriptor. Fixes bug 3577;
2282 bugfix on 0.2.0.1-alpha.
2283 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
2284 on 0.2.2.4-alpha; fixes bug 3427.
2286 o Code simplification and refactoring:
2287 - Use tor_sscanf() in place of scanf() in more places through the
2288 code. This makes us a little more locale-independent, and
2289 should help shut up code-analysis tools that can't tell
2290 a safe sscanf string from a dangerous one.
2291 - Use tt_assert(), not tor_assert(), for checking for test failures.
2292 This makes the unit tests more able to go on in the event that
2294 - Split connection_about_to_close() into separate functions for each
2298 - On Windows, we now define the _WIN32_WINNT macros only if they
2299 are not already defined. This lets the person building Tor decide,
2300 if they want, to require a later version of Windows.
2303 Changes in version 0.2.2.30-rc - 2011-07-07
2304 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
2305 series. It fixes a few smaller bugs, but generally appears stable.
2306 Please test it and let us know whether it is!
2309 - Send a SUCCEEDED stream event to the controller when a reverse
2310 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
2311 discovered by katmagic.
2312 - Always NUL-terminate the sun_path field of a sockaddr_un before
2313 passing it to the kernel. (Not a security issue: kernels are
2314 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2315 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2316 - Don't stack-allocate the list of supplementary GIDs when we're
2317 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2318 could take up to 256K, which is way too much stack. Found by
2319 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2320 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
2321 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
2322 fixes part of bug 3465.
2323 - Fix a memory leak when receiving a descriptor for a hidden
2324 service we didn't ask for. Found by Coverity; CID #30. Bugfix
2328 - Update to the July 1 2011 Maxmind GeoLite Country database.
2331 Changes in version 0.2.2.29-beta - 2011-06-20
2332 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
2333 have bridge lines in their torrc but don't want to use them; gets
2334 us closer to having the control socket feature working on Debian;
2335 and fixes a variety of smaller bugs.
2338 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
2339 When we changed the default behavior to "use bridges if any
2340 are listed in the torrc", we surprised users who had bridges
2341 in their torrc files but who didn't actually want to use them.
2342 Partial resolution for bug 3354.
2345 - Don't attach new streams to old rendezvous circuits after SIGNAL
2346 NEWNYM. Previously, we would keep using an existing rendezvous
2347 circuit if it remained open (i.e. if it were kept open by a
2348 long-lived stream, or if a new stream were attached to it before
2349 Tor could notice that it was old and no longer in use). Bugfix on
2350 0.1.1.15-rc; fixes bug 3375.
2353 - Fix a bug when using ControlSocketsGroupWritable with User. The
2354 directory's group would be checked against the current group, not
2355 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
2356 bugfix on 0.2.2.26-beta.
2357 - Make connection_printf_to_buf()'s behaviour sane. Its callers
2358 expect it to emit a CRLF iff the format string ends with CRLF;
2359 it actually emitted a CRLF iff (a) the format string ended with
2360 CRLF or (b) the resulting string was over 1023 characters long or
2361 (c) the format string did not end with CRLF *and* the resulting
2362 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
2363 fixes part of bug 3407.
2364 - Make send_control_event_impl()'s behaviour sane. Its callers
2365 expect it to always emit a CRLF at the end of the string; it
2366 might have emitted extra control characters as well. Bugfix on
2367 0.1.1.9-alpha; fixes another part of bug 3407.
2368 - Make crypto_rand_int() check the value of its input correctly.
2369 Previously, it accepted values up to UINT_MAX, but could return a
2370 negative number if given a value above INT_MAX+1. Found by George
2371 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
2372 - Avoid a segfault when reading a malformed circuit build state
2373 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
2375 - When asked about a DNS record type we don't support via a
2376 client DNSPort, reply with NOTIMPL rather than an empty
2377 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
2378 - Fix a rare memory leak during stats writing. Found by coverity.
2381 - Update to the June 1 2011 Maxmind GeoLite Country database.
2383 o Code simplifications and refactoring:
2384 - Remove some dead code as indicated by coverity.
2385 - Remove a few dead assignments during router parsing. Found by
2387 - Add some forgotten return value checks during unit tests. Found
2389 - Don't use 1-bit wide signed bit fields. Found by coverity.
2392 Changes in version 0.2.2.28-beta - 2011-06-04
2393 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
2394 fixed a big bug in whether relays stay in the consensus consistently,
2395 we moved closer to handling bridges and hidden services correctly,
2396 and we started the process of better handling the dreaded "my Vidalia
2397 died, and now my Tor demands a password when I try to reconnect to it"
2401 - Don't decide to make a new descriptor when receiving a HUP signal.
2402 This bug has caused a lot of 0.2.2.x relays to disappear from the
2403 consensus periodically. Fixes the most common case of triggering
2404 bug 1810; bugfix on 0.2.2.7-alpha.
2405 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
2406 - Don't try to build descriptors if "ORPort auto" is set and we
2407 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
2409 - Resolve a crash that occurred when setting BridgeRelay to 1 with
2410 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
2411 - Apply circuit timeouts to opened hidden-service-related circuits
2412 based on the correct start time. Previously, we would apply the
2413 circuit build timeout based on time since the circuit's creation;
2414 it was supposed to be applied based on time since the circuit
2415 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
2416 - Use the same circuit timeout for client-side introduction
2417 circuits as for other four-hop circuits, rather than the timeout
2418 for single-hop directory-fetch circuits; the shorter timeout may
2419 have been appropriate with the static circuit build timeout in
2420 0.2.1.x and earlier, but caused many hidden service access attempts
2421 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
2422 on 0.2.2.2-alpha; fixes another part of bug 1297.
2423 - In ticket 2511 we fixed a case where you could use an unconfigured
2424 bridge if you had configured it as a bridge the last time you ran
2425 Tor. Now fix another edge case: if you had configured it as a bridge
2426 but then switched to a different bridge via the controller, you
2427 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
2431 - Add an __OwningControllerProcess configuration option and a
2432 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
2433 that when it exits, Tor will shut down. Implements feature 3049.
2434 - If "UseBridges 1" is set and no bridges are configured, Tor will
2435 now refuse to build any circuits until some bridges are set.
2436 If "UseBridges auto" is set, Tor will use bridges if they are
2437 configured and we are not running as a server, but otherwise will
2438 make circuits as usual. The new default is "auto". Patch by anonym,
2439 so the Tails LiveCD can stop automatically revealing you as a Tor
2443 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2444 - Remove a trailing asterisk from "exit-policy/default" in the
2445 output of the control port command "GETINFO info/names". Bugfix
2447 - Use a wide type to hold sockets when built for 64-bit Windows builds.
2449 - Warn when the user configures two HiddenServiceDir lines that point
2450 to the same directory. Bugfix on 0.0.6 (the version introducing
2451 HiddenServiceDir); fixes bug 3289.
2452 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
2453 part of bug 2748; bugfix on 0.2.0.10-alpha.
2454 - Log malformed requests for rendezvous descriptors as protocol
2455 warnings, not warnings. Also, use a more informative log message
2456 in case someone sees it at log level warning without prior
2457 info-level messages. Fixes the other part of bug 2748; bugfix
2459 - Clear the table recording the time of the last request for each
2460 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
2461 Previously, we would clear our HS descriptor cache on SIGNAL
2462 NEWNYM, but if we had previously retrieved a descriptor (or tried
2463 to) from every directory responsible for it, we would refuse to
2464 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
2466 - Fix a log message that said "bits" while displaying a value in
2467 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
2469 - When checking for 1024-bit keys, check for 1024 bits, not 128
2470 bytes. This allows Tor to correctly discard keys of length 1017
2471 through 1023. Bugfix on 0.0.9pre5.
2474 - Relays now log the reason for publishing a new relay descriptor,
2475 so we have a better chance of hunting down instances of bug 1810.
2476 Resolves ticket 3252.
2477 - Revise most log messages that refer to nodes by nickname to
2478 instead use the "$key=nickname at address" format. This should be
2479 more useful, especially since nicknames are less and less likely
2480 to be unique. Resolves ticket 3045.
2481 - Log (at info level) when purging pieces of hidden-service-client
2482 state because of SIGNAL NEWNYM.
2485 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2486 anything since 0.2.1.16-rc.
2489 Changes in version 0.2.2.27-beta - 2011-05-18
2490 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
2491 release, and also adds a few more general bugfixes.
2494 - Fix a crash bug when changing bridges in a running Tor process.
2495 Fixes bug 3213; bugfix on 0.2.2.26-beta.
2496 - When the controller configures a new bridge, don't wait 10 to 60
2497 seconds before trying to fetch its descriptor. Bugfix on
2498 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
2501 - Require that onion keys have exponent 65537 in microdescriptors too.
2502 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
2503 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
2504 Changed the limit to 512 characters by removing base64 newlines.
2505 Fixes bug 2752. Fix by Michael Yakubovich.
2506 - When a client starts or stops using bridges, never use a circuit
2507 that was built before the configuration change. This behavior could
2508 put at risk a user who uses bridges to ensure that her traffic
2509 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
2513 Changes in version 0.2.2.26-beta - 2011-05-17
2514 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
2515 also introduces a new "socksport auto" approach that should make it
2516 easier to run multiple Tors on the same system, and does a lot of
2517 cleanup to get us closer to a release candidate.
2519 o Security/privacy fixes:
2520 - Replace all potentially sensitive memory comparison operations
2521 with versions whose runtime does not depend on the data being
2522 compared. This will help resist a class of attacks where an
2523 adversary can use variations in timing information to learn
2524 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2525 implementation by Robert Ransom based partially on code by DJB.)
2526 - When receiving a hidden service descriptor, check that it is for
2527 the hidden service we wanted. Previously, Tor would store any
2528 hidden service descriptors that a directory gave it, whether it
2529 wanted them or not. This wouldn't have let an attacker impersonate
2530 a hidden service, but it did let directories pre-seed a client
2531 with descriptors that it didn't want. Bugfix on 0.0.6.
2532 - On SIGHUP, do not clear out all TrackHostExits mappings, client
2533 DNS cache entries, and virtual address mappings: that's what
2534 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
2537 - The options SocksPort, ControlPort, and so on now all accept a
2538 value "auto" that opens a socket on an OS-selected port. A
2539 new ControlPortWriteToFile option tells Tor to write its
2540 actual control port or ports to a chosen file. If the option
2541 ControlPortFileGroupReadable is set, the file is created as
2542 group-readable. Now users can run two Tor clients on the same
2543 system without needing to manually mess with parameters. Resolves
2544 part of ticket 3076.
2545 - Set SO_REUSEADDR on all sockets, not just listeners. This should
2546 help busy exit nodes avoid running out of useable ports just
2547 because all the ports have been used in the near past. Resolves
2551 - New "GETINFO net/listeners/(type)" controller command to return
2552 a list of addresses and ports that are bound for listeners for a
2553 given connection type. This is useful when the user has configured
2554 "SocksPort auto" and the controller needs to know which port got
2555 chosen. Resolves another part of ticket 3076.
2556 - Add a new ControlSocketsGroupWritable configuration option: when
2557 it is turned on, ControlSockets are group-writeable by the default
2558 group of the current user. Patch by Jérémy Bobbio; implements
2560 - Tor now refuses to create a ControlSocket in a directory that is
2561 world-readable (or group-readable if ControlSocketsGroupWritable
2562 is 0). This is necessary because some operating systems do not
2563 enforce permissions on an AF_UNIX sockets. Permissions on the
2564 directory holding the socket, however, seems to work everywhere.
2565 - Rate-limit a warning about failures to download v2 networkstatus
2566 documents. Resolves part of bug 1352.
2567 - Backport code from 0.2.3.x that allows directory authorities to
2568 clean their microdescriptor caches. Needed to resolve bug 2230.
2569 - When an HTTPS proxy reports "403 Forbidden", we now explain
2570 what it means rather than calling it an unexpected status code.
2571 Closes bug 2503. Patch from Michael Yakubovich.
2572 - Update to the May 1 2011 Maxmind GeoLite Country database.
2575 - Authorities now clean their microdesc cache periodically and when
2576 reading from disk initially, not only when adding new descriptors.
2577 This prevents a bug where we could lose microdescriptors. Bugfix
2578 on 0.2.2.6-alpha. Fixes bug 2230.
2579 - Do not crash when our configuration file becomes unreadable, for
2580 example due to a permissions change, between when we start up
2581 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2583 - Avoid a bug that would keep us from replacing a microdescriptor
2584 cache on Windows. (We would try to replace the file while still
2585 holding it open. That's fine on Unix, but Windows doesn't let us
2586 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
2587 - Add missing explanations for the authority-related torrc options
2588 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
2589 man page. Resolves issue 2379.
2590 - As an authority, do not upload our own vote or signature set to
2591 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
2592 it would get flagged as a duplicate. Resolves bug 3026.
2593 - Accept hidden service descriptors if we think we might be a hidden
2594 service directory, regardless of what our consensus says. This
2595 helps robustness, since clients and hidden services can sometimes
2596 have a more up-to-date view of the network consensus than we do,
2597 and if they think that the directory authorities list us a HSDir,
2598 we might actually be one. Related to bug 2732; bugfix on
2600 - When a controller changes TrackHostExits, remove mappings for
2601 hosts that should no longer have their exits tracked. Bugfix on
2603 - When a controller changes VirtualAddrNetwork, remove any mappings
2604 for hosts that were automapped to the old network. Bugfix on
2606 - When a controller changes one of the AutomapHosts* options, remove
2607 any mappings for hosts that should no longer be automapped. Bugfix
2609 - Do not reset the bridge descriptor download status every time we
2610 re-parse our configuration or get a configuration change. Fixes
2611 bug 3019; bugfix on 0.2.0.3-alpha.
2613 o Minor bugfixes (code cleanup):
2614 - When loading the microdesc journal, remember its current size.
2615 In 0.2.2, this helps prevent the microdesc journal from growing
2616 without limit on authorities (who are the only ones to use it in
2617 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
2618 Fix posted by "cypherpunks."
2619 - The microdesc journal is supposed to get rebuilt only if it is
2620 at least _half_ the length of the store, not _twice_ the length
2621 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
2622 - Fix a potential null-pointer dereference while computing a
2623 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
2625 - Avoid a possible null-pointer dereference when rebuilding the mdesc
2626 cache without actually having any descriptors to cache. Bugfix on
2627 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
2628 - If we fail to compute the identity digest of a v3 legacy keypair,
2629 warn, and don't use a buffer-full of junk instead. Bugfix on
2630 0.2.1.1-alpha; fixes bug 3106.
2631 - Resolve an untriggerable issue in smartlist_string_num_isin(),
2632 where if the function had ever in the future been used to check
2633 for the presence of a too-large number, it would have given an
2634 incorrect result. (Fortunately, we only used it for 16-bit
2635 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
2636 - Require that introduction point keys and onion handshake keys
2637 have a public exponent of 65537. Starts to fix bug 3207; bugfix
2641 - Caches no longer download and serve v2 networkstatus documents
2642 unless FetchV2Networkstatus flag is set: these documents haven't
2643 haven't been used by clients or relays since 0.2.0.x. Resolves
2647 Changes in version 0.2.3.1-alpha - 2011-05-05
2648 Tor 0.2.3.1-alpha adds some new experimental features, including support
2649 for an improved network IO backend, IOCP networking on Windows,
2650 microdescriptor caching, "fast-start" support for streams, and automatic
2651 home router configuration. There are also numerous internal improvements
2652 to try to make the code easier for developers to work with.
2654 This is the first alpha release in a new series, so expect there to be
2655 bugs. Users who would rather test out a more stable branch should
2656 stay with 0.2.2.x for now.
2659 - Tor can now optionally build with the "bufferevents" buffered IO
2660 backend provided by Libevent 2. To use this feature, make sure you
2661 have the latest possible version of Libevent, and pass the
2662 --enable-bufferevents flag to configure when building Tor from
2663 source. This feature will make our networking code more flexible,
2664 let us stack layers on each other, and let us use more efficient
2665 zero-copy transports where available.
2666 - As an experimental feature, Tor can use IOCP for networking on Windows.
2667 Once this code is tuned and optimized, it promises much better
2668 performance than the select-based backend we've used in the past. To
2669 try this feature, you must build Tor with Libevent 2, configure Tor
2670 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
2671 your torrc. There are known bugs here: only try this if you can help
2672 debug it as it breaks.
2673 - The EntryNodes option can now include country codes like {de} or IP
2674 addresses or network masks. Previously we had disallowed these options
2675 because we didn't have an efficient way to keep the list up to
2676 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
2677 - Exit nodes now accept and queue data on not-yet-connected streams.
2678 Previously, the client wasn't allowed to send data until the stream was
2679 connected, which slowed down all connections. This change will enable
2680 clients to perform a "fast-start" on streams and send data without
2681 having to wait for a confirmation that the stream has opened. (Patch
2682 from Ian Goldberg; implements the server side of Proposal 174.)
2683 - Tor now has initial support for automatic port mapping on the many
2684 home routers that support NAT-PMP or UPnP. (Not yet supported on
2685 Windows). To build the support code, you'll need to have libnatpnp
2686 library and/or the libminiupnpc library, and you'll need to enable the
2687 feature specifically by passing "--enable-upnp" and/or
2688 "--enable-natpnp" to configure. To turn it on, use the new
2689 PortForwarding option.
2690 - Caches now download, cache, and serve multiple "flavors" of the
2691 consensus, including a flavor that describes microdescriptors.
2692 - Caches now download, cache, and serve microdescriptors -- small
2693 summaries of router descriptors that are authenticated by all of the
2694 directory authorities. Once enough caches are running this code,
2695 clients will be able to save significant amounts of directory bandwidth
2696 by downloading microdescriptors instead of router descriptors.
2699 - Make logging resolution configurable with a new LogTimeGranularity
2700 option, and change the default from 1 millisecond to 1 second.
2701 Implements enhancement 1668.
2702 - We log which torrc file we're using on startup. Implements ticket
2704 - Ordinarily, Tor does not count traffic from private addresses (like
2705 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
2706 There is now a new option, CountPrivateBandwidth, to disable this
2707 behavior. Patch from Daniel Cagara.
2708 - New --enable-static-tor configure option for building Tor as
2709 statically as possible. Idea, general hackery and thoughts from
2710 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
2712 - If you set the NumCPUs option to 0, Tor will now try to detect how
2713 many CPUs you have. This is the new default behavior.
2714 - Turn on directory request statistics by default and include them in
2715 extra-info descriptors. Don't break if we have no GeoIP database.
2716 - Relays that set "ConnDirectionStatistics 1" write statistics on the
2717 bidirectional use of connections to disk every 24 hours.
2718 - Add a GeoIP file digest to the extra-info descriptor. Implements
2720 - The NodeFamily option -- which let you declare that you want to
2721 consider nodes to be part of a family whether they list themselves
2722 that way or not -- now allows IP address ranges and country codes.
2723 - Add a new 'Heartbeat' log message type to periodically log a message
2724 describing Tor's status at level Notice. This feature is meant for
2725 operators who log at notice, and want to make sure that their Tor
2726 server is still working. Implementation by George Kadianakis.
2728 o Minor bugfixes (on 0.2.2.25-alpha):
2729 - When loading the microdesc journal, remember its current size.
2730 In 0.2.2, this helps prevent the microdesc journal from growing
2731 without limit on authorities (who are the only ones to use it in
2732 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
2733 Fix posted by "cypherpunks."
2734 - The microdesc journal is supposed to get rebuilt only if it is
2735 at least _half_ the length of the store, not _twice_ the length
2736 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
2737 - If as an authority we fail to compute the identity digest of a v3
2738 legacy keypair, warn, and don't use a buffer-full of junk instead.
2739 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
2740 - Authorities now clean their microdesc cache periodically and when
2741 reading from disk initially, not only when adding new descriptors.
2742 This prevents a bug where we could lose microdescriptors. Bugfix
2745 o Minor features (controller):
2746 - Add a new SIGNAL event to the controller interface so that
2747 controllers can be notified when Tor handles a signal. Resolves
2748 issue 1955. Patch by John Brooks.
2749 - Add a new GETINFO option to get total bytes read and written. Patch
2750 from pipe, revised by atagar. Resolves ticket 2345.
2751 - Implement some GETINFO controller fields to provide information about
2752 the Tor process's pid, euid, username, and resource limits.
2755 - Our build system requires automake 1.6 or later to create the
2756 Makefile.in files. Previously, you could have used 1.4.
2757 This only affects developers and people building Tor from git;
2758 people who build Tor from the source distribution without changing
2759 the Makefile.am files should be fine.
2760 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
2761 so on. This is more robust against some of the failure modes
2762 associated with running the autotools pieces on their own.
2764 o Minor packaging issues:
2765 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
2766 already created. Patch from Andreas Stieger. Fixes bug 2573.
2768 o Code simplifications and refactoring:
2769 - A major revision to our internal node-selecting and listing logic.
2770 Tor already had at least two major ways to look at the question of
2771 "which Tor servers do we know about": a list of router descriptors,
2772 and a list of entries in the current consensus. With
2773 microdescriptors, we're adding a third. Having so many systems
2774 without an abstraction layer over them was hurting the codebase.
2775 Now, we have a new "node_t" abstraction that presents a consistent
2776 interface to a client's view of a Tor node, and holds (nearly) all
2777 of the mutable state formerly in routerinfo_t and routerstatus_t.
2778 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
2779 no longer link against Libevent: they never used it, but
2780 our library structure used to force them to link it.
2783 - Remove some old code to work around even older versions of Tor that
2784 used forked processes to handle DNS requests. Such versions of Tor
2785 are no longer in use as servers.
2787 o Documentation fixes:
2788 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
2789 - Add missing documentation for the authority-related torrc options
2790 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
2794 Changes in version 0.2.2.25-alpha - 2011-04-29
2795 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
2796 robust, routers no longer overreport their bandwidth, Win7 should crash
2797 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
2798 now prevents hidden service-related activity from being linkable. It
2799 provides more information to Vidalia so you can see if your bridge is
2800 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
2801 StrictNodes configuration options to make them more reliable, more
2802 understandable, and more regularly applied. If you use those options,
2803 please see the revised documentation for them in the manual page.
2806 - Relays were publishing grossly inflated bandwidth values because
2807 they were writing their state files wrong--now they write the
2808 correct value. Also, resume reading bandwidth history from the
2809 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
2810 - Improve hidden service robustness: When we find that we have
2811 extended a hidden service's introduction circuit to a relay not
2812 listed as an introduction point in the HS descriptor we currently
2813 have, retry with an introduction point from the current
2814 descriptor. Previously we would just give up. Fixes bugs 1024 and
2815 1930; bugfix on 0.2.0.10-alpha.
2816 - Clients now stop trying to use an exit node associated with a given
2817 destination by TrackHostExits if they fail to reach that exit node.
2818 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
2819 - Fix crash bug on platforms where gmtime and localtime can return
2820 NULL. Windows 7 users were running into this one. Fixes part of bug
2821 2077. Bugfix on all versions of Tor. Found by boboper.
2823 o Security and stability fixes:
2824 - Don't double-free a parsable, but invalid, microdescriptor, even if
2825 it is followed in the blob we're parsing by an unparsable
2826 microdescriptor. Fixes an issue reported in a comment on bug 2954.
2827 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
2828 - If the Nickname configuration option isn't given, Tor would pick a
2829 nickname based on the local hostname as the nickname for a relay.
2830 Because nicknames are not very important in today's Tor and the
2831 "Unnamed" nickname has been implemented, this is now problematic
2832 behavior: It leaks information about the hostname without being
2833 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
2834 introduced the Unnamed nickname. Reported by tagnaq.
2835 - Fix an uncommon assertion failure when running with DNSPort under
2836 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
2837 - Avoid linkability based on cached hidden service descriptors: forget
2838 all hidden service descriptors cached as a client when processing a
2839 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
2842 - Export GeoIP information on bridge usage to controllers even if we
2843 have not yet been running for 24 hours. Now Vidalia bridge operators
2844 can get more accurate and immediate feedback about their
2845 contributions to the network.
2847 o Major features and bugfixes (node selection):
2848 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
2849 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
2850 options. Previously, we had been ambiguous in describing what
2851 counted as an "exit" node, and what operations exactly "StrictNodes
2852 0" would permit. This created confusion when people saw nodes built
2853 through unexpected circuits, and made it hard to tell real bugs from
2854 surprises. Now the intended behavior is:
2855 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
2856 a node that delivers user traffic outside the Tor network.
2857 . "Entry", in the context of EntryNodes, means a node used as the
2858 first hop of a multihop circuit. It doesn't include direct
2859 connections to directory servers.
2860 . "ExcludeNodes" applies to all nodes.
2861 . "StrictNodes" changes the behavior of ExcludeNodes only. When
2862 StrictNodes is set, Tor should avoid all nodes listed in
2863 ExcludeNodes, even when it will make user requests fail. When
2864 StrictNodes is *not* set, then Tor should follow ExcludeNodes
2865 whenever it can, except when it must use an excluded node to
2866 perform self-tests, connect to a hidden service, provide a
2867 hidden service, fulfill a .exit request, upload directory
2868 information, or fetch directory information.
2869 Collectively, the changes to implement the behavior fix bug 1090.
2870 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
2871 a node is listed in both, it's treated as excluded.
2872 - ExcludeNodes now applies to directory nodes -- as a preference if
2873 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
2874 Don't exclude all the directory authorities and set StrictNodes to 1
2875 unless you really want your Tor to break.
2876 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
2877 - ExcludeExitNodes now overrides .exit requests.
2878 - We don't use bridges listed in ExcludeNodes.
2879 - When StrictNodes is 1:
2880 . We now apply ExcludeNodes to hidden service introduction points
2881 and to rendezvous points selected by hidden service users. This
2882 can make your hidden service less reliable: use it with caution!
2883 . If we have used ExcludeNodes on ourself, do not try relay
2884 reachability self-tests.
2885 . If we have excluded all the directory authorities, we will not
2886 even try to upload our descriptor if we're a relay.
2887 . Do not honor .exit requests to an excluded node.
2888 - Remove a misfeature that caused us to ignore the Fast/Stable flags
2889 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
2890 - When the set of permitted nodes changes, we now remove any mappings
2891 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
2893 - We never cannibalize a circuit that had excluded nodes on it, even
2894 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
2895 - Revert a change where we would be laxer about attaching streams to
2896 circuits than when building the circuits. This was meant to prevent
2897 a set of bugs where streams were never attachable, but our improved
2898 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
2899 - Keep track of how many times we launch a new circuit to handle a
2900 given stream. Too many launches could indicate an inconsistency
2901 between our "launch a circuit to handle this stream" logic and our
2902 "attach this stream to one of the available circuits" logic.
2903 - Improve log messages related to excluded nodes.
2906 - Fix a spurious warning when moving from a short month to a long
2907 month on relays with month-based BandwidthAccounting. Bugfix on
2908 0.2.2.17-alpha; fixes bug 3020.
2909 - When a client finds that an origin circuit has run out of 16-bit
2910 stream IDs, we now mark it as unusable for new streams. Previously,
2911 we would try to close the entire circuit. Bugfix on 0.0.6.
2912 - Add a forgotten cast that caused a compile warning on OS X 10.6.
2913 Bugfix on 0.2.2.24-alpha.
2914 - Be more careful about reporting the correct error from a failed
2915 connect() system call. Under some circumstances, it was possible to
2916 look at an incorrect value for errno when sending the end reason.
2917 Bugfix on 0.1.0.1-rc.
2918 - Correctly handle an "impossible" overflow cases in connection byte
2919 counting, where we write or read more than 4GB on an edge connection
2920 in a single second. Bugfix on 0.1.2.8-beta.
2921 - Correct the warning displayed when a rendezvous descriptor exceeds
2922 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
2924 - Clients and hidden services now use HSDir-flagged relays for hidden
2925 service descriptor downloads and uploads even if the relays have no
2926 DirPort set and the client has disabled TunnelDirConns. This will
2927 eventually allow us to give the HSDir flag to relays with no
2928 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
2929 - Downgrade "no current certificates known for authority" message from
2930 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
2931 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
2932 2917. Bugfix on 0.1.1.1-alpha.
2933 - Only limit the lengths of single HS descriptors, even when multiple
2934 HS descriptors are published to an HSDir relay in a single POST
2935 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
2936 - Write the current time into the LastWritten line in our state file,
2937 rather than the time from the previous write attempt. Also, stop
2938 trying to use a time of -1 in our log statements. Fixes bug 3039;
2939 bugfix on 0.2.2.14-alpha.
2940 - Be more consistent in our treatment of file system paths. "~" should
2941 get expanded to the user's home directory in the Log config option.
2942 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
2943 feature for the -f and --DataDirectory options.
2946 - Make sure every relay writes a state file at least every 12 hours.
2947 Previously, a relay could go for weeks without writing its state
2948 file, and on a crash could lose its bandwidth history, capacity
2949 estimates, client country statistics, and so on. Addresses bug 3012.
2950 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
2951 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
2952 clients are already deprecated because of security bugs.
2953 - Don't allow v0 hidden service authorities to act as clients.
2954 Required by fix for bug 3000.
2955 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
2956 by fix for bug 3000.
2957 - Ensure that no empty [dirreq-](read|write)-history lines are added
2958 to an extrainfo document. Implements ticket 2497.
2960 o Code simplification and refactoring:
2961 - Remove workaround code to handle directory responses from servers
2962 that had bug 539 (they would send HTTP status 503 responses _and_
2963 send a body too). Since only server versions before
2964 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
2965 keep the workaround in place.
2966 - Remove the old 'fuzzy time' logic. It was supposed to be used for
2967 handling calculations where we have a known amount of clock skew and
2968 an allowed amount of unknown skew. But we only used it in three
2969 places, and we never adjusted the known/unknown skew values. This is
2970 still something we might want to do someday, but if we do, we'll
2971 want to do it differently.
2972 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
2973 None of the cases where we did this before were wrong, but by making
2974 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
2975 - Use GetTempDir to find the proper temporary directory location on
2976 Windows when generating temporary files for the unit tests. Patch by
2980 Changes in version 0.2.2.24-alpha - 2011-04-08
2981 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
2982 prevented Tor clients from effectively using "multihomed" bridges,
2983 that is, bridges that listen on multiple ports or IP addresses so users
2984 can continue to use some of their addresses even if others get blocked.
2987 - Fix a bug where bridge users who configure the non-canonical
2988 address of a bridge automatically switch to its canonical
2989 address. If a bridge listens at more than one address, it should be
2990 able to advertise those addresses independently and any non-blocked
2991 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
2993 - If you configured Tor to use bridge A, and then quit and
2994 configured Tor to use bridge B instead, it would happily continue
2995 to use bridge A if it's still reachable. While this behavior is
2996 a feature if your goal is connectivity, in some scenarios it's a
2997 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
2998 - Directory authorities now use data collected from their own
2999 uptime observations when choosing whether to assign the HSDir flag
3000 to relays, instead of trusting the uptime value the relay reports in
3001 its descriptor. This change helps prevent an attack where a small
3002 set of nodes with frequently-changing identity keys can blackhole
3003 a hidden service. (Only authorities need upgrade; others will be
3004 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
3007 - When we restart our relay, we might get a successful connection
3008 from the outside before we've started our reachability tests,
3009 triggering a warning: "ORPort found reachable, but I have no
3010 routerinfo yet. Failing to inform controller of success." This
3011 bug was harmless unless Tor is running under a controller
3012 like Vidalia, in which case the controller would never get a
3013 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3015 - Make directory authorities more accurate at recording when
3016 relays that have failed several reachability tests became
3017 unreachable, so we can provide more accuracy at assigning Stable,
3018 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
3019 - Fix an issue that prevented static linking of libevent on
3020 some platforms (notably Linux). Fixes bug 2698; bugfix on
3021 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
3022 the --with-static-libevent configure option).
3023 - We now ask the other side of a stream (the client or the exit)
3024 for more data on that stream when the amount of queued data on
3025 that stream dips low enough. Previously, we wouldn't ask the
3026 other side for more data until either it sent us more data (which
3027 it wasn't supposed to do if it had exhausted its window!) or we
3028 had completely flushed all our queued data. This flow control fix
3029 should improve throughput. Fixes bug 2756; bugfix on the earliest
3030 released versions of Tor (svn commit r152).
3031 - Avoid a double-mark-for-free warning when failing to attach a
3032 transparent proxy connection. (We thought we had fixed this in
3033 0.2.2.23-alpha, but it turns out our fix was checking the wrong
3034 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
3035 bug) and 0.2.2.23-alpha (the incorrect fix).
3036 - When warning about missing zlib development packages during compile,
3037 give the correct package names. Bugfix on 0.2.0.1-alpha.
3040 - Directory authorities now log the source of a rejected POSTed v3
3042 - Make compilation with clang possible when using
3043 --enable-gcc-warnings by removing two warning options that clang
3044 hasn't implemented yet and by fixing a few warnings. Implements
3046 - When expiring circuits, use microsecond timers rather than
3047 one-second timers. This can avoid an unpleasant situation where a
3048 circuit is launched near the end of one second and expired right
3049 near the beginning of the next, and prevent fluctuations in circuit
3051 - Use computed circuit-build timeouts to decide when to launch
3052 parallel introduction circuits for hidden services. (Previously,
3053 we would retry after 15 seconds.)
3054 - Update to the April 1 2011 Maxmind GeoLite Country database.
3057 - Create the /var/run/tor directory on startup on OpenSUSE if it is
3058 not already created. Patch from Andreas Stieger. Fixes bug 2573.
3060 o Documentation changes:
3061 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
3062 - Resolve all doxygen warnings except those for missing documentation.
3064 - Add doxygen documentation for more functions, fields, and types.
3067 Changes in version 0.2.2.23-alpha - 2011-03-08
3068 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
3069 they restart they don't lose their bandwidth capacity estimate. This
3070 release also fixes a diverse set of user-facing bugs, ranging from
3071 relays overrunning their rate limiting to clients falsely warning about
3072 clock skew to bridge descriptor leaks by our bridge directory authority.
3075 - Stop sending a CLOCK_SKEW controller status event whenever
3076 we fetch directory information from a relay that has a wrong clock.
3077 Instead, only inform the controller when it's a trusted authority
3078 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3079 the rest of bug 1074.
3080 - Fix an assert in parsing router descriptors containing IPv6
3081 addresses. This one took down the directory authorities when
3082 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3083 - Make the bridge directory authority refuse to answer directory
3084 requests for "all" descriptors. It used to include bridge
3085 descriptors in its answer, which was a major information leak.
3086 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3087 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3088 Tor would ignore their RelayBandwidthBurst setting,
3089 potentially using more bandwidth than expected. Bugfix on
3090 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3091 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3092 hidserv" in her torrc. The 'hidserv' argument never controlled
3093 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3096 - Relays now save observed peak bandwidth throughput rates to their
3097 state file (along with total usage, which was already saved)
3098 so that they can determine their correct estimated bandwidth on
3099 restart. Resolves bug 1863, where Tor relays would reset their
3100 estimated bandwidth to 0 after restarting.
3101 - Directory authorities now take changes in router IP address and
3102 ORPort into account when determining router stability. Previously,
3103 if a router changed its IP or ORPort, the authorities would not
3104 treat it as having any downtime for the purposes of stability
3105 calculation, whereas clients would experience downtime since the
3106 change could take a while to propagate to them. Resolves issue 1035.
3107 - Enable Address Space Layout Randomization (ASLR) and Data Execution
3108 Prevention (DEP) by default on Windows to make it harder for
3109 attackers to exploit vulnerabilities. Patch from John Brooks.
3111 o Minor bugfixes (on 0.2.1.x and earlier):
3112 - Fix a rare crash bug that could occur when a client was configured
3113 with a large number of bridges. Fixes bug 2629; bugfix on
3114 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3115 - Avoid a double mark-for-free warning when failing to attach a
3116 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
3118 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
3119 found by "cypherpunks". This bug was introduced before the first
3120 Tor release, in svn commit r110.
3121 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
3122 don't mention them in the manpage. Fixes bug 2450; issue
3123 spotted by keb and G-Lo.
3124 - Fix a bug in bandwidth history state parsing that could have been
3125 triggered if a future version of Tor ever changed the timing
3126 granularity at which bandwidth history is measured. Bugfix on
3128 - When a relay decides that its DNS is too broken for it to serve
3129 as an exit server, it advertised itself as a non-exit, but
3130 continued to act as an exit. This could create accidental
3131 partitioning opportunities for users. Instead, if a relay is
3132 going to advertise reject *:* as its exit policy, it should
3133 really act with exit policy "reject *:*". Fixes bug 2366.
3134 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
3135 - In the special case where you configure a public exit relay as your
3136 bridge, Tor would be willing to use that exit relay as the last
3137 hop in your circuit as well. Now we fail that circuit instead.
3138 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
3139 - Fix a bug with our locking implementation on Windows that couldn't
3140 correctly detect when a file was already locked. Fixes bug 2504,
3141 bugfix on 0.2.1.6-alpha.
3142 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
3143 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
3145 - Set target port in get_interface_address6() correctly. Bugfix
3146 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
3147 - Directory authorities are now more robust to hops back in time
3148 when calculating router stability. Previously, if a run of uptime
3149 or downtime appeared to be negative, the calculation could give
3150 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
3152 - Fix an assert that got triggered when using the TestingTorNetwork
3153 configuration option and then issuing a GETINFO config-text control
3154 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
3156 o Minor bugfixes (on 0.2.2.x):
3157 - Clients should not weight BadExit nodes as Exits in their node
3158 selection. Similarly, directory authorities should not count BadExit
3159 bandwidth as Exit bandwidth when computing bandwidth-weights.
3160 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
3161 - Correctly clear our dir_read/dir_write history when there is an
3162 error parsing any bw history value from the state file. Bugfix on
3164 - Resolve a bug in verifying signatures of directory objects
3165 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
3166 Fixes bug 2409. Found by "piebeer".
3167 - Bridge authorities no longer crash on SIGHUP when they try to
3168 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
3172 - Log less aggressively about circuit timeout changes, and improve
3173 some other circuit timeout messages. Resolves bug 2004.
3174 - Log a little more clearly about the times at which we're no longer
3175 accepting new connections. Resolves bug 2181.
3176 - Reject attempts at the client side to open connections to private
3177 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
3178 a randomly chosen exit node. Attempts to do so are always
3179 ill-defined, generally prevented by exit policies, and usually
3180 in error. This will also help to detect loops in transparent
3181 proxy configurations. You can disable this feature by setting
3182 "ClientRejectInternalAddresses 0" in your torrc.
3183 - Always treat failure to allocate an RSA key as an unrecoverable
3185 - Update to the March 1 2011 Maxmind GeoLite Country database.
3187 o Minor features (log subsystem):
3188 - Add documentation for configuring logging at different severities in
3189 different log domains. We've had this feature since 0.2.1.1-alpha,
3190 but for some reason it never made it into the manpage. Fixes
3192 - Make it simpler to specify "All log domains except for A and B".
3193 Previously you needed to say "[*,~A,~B]". Now you can just say
3195 - Add a "LogMessageDomains 1" option to include the domains of log
3196 messages along with the messages. Without this, there's no way
3197 to use log domains without reading the source or doing a lot
3200 o Packaging changes:
3201 - Stop shipping the Tor specs files and development proposal documents
3202 in the tarball. They are now in a separate git repository at
3203 git://git.torproject.org/torspec.git
3206 Changes in version 0.2.1.30 - 2011-02-23
3207 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
3208 change is a slight tweak to Tor's TLS handshake that makes relays
3209 and bridges that run this new version reachable from Iran again.
3210 We don't expect this tweak will win the arms race long-term, but it
3211 buys us time until we roll out a better solution.
3214 - Stop sending a CLOCK_SKEW controller status event whenever
3215 we fetch directory information from a relay that has a wrong clock.
3216 Instead, only inform the controller when it's a trusted authority
3217 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3218 the rest of bug 1074.
3219 - Fix a bounds-checking error that could allow an attacker to
3220 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3222 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3223 Tor would ignore their RelayBandwidthBurst setting,
3224 potentially using more bandwidth than expected. Bugfix on
3225 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3226 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3227 hidserv" in her torrc. The 'hidserv' argument never controlled
3228 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3231 - Adjust our TLS Diffie-Hellman parameters to match those used by
3233 - Update to the February 1 2011 Maxmind GeoLite Country database.
3236 - Check for and reject overly long directory certificates and
3237 directory tokens before they have a chance to hit any assertions.
3238 Bugfix on 0.2.1.28. Found by "doorss".
3239 - Bring the logic that gathers routerinfos and assesses the
3240 acceptability of circuits into line. This prevents a Tor OP from
3241 getting locked in a cycle of choosing its local OR as an exit for a
3242 path (due to a .exit request) and then rejecting the circuit because
3243 its OR is not listed yet. It also prevents Tor clients from using an
3244 OR running in the same instance as an exit (due to a .exit request)
3245 if the OR does not meet the same requirements expected of an OR
3246 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
3248 o Packaging changes:
3249 - Stop shipping the Tor specs files and development proposal documents
3250 in the tarball. They are now in a separate git repository at
3251 git://git.torproject.org/torspec.git
3252 - Do not include Git version tags as though they are SVN tags when
3253 generating a tarball from inside a repository that has switched
3254 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3257 Changes in version 0.2.2.22-alpha - 2011-01-25
3258 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
3259 main other change is a slight tweak to Tor's TLS handshake that makes
3260 relays and bridges that run this new version reachable from Iran again.
3261 We don't expect this tweak will win the arms race long-term, but it
3262 will buy us a bit more time until we roll out a better solution.
3265 - Fix a bounds-checking error that could allow an attacker to
3266 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3268 - Don't assert when changing from bridge to relay or vice versa
3269 via the controller. The assert happened because we didn't properly
3270 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
3271 bug 2433. Reported by bastik.
3274 - Adjust our TLS Diffie-Hellman parameters to match those used by
3276 - Provide a log message stating which geoip file we're parsing
3277 instead of just stating that we're parsing the geoip file.
3278 Implements ticket 2432.
3281 - Check for and reject overly long directory certificates and
3282 directory tokens before they have a chance to hit any assertions.
3283 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
3286 Changes in version 0.2.2.21-alpha - 2011-01-15
3287 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
3288 continues our recent code security audit work. The main fix resolves
3289 a remote heap overflow vulnerability that can allow remote code
3290 execution (CVE-2011-0427). Other fixes address a variety of assert
3291 and crash bugs, most of which we think are hard to exploit remotely.
3293 o Major bugfixes (security), also included in 0.2.1.29:
3294 - Fix a heap overflow bug where an adversary could cause heap
3295 corruption. This bug probably allows remote code execution
3296 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3298 - Prevent a denial-of-service attack by disallowing any
3299 zlib-compressed data whose compression factor is implausibly
3300 high. Fixes part of bug 2324; reported by "doorss".
3301 - Zero out a few more keys in memory before freeing them. Fixes
3302 bug 2384 and part of bug 2385. These key instances found by
3303 "cypherpunks", based on Andrew Case's report about being able
3304 to find sensitive data in Tor's memory space if you have enough
3305 permissions. Bugfix on 0.0.2pre9.
3307 o Major bugfixes (crashes), also included in 0.2.1.29:
3308 - Prevent calls to Libevent from inside Libevent log handlers.
3309 This had potential to cause a nasty set of crashes, especially
3310 if running Libevent with debug logging enabled, and running
3311 Tor with a controller watching for low-severity log messages.
3312 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3313 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3314 underflow errors there too. Fixes the other part of bug 2324.
3315 - Fix a bug where we would assert if we ever had a
3316 cached-descriptors.new file (or another file read directly into
3317 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3318 on 0.2.1.25. Found by doorss.
3319 - Fix some potential asserts and parsing issues with grossly
3320 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3323 o Minor bugfixes (other), also included in 0.2.1.29:
3324 - Fix a bug with handling misformed replies to reverse DNS lookup
3325 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3326 bug reported by doorss.
3327 - Fix compilation on mingw when a pthreads compatibility library
3328 has been installed. (We don't want to use it, so we shouldn't
3329 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3330 - Fix a bug where we would declare that we had run out of virtual
3331 addresses when the address space was only half-exhausted. Bugfix
3333 - Correctly handle the case where AutomapHostsOnResolve is set but
3334 no virtual addresses are available. Fixes bug 2328; bugfix on
3335 0.1.2.1-alpha. Bug found by doorss.
3336 - Correctly handle wrapping around when we run out of virtual
3337 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
3339 o Minor features, also included in 0.2.1.29:
3340 - Update to the January 1 2011 Maxmind GeoLite Country database.
3341 - Introduce output size checks on all of our decryption functions.
3343 o Build changes, also included in 0.2.1.29:
3344 - Tor does not build packages correctly with Automake 1.6 and earlier;
3345 added a check to Makefile.am to make sure that we're building with
3346 Automake 1.7 or later.
3347 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
3348 because we built it with a too-old version of automake. Thus that
3349 release broke ./configure --enable-openbsd-malloc, which is popular
3350 among really fast exit relays on Linux.
3352 o Major bugfixes, new in 0.2.2.21-alpha:
3353 - Prevent crash/heap corruption when the cbtnummodes consensus
3354 parameter is set to 0 or large values. Fixes bug 2317; bugfix
3357 o Major features, new in 0.2.2.21-alpha:
3358 - Introduce minimum/maximum values that clients will believe
3359 from the consensus. Now we'll have a better chance to avoid crashes
3360 or worse when a consensus param has a weird value.
3362 o Minor features, new in 0.2.2.21-alpha:
3363 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
3364 used on bridges, and it makes bridge scanning somewhat easier.
3365 - If writing the state file to disk fails, wait up to an hour before
3366 retrying again, rather than trying again each second. Fixes bug
3367 2346; bugfix on Tor 0.1.1.3-alpha.
3368 - Make Libevent log messages get delivered to controllers later,
3369 and not from inside the Libevent log handler. This prevents unsafe
3370 reentrant Libevent calls while still letting the log messages
3372 - Detect platforms that brokenly use a signed size_t, and refuse to
3373 build there. Found and analyzed by doorss and rransom.
3374 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
3377 o Minor bugfixes, new in 0.2.2.21-alpha:
3378 - Handle SOCKS messages longer than 128 bytes long correctly, rather
3379 than waiting forever for them to finish. Fixes bug 2330; bugfix
3380 on 0.2.0.16-alpha. Found by doorss.
3381 - Add assertions to check for overflow in arguments to
3382 base32_encode() and base32_decode(); fix a signed-unsigned
3383 comparison there too. These bugs are not actually reachable in Tor,
3384 but it's good to prevent future errors too. Found by doorss.
3385 - Correctly detect failures to create DNS requests when using Libevent
3386 versions before v2. (Before Libevent 2, we used our own evdns
3387 implementation. Its return values for Libevent's evdns_resolve_*()
3388 functions are not consistent with those from Libevent.) Fixes bug
3389 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
3391 o Documentation, new in 0.2.2.21-alpha:
3392 - Document the default socks host and port (127.0.0.1:9050) for
3396 Changes in version 0.2.1.29 - 2011-01-15
3397 Tor 0.2.1.29 continues our recent code security audit work. The main
3398 fix resolves a remote heap overflow vulnerability that can allow remote
3399 code execution. Other fixes address a variety of assert and crash bugs,
3400 most of which we think are hard to exploit remotely.
3402 o Major bugfixes (security):
3403 - Fix a heap overflow bug where an adversary could cause heap
3404 corruption. This bug probably allows remote code execution
3405 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3407 - Prevent a denial-of-service attack by disallowing any
3408 zlib-compressed data whose compression factor is implausibly
3409 high. Fixes part of bug 2324; reported by "doorss".
3410 - Zero out a few more keys in memory before freeing them. Fixes
3411 bug 2384 and part of bug 2385. These key instances found by
3412 "cypherpunks", based on Andrew Case's report about being able
3413 to find sensitive data in Tor's memory space if you have enough
3414 permissions. Bugfix on 0.0.2pre9.
3416 o Major bugfixes (crashes):
3417 - Prevent calls to Libevent from inside Libevent log handlers.
3418 This had potential to cause a nasty set of crashes, especially
3419 if running Libevent with debug logging enabled, and running
3420 Tor with a controller watching for low-severity log messages.
3421 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3422 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3423 underflow errors there too. Fixes the other part of bug 2324.
3424 - Fix a bug where we would assert if we ever had a
3425 cached-descriptors.new file (or another file read directly into
3426 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3427 on 0.2.1.25. Found by doorss.
3428 - Fix some potential asserts and parsing issues with grossly
3429 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3432 o Minor bugfixes (other):
3433 - Fix a bug with handling misformed replies to reverse DNS lookup
3434 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3435 bug reported by doorss.
3436 - Fix compilation on mingw when a pthreads compatibility library
3437 has been installed. (We don't want to use it, so we shouldn't
3438 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3439 - Fix a bug where we would declare that we had run out of virtual
3440 addresses when the address space was only half-exhausted. Bugfix
3442 - Correctly handle the case where AutomapHostsOnResolve is set but
3443 no virtual addresses are available. Fixes bug 2328; bugfix on
3444 0.1.2.1-alpha. Bug found by doorss.
3445 - Correctly handle wrapping around to when we run out of virtual
3446 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
3447 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
3448 because we built it with a too-old version of automake. Thus that
3449 release broke ./configure --enable-openbsd-malloc, which is popular
3450 among really fast exit relays on Linux.
3453 - Update to the January 1 2011 Maxmind GeoLite Country database.
3454 - Introduce output size checks on all of our decryption functions.
3457 - Tor does not build packages correctly with Automake 1.6 and earlier;
3458 added a check to Makefile.am to make sure that we're building with
3459 Automake 1.7 or later.
3462 Changes in version 0.2.2.20-alpha - 2010-12-17
3463 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
3464 exploitable bugs. We also fix a variety of other significant bugs,
3465 change the IP address for one of our directory authorities, and update
3466 the minimum version that Tor relays must run to join the network.
3469 - Fix a remotely exploitable bug that could be used to crash instances
3470 of Tor remotely by overflowing on the heap. Remote-code execution
3471 hasn't been confirmed, but can't be ruled out. Everyone should
3472 upgrade. Bugfix on the 0.1.1 series and later.
3473 - Fix a bug that could break accounting on 64-bit systems with large
3474 time_t values, making them hibernate for impossibly long intervals.
3475 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
3476 - Fix a logic error in directory_fetches_from_authorities() that
3477 would cause all _non_-exits refusing single-hop-like circuits
3478 to fetch from authorities, when we wanted to have _exits_ fetch
3479 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
3481 - Fix a stream fairness bug that would cause newer streams on a given
3482 circuit to get preference when reading bytes from the origin or
3483 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
3484 introduced before the first Tor release, in svn revision r152.
3486 o Directory authority changes:
3487 - Change IP address and ports for gabelmoo (v3 directory authority).
3490 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
3491 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
3492 - Fix an off-by-one error in calculating some controller command
3493 argument lengths. Fortunately, this mistake is harmless since
3494 the controller code does redundant NUL termination too. Found by
3495 boboper. Bugfix on 0.1.1.1-alpha.
3496 - Do not dereference NULL if a bridge fails to build its
3497 extra-info descriptor. Found by an anonymous commenter on
3498 Trac. Bugfix on 0.2.2.19-alpha.
3501 - Update to the December 1 2010 Maxmind GeoLite Country database.
3502 - Directory authorities now reject relays running any versions of
3503 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
3504 known bugs that keep RELAY_EARLY cells from working on rendezvous
3505 circuits. Followup to fix for bug 2081.
3506 - Directory authorities now reject relays running any version of Tor
3507 older than 0.2.0.26-rc. That version is the earliest that fetches
3508 current directory information correctly. Fixes bug 2156.
3509 - Report only the top 10 ports in exit-port stats in order not to
3510 exceed the maximum extra-info descriptor length of 50 KB. Implements
3514 Changes in version 0.2.1.28 - 2010-12-17
3515 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
3516 exploitable bugs. We also took this opportunity to change the IP address
3517 for one of our directory authorities, and to update the geoip database
3521 - Fix a remotely exploitable bug that could be used to crash instances
3522 of Tor remotely by overflowing on the heap. Remote-code execution
3523 hasn't been confirmed, but can't be ruled out. Everyone should
3524 upgrade. Bugfix on the 0.1.1 series and later.
3526 o Directory authority changes:
3527 - Change IP address and ports for gabelmoo (v3 directory authority).
3530 - Update to the December 1 2010 Maxmind GeoLite Country database.
3533 Changes in version 0.2.1.27 - 2010-11-23
3534 Yet another OpenSSL security patch broke its compatibility with Tor:
3535 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
3536 also took this opportunity to fix several crash bugs, integrate a new
3537 directory authority, and update the bundled GeoIP database.
3540 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
3541 No longer set the tlsext_host_name extension on server SSL objects;
3542 but continue to set it on client SSL objects. Our goal in setting
3543 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
3544 bugfix on 0.2.1.1-alpha.
3545 - Do not log messages to the controller while shrinking buffer
3546 freelists. Doing so would sometimes make the controller connection
3547 try to allocate a buffer chunk, which would mess up the internals
3548 of the freelist and cause an assertion failure. Fixes bug 1125;
3549 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
3550 - Learn our external IP address when we're a relay or bridge, even if
3551 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
3552 where we introduced bridge relays that don't need to publish to
3553 be useful. Fixes bug 2050.
3554 - Do even more to reject (and not just ignore) annotations on
3555 router descriptors received anywhere but from the cache. Previously
3556 we would ignore such annotations at first, but cache them to disk
3557 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
3558 - When you're using bridges and your network goes away and your
3559 bridges get marked as down, recover when you attempt a new socks
3560 connection (if the network is back), rather than waiting up to an
3561 hour to try fetching new descriptors for your bridges. Bugfix on
3562 0.2.0.3-alpha; fixes bug 1981.
3565 - Move to the November 2010 Maxmind GeoLite country db (rather
3566 than the June 2009 ip-to-country GeoIP db) for our statistics that
3567 count how many users relays are seeing from each country. Now we'll
3568 have more accurate data, especially for many African countries.
3570 o New directory authorities:
3571 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
3575 - Fix an assertion failure that could occur in directory caches or
3576 bridge users when using a very short voting interval on a testing
3577 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
3579 - Enforce multiplicity rules when parsing annotations. Bugfix on
3580 0.2.0.8-alpha. Found by piebeer.
3581 - Allow handshaking OR connections to take a full KeepalivePeriod
3582 seconds to handshake. Previously, we would close them after
3583 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
3584 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
3586 - When building with --enable-gcc-warnings on OpenBSD, disable
3587 warnings in system headers. This makes --enable-gcc-warnings
3588 pass on OpenBSD 4.8.
3591 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
3592 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
3593 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
3594 Servers can start sending this code when enough clients recognize
3595 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
3596 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
3597 Patch from mingw-san.
3600 - Remove the old debian/ directory from the main Tor distribution.
3601 The official Tor-for-debian git repository lives at the URL
3602 https://git.torproject.org/debian/tor.git
3603 - Stop shipping the old doc/website/ directory in the tarball. We
3604 changed the website format in late 2010, and what we shipped in
3605 0.2.1.26 really wasn't that useful anyway.
3608 Changes in version 0.2.2.19-alpha - 2010-11-22
3609 Yet another OpenSSL security patch broke its compatibility with Tor:
3610 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
3613 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
3614 No longer set the tlsext_host_name extension on server SSL objects;
3615 but continue to set it on client SSL objects. Our goal in setting
3616 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
3617 bugfix on 0.2.1.1-alpha.
3620 - Try harder not to exceed the maximum length of 50 KB when writing
3621 statistics to extra-info descriptors. This bug was triggered by very
3622 fast relays reporting exit-port, entry, and dirreq statistics.
3623 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
3624 - Publish a router descriptor even if generating an extra-info
3625 descriptor fails. Previously we would not publish a router
3626 descriptor without an extra-info descriptor; this can cause fast
3627 exit relays collecting exit-port statistics to drop from the
3628 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
3631 Changes in version 0.2.2.18-alpha - 2010-11-16
3632 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
3633 us lately, makes unpublished bridge relays able to detect their IP
3634 address, and fixes a wide variety of other bugs to get us much closer
3635 to a stable release.
3638 - Do even more to reject (and not just ignore) annotations on
3639 router descriptors received anywhere but from the cache. Previously
3640 we would ignore such annotations at first, but cache them to disk
3641 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
3642 - Do not log messages to the controller while shrinking buffer
3643 freelists. Doing so would sometimes make the controller connection
3644 try to allocate a buffer chunk, which would mess up the internals
3645 of the freelist and cause an assertion failure. Fixes bug 1125;
3646 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
3647 - Learn our external IP address when we're a relay or bridge, even if
3648 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
3649 where we introduced bridge relays that don't need to publish to
3650 be useful. Fixes bug 2050.
3651 - Maintain separate TLS contexts and certificates for incoming and
3652 outgoing connections in bridge relays. Previously we would use the
3653 same TLS contexts and certs for incoming and outgoing connections.
3654 Bugfix on 0.2.0.3-alpha; addresses bug 988.
3655 - Maintain separate identity keys for incoming and outgoing TLS
3656 contexts in bridge relays. Previously we would use the same
3657 identity keys for incoming and outgoing TLS contexts. Bugfix on
3658 0.2.0.3-alpha; addresses the other half of bug 988.
3659 - Avoid an assertion failure when we as an authority receive a
3660 duplicate upload of a router descriptor that we already have,
3661 but which we previously considered an obsolete descriptor.
3662 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
3663 - Avoid a crash bug triggered by looking at a dangling pointer while
3664 setting the network status consensus. Found by Robert Ransom.
3665 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
3666 - Fix a logic error where servers that _didn't_ act as exits would
3667 try to keep their server lists more aggressively up to date than
3668 exits, when it was supposed to be the other way around. Bugfix
3671 o Minor bugfixes (on Tor 0.2.1.x and earlier):
3672 - When we're trying to guess whether we know our IP address as
3673 a relay, we would log various ways that we failed to guess
3674 our address, but never log that we ended up guessing it
3675 successfully. Now add a log line to help confused and anxious
3676 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
3677 - Bring the logic that gathers routerinfos and assesses the
3678 acceptability of circuits into line. This prevents a Tor OP from
3679 getting locked in a cycle of choosing its local OR as an exit for a
3680 path (due to a .exit request) and then rejecting the circuit because
3681 its OR is not listed yet. It also prevents Tor clients from using an
3682 OR running in the same instance as an exit (due to a .exit request)
3683 if the OR does not meet the same requirements expected of an OR
3684 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
3685 - Correctly describe errors that occur when generating a TLS object.
3686 Previously we would attribute them to a failure while generating a
3687 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
3689 - Enforce multiplicity rules when parsing annotations. Bugfix on
3690 0.2.0.8-alpha. Found by piebeer.
3691 - Fix warnings that newer versions of autoconf produced during
3692 ./autogen.sh. These warnings appear to be harmless in our case,
3693 but they were extremely verbose. Fixes bug 2020.
3695 o Minor bugfixes (on Tor 0.2.2.x):
3696 - Enable protection of small arrays whenever we build with gcc
3697 hardening features, not only when also building with warnings
3698 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
3701 - Make hidden services work better in private Tor networks by not
3702 requiring any uptime to join the hidden service descriptor
3703 DHT. Implements ticket 2088.
3704 - Rate-limit the "your application is giving Tor only an IP address"
3705 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
3706 - When AllowSingleHopExits is set, print a warning to explain to the
3707 relay operator why most clients are avoiding her relay.
3708 - Update to the November 1 2010 Maxmind GeoLite Country database.
3710 o Code simplifications and refactoring:
3711 - When we fixed bug 1038 we had to put in a restriction not to send
3712 RELAY_EARLY cells on rend circuits. This was necessary as long
3713 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
3714 active. Now remove this obsolete check. Resolves bug 2081.
3715 - Some options used different conventions for uppercasing of acronyms
3716 when comparing manpage and source. Fix those in favor of the
3717 manpage, as it makes sense to capitalize acronyms.
3718 - Remove the torrc.complete file. It hasn't been kept up to date
3719 and users will have better luck checking out the manpage.
3720 - Remove the obsolete "NoPublish" option; it has been flagged
3721 as obsolete and has produced a warning since 0.1.1.18-rc.
3722 - Remove everything related to building the expert bundle for OS X.
3723 It has confused many users, doesn't work right on OS X 10.6,
3724 and is hard to get rid of once installed. Resolves bug 1274.
3727 Changes in version 0.2.2.17-alpha - 2010-09-30
3728 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
3729 to use one-hop circuits (which can put the exit relays at higher risk,
3730 plus unbalance the network); fixes a big bug in bandwidth accounting
3731 for relays that want to limit their monthly bandwidth use; fixes a
3732 big pile of bugs in how clients tolerate temporary network failure;
3733 and makes our adaptive circuit build timeout feature (which improves
3734 client performance if your network is fast while not breaking things
3735 if your network is slow) better handle bad networks.
3738 - Exit relays now try harder to block exit attempts from unknown
3739 relays, to make it harder for people to use them as one-hop proxies
3740 a la tortunnel. Controlled by the refuseunknownexits consensus
3741 parameter (currently enabled), or you can override it on your
3742 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
3744 o Major bugfixes (0.2.1.x and earlier):
3745 - Fix a bug in bandwidth accounting that could make us use twice
3746 the intended bandwidth when our interval start changes due to
3747 daylight saving time. Now we tolerate skew in stored vs computed
3748 interval starts: if the start of the period changes by no more than
3749 50% of the period's duration, we remember bytes that we transferred
3750 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
3751 - Always search the Windows system directory for system DLLs, and
3752 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
3753 - When you're using bridges and your network goes away and your
3754 bridges get marked as down, recover when you attempt a new socks
3755 connection (if the network is back), rather than waiting up to an
3756 hour to try fetching new descriptors for your bridges. Bugfix on
3757 0.2.0.3-alpha; fixes bug 1981.
3759 o Major bugfixes (on 0.2.2.x):
3760 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
3762 - Fix a segfault that could happen when operating a bridge relay with
3763 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
3764 - The consensus bandwidth-weights (used by clients to choose fast
3765 relays) entered an unexpected edge case in September where
3766 Exits were much scarcer than Guards, resulting in bad weight
3767 recommendations. Now we compute them using new constraints that
3768 should succeed in all cases. Also alter directory authorities to
3769 not include the bandwidth-weights line if they fail to produce
3770 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
3771 - When weighting bridges during path selection, we used to trust
3772 the bandwidths they provided in their descriptor, only capping them
3773 at 10MB/s. This turned out to be problematic for two reasons:
3774 Bridges could claim to handle a lot more traffic then they
3775 actually would, thus making more clients pick them and have a
3776 pretty effective DoS attack. The other issue is that new bridges
3777 that might not have a good estimate for their bw capacity yet
3778 would not get used at all unless no other bridges are available
3779 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
3781 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
3782 - Ignore cannibalized circuits when recording circuit build times.
3783 This should provide for a minor performance improvement for hidden
3784 service users using 0.2.2.14-alpha, and should remove two spurious
3785 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
3786 - Simplify the logic that causes us to decide if the network is
3787 unavailable for purposes of recording circuit build times. If we
3788 receive no cells whatsoever for the entire duration of a circuit's
3789 full measured lifetime, the network is probably down. Also ignore
3790 one-hop directory fetching circuit timeouts when calculating our
3791 circuit build times. These changes should hopefully reduce the
3792 cases where we see ridiculous circuit build timeouts for people
3793 with spotty wireless connections. Fixes part of bug 1772; bugfix
3795 - Prevent the circuit build timeout from becoming larger than
3796 the maximum build time we have ever seen. Also, prevent the time
3797 period for measurement circuits from becoming larger than twice that
3798 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
3801 - When we run out of directory information such that we can't build
3802 circuits, but then get enough that we can build circuits, log when
3803 we actually construct a circuit, so the user has a better chance of
3804 knowing what's going on. Fixes bug 1362.
3805 - Be more generous with how much bandwidth we'd use up (with
3806 accounting enabled) before entering "soft hibernation". Previously,
3807 we'd refuse new connections and circuits once we'd used up 95% of
3808 our allotment. Now, we use up 95% of our allotment, AND make sure
3809 that we have no more than 500MB (or 3 hours of expected traffic,
3810 whichever is lower) remaining before we enter soft hibernation.
3811 - If we've configured EntryNodes and our network goes away and/or all
3812 our entrynodes get marked down, optimistically retry them all when
3813 a new socks application request appears. Fixes bug 1882.
3814 - Add some more defensive programming for architectures that can't
3815 handle unaligned integer accesses. We don't know of any actual bugs
3816 right now, but that's the best time to fix them. Fixes bug 1943.
3817 - Support line continuations in the torrc config file. If a line
3818 ends with a single backslash character, the newline is ignored, and
3819 the configuration value is treated as continuing on the next line.
3822 o Minor bugfixes (on 0.2.1.x and earlier):
3823 - For bandwidth accounting, calculate our expected bandwidth rate
3824 based on the time during which we were active and not in
3825 soft-hibernation during the last interval. Previously, we were
3826 also considering the time spent in soft-hibernation. If this
3827 was a long time, we would wind up underestimating our bandwidth
3828 by a lot, and skewing our wakeup time towards the start of the
3829 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
3831 o Minor bugfixes (on 0.2.2.x):
3832 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
3833 which were disabled by the circuit build timeout changes in
3834 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
3835 - Make sure we don't warn about missing bandwidth weights when
3836 choosing bridges or other relays not in the consensus. Bugfix on
3837 0.2.2.10-alpha; fixes bug 1805.
3838 - In our logs, do not double-report signatures from unrecognized
3839 authorities both as "from unknown authority" and "not
3840 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
3843 Changes in version 0.2.2.16-alpha - 2010-09-17
3844 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
3845 evident at exit relays), and also continues to resolve all the little
3846 bugs that have been filling up trac lately.
3848 o Major bugfixes (stream-level fairness):
3849 - When receiving a circuit-level SENDME for a blocked circuit, try
3850 to package cells fairly from all the streams that had previously
3851 been blocked on that circuit. Previously, we had started with the
3852 oldest stream, and allowed each stream to potentially exhaust
3853 the circuit's package window. This gave older streams on any
3854 given circuit priority over newer ones. Fixes bug 1937. Detected
3855 originally by Camilo Viecco. This bug was introduced before the
3856 first Tor release, in svn commit r152: it is the new winner of
3857 the longest-lived bug prize.
3858 - When the exit relay got a circuit-level sendme cell, it started
3859 reading on the exit streams, even if had 500 cells queued in the
3860 circuit queue already, so the circuit queue just grew and grew in
3861 some cases. We fix this by not re-enabling reading on receipt of a
3862 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
3863 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
3865 - Newly created streams were allowed to read cells onto circuits,
3866 even if the circuit's cell queue was blocked and waiting to drain.
3867 This created potential unfairness, as older streams would be
3868 blocked, but newer streams would gladly fill the queue completely.
3869 We add code to detect this situation and prevent any stream from
3870 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
3874 - Update to the September 1 2010 Maxmind GeoLite Country database.
3875 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
3876 not. This would lead to a cookie that is still not group readable.
3877 Closes bug 1843. Suggested by katmagic.
3878 - When logging a rate-limited warning, we now mention how many messages
3879 got suppressed since the last warning.
3880 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
3881 do individual connection-level rate limiting of clients. The torrc
3882 config options with the same names trump the consensus params, if
3883 both are present. Replaces the old "bwconnrate" and "bwconnburst"
3884 consensus params which were broken from 0.2.2.7-alpha through
3885 0.2.2.14-alpha. Closes bug 1947.
3886 - When a router changes IP address or port, authorities now launch
3887 a new reachability test for it. Implements ticket 1899.
3888 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
3889 2 no signature, 4 required" messages about consensus signatures
3890 easier to read, and make sure they get logged at the same severity
3891 as the messages explaining which keys are which. Fixes bug 1290.
3892 - Don't warn when we have a consensus that we can't verify because
3893 of missing certificates, unless those certificates are ones
3894 that we have been trying and failing to download. Fixes bug 1145.
3895 - If you configure your bridge with a known identity fingerprint,
3896 and the bridge authority is unreachable (as it is in at least
3897 one country now), fall back to directly requesting the descriptor
3898 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
3900 - When building with --enable-gcc-warnings on OpenBSD, disable
3901 warnings in system headers. This makes --enable-gcc-warnings
3902 pass on OpenBSD 4.8.
3904 o Minor bugfixes (on 0.2.1.x and earlier):
3905 - Authorities will now attempt to download consensuses if their
3906 own efforts to make a live consensus have failed. This change
3907 means authorities that restart will fetch a valid consensus, and
3908 it means authorities that didn't agree with the current consensus
3909 will still fetch and serve it if it has enough signatures. Bugfix
3910 on 0.2.0.9-alpha; fixes bug 1300.
3911 - Ensure DNS requests launched by "RESOLVE" commands from the
3912 controller respect the __LeaveStreamsUnattached setconf options. The
3913 same goes for requests launched via DNSPort or transparent
3914 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
3915 - Allow handshaking OR connections to take a full KeepalivePeriod
3916 seconds to handshake. Previously, we would close them after
3917 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
3918 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
3920 - Rate-limit "Failed to hand off onionskin" warnings.
3921 - Never relay a cell for a circuit we have already destroyed.
3922 Between marking a circuit as closeable and finally closing it,
3923 it may have been possible for a few queued cells to get relayed,
3924 even though they would have been immediately dropped by the next
3925 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
3926 - Never queue a cell for a circuit that's already been marked
3928 - Never vote for a server as "Running" if we have a descriptor for
3929 it claiming to be hibernating, and that descriptor was published
3930 more recently than our last contact with the server. Bugfix on
3931 0.2.0.3-alpha; fixes bug 911.
3932 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
3935 o Minor bugfixes (on 0.2.2.x):
3936 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
3937 down if a directory fetch fails and you've configured either
3938 bridges or EntryNodes. The intent was to mark the relay as down
3939 _unless_ you're using bridges or EntryNodes, since if you are
3940 then you could quickly run out of entry points.
3941 - Fix the Windows directory-listing code. A bug introduced in
3942 0.2.2.14-alpha could make Windows directory servers forget to load
3943 some of their cached v2 networkstatus files.
3944 - Really allow clients to use relays as bridges. Fixes bug 1776;
3945 bugfix on 0.2.2.15-alpha.
3946 - Demote a warn to info that happens when the CellStatistics option
3947 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
3948 Reported by Moritz Bartl.
3949 - On Windows, build correctly either with or without Unicode support.
3950 This is necessary so that Tor can support fringe platforms like
3951 Windows 98 (which has no Unicode), or Windows CE (which has no
3952 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
3955 - Add a unit test for cross-platform directory-listing code.
3958 Changes in version 0.2.2.15-alpha - 2010-08-18
3959 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
3960 fixes a variety of other bugs that were preventing performance
3961 experiments from moving forward, fixes several bothersome memory leaks,
3962 and generally closes a lot of smaller bugs that have been filling up
3966 - Stop assigning the HSDir flag to relays that disable their
3967 DirPort (and thus will refuse to answer directory requests). This
3968 fix should dramatically improve the reachability of hidden services:
3969 hidden services and hidden service clients pick six HSDir relays
3970 to store and retrieve the hidden service descriptor, and currently
3971 about half of the HSDir relays will refuse to work. Bugfix on
3972 0.2.0.10-alpha; fixes part of bug 1693.
3973 - The PerConnBWRate and Burst config options, along with the
3974 bwconnrate and bwconnburst consensus params, initialized each conn's
3975 token bucket values only when the connection is established. Now we
3976 update them if the config options change, and update them every time
3977 we get a new consensus. Otherwise we can encounter an ugly edge
3978 case where we initialize an OR conn to client-level bandwidth,
3979 but then later the relay joins the consensus and we leave it
3980 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
3981 - Fix a regression that caused Tor to rebind its ports if it receives
3982 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
3985 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
3986 should give us approximately 40-50% more Guard-flagged nodes,
3987 improving the anonymity the Tor network can provide and also
3988 decreasing the dropoff in throughput that relays experience when
3989 they first get the Guard flag.
3990 - Allow enabling or disabling the *Statistics config options while
3994 - Update to the August 1 2010 Maxmind GeoLite Country database.
3995 - Have the controller interface give a more useful message than
3996 "Internal Error" in response to failed GETINFO requests.
3997 - Warn when the same option is provided more than once in a torrc
3998 file, on the command line, or in a single SETCONF statement, and
3999 the option is one that only accepts a single line. Closes bug 1384.
4000 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4001 Patch from mingw-san.
4002 - Add support for the country code "{??}" in torrc options like
4003 ExcludeNodes, to indicate all routers of unknown country. Closes
4005 - Relays report the number of bytes spent on answering directory
4006 requests in extra-info descriptors similar to {read,write}-history.
4007 Implements enhancement 1790.
4009 o Minor bugfixes (on 0.2.1.x and earlier):
4010 - Complain if PublishServerDescriptor is given multiple arguments that
4011 include 0 or 1. This configuration will be rejected in the future.
4012 Bugfix on 0.2.0.1-alpha; closes bug 1107.
4013 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
4014 Bugfix on 0.2.0.13-alpha; closes bug 928.
4015 - Change "Application request when we're believed to be offline."
4016 notice to "Application request when we haven't used client
4017 functionality lately.", to clarify that it's not an error. Bugfix
4018 on 0.0.9.3; fixes bug 1222.
4019 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
4020 would return "551 Internal error" rather than "552 Unrecognized key
4021 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
4022 - Users can't configure a regular relay to be their bridge. It didn't
4023 work because when Tor fetched the bridge descriptor, it found
4024 that it already had it, and didn't realize that the purpose of the
4025 descriptor had changed. Now we replace routers with a purpose other
4026 than bridge with bridge descriptors when fetching them. Bugfix on
4027 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
4028 refetch the descriptor with router purpose 'general', disabling
4030 - Fix a rare bug in rend_fn unit tests: we would fail a test when
4031 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
4032 on 0.2.0.10-alpha; fixes bug 1808.
4033 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
4034 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
4035 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
4036 Servers can start sending this code when enough clients recognize
4037 it. Also update the spec to reflect this new reason. Bugfix on
4038 0.1.0.1-rc; fixes part of bug 1793.
4039 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
4040 when we switch from being a public relay to a bridge. Otherwise
4041 there will still be clients that see the relay in their consensus,
4042 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
4044 - Instead of giving an assertion failure on an internal mismatch
4045 on estimated freelist size, just log a BUG warning and try later.
4046 Mitigates but does not fix bug 1125.
4047 - Fix an assertion failure that could occur in caches or bridge users
4048 when using a very short voting interval on a testing network.
4049 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
4051 o Minor bugfixes (on 0.2.2.x):
4052 - Alter directory authorities to always consider Exit-flagged nodes
4053 as potential Guard nodes in their votes. The actual decision to
4054 use Exits as Guards is done in the consensus bandwidth weights.
4055 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
4056 - When the controller is reporting the purpose of circuits that
4057 didn't finish building before the circuit build timeout, it was
4058 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
4059 - Our libevent version parsing code couldn't handle versions like
4060 1.4.14b-stable and incorrectly warned the user about using an
4061 old and broken version of libevent. Treat 1.4.14b-stable like
4062 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
4064 - Don't use substitution references like $(VAR:MOD) when
4065 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
4066 '$(:x)' to 'x' rather than the empty string. This bites us in
4067 doc/ when configured with --disable-asciidoc. Bugfix on
4068 0.2.2.9-alpha; fixes bug 1773.
4069 - Remove a spurious hidden service server-side log notice about
4070 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
4072 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
4074 - Correctly report written bytes on linked connections. Found while
4075 implementing 1790. Bugfix on 0.2.2.4-alpha.
4076 - Fix three memory leaks: one in circuit_build_times_parse_state(),
4077 one in dirvote_add_signatures_to_pending_consensus(), and one every
4078 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
4079 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
4081 o Code simplifications and refactoring:
4082 - Take a first step towards making or.h smaller by splitting out
4083 function definitions for all source files in src/or/. Leave
4084 structures and defines in or.h for now.
4085 - Remove a bunch of unused function declarations as well as a block of
4086 #if 0'd code from the unit tests. Closes bug 1824.
4087 - New unit tests for exit-port history statistics; refactored exit
4088 statistics code to be more easily tested.
4089 - Remove the old debian/ directory from the main Tor distribution.
4090 The official Tor-for-debian git repository lives at the URL
4091 https://git.torproject.org/debian/tor.git
4094 Changes in version 0.2.2.14-alpha - 2010-07-12
4095 Tor 0.2.2.14-alpha greatly improves client-side handling of
4096 circuit build timeouts, which are used to estimate speed and improve
4097 performance. We also move to a much better GeoIP database, port Tor to
4098 Windows CE, introduce new compile flags that improve code security,
4099 add an eighth v3 directory authority, and address a lot of more
4103 - Tor directory authorities no longer crash when started with a
4104 cached-microdesc-consensus file in their data directory. Bugfix
4105 on 0.2.2.6-alpha; fixes bug 1532.
4106 - Treat an unset $HOME like an empty $HOME rather than triggering an
4107 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
4108 - Ignore negative and large circuit build timeout values that can
4109 happen during a suspend or hibernate. These values caused various
4110 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
4111 - Alter calculation of Pareto distribution parameter 'Xm' for
4112 Circuit Build Timeout learning to use the weighted average of the
4113 top N=3 modes (because we have three entry guards). Considering
4114 multiple modes should improve the timeout calculation in some cases,
4115 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
4117 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
4118 right censored distribution model. This approach improves over the
4119 synthetic timeout generation approach that was producing insanely
4120 high timeout values. Now we calculate build timeouts using truncated
4121 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
4122 - Do not close circuits that are under construction when they reach
4123 the circuit build timeout. Instead, leave them building (but do not
4124 use them) for up until the time corresponding to the 95th percentile
4125 on the Pareto CDF or 60 seconds, whichever is greater. This is done
4126 to provide better data for the new Pareto model. This percentile
4127 can be controlled by the consensus.
4130 - Move to the June 2010 Maxmind GeoLite country db (rather than the
4131 June 2009 ip-to-country GeoIP db) for our statistics that count
4132 how many users relays are seeing from each country. Now we have
4133 more accurate data for many African countries.
4134 - Port Tor to build and run correctly on Windows CE systems, using
4135 the wcecompat library. Contributed by Valerio Lupi.
4136 - New "--enable-gcc-hardening" ./configure flag (off by default)
4137 to turn on gcc compile time hardening options. It ensures
4138 that signed ints have defined behavior (-fwrapv), enables
4139 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
4140 with canaries (-fstack-protector-all), turns on ASLR protection if
4141 supported by the kernel (-fPIE, -pie), and adds additional security
4142 related warnings. Verified to work on Mac OS X and Debian Lenny.
4143 - New "--enable-linker-hardening" ./configure flag (off by default)
4144 to turn on ELF specific hardening features (relro, now). This does
4145 not work with Mac OS X or any other non-ELF binary format.
4147 o New directory authorities:
4148 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
4152 - New config option "WarnUnsafeSocks 0" disables the warning that
4153 occurs whenever Tor receives a socks handshake using a version of
4154 the socks protocol that can only provide an IP address (rather
4155 than a hostname). Setups that do DNS locally over Tor are fine,
4156 and we shouldn't spam the logs in that case.
4157 - Convert the HACKING file to asciidoc, and add a few new sections
4158 to it, explaining how we use Git, how we make changelogs, and
4159 what should go in a patch.
4160 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
4161 event, to give information on the current rate of circuit timeouts
4162 over our stored history.
4163 - Add ability to disable circuit build time learning via consensus
4164 parameter and via a LearnCircuitBuildTimeout config option. Also
4165 automatically disable circuit build time calculation if we are
4166 either a AuthoritativeDirectory, or if we fail to write our state
4167 file. Fixes bug 1296.
4168 - More gracefully handle corrupt state files, removing asserts
4169 in favor of saving a backup and resetting state.
4170 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
4174 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4176 - When a2x fails, mention that the user could disable manpages instead
4177 of trying to fix their asciidoc installation.
4178 - Where available, use Libevent 2.0's periodic timers so that our
4179 once-per-second cleanup code gets called even more closely to
4180 once per second than it would otherwise. Fixes bug 943.
4181 - If you run a bridge that listens on multiple IP addresses, and
4182 some user configures a bridge address that uses a different IP
4183 address than your bridge writes in its router descriptor, and the
4184 user doesn't specify an identity key, their Tor would discard the
4185 descriptor because "it isn't one of our configured bridges", and
4186 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
4187 Bugfix on 0.2.0.3-alpha.
4188 - If OpenSSL fails to make a duplicate of a private or public key, log
4189 an error message and try to exit cleanly. May help with debugging
4190 if bug 1209 ever remanifests.
4191 - Save a couple bytes in memory allocation every time we escape
4192 certain characters in a string. Patch from Florian Zumbiehl.
4193 - Make it explicit that we don't cannibalize one-hop circuits. This
4194 happens in the wild, but doesn't turn out to be a problem because
4195 we fortunately don't use those circuits. Many thanks to outofwords
4196 for the initial analysis and to swissknife who confirmed that
4197 two-hop circuits are actually created.
4198 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
4199 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
4200 - Eliminate a case where a circuit build time warning was displayed
4201 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
4204 Changes in version 0.2.1.26 - 2010-05-02
4205 Tor 0.2.1.26 addresses the recent connection and memory overload
4206 problems we've been seeing on relays, especially relays with their
4207 DirPort open. If your relay has been crashing, or you turned it off
4208 because it used too many resources, give this release a try.
4210 This release also fixes yet another instance of broken OpenSSL libraries
4211 that was causing some relays to drop out of the consensus.
4214 - Teach relays to defend themselves from connection overload. Relays
4215 now close idle circuits early if it looks like they were intended
4216 for directory fetches. Relays are also more aggressive about closing
4217 TLS connections that have no circuits on them. Such circuits are
4218 unlikely to be re-used, and tens of thousands of them were piling
4219 up at the fast relays, causing the relays to run out of sockets
4220 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4221 their directory fetches over TLS).
4222 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4223 that claim to be earlier than 0.9.8m, but which have in reality
4224 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4225 behavior. Possible fix for some cases of bug 1346.
4226 - Directory mirrors were fetching relay descriptors only from v2
4227 directory authorities, rather than v3 authorities like they should.
4228 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4229 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4232 - Finally get rid of the deprecated and now harmful notion of "clique
4233 mode", where directory authorities maintain TLS connections to
4237 - In the util/threads test, no longer free the test_mutex before all
4238 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4239 - The master thread could starve the worker threads quite badly on
4240 certain systems, causing them to run only partially in the allowed
4241 window. This resulted in test failures. Now the master thread sleeps
4242 occasionally for a few microseconds while the two worker-threads
4243 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4246 Changes in version 0.2.2.13-alpha - 2010-04-24
4247 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
4248 problems we've been seeing on relays, especially relays with their
4249 DirPort open. If your relay has been crashing, or you turned it off
4250 because it used too many resources, give this release a try.
4253 - Teach relays to defend themselves from connection overload. Relays
4254 now close idle circuits early if it looks like they were intended
4255 for directory fetches. Relays are also more aggressive about closing
4256 TLS connections that have no circuits on them. Such circuits are
4257 unlikely to be re-used, and tens of thousands of them were piling
4258 up at the fast relays, causing the relays to run out of sockets
4259 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4260 their directory fetches over TLS).
4263 - Finally get rid of the deprecated and now harmful notion of "clique
4264 mode", where directory authorities maintain TLS connections to
4266 - Directory authorities now do an immediate reachability check as soon
4267 as they hear about a new relay. This change should slightly reduce
4268 the time between setting up a relay and getting listed as running
4269 in the consensus. It should also improve the time between setting
4270 up a bridge and seeing use by bridge users.
4271 - Directory authorities no longer launch a TLS connection to every
4272 relay as they startup. Now that we have 2k+ descriptors cached,
4273 the resulting network hiccup is becoming a burden. Besides,
4274 authorities already avoid voting about Running for the first half
4275 hour of their uptime.
4278 Changes in version 0.2.2.12-alpha - 2010-04-20
4279 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
4280 handle and vote on descriptors. It was causing relays to drop out of
4284 - Many relays have been falling out of the consensus lately because
4285 not enough authorities know about their descriptor for them to get
4286 a majority of votes. When we deprecated the v2 directory protocol,
4287 we got rid of the only way that v3 authorities can hear from each
4288 other about other descriptors. Now authorities examine every v3
4289 vote for new descriptors, and fetch them from that authority. Bugfix
4291 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
4292 and a warning in or.h related to bandwidth_weight_rule_t that
4293 prevented clean compile on OS X. Fixes bug 1363; bugfix on
4295 - Fix a segfault on relays when DirReqStatistics is enabled
4296 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
4300 - Demote a confusing TLS warning that relay operators might get when
4301 someone tries to talk to their OrPort. It is neither the operator's
4302 fault nor can they do anything about it. Fixes bug 1364; bugfix
4306 Changes in version 0.2.2.11-alpha - 2010-04-15
4307 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
4308 libraries that was causing some relays to drop out of the consensus.
4311 - Directory mirrors were fetching relay descriptors only from v2
4312 directory authorities, rather than v3 authorities like they should.
4313 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4314 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4315 - Fix a parsing error that made every possible value of
4316 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
4317 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
4318 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
4319 about the option without breaking older ones.
4320 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4321 that claim to be earlier than 0.9.8m, but which have in reality
4322 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4323 behavior. Possible fix for some cases of bug 1346.
4326 - Experiment with a more aggressive approach to preventing clients
4327 from making one-hop exit streams. Exit relays who want to try it
4328 out can set "RefuseUnknownExits 1" in their torrc, and then look
4329 for "Attempt by %s to open a stream" log messages. Let us know
4331 - Add support for statically linking zlib by specifying
4332 --enable-static-zlib, to go with our support for statically linking
4333 openssl and libevent. Resolves bug 1358.
4336 - Fix a segfault that happens whenever a Tor client that is using
4337 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
4339 - When we cleaned up the contrib/tor-exit-notice.html file, we left
4340 out the first line. Fixes bug 1295.
4341 - When building the manpage from a tarball, we required asciidoc, but
4342 the asciidoc -> roff/html conversion was already done for the
4343 tarball. Make 'make' complain only when we need asciidoc (either
4344 because we're compiling directly from git, or because we altered
4345 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
4346 - When none of the directory authorities vote on any params, Tor
4347 segfaulted when trying to make the consensus from the votes. We
4348 didn't trigger the bug in practice, because authorities do include
4349 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
4352 - In the util/threads test, no longer free the test_mutex before all
4353 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4354 - The master thread could starve the worker threads quite badly on
4355 certain systems, causing them to run only partially in the allowed
4356 window. This resulted in test failures. Now the master thread sleeps
4357 occasionally for a few microseconds while the two worker-threads
4358 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4361 Changes in version 0.2.2.10-alpha - 2010-03-07
4362 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
4363 could prevent relays from guessing their IP address correctly. It also
4364 starts the groundwork for another client-side performance boost, since
4365 currently we're not making efficient use of relays that have both the
4366 Guard flag and the Exit flag.
4369 - Fix a regression from our patch for bug 1244 that caused relays
4370 to guess their IP address incorrectly if they didn't set Address
4371 in their torrc and/or their address fails to resolve. Bugfix on
4372 0.2.2.9-alpha; fixes bug 1269.
4374 o Major features (performance):
4375 - Directory authorities now compute consensus weightings that instruct
4376 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
4377 and no flag. Clients that use these weightings will distribute
4378 network load more evenly across these different relay types. The
4379 weightings are in the consensus so we can change them globally in
4380 the future. Extra thanks to "outofwords" for finding some nasty
4381 security bugs in the first implementation of this feature.
4383 o Minor features (performance):
4384 - Always perform router selections using weighted relay bandwidth,
4385 even if we don't need a high capacity circuit at the time. Non-fast
4386 circuits now only differ from fast ones in that they can use relays
4387 not marked with the Fast flag. This "feature" could turn out to
4388 be a horrible bug; we should investigate more before it goes into
4392 - Allow disabling building of the manpages. Skipping the manpage
4393 speeds up the build considerably.
4395 o Minor bugfixes (on 0.2.2.x):
4396 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
4397 Bugfix on 0.2.2.9-alpha.
4398 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
4399 config option. Bugfix on 0.2.2.7-alpha.
4400 - Ship the asciidoc-helper file in the tarball, so that people can
4401 build from source if they want to, and touching the .1.txt files
4402 doesn't break the build. Bugfix on 0.2.2.9-alpha.
4404 o Minor bugfixes (on 0.2.1.x or earlier):
4405 - Fix a dereference-then-NULL-check sequence when publishing
4406 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4408 - Fix another dereference-then-NULL-check sequence. Bugfix on
4409 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4410 - Make sure we treat potentially not NUL-terminated strings correctly.
4411 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4413 o Code simplifications and refactoring:
4414 - Fix some urls in the exit notice file and make it XHTML1.1 strict
4415 compliant. Based on a patch from Christian Kujau.
4416 - Don't use sed in asciidoc-helper anymore.
4417 - Make the build process fail if asciidoc cannot be found and
4418 building with asciidoc isn't disabled.
4421 Changes in version 0.2.2.9-alpha - 2010-02-22
4422 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
4423 location of a directory authority, and cleans up a bunch of small bugs.
4425 o Directory authority changes:
4426 - Change IP address for dannenberg (v3 directory authority), and
4427 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4428 service directory authority) from the list.
4431 - Make Tor work again on the latest OS X: when deciding whether to
4432 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4433 version at run-time, not compile time. We need to do this because
4434 Apple doesn't update its dev-tools headers when it updates its
4435 libraries in a security patch.
4436 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4437 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4438 a memory leak when requesting a hidden service descriptor we've
4439 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4441 - Authorities could be tricked into giving out the Exit flag to relays
4442 that didn't allow exiting to any ports. This bug could screw
4443 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
4444 1238. Bug discovered by Martin Kowalczyk.
4445 - When freeing a session key, zero it out completely. We only zeroed
4446 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4447 patched by ekir. Fixes bug 1254.
4450 - Fix static compilation by listing the openssl libraries in the right
4451 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
4452 - Resume handling .exit hostnames in a special way: originally we
4453 stripped the .exit part and used the requested exit relay. In
4454 0.2.2.1-alpha we stopped treating them in any special way, meaning
4455 if you use a .exit address then Tor will pass it on to the exit
4456 relay. Now we reject the .exit stream outright, since that behavior
4457 might be more expected by the user. Found and diagnosed by Scott
4458 Bennett and Downie on or-talk.
4459 - Don't spam the controller with events when we have no file
4460 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
4461 for log messages was already solved from bug 748.)
4462 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
4464 - Make the DNSPort option work with libevent 2.x. Don't alter the
4465 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
4466 - Emit a GUARD DROPPED controller event for a case we missed.
4467 - Make more fields in the controller protocol case-insensitive, since
4468 control-spec.txt said they were.
4469 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4470 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4471 - Fix a spec conformance issue: the network-status-version token
4472 must be the first token in a v3 consensus or vote. Discovered by
4473 parakeep. Bugfix on 0.2.0.3-alpha.
4475 o Code simplifications and refactoring:
4476 - Generate our manpage and HTML documentation using Asciidoc. This
4477 change should make it easier to maintain the documentation, and
4479 - Remove the --enable-iphone option. According to reports from Marco
4480 Bonetti, Tor builds fine without any special tweaking on recent
4481 iPhone SDK versions.
4482 - Removed some unnecessary files from the source distribution. The
4483 AUTHORS file has now been merged into the people page on the
4484 website. The roadmaps and design doc can now be found in the
4485 projects directory in svn.
4486 - Enabled various circuit build timeout constants to be controlled
4487 by consensus parameters. Also set better defaults for these
4488 parameters based on experimentation on broadband and simulated
4492 - The 'EXTENDCIRCUIT' control port command can now be used with
4493 a circ id of 0 and no path. This feature will cause Tor to build
4494 a new 'fast' general purpose circuit using its own path selection
4496 - Added a BUILDTIMEOUT_SET controller event to describe changes
4497 to the circuit build timeout.
4498 - Future-proof the controller protocol a bit by ignoring keyword
4499 arguments we do not recognize.
4500 - Expand homedirs passed to tor-checkkey. This should silence a
4501 coverity complaint about passing a user-supplied string into
4502 open() without checking it.
4505 Changes in version 0.2.1.25 - 2010-03-16
4506 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
4507 prevent relays from guessing their IP address correctly. It also fixes
4508 several minor potential security bugs.
4511 - Fix a regression from our patch for bug 1244 that caused relays
4512 to guess their IP address incorrectly if they didn't set Address
4513 in their torrc and/or their address fails to resolve. Bugfix on
4514 0.2.1.23; fixes bug 1269.
4515 - When freeing a session key, zero it out completely. We only zeroed
4516 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4517 patched by ekir. Fixes bug 1254.
4520 - Fix a dereference-then-NULL-check sequence when publishing
4521 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4523 - Fix another dereference-then-NULL-check sequence. Bugfix on
4524 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4525 - Make sure we treat potentially not NUL-terminated strings correctly.
4526 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4530 Changes in version 0.2.1.24 - 2010-02-21
4531 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
4535 - Work correctly out-of-the-box with even more vendor-patched versions
4536 of OpenSSL. In particular, make it so Debian and OS X don't need
4537 customized patches to run/build.
4540 Changes in version 0.2.1.23 - 2010-02-13
4541 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
4542 again on the latest OS X, and updates the location of a directory
4545 o Major bugfixes (performance):
4546 - We were selecting our guards uniformly at random, and then weighting
4547 which of our guards we'd use uniformly at random. This imbalance
4548 meant that Tor clients were severely limited on throughput (and
4549 probably latency too) by the first hop in their circuit. Now we
4550 select guards weighted by currently advertised bandwidth. We also
4551 automatically discard guards picked using the old algorithm. Fixes
4552 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4555 - Make Tor work again on the latest OS X: when deciding whether to
4556 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4557 version at run-time, not compile time. We need to do this because
4558 Apple doesn't update its dev-tools headers when it updates its
4559 libraries in a security patch.
4560 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4561 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4562 a memory leak when requesting a hidden service descriptor we've
4563 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4566 o Directory authority changes:
4567 - Change IP address for dannenberg (v3 directory authority), and
4568 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4569 service directory authority) from the list.
4572 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4573 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4576 - Avoid a mad rush at the beginning of each month when each client
4577 rotates half of its guards. Instead we spread the rotation out
4578 throughout the month, but we still avoid leaving a precise timestamp
4579 in the state file about when we first picked the guard. Improves
4580 over the behavior introduced in 0.1.2.17.
4583 Changes in version 0.2.2.8-alpha - 2010-01-26
4584 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
4585 causing bridge relays to disappear. If you're running a bridge,
4589 - Fix a memory corruption bug on bridges that occured during the
4590 inclusion of stats data in extra-info descriptors. Also fix the
4591 interface for geoip_get_bridge_stats* to prevent similar bugs in
4592 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
4593 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
4596 - Ignore OutboundBindAddress when connecting to localhost.
4597 Connections to localhost need to come _from_ localhost, or else
4598 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
4602 Changes in version 0.2.2.7-alpha - 2010-01-19
4603 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
4604 as laying the groundwork for further relay-side performance fixes. It
4605 also starts cleaning up client behavior with respect to the EntryNodes,
4606 ExitNodes, and StrictNodes config options.
4608 This release also rotates two directory authority keys, due to a
4609 security breach of some of the Torproject servers.
4611 o Directory authority changes:
4612 - Rotate keys (both v3 identity and relay identity) for moria1
4615 o Major features (performance):
4616 - We were selecting our guards uniformly at random, and then weighting
4617 which of our guards we'd use uniformly at random. This imbalance
4618 meant that Tor clients were severely limited on throughput (and
4619 probably latency too) by the first hop in their circuit. Now we
4620 select guards weighted by currently advertised bandwidth. We also
4621 automatically discard guards picked using the old algorithm. Fixes
4622 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4623 - When choosing which cells to relay first, relays can now favor
4624 circuits that have been quiet recently, to provide lower latency
4625 for low-volume circuits. By default, relays enable or disable this
4626 feature based on a setting in the consensus. You can override
4627 this default by using the new "CircuitPriorityHalflife" config
4628 option. Design and code by Ian Goldberg, Can Tang, and Chris
4630 - Add separate per-conn write limiting to go with the per-conn read
4631 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
4632 but never per-conn write limits.
4633 - New consensus params "bwconnrate" and "bwconnburst" to let us
4634 rate-limit client connections as they enter the network. It's
4635 controlled in the consensus so we can turn it on and off for
4636 experiments. It's starting out off. Based on proposal 163.
4638 o Major features (relay selection options):
4639 - Switch to a StrictNodes config option, rather than the previous
4640 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
4641 "StrictExcludeNodes" option.
4642 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
4643 change during a config reload, mark and discard all our origin
4644 circuits. This fix should address edge cases where we change the
4645 config options and but then choose a circuit that we created before
4647 - If EntryNodes or ExitNodes are set, be more willing to use an
4648 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
4650 - Make EntryNodes config option much more aggressive even when
4651 StrictNodes is not set. Before it would prepend your requested
4652 entrynodes to your list of guard nodes, but feel free to use others
4653 after that. Now it chooses only from your EntryNodes if any of
4654 those are available, and only falls back to others if a) they're
4655 all down and b) StrictNodes is not set.
4656 - Now we refresh your entry guards from EntryNodes at each consensus
4657 fetch -- rather than just at startup and then they slowly rot as
4658 the network changes.
4661 - Stop bridge directory authorities from answering dbg-stability.txt
4662 directory queries, which would let people fetch a list of all
4663 bridge identities they track. Bugfix on 0.2.1.6-alpha.
4666 - Log a notice when we get a new control connection. Now it's easier
4667 for security-conscious users to recognize when a local application
4668 is knocking on their controller door. Suggested by bug 1196.
4669 - New config option "CircuitStreamTimeout" to override our internal
4670 timeout schedule for how many seconds until we detach a stream from
4671 a circuit and try a new circuit. If your network is particularly
4672 slow, you might want to set this to a number like 60.
4673 - New controller command "getinfo config-text". It returns the
4674 contents that Tor would write if you send it a SAVECONF command,
4675 so the controller can write the file to disk itself.
4676 - New options for SafeLogging to allow scrubbing only log messages
4677 generated while acting as a relay.
4678 - Ship the bridges spec file in the tarball too.
4679 - Avoid a mad rush at the beginning of each month when each client
4680 rotates half of its guards. Instead we spread the rotation out
4681 throughout the month, but we still avoid leaving a precise timestamp
4682 in the state file about when we first picked the guard. Improves
4683 over the behavior introduced in 0.1.2.17.
4685 o Minor bugfixes (compiling):
4686 - Fix compilation on OS X 10.3, which has a stub mlockall() but
4687 hides it. Bugfix on 0.2.2.6-alpha.
4688 - Fix compilation on Solaris by removing support for the
4689 DisableAllSwap config option. Solaris doesn't have an rlimit for
4690 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
4693 o Minor bugfixes (crashes):
4694 - Do not segfault when writing buffer stats when we haven't observed
4695 a single circuit to report about. Found by Fabian Lanze. Bugfix on
4697 - If we're in the pathological case where there's no exit bandwidth
4698 but there is non-exit bandwidth, or no guard bandwidth but there
4699 is non-guard bandwidth, don't crash during path selection. Bugfix
4701 - Fix an impossible-to-actually-trigger buffer overflow in relay
4702 descriptor generation. Bugfix on 0.1.0.15.
4704 o Minor bugfixes (privacy):
4705 - Fix an instance where a Tor directory mirror might accidentally
4706 log the IP address of a misbehaving Tor client. Bugfix on
4708 - Don't list Windows capabilities in relay descriptors. We never made
4709 use of them, and maybe it's a bad idea to publish them. Bugfix
4712 o Minor bugfixes (other):
4713 - Resolve an edge case in path weighting that could make us misweight
4714 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
4715 - Fix statistics on client numbers by country as seen by bridges that
4716 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
4717 intervals instead of variable 12-to-48-hour intervals.
4718 - After we free an internal connection structure, overwrite it
4719 with a different memory value than we use for overwriting a freed
4720 internal circuit structure. Should help with debugging. Suggested
4722 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
4726 - Remove the HSAuthorityRecordStats option that version 0 hidden
4727 service authorities could have used to track statistics of overall
4728 hidden service usage.
4731 Changes in version 0.2.1.22 - 2010-01-19
4732 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
4733 authorities -- it would tell you its whole history of bridge descriptors
4734 if you make the right directory request. This stable update also
4735 rotates two of the seven v3 directory authority keys and locations.
4737 o Directory authority changes:
4738 - Rotate keys (both v3 identity and relay identity) for moria1
4742 - Stop bridge directory authorities from answering dbg-stability.txt
4743 directory queries, which would let people fetch a list of all
4744 bridge identities they track. Bugfix on 0.2.1.6-alpha.
4747 Changes in version 0.2.1.21 - 2009-12-21
4748 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
4749 library. If you use Tor on Linux / Unix and you're getting SSL
4750 renegotiation errors, upgrading should help. We also recommend an
4751 upgrade if you're an exit relay.
4754 - Work around a security feature in OpenSSL 0.9.8l that prevents our
4755 handshake from working unless we explicitly tell OpenSSL that we
4756 are using SSL renegotiation safely. We are, of course, but OpenSSL
4757 0.9.8l won't work unless we say we are.
4758 - Avoid crashing if the client is trying to upload many bytes and the
4759 circuit gets torn down at the same time, or if the flip side
4760 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
4763 - Do not refuse to learn about authority certs and v2 networkstatus
4764 documents that are older than the latest consensus. This bug might
4765 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
4766 Spotted and fixed by xmux.
4767 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
4768 trigger platform-specific option misparsing case found by Coverity
4770 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
4771 trigger assert. Fixes bug 1173.
4774 Changes in version 0.2.2.6-alpha - 2009-11-19
4775 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
4776 support for the new lower-footprint "microdescriptor" directory design,
4777 future-proofing our consensus format against new hash functions or
4778 other changes, and an Android port. It also makes Tor compatible with
4779 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
4782 - Directory authorities can now create, vote on, and serve multiple
4783 parallel formats of directory data as part of their voting process.
4784 Partially implements Proposal 162: "Publish the consensus in
4786 - Directory authorities can now agree on and publish small summaries
4787 of router information that clients can use in place of regular
4788 server descriptors. This transition will eventually allow clients
4789 to use far less bandwidth for downloading information about the
4790 network. Begins the implementation of Proposal 158: "Clients
4791 download consensus + microdescriptors".
4792 - The directory voting system is now extensible to use multiple hash
4793 algorithms for signatures and resource selection. Newer formats
4794 are signed with SHA256, with a possibility for moving to a better
4795 hash algorithm in the future.
4796 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
4797 current and future memory pages via mlockall(). On supported
4798 platforms (modern Linux and probably BSD but not Windows or OS X),
4799 this should effectively disable any and all attempts to page out
4800 memory. This option requires that you start your Tor as root --
4801 if you use DisableAllSwap, please consider using the User option
4802 to properly reduce the privileges of your Tor.
4803 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
4804 to help Tor build correctly for Android phones.
4807 - Work around a security feature in OpenSSL 0.9.8l that prevents our
4808 handshake from working unless we explicitly tell OpenSSL that we
4809 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
4810 won't work unless we say we are.
4813 - Fix a crash bug when trying to initialize the evdns module in
4814 Libevent 2. Bugfix on 0.2.1.16-rc.
4815 - Stop logging at severity 'warn' when some other Tor client tries
4816 to establish a circuit with us using weak DH keys. It's a protocol
4817 violation, but that doesn't mean ordinary users need to hear about
4818 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
4819 - Do not refuse to learn about authority certs and v2 networkstatus
4820 documents that are older than the latest consensus. This bug might
4821 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
4822 Spotted and fixed by xmux.
4823 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
4824 - If all authorities restart at once right before a consensus vote,
4825 nobody will vote about "Running", and clients will get a consensus
4826 with no usable relays. Instead, authorities refuse to build a
4827 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
4828 - If your relay can't keep up with the number of incoming create
4829 cells, it would log one warning per failure into your logs. Limit
4830 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
4831 - Bridges now use "reject *:*" as their default exit policy. Bugfix
4832 on 0.2.0.3-alpha; fixes bug 1113.
4833 - Fix a memory leak on directory authorities during voting that was
4834 introduced in 0.2.2.1-alpha. Found via valgrind.
4837 Changes in version 0.2.1.20 - 2009-10-15
4838 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
4839 services at once, prepares for more performance improvements, and
4840 fixes a bunch of smaller bugs.
4842 The Windows and OS X bundles also include a more recent Vidalia,
4843 and switch from Privoxy to Polipo.
4845 The OS X installers are now drag and drop. It's best to un-install
4846 Tor/Vidalia and then install this new bundle, rather than upgrade. If
4847 you want to upgrade, you'll need to update the paths for Tor and Polipo
4848 in the Vidalia Settings window.
4851 - Send circuit or stream sendme cells when our window has decreased
4852 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
4853 by Karsten when testing the "reduce circuit window" performance
4854 patch. Bugfix on the 54th commit on Tor -- from July 2002,
4855 before the release of Tor 0.0.0. This is the new winner of the
4857 - Fix a remotely triggerable memory leak when a consensus document
4858 contains more than one signature from the same voter. Bugfix on
4860 - Avoid segfault in rare cases when finishing an introduction circuit
4861 as a client and finding out that we don't have an introduction key
4862 for it. Fixes bug 1073. Reported by Aaron Swartz.
4865 - Tor now reads the "circwindow" parameter out of the consensus,
4866 and uses that value for its circuit package window rather than the
4867 default of 1000 cells. Begins the implementation of proposal 168.
4869 o New directory authorities:
4870 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
4872 - Move moria1 and tonga to alternate IP addresses.
4875 - Fix a signed/unsigned compile warning in 0.2.1.19.
4876 - Fix possible segmentation fault on directory authorities. Bugfix on
4878 - Fix an extremely rare infinite recursion bug that could occur if
4879 we tried to log a message after shutting down the log subsystem.
4880 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
4881 - Fix an obscure bug where hidden services on 64-bit big-endian
4882 systems might mis-read the timestamp in v3 introduce cells, and
4883 refuse to connect back to the client. Discovered by "rotor".
4884 Bugfix on 0.2.1.6-alpha.
4885 - We were triggering a CLOCK_SKEW controller status event whenever
4886 we connect via the v2 connection protocol to any relay that has
4887 a wrong clock. Instead, we should only inform the controller when
4888 it's a trusted authority that claims our clock is wrong. Bugfix
4889 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
4890 - We were telling the controller about CHECKING_REACHABILITY and
4891 REACHABILITY_FAILED status events whenever we launch a testing
4892 circuit or notice that one has failed. Instead, only tell the
4893 controller when we want to inform the user of overall success or
4894 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
4896 - Don't warn when we're using a circuit that ends with a node
4897 excluded in ExcludeExitNodes, but the circuit is not used to access
4898 the outside world. This should help fix bug 1090. Bugfix on
4900 - Work around a small memory leak in some versions of OpenSSL that
4901 stopped the memory used by the hostname TLS extension from being
4905 - Add a "getinfo status/accepted-server-descriptor" controller
4906 command, which is the recommended way for controllers to learn
4907 whether our server descriptor has been successfully received by at
4908 least on directory authority. Un-recommend good-server-descriptor
4909 getinfo and status events until we have a better design for them.
4912 Changes in version 0.2.2.5-alpha - 2009-10-11
4913 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
4916 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
4918 o Directory authorities:
4919 - Temporarily (just for this release) move dizum to an alternate
4923 Changes in version 0.2.2.4-alpha - 2009-10-10
4924 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
4925 introduces a new unit test framework, shifts directry authority
4926 addresses around to reduce the impact from recent blocking events,
4927 and fixes a few smaller bugs.
4930 - Fix several more asserts in the circuit_build_times code, for
4931 example one that causes Tor to fail to start once we have
4932 accumulated 5000 build times in the state file. Bugfixes on
4933 0.2.2.2-alpha; fixes bug 1108.
4935 o New directory authorities:
4936 - Move moria1 and Tonga to alternate IP addresses.
4939 - Log SSL state transitions at debug level during handshake, and
4940 include SSL states in error messages. This may help debug future
4941 SSL handshake issues.
4942 - Add a new "Handshake" log domain for activities that happen
4943 during the TLS handshake.
4944 - Revert to the "June 3 2009" ip-to-country file. The September one
4945 seems to have removed most US IP addresses.
4946 - Directory authorities now reject Tor relays with versions less than
4947 0.1.2.14. This step cuts out four relays from the current network,
4948 none of which are very big.
4951 - Fix a couple of smaller issues with gathering statistics. Bugfixes
4953 - Fix two memory leaks in the error case of
4954 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
4955 - Don't count one-hop circuits when we're estimating how long it
4956 takes circuits to build on average. Otherwise we'll set our circuit
4957 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
4958 - Directory authorities no longer change their opinion of, or vote on,
4959 whether a router is Running, unless they have themselves been
4960 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
4963 o Code simplifications and refactoring:
4964 - Revise our unit tests to use the "tinytest" framework, so we
4965 can run tests in their own processes, have smarter setup/teardown
4966 code, and so on. The unit test code has moved to its own
4967 subdirectory, and has been split into multiple modules.
4970 Changes in version 0.2.2.3-alpha - 2009-09-23
4971 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
4974 - Fix an overzealous assert in our new circuit build timeout code.
4975 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
4978 - If the networkstatus consensus tells us that we should use a
4979 negative circuit package window, ignore it. Otherwise we'll
4980 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
4983 Changes in version 0.2.2.2-alpha - 2009-09-21
4984 Tor 0.2.2.2-alpha introduces our latest performance improvement for
4985 clients: Tor tracks the average time it takes to build a circuit, and
4986 avoids using circuits that take too long to build. For fast connections,
4987 this feature can cut your expected latency in half. For slow or flaky
4988 connections, it could ruin your Tor experience. Let us know if it does!
4991 - Tor now tracks how long it takes to build client-side circuits
4992 over time, and adapts its timeout to local network performance.
4993 Since a circuit that takes a long time to build will also provide
4994 bad performance, we get significant latency improvements by
4995 discarding the slowest 20% of circuits. Specifically, Tor creates
4996 circuits more aggressively than usual until it has enough data
4997 points for a good timeout estimate. Implements proposal 151.
4998 We are especially looking for reports (good and bad) from users with
4999 both EDGE and broadband connections that can move from broadband
5000 to EDGE and find out if the build-time data in the .tor/state gets
5001 reset without loss of Tor usability. You should also see a notice
5002 log message telling you that Tor has reset its timeout.
5003 - Directory authorities can now vote on arbitary integer values as
5004 part of the consensus process. This is designed to help set
5005 network-wide parameters. Implements proposal 167.
5006 - Tor now reads the "circwindow" parameter out of the consensus,
5007 and uses that value for its circuit package window rather than the
5008 default of 1000 cells. Begins the implementation of proposal 168.
5011 - Fix a remotely triggerable memory leak when a consensus document
5012 contains more than one signature from the same voter. Bugfix on
5016 - Fix an extremely rare infinite recursion bug that could occur if
5017 we tried to log a message after shutting down the log subsystem.
5018 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5019 - Fix parsing for memory or time units given without a space between
5020 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
5021 - A networkstatus vote must contain exactly one signature. Spec
5022 conformance issue. Bugfix on 0.2.0.3-alpha.
5023 - Fix an obscure bug where hidden services on 64-bit big-endian
5024 systems might mis-read the timestamp in v3 introduce cells, and
5025 refuse to connect back to the client. Discovered by "rotor".
5026 Bugfix on 0.2.1.6-alpha.
5027 - We were triggering a CLOCK_SKEW controller status event whenever
5028 we connect via the v2 connection protocol to any relay that has
5029 a wrong clock. Instead, we should only inform the controller when
5030 it's a trusted authority that claims our clock is wrong. Bugfix
5031 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5032 - We were telling the controller about CHECKING_REACHABILITY and
5033 REACHABILITY_FAILED status events whenever we launch a testing
5034 circuit or notice that one has failed. Instead, only tell the
5035 controller when we want to inform the user of overall success or
5036 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5038 - Don't warn when we're using a circuit that ends with a node
5039 excluded in ExcludeExitNodes, but the circuit is not used to access
5040 the outside world. This should help fix bug 1090, but more problems
5041 remain. Bugfix on 0.2.1.6-alpha.
5042 - Work around a small memory leak in some versions of OpenSSL that
5043 stopped the memory used by the hostname TLS extension from being
5045 - Make our 'torify' script more portable; if we have only one of
5046 'torsocks' or 'tsocks' installed, don't complain to the user;
5047 and explain our warning about tsocks better.
5050 - Add a "getinfo status/accepted-server-descriptor" controller
5051 command, which is the recommended way for controllers to learn
5052 whether our server descriptor has been successfully received by at
5053 least on directory authority. Un-recommend good-server-descriptor
5054 getinfo and status events until we have a better design for them.
5055 - Update to the "September 4 2009" ip-to-country file.
5058 Changes in version 0.2.2.1-alpha - 2009-08-26
5059 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
5060 Tor clients to bootstrap on networks where only port 80 is reachable,
5061 makes it more straightforward to support hardware crypto accelerators,
5062 and starts the groundwork for gathering stats safely at relays.
5065 - Start the process of disabling ".exit" address notation, since it
5066 can be used for a variety of esoteric application-level attacks
5067 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
5070 o New directory authorities:
5071 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5075 - New AccelName and AccelDir options add support for dynamic OpenSSL
5076 hardware crypto acceleration engines.
5077 - Tor now supports tunneling all of its outgoing connections over
5078 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
5079 configuration options. Code by Christopher Davis.
5082 - Send circuit or stream sendme cells when our window has decreased
5083 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5084 by Karsten when testing the "reduce circuit window" performance
5085 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5086 before the release of Tor 0.0.0. This is the new winner of the
5089 o New options for gathering stats safely:
5090 - Directory mirrors that set "DirReqStatistics 1" write statistics
5091 about directory requests to disk every 24 hours. As compared to the
5092 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
5093 1) stats are written to disk exactly every 24 hours; 2) estimated
5094 shares of v2 and v3 requests are determined as mean values, not at
5095 the end of a measurement period; 3) unresolved requests are listed
5096 with country code '??'; 4) directories also measure download times.
5097 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
5098 number of exit streams and transferred bytes per port to disk every
5100 - Relays that set "CellStatistics 1" write statistics on how long
5101 cells spend in their circuit queues to disk every 24 hours.
5102 - Entry nodes that set "EntryStatistics 1" write statistics on the
5103 rough number and origins of connecting clients to disk every 24
5105 - Relays that write any of the above statistics to disk and set
5106 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
5107 their extra-info documents.
5110 - New --digests command-line switch to output the digests of the
5111 source files Tor was built with.
5112 - The "torify" script now uses torsocks where available.
5113 - The memarea code now uses a sentinel value at the end of each area
5114 to make sure nothing writes beyond the end of an area. This might
5115 help debug some conceivable causes of bug 930.
5116 - Time and memory units in the configuration file can now be set to
5117 fractional units. For example, "2.5 GB" is now a valid value for
5119 - Certain Tor clients (such as those behind check.torproject.org) may
5120 want to fetch the consensus in an extra early manner. To enable this
5121 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
5122 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
5123 as only certain clients who must have this information sooner should
5125 - Instead of adding the svn revision to the Tor version string, report
5126 the git commit (when we're building from a git checkout).
5129 - If any of the v3 certs we download are unparseable, we should
5130 actually notice the failure so we don't retry indefinitely. Bugfix
5131 on 0.2.0.x; reported by "rotator".
5132 - If the cached cert file is unparseable, warn but don't exit.
5133 - Fix possible segmentation fault on directory authorities. Bugfix on
5135 - When Tor fails to parse a descriptor of any kind, dump it to disk.
5136 Might help diagnosing bug 1051.
5138 o Deprecated and removed features:
5139 - The controller no longer accepts the old obsolete "addr-mappings/"
5140 or "unregistered-servers-" GETINFO values.
5141 - Hidden services no longer publish version 0 descriptors, and clients
5142 do not request or use version 0 descriptors. However, the old hidden
5143 service authorities still accept and serve version 0 descriptors
5144 when contacted by older hidden services/clients.
5145 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
5146 always on; using them is necessary for correct forward-compatible
5148 - Remove support for .noconnect style addresses. Nobody was using
5149 them, and they provided another avenue for detecting Tor users
5150 via application-level web tricks.
5152 o Packaging changes:
5153 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
5154 installer bundles. See
5155 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
5156 for details of what's new in Vidalia 0.2.3.
5157 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
5158 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
5159 configuration file, rather than the old Privoxy.
5160 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
5161 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
5162 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
5163 better compatibility with OS X 10.6, aka Snow Leopard.
5164 - OS X Vidalia Bundle: The multi-package installer is now replaced
5165 by a simple drag and drop to the /Applications folder. This change
5166 occurred with the upgrade to Vidalia 0.2.3.
5169 Changes in version 0.2.1.19 - 2009-07-28
5170 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
5171 services on Tor 0.2.1.3-alpha through 0.2.1.18.
5174 - Make accessing hidden services on 0.2.1.x work right again.
5175 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
5176 part of patch provided by "optimist".
5179 - When a relay/bridge is writing out its identity key fingerprint to
5180 the "fingerprint" file and to its logs, write it without spaces. Now
5181 it will look like the fingerprints in our bridges documentation,
5182 and confuse fewer users.
5185 - Relays no longer publish a new server descriptor if they change
5186 their MaxAdvertisedBandwidth config option but it doesn't end up
5187 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
5188 fixes bug 1026. Patch from Sebastian.
5189 - Avoid leaking memory every time we get a create cell but we have
5190 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
5191 fixes bug 1034. Reported by BarkerJr.
5194 Changes in version 0.2.1.18 - 2009-07-24
5195 Tor 0.2.1.18 lays the foundations for performance improvements,
5196 adds status events to help users diagnose bootstrap problems, adds
5197 optional authentication/authorization for hidden services, fixes a
5198 variety of potential anonymity problems, and includes a huge pile of
5199 other features and bug fixes.
5202 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
5205 Changes in version 0.2.1.17-rc - 2009-07-07
5206 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
5207 candidate for the 0.2.1.x series. It lays the groundwork for further
5208 client performance improvements, and also fixes a big bug with directory
5209 authorities that were causing them to assign Guard and Stable flags
5212 The Windows bundles also finally include the geoip database that we
5213 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
5214 should actually install Torbutton rather than giving you a cryptic
5215 failure message (oops).
5218 - Clients now use the bandwidth values in the consensus, rather than
5219 the bandwidth values in each relay descriptor. This approach opens
5220 the door to more accurate bandwidth estimates once the directory
5221 authorities start doing active measurements. Implements more of
5225 - When Tor clients restart after 1-5 days, they discard all their
5226 cached descriptors as too old, but they still use the cached
5227 consensus document. This approach is good for robustness, but
5228 bad for performance: since they don't know any bandwidths, they
5229 end up choosing at random rather than weighting their choice by
5230 speed. Fixed by the above feature of putting bandwidths in the
5231 consensus. Bugfix on 0.2.0.x.
5232 - Directory authorities were neglecting to mark relays down in their
5233 internal histories if the relays fall off the routerlist without
5234 ever being found unreachable. So there were relays in the histories
5235 that haven't been seen for eight months, and are listed as being
5236 up for eight months. This wreaked havoc on the "median wfu"
5237 and "median mtbf" calculations, in turn making Guard and Stable
5238 flags very wrong, hurting network performance. Fixes bugs 696 and
5239 969. Bugfix on 0.2.0.6-alpha.
5242 - Serve the DirPortFrontPage page even when we have been approaching
5243 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
5244 - The control port would close the connection before flushing long
5245 replies, such as the network consensus, if a QUIT command was issued
5246 before the reply had completed. Now, the control port flushes all
5247 pending replies before closing the connection. Also fixed a spurious
5248 warning when a QUIT command is issued after a malformed or rejected
5249 AUTHENTICATE command, but before the connection was closed. Patch
5250 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
5251 - When we can't find an intro key for a v2 hidden service descriptor,
5252 fall back to the v0 hidden service descriptor and log a bug message.
5253 Workaround for bug 1024.
5254 - Fix a log message that did not respect the SafeLogging option.
5258 - If we're a relay and we change our IP address, be more verbose
5259 about the reason that made us change. Should help track down
5260 further bugs for relays on dynamic IP addresses.
5263 Changes in version 0.2.0.35 - 2009-06-24
5265 - Avoid crashing in the presence of certain malformed descriptors.
5266 Found by lark, and by automated fuzzing.
5267 - Fix an edge case where a malicious exit relay could convince a
5268 controller that the client's DNS question resolves to an internal IP
5269 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5272 - Finally fix the bug where dynamic-IP relays disappear when their
5273 IP address changes: directory mirrors were mistakenly telling
5274 them their old address if they asked via begin_dir, so they
5275 never got an accurate answer about their new address, so they
5276 just vanished after a day. For belt-and-suspenders, relays that
5277 don't set Address in their config now avoid using begin_dir for
5278 all direct connections. Should fix bugs 827, 883, and 900.
5279 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5280 that would occur on some exit nodes when DNS failures and timeouts
5281 occurred in certain patterns. Fix for bug 957.
5284 - When starting with a cache over a few days old, do not leak
5285 memory for the obsolete router descriptors in it. Bugfix on
5286 0.2.0.33; fixes bug 672.
5287 - Hidden service clients didn't use a cached service descriptor that
5288 was older than 15 minutes, but wouldn't fetch a new one either,
5289 because there was already one in the cache. Now, fetch a v2
5290 descriptor unless the same descriptor was added to the cache within
5291 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5294 Changes in version 0.2.1.16-rc - 2009-06-20
5295 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
5296 a bunch of minor bugs.
5299 - Fix an edge case where a malicious exit relay could convince a
5300 controller that the client's DNS question resolves to an internal IP
5301 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5303 o Major performance improvements (on 0.2.0.x):
5304 - Disable and refactor some debugging checks that forced a linear scan
5305 over the whole server-side DNS cache. These accounted for over 50%
5306 of CPU time on a relatively busy exit node's gprof profile. Found
5308 - Disable some debugging checks that appeared in exit node profile
5312 - Update to the "June 3 2009" ip-to-country file.
5313 - Do not have tor-resolve automatically refuse all .onion addresses;
5314 if AutomapHostsOnResolve is set in your torrc, this will work fine.
5316 o Minor bugfixes (on 0.2.0.x):
5317 - Log correct error messages for DNS-related network errors on
5319 - Fix a race condition that could cause crashes or memory corruption
5320 when running as a server with a controller listening for log
5322 - Avoid crashing when we have a policy specified in a DirPolicy or
5323 SocksPolicy or ReachableAddresses option with ports set on it,
5324 and we re-load the policy. May fix bug 996.
5325 - Hidden service clients didn't use a cached service descriptor that
5326 was older than 15 minutes, but wouldn't fetch a new one either,
5327 because there was already one in the cache. Now, fetch a v2
5328 descriptor unless the same descriptor was added to the cache within
5329 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5331 o Minor bugfixes (on 0.2.1.x):
5332 - Don't warn users about low port and hibernation mix when they
5333 provide a *ListenAddress directive to fix that. Bugfix on
5335 - When switching back and forth between bridge mode, do not start
5336 gathering GeoIP data until two hours have passed.
5337 - Do not complain that the user has requested an excluded node as
5338 an exit when the node is not really an exit. This could happen
5339 because the circuit was for testing, or an introduction point.
5343 Changes in version 0.2.1.15-rc - 2009-05-25
5344 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
5345 series. It fixes a major bug on fast exit relays, as well as a variety
5348 o Major bugfixes (on 0.2.0.x):
5349 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5350 that would occur on some exit nodes when DNS failures and timeouts
5351 occurred in certain patterns. Fix for bug 957.
5353 o Minor bugfixes (on 0.2.0.x):
5354 - Actually return -1 in the error case for read_bandwidth_usage().
5355 Harmless bug, since we currently don't care about the return value
5356 anywhere. Bugfix on 0.2.0.9-alpha.
5357 - Provide a more useful log message if bug 977 (related to buffer
5358 freelists) ever reappears, and do not crash right away.
5359 - Fix an assertion failure on 64-bit platforms when we allocated
5360 memory right up to the end of a memarea, then realigned the memory
5361 one step beyond the end. Fixes a possible cause of bug 930.
5362 - Protect the count of open sockets with a mutex, so we can't
5363 corrupt it when two threads are closing or opening sockets at once.
5364 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
5365 - Don't allow a bridge to publish its router descriptor to a
5366 non-bridge directory authority. Fixes part of bug 932.
5367 - When we change to or from being a bridge, reset our counts of
5368 client usage by country. Fixes bug 932.
5369 - Fix a bug that made stream bandwidth get misreported to the
5371 - Stop using malloc_usable_size() to use more area than we had
5372 actually allocated: it was safe, but made valgrind really unhappy.
5373 - Fix a memory leak when v3 directory authorities load their keys
5374 and cert from disk. Bugfix on 0.2.0.1-alpha.
5376 o Minor bugfixes (on 0.2.1.x):
5377 - Fix use of freed memory when deciding to mark a non-addable
5378 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
5381 Changes in version 0.2.1.14-rc - 2009-04-12
5382 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
5383 series. It begins fixing some major performance problems, and also
5384 finally addresses the bug that was causing relays on dynamic IP
5385 addresses to fall out of the directory.
5388 - Clients replace entry guards that were chosen more than a few months
5389 ago. This change should significantly improve client performance,
5390 especially once more people upgrade, since relays that have been
5391 a guard for a long time are currently overloaded.
5393 o Major bugfixes (on 0.2.0):
5394 - Finally fix the bug where dynamic-IP relays disappear when their
5395 IP address changes: directory mirrors were mistakenly telling
5396 them their old address if they asked via begin_dir, so they
5397 never got an accurate answer about their new address, so they
5398 just vanished after a day. For belt-and-suspenders, relays that
5399 don't set Address in their config now avoid using begin_dir for
5400 all direct connections. Should fix bugs 827, 883, and 900.
5401 - Relays were falling out of the networkstatus consensus for
5402 part of a day if they changed their local config but the
5403 authorities discarded their new descriptor as "not sufficiently
5404 different". Now directory authorities accept a descriptor as changed
5405 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
5407 - Avoid crashing in the presence of certain malformed descriptors.
5408 Found by lark, and by automated fuzzing.
5411 - When generating circuit events with verbose nicknames for
5412 controllers, try harder to look up nicknames for routers on a
5413 circuit. (Previously, we would look in the router descriptors we had
5414 for nicknames, but not in the consensus.) Partial fix for bug 941.
5415 - If the bridge config line doesn't specify a port, assume 443.
5416 This makes bridge lines a bit smaller and easier for users to
5418 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
5419 bytes (aka 20KB/s), to match our documentation. Also update
5420 directory authorities so they always assign the Fast flag to relays
5421 with 20KB/s of capacity. Now people running relays won't suddenly
5422 find themselves not seeing any use, if the network gets faster
5424 - Update to the "April 3 2009" ip-to-country file.
5427 - Avoid trying to print raw memory to the logs when we decide to
5428 give up on downloading a given relay descriptor. Bugfix on
5430 - In tor-resolve, when the Tor client to use is specified by
5431 <hostname>:<port>, actually use the specified port rather than
5432 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
5433 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
5434 - When starting with a cache over a few days old, do not leak
5435 memory for the obsolete router descriptors in it. Bugfix on
5437 - Avoid double-free on list of successfully uploaded hidden
5438 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
5439 - Change memarea_strndup() implementation to work even when
5440 duplicating a string at the end of a page. This bug was
5441 harmless for now, but could have meant crashes later. Fix by
5442 lark. Bugfix on 0.2.1.1-alpha.
5443 - Limit uploaded directory documents to be 16M rather than 500K.
5444 The directory authorities were refusing v3 consensus votes from
5445 other authorities, since the votes are now 504K. Fixes bug 959;
5446 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
5447 - Directory authorities should never send a 503 "busy" response to
5448 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
5452 Changes in version 0.2.1.13-alpha - 2009-03-09
5453 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
5454 cleanups. We're finally getting close to a release candidate.
5457 - Correctly update the list of which countries we exclude as
5458 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
5459 lark. Bugfix on 0.2.1.6-alpha.
5461 o Minor bugfixes (on 0.2.0.x and earlier):
5462 - Automatically detect MacOSX versions earlier than 10.4.0, and
5463 disable kqueue from inside Tor when running with these versions.
5464 We previously did this from the startup script, but that was no
5465 help to people who didn't use the startup script. Resolves bug 863.
5466 - When we had picked an exit node for a connection, but marked it as
5467 "optional", and it turned out we had no onion key for the exit,
5468 stop wanting that exit and try again. This situation may not
5469 be possible now, but will probably become feasible with proposal
5470 158. Spotted by rovv. Fixes another case of bug 752.
5471 - Clients no longer cache certificates for authorities they do not
5472 recognize. Bugfix on 0.2.0.9-alpha.
5473 - When we can't transmit a DNS request due to a network error, retry
5474 it after a while, and eventually transmit a failing response to
5475 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
5476 - If the controller claimed responsibility for a stream, but that
5477 stream never finished making its connection, it would live
5478 forever in circuit_wait state. Now we close it after SocksTimeout
5479 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
5480 - Drop begin cells to a hidden service if they come from the middle
5481 of a circuit. Patch from lark.
5482 - When we erroneously receive two EXTEND cells for the same circuit
5483 ID on the same connection, drop the second. Patch from lark.
5484 - Fix a crash that occurs on exit nodes when a nameserver request
5485 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
5486 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
5488 - Do not assume that a stack-allocated character array will be
5489 64-bit aligned on platforms that demand that uint64_t access is
5490 aligned. Possible fix for bug 604.
5491 - Parse dates and IPv4 addresses in a locale- and libc-independent
5492 manner, to avoid platform-dependent behavior on malformed input.
5493 - Build correctly when configured to build outside the main source
5494 path. Patch from Michael Gold.
5495 - We were already rejecting relay begin cells with destination port
5496 of 0. Now also reject extend cells with destination port or address
5497 of 0. Suggested by lark.
5499 o Minor bugfixes (on 0.2.1.x):
5500 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
5501 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
5502 - If we're an exit node, scrub the IP address to which we are exiting
5503 in the logs. Bugfix on 0.2.1.8-alpha.
5506 - On Linux, use the prctl call to re-enable core dumps when the user
5508 - New controller event NEWCONSENSUS that lists the networkstatus
5509 lines for every recommended relay. Now controllers like Torflow
5510 can keep up-to-date on which relays they should be using.
5511 - Update to the "February 26 2009" ip-to-country file.
5514 Changes in version 0.2.0.34 - 2009-02-08
5515 Tor 0.2.0.34 features several more security-related fixes. You should
5516 upgrade, especially if you run an exit relay (remote crash) or a
5517 directory authority (remote infinite loop), or you're on an older
5518 (pre-XP) or not-recently-patched Windows (remote exploit).
5520 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
5521 have many known flaws, and nobody should be using them. You should
5522 upgrade. If you're using a Linux or BSD and its packages are obsolete,
5523 stop using those packages and upgrade anyway.
5526 - Fix an infinite-loop bug on handling corrupt votes under certain
5527 circumstances. Bugfix on 0.2.0.8-alpha.
5528 - Fix a temporary DoS vulnerability that could be performed by
5529 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5530 - Avoid a potential crash on exit nodes when processing malformed
5531 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
5532 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
5533 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
5536 - Fix compilation on systems where time_t is a 64-bit integer.
5537 Patch from Matthias Drochner.
5538 - Don't consider expiring already-closed client connections. Fixes
5539 bug 893. Bugfix on 0.0.2pre20.
5542 Changes in version 0.2.1.12-alpha - 2009-02-08
5543 Tor 0.2.1.12-alpha features several more security-related fixes. You
5544 should upgrade, especially if you run an exit relay (remote crash) or
5545 a directory authority (remote infinite loop), or you're on an older
5546 (pre-XP) or not-recently-patched Windows (remote exploit). It also
5547 includes a big pile of minor bugfixes and cleanups.
5550 - Fix an infinite-loop bug on handling corrupt votes under certain
5551 circumstances. Bugfix on 0.2.0.8-alpha.
5552 - Fix a temporary DoS vulnerability that could be performed by
5553 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5554 - Avoid a potential crash on exit nodes when processing malformed
5555 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
5558 - Let controllers actually ask for the "clients_seen" event for
5559 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
5560 reported by Matt Edman.
5561 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
5563 - Fix a bug in address parsing that was preventing bridges or hidden
5564 service targets from being at IPv6 addresses.
5565 - Solve a bug that kept hardware crypto acceleration from getting
5566 enabled when accounting was turned on. Fixes bug 907. Bugfix on
5568 - Remove a bash-ism from configure.in to build properly on non-Linux
5569 platforms. Bugfix on 0.2.1.1-alpha.
5570 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
5571 headers. Bugfix on 0.2.0.10-alpha.
5572 - Don't consider expiring already-closed client connections. Fixes
5573 bug 893. Bugfix on 0.0.2pre20.
5574 - Fix another interesting corner-case of bug 891 spotted by rovv:
5575 Previously, if two hosts had different amounts of clock drift, and
5576 one of them created a new connection with just the wrong timing,
5577 the other might decide to deprecate the new connection erroneously.
5578 Bugfix on 0.1.1.13-alpha.
5579 - Resolve a very rare crash bug that could occur when the user forced
5580 a nameserver reconfiguration during the middle of a nameserver
5581 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
5582 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
5583 Bugfix on 0.2.1.7-alpha.
5584 - If we're using bridges and our network goes away, be more willing
5585 to forgive our bridges and try again when we get an application
5586 request. Bugfix on 0.2.0.x.
5589 - Support platforms where time_t is 64 bits long. (Congratulations,
5590 NetBSD!) Patch from Matthias Drochner.
5591 - Add a 'getinfo status/clients-seen' controller command, in case
5592 controllers want to hear clients_seen events but connect late.
5595 - Disable GCC's strict alias optimization by default, to avoid the
5596 likelihood of its introducing subtle bugs whenever our code violates
5597 the letter of C99's alias rules.
5600 Changes in version 0.2.0.33 - 2009-01-21
5601 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
5602 useful to users. It also finally fixes a bug where a relay or client
5603 that's been off for many days would take a long time to bootstrap.
5605 This update also fixes an important security-related bug reported by
5606 Ilja van Sprundel. You should upgrade. (We'll send out more details
5607 about the bug once people have had some time to upgrade.)
5610 - Fix a heap-corruption bug that may be remotely triggerable on
5611 some platforms. Reported by Ilja van Sprundel.
5614 - When a stream at an exit relay is in state "resolving" or
5615 "connecting" and it receives an "end" relay cell, the exit relay
5616 would silently ignore the end cell and not close the stream. If
5617 the client never closes the circuit, then the exit relay never
5618 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
5620 - When sending CREATED cells back for a given circuit, use a 64-bit
5621 connection ID to find the right connection, rather than an addr:port
5622 combination. Now that we can have multiple OR connections between
5623 the same ORs, it is no longer possible to use addr:port to uniquely
5624 identify a connection.
5625 - Bridge relays that had DirPort set to 0 would stop fetching
5626 descriptors shortly after startup, and then briefly resume
5627 after a new bandwidth test and/or after publishing a new bridge
5628 descriptor. Bridge users that try to bootstrap from them would
5629 get a recent networkstatus but would get descriptors from up to
5630 18 hours earlier, meaning most of the descriptors were obsolete
5631 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
5632 - Prevent bridge relays from serving their 'extrainfo' document
5633 to anybody who asks, now that extrainfo docs include potentially
5634 sensitive aggregated client geoip summaries. Bugfix on
5636 - If the cached networkstatus consensus is more than five days old,
5637 discard it rather than trying to use it. In theory it could be
5638 useful because it lists alternate directory mirrors, but in practice
5639 it just means we spend many minutes trying directory mirrors that
5640 are long gone from the network. Also discard router descriptors as
5641 we load them if they are more than five days old, since the onion
5642 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
5645 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
5646 could make gcc generate non-functional binary search code. Bugfix
5648 - Build correctly on platforms without socklen_t.
5649 - Compile without warnings on solaris.
5650 - Avoid potential crash on internal error during signature collection.
5651 Fixes bug 864. Patch from rovv.
5652 - Correct handling of possible malformed authority signing key
5653 certificates with internal signature types. Fixes bug 880.
5654 Bugfix on 0.2.0.3-alpha.
5655 - Fix a hard-to-trigger resource leak when logging credential status.
5657 - When we can't initialize DNS because the network is down, do not
5658 automatically stop Tor from starting. Instead, we retry failed
5659 dns_init() every 10 minutes, and change the exit policy to reject
5660 *:* until one succeeds. Fixes bug 691.
5661 - Use 64 bits instead of 32 bits for connection identifiers used with
5662 the controller protocol, to greatly reduce risk of identifier reuse.
5663 - When we're choosing an exit node for a circuit, and we have
5664 no pending streams, choose a good general exit rather than one that
5665 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
5666 - Fix another case of assuming, when a specific exit is requested,
5667 that we know more than the user about what hosts it allows.
5668 Fixes one case of bug 752. Patch from rovv.
5669 - Clip the MaxCircuitDirtiness config option to a minimum of 10
5670 seconds. Warn the user if lower values are given in the
5671 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
5672 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
5673 user if lower values are given in the configuration. Bugfix on
5674 0.1.1.17-rc. Patch by Sebastian.
5675 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
5676 the cache because we already had a v0 descriptor with the same ID.
5677 Bugfix on 0.2.0.18-alpha.
5678 - Fix a race condition when freeing keys shared between main thread
5679 and CPU workers that could result in a memory leak. Bugfix on
5680 0.1.0.1-rc. Fixes bug 889.
5681 - Send a valid END cell back when a client tries to connect to a
5682 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
5683 840. Patch from rovv.
5684 - Check which hops rendezvous stream cells are associated with to
5685 prevent possible guess-the-streamid injection attacks from
5686 intermediate hops. Fixes another case of bug 446. Based on patch
5688 - If a broken client asks a non-exit router to connect somewhere,
5689 do not even do the DNS lookup before rejecting the connection.
5690 Fixes another case of bug 619. Patch from rovv.
5691 - When a relay gets a create cell it can't decrypt (e.g. because it's
5692 using the wrong onion key), we were dropping it and letting the
5693 client time out. Now actually answer with a destroy cell. Fixes
5694 bug 904. Bugfix on 0.0.2pre8.
5696 o Minor bugfixes (hidden services):
5697 - Do not throw away existing introduction points on SIGHUP. Bugfix on
5698 0.0.6pre1. Patch by Karsten. Fixes bug 874.
5701 - Report the case where all signatures in a detached set are rejected
5702 differently than the case where there is an error handling the
5704 - When we realize that another process has modified our cached
5705 descriptors, print out a more useful error message rather than
5706 triggering an assertion. Fixes bug 885. Patch from Karsten.
5707 - Implement the 0x20 hack to better resist DNS poisoning: set the
5708 case on outgoing DNS requests randomly, and reject responses that do
5709 not match the case correctly. This logic can be disabled with the
5710 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
5711 of servers that do not reliably preserve case in replies. See
5712 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
5714 - Check DNS replies for more matching fields to better resist DNS
5716 - Never use OpenSSL compression: it wastes RAM and CPU trying to
5717 compress cells, which are basically all encrypted, compressed, or
5721 Changes in version 0.2.1.11-alpha - 2009-01-20
5722 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
5723 week it will take a long time to bootstrap again" bug. It also fixes
5724 an important security-related bug reported by Ilja van Sprundel. You
5725 should upgrade. (We'll send out more details about the bug once people
5726 have had some time to upgrade.)
5729 - Fix a heap-corruption bug that may be remotely triggerable on
5730 some platforms. Reported by Ilja van Sprundel.
5733 - Discard router descriptors as we load them if they are more than
5734 five days old. Otherwise if Tor is off for a long time and then
5735 starts with cached descriptors, it will try to use the onion
5736 keys in those obsolete descriptors when building circuits. Bugfix
5737 on 0.2.0.x. Fixes bug 887.
5740 - Try to make sure that the version of Libevent we're running with
5741 is binary-compatible with the one we built with. May address bug
5743 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
5744 for bug 905. Bugfix on 0.2.1.7-alpha.
5745 - Add a new --enable-local-appdata configuration switch to change
5746 the default location of the datadir on win32 from APPDATA to
5747 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
5748 entirely. Patch from coderman.
5751 - Make outbound DNS packets respect the OutboundBindAddress setting.
5752 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
5753 - When our circuit fails at the first hop (e.g. we get a destroy
5754 cell back), avoid using that OR connection anymore, and also
5755 tell all the one-hop directory requests waiting for it that they
5756 should fail. Bugfix on 0.2.1.3-alpha.
5757 - In the torify(1) manpage, mention that tsocks will leak your
5761 Changes in version 0.2.1.10-alpha - 2009-01-06
5762 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
5763 would make the bridge relay not so useful if it had DirPort set to 0,
5764 and one that could let an attacker learn a little bit of information
5765 about the bridge's users), and a bug that would cause your Tor relay
5766 to ignore a circuit create request it can't decrypt (rather than reply
5767 with an error). It also fixes a wide variety of other bugs.
5770 - If the cached networkstatus consensus is more than five days old,
5771 discard it rather than trying to use it. In theory it could
5772 be useful because it lists alternate directory mirrors, but in
5773 practice it just means we spend many minutes trying directory
5774 mirrors that are long gone from the network. Helps bug 887 a bit;
5776 - Bridge relays that had DirPort set to 0 would stop fetching
5777 descriptors shortly after startup, and then briefly resume
5778 after a new bandwidth test and/or after publishing a new bridge
5779 descriptor. Bridge users that try to bootstrap from them would
5780 get a recent networkstatus but would get descriptors from up to
5781 18 hours earlier, meaning most of the descriptors were obsolete
5782 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
5783 - Prevent bridge relays from serving their 'extrainfo' document
5784 to anybody who asks, now that extrainfo docs include potentially
5785 sensitive aggregated client geoip summaries. Bugfix on
5789 - New controller event "clients_seen" to report a geoip-based summary
5790 of which countries we've seen clients from recently. Now controllers
5791 like Vidalia can show bridge operators that they're actually making
5793 - Build correctly against versions of OpenSSL 0.9.8 or later built
5794 without support for deprecated functions.
5795 - Update to the "December 19 2008" ip-to-country file.
5797 o Minor bugfixes (on 0.2.0.x):
5798 - Authorities now vote for the Stable flag for any router whose
5799 weighted MTBF is at least 5 days, regardless of the mean MTBF.
5800 - Do not remove routers as too old if we do not have any consensus
5801 document. Bugfix on 0.2.0.7-alpha.
5802 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
5803 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
5804 - When an exit relay resolves a stream address to a local IP address,
5805 do not just keep retrying that same exit relay over and
5806 over. Instead, just close the stream. Addresses bug 872. Bugfix
5807 on 0.2.0.32. Patch from rovv.
5808 - If a hidden service sends us an END cell, do not consider
5809 retrying the connection; just close it. Patch from rovv.
5810 - When we made bridge authorities stop serving bridge descriptors over
5811 unencrypted links, we also broke DirPort reachability testing for
5812 bridges. So bridges with a non-zero DirPort were printing spurious
5813 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
5814 - When a relay gets a create cell it can't decrypt (e.g. because it's
5815 using the wrong onion key), we were dropping it and letting the
5816 client time out. Now actually answer with a destroy cell. Fixes
5817 bug 904. Bugfix on 0.0.2pre8.
5818 - Squeeze 2-5% out of client performance (according to oprofile) by
5819 improving the implementation of some policy-manipulation functions.
5821 o Minor bugfixes (on 0.2.1.x):
5822 - Make get_interface_address() function work properly again; stop
5823 guessing the wrong parts of our address as our address.
5824 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
5825 send on that circuit. Otherwise we might violate the proposal-110
5826 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
5828 - When we're sending non-EXTEND cells to the first hop in a circuit,
5829 for example to use an encrypted directory connection, we don't need
5830 to use RELAY_EARLY cells: the first hop knows what kind of cell
5831 it is, and nobody else can even see the cell type. Conserving
5832 RELAY_EARLY cells makes it easier to cannibalize circuits like
5834 - Stop logging nameserver addresses in reverse order.
5835 - If we are retrying a directory download slowly over and over, do
5836 not automatically give up after the 254th failure. Bugfix on
5838 - Resume reporting accurate "stream end" reasons to the local control
5839 port. They were lost in the changes for Proposal 148. Bugfix on
5842 o Deprecated and removed features:
5843 - The old "tor --version --version" command, which would print out
5844 the subversion "Id" of most of the source files, is now removed. It
5845 turned out to be less useful than we'd expected, and harder to
5848 o Code simplifications and refactoring:
5849 - Change our header file guard macros to be less likely to conflict
5850 with system headers. Adam Langley noticed that we were conflicting
5851 with log.h on Android.
5852 - Tool-assisted documentation cleanup. Nearly every function or
5853 static variable in Tor should have its own documentation now.
5856 Changes in version 0.2.1.9-alpha - 2008-12-25
5857 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
5859 o New directory authorities:
5860 - gabelmoo (the authority run by Karsten Loesing) now has a new
5864 - Never use a connection with a mismatched address to extend a
5865 circuit, unless that connection is canonical. A canonical
5866 connection is one whose address is authenticated by the router's
5867 identity key, either in a NETINFO cell or in a router descriptor.
5868 - Avoid a possible memory corruption bug when receiving hidden service
5869 descriptors. Bugfix on 0.2.1.6-alpha.
5872 - Fix a logic error that would automatically reject all but the first
5873 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
5874 part of bug 813/868. Bug spotted by coderman.
5875 - When a stream at an exit relay is in state "resolving" or
5876 "connecting" and it receives an "end" relay cell, the exit relay
5877 would silently ignore the end cell and not close the stream. If
5878 the client never closes the circuit, then the exit relay never
5879 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
5881 - When we can't initialize DNS because the network is down, do not
5882 automatically stop Tor from starting. Instead, retry failed
5883 dns_init() every 10 minutes, and change the exit policy to reject
5884 *:* until one succeeds. Fixes bug 691.
5887 - Give a better error message when an overzealous init script says
5888 "sudo -u username tor --user username". Makes Bug 882 easier for
5890 - When a directory authority gives us a new guess for our IP address,
5891 log which authority we used. Hopefully this will help us debug
5892 the recent complaints about bad IP address guesses.
5893 - Detect svn revision properly when we're using git-svn.
5894 - Try not to open more than one descriptor-downloading connection
5895 to an authority at once. This should reduce load on directory
5896 authorities. Fixes bug 366.
5897 - Add cross-certification to newly generated certificates, so that
5898 a signing key is enough information to look up a certificate.
5899 Partial implementation of proposal 157.
5900 - Start serving certificates by <identity digest, signing key digest>
5901 pairs. Partial implementation of proposal 157.
5902 - Clients now never report any stream end reason except 'MISC'.
5903 Implements proposal 148.
5904 - On platforms with a maximum syslog string length, truncate syslog
5905 messages to that length ourselves, rather than relying on the
5906 system to do it for us.
5907 - Optimize out calls to time(NULL) that occur for every IO operation,
5908 or for every cell. On systems where time() is a slow syscall,
5909 this fix will be slightly helpful.
5910 - Exit servers can now answer resolve requests for ip6.arpa addresses.
5911 - When we download a descriptor that we then immediately (as
5912 a directory authority) reject, do not retry downloading it right
5913 away. Should save some bandwidth on authorities. Fix for bug
5914 888. Patch by Sebastian Hahn.
5915 - When a download gets us zero good descriptors, do not notify
5916 Tor that new directory information has arrived.
5917 - Avoid some nasty corner cases in the logic for marking connections
5918 as too old or obsolete or noncanonical for circuits. Partial
5921 o Minor features (controller):
5922 - New CONSENSUS_ARRIVED event to note when a new consensus has
5923 been fetched and validated.
5924 - When we realize that another process has modified our cached
5925 descriptors file, print out a more useful error message rather
5926 than triggering an assertion. Fixes bug 885. Patch from Karsten.
5927 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
5928 controllers to prevent SIGHUP from reloading the
5929 configuration. Fixes bug 856.
5932 - Resume using the correct "REASON=" stream when telling the
5933 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
5934 - When a canonical connection appears later in our internal list
5935 than a noncanonical one for a given OR ID, always use the
5936 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
5938 - Clip the MaxCircuitDirtiness config option to a minimum of 10
5939 seconds. Warn the user if lower values are given in the
5940 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
5941 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
5942 user if lower values are given in the configuration. Bugfix on
5943 0.1.1.17-rc. Patch by Sebastian.
5944 - Fix a race condition when freeing keys shared between main thread
5945 and CPU workers that could result in a memory leak. Bugfix on
5946 0.1.0.1-rc. Fixes bug 889.
5948 o Minor bugfixes (hidden services):
5949 - Do not throw away existing introduction points on SIGHUP (bugfix on
5950 0.0.6pre1); also, do not stall hidden services because we're
5951 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
5952 by John Brooks. Patch by Karsten. Fixes bug 874.
5953 - Fix a memory leak when we decline to add a v2 rendezvous
5954 descriptor to the cache because we already had a v0 descriptor
5955 with the same ID. Bugfix on 0.2.0.18-alpha.
5957 o Deprecated and removed features:
5958 - RedirectExits has been removed. It was deprecated since
5960 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
5961 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
5962 - Cell pools are now always enabled; --disable-cell-pools is ignored.
5964 o Code simplifications and refactoring:
5965 - Rename the confusing or_is_obsolete field to the more appropriate
5966 is_bad_for_new_circs, and move it to or_connection_t where it
5968 - Move edge-only flags from connection_t to edge_connection_t: not
5969 only is this better coding, but on machines of plausible alignment,
5970 it should save 4-8 bytes per connection_t. "Every little bit helps."
5971 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
5972 for consistency; keep old option working for backward compatibility.
5973 - Simplify the code for finding connections to use for a circuit.
5976 Changes in version 0.2.1.8-alpha - 2008-12-08
5977 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
5978 builds better on unusual platforms like Solaris and old OS X, and
5979 fixes a variety of other issues.
5982 - New DirPortFrontPage option that takes an html file and publishes
5983 it as "/" on the DirPort. Now relay operators can provide a
5984 disclaimer without needing to set up a separate webserver. There's
5985 a sample disclaimer in contrib/tor-exit-notice.html.
5988 - When the client is choosing entry guards, now it selects at most
5989 one guard from a given relay family. Otherwise we could end up with
5990 all of our entry points into the network run by the same operator.
5991 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
5994 - Fix a DOS opportunity during the voting signature collection process
5995 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
5996 - Fix a possible segfault when establishing an exit connection. Bugfix
6000 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
6002 - Made Tor a little less aggressive about deleting expired
6003 certificates. Partial fix for bug 854.
6004 - Stop doing unaligned memory access that generated bus errors on
6005 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
6006 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
6007 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
6008 - Make USR2 log-level switch take effect immediately. Bugfix on
6010 - If one win32 nameserver fails to get added, continue adding the
6011 rest, and don't automatically fail.
6012 - Use fcntl() for locking when flock() is not available. Should fix
6013 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
6014 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6015 could make gcc generate non-functional binary search code. Bugfix
6017 - Build correctly on platforms without socklen_t.
6018 - Avoid potential crash on internal error during signature collection.
6019 Fixes bug 864. Patch from rovv.
6020 - Do not use C's stdio library for writing to log files. This will
6021 improve logging performance by a minute amount, and will stop
6022 leaking fds when our disk is full. Fixes bug 861.
6023 - Stop erroneous use of O_APPEND in cases where we did not in fact
6024 want to re-seek to the end of a file before every last write().
6025 - Correct handling of possible malformed authority signing key
6026 certificates with internal signature types. Fixes bug 880. Bugfix
6028 - Fix a hard-to-trigger resource leak when logging credential status.
6032 - Directory mirrors no longer fetch the v1 directory or
6033 running-routers files. They are obsolete, and nobody asks for them
6034 anymore. This is the first step to making v1 authorities obsolete.
6036 o Minor features (controller):
6037 - Return circuit purposes in response to GETINFO circuit-status. Fixes
6041 Changes in version 0.2.0.32 - 2008-11-20
6042 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
6043 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6044 a smaller security flaw that might allow an attacker to access local
6045 services, further improves hidden service performance, and fixes a
6046 variety of other issues.
6049 - The "User" and "Group" config options did not clear the
6050 supplementary group entries for the Tor process. The "User" option
6051 is now more robust, and we now set the groups to the specified
6052 user's primary group. The "Group" option is now ignored. For more
6053 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6054 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6055 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
6056 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6057 consistently obeyed: if an exit relay refuses a stream because its
6058 exit policy doesn't allow it, we would remember what IP address
6059 the relay said the destination address resolves to, even if it's
6060 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6063 - Fix a DOS opportunity during the voting signature collection process
6064 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6066 o Major bugfixes (hidden services):
6067 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6068 we were failing the whole hidden service request when the v0
6069 descriptor fetch fails, even if the v2 fetch is still pending and
6070 might succeed. Similarly, if the last v2 fetch fails, we were
6071 failing the whole hidden service request even if a v0 fetch is
6072 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6073 - When extending a circuit to a hidden service directory to upload a
6074 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6075 requests failed, because the router descriptor has not been
6076 downloaded yet. In these cases, do not attempt to upload the
6077 rendezvous descriptor, but wait until the router descriptor is
6078 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
6079 descriptor from a hidden service directory for which the router
6080 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
6084 - Fix several infrequent memory leaks spotted by Coverity.
6085 - When testing for libevent functions, set the LDFLAGS variable
6086 correctly. Found by Riastradh.
6087 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6088 bootstrapping with tunneled directory connections. Bugfix on
6089 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6090 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6091 and we know that server B rejects most-but-not all connections to
6092 port 80, we would previously reject the connection. Now, we assume
6093 the user knows what they were asking for. Fixes bug 752. Bugfix
6094 on 0.0.9rc5. Diagnosed by BarkerJr.
6095 - If we overrun our per-second write limits a little, count this as
6096 having used up our write allocation for the second, and choke
6097 outgoing directory writes. Previously, we had only counted this when
6098 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
6099 Bugfix on 0.2.0.x (??).
6100 - Remove the old v2 directory authority 'lefkada' from the default
6101 list. It has been gone for many months.
6102 - Stop doing unaligned memory access that generated bus errors on
6103 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
6104 - Make USR2 log-level switch take effect immediately. Bugfix on
6107 o Minor bugfixes (controller):
6108 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
6109 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
6112 Changes in version 0.2.1.7-alpha - 2008-11-08
6113 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
6114 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6115 a smaller security flaw that might allow an attacker to access local
6116 services, adds better defense against DNS poisoning attacks on exit
6117 relays, further improves hidden service performance, and fixes a
6118 variety of other issues.
6121 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6122 consistently obeyed: if an exit relay refuses a stream because its
6123 exit policy doesn't allow it, we would remember what IP address
6124 the relay said the destination address resolves to, even if it's
6125 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6126 - The "User" and "Group" config options did not clear the
6127 supplementary group entries for the Tor process. The "User" option
6128 is now more robust, and we now set the groups to the specified
6129 user's primary group. The "Group" option is now ignored. For more
6130 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6131 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6132 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
6133 - Do not use or believe expired v3 authority certificates. Patch
6134 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
6137 - Now NodeFamily and MyFamily config options allow spaces in
6138 identity fingerprints, so it's easier to paste them in.
6139 Suggested by Lucky Green.
6140 - Implement the 0x20 hack to better resist DNS poisoning: set the
6141 case on outgoing DNS requests randomly, and reject responses that do
6142 not match the case correctly. This logic can be disabled with the
6143 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
6144 of servers that do not reliably preserve case in replies. See
6145 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
6147 - Preserve case in replies to DNSPort requests in order to support
6148 the 0x20 hack for resisting DNS poisoning attacks.
6150 o Hidden service performance improvements:
6151 - When the client launches an introduction circuit, retry with a
6152 new circuit after 30 seconds rather than 60 seconds.
6153 - Launch a second client-side introduction circuit in parallel
6154 after a delay of 15 seconds (based on work by Christian Wilms).
6155 - Hidden services start out building five intro circuits rather
6156 than three, and when the first three finish they publish a service
6157 descriptor using those. Now we publish our service descriptor much
6158 faster after restart.
6161 - Minor fix in the warning messages when you're having problems
6162 bootstrapping; also, be more forgiving of bootstrap problems when
6163 we're still making incremental progress on a given bootstrap phase.
6164 - When we're choosing an exit node for a circuit, and we have
6165 no pending streams, choose a good general exit rather than one that
6166 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
6167 - Send a valid END cell back when a client tries to connect to a
6168 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
6169 840. Patch from rovv.
6170 - If a broken client asks a non-exit router to connect somewhere,
6171 do not even do the DNS lookup before rejecting the connection.
6172 Fixes another case of bug 619. Patch from rovv.
6173 - Fix another case of assuming, when a specific exit is requested,
6174 that we know more than the user about what hosts it allows.
6175 Fixes another case of bug 752. Patch from rovv.
6176 - Check which hops rendezvous stream cells are associated with to
6177 prevent possible guess-the-streamid injection attacks from
6178 intermediate hops. Fixes another case of bug 446. Based on patch
6180 - Avoid using a negative right-shift when comparing 32-bit
6181 addresses. Possible fix for bug 845 and bug 811.
6182 - Make the assert_circuit_ok() function work correctly on circuits that
6183 have already been marked for close.
6184 - Fix read-off-the-end-of-string error in unit tests when decoding
6185 introduction points.
6186 - Fix uninitialized size field for memory area allocation: may improve
6187 memory performance during directory parsing.
6188 - Treat duplicate certificate fetches as failures, so that we do
6189 not try to re-fetch an expired certificate over and over and over.
6190 - Do not say we're fetching a certificate when we'll in fact skip it
6191 because of a pending download.
6194 Changes in version 0.2.1.6-alpha - 2008-09-30
6195 Tor 0.2.1.6-alpha further improves performance and robustness of
6196 hidden services, starts work on supporting per-country relay selection,
6197 and fixes a variety of smaller issues.
6200 - Implement proposal 121: make it possible to build hidden services
6201 that only certain clients are allowed to connect to. This is
6202 enforced at several points, so that unauthorized clients are unable
6203 to send INTRODUCE cells to the service, or even (depending on the
6204 type of authentication) to learn introduction points. This feature
6205 raises the bar for certain kinds of active attacks against hidden
6206 services. Code by Karsten Loesing.
6207 - Relays now store and serve v2 hidden service descriptors by default,
6208 i.e., the new default value for HidServDirectoryV2 is 1. This is
6209 the last step in proposal 114, which aims to make hidden service
6210 lookups more reliable.
6211 - Start work to allow node restrictions to include country codes. The
6212 syntax to exclude nodes in a country with country code XX is
6213 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
6214 refinement to decide what config options should take priority if
6215 you ask to both use a particular node and exclude it.
6216 - Allow ExitNodes list to include IP ranges and country codes, just
6217 like the Exclude*Nodes lists. Patch from Robert Hogan.
6220 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
6221 Tor to fail to start if you had it configured to use a bridge
6222 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
6223 - When extending a circuit to a hidden service directory to upload a
6224 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6225 requests failed, because the router descriptor had not been
6226 downloaded yet. In these cases, we now wait until the router
6227 descriptor is downloaded, and then retry. Likewise, clients
6228 now skip over a hidden service directory if they don't yet have
6229 its router descriptor, rather than futilely requesting it and
6230 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
6232 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6233 we were failing the whole hidden service request when the v0
6234 descriptor fetch fails, even if the v2 fetch is still pending and
6235 might succeed. Similarly, if the last v2 fetch fails, we were
6236 failing the whole hidden service request even if a v0 fetch is
6237 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6238 - DNS replies need to have names matching their requests, but
6239 these names should be in the questions section, not necessarily
6240 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
6243 - Update to the "September 1 2008" ip-to-country file.
6244 - Allow ports 465 and 587 in the default exit policy again. We had
6245 rejected them in 0.1.0.15, because back in 2005 they were commonly
6246 misconfigured and ended up as spam targets. We hear they are better
6247 locked down these days.
6248 - Use a lockfile to make sure that two Tor processes are not
6249 simultaneously running with the same datadir.
6250 - Serve the latest v3 networkstatus consensus via the control
6251 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
6252 - Better logging about stability/reliability calculations on directory
6254 - Drop the requirement to have an open dir port for storing and
6255 serving v2 hidden service descriptors.
6256 - Directory authorities now serve a /tor/dbg-stability.txt URL to
6257 help debug WFU and MTBF calculations.
6258 - Implement most of Proposal 152: allow specialized servers to permit
6259 single-hop circuits, and clients to use those servers to build
6260 single-hop circuits when using a specialized controller. Patch
6261 from Josh Albrecht. Resolves feature request 768.
6262 - Add a -p option to tor-resolve for specifying the SOCKS port: some
6263 people find host:port too confusing.
6264 - Make TrackHostExit mappings expire a while after their last use, not
6265 after their creation. Patch from Robert Hogan.
6266 - Provide circuit purposes along with circuit events to the controller.
6269 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
6271 - Fixed some memory leaks -- some quite frequent, some almost
6272 impossible to trigger -- based on results from Coverity.
6273 - When testing for libevent functions, set the LDFLAGS variable
6274 correctly. Found by Riastradh.
6275 - Fix an assertion bug in parsing policy-related options; possible fix
6277 - Catch and report a few more bootstrapping failure cases when Tor
6278 fails to establish a TCP connection. Cleanup on 0.2.1.x.
6279 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6280 bootstrapping with tunneled directory connections. Bugfix on
6281 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6282 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6283 and we know that server B rejects most-but-not all connections to
6284 port 80, we would previously reject the connection. Now, we assume
6285 the user knows what they were asking for. Fixes bug 752. Bugfix
6286 on 0.0.9rc5. Diagnosed by BarkerJr.
6287 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
6288 service directories if they have no advertised dir port. Bugfix
6290 - If we overrun our per-second write limits a little, count this as
6291 having used up our write allocation for the second, and choke
6292 outgoing directory writes. Previously, we had only counted this when
6293 we had met our limits precisely. Fixes bug 824. Patch by rovv.
6294 Bugfix on 0.2.0.x (??).
6295 - Avoid a "0 divided by 0" calculation when calculating router uptime
6296 at directory authorities. Bugfix on 0.2.0.8-alpha.
6297 - Make DNS resolved controller events into "CLOSED", not
6298 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
6300 - Fix a bug where an unreachable relay would establish enough
6301 reachability testing circuits to do a bandwidth test -- if
6302 we already have a connection to the middle hop of the testing
6303 circuit, then it could establish the last hop by using the existing
6304 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
6305 circuits no longer use entry guards in 0.2.1.3-alpha.
6306 - If we have correct permissions on $datadir, we complain to stdout
6307 and fail to start. But dangerous permissions on
6308 $datadir/cached-status/ would cause us to open a log and complain
6309 there. Now complain to stdout and fail to start in both cases. Fixes
6310 bug 820, reported by seeess.
6311 - Remove the old v2 directory authority 'lefkada' from the default
6312 list. It has been gone for many months.
6314 o Code simplifications and refactoring:
6315 - Revise the connection_new functions so that a more typesafe variant
6316 exists. This will work better with Coverity, and let us find any
6317 actual mistakes we're making here.
6318 - Refactor unit testing logic so that dmalloc can be used sensibly
6319 with unit tests to check for memory leaks.
6320 - Move all hidden-service related fields from connection and circuit
6321 structure to substructures: this way they won't eat so much memory.
6324 Changes in version 0.2.0.31 - 2008-09-03
6325 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
6326 a big bug we're seeing where in rare cases traffic from one Tor stream
6327 gets mixed into another stream, and fixes a variety of smaller issues.
6330 - Make sure that two circuits can never exist on the same connection
6331 with the same circuit ID, even if one is marked for close. This
6332 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
6333 - Relays now reject risky extend cells: if the extend cell includes
6334 a digest of all zeroes, or asks to extend back to the relay that
6335 sent the extend cell, tear down the circuit. Ideas suggested
6337 - If not enough of our entry guards are available so we add a new
6338 one, we might use the new one even if it overlapped with the
6339 current circuit's exit relay (or its family). Anonymity bugfix
6340 pointed out by rovv.
6343 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6344 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6345 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6346 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6347 - Pick size of default geoip filename string correctly on windows.
6348 Fixes bug 806. Bugfix on 0.2.0.30.
6349 - Make the autoconf script accept the obsolete --with-ssl-dir
6350 option as an alias for the actually-working --with-openssl-dir
6351 option. Fix the help documentation to recommend --with-openssl-dir.
6352 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6353 - When using the TransPort option on OpenBSD, and using the User
6354 option to change UID and drop privileges, make sure to open
6355 /dev/pf before dropping privileges. Fixes bug 782. Patch from
6356 Christopher Davis. Bugfix on 0.1.2.1-alpha.
6357 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6358 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6359 on the client side when connecting to a hidden service. Bugfix
6360 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6361 - When closing an application-side connection because its circuit is
6362 getting torn down, generate the stream event correctly. Bugfix on
6363 0.1.2.x. Anonymous patch.
6366 Changes in version 0.2.1.5-alpha - 2008-08-31
6367 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
6368 in a lot of the infrastructure for adding authorization to hidden
6369 services, lays the groundwork for having clients read their load
6370 balancing information out of the networkstatus consensus rather than
6371 the individual router descriptors, addresses two potential anonymity
6372 issues, and fixes a variety of smaller issues.
6375 - Convert many internal address representations to optionally hold
6377 - Generate and accept IPv6 addresses in many protocol elements.
6378 - Make resolver code handle nameservers located at ipv6 addresses.
6379 - Begin implementation of proposal 121 ("Client authorization for
6380 hidden services"): configure hidden services with client
6381 authorization, publish descriptors for them, and configure
6382 authorization data for hidden services at clients. The next
6383 step is to actually access hidden services that perform client
6385 - More progress toward proposal 141: Network status consensus
6386 documents and votes now contain bandwidth information for each
6387 router and a summary of that router's exit policy. Eventually this
6388 will be used by clients so that they do not have to download every
6389 known descriptor before building circuits.
6391 o Major bugfixes (on 0.2.0.x and before):
6392 - When sending CREATED cells back for a given circuit, use a 64-bit
6393 connection ID to find the right connection, rather than an addr:port
6394 combination. Now that we can have multiple OR connections between
6395 the same ORs, it is no longer possible to use addr:port to uniquely
6396 identify a connection.
6397 - Relays now reject risky extend cells: if the extend cell includes
6398 a digest of all zeroes, or asks to extend back to the relay that
6399 sent the extend cell, tear down the circuit. Ideas suggested
6401 - If not enough of our entry guards are available so we add a new
6402 one, we might use the new one even if it overlapped with the
6403 current circuit's exit relay (or its family). Anonymity bugfix
6404 pointed out by rovv.
6407 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6408 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6409 - When using the TransPort option on OpenBSD, and using the User
6410 option to change UID and drop privileges, make sure to open /dev/pf
6411 before dropping privileges. Fixes bug 782. Patch from Christopher
6412 Davis. Bugfix on 0.1.2.1-alpha.
6413 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6414 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6415 - Add a missing safe_str() call for a debug log message.
6416 - Use 64 bits instead of 32 bits for connection identifiers used with
6417 the controller protocol, to greatly reduce risk of identifier reuse.
6418 - Make the autoconf script accept the obsolete --with-ssl-dir
6419 option as an alias for the actually-working --with-openssl-dir
6420 option. Fix the help documentation to recommend --with-openssl-dir.
6421 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6424 - Rate-limit too-many-sockets messages: when they happen, they happen
6425 a lot. Resolves bug 748.
6426 - Resist DNS poisoning a little better by making sure that names in
6427 answer sections match.
6428 - Print the SOCKS5 error message string as well as the error code
6429 when a tor-resolve request fails. Patch from Jacob.
6432 Changes in version 0.2.1.4-alpha - 2008-08-04
6433 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
6436 - The address part of exit policies was not correctly written
6437 to router descriptors. This generated router descriptors that failed
6438 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
6440 - Tor triggered a false assert when extending a circuit to a relay
6441 but we already have a connection open to that relay. Noticed by
6442 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
6445 - Fix a hidden service logging bug: in some edge cases, the router
6446 descriptor of a previously picked introduction point becomes
6447 obsolete and we need to give up on it rather than continually
6448 complaining that it has become obsolete. Observed by xiando. Bugfix
6452 - Take out the TestVia config option, since it was a workaround for
6453 a bug that was fixed in Tor 0.1.1.21.
6456 Changes in version 0.2.1.3-alpha - 2008-08-03
6457 Tor 0.2.1.3-alpha implements most of the pieces to prevent
6458 infinite-length circuit attacks (see proposal 110); fixes a bug that
6459 might cause exit relays to corrupt streams they send back; allows
6460 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
6461 ExcludeExitNodes config options; and fixes a big pile of bugs.
6463 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
6464 - Send a bootstrap problem "warn" event on the first problem if the
6465 reason is NO_ROUTE (that is, our network is down).
6468 - Implement most of proposal 110: The first K cells to be sent
6469 along a circuit are marked as special "early" cells; only K "early"
6470 cells will be allowed. Once this code is universal, we can block
6471 certain kinds of DOS attack by requiring that EXTEND commands must
6472 be sent using an "early" cell.
6475 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6476 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6477 on the client side when connecting to a hidden service. Bugfix
6478 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6479 - Ensure that two circuits can never exist on the same connection
6480 with the same circuit ID, even if one is marked for close. This
6481 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
6484 - When relays do their initial bandwidth measurement, don't limit
6485 to just our entry guards for the test circuits. Otherwise we tend
6486 to have multiple test circuits going through a single entry guard,
6487 which makes our bandwidth test less accurate. Fixes part of bug 654;
6488 patch contributed by Josh Albrecht.
6489 - Add an ExcludeExitNodes option so users can list a set of nodes
6490 that should be be excluded from the exit node position, but
6491 allowed elsewhere. Implements proposal 151.
6492 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
6493 ExcludeNodes and ExcludeExitNodes lists.
6494 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
6495 be more efficient. Formerly it was quadratic in the number of
6496 servers; now it should be linear. Fixes bug 509.
6497 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
6498 and n_conn_id_digest fields into a separate structure that's
6499 only needed when the circuit has not yet attached to an n_conn.
6502 - Change the contrib/tor.logrotate script so it makes the new
6503 logs as "_tor:_tor" rather than the default, which is generally
6504 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
6505 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
6506 warnings (occasionally), but it can also cause the compiler to
6507 eliminate error-checking code. Suggested by Peter Gutmann.
6508 - When a hidden service is giving up on an introduction point candidate
6509 that was not included in the last published rendezvous descriptor,
6510 don't reschedule publication of the next descriptor. Fixes bug 763.
6512 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
6513 HiddenServiceExcludeNodes as obsolete: they never worked properly,
6514 and nobody claims to be using them. Fixes bug 754. Bugfix on
6515 0.1.0.1-rc. Patch from Christian Wilms.
6516 - Fix a small alignment and memory-wasting bug on buffer chunks.
6519 o Minor bugfixes (controller):
6520 - When closing an application-side connection because its circuit
6521 is getting torn down, generate the stream event correctly.
6522 Bugfix on 0.1.2.x. Anonymous patch.
6525 - Remove all backward-compatibility code to support relays running
6526 versions of Tor so old that they no longer work at all on the
6530 Changes in version 0.2.0.30 - 2008-07-15
6532 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
6533 warnings (occasionally), but it can also cause the compiler to
6534 eliminate error-checking code. Suggested by Peter Gutmann.
6537 Changes in version 0.2.0.29-rc - 2008-07-08
6538 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
6539 hidden-service performance bugs, and fixes a bunch of smaller bugs.
6542 - If you have more than one bridge but don't know their keys,
6543 you would only launch a request for the descriptor of the first one
6544 on your list. (Tor considered launching requests for the others, but
6545 found that it already had a connection on the way for $0000...0000
6546 so it didn't open another.) Bugfix on 0.2.0.x.
6547 - If you have more than one bridge but don't know their keys, and the
6548 connection to one of the bridges failed, you would cancel all
6549 pending bridge connections. (After all, they all have the same
6550 digest.) Bugfix on 0.2.0.x.
6551 - When a hidden service was trying to establish an introduction point,
6552 and Tor had built circuits preemptively for such purposes, we
6553 were ignoring all the preemptive circuits and launching a new one
6554 instead. Bugfix on 0.2.0.14-alpha.
6555 - When a hidden service was trying to establish an introduction point,
6556 and Tor *did* manage to reuse one of the preemptively built
6557 circuits, it didn't correctly remember which one it used,
6558 so it asked for another one soon after, until there were no
6559 more preemptive circuits, at which point it launched one from
6560 scratch. Bugfix on 0.0.9.x.
6561 - Make directory servers include the X-Your-Address-Is: http header in
6562 their responses even for begin_dir conns. Now clients who only
6563 ever use begin_dir connections still have a way to learn their IP
6564 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
6567 - Fix a macro/CPP interaction that was confusing some compilers:
6568 some GCCs don't like #if/#endif pairs inside macro arguments.
6570 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
6571 Fixes bug 704; fix from Steven Murdoch.
6572 - When opening /dev/null in finish_daemonize(), do not pass the
6573 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
6574 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
6575 - Correctly detect transparent proxy support on Linux hosts that
6576 require in.h to be included before netfilter_ipv4.h. Patch
6578 - Disallow session resumption attempts during the renegotiation
6579 stage of the v2 handshake protocol. Clients should never be trying
6580 session resumption at this point, but apparently some did, in
6581 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
6582 found by Geoff Goodell.
6585 Changes in version 0.2.1.2-alpha - 2008-06-20
6586 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
6587 make it easier to set up your own private Tor network; fixes several
6588 big bugs with using more than one bridge relay; fixes a big bug with
6589 offering hidden services quickly after Tor starts; and uses a better
6590 API for reporting potential bootstrapping problems to the controller.
6593 - New TestingTorNetwork config option to allow adjustment of
6594 previously constant values that, while reasonable, could slow
6595 bootstrapping. Implements proposal 135. Patch from Karsten.
6598 - If you have more than one bridge but don't know their digests,
6599 you would only learn a request for the descriptor of the first one
6600 on your list. (Tor considered launching requests for the others, but
6601 found that it already had a connection on the way for $0000...0000
6602 so it didn't open another.) Bugfix on 0.2.0.x.
6603 - If you have more than one bridge but don't know their digests,
6604 and the connection to one of the bridges failed, you would cancel
6605 all pending bridge connections. (After all, they all have the
6606 same digest.) Bugfix on 0.2.0.x.
6607 - When establishing a hidden service, introduction points that
6608 originate from cannibalized circuits are completely ignored and not
6609 included in rendezvous service descriptors. This might be another
6610 reason for delay in making a hidden service available. Bugfix
6611 from long ago (0.0.9.x?)
6614 - Allow OpenSSL to use dynamic locks if it wants.
6615 - When building a consensus, do not include routers that are down.
6616 This will cut down 30% to 40% on consensus size. Implements
6618 - In directory authorities' approved-routers files, allow
6619 fingerprints with or without space.
6620 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
6621 controller can query our current bootstrap state in case it attaches
6622 partway through and wants to catch up.
6623 - Send an initial "Starting" bootstrap status event, so we have a
6624 state to start out in.
6627 - Asking for a conditional consensus at .../consensus/<fingerprints>
6628 would crash a dirserver if it did not already have a
6629 consensus. Bugfix on 0.2.1.1-alpha.
6630 - Clean up some macro/CPP interactions: some GCC versions don't like
6631 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
6634 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
6635 - Directory authorities shouldn't complain about bootstrapping
6636 problems just because they do a lot of reachability testing and
6637 some of the connection attempts fail.
6638 - Start sending "count" and "recommendation" key/value pairs in
6639 bootstrap problem status events, so the controller can hear about
6640 problems even before Tor decides they're worth reporting for sure.
6641 - If you're using bridges, generate "bootstrap problem" warnings
6642 as soon as you run out of working bridges, rather than waiting
6643 for ten failures -- which will never happen if you have less than
6645 - If we close our OR connection because there's been a circuit
6646 pending on it for too long, we were telling our bootstrap status
6647 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
6650 Changes in version 0.2.1.1-alpha - 2008-06-13
6651 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
6652 were making the Tor process bloat especially on Linux; makes our TLS
6653 handshake blend in better; sends "bootstrap phase" status events to
6654 the controller, so it can keep the user informed of progress (and
6655 problems) fetching directory information and establishing circuits;
6656 and adds a variety of smaller features.
6659 - More work on making our TLS handshake blend in: modify the list
6660 of ciphers advertised by OpenSSL in client mode to even more
6661 closely resemble a common web browser. We cheat a little so that
6662 we can advertise ciphers that the locally installed OpenSSL doesn't
6664 - Start sending "bootstrap phase" status events to the controller,
6665 so it can keep the user informed of progress fetching directory
6666 information and establishing circuits. Also inform the controller
6667 if we think we're stuck at a particular bootstrap phase. Implements
6669 - Resume using OpenSSL's RAND_poll() for better (and more portable)
6670 cross-platform entropy collection again. We used to use it, then
6671 stopped using it because of a bug that could crash systems that
6672 called RAND_poll when they had a lot of fds open. It looks like the
6673 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
6674 at startup, and to call RAND_poll() when we reseed later only if
6675 we have a non-buggy OpenSSL version.
6678 - When we choose to abandon a new entry guard because we think our
6679 older ones might be better, close any circuits pending on that
6680 new entry guard connection. This fix should make us recover much
6681 faster when our network is down and then comes back. Bugfix on
6682 0.1.2.8-beta; found by lodger.
6684 o Memory fixes and improvements:
6685 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
6686 to avoid unused RAM in buffer chunks and memory pools.
6687 - Speed up parsing and cut down on memory fragmentation by using
6688 stack-style allocations for parsing directory objects. Previously,
6689 this accounted for over 40% of allocations from within Tor's code
6690 on a typical directory cache.
6691 - Use a Bloom filter rather than a digest-based set to track which
6692 descriptors we need to keep around when we're cleaning out old
6693 router descriptors. This speeds up the computation significantly,
6694 and may reduce fragmentation.
6695 - Reduce the default smartlist size from 32 to 16; it turns out that
6696 most smartlists hold around 8-12 elements tops.
6697 - Make dumpstats() log the fullness and size of openssl-internal
6699 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
6700 patch to their OpenSSL, turn it on to save memory on servers. This
6701 patch will (with any luck) get included in a mainline distribution
6703 - Never use OpenSSL compression: it wastes RAM and CPU trying to
6704 compress cells, which are basically all encrypted, compressed,
6708 - Stop reloading the router list from disk for no reason when we
6709 run out of reachable directory mirrors. Once upon a time reloading
6710 it would set the 'is_running' flag back to 1 for them. It hasn't
6711 done that for a long time.
6712 - In very rare situations new hidden service descriptors were
6713 published earlier than 30 seconds after the last change to the
6714 service. (We currently think that a hidden service descriptor
6715 that's been stable for 30 seconds is worth publishing.)
6718 - Allow separate log levels to be configured for different logging
6719 domains. For example, this allows one to log all notices, warnings,
6720 or errors, plus all memory management messages of level debug or
6721 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
6722 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
6723 and stop using a warning that had become unfixably verbose under
6725 - New --hush command-line option similar to --quiet. While --quiet
6726 disables all logging to the console on startup, --hush limits the
6727 output to messages of warning and error severity.
6728 - Servers support a new URL scheme for consensus downloads that
6729 allows the client to specify which authorities are trusted.
6730 The server then only sends the consensus if the client will trust
6731 it. Otherwise a 404 error is sent back. Clients use this
6732 new scheme when the server supports it (meaning it's running
6733 0.2.1.1-alpha or later). Implements proposal 134.
6734 - New configure/torrc options (--enable-geoip-stats,
6735 DirRecordUsageByCountry) to record how many IPs we've served
6736 directory info to in each country code, how many status documents
6737 total we've sent to each country code, and what share of the total
6738 directory requests we should expect to see.
6739 - Use the TLS1 hostname extension to more closely resemble browser
6741 - Lots of new unit tests.
6742 - Add a macro to implement the common pattern of iterating through
6743 two parallel lists in lockstep.
6746 Changes in version 0.2.0.28-rc - 2008-06-13
6747 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
6748 performance bug, and fixes a bunch of smaller bugs.
6751 - Fix a bug where, when we were choosing the 'end stream reason' to
6752 put in our relay end cell that we send to the exit relay, Tor
6753 clients on Windows were sometimes sending the wrong 'reason'. The
6754 anonymity problem is that exit relays may be able to guess whether
6755 the client is running Windows, thus helping partition the anonymity
6756 set. Down the road we should stop sending reasons to exit relays,
6757 or otherwise prevent future versions of this bug.
6760 - While setting up a hidden service, some valid introduction circuits
6761 were overlooked and abandoned. This might be the reason for
6762 the long delay in making a hidden service available. Bugfix on
6766 - Update to the "June 9 2008" ip-to-country file.
6767 - Run 'make test' as part of 'make dist', so we stop releasing so
6768 many development snapshots that fail their unit tests.
6771 - When we're checking if we have enough dir info for each relay
6772 to begin establishing circuits, make sure that we actually have
6773 the descriptor listed in the consensus, not just any descriptor.
6775 - Bridge relays no longer print "xx=0" in their extrainfo document
6776 for every single country code in the geoip db. Bugfix on
6778 - Only warn when we fail to load the geoip file if we were planning to
6779 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
6780 - If we change our MaxAdvertisedBandwidth and then reload torrc,
6781 Tor won't realize it should publish a new relay descriptor. Fixes
6782 bug 688, reported by mfr. Bugfix on 0.1.2.x.
6783 - When we haven't had any application requests lately, don't bother
6784 logging that we have expired a bunch of descriptors. Bugfix
6786 - Make relay cells written on a connection count as non-padding when
6787 tracking how long a connection has been in use. Bugfix on
6788 0.2.0.1-alpha. Spotted by lodger.
6789 - Fix unit tests in 0.2.0.27-rc.
6790 - Fix compile on Windows.
6793 Changes in version 0.2.0.27-rc - 2008-06-03
6794 Tor 0.2.0.27-rc adds a few features we left out of the earlier
6795 release candidates. In particular, we now include an IP-to-country
6796 GeoIP database, so controllers can easily look up what country a
6797 given relay is in, and so bridge relays can give us some sanitized
6798 summaries about which countries are making use of bridges. (See proposal
6799 126-geoip-fetching.txt for details.)
6802 - Include an IP-to-country GeoIP file in the tarball, so bridge
6803 relays can report sanitized summaries of the usage they're seeing.
6806 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
6807 Robert Hogan. Fixes the first part of bug 681.
6808 - Make bridge authorities never serve extrainfo docs.
6809 - Add support to detect Libevent versions in the 1.4.x series
6811 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
6812 - Include a new contrib/tor-exit-notice.html file that exit relay
6813 operators can put on their website to help reduce abuse queries.
6816 - When tunneling an encrypted directory connection, and its first
6817 circuit fails, do not leave it unattached and ask the controller
6818 to deal. Fixes the second part of bug 681.
6819 - Make bridge authorities correctly expire old extrainfo documents
6823 Changes in version 0.2.0.26-rc - 2008-05-13
6824 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
6825 in Debian's OpenSSL packages. All users running any 0.2.0.x version
6826 should upgrade, whether they're running Debian or not.
6828 o Major security fixes:
6829 - Use new V3 directory authority keys on the tor26, gabelmoo, and
6830 moria1 V3 directory authorities. The old keys were generated with
6831 a vulnerable version of Debian's OpenSSL package, and must be
6832 considered compromised. Other authorities' keys were not generated
6833 with an affected version of OpenSSL.
6836 - List authority signatures as "unrecognized" based on DirServer
6837 lines, not on cert cache. Bugfix on 0.2.0.x.
6840 - Add a new V3AuthUseLegacyKey option to make it easier for
6841 authorities to change their identity keys if they have to.
6844 Changes in version 0.2.0.25-rc - 2008-04-23
6845 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
6848 - Remember to initialize threading before initializing logging.
6849 Otherwise, many BSD-family implementations will crash hard on
6850 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
6853 - Authorities correctly free policies on bad servers on
6854 exit. Fixes bug 672. Bugfix on 0.2.0.x.
6857 Changes in version 0.2.0.24-rc - 2008-04-22
6858 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
6859 v3 directory authority, makes relays with dynamic IP addresses and no
6860 DirPort notice more quickly when their IP address changes, fixes a few
6861 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
6863 o New directory authorities:
6864 - Take lefkada out of the list of v3 directory authorities, since
6865 it has been down for months.
6866 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
6870 - Detect address changes more quickly on non-directory mirror
6871 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
6873 o Minor features (security):
6874 - Reject requests for reverse-dns lookup of names that are in
6875 a private address space. Patch from lodger.
6876 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
6879 o Minor bugfixes (crashes):
6880 - Avoid a rare assert that can trigger when Tor doesn't have much
6881 directory information yet and it tries to fetch a v2 hidden
6882 service descriptor. Fixes bug 651, reported by nwf.
6883 - Initialize log mutex before initializing dmalloc. Otherwise,
6884 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
6885 - Use recursive pthread mutexes in order to avoid deadlock when
6886 logging debug-level messages to a controller. Bug spotted by nwf,
6887 bugfix on 0.2.0.16-alpha.
6889 o Minor bugfixes (resource management):
6890 - Keep address policies from leaking memory: start their refcount
6891 at 1, not 2. Bugfix on 0.2.0.16-alpha.
6892 - Free authority certificates on exit, so they don't look like memory
6893 leaks. Bugfix on 0.2.0.19-alpha.
6894 - Free static hashtables for policy maps and for TLS connections on
6895 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
6896 - Avoid allocating extra space when computing consensuses on 64-bit
6897 platforms. Bug spotted by aakova.
6899 o Minor bugfixes (misc):
6900 - Do not read the configuration file when we've only been told to
6901 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
6902 based on patch from Sebastian Hahn.
6903 - Exit relays that are used as a client can now reach themselves
6904 using the .exit notation, rather than just launching an infinite
6905 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
6906 - When attempting to open a logfile fails, tell us why.
6907 - Fix a dumb bug that was preventing us from knowing that we should
6908 preemptively build circuits to handle expected directory requests.
6909 Fixes bug 660. Bugfix on 0.1.2.x.
6910 - Warn less verbosely about clock skew from netinfo cells from
6911 untrusted sources. Fixes bug 663.
6912 - Make controller stream events for DNS requests more consistent,
6913 by adding "new stream" events for DNS requests, and removing
6914 spurious "stream closed" events" for cached reverse resolves.
6915 Patch from mwenge. Fixes bug 646.
6916 - Correctly notify one-hop connections when a circuit build has
6917 failed. Possible fix for bug 669. Found by lodger.
6920 Changes in version 0.2.0.23-rc - 2008-03-24
6921 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
6922 makes bootstrapping faster if the first directory mirror you contact
6923 is down. The bundles also include the new Vidalia 0.1.2 release.
6926 - When a tunneled directory request is made to a directory server
6927 that's down, notice after 30 seconds rather than 120 seconds. Also,
6928 fail any begindir streams that are pending on it, so they can
6929 retry elsewhere. This was causing multi-minute delays on bootstrap.
6932 Changes in version 0.2.0.22-rc - 2008-03-18
6933 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
6934 enables encrypted directory connections by default for non-relays, fixes
6935 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
6936 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
6939 - Enable encrypted directory connections by default for non-relays,
6940 so censor tools that block Tor directory connections based on their
6941 plaintext patterns will no longer work. This means Tor works in
6942 certain censored countries by default again.
6945 - Make sure servers always request certificates from clients during
6946 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
6947 - Do not enter a CPU-eating loop when a connection is closed in
6948 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
6949 diagnosed by lodger; bugfix on 0.2.0.20-rc.
6950 - Fix assertion failure that could occur when a blocked circuit
6951 became unblocked, and it had pending client DNS requests. Bugfix
6952 on 0.2.0.1-alpha. Fixes bug 632.
6954 o Minor bugfixes (on 0.1.2.x):
6955 - Generate "STATUS_SERVER" events rather than misspelled
6956 "STATUS_SEVER" events. Caught by mwenge.
6957 - When counting the number of bytes written on a TLS connection,
6958 look at the BIO actually used for writing to the network, not
6959 at the BIO used (sometimes) to buffer data for the network.
6960 Looking at different BIOs could result in write counts on the
6961 order of ULONG_MAX. Fixes bug 614.
6962 - On Windows, correctly detect errors when listing the contents of
6963 a directory. Fix from lodger.
6965 o Minor bugfixes (on 0.2.0.x):
6966 - Downgrade "sslv3 alert handshake failure" message to INFO.
6967 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
6968 left BandwidthRate and BandwidthBurst at the default, we would be
6969 silently limited by those defaults. Now raise them to match the
6970 RelayBandwidth* values.
6971 - Fix the SVK version detection logic to work correctly on a branch.
6972 - Make --enable-openbsd-malloc work correctly on Linux with alpha
6973 CPUs. Fixes bug 625.
6974 - Logging functions now check that the passed severity is sane.
6975 - Use proper log levels in the testsuite call of
6976 get_interface_address6().
6977 - When using a nonstandard malloc, do not use the platform values for
6978 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
6979 - Make the openbsd malloc code use 8k pages on alpha CPUs and
6981 - Detect mismatched page sizes when using --enable-openbsd-malloc.
6982 - Avoid double-marked-for-close warning when certain kinds of invalid
6983 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
6984 for bug 617. Bugfix on 0.2.0.1-alpha.
6985 - Make sure that the "NULL-means-reject *:*" convention is followed by
6986 all the policy manipulation functions, avoiding some possible crash
6987 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
6988 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
6989 actually works, and doesn't warn about every single reverse lookup.
6990 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
6993 - Only log guard node status when guard node status has changed.
6994 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
6995 make "INFO" 75% less verbose.
6998 Changes in version 0.2.0.21-rc - 2008-03-02
6999 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
7000 makes Tor work well with Vidalia again, fixes a rare assert bug,
7001 and fixes a pair of more minor bugs. The bundles also include Vidalia
7002 0.1.0 and Torbutton 1.1.16.
7005 - The control port should declare that it requires password auth
7006 when HashedControlSessionPassword is set too. Patch from Matt Edman;
7007 bugfix on 0.2.0.20-rc. Fixes bug 615.
7008 - Downgrade assert in connection_buckets_decrement() to a log message.
7009 This may help us solve bug 614, and in any case will make its
7010 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
7011 - We were sometimes miscounting the number of bytes read from the
7012 network, causing our rate limiting to not be followed exactly.
7013 Bugfix on 0.2.0.16-alpha. Reported by lodger.
7016 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
7017 OpenSSL versions should have been working fine. Diagnosis and patch
7018 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
7019 Bugfix on 0.2.0.20-rc.
7022 Changes in version 0.2.0.20-rc - 2008-02-24
7023 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
7024 makes more progress towards normalizing Tor's TLS handshake, makes
7025 hidden services work better again, helps relays bootstrap if they don't
7026 know their IP address, adds optional support for linking in openbsd's
7027 allocator or tcmalloc, allows really fast relays to scale past 15000
7028 sockets, and fixes a bunch of minor bugs reported by Veracode.
7031 - Enable the revised TLS handshake based on the one designed by
7032 Steven Murdoch in proposal 124, as revised in proposal 130. It
7033 includes version negotiation for OR connections as described in
7034 proposal 105. The new handshake is meant to be harder for censors
7035 to fingerprint, and it adds the ability to detect certain kinds of
7036 man-in-the-middle traffic analysis attacks. The version negotiation
7037 feature will allow us to improve Tor's link protocol more safely
7039 - Choose which bridge to use proportional to its advertised bandwidth,
7040 rather than uniformly at random. This should speed up Tor for
7041 bridge users. Also do this for people who set StrictEntryNodes.
7042 - When a TrackHostExits-chosen exit fails too many times in a row,
7043 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
7046 - Resolved problems with (re-)fetching hidden service descriptors.
7047 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
7049 - If we only ever used Tor for hidden service lookups or posts, we
7050 would stop building circuits and start refusing connections after
7051 24 hours, since we falsely believed that Tor was dormant. Reported
7052 by nwf; bugfix on 0.1.2.x.
7053 - Servers that don't know their own IP address should go to the
7054 authorities for their first directory fetch, even if their DirPort
7055 is off or if they don't know they're reachable yet. This will help
7056 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
7057 - When counting the number of open sockets, count not only the number
7058 of sockets we have received from the socket() call, but also
7059 the number we've gotten from accept() and socketpair(). This bug
7060 made us fail to count all sockets that we were using for incoming
7061 connections. Bugfix on 0.2.0.x.
7062 - Fix code used to find strings within buffers, when those strings
7063 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
7064 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
7065 - Add a new __HashedControlSessionPassword option for controllers
7066 to use for one-off session password hashes that shouldn't get
7067 saved to disk by SAVECONF --- Vidalia users were accumulating a
7068 pile of HashedControlPassword lines in their torrc files, one for
7069 each time they had restarted Tor and then clicked Save. Make Tor
7070 automatically convert "HashedControlPassword" to this new option but
7071 only when it's given on the command line. Partial fix for bug 586.
7073 o Minor features (performance):
7074 - Tune parameters for cell pool allocation to minimize amount of
7076 - Add OpenBSD malloc code from phk as an optional malloc
7077 replacement on Linux: some glibc libraries do very poorly
7078 with Tor's memory allocation patterns. Pass
7079 --enable-openbsd-malloc to get the replacement malloc code.
7080 - Add a --with-tcmalloc option to the configure script to link
7081 against tcmalloc (if present). Does not yet search for
7082 non-system include paths.
7083 - Stop imposing an arbitrary maximum on the number of file descriptors
7084 used for busy servers. Bug reported by Olaf Selke; patch from
7087 o Minor features (other):
7088 - When SafeLogging is disabled, log addresses along with all TLS
7090 - When building with --enable-gcc-warnings, check for whether Apple's
7091 warning "-Wshorten-64-to-32" is available.
7092 - Add a --passphrase-fd argument to the tor-gencert command for
7095 o Minor bugfixes (memory leaks and code problems):
7096 - We were leaking a file descriptor if Tor started with a zero-length
7097 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
7098 - Detect size overflow in zlib code. Reported by Justin Ferguson and
7100 - We were comparing the raw BridgePassword entry with a base64'ed
7101 version of it, when handling a "/tor/networkstatus-bridges"
7102 directory request. Now compare correctly. Noticed by Veracode.
7103 - Recover from bad tracked-since value in MTBF-history file.
7105 - Alter the code that tries to recover from unhandled write
7106 errors, to not try to flush onto a socket that's given us
7107 unhandled errors. Bugfix on 0.1.2.x.
7108 - Make Unix controlsockets work correctly on OpenBSD. Patch from
7109 tup. Bugfix on 0.2.0.3-alpha.
7111 o Minor bugfixes (other):
7112 - If we have an extra-info document for our server, always make
7113 it available on the control port, even if we haven't gotten
7114 a copy of it from an authority yet. Patch from mwenge.
7115 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
7116 - Directory mirrors no longer include a guess at the client's IP
7117 address if the connection appears to be coming from the same /24
7118 network; it was producing too many wrong guesses.
7119 - Make the new hidden service code respect the SafeLogging setting.
7120 Bugfix on 0.2.0.x. Patch from Karsten.
7121 - When starting as an authority, do not overwrite all certificates
7122 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
7123 - If we're trying to flush the last bytes on a connection (for
7124 example, when answering a directory request), reset the
7125 time-to-give-up timeout every time we manage to write something
7126 on the socket. Bugfix on 0.1.2.x.
7127 - Change the behavior of "getinfo status/good-server-descriptor"
7128 so it doesn't return failure when any authority disappears.
7129 - Even though the man page said that "TrackHostExits ." should
7130 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
7131 - Report TLS "zero return" case as a "clean close" and "IO error"
7132 as a "close". Stop calling closes "unexpected closes": existing
7133 Tors don't use SSL_close(), so having a connection close without
7134 the TLS shutdown handshake is hardly unexpected.
7135 - Send NAMESERVER_STATUS messages for a single failed nameserver
7138 o Code simplifications and refactoring:
7139 - Remove the tor_strpartition function: its logic was confused,
7140 and it was only used for one thing that could be implemented far
7144 Changes in version 0.2.0.19-alpha - 2008-02-09
7145 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
7146 handshake, makes path selection for relays more secure and IP address
7147 guessing more robust, and generally fixes a lot of bugs in preparation
7148 for calling the 0.2.0 branch stable.
7151 - Do not include recognizeable strings in the commonname part of
7152 Tor's x509 certificates.
7155 - If we're a relay, avoid picking ourselves as an introduction point,
7156 a rendezvous point, or as the final hop for internal circuits. Bug
7157 reported by taranis and lodger. Bugfix on 0.1.2.x.
7158 - Patch from "Andrew S. Lists" to catch when we contact a directory
7159 mirror at IP address X and he says we look like we're coming from
7160 IP address X. Bugfix on 0.1.2.x.
7162 o Minor features (security):
7163 - Be more paranoid about overwriting sensitive memory on free(),
7164 as a defensive programming tactic to ensure forward secrecy.
7166 o Minor features (directory authority):
7167 - Actually validate the options passed to AuthDirReject,
7168 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
7169 - Reject router descriptors with out-of-range bandwidthcapacity or
7170 bandwidthburst values.
7172 o Minor features (controller):
7173 - Reject controller commands over 1MB in length. This keeps rogue
7174 processes from running us out of memory.
7176 o Minor features (misc):
7177 - Give more descriptive well-formedness errors for out-of-range
7178 hidden service descriptor/protocol versions.
7179 - Make memory debugging information describe more about history
7180 of cell allocation, so we can help reduce our memory use.
7182 o Deprecated features (controller):
7183 - The status/version/num-versioning and status/version/num-concurring
7184 GETINFO options are no longer useful in the v3 directory protocol:
7185 treat them as deprecated, and warn when they're used.
7188 - When our consensus networkstatus has been expired for a while, stop
7189 being willing to build circuits using it. Fixes bug 401. Bugfix
7191 - Directory caches now fetch certificates from all authorities
7192 listed in a networkstatus consensus, even when they do not
7193 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
7194 - When connecting to a bridge without specifying its key, insert
7195 the connection into the identity-to-connection map as soon as
7196 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
7197 - Detect versions of OS X where malloc_good_size() is present in the
7198 library but never actually declared. Resolves bug 587. Bugfix
7200 - Stop incorrectly truncating zlib responses to directory authority
7201 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
7202 - Stop recommending that every server operator send mail to tor-ops.
7203 Resolves bug 597. Bugfix on 0.1.2.x.
7204 - Don't trigger an assert if we start a directory authority with a
7205 private IP address (like 127.0.0.1).
7206 - Avoid possible failures when generating a directory with routers
7207 with over-long versions strings, or too many flags set. Bugfix
7209 - If an attempt to launch a DNS resolve request over the control
7210 port fails because we have overrun the limit on the number of
7211 connections, tell the controller that the request has failed.
7212 - Avoid using too little bandwidth when our clock skips a few
7213 seconds. Bugfix on 0.1.2.x.
7214 - Fix shell error when warning about missing packages in configure
7215 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
7216 - Do not become confused when receiving a spurious VERSIONS-like
7217 cell from a confused v1 client. Bugfix on 0.2.0.x.
7218 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
7219 introduction points for a hidden service have failed. Patch from
7220 Karsten Loesing. Bugfix on 0.2.0.x.
7222 o Code simplifications and refactoring:
7223 - Remove some needless generality from cpuworker code, for improved
7225 - Stop overloading the circuit_t.onionskin field for both "onionskin
7226 from a CREATE cell that we are waiting for a cpuworker to be
7227 assigned" and "onionskin from an EXTEND cell that we are going to
7228 send to an OR as soon as we are connected". Might help with bug 600.
7229 - Add an in-place version of aes_crypt() so that we can avoid doing a
7230 needless memcpy() call on each cell payload.
7233 Changes in version 0.2.0.18-alpha - 2008-01-25
7234 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
7235 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
7236 that can warn or reject connections to ports generally associated with
7237 vulnerable-plaintext protocols.
7239 o New directory authorities:
7240 - Set up dannenberg (run by CCC) as the sixth v3 directory
7244 - Fix a major memory leak when attempting to use the v2 TLS
7245 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
7246 - We accidentally enabled the under-development v2 TLS handshake
7247 code, which was causing log entries like "TLS error while
7248 renegotiating handshake". Disable it again. Resolves bug 590.
7249 - We were computing the wrong Content-Length: header for directory
7250 responses that need to be compressed on the fly, causing clients
7251 asking for those items to always fail. Bugfix on 0.2.0.x; partially
7255 - Avoid going directly to the directory authorities even if you're a
7256 relay, if you haven't found yourself reachable yet or if you've
7257 decided not to advertise your dirport yet. Addresses bug 556.
7258 - If we've gone 12 hours since our last bandwidth check, and we
7259 estimate we have less than 50KB bandwidth capacity but we could
7260 handle more, do another bandwidth test.
7261 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
7262 Tor can warn and/or refuse connections to ports commonly used with
7263 vulnerable-plaintext protocols. Currently we warn on ports 23,
7264 109, 110, and 143, but we don't reject any.
7267 - When we setconf ClientOnly to 1, close any current OR and Dir
7268 listeners. Reported by mwenge.
7269 - When we get a consensus that's been signed by more people than
7270 we expect, don't log about it; it's not a big deal. Reported
7274 - Don't answer "/tor/networkstatus-bridges" directory requests if
7275 the request isn't encrypted.
7276 - Make "ClientOnly 1" config option disable directory ports too.
7277 - Patches from Karsten Loesing to make v2 hidden services more
7278 robust: work even when there aren't enough HSDir relays available;
7279 retry when a v2 rend desc fetch fails; but don't retry if we
7280 already have a usable v0 rend desc.
7283 Changes in version 0.2.0.17-alpha - 2008-01-17
7284 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
7287 - Make the tor-gencert man page get included correctly in the tarball.
7290 Changes in version 0.2.0.16-alpha - 2008-01-17
7291 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
7292 Loesing, and generally cleans up a lot of features and minor bugs.
7294 o New directory authorities:
7295 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
7298 o Major performance improvements:
7299 - Switch our old ring buffer implementation for one more like that
7300 used by free Unix kernels. The wasted space in a buffer with 1mb
7301 of data will now be more like 8k than 1mb. The new implementation
7302 also avoids realloc();realloc(); patterns that can contribute to
7303 memory fragmentation.
7306 - Configuration files now accept C-style strings as values. This
7307 helps encode characters not allowed in the current configuration
7308 file format, such as newline or #. Addresses bug 557.
7309 - Although we fixed bug 539 (where servers would send HTTP status 503
7310 responses _and_ send a body too), there are still servers out
7311 there that haven't upgraded. Therefore, make clients parse such
7312 bodies when they receive them.
7313 - When we're not serving v2 directory information, there is no reason
7314 to actually keep any around. Remove the obsolete files and directory
7315 on startup if they are very old and we aren't going to serve them.
7317 o Minor performance improvements:
7318 - Reference-count and share copies of address policy entries; only 5%
7319 of them were actually distinct.
7320 - Never walk through the list of logs if we know that no log is
7321 interested in a given message.
7324 - When an authority has not signed a consensus, do not try to
7325 download a nonexistent "certificate with key 00000000". Bugfix
7326 on 0.2.0.x. Fixes bug 569.
7327 - Fix a rare assert error when we're closing one of our threads:
7328 use a mutex to protect the list of logs, so we never write to the
7329 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
7330 bug 575, which is kind of the revenge of bug 222.
7331 - Patch from Karsten Loesing to complain less at both the client
7332 and the relay when a relay used to have the HSDir flag but doesn't
7333 anymore, and we try to upload a hidden service descriptor.
7334 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
7336 - Do not try to download missing certificates until we have tried
7337 to check our fallback consensus. Fixes bug 583.
7338 - Make bridges round reported GeoIP stats info up to the nearest
7339 estimate, not down. Now we can distinguish between "0 people from
7340 this country" and "1 person from this country".
7341 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
7342 - Avoid possible segfault if key generation fails in
7343 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
7344 - Avoid segfault in the case where a badly behaved v2 versioning
7345 directory sends a signed networkstatus with missing client-versions.
7347 - Avoid segfaults on certain complex invocations of
7348 router_get_by_hexdigest(). Bugfix on 0.1.2.
7349 - Correct bad index on array access in parse_http_time(). Bugfix
7351 - Fix possible bug in vote generation when server versions are present
7352 but client versions are not.
7353 - Fix rare bug on REDIRECTSTREAM control command when called with no
7354 port set: it could erroneously report an error when none had
7356 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
7357 compressing large objects and find ourselves with more than 4k
7358 left over. Bugfix on 0.2.0.
7359 - Fix a small memory leak when setting up a hidden service.
7360 - Fix a few memory leaks that could in theory happen under bizarre
7362 - Fix an assert if we post a general-purpose descriptor via the
7363 control port but that descriptor isn't mentioned in our current
7364 network consensus. Bug reported by Jon McLachlan; bugfix on
7367 o Minor features (controller):
7368 - Get NS events working again. Patch from tup.
7369 - The GETCONF command now escapes and quotes configuration values
7370 that don't otherwise fit into the torrc file.
7371 - The SETCONF command now handles quoted values correctly.
7373 o Minor features (directory authorities):
7374 - New configuration options to override default maximum number of
7375 servers allowed on a single IP address. This is important for
7376 running a test network on a single host.
7377 - Actually implement the -s option to tor-gencert.
7378 - Add a manual page for tor-gencert.
7380 o Minor features (bridges):
7381 - Bridge authorities no longer serve bridge descriptors over
7382 unencrypted connections.
7384 o Minor features (other):
7385 - Add hidden services and DNSPorts to the list of things that make
7386 Tor accept that it has running ports. Change starting Tor with no
7387 ports from a fatal error to a warning; we might change it back if
7388 this turns out to confuse anybody. Fixes bug 579.
7391 Changes in version 0.1.2.19 - 2008-01-17
7392 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
7393 exit policy a little bit more conservative so it's safer to run an
7394 exit relay on a home system, and fixes a variety of smaller issues.
7397 - Exit policies now reject connections that are addressed to a
7398 relay's public (external) IP address too, unless
7399 ExitPolicyRejectPrivate is turned off. We do this because too
7400 many relays are running nearby to services that trust them based
7404 - When the clock jumps forward a lot, do not allow the bandwidth
7405 buckets to become negative. Fixes bug 544.
7406 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7407 on every successful resolve. Reported by Mike Perry.
7408 - Purge old entries from the "rephist" database and the hidden
7409 service descriptor database even when DirPort is zero.
7410 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7411 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7412 crashing or mis-answering these requests.
7413 - When we decide to send a 503 response to a request for servers, do
7414 not then also send the server descriptors: this defeats the whole
7415 purpose. Fixes bug 539.
7418 - Changing the ExitPolicyRejectPrivate setting should cause us to
7419 rebuild our server descriptor.
7420 - Fix handling of hex nicknames when answering controller requests for
7421 networkstatus by name, or when deciding whether to warn about
7422 unknown routers in a config option. (Patch from mwenge.)
7423 - Fix a couple of hard-to-trigger autoconf problems that could result
7424 in really weird results on platforms whose sys/types.h files define
7425 nonstandard integer types.
7426 - Don't try to create the datadir when running --verify-config or
7427 --hash-password. Resolves bug 540.
7428 - If we were having problems getting a particular descriptor from the
7429 directory caches, and then we learned about a new descriptor for
7430 that router, we weren't resetting our failure count. Reported
7432 - Although we fixed bug 539 (where servers would send HTTP status 503
7433 responses _and_ send a body too), there are still servers out there
7434 that haven't upgraded. Therefore, make clients parse such bodies
7435 when they receive them.
7436 - Run correctly on systems where rlim_t is larger than unsigned long.
7437 This includes some 64-bit systems.
7438 - Run correctly on platforms (like some versions of OS X 10.5) where
7439 the real limit for number of open files is OPEN_FILES, not rlim_max
7440 from getrlimit(RLIMIT_NOFILES).
7441 - Avoid a spurious free on base64 failure.
7442 - Avoid segfaults on certain complex invocations of
7443 router_get_by_hexdigest().
7444 - Fix rare bug on REDIRECTSTREAM control command when called with no
7445 port set: it could erroneously report an error when none had
7449 Changes in version 0.2.0.15-alpha - 2007-12-25
7450 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
7451 features added in 0.2.0.13-alpha.
7454 - Fix several remotely triggerable asserts based on DirPort requests
7455 for a v2 or v3 networkstatus object before we were prepared. This
7456 was particularly bad for 0.2.0.13 and later bridge relays, who
7457 would never have a v2 networkstatus and would thus always crash
7458 when used. Bugfixes on 0.2.0.x.
7459 - Estimate the v3 networkstatus size more accurately, rather than
7460 estimating it at zero bytes and giving it artificially high priority
7461 compared to other directory requests. Bugfix on 0.2.0.x.
7464 - Fix configure.in logic for cross-compilation.
7465 - When we load a bridge descriptor from the cache, and it was
7466 previously unreachable, mark it as retriable so we won't just
7467 ignore it. Also, try fetching a new copy immediately. Bugfixes
7469 - The bridge GeoIP stats were counting other relays, for example
7470 self-reachability and authority-reachability tests.
7473 - Support compilation to target iPhone; patch from cjacker huang.
7474 To build for iPhone, pass the --enable-iphone option to configure.
7477 Changes in version 0.2.0.14-alpha - 2007-12-23
7479 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
7480 without a datadirectory from a previous Tor install. Reported
7482 - Fix a crash when we fetch a descriptor that turns out to be
7483 unexpected (it used to be in our networkstatus when we started
7484 fetching it, but it isn't in our current networkstatus), and we
7485 aren't using bridges. Bugfix on 0.2.0.x.
7486 - Fix a crash when accessing hidden services: it would work the first
7487 time you use a given introduction point for your service, but
7488 on subsequent requests we'd be using garbage memory. Fixed by
7489 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
7490 - Fix a crash when we load a bridge descriptor from disk but we don't
7491 currently have a Bridge line for it in our torrc. Bugfix on
7495 - If bridge authorities set BridgePassword, they will serve a
7496 snapshot of known bridge routerstatuses from their DirPort to
7497 anybody who knows that password. Unset by default.
7500 - Make the unit tests build again.
7501 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
7502 - Make PublishServerDescriptor default to 1, so the default doesn't
7503 have to change as we invent new directory protocol versions.
7504 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
7505 be included unless sys/time.h is already included. Fixes
7506 bug 553. Bugfix on 0.2.0.x.
7507 - If we receive a general-purpose descriptor and then receive an
7508 identical bridge-purpose descriptor soon after, don't discard
7509 the next one as a duplicate.
7512 - If BridgeRelay is set to 1, then the default for
7513 PublishServerDescriptor is now "bridge" rather than "v2,v3".
7514 - If the user sets RelayBandwidthRate but doesn't set
7515 RelayBandwidthBurst, then make them equal rather than erroring out.
7518 Changes in version 0.2.0.13-alpha - 2007-12-21
7519 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
7520 Goodell, fixes many more bugs, and adds a lot of infrastructure for
7523 o New directory authorities:
7524 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
7528 - Only update guard status (usable / not usable) once we have
7529 enough directory information. This was causing us to always pick
7530 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
7531 causing us to discard all our guards on startup if we hadn't been
7532 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
7533 - Purge old entries from the "rephist" database and the hidden
7534 service descriptor databases even when DirPort is zero. Bugfix
7536 - We were ignoring our RelayBandwidthRate for the first 30 seconds
7537 after opening a circuit -- even a relayed circuit. Bugfix on
7539 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7540 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7541 crashing or mis-answering these types of requests.
7542 - Relays were publishing their server descriptor to v1 and v2
7543 directory authorities, but they didn't try publishing to v3-only
7544 authorities. Fix this; and also stop publishing to v1 authorities.
7546 - When we were reading router descriptors from cache, we were ignoring
7547 the annotations -- so for example we were reading in bridge-purpose
7548 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
7549 - When we decided to send a 503 response to a request for servers, we
7550 were then also sending the server descriptors: this defeats the
7551 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
7554 - Bridge relays now behave like clients with respect to time
7555 intervals for downloading new consensus documents -- otherwise they
7556 stand out. Bridge users now wait until the end of the interval,
7557 so their bridge relay will be sure to have a new consensus document.
7558 - Three new config options (AlternateDirAuthority,
7559 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
7560 user selectively replace the default directory authorities by type,
7561 rather than the all-or-nothing replacement that DirServer offers.
7562 - Tor can now be configured to read a GeoIP file from disk in one
7563 of two formats. This can be used by controllers to map IP addresses
7564 to countries. Eventually, it may support exit-by-country.
7565 - When possible, bridge relays remember which countries users
7566 are coming from, and report aggregate information in their
7567 extra-info documents, so that the bridge authorities can learn
7568 where Tor is blocked.
7569 - Bridge directory authorities now do reachability testing on the
7570 bridges they know. They provide router status summaries to the
7571 controller via "getinfo ns/purpose/bridge", and also dump summaries
7572 to a file periodically.
7573 - Stop fetching directory info so aggressively if your DirPort is
7574 on but your ORPort is off; stop fetching v2 dir info entirely.
7575 You can override these choices with the new FetchDirInfoEarly
7579 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
7580 consensus documents when there are too many relays at a single
7581 IP address. Now clear it in v2 network status documents too, and
7582 also clear it in routerinfo_t when the relay is no longer listed
7583 in the relevant networkstatus document.
7584 - Don't crash if we get an unexpected value for the
7585 PublishServerDescriptor config option. Reported by Matt Edman;
7586 bugfix on 0.2.0.9-alpha.
7587 - Our new v2 hidden service descriptor format allows descriptors
7588 that have no introduction points. But Tor crashed when we tried
7589 to build a descriptor with no intro points (and it would have
7590 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
7592 - Fix building with dmalloc 5.5.2 with glibc.
7593 - Reject uploaded descriptors and extrainfo documents if they're
7594 huge. Otherwise we'll cache them all over the network and it'll
7595 clog everything up. Reported by Aljosha Judmayer.
7596 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
7597 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
7598 - When the DANGEROUS_VERSION controller status event told us we're
7599 running an obsolete version, it used the string "OLD" to describe
7600 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
7601 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
7602 - If we can't expand our list of entry guards (e.g. because we're
7603 using bridges or we have StrictEntryNodes set), don't mark relays
7604 down when they fail a directory request. Otherwise we're too quick
7605 to mark all our entry points down. Bugfix on 0.1.2.x.
7606 - Fix handling of hex nicknames when answering controller requests for
7607 networkstatus by name, or when deciding whether to warn about unknown
7608 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
7609 - Fix a couple of hard-to-trigger autoconf problems that could result
7610 in really weird results on platforms whose sys/types.h files define
7611 nonstandard integer types. Bugfix on 0.1.2.x.
7612 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
7613 - Don't crash on name lookup when we have no current consensus. Fixes
7614 bug 538; bugfix on 0.2.0.x.
7615 - Only Tors that want to mirror the v2 directory info should
7616 create the "cached-status" directory in their datadir. (All Tors
7617 used to create it.) Bugfix on 0.2.0.9-alpha.
7618 - Directory authorities should only automatically download Extra Info
7619 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
7622 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
7623 consumers. (We already do this on HUP.)
7624 - Authorities and caches fetch the v2 networkstatus documents
7625 less often, now that v3 is encouraged.
7626 - Add a new config option BridgeRelay that specifies you want to
7627 be a bridge relay. Right now the only difference is that it makes
7628 you answer begin_dir requests, and it makes you cache dir info,
7629 even if your DirPort isn't on.
7630 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
7631 ask about source, timestamp of arrival, purpose, etc. We need
7632 something like this to help Vidalia not do GeoIP lookups on bridge
7634 - Allow multiple HashedControlPassword config lines, to support
7635 multiple controller passwords.
7636 - Authorities now decide whether they're authoritative for a given
7637 router based on the router's purpose.
7638 - New config options AuthDirBadDir and AuthDirListBadDirs for
7639 authorities to mark certain relays as "bad directories" in the
7640 networkstatus documents. Also supports the "!baddir" directive in
7641 the approved-routers file.
7644 Changes in version 0.2.0.12-alpha - 2007-11-16
7645 This twelfth development snapshot fixes some more build problems as
7646 well as a few minor bugs.
7649 - Make it build on OpenBSD again. Patch from tup.
7650 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
7651 package-building for Red Hat, OS X, etc.
7653 o Minor bugfixes (on 0.1.2.x):
7654 - Changing the ExitPolicyRejectPrivate setting should cause us to
7655 rebuild our server descriptor.
7657 o Minor bugfixes (on 0.2.0.x):
7658 - When we're lacking a consensus, don't try to perform rendezvous
7659 operations. Reported by Karsten Loesing.
7660 - Fix a small memory leak whenever we decide against using a
7661 newly picked entry guard. Reported by Mike Perry.
7662 - When authorities detected more than two relays running on the same
7663 IP address, they were clearing all the status flags but forgetting
7664 to clear the "hsdir" flag. So clients were being told that a
7665 given relay was the right choice for a v2 hsdir lookup, yet they
7666 never had its descriptor because it was marked as 'not running'
7668 - If we're trying to fetch a bridge descriptor and there's no way
7669 the bridge authority could help us (for example, we don't know
7670 a digest, or there is no bridge authority), don't be so eager to
7671 fall back to asking the bridge authority.
7672 - If we're using bridges or have strictentrynodes set, and our
7673 chosen exit is in the same family as all our bridges/entry guards,
7674 then be flexible about families.
7677 - When we negotiate a v2 link-layer connection (not yet implemented),
7678 accept RELAY_EARLY cells and turn them into RELAY cells if we've
7679 negotiated a v1 connection for their next step. Initial code for
7683 Changes in version 0.2.0.11-alpha - 2007-11-12
7684 This eleventh development snapshot fixes some build problems with
7685 the previous snapshot. It also includes a more secure-by-default exit
7686 policy for relays, fixes an enormous memory leak for exit relays, and
7687 fixes another bug where servers were falling out of the directory list.
7690 - Exit policies now reject connections that are addressed to a
7691 relay's public (external) IP address too, unless
7692 ExitPolicyRejectPrivate is turned off. We do this because too
7693 many relays are running nearby to services that trust them based
7694 on network address. Bugfix on 0.1.2.x.
7697 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7698 on every successful resolve. Reported by Mike Perry; bugfix
7700 - On authorities, never downgrade to old router descriptors simply
7701 because they're listed in the consensus. This created a catch-22
7702 where we wouldn't list a new descriptor because there was an
7703 old one in the consensus, and we couldn't get the new one in the
7704 consensus because we wouldn't list it. Possible fix for bug 548.
7705 Also, this might cause bug 543 to appear on authorities; if so,
7706 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
7708 o Packaging fixes on 0.2.0.10-alpha:
7709 - We were including instructions about what to do with the
7710 src/config/fallback-consensus file, but we weren't actually
7711 including it in the tarball. Disable all of that for now.
7714 - Allow people to say PreferTunnelledDirConns rather than
7715 PreferTunneledDirConns, for those alternate-spellers out there.
7718 - Don't reevaluate all the information from our consensus document
7719 just because we've downloaded a v2 networkstatus that we intend
7720 to cache. Fixes bug 545; bugfix on 0.2.0.x.
7723 Changes in version 0.2.0.10-alpha - 2007-11-10
7724 This tenth development snapshot adds a third v3 directory authority
7725 run by Mike Perry, adds most of Karsten Loesing's new hidden service
7726 descriptor format, fixes a bad crash bug and new bridge bugs introduced
7727 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
7728 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
7729 addresses many more minor issues.
7731 o New directory authorities:
7732 - Set up ides (run by Mike Perry) as the third v3 directory authority.
7735 - Allow tunnelled directory connections to ask for an encrypted
7736 "begin_dir" connection or an anonymized "uses a full Tor circuit"
7737 connection independently. Now we can make anonymized begin_dir
7738 connections for (e.g.) more secure hidden service posting and
7740 - More progress on proposal 114: code from Karsten Loesing to
7741 implement new hidden service descriptor format.
7742 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
7743 accommodate the growing number of servers that use the default
7744 and are reaching it.
7745 - Directory authorities use a new formula for selecting which nodes
7746 to advertise as Guards: they must be in the top 7/8 in terms of
7747 how long we have known about them, and above the median of those
7748 nodes in terms of weighted fractional uptime.
7749 - Make "not enough dir info yet" warnings describe *why* Tor feels
7750 it doesn't have enough directory info yet.
7753 - Stop servers from crashing if they set a Family option (or
7754 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
7756 - Make bridge users work again -- the move to v3 directories in
7757 0.2.0.9-alpha had introduced a number of bugs that made bridges
7758 no longer work for clients.
7759 - When the clock jumps forward a lot, do not allow the bandwidth
7760 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
7762 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
7763 - When the consensus lists a router descriptor that we previously were
7764 mirroring, but that we considered non-canonical, reload the
7765 descriptor as canonical. This fixes bug 543 where Tor servers
7766 would start complaining after a few days that they don't have
7767 enough directory information to build a circuit.
7768 - Consider replacing the current consensus when certificates arrive
7769 that make the pending consensus valid. Previously, we were only
7770 considering replacement when the new certs _didn't_ help.
7771 - Fix an assert error on startup if we didn't already have the
7772 consensus and certs cached in our datadirectory: we were caching
7773 the consensus in consensus_waiting_for_certs but then free'ing it
7775 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
7776 Request) if we need more v3 certs but we've already got pending
7777 requests for all of them.
7778 - Correctly back off from failing certificate downloads. Fixes
7780 - Authorities don't vote on the Running flag if they have been running
7781 for less than 30 minutes themselves. Fixes bug 547, where a newly
7782 started authority would vote that everyone was down.
7785 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
7786 it, it had no AES, and it hasn't seen any security patches since
7790 - Clients now hold circuitless TLS connections open for 1.5 times
7791 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
7792 rebuild a new circuit over them within that timeframe. Previously,
7793 they held them open only for KeepalivePeriod (5 minutes).
7794 - Use "If-Modified-Since" to avoid retrieving consensus
7795 networkstatuses that we already have.
7796 - When we have no consensus, check FallbackNetworkstatusFile (defaults
7797 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
7798 we start knowing some directory caches.
7799 - When we receive a consensus from the future, warn about skew.
7800 - Improve skew reporting: try to give the user a better log message
7801 about how skewed they are, and how much this matters.
7802 - When we have a certificate for an authority, believe that
7803 certificate's claims about the authority's IP address.
7804 - New --quiet command-line option to suppress the default console log.
7805 Good in combination with --hash-password.
7806 - Authorities send back an X-Descriptor-Not-New header in response to
7807 an accepted-but-discarded descriptor upload. Partially implements
7809 - Make the log message for "tls error. breaking." more useful.
7810 - Better log messages about certificate downloads, to attempt to
7811 track down the second incarnation of bug 546.
7813 o Minor features (bridges):
7814 - If bridge users set UpdateBridgesFromAuthority, but the digest
7815 they ask for is a 404 from the bridge authority, they now fall
7816 back to trying the bridge directly.
7817 - Bridges now use begin_dir to publish their server descriptor to
7818 the bridge authority, even when they haven't set TunnelDirConns.
7820 o Minor features (controller):
7821 - When reporting clock skew, and we know that the clock is _at least
7822 as skewed_ as some value, but we don't know the actual value,
7823 report the value as a "minimum skew."
7826 - Update linux-tor-prio.sh script to allow QoS based on the uid of
7827 the Tor process. Patch from Marco Bonetti with tweaks from Mike
7831 - Refuse to start if both ORPort and UseBridges are set. Bugfix
7832 on 0.2.0.x, suggested by Matt Edman.
7833 - Don't stop fetching descriptors when FetchUselessDescriptors is
7834 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
7835 reported by tup and ioerror.
7836 - Better log message on vote from unknown authority.
7837 - Don't log "Launching 0 request for 0 router" message.
7839 o Minor bugfixes (memory leaks):
7840 - Stop leaking memory every time we parse a v3 certificate. Bugfix
7842 - Stop leaking memory every time we load a v3 certificate. Bugfix
7843 on 0.2.0.1-alpha. Fixes bug 536.
7844 - Stop leaking a cached networkstatus on exit. Bugfix on
7846 - Stop leaking voter information every time we free a consensus.
7847 Bugfix on 0.2.0.3-alpha.
7848 - Stop leaking signed data every time we check a voter signature.
7849 Bugfix on 0.2.0.3-alpha.
7850 - Stop leaking a signature every time we fail to parse a consensus or
7851 a vote. Bugfix on 0.2.0.3-alpha.
7852 - Stop leaking v2_download_status_map on shutdown. Bugfix on
7854 - Stop leaking conn->nickname every time we make a connection to a
7855 Tor relay without knowing its expected identity digest (e.g. when
7856 using bridges). Bugfix on 0.2.0.3-alpha.
7858 - Minor bugfixes (portability):
7859 - Run correctly on platforms where rlim_t is larger than unsigned
7860 long, and/or where the real limit for number of open files is
7861 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
7862 particular, these may be needed for OS X 10.5.
7865 Changes in version 0.1.2.18 - 2007-10-28
7866 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
7867 hidden service introduction that were causing huge delays, and a big
7868 bug that was causing some servers to disappear from the network status
7869 lists for a few hours each day.
7871 o Major bugfixes (crashes):
7872 - If a connection is shut down abruptly because of something that
7873 happened inside connection_flushed_some(), do not call
7874 connection_finished_flushing(). Should fix bug 451:
7875 "connection_stop_writing: Assertion conn->write_event failed"
7876 Bugfix on 0.1.2.7-alpha.
7877 - Fix possible segfaults in functions called from
7878 rend_process_relay_cell().
7880 o Major bugfixes (hidden services):
7881 - Hidden services were choosing introduction points uniquely by
7882 hexdigest, but when constructing the hidden service descriptor
7883 they merely wrote the (potentially ambiguous) nickname.
7884 - Clients now use the v2 intro format for hidden service
7885 connections: they specify their chosen rendezvous point by identity
7886 digest rather than by (potentially ambiguous) nickname. These
7887 changes could speed up hidden service connections dramatically.
7889 o Major bugfixes (other):
7890 - Stop publishing a new server descriptor just because we get a
7891 HUP signal. This led (in a roundabout way) to some servers getting
7892 dropped from the networkstatus lists for a few hours each day.
7893 - When looking for a circuit to cannibalize, consider family as well
7894 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
7895 circuit cannibalization).
7896 - When a router wasn't listed in a new networkstatus, we were leaving
7897 the flags for that router alone -- meaning it remained Named,
7898 Running, etc -- even though absence from the networkstatus means
7899 that it shouldn't be considered to exist at all anymore. Now we
7900 clear all the flags for routers that fall out of the networkstatus
7901 consensus. Fixes bug 529.
7904 - Don't try to access (or alter) the state file when running
7905 --list-fingerprint or --verify-config or --hash-password. Resolves
7907 - When generating information telling us how to extend to a given
7908 router, do not try to include the nickname if it is
7909 absent. Resolves bug 467.
7910 - Fix a user-triggerable segfault in expand_filename(). (There isn't
7911 a way to trigger this remotely.)
7912 - When sending a status event to the controller telling it that an
7913 OR address is reachable, set the port correctly. (Previously we
7914 were reporting the dir port.)
7915 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
7916 command. Bugfix on 0.1.2.17.
7917 - When loading bandwidth history, do not believe any information in
7918 the future. Fixes bug 434.
7919 - When loading entry guard information, do not believe any information
7921 - When we have our clock set far in the future and generate an
7922 onion key, then re-set our clock to be correct, we should not stop
7923 the onion key from getting rotated.
7924 - On some platforms, accept() can return a broken address. Detect
7925 this more quietly, and deal accordingly. Fixes bug 483.
7926 - It's not actually an error to find a non-pending entry in the DNS
7927 cache when canceling a pending resolve. Don't log unless stuff
7928 is fishy. Resolves bug 463.
7929 - Don't reset trusted dir server list when we set a configuration
7930 option. Patch from Robert Hogan.
7931 - Don't try to create the datadir when running --verify-config or
7932 --hash-password. Resolves bug 540.
7935 Changes in version 0.2.0.9-alpha - 2007-10-24
7936 This ninth development snapshot switches clients to the new v3 directory
7937 system; allows servers to be listed in the network status even when they
7938 have the same nickname as a registered server; and fixes many other
7939 bugs including a big one that was causing some servers to disappear
7940 from the network status lists for a few hours each day.
7942 o Major features (directory system):
7943 - Clients now download v3 consensus networkstatus documents instead
7944 of v2 networkstatus documents. Clients and caches now base their
7945 opinions about routers on these consensus documents. Clients only
7946 download router descriptors listed in the consensus.
7947 - Authorities now list servers who have the same nickname as
7948 a different named server, but list them with a new flag,
7949 "Unnamed". Now we can list servers that happen to pick the same
7950 nickname as a server that registered two years ago and then
7951 disappeared. Partially implements proposal 122.
7952 - If the consensus lists a router as "Unnamed", the name is assigned
7953 to a different router: do not identify the router by that name.
7954 Partially implements proposal 122.
7955 - Authorities can now come to a consensus on which method to use to
7956 compute the consensus. This gives us forward compatibility.
7959 - Stop publishing a new server descriptor just because we HUP or
7960 when we find our DirPort to be reachable but won't actually publish
7961 it. New descriptors without any real changes are dropped by the
7962 authorities, and can screw up our "publish every 18 hours" schedule.
7964 - When a router wasn't listed in a new networkstatus, we were leaving
7965 the flags for that router alone -- meaning it remained Named,
7966 Running, etc -- even though absence from the networkstatus means
7967 that it shouldn't be considered to exist at all anymore. Now we
7968 clear all the flags for routers that fall out of the networkstatus
7969 consensus. Fixes bug 529; bugfix on 0.1.2.x.
7970 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
7971 extrainfo documents and then discard them immediately for not
7972 matching the latest router. Bugfix on 0.2.0.1-alpha.
7974 o Minor features (v3 directory protocol):
7975 - Allow tor-gencert to generate a new certificate without replacing
7977 - Allow certificates to include an address.
7978 - When we change our directory-cache settings, reschedule all voting
7979 and download operations.
7980 - Reattempt certificate downloads immediately on failure, as long as
7981 we haven't failed a threshold number of times yet.
7982 - Delay retrying consensus downloads while we're downloading
7983 certificates to verify the one we just got. Also, count getting a
7984 consensus that we already have (or one that isn't valid) as a failure,
7985 and count failing to get the certificates after 20 minutes as a
7987 - Build circuits and download descriptors even if our consensus is a
7988 little expired. (This feature will go away once authorities are
7991 o Minor features (router descriptor cache):
7992 - If we find a cached-routers file that's been sitting around for more
7993 than 28 days unmodified, then most likely it's a leftover from
7994 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
7996 - When we (as a cache) download a descriptor because it was listed
7997 in a consensus, remember when the consensus was supposed to expire,
7998 and don't expire the descriptor until then.
8000 o Minor features (performance):
8001 - Call routerlist_remove_old_routers() much less often. This should
8002 speed startup, especially on directory caches.
8003 - Don't try to launch new descriptor downloads quite so often when we
8004 already have enough directory information to build circuits.
8005 - Base64 decoding was actually showing up on our profile when parsing
8006 the initial descriptor file; switch to an in-process all-at-once
8007 implementation that's about 3.5x times faster than calling out to
8010 o Minor features (compilation):
8011 - Detect non-ASCII platforms (if any still exist) and refuse to
8012 build there: some of our code assumes that 'A' is 65 and so on.
8014 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
8015 - Make the "next period" votes into "current period" votes immediately
8016 after publishing the consensus; avoid a heisenbug that made them
8017 stick around indefinitely.
8018 - When we discard a vote as a duplicate, do not report this as
8020 - Treat missing v3 keys or certificates as an error when running as a
8021 v3 directory authority.
8022 - When we're configured to be a v3 authority, but we're only listed
8023 as a non-v3 authority in our DirServer line for ourself, correct
8025 - If an authority doesn't have a qualified hostname, just put
8026 its address in the vote. This fixes the problem where we referred to
8027 "moria on moria:9031."
8028 - Distinguish between detached signatures for the wrong period, and
8029 detached signatures for a divergent vote.
8030 - Fix a small memory leak when computing a consensus.
8031 - When there's no concensus, we were forming a vote every 30
8032 minutes, but writing the "valid-after" line in our vote based
8033 on our configured V3AuthVotingInterval: so unless the intervals
8034 matched up, we immediately rejected our own vote because it didn't
8035 start at the voting interval that caused us to construct a vote.
8037 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
8038 - Delete unverified-consensus when the real consensus is set.
8039 - Consider retrying a consensus networkstatus fetch immediately
8040 after one fails: don't wait 60 seconds to notice.
8041 - When fetching a consensus as a cache, wait until a newer consensus
8042 should exist before trying to replace the current one.
8043 - Use a more forgiving schedule for retrying failed consensus
8044 downloads than for other types.
8046 o Minor bugfixes (other directory issues):
8047 - Correct the implementation of "download votes by digest." Bugfix on
8049 - Authorities no longer send back "400 you're unreachable please fix
8050 it" errors to Tor servers that aren't online all the time. We're
8051 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
8053 o Minor bugfixes (controller):
8054 - Don't reset trusted dir server list when we set a configuration
8055 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
8056 - Respond to INT and TERM SIGNAL commands before we execute the
8057 signal, in case the signal shuts us down. We had a patch in
8058 0.1.2.1-alpha that tried to do this by queueing the response on
8059 the connection's buffer before shutting down, but that really
8060 isn't the same thing at all. Bug located by Matt Edman.
8062 o Minor bugfixes (misc):
8063 - Correctly check for bad options to the "PublishServerDescriptor"
8064 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
8065 - Stop leaking memory on failing case of base32_decode, and make
8066 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
8067 - Don't try to download extrainfo documents when we're trying to
8068 fetch enough directory info to build a circuit: having enough
8069 info should get priority. Bugfix on 0.2.0.x.
8070 - Don't complain that "your server has not managed to confirm that its
8071 ports are reachable" if we haven't been able to build any circuits
8072 yet. Bug found by spending four hours without a v3 consensus. Bugfix
8074 - Detect the reason for failing to mmap a descriptor file we just
8075 wrote, and give a more useful log message. Fixes bug 533. Bugfix
8078 o Code simplifications and refactoring:
8079 - Remove support for the old bw_accounting file: we've been storing
8080 bandwidth accounting information in the state file since
8081 0.1.2.5-alpha. This may result in bandwidth accounting errors
8082 if you try to upgrade from 0.1.1.x or earlier, or if you try to
8083 downgrade to 0.1.1.x or earlier.
8084 - New convenience code to locate a file within the DataDirectory.
8085 - Move non-authority functionality out of dirvote.c.
8086 - Refactor the arguments for router_pick_{directory_|trusteddir}server
8087 so that they all take the same named flags.
8090 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
8091 Unix users an easy way to script their Tor process (e.g. by
8092 adjusting bandwidth based on the time of the day).
8095 Changes in version 0.2.0.8-alpha - 2007-10-12
8096 This eighth development snapshot fixes a crash bug that's been bothering
8097 us since February 2007, lets bridge authorities store a list of bridge
8098 descriptors they've seen, gets v3 directory voting closer to working,
8099 starts caching v3 directory consensus documents on directory mirrors,
8100 and fixes a variety of smaller issues including some minor memory leaks.
8102 o Major features (router descriptor cache):
8103 - Store routers in a file called cached-descriptors instead of in
8104 cached-routers. Initialize cached-descriptors from cached-routers
8105 if the old format is around. The new format allows us to store
8106 annotations along with descriptors.
8107 - Use annotations to record the time we received each descriptor, its
8108 source, and its purpose.
8109 - Disable the SETROUTERPURPOSE controller command: it is now
8111 - Controllers should now specify cache=no or cache=yes when using
8112 the +POSTDESCRIPTOR command.
8113 - Bridge authorities now write bridge descriptors to disk, meaning
8114 we can export them to other programs and begin distributing them
8117 o Major features (directory authorities):
8118 - When a v3 authority is missing votes or signatures, it now tries
8120 - Directory authorities track weighted fractional uptime as well as
8121 weighted mean-time-between failures. WFU is suitable for deciding
8122 whether a node is "usually up", while MTBF is suitable for deciding
8123 whether a node is "likely to stay up." We need both, because
8124 "usually up" is a good requirement for guards, while "likely to
8125 stay up" is a good requirement for long-lived connections.
8127 o Major features (v3 directory system):
8128 - Caches now download v3 network status documents as needed,
8129 and download the descriptors listed in them.
8130 - All hosts now attempt to download and keep fresh v3 authority
8131 certificates, and re-attempt after failures.
8132 - More internal-consistency checks for vote parsing.
8134 o Major bugfixes (crashes):
8135 - If a connection is shut down abruptly because of something that
8136 happened inside connection_flushed_some(), do not call
8137 connection_finished_flushing(). Should fix bug 451. Bugfix on
8140 o Major bugfixes (performance):
8141 - Fix really bad O(n^2) performance when parsing a long list of
8142 routers: Instead of searching the entire list for an "extra-info "
8143 string which usually wasn't there, once for every routerinfo
8144 we read, just scan lines forward until we find one we like.
8146 - When we add data to a write buffer in response to the data on that
8147 write buffer getting low because of a flush, do not consider the
8148 newly added data as a candidate for immediate flushing, but rather
8149 make it wait until the next round of writing. Otherwise, we flush
8150 and refill recursively, and a single greedy TLS connection can
8151 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
8153 o Minor features (v3 authority system):
8154 - Add more ways for tools to download the votes that lead to the
8156 - Send a 503 when low on bandwidth and a vote, consensus, or
8157 certificate is requested.
8158 - If-modified-since is now implemented properly for all kinds of
8159 certificate requests.
8161 o Minor bugfixes (network statuses):
8162 - Tweak the implementation of proposal 109 slightly: allow at most
8163 two Tor servers on the same IP address, except if it's the location
8164 of a directory authority, in which case allow five. Bugfix on
8167 o Minor bugfixes (controller):
8168 - When sending a status event to the controller telling it that an
8169 OR address is reachable, set the port correctly. (Previously we
8170 were reporting the dir port.) Bugfix on 0.1.2.x.
8172 o Minor bugfixes (v3 directory system):
8173 - Fix logic to look up a cert by its signing key digest. Bugfix on
8175 - Only change the reply to a vote to "OK" if it's not already
8176 set. This gets rid of annoying "400 OK" log messages, which may
8177 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
8178 - When we get a valid consensus, recompute the voting schedule.
8179 - Base the valid-after time of a vote on the consensus voting
8180 schedule, not on our preferred schedule.
8181 - Make the return values and messages from signature uploads and
8182 downloads more sensible.
8183 - Fix a memory leak when serving votes and consensus documents, and
8184 another when serving certificates.
8186 o Minor bugfixes (performance):
8187 - Use a slightly simpler string hashing algorithm (copying Python's
8188 instead of Java's) and optimize our digest hashing algorithm to take
8189 advantage of 64-bit platforms and to remove some possibly-costly
8191 - Fix a minor memory leak whenever we parse guards from our state
8192 file. Bugfix on 0.2.0.7-alpha.
8193 - Fix a minor memory leak whenever we write out a file. Bugfix on
8195 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8196 command. Bugfix on 0.2.0.5-alpha.
8198 o Minor bugfixes (portability):
8199 - On some platforms, accept() can return a broken address. Detect
8200 this more quietly, and deal accordingly. Fixes bug 483.
8201 - Stop calling tor_strlower() on uninitialized memory in some cases.
8202 Bugfix in 0.2.0.7-alpha.
8204 o Minor bugfixes (usability):
8205 - Treat some 403 responses from directory servers as INFO rather than
8206 WARN-severity events.
8207 - It's not actually an error to find a non-pending entry in the DNS
8208 cache when canceling a pending resolve. Don't log unless stuff is
8209 fishy. Resolves bug 463.
8211 o Minor bugfixes (anonymity):
8212 - Never report that we've used more bandwidth than we're willing to
8213 relay: it leaks how much non-relay traffic we're using. Resolves
8215 - When looking for a circuit to cannibalize, consider family as well
8216 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8217 circuit cannibalization).
8219 o Code simplifications and refactoring:
8220 - Make a bunch of functions static. Remove some dead code.
8221 - Pull out about a third of the really big routerlist.c; put it in a
8222 new module, networkstatus.c.
8223 - Merge the extra fields in local_routerstatus_t back into
8224 routerstatus_t: we used to need one routerstatus_t for each
8225 authority's opinion, plus a local_routerstatus_t for the locally
8226 computed consensus opinion. To save space, we put the locally
8227 modified fields into local_routerstatus_t, and only the common
8228 stuff into routerstatus_t. But once v3 directories are in use,
8229 clients and caches will no longer need to hold authority opinions;
8230 thus, the rationale for keeping the types separate is now gone.
8231 - Make the code used to reschedule and reattempt downloads more
8233 - Turn all 'Are we a directory server/mirror?' logic into a call to
8235 - Remove the code to generate the oldest (v1) directory format.
8236 The code has been disabled since 0.2.0.5-alpha.
8239 Changes in version 0.2.0.7-alpha - 2007-09-21
8240 This seventh development snapshot makes bridges work again, makes bridge
8241 authorities work for the first time, fixes two huge performance flaws
8242 in hidden services, and fixes a variety of minor issues.
8244 o New directory authorities:
8245 - Set up moria1 and tor26 as the first v3 directory authorities. See
8246 doc/spec/dir-spec.txt for details on the new directory design.
8248 o Major bugfixes (crashes):
8249 - Fix possible segfaults in functions called from
8250 rend_process_relay_cell(). Bugfix on 0.1.2.x.
8252 o Major bugfixes (bridges):
8253 - Fix a bug that made servers send a "404 Not found" in response to
8254 attempts to fetch their server descriptor. This caused Tor servers
8255 to take many minutes to establish reachability for their DirPort,
8256 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
8257 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
8258 users configure that and specify a bridge with an identity
8259 fingerprint, now they will lookup the bridge descriptor at the
8260 default bridge authority via a one-hop tunnel, but once circuits
8261 are established they will switch to a three-hop tunnel for later
8262 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
8264 o Major bugfixes (hidden services):
8265 - Hidden services were choosing introduction points uniquely by
8266 hexdigest, but when constructing the hidden service descriptor
8267 they merely wrote the (potentially ambiguous) nickname.
8268 - Clients now use the v2 intro format for hidden service
8269 connections: they specify their chosen rendezvous point by identity
8270 digest rather than by (potentially ambiguous) nickname. Both
8271 are bugfixes on 0.1.2.x, and they could speed up hidden service
8272 connections dramatically. Thanks to Karsten Loesing.
8274 o Minor features (security):
8275 - As a client, do not believe any server that tells us that an
8276 address maps to an internal address space.
8277 - Make it possible to enable HashedControlPassword and
8278 CookieAuthentication at the same time.
8280 o Minor features (guard nodes):
8281 - Tag every guard node in our state file with the version that
8282 we believe added it, or with our own version if we add it. This way,
8283 if a user temporarily runs an old version of Tor and then switches
8284 back to a new one, she doesn't automatically lose her guards.
8286 o Minor features (speed):
8287 - When implementing AES counter mode, update only the portions of the
8288 counter buffer that need to change, and don't keep separate
8289 network-order and host-order counters when they are the same (i.e.,
8290 on big-endian hosts.)
8292 o Minor features (controller):
8293 - Accept LF instead of CRLF on controller, since some software has a
8294 hard time generating real Internet newlines.
8295 - Add GETINFO values for the server status events
8296 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
8300 - Routers no longer include bandwidth-history lines in their
8301 descriptors; this information is already available in extra-info
8302 documents, and including it in router descriptors took up 60%
8303 (!) of compressed router descriptor downloads. Completes
8304 implementation of proposal 104.
8305 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
8306 and TorControl.py, as they use the old v0 controller protocol,
8307 and are obsoleted by TorFlow anyway.
8308 - Drop support for v1 rendezvous descriptors, since we never used
8309 them anyway, and the code has probably rotted by now. Based on
8310 patch from Karsten Loesing.
8311 - On OSX, stop warning the user that kqueue support in libevent is
8312 "experimental", since it seems to have worked fine for ages.
8315 - When generating information telling us how to extend to a given
8316 router, do not try to include the nickname if it is absent. Fixes
8317 bug 467. Bugfix on 0.2.0.3-alpha.
8318 - Fix a user-triggerable (but not remotely-triggerable) segfault
8319 in expand_filename(). Bugfix on 0.1.2.x.
8320 - Fix a memory leak when freeing incomplete requests from DNSPort.
8321 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
8322 - Don't try to access (or alter) the state file when running
8323 --list-fingerprint or --verify-config or --hash-password. (Resolves
8324 bug 499.) Bugfix on 0.1.2.x.
8325 - Servers used to decline to publish their DirPort if their
8326 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
8327 were below a threshold. Now they only look at BandwidthRate and
8328 RelayBandwidthRate. Bugfix on 0.1.2.x.
8329 - Remove an optimization in the AES counter-mode code that assumed
8330 that the counter never exceeded 2^68. When the counter can be set
8331 arbitrarily as an IV (as it is by Karsten's new hidden services
8332 code), this assumption no longer holds. Bugfix on 0.1.2.x.
8333 - Resume listing "AUTHORITY" flag for authorities in network status.
8334 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
8336 o Code simplifications and refactoring:
8337 - Revamp file-writing logic so we don't need to have the entire
8338 contents of a file in memory at once before we write to disk. Tor,
8340 - Turn "descriptor store" into a full-fledged type.
8341 - Move all NT services code into a separate source file.
8342 - Unify all code that computes medians, percentile elements, etc.
8343 - Get rid of a needless malloc when parsing address policies.
8346 Changes in version 0.1.2.17 - 2007-08-30
8347 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
8348 X bundles. Vidalia 0.0.14 makes authentication required for the
8349 ControlPort in the default configuration, which addresses important
8350 security risks. Everybody who uses Vidalia (or another controller)
8353 In addition, this Tor update fixes major load balancing problems with
8354 path selection, which should speed things up a lot once many people
8357 o Major bugfixes (security):
8358 - We removed support for the old (v0) control protocol. It has been
8359 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
8360 become more of a headache than it's worth.
8362 o Major bugfixes (load balancing):
8363 - When choosing nodes for non-guard positions, weight guards
8364 proportionally less, since they already have enough load. Patch
8366 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8367 will allow fast Tor servers to get more attention.
8368 - When we're upgrading from an old Tor version, forget our current
8369 guards and pick new ones according to the new weightings. These
8370 three load balancing patches could raise effective network capacity
8371 by a factor of four. Thanks to Mike Perry for measurements.
8373 o Major bugfixes (stream expiration):
8374 - Expire not-yet-successful application streams in all cases if
8375 they've been around longer than SocksTimeout. Right now there are
8376 some cases where the stream will live forever, demanding a new
8377 circuit every 15 seconds. Fixes bug 454; reported by lodger.
8379 o Minor features (controller):
8380 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8381 is valid before any authentication has been received. It tells
8382 a controller what kind of authentication is expected, and what
8383 protocol is spoken. Implements proposal 119.
8385 o Minor bugfixes (performance):
8386 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
8387 greatly speeding up loading cached-routers from disk on startup.
8388 - Disable sentinel-based debugging for buffer code: we squashed all
8389 the bugs that this was supposed to detect a long time ago, and now
8390 its only effect is to change our buffer sizes from nice powers of
8391 two (which platform mallocs tend to like) to values slightly over
8392 powers of two (which make some platform mallocs sad).
8394 o Minor bugfixes (misc):
8395 - If exit bandwidth ever exceeds one third of total bandwidth, then
8396 use the correct formula to weight exit nodes when choosing paths.
8397 Based on patch from Mike Perry.
8398 - Choose perfectly fairly among routers when choosing by bandwidth and
8399 weighting by fraction of bandwidth provided by exits. Previously, we
8400 would choose with only approximate fairness, and correct ourselves
8401 if we ran off the end of the list.
8402 - If we require CookieAuthentication but we fail to write the
8403 cookie file, we would warn but not exit, and end up in a state
8404 where no controller could authenticate. Now we exit.
8405 - If we require CookieAuthentication, stop generating a new cookie
8406 every time we change any piece of our config.
8407 - Refuse to start with certain directory authority keys, and
8408 encourage people using them to stop.
8409 - Terminate multi-line control events properly. Original patch
8411 - Fix a minor memory leak when we fail to find enough suitable
8412 servers to choose a circuit.
8413 - Stop leaking part of the descriptor when we run into a particularly
8414 unparseable piece of it.
8417 Changes in version 0.2.0.6-alpha - 2007-08-26
8418 This sixth development snapshot features a new Vidalia version in the
8419 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
8420 the ControlPort in the default configuration, which addresses important
8423 In addition, this snapshot fixes major load balancing problems
8424 with path selection, which should speed things up a lot once many
8425 people have upgraded. The directory authorities also use a new
8426 mean-time-between-failure approach to tracking which servers are stable,
8427 rather than just looking at the most recent uptime.
8429 o New directory authorities:
8430 - Set up Tonga as the default bridge directory authority.
8433 - Directory authorities now track servers by weighted
8434 mean-times-between-failures. When we have 4 or more days of data,
8435 use measured MTBF rather than declared uptime to decide whether
8436 to call a router Stable. Implements proposal 108.
8438 o Major bugfixes (load balancing):
8439 - When choosing nodes for non-guard positions, weight guards
8440 proportionally less, since they already have enough load. Patch
8442 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8443 will allow fast Tor servers to get more attention.
8444 - When we're upgrading from an old Tor version, forget our current
8445 guards and pick new ones according to the new weightings. These
8446 three load balancing patches could raise effective network capacity
8447 by a factor of four. Thanks to Mike Perry for measurements.
8449 o Major bugfixes (descriptor parsing):
8450 - Handle unexpected whitespace better in malformed descriptors. Bug
8451 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
8454 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
8455 GETINFO for Torstat to use until it can switch to using extrainfos.
8456 - Optionally (if built with -DEXPORTMALLINFO) export the output
8457 of mallinfo via http, as tor/mallinfo.txt. Only accessible
8461 - Do not intermix bridge routers with controller-added
8462 routers. (Bugfix on 0.2.0.x)
8463 - Do not fail with an assert when accept() returns an unexpected
8464 address family. Addresses but does not wholly fix bug 483. (Bugfix
8466 - Let directory authorities startup even when they can't generate
8467 a descriptor immediately, e.g. because they don't know their
8469 - Stop putting the authentication cookie in a file called "0"
8470 in your working directory if you don't specify anything for the
8471 new CookieAuthFile option. Reported by Matt Edman.
8472 - Make it possible to read the PROTOCOLINFO response in a way that
8473 conforms to our control-spec. Reported by Matt Edman.
8474 - Fix a minor memory leak when we fail to find enough suitable
8475 servers to choose a circuit. Bugfix on 0.1.2.x.
8476 - Stop leaking part of the descriptor when we run into a particularly
8477 unparseable piece of it. Bugfix on 0.1.2.x.
8478 - Unmap the extrainfo cache file on exit.
8481 Changes in version 0.2.0.5-alpha - 2007-08-19
8482 This fifth development snapshot fixes compilation on Windows again;
8483 fixes an obnoxious client-side bug that slowed things down and put
8484 extra load on the network; gets us closer to using the v3 directory
8485 voting scheme; makes it easier for Tor controllers to use cookie-based
8486 authentication; and fixes a variety of other bugs.
8489 - Version 1 directories are no longer generated in full. Instead,
8490 authorities generate and serve "stub" v1 directories that list
8491 no servers. This will stop Tor versions 0.1.0.x and earlier from
8492 working, but (for security reasons) nobody should be running those
8495 o Major bugfixes (compilation, 0.2.0.x):
8496 - Try to fix Win32 compilation again: improve checking for IPv6 types.
8497 - Try to fix MSVC compilation: build correctly on platforms that do
8498 not define s6_addr16 or s6_addr32.
8499 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
8502 o Major bugfixes (stream expiration):
8503 - Expire not-yet-successful application streams in all cases if
8504 they've been around longer than SocksTimeout. Right now there are
8505 some cases where the stream will live forever, demanding a new
8506 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
8509 o Minor features (directory servers):
8510 - When somebody requests a list of statuses or servers, and we have
8511 none of those, return a 404 rather than an empty 200.
8513 o Minor features (directory voting):
8514 - Store v3 consensus status consensuses on disk, and reload them
8517 o Minor features (security):
8518 - Warn about unsafe ControlPort configurations.
8519 - Refuse to start with certain directory authority keys, and
8520 encourage people using them to stop.
8522 o Minor features (controller):
8523 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8524 is valid before any authentication has been received. It tells
8525 a controller what kind of authentication is expected, and what
8526 protocol is spoken. Implements proposal 119.
8527 - New config option CookieAuthFile to choose a new location for the
8528 cookie authentication file, and config option
8529 CookieAuthFileGroupReadable to make it group-readable.
8531 o Minor features (unit testing):
8532 - Add command-line arguments to unit-test executable so that we can
8533 invoke any chosen test from the command line rather than having
8534 to run the whole test suite at once; and so that we can turn on
8535 logging for the unit tests.
8537 o Minor bugfixes (on 0.1.2.x):
8538 - If we require CookieAuthentication but we fail to write the
8539 cookie file, we would warn but not exit, and end up in a state
8540 where no controller could authenticate. Now we exit.
8541 - If we require CookieAuthentication, stop generating a new cookie
8542 every time we change any piece of our config.
8543 - When loading bandwidth history, do not believe any information in
8544 the future. Fixes bug 434.
8545 - When loading entry guard information, do not believe any information
8547 - When we have our clock set far in the future and generate an
8548 onion key, then re-set our clock to be correct, we should not stop
8549 the onion key from getting rotated.
8550 - Clean up torrc sample config file.
8551 - Do not automatically run configure from autogen.sh. This
8552 non-standard behavior tended to annoy people who have built other
8555 o Minor bugfixes (on 0.2.0.x):
8556 - Fix a bug with AutomapHostsOnResolve that would always cause
8557 the second request to fail. Bug reported by Kate. Bugfix on
8559 - Fix a bug in ADDRMAP controller replies that would sometimes
8560 try to print a NULL. Patch from tup.
8561 - Read v3 directory authority keys from the right location.
8562 - Numerous bugfixes to directory voting code.
8565 Changes in version 0.1.2.16 - 2007-08-01
8566 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
8567 remote attacker in certain situations to rewrite the user's torrc
8568 configuration file. This can completely compromise anonymity of users
8569 in most configurations, including those running the Vidalia bundles,
8570 TorK, etc. Or worse.
8572 o Major security fixes:
8573 - Close immediately after missing authentication on control port;
8574 do not allow multiple authentication attempts.
8577 Changes in version 0.2.0.4-alpha - 2007-08-01
8578 This fourth development snapshot fixes a critical security vulnerability
8579 for most users, specifically those running Vidalia, TorK, etc. Everybody
8580 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
8582 o Major security fixes:
8583 - Close immediately after missing authentication on control port;
8584 do not allow multiple authentication attempts.
8586 o Major bugfixes (compilation):
8587 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
8590 o Minor features (performance):
8591 - Be even more aggressive about releasing RAM from small
8592 empty buffers. Thanks to our free-list code, this shouldn't be too
8593 performance-intensive.
8594 - Disable sentinel-based debugging for buffer code: we squashed all
8595 the bugs that this was supposed to detect a long time ago, and
8596 now its only effect is to change our buffer sizes from nice
8597 powers of two (which platform mallocs tend to like) to values
8598 slightly over powers of two (which make some platform mallocs sad).
8599 - Log malloc statistics from mallinfo() on platforms where it
8603 Changes in version 0.2.0.3-alpha - 2007-07-29
8604 This third development snapshot introduces new experimental
8605 blocking-resistance features and a preliminary version of the v3
8606 directory voting design, and includes many other smaller features
8610 - The first pieces of our "bridge" design for blocking-resistance
8611 are implemented. People can run bridge directory authorities;
8612 people can run bridges; and people can configure their Tor clients
8613 with a set of bridges to use as the first hop into the Tor network.
8614 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
8616 - Create listener connections before we setuid to the configured
8617 User and Group. Now non-Windows users can choose port values
8618 under 1024, start Tor as root, and have Tor bind those ports
8619 before it changes to another UID. (Windows users could already
8621 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
8622 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
8623 on "vserver" accounts. (Patch from coderman.)
8624 - Be even more aggressive about separating local traffic from relayed
8625 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
8627 o Major features (experimental):
8628 - First cut of code for "v3 dir voting": directory authorities will
8629 vote on a common network status document rather than each publishing
8630 their own opinion. This code needs more testing and more corner-case
8631 handling before it's ready for use.
8634 - Directory authorities now call routers Fast if their bandwidth is
8635 at least 100KB/s, and consider their bandwidth adequate to be a
8636 Guard if it is at least 250KB/s, no matter the medians. This fix
8637 complements proposal 107. [Bugfix on 0.1.2.x]
8638 - Directory authorities now never mark more than 3 servers per IP as
8639 Valid and Running. (Implements proposal 109, by Kevin Bauer and
8641 - Minor change to organizationName and commonName generation
8642 procedures in TLS certificates during Tor handshakes, to invalidate
8643 some earlier censorware approaches. This is not a long-term
8644 solution, but applying it will give us a bit of time to look into
8645 the epidemiology of countermeasures as they spread.
8647 o Major bugfixes (directory):
8648 - Rewrite directory tokenization code to never run off the end of
8649 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
8651 o Minor features (controller):
8652 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
8653 match requests to applications. (Patch from Robert Hogan.)
8654 - Report address and port correctly on connections to DNSPort. (Patch
8656 - Add a RESOLVE command to launch hostname lookups. (Original patch
8658 - Add GETINFO status/enough-dir-info to let controllers tell whether
8659 Tor has downloaded sufficient directory information. (Patch
8661 - You can now use the ControlSocket option to tell Tor to listen for
8662 controller connections on Unix domain sockets on systems that
8663 support them. (Patch from Peter Palfrader.)
8664 - STREAM NEW events are generated for DNSPort requests and for
8665 tunneled directory connections. (Patch from Robert Hogan.)
8666 - New "GETINFO address-mappings/*" command to get address mappings
8667 with expiry information. "addr-mappings/*" is now deprecated.
8670 o Minor features (misc):
8671 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
8673 - The tor-gencert tool for v3 directory authorities now creates all
8674 files as readable to the file creator only, and write-protects
8675 the authority identity key.
8676 - When dumping memory usage, list bytes used in buffer memory
8678 - When running with dmalloc, dump more stats on hup and on exit.
8679 - Directory authorities now fail quickly and (relatively) harmlessly
8680 if they generate a network status document that is somehow
8683 o Traffic load balancing improvements:
8684 - If exit bandwidth ever exceeds one third of total bandwidth, then
8685 use the correct formula to weight exit nodes when choosing paths.
8686 (Based on patch from Mike Perry.)
8687 - Choose perfectly fairly among routers when choosing by bandwidth and
8688 weighting by fraction of bandwidth provided by exits. Previously, we
8689 would choose with only approximate fairness, and correct ourselves
8690 if we ran off the end of the list. [Bugfix on 0.1.2.x]
8692 o Performance improvements:
8693 - Be more aggressive with freeing buffer RAM or putting it on the
8695 - Use Critical Sections rather than Mutexes for synchronizing threads
8696 on win32; Mutexes are heavier-weight, and designed for synchronizing
8699 o Deprecated and removed features:
8700 - RedirectExits is now deprecated.
8701 - Stop allowing address masks that do not correspond to bit prefixes.
8702 We have warned about these for a really long time; now it's time
8703 to reject them. (Patch from croup.)
8705 o Minor bugfixes (directory):
8706 - Fix another crash bug related to extra-info caching. (Bug found by
8707 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
8708 - Directories no longer return a "304 not modified" when they don't
8709 have the networkstatus the client asked for. Also fix a memory
8710 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
8711 - We had accidentally labelled 0.1.2.x directory servers as not
8712 suitable for begin_dir requests, and had labelled no directory
8713 servers as suitable for uploading extra-info documents. [Bugfix
8716 o Minor bugfixes (dns):
8717 - Fix a crash when DNSPort is set more than once. (Patch from Robert
8718 Hogan.) [Bugfix on 0.2.0.2-alpha]
8719 - Add DNSPort connections to the global connection list, so that we
8720 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
8722 - Fix a dangling reference that could lead to a crash when DNSPort is
8723 changed or closed (Patch from Robert Hogan.) [Bugfix on
8726 o Minor bugfixes (controller):
8727 - Provide DNS expiry times in GMT, not in local time. For backward
8728 compatibility, ADDRMAP events only provide GMT expiry in an extended
8729 field. "GETINFO address-mappings" always does the right thing.
8730 - Use CRLF line endings properly in NS events.
8731 - Terminate multi-line control events properly. (Original patch
8732 from tup.) [Bugfix on 0.1.2.x-alpha]
8733 - Do not include spaces in SOURCE_ADDR fields in STREAM
8734 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
8737 Changes in version 0.1.2.15 - 2007-07-17
8738 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
8739 problems, fixes compilation on BSD, and fixes a variety of other
8740 bugs. Everybody should upgrade.
8742 o Major bugfixes (compilation):
8743 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
8745 o Major bugfixes (crashes):
8746 - Try even harder not to dereference the first character after
8747 an mmap(). Reported by lodger.
8748 - Fix a crash bug in directory authorities when we re-number the
8749 routerlist while inserting a new router.
8750 - When the cached-routers file is an even multiple of the page size,
8751 don't run off the end and crash. (Fixes bug 455; based on idea
8753 - Fix eventdns.c behavior on Solaris: It is critical to include
8754 orconfig.h _before_ sys/types.h, so that we can get the expected
8755 definition of _FILE_OFFSET_BITS.
8757 o Major bugfixes (security):
8758 - Fix a possible buffer overrun when using BSD natd support. Bug
8760 - When sending destroy cells from a circuit's origin, don't include
8761 the reason for tearing down the circuit. The spec says we didn't,
8762 and now we actually don't. Reported by lodger.
8763 - Keep streamids from different exits on a circuit separate. This
8764 bug may have allowed other routers on a given circuit to inject
8765 cells into streams. Reported by lodger; fixes bug 446.
8766 - If there's a never-before-connected-to guard node in our list,
8767 never choose any guards past it. This way we don't expand our
8768 guard list unless we need to.
8770 o Minor bugfixes (guard nodes):
8771 - Weight guard selection by bandwidth, so that low-bandwidth nodes
8772 don't get overused as guards.
8774 o Minor bugfixes (directory):
8775 - Correctly count the number of authorities that recommend each
8776 version. Previously, we were under-counting by 1.
8777 - Fix a potential crash bug when we load many server descriptors at
8778 once and some of them make others of them obsolete. Fixes bug 458.
8780 o Minor bugfixes (hidden services):
8781 - Stop tearing down the whole circuit when the user asks for a
8782 connection to a port that the hidden service didn't configure.
8785 o Minor bugfixes (misc):
8786 - On Windows, we were preventing other processes from reading
8787 cached-routers while Tor was running. Reported by janbar.
8788 - Fix a possible (but very unlikely) bug in picking routers by
8789 bandwidth. Add a log message to confirm that it is in fact
8790 unlikely. Patch from lodger.
8791 - Backport a couple of memory leak fixes.
8792 - Backport miscellaneous cosmetic bugfixes.
8795 Changes in version 0.2.0.2-alpha - 2007-06-02
8796 o Major bugfixes on 0.2.0.1-alpha:
8797 - Fix an assertion failure related to servers without extra-info digests.
8798 Resolves bugs 441 and 442.
8800 o Minor features (directory):
8801 - Support "If-Modified-Since" when answering HTTP requests for
8802 directories, running-routers documents, and network-status documents.
8803 (There's no need to support it for router descriptors, since those
8804 are downloaded by descriptor digest.)
8806 o Minor build issues:
8807 - Clear up some MIPSPro compiler warnings.
8808 - When building from a tarball on a machine that happens to have SVK
8809 installed, report the micro-revision as whatever version existed
8810 in the tarball, not as "x".
8813 Changes in version 0.2.0.1-alpha - 2007-06-01
8814 This early development snapshot provides new features for people running
8815 Tor as both a client and a server (check out the new RelayBandwidth
8816 config options); lets Tor run as a DNS proxy; and generally moves us
8817 forward on a lot of fronts.
8819 o Major features, server usability:
8820 - New config options RelayBandwidthRate and RelayBandwidthBurst:
8821 a separate set of token buckets for relayed traffic. Right now
8822 relayed traffic is defined as answers to directory requests, and
8823 OR connections that don't have any local circuits on them.
8825 o Major features, client usability:
8826 - A client-side DNS proxy feature to replace the need for
8827 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
8828 for DNS requests on port 9999, use the Tor network to resolve them
8829 anonymously, and send the reply back like a regular DNS server.
8830 The code still only implements a subset of DNS.
8831 - Make PreferTunneledDirConns and TunnelDirConns work even when
8832 we have no cached directory info. This means Tor clients can now
8833 do all of their connections protected by TLS.
8835 o Major features, performance and efficiency:
8836 - Directory authorities accept and serve "extra info" documents for
8837 routers. These documents contain fields from router descriptors
8838 that aren't usually needed, and that use a lot of excess
8839 bandwidth. Once these fields are removed from router descriptors,
8840 the bandwidth savings should be about 60%. [Partially implements
8842 - Servers upload extra-info documents to any authority that accepts
8843 them. Authorities (and caches that have been configured to download
8844 extra-info documents) download them as needed. [Partially implements
8846 - Change the way that Tor buffers data that it is waiting to write.
8847 Instead of queueing data cells in an enormous ring buffer for each
8848 client->OR or OR->OR connection, we now queue cells on a separate
8849 queue for each circuit. This lets us use less slack memory, and
8850 will eventually let us be smarter about prioritizing different kinds
8852 - Use memory pools to allocate cells with better speed and memory
8853 efficiency, especially on platforms where malloc() is inefficient.
8854 - Stop reading on edge connections when their corresponding circuit
8855 buffers are full; start again as the circuits empty out.
8857 o Major features, other:
8858 - Add an HSAuthorityRecordStats option that hidden service authorities
8859 can use to track statistics of overall hidden service usage without
8860 logging information that would be very useful to an attacker.
8861 - Start work implementing multi-level keys for directory authorities:
8862 Add a standalone tool to generate key certificates. (Proposal 103.)
8865 - Directory authorities now call routers Stable if they have an
8866 uptime of at least 30 days, even if that's not the median uptime
8867 in the network. Implements proposal 107, suggested by Kevin Bauer
8870 o Minor fixes (resource management):
8871 - Count the number of open sockets separately from the number
8872 of active connection_t objects. This will let us avoid underusing
8873 our allocated connection limit.
8874 - We no longer use socket pairs to link an edge connection to an
8875 anonymous directory connection or a DirPort test connection.
8876 Instead, we track the link internally and transfer the data
8877 in-process. This saves two sockets per "linked" connection (at the
8878 client and at the server), and avoids the nasty Windows socketpair()
8880 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
8881 for every single inactive connection_t. Free items from the
8882 4k/16k-buffer free lists when they haven't been used for a while.
8884 o Minor features (build):
8885 - Make autoconf search for libevent, openssl, and zlib consistently.
8886 - Update deprecated macros in configure.in.
8887 - When warning about missing headers, tell the user to let us
8888 know if the compile succeeds anyway, so we can downgrade the
8890 - Include the current subversion revision as part of the version
8891 string: either fetch it directly if we're in an SVN checkout, do
8892 some magic to guess it if we're in an SVK checkout, or use
8893 the last-detected version if we're building from a .tar.gz.
8894 Use this version consistently in log messages.
8896 o Minor features (logging):
8897 - Always prepend "Bug: " to any log message about a bug.
8898 - Put a platform string (e.g. "Linux i686") in the startup log
8899 message, so when people paste just their logs, we know if it's
8900 OpenBSD or Windows or what.
8901 - When logging memory usage, break down memory used in buffers by
8904 o Minor features (directory system):
8905 - New config option V2AuthoritativeDirectory that all directory
8906 authorities should set. This will let future authorities choose
8907 not to serve V2 directory information.
8908 - Directory authorities allow multiple router descriptors and/or extra
8909 info documents to be uploaded in a single go. This will make
8910 implementing proposal 104 simpler.
8912 o Minor features (controller):
8913 - Add a new config option __DisablePredictedCircuits designed for
8914 use by the controller, when we don't want Tor to build any circuits
8916 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
8917 so we can exit from the middle of the circuit.
8918 - Implement "getinfo status/circuit-established".
8919 - Implement "getinfo status/version/..." so a controller can tell
8920 whether the current version is recommended, and whether any versions
8921 are good, and how many authorities agree. (Patch from shibz.)
8923 o Minor features (hidden services):
8924 - Allow multiple HiddenServicePort directives with the same virtual
8925 port; when they occur, the user is sent round-robin to one
8926 of the target ports chosen at random. Partially fixes bug 393 by
8927 adding limited ad-hoc round-robining.
8929 o Minor features (other):
8931 - Add a new AutomapHostsOnResolve option: when it is enabled, any
8932 resolve request for hosts matching a given pattern causes Tor to
8933 generate an internal virtual address mapping for that host. This
8934 allows DNSPort to work sensibly with hidden service users. By
8935 default, .exit and .onion addresses are remapped; the list of
8936 patterns can be reconfigured with AutomapHostsSuffixes.
8937 - Add an "-F" option to tor-resolve to force a resolve for a .onion
8938 address. Thanks to the AutomapHostsOnResolve option, this is no
8939 longer a completely silly thing to do.
8940 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
8941 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
8942 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
8943 minus 1 byte: the actual maximum declared bandwidth.
8946 - Removed support for the old binary "version 0" controller protocol.
8947 This has been deprecated since 0.1.1, and warnings have been issued
8948 since 0.1.2. When we encounter a v0 control message, we now send
8949 back an error and close the connection.
8950 - Remove the old "dns worker" server DNS code: it hasn't been default
8951 since 0.1.2.2-alpha, and all the servers seem to be using the new
8954 o Minor bugfixes (portability):
8955 - Even though Windows is equally happy with / and \ as path separators,
8956 try to use \ consistently on Windows and / consistently on Unix: it
8957 makes the log messages nicer.
8958 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
8959 - Read resolv.conf files correctly on platforms where read() returns
8960 partial results on small file reads.
8962 o Minor bugfixes (directory):
8963 - Correctly enforce that elements of directory objects do not appear
8964 more often than they are allowed to appear.
8965 - When we are reporting the DirServer line we just parsed, we were
8966 logging the second stanza of the key fingerprint, not the first.
8968 o Minor bugfixes (logging):
8969 - When we hit an EOF on a log (probably because we're shutting down),
8970 don't try to remove the log from the list: just mark it as
8971 unusable. (Bulletproofs against bug 222.)
8973 o Minor bugfixes (other):
8974 - In the exitlist script, only consider the most recently published
8975 server descriptor for each server. Also, when the user requests
8976 a list of servers that _reject_ connections to a given address,
8977 explicitly exclude the IPs that also have servers that accept
8978 connections to that address. (Resolves bug 405.)
8979 - Stop allowing hibernating servers to be "stable" or "fast".
8980 - On Windows, we were preventing other processes from reading
8981 cached-routers while Tor was running. (Reported by janbar)
8982 - Make the NodeFamilies config option work. (Reported by
8983 lodger -- it has never actually worked, even though we added it
8985 - Check return values from pthread_mutex functions.
8986 - Don't save non-general-purpose router descriptors to the disk cache,
8987 because we have no way of remembering what their purpose was when
8989 - Add even more asserts to hunt down bug 417.
8990 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
8991 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
8992 Add a log message to confirm that it is in fact unlikely.
8994 o Minor bugfixes (controller):
8995 - Make 'getinfo fingerprint' return a 551 error if we're not a
8996 server, so we match what the control spec claims we do. Reported
8998 - Fix a typo in an error message when extendcircuit fails that
8999 caused us to not follow the \r\n-based delimiter protocol. Reported
9002 o Code simplifications and refactoring:
9003 - Stop passing around circuit_t and crypt_path_t pointers that are
9004 implicit in other procedure arguments.
9005 - Drop the old code to choke directory connections when the
9006 corresponding OR connections got full: thanks to the cell queue
9007 feature, OR conns don't get full any more.
9008 - Make dns_resolve() handle attaching connections to circuits
9009 properly, so the caller doesn't have to.
9010 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
9011 - Keep the connection array as a dynamic smartlist_t, rather than as
9012 a fixed-sized array. This is important, as the number of connections
9013 is becoming increasingly decoupled from the number of sockets.
9016 Changes in version 0.1.2.14 - 2007-05-25
9017 Tor 0.1.2.14 changes the addresses of two directory authorities (this
9018 change especially affects those who serve or use hidden services),
9019 and fixes several other crash- and security-related bugs.
9021 o Directory authority changes:
9022 - Two directory authorities (moria1 and moria2) just moved to new
9023 IP addresses. This change will particularly affect those who serve
9024 or use hidden services.
9026 o Major bugfixes (crashes):
9027 - If a directory server runs out of space in the connection table
9028 as it's processing a begin_dir request, it will free the exit stream
9029 but leave it attached to the circuit, leading to unpredictable
9030 behavior. (Reported by seeess, fixes bug 425.)
9031 - Fix a bug in dirserv_remove_invalid() that would cause authorities
9032 to corrupt memory under some really unlikely scenarios.
9033 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
9034 - Avoid segfaults when reading from mmaped descriptor file. (Reported
9037 o Major bugfixes (security):
9038 - When choosing an entry guard for a circuit, avoid using guards
9039 that are in the same family as the chosen exit -- not just guards
9040 that are exactly the chosen exit. (Reported by lodger.)
9042 o Major bugfixes (resource management):
9043 - If a directory authority is down, skip it when deciding where to get
9044 networkstatus objects or descriptors. Otherwise we keep asking
9045 every 10 seconds forever. Fixes bug 384.
9046 - Count it as a failure if we fetch a valid network-status but we
9047 don't want to keep it. Otherwise we'll keep fetching it and keep
9048 not wanting to keep it. Fixes part of bug 422.
9049 - If all of our dirservers have given us bad or no networkstatuses
9050 lately, then stop hammering them once per minute even when we
9051 think they're failed. Fixes another part of bug 422.
9054 - Actually set the purpose correctly for descriptors inserted with
9056 - When we have k non-v2 authorities in our DirServer config,
9057 we ignored the last k authorities in the list when updating our
9059 - Correctly back-off from requesting router descriptors that we are
9060 having a hard time downloading.
9061 - Read resolv.conf files correctly on platforms where read() returns
9062 partial results on small file reads.
9063 - Don't rebuild the entire router store every time we get 32K of
9064 routers: rebuild it when the journal gets very large, or when
9065 the gaps in the store get very large.
9068 - When routers publish SVN revisions in their router descriptors,
9069 authorities now include those versions correctly in networkstatus
9071 - Warn when using a version of libevent before 1.3b to run a server on
9072 OSX or BSD: these versions interact badly with userspace threads.
9075 Changes in version 0.1.2.13 - 2007-04-24
9076 This release features some major anonymity fixes, such as safer path
9077 selection; better client performance; faster bootstrapping, better
9078 address detection, and better DNS support for servers; write limiting as
9079 well as read limiting to make servers easier to run; and a huge pile of
9080 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
9082 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
9083 of the Freenode IRC network, remembering his patience and vision for
9084 free speech on the Internet.
9087 - Fix a memory leak when we ask for "all" networkstatuses and we
9088 get one we don't recognize.
9089 - Add more asserts to hunt down bug 417.
9090 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
9093 Changes in version 0.1.2.12-rc - 2007-03-16
9095 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
9096 directory information requested inside Tor connections (i.e. via
9097 begin_dir cells). It only triggered when the same connection was
9098 serving other data at the same time. Reported by seeess.
9101 - When creating a circuit via the controller, send a 'launched'
9102 event when we're done, so we follow the spec better.
9105 Changes in version 0.1.2.11-rc - 2007-03-15
9106 o Minor bugfixes (controller), reported by daejees:
9107 - Correct the control spec to match how the code actually responds
9108 to 'getinfo addr-mappings/*'.
9109 - The control spec described a GUARDS event, but the code
9110 implemented a GUARD event. Standardize on GUARD, but let people
9114 Changes in version 0.1.2.10-rc - 2007-03-07
9115 o Major bugfixes (Windows):
9116 - Do not load the NT services library functions (which may not exist)
9117 just to detect if we're a service trying to shut down. Now we run
9118 on Win98 and friends again.
9120 o Minor bugfixes (other):
9121 - Clarify a couple of log messages.
9122 - Fix a misleading socks5 error number.
9125 Changes in version 0.1.2.9-rc - 2007-03-02
9126 o Major bugfixes (Windows):
9127 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
9128 of the usual GCC "%llu". This prevents a bug when saving 64-bit
9129 int configuration values: the high-order 32 bits would get
9130 truncated. In particular, we were being bitten by the default
9131 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
9132 and maybe also bug 397.)
9134 o Minor bugfixes (performance):
9135 - Use OpenSSL's AES implementation on platforms where it's faster.
9136 This could save us as much as 10% CPU usage.
9138 o Minor bugfixes (server):
9139 - Do not rotate onion key immediately after setting it for the first
9142 o Minor bugfixes (directory authorities):
9143 - Stop calling servers that have been hibernating for a long time
9144 "stable". Also, stop letting hibernating or obsolete servers affect
9145 uptime and bandwidth cutoffs.
9146 - Stop listing hibernating servers in the v1 directory.
9148 o Minor bugfixes (hidden services):
9149 - Upload hidden service descriptors slightly less often, to reduce
9150 load on authorities.
9152 o Minor bugfixes (other):
9153 - Fix an assert that could trigger if a controller quickly set then
9154 cleared EntryNodes. Bug found by Udo van den Heuvel.
9155 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
9157 - Fix a potential race condition in the rpm installer. Found by
9159 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
9160 of 2 as indicating that the server is completely bad; it sometimes
9161 means that the server is just bad for the request in question. (may fix
9162 the last of bug 326.)
9163 - Disable encrypted directory connections when we don't have a server
9164 descriptor for the destination. We'll get this working again in
9168 Changes in version 0.1.2.8-beta - 2007-02-26
9169 o Major bugfixes (crashes):
9170 - Stop crashing when the controller asks us to resetconf more than
9171 one config option at once. (Vidalia 0.0.11 does this.)
9172 - Fix a crash that happened on Win98 when we're given command-line
9173 arguments: don't try to load NT service functions from advapi32.dll
9174 except when we need them. (Bug introduced in 0.1.2.7-alpha;
9176 - Fix a longstanding obscure crash bug that could occur when
9177 we run out of DNS worker processes. (Resolves bug 390.)
9179 o Major bugfixes (hidden services):
9180 - Correctly detect whether hidden service descriptor downloads are
9181 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
9183 o Major bugfixes (accounting):
9184 - When we start during an accounting interval before it's time to wake
9185 up, remember to wake up at the correct time. (May fix bug 342.)
9187 o Minor bugfixes (controller):
9188 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
9189 clear the corresponding on_circuit variable, and remember later
9190 that we don't need to send a redundant CLOSED event. Resolves part
9192 - Report events where a resolve succeeded or where we got a socks
9193 protocol error correctly, rather than calling both of them
9195 - Change reported stream target addresses to IP consistently when
9196 we finally get the IP from an exit node.
9197 - Send log messages to the controller even if they happen to be very
9200 o Minor bugfixes (other):
9201 - Display correct results when reporting which versions are
9202 recommended, and how recommended they are. (Resolves bug 383.)
9203 - Improve our estimates for directory bandwidth to be less random:
9204 guess that an unrecognized directory will have the average bandwidth
9205 from all known directories, not that it will have the average
9206 bandwidth from those directories earlier than it on the list.
9207 - If we start a server with ClientOnly 1, then set ClientOnly to 0
9208 and hup, stop triggering an assert based on an empty onion_key.
9209 - On platforms with no working mmap() equivalent, don't warn the
9210 user when cached-routers doesn't exist.
9211 - Warn the user when mmap() [or its equivalent] fails for some reason
9212 other than file-not-found.
9213 - Don't warn the user when cached-routers.new doesn't exist: that's
9214 perfectly fine when starting up for the first time.
9215 - When EntryNodes are configured, rebuild the guard list to contain,
9216 in order: the EntryNodes that were guards before; the rest of the
9217 EntryNodes; the nodes that were guards before.
9218 - Mask out all signals in sub-threads; only the libevent signal
9219 handler should be processing them. This should prevent some crashes
9220 on some machines using pthreads. (Patch from coderman.)
9221 - Fix switched arguments on memset in the implementation of
9222 tor_munmap() for systems with no mmap() call.
9223 - When Tor receives a router descriptor that it asked for, but
9224 no longer wants (because it has received fresh networkstatuses
9225 in the meantime), do not warn the user. Cache the descriptor if
9226 we're a cache; drop it if we aren't.
9227 - Make earlier entry guards _really_ get retried when the network
9229 - On a malformed DNS reply, always give an error to the corresponding
9231 - Build with recent libevents on platforms that do not define the
9232 nonstandard types "u_int8_t" and friends.
9234 o Minor features (controller):
9235 - Warn the user when an application uses the obsolete binary v0
9236 control protocol. We're planning to remove support for it during
9237 the next development series, so it's good to give people some
9239 - Add STREAM_BW events to report per-entry-stream bandwidth
9240 use. (Patch from Robert Hogan.)
9241 - Rate-limit SIGNEWNYM signals in response to controllers that
9242 impolitely generate them for every single stream. (Patch from
9243 mwenge; closes bug 394.)
9244 - Make REMAP stream events have a SOURCE (cache or exit), and
9245 make them generated in every case where we get a successful
9246 connected or resolved cell.
9248 o Minor bugfixes (performance):
9249 - Call router_have_min_dir_info half as often. (This is showing up in
9250 some profiles, but not others.)
9251 - When using GCC, make log_debug never get called at all, and its
9252 arguments never get evaluated, when no debug logs are configured.
9253 (This is showing up in some profiles, but not others.)
9256 - Remove some never-implemented options. Mark PathlenCoinWeight as
9258 - Implement proposal 106: Stop requiring clients to have well-formed
9259 certificates; stop checking nicknames in certificates. (Clients
9260 have certificates so that they can look like Tor servers, but in
9261 the future we might want to allow them to look like regular TLS
9262 clients instead. Nicknames in certificates serve no purpose other
9263 than making our protocol easier to recognize on the wire.)
9264 - Revise messages on handshake failure again to be even more clear about
9265 which are incoming connections and which are outgoing.
9266 - Discard any v1 directory info that's over 1 month old (for
9267 directories) or over 1 week old (for running-routers lists).
9268 - Do not warn when individual nodes in the configuration's EntryNodes,
9269 ExitNodes, etc are down: warn only when all possible nodes
9270 are down. (Fixes bug 348.)
9271 - Always remove expired routers and networkstatus docs before checking
9272 whether we have enough information to build circuits. (Fixes
9274 - Put a lower-bound on MaxAdvertisedBandwidth.
9277 Changes in version 0.1.2.7-alpha - 2007-02-06
9278 o Major bugfixes (rate limiting):
9279 - Servers decline directory requests much more aggressively when
9280 they're low on bandwidth. Otherwise they end up queueing more and
9281 more directory responses, which can't be good for latency.
9282 - But never refuse directory requests from local addresses.
9283 - Fix a memory leak when sending a 503 response for a networkstatus
9285 - Be willing to read or write on local connections (e.g. controller
9286 connections) even when the global rate limiting buckets are empty.
9287 - If our system clock jumps back in time, don't publish a negative
9288 uptime in the descriptor. Also, don't let the global rate limiting
9289 buckets go absurdly negative.
9290 - Flush local controller connection buffers periodically as we're
9291 writing to them, so we avoid queueing 4+ megabytes of data before
9294 o Major bugfixes (NT services):
9295 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
9296 command-line flag so that admins can override the default by saying
9297 "tor --service install --user "SomeUser"". This will not affect
9298 existing installed services. Also, warn the user that the service
9299 will look for its configuration file in the service user's
9300 %appdata% directory. (We can't do the 'hardwire the user's appdata
9301 directory' trick any more, since we may not have read access to that
9304 o Major bugfixes (other):
9305 - Previously, we would cache up to 16 old networkstatus documents
9306 indefinitely, if they came from nontrusted authorities. Now we
9307 discard them if they are more than 10 days old.
9308 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
9310 - Detect and reject malformed DNS responses containing circular
9312 - If exits are rare enough that we're not marking exits as guards,
9313 ignore exit bandwidth when we're deciding the required bandwidth
9315 - When we're handling a directory connection tunneled over Tor,
9316 don't fill up internal memory buffers with all the data we want
9317 to tunnel; instead, only add it if the OR connection that will
9318 eventually receive it has some room for it. (This can lead to
9319 slowdowns in tunneled dir connections; a better solution will have
9322 o Minor bugfixes (dns):
9323 - Add some defensive programming to eventdns.c in an attempt to catch
9324 possible memory-stomping bugs.
9325 - Detect and reject DNS replies containing IPv4 or IPv6 records with
9326 an incorrect number of bytes. (Previously, we would ignore the
9328 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
9329 in the correct order, and doesn't crash.
9330 - Free memory held in recently-completed DNS lookup attempts on exit.
9331 This was not a memory leak, but may have been hiding memory leaks.
9332 - Handle TTL values correctly on reverse DNS lookups.
9333 - Treat failure to parse resolv.conf as an error.
9335 o Minor bugfixes (other):
9336 - Fix crash with "tor --list-fingerprint" (reported by seeess).
9337 - When computing clock skew from directory HTTP headers, consider what
9338 time it was when we finished asking for the directory, not what
9340 - Expire socks connections if they spend too long waiting for the
9341 handshake to finish. Previously we would let them sit around for
9342 days, if the connecting application didn't close them either.
9343 - And if the socks handshake hasn't started, don't send a
9344 "DNS resolve socks failed" handshake reply; just close it.
9345 - Stop using C functions that OpenBSD's linker doesn't like.
9346 - Don't launch requests for descriptors unless we have networkstatuses
9347 from at least half of the authorities. This delays the first
9348 download slightly under pathological circumstances, but can prevent
9349 us from downloading a bunch of descriptors we don't need.
9350 - Do not log IPs with TLS failures for incoming TLS
9351 connections. (Fixes bug 382.)
9352 - If the user asks to use invalid exit nodes, be willing to use
9354 - Stop using the reserved ac_cv namespace in our configure script.
9355 - Call stat() slightly less often; use fstat() when possible.
9356 - Refactor the way we handle pending circuits when an OR connection
9357 completes or fails, in an attempt to fix a rare crash bug.
9358 - Only rewrite a conn's address based on X-Forwarded-For: headers
9359 if it's a parseable public IP address; and stop adding extra quotes
9360 to the resulting address.
9363 - Weight directory requests by advertised bandwidth. Now we can
9364 let servers enable write limiting but still allow most clients to
9365 succeed at their directory requests. (We still ignore weights when
9366 choosing a directory authority; I hope this is a feature.)
9369 - Create a new file ReleaseNotes which was the old ChangeLog. The
9370 new ChangeLog file now includes the summaries for all development
9372 - Check for addresses with invalid characters at the exit as well
9373 as at the client, and warn less verbosely when they fail. You can
9374 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
9375 - Adapt a patch from goodell to let the contrib/exitlist script
9376 take arguments rather than require direct editing.
9377 - Inform the server operator when we decide not to advertise a
9378 DirPort due to AccountingMax enabled or a low BandwidthRate. It
9379 was confusing Zax, so now we're hopefully more helpful.
9380 - Bring us one step closer to being able to establish an encrypted
9381 directory tunnel without knowing a descriptor first. Still not
9382 ready yet. As part of the change, now assume we can use a
9383 create_fast cell if we don't know anything about a router.
9384 - Allow exit nodes to use nameservers running on ports other than 53.
9385 - Servers now cache reverse DNS replies.
9386 - Add an --ignore-missing-torrc command-line option so that we can
9387 get the "use sensible defaults if the configuration file doesn't
9388 exist" behavior even when specifying a torrc location on the command
9391 o Minor features (controller):
9392 - Track reasons for OR connection failure; make these reasons
9393 available via the controller interface. (Patch from Mike Perry.)
9394 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
9395 can learn when clients are sending malformed hostnames to Tor.
9396 - Clean up documentation for controller status events.
9397 - Add a REMAP status to stream events to note that a stream's
9398 address has changed because of a cached address or a MapAddress
9402 Changes in version 0.1.2.6-alpha - 2007-01-09
9404 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
9405 connection handles more than 4 gigs in either direction, we crash.
9406 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
9407 advertised exit node, somebody might try to exit from us when
9408 we're bootstrapping and before we've built our descriptor yet.
9409 Refuse the connection rather than crashing.
9412 - Warn if we (as a server) find that we've resolved an address that we
9413 weren't planning to resolve.
9414 - Warn that using select() on any libevent version before 1.1 will be
9415 unnecessarily slow (even for select()).
9416 - Flush ERR-level controller status events just like we currently
9417 flush ERR-level log events, so that a Tor shutdown doesn't prevent
9418 the controller from learning about current events.
9420 o Minor features (more controller status events):
9421 - Implement EXTERNAL_ADDRESS server status event so controllers can
9422 learn when our address changes.
9423 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
9424 can learn when directories reject our descriptor.
9425 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
9426 can learn when a client application is speaking a non-socks protocol
9428 - Implement DANGEROUS_SOCKS client status event so controllers
9429 can learn when a client application is leaking DNS addresses.
9430 - Implement BUG general status event so controllers can learn when
9431 Tor is unhappy about its internal invariants.
9432 - Implement CLOCK_SKEW general status event so controllers can learn
9433 when Tor thinks the system clock is set incorrectly.
9434 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
9435 server status events so controllers can learn when their descriptors
9436 are accepted by a directory.
9437 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
9438 server status events so controllers can learn about Tor's progress in
9439 deciding whether it's reachable from the outside.
9440 - Implement BAD_LIBEVENT general status event so controllers can learn
9441 when we have a version/method combination in libevent that needs to
9443 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
9444 and DNS_USELESS server status events so controllers can learn
9445 about changes to DNS server status.
9447 o Minor features (directory):
9448 - Authorities no longer recommend exits as guards if this would shift
9449 too much load to the exit nodes.
9452 Changes in version 0.1.2.5-alpha - 2007-01-06
9454 - Enable write limiting as well as read limiting. Now we sacrifice
9455 capacity if we're pushing out lots of directory traffic, rather
9456 than overrunning the user's intended bandwidth limits.
9457 - Include TLS overhead when counting bandwidth usage; previously, we
9458 would count only the bytes sent over TLS, but not the bytes used
9460 - Support running the Tor service with a torrc not in the same
9461 directory as tor.exe and default to using the torrc located in
9462 the %appdata%\Tor\ of the user who installed the service. Patch
9464 - Servers now check for the case when common DNS requests are going to
9465 wildcarded addresses (i.e. all getting the same answer), and change
9466 their exit policy to reject *:* if it's happening.
9467 - Implement BEGIN_DIR cells, so we can connect to the directory
9468 server via TLS to do encrypted directory requests rather than
9469 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
9470 config options if you like.
9472 o Minor features (config and docs):
9473 - Start using the state file to store bandwidth accounting data:
9474 the bw_accounting file is now obsolete. We'll keep generating it
9475 for a while for people who are still using 0.1.2.4-alpha.
9476 - Try to batch changes to the state file so that we do as few
9477 disk writes as possible while still storing important things in
9479 - The state file and the bw_accounting file get saved less often when
9480 the AvoidDiskWrites config option is set.
9481 - Make PIDFile work on Windows (untested).
9482 - Add internal descriptions for a bunch of configuration options:
9483 accessible via controller interface and in comments in saved
9485 - Reject *:563 (NNTPS) in the default exit policy. We already reject
9486 NNTP by default, so this seems like a sensible addition.
9487 - Clients now reject hostnames with invalid characters. This should
9488 avoid some inadvertent info leaks. Add an option
9489 AllowNonRFC953Hostnames to disable this behavior, in case somebody
9490 is running a private network with hosts called @, !, and #.
9491 - Add a maintainer script to tell us which options are missing
9492 documentation: "make check-docs".
9493 - Add a new address-spec.txt document to describe our special-case
9494 addresses: .exit, .onion, and .noconnnect.
9496 o Minor features (DNS):
9497 - Ongoing work on eventdns infrastructure: now it has dns server
9498 and ipv6 support. One day Tor will make use of it.
9499 - Add client-side caching for reverse DNS lookups.
9500 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
9501 - When we change nameservers or IP addresses, reset and re-launch
9502 our tests for DNS hijacking.
9504 o Minor features (directory):
9505 - Authorities now specify server versions in networkstatus. This adds
9506 about 2% to the size of compressed networkstatus docs, and allows
9507 clients to tell which servers support BEGIN_DIR and which don't.
9508 The implementation is forward-compatible with a proposed future
9509 protocol version scheme not tied to Tor versions.
9510 - DirServer configuration lines now have an orport= option so
9511 clients can open encrypted tunnels to the authorities without
9512 having downloaded their descriptors yet. Enabled for moria1,
9513 moria2, tor26, and lefkada now in the default configuration.
9514 - Directory servers are more willing to send a 503 "busy" if they
9515 are near their write limit, especially for v1 directory requests.
9516 Now they can use their limited bandwidth for actual Tor traffic.
9517 - Clients track responses with status 503 from dirservers. After a
9518 dirserver has given us a 503, we try not to use it until an hour has
9519 gone by, or until we have no dirservers that haven't given us a 503.
9520 - When we get a 503 from a directory, and we're not a server, we don't
9521 count the failure against the total number of failures allowed
9522 for the thing we're trying to download.
9523 - Report X-Your-Address-Is correctly from tunneled directory
9524 connections; don't report X-Your-Address-Is when it's an internal
9525 address; and never believe reported remote addresses when they're
9527 - Protect against an unlikely DoS attack on directory servers.
9528 - Add a BadDirectory flag to network status docs so that authorities
9529 can (eventually) tell clients about caches they believe to be
9532 o Minor features (controller):
9533 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
9534 - Reimplement GETINFO so that info/names stays in sync with the
9536 - Implement "GETINFO fingerprint".
9537 - Implement "SETEVENTS GUARD" so controllers can get updates on
9538 entry guard status as it changes.
9540 o Minor features (clean up obsolete pieces):
9541 - Remove some options that have been deprecated since at least
9542 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
9543 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
9545 - We no longer look for identity and onion keys in "identity.key" and
9546 "onion.key" -- these were replaced by secret_id_key and
9547 secret_onion_key in 0.0.8pre1.
9548 - We no longer require unrecognized directory entries to be
9551 o Major bugfixes (security):
9552 - Stop sending the HttpProxyAuthenticator string to directory
9553 servers when directory connections are tunnelled through Tor.
9554 - Clients no longer store bandwidth history in the state file.
9555 - Do not log introduction points for hidden services if SafeLogging
9557 - When generating bandwidth history, round down to the nearest
9558 1k. When storing accounting data, round up to the nearest 1k.
9559 - When we're running as a server, remember when we last rotated onion
9560 keys, so that we will rotate keys once they're a week old even if
9561 we never stay up for a week ourselves.
9563 o Major bugfixes (other):
9564 - Fix a longstanding bug in eventdns that prevented the count of
9565 timed-out resolves from ever being reset. This bug caused us to
9566 give up on a nameserver the third time it timed out, and try it
9567 10 seconds later... and to give up on it every time it timed out
9569 - Take out the '5 second' timeout from the connection retry
9570 schedule. Now the first connect attempt will wait a full 10
9571 seconds before switching to a new circuit. Perhaps this will help
9572 a lot. Based on observations from Mike Perry.
9573 - Fix a bug on the Windows implementation of tor_mmap_file() that
9574 would prevent the cached-routers file from ever loading. Reported
9578 - Fix an assert failure when a directory authority sets
9579 AuthDirRejectUnlisted and then receives a descriptor from an
9580 unlisted router. Reported by seeess.
9581 - Avoid a double-free when parsing malformed DirServer lines.
9582 - Fix a bug when a BSD-style PF socket is first used. Patch from
9584 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
9585 to resolve an address at a given exit node even when they ask for
9587 - Servers no longer ever list themselves in their "family" line,
9588 even if configured to do so. This makes it easier to configure
9589 family lists conveniently.
9590 - When running as a server, don't fall back to 127.0.0.1 when no
9591 nameservers are configured in /etc/resolv.conf; instead, make the
9592 user fix resolv.conf or specify nameservers explicitly. (Resolves
9594 - Stop accepting certain malformed ports in configured exit policies.
9595 - Don't re-write the fingerprint file every restart, unless it has
9597 - Stop warning when a single nameserver fails: only warn when _all_ of
9598 our nameservers have failed. Also, when we only have one nameserver,
9599 raise the threshold for deciding that the nameserver is dead.
9600 - Directory authorities now only decide that routers are reachable
9601 if their identity keys are as expected.
9602 - When the user uses bad syntax in the Log config line, stop
9603 suggesting other bad syntax as a replacement.
9604 - Correctly detect ipv6 DNS capability on OpenBSD.
9606 o Minor bugfixes (controller):
9607 - Report the circuit number correctly in STREAM CLOSED events. Bug
9608 reported by Mike Perry.
9609 - Do not report bizarre values for results of accounting GETINFOs
9610 when the last second's write or read exceeds the allotted bandwidth.
9611 - Report "unrecognized key" rather than an empty string when the
9612 controller tries to fetch a networkstatus that doesn't exist.
9615 Changes in version 0.1.1.26 - 2006-12-14
9616 o Security bugfixes:
9617 - Stop sending the HttpProxyAuthenticator string to directory
9618 servers when directory connections are tunnelled through Tor.
9619 - Clients no longer store bandwidth history in the state file.
9620 - Do not log introduction points for hidden services if SafeLogging
9624 - Fix an assert failure when a directory authority sets
9625 AuthDirRejectUnlisted and then receives a descriptor from an
9626 unlisted router (reported by seeess).
9629 Changes in version 0.1.2.4-alpha - 2006-12-03
9631 - Add support for using natd; this allows FreeBSDs earlier than
9632 5.1.2 to have ipfw send connections through Tor without using
9633 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
9636 - Make all connections to addresses of the form ".noconnect"
9637 immediately get closed. This lets application/controller combos
9638 successfully test whether they're talking to the same Tor by
9639 watching for STREAM events.
9640 - Make cross.sh cross-compilation script work even when autogen.sh
9641 hasn't been run. (Patch from Michael Mohr.)
9642 - Statistics dumped by -USR2 now include a breakdown of public key
9643 operations, for profiling.
9646 - Fix a major leak when directory authorities parse their
9647 approved-routers list, a minor memory leak when we fail to pick
9648 an exit node, and a few rare leaks on errors.
9649 - Handle TransPort connections even when the server sends data before
9650 the client sends data. Previously, the connection would just hang
9651 until the client sent data. (Patch from tup based on patch from
9653 - Avoid assert failure when our cached-routers file is empty on
9657 - Don't log spurious warnings when we see a circuit close reason we
9658 don't recognize; it's probably just from a newer version of Tor.
9659 - Have directory authorities allow larger amounts of drift in uptime
9660 without replacing the server descriptor: previously, a server that
9661 restarted every 30 minutes could have 48 "interesting" descriptors
9663 - Start linking to the Tor specification and Tor reference manual
9664 correctly in the Windows installer.
9665 - Add Vidalia to the OS X uninstaller script, so when we uninstall
9666 Tor/Privoxy we also uninstall Vidalia.
9667 - Resume building on Irix64, and fix a lot of warnings from its
9669 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
9670 when we're running as a client.
9673 Changes in version 0.1.1.25 - 2006-11-04
9675 - When a client asks us to resolve (rather than connect to)
9676 an address, and we have a cached answer, give them the cached
9677 answer. Previously, we would give them no answer at all.
9678 - We were building exactly the wrong circuits when we predict
9679 hidden service requirements, meaning Tor would have to build all
9680 its circuits on demand.
9681 - If none of our live entry guards have a high uptime, but we
9682 require a guard with a high uptime, try adding a new guard before
9683 we give up on the requirement. This patch should make long-lived
9684 connections more stable on average.
9685 - When testing reachability of our DirPort, don't launch new
9686 tests when there's already one in progress -- unreachable
9687 servers were stacking up dozens of testing streams.
9689 o Security bugfixes:
9690 - When the user sends a NEWNYM signal, clear the client-side DNS
9691 cache too. Otherwise we continue to act on previous information.
9694 - Avoid a memory corruption bug when creating a hash table for
9696 - Avoid possibility of controller-triggered crash when misusing
9697 certain commands from a v0 controller on platforms that do not
9698 handle printf("%s",NULL) gracefully.
9699 - Avoid infinite loop on unexpected controller input.
9700 - Don't log spurious warnings when we see a circuit close reason we
9701 don't recognize; it's probably just from a newer version of Tor.
9702 - Add Vidalia to the OS X uninstaller script, so when we uninstall
9703 Tor/Privoxy we also uninstall Vidalia.
9706 Changes in version 0.1.2.3-alpha - 2006-10-29
9708 - Prepare for servers to publish descriptors less often: never
9709 discard a descriptor simply for being too old until either it is
9710 recommended by no authorities, or until we get a better one for
9711 the same router. Make caches consider retaining old recommended
9712 routers for even longer.
9713 - If most authorities set a BadExit flag for a server, clients
9714 don't think of it as a general-purpose exit. Clients only consider
9715 authorities that advertise themselves as listing bad exits.
9716 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
9717 headers for content, so that we can work better in the presence of
9718 caching HTTP proxies.
9719 - Allow authorities to list nodes as bad exits by fingerprint or by
9722 o Minor features, controller:
9723 - Add a REASON field to CIRC events; for backward compatibility, this
9724 field is sent only to controllers that have enabled the extended
9725 event format. Also, add additional reason codes to explain why
9726 a given circuit has been destroyed or truncated. (Patches from
9728 - Add a REMOTE_REASON field to extended CIRC events to tell the
9729 controller about why a remote OR told us to close a circuit.
9730 - Stream events also now have REASON and REMOTE_REASON fields,
9731 working much like those for circuit events.
9732 - There's now a GETINFO ns/... field so that controllers can ask Tor
9733 about the current status of a router.
9734 - A new event type "NS" to inform a controller when our opinion of
9735 a router's status has changed.
9736 - Add a GETINFO events/names and GETINFO features/names so controllers
9737 can tell which events and features are supported.
9738 - A new CLEARDNSCACHE signal to allow controllers to clear the
9739 client-side DNS cache without expiring circuits.
9741 o Security bugfixes:
9742 - When the user sends a NEWNYM signal, clear the client-side DNS
9743 cache too. Otherwise we continue to act on previous information.
9746 - Avoid sending junk to controllers or segfaulting when a controller
9747 uses EVENT_NEW_DESC with verbose nicknames.
9748 - Stop triggering asserts if the controller tries to extend hidden
9749 service circuits (reported by mwenge).
9750 - Avoid infinite loop on unexpected controller input.
9751 - When the controller does a "GETINFO network-status", tell it
9752 about even those routers whose descriptors are very old, and use
9753 long nicknames where appropriate.
9754 - Change NT service functions to be loaded on demand. This lets us
9755 build with MinGW without breaking Tor for Windows 98 users.
9756 - Do DirPort reachability tests less often, since a single test
9757 chews through many circuits before giving up.
9758 - In the hidden service example in torrc.sample, stop recommending
9759 esoteric and discouraged hidden service options.
9760 - When stopping an NT service, wait up to 10 sec for it to actually
9761 stop. Patch from Matt Edman; resolves bug 295.
9762 - Fix handling of verbose nicknames with ORCONN controller events:
9763 make them show up exactly when requested, rather than exactly when
9765 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
9766 printing a duplicate "$" in the keys we send (reported by mwenge).
9767 - Correctly set maximum connection limit on Cygwin. (This time
9769 - Try to detect Windows correctly when cross-compiling.
9770 - Detect the size of the routers file correctly even if it is
9771 corrupted (on systems without mmap) or not page-aligned (on systems
9772 with mmap). This bug was harmless.
9773 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
9774 to open a stream fails; now we do in more cases. This should
9775 make clients able to find a good exit faster in some cases, since
9776 unhandleable requests will now get an error rather than timing out.
9777 - Resolve two memory leaks when rebuilding the on-disk router cache
9778 (reported by fookoowa).
9779 - Clean up minor code warnings suggested by the MIPSpro C compiler,
9780 and reported by some Centos users.
9781 - Controller signals now work on non-Unix platforms that don't define
9782 SIGUSR1 and SIGUSR2 the way we expect.
9783 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
9784 values before failing, and always enables eventdns.
9785 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
9786 Try to fix this in configure.in by checking for most functions
9787 before we check for libevent.
9790 Changes in version 0.1.2.2-alpha - 2006-10-07
9792 - Make our async eventdns library on-by-default for Tor servers,
9793 and plan to deprecate the separate dnsworker threads.
9794 - Add server-side support for "reverse" DNS lookups (using PTR
9795 records so clients can determine the canonical hostname for a given
9796 IPv4 address). Only supported by servers using eventdns; servers
9797 now announce in their descriptors whether they support eventdns.
9798 - Specify and implement client-side SOCKS5 interface for reverse DNS
9799 lookups (see doc/socks-extensions.txt).
9800 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
9801 connect to directory servers through Tor. Previously, clients needed
9802 to find Tor exits to make private connections to directory servers.
9803 - Avoid choosing Exit nodes for entry or middle hops when the
9804 total bandwidth available from non-Exit nodes is much higher than
9805 the total bandwidth available from Exit nodes.
9806 - Workaround for name servers (like Earthlink's) that hijack failing
9807 DNS requests and replace the no-such-server answer with a "helpful"
9808 redirect to an advertising-driven search portal. Also work around
9809 DNS hijackers who "helpfully" decline to hijack known-invalid
9810 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
9811 lets you turn it off.
9812 - Send out a burst of long-range padding cells once we've established
9813 that we're reachable. Spread them over 4 circuits, so hopefully
9814 a few will be fast. This exercises our bandwidth and bootstraps
9815 us into the directory more quickly.
9817 o New/improved config options:
9818 - Add new config option "ResolvConf" to let the server operator
9819 choose an alternate resolve.conf file when using eventdns.
9820 - Add an "EnforceDistinctSubnets" option to control our "exclude
9821 servers on the same /16" behavior. It's still on by default; this
9822 is mostly for people who want to operate private test networks with
9823 all the machines on the same subnet.
9824 - If one of our entry guards is on the ExcludeNodes list, or the
9825 directory authorities don't think it's a good guard, treat it as
9826 if it were unlisted: stop using it as a guard, and throw it off
9827 the guards list if it stays that way for a long time.
9828 - Allow directory authorities to be marked separately as authorities
9829 for the v1 directory protocol, the v2 directory protocol, and
9830 as hidden service directories, to make it easier to retire old
9831 authorities. V1 authorities should set "HSAuthoritativeDir 1"
9832 to continue being hidden service authorities too.
9833 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
9835 o Minor features, controller:
9836 - Fix CIRC controller events so that controllers can learn the
9837 identity digests of non-Named servers used in circuit paths.
9838 - Let controllers ask for more useful identifiers for servers. Instead
9839 of learning identity digests for un-Named servers and nicknames
9840 for Named servers, the new identifiers include digest, nickname,
9841 and indication of Named status. Off by default; see control-spec.txt
9842 for more information.
9843 - Add a "getinfo address" controller command so it can display Tor's
9844 best guess to the user.
9845 - New controller event to alert the controller when our server
9846 descriptor has changed.
9847 - Give more meaningful errors on controller authentication failure.
9849 o Minor features, other:
9850 - When asked to resolve a hostname, don't use non-exit servers unless
9851 requested to do so. This allows servers with broken DNS to be
9852 useful to the network.
9853 - Divide eventdns log messages into warn and info messages.
9854 - Reserve the nickname "Unnamed" for routers that can't pick
9855 a hostname: any router can call itself Unnamed; directory
9856 authorities will never allocate Unnamed to any particular router;
9857 clients won't believe that any router is the canonical Unnamed.
9858 - Only include function names in log messages for info/debug messages.
9859 For notice/warn/err, the content of the message should be clear on
9860 its own, and printing the function name only confuses users.
9861 - Avoid some false positives during reachability testing: don't try
9862 to test via a server that's on the same /24 as us.
9863 - If we fail to build a circuit to an intended enclave, and it's
9864 not mandatory that we use that enclave, stop wanting it.
9865 - When eventdns is enabled, allow multithreaded builds on NetBSD and
9866 OpenBSD. (We had previously disabled threads on these platforms
9867 because they didn't have working thread-safe resolver functions.)
9869 o Major bugfixes, anonymity/security:
9870 - If a client asked for a server by name, and there's a named server
9871 in our network-status but we don't have its descriptor yet, we
9872 could return an unnamed server instead.
9873 - Fix NetBSD bug that could allow someone to force uninitialized RAM
9874 to be sent to a server's DNS resolver. This only affects NetBSD
9875 and other platforms that do not bounds-check tolower().
9876 - Reject (most) attempts to use Tor circuits with length one. (If
9877 many people start using Tor as a one-hop proxy, exit nodes become
9878 a more attractive target for compromise.)
9879 - Just because your DirPort is open doesn't mean people should be
9880 able to remotely teach you about hidden service descriptors. Now
9881 only accept rendezvous posts if you've got HSAuthoritativeDir set.
9883 o Major bugfixes, other:
9884 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
9885 - When a client asks the server to resolve (not connect to)
9886 an address, and it has a cached answer, give them the cached answer.
9887 Previously, the server would give them no answer at all.
9888 - Allow really slow clients to not hang up five minutes into their
9889 directory downloads (suggested by Adam J. Richter).
9890 - We were building exactly the wrong circuits when we anticipated
9891 hidden service requirements, meaning Tor would have to build all
9892 its circuits on demand.
9893 - Avoid crashing when we mmap a router cache file of size 0.
9894 - When testing reachability of our DirPort, don't launch new
9895 tests when there's already one in progress -- unreachable
9896 servers were stacking up dozens of testing streams.
9898 o Minor bugfixes, correctness:
9899 - If we're a directory mirror and we ask for "all" network status
9900 documents, we would discard status documents from authorities
9902 - Avoid a memory corruption bug when creating a hash table for
9904 - Avoid controller-triggered crash when misusing certain commands
9905 from a v0 controller on platforms that do not handle
9906 printf("%s",NULL) gracefully.
9907 - Don't crash when a controller sends a third argument to an
9908 "extendcircuit" request.
9909 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
9910 response; fix error code when "getinfo dir/status/" fails.
9911 - Avoid crash when telling controller stream-status and a stream
9913 - Patch from Adam Langley to fix assert() in eventdns.c.
9914 - Fix a debug log message in eventdns to say "X resolved to Y"
9915 instead of "X resolved to X".
9916 - Make eventdns give strings for DNS errors, not just error numbers.
9917 - Track unreachable entry guards correctly: don't conflate
9918 'unreachable by us right now' with 'listed as down by the directory
9919 authorities'. With the old code, if a guard was unreachable by
9920 us but listed as running, it would clog our guard list forever.
9921 - Behave correctly in case we ever have a network with more than
9922 2GB/s total advertised capacity.
9923 - Make TrackExitHosts case-insensitive, and fix the behavior of
9924 ".suffix" TrackExitHosts items to avoid matching in the middle of
9926 - Finally fix the openssl warnings from newer gccs that believe that
9927 ignoring a return value is okay, but casting a return value and
9928 then ignoring it is a sign of madness.
9929 - Prevent the contrib/exitlist script from printing the same
9930 result more than once.
9931 - Patch from Steve Hildrey: Generate network status correctly on
9932 non-versioning dirservers.
9933 - Don't listen to the X-Your-Address-Is hint if you did the lookup
9934 via Tor; otherwise you'll think you're the exit node's IP address.
9936 o Minor bugfixes, performance:
9937 - Two small performance improvements on parsing descriptors.
9938 - Major performance improvement on inserting descriptors: change
9939 algorithm from O(n^2) to O(n).
9940 - Make the common memory allocation path faster on machines where
9941 malloc(0) returns a pointer.
9942 - Start remembering X-Your-Address-Is directory hints even if you're
9943 a client, so you can become a server more smoothly.
9944 - Avoid duplicate entries on MyFamily line in server descriptor.
9946 o Packaging, features:
9947 - Remove architecture from OS X builds. The official builds are
9948 now universal binaries.
9949 - The Debian package now uses --verify-config when (re)starting,
9950 to distinguish configuration errors from other errors.
9951 - Update RPMs to require libevent 1.1b.
9953 o Packaging, bugfixes:
9954 - Patches so Tor builds with MinGW on Windows.
9955 - Patches so Tor might run on Cygwin again.
9956 - Resume building on non-gcc compilers and ancient gcc. Resume
9957 building with the -O0 compile flag. Resume building cleanly on
9959 - Run correctly on OS X platforms with case-sensitive filesystems.
9960 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
9961 - Add autoconf checks so Tor can build on Solaris x86 again.
9964 - Documented (and renamed) ServerDNSSearchDomains and
9965 ServerDNSResolvConfFile options.
9966 - Be clearer that the *ListenAddress directives can be repeated
9970 Changes in version 0.1.1.24 - 2006-09-29
9972 - Allow really slow clients to not hang up five minutes into their
9973 directory downloads (suggested by Adam J. Richter).
9974 - Fix major performance regression from 0.1.0.x: instead of checking
9975 whether we have enough directory information every time we want to
9976 do something, only check when the directory information has changed.
9977 This should improve client CPU usage by 25-50%.
9978 - Don't crash if, after a server has been running for a while,
9979 it can't resolve its hostname.
9982 - Allow Tor to start when RunAsDaemon is set but no logs are set.
9983 - Don't crash when the controller receives a third argument to an
9984 "extendcircuit" request.
9985 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
9986 response; fix error code when "getinfo dir/status/" fails.
9987 - Fix configure.in to not produce broken configure files with
9988 more recent versions of autoconf. Thanks to Clint for his auto*
9990 - Fix security bug on NetBSD that could allow someone to force
9991 uninitialized RAM to be sent to a server's DNS resolver. This
9992 only affects NetBSD and other platforms that do not bounds-check
9994 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
9995 methods: these are known to be buggy.
9996 - If we're a directory mirror and we ask for "all" network status
9997 documents, we would discard status documents from authorities
10001 Changes in version 0.1.2.1-alpha - 2006-08-27
10003 - Add "eventdns" async dns library from Adam Langley, tweaked to
10004 build on OSX and Windows. Only enabled if you pass the
10005 --enable-eventdns argument to configure.
10006 - Allow servers with no hostname or IP address to learn their
10007 IP address by asking the directory authorities. This code only
10008 kicks in when you would normally have exited with a "no address"
10009 error. Nothing's authenticated, so use with care.
10010 - Rather than waiting a fixed amount of time between retrying
10011 application connections, we wait only 5 seconds for the first,
10012 10 seconds for the second, and 15 seconds for each retry after
10013 that. Hopefully this will improve the expected user experience.
10014 - Patch from Tup to add support for transparent AP connections:
10015 this basically bundles the functionality of trans-proxy-tor
10016 into the Tor mainline. Now hosts with compliant pf/netfilter
10017 implementations can redirect TCP connections straight to Tor
10018 without diverting through SOCKS. Needs docs.
10019 - Busy directory servers save lots of memory by spooling server
10020 descriptors, v1 directories, and v2 networkstatus docs to buffers
10021 as needed rather than en masse. Also mmap the cached-routers
10022 files, so we don't need to keep the whole thing in memory too.
10023 - Automatically avoid picking more than one node from the same
10024 /16 network when constructing a circuit.
10025 - Revise and clean up the torrc.sample that we ship with; add
10026 a section for BandwidthRate and BandwidthBurst.
10029 - Split circuit_t into origin_circuit_t and or_circuit_t, and
10030 split connection_t into edge, or, dir, control, and base structs.
10031 These will save quite a bit of memory on busy servers, and they'll
10032 also help us track down bugs in the code and bugs in the spec.
10033 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
10034 or later. Log when we are doing this, so we can diagnose it when
10035 it fails. (Also, recommend libevent 1.1b for kqueue and
10036 win32 methods; deprecate libevent 1.0b harder; make libevent
10037 recommendation system saner.)
10038 - Start being able to build universal binaries on OS X (thanks
10040 - Export the default exit policy via the control port, so controllers
10041 don't need to guess what it is / will be later.
10042 - Add a man page entry for ProtocolWarnings.
10043 - Add TestVia config option to the man page.
10044 - Remove even more protocol-related warnings from Tor server logs,
10045 such as bad TLS handshakes and malformed begin cells.
10046 - Stop fetching descriptors if you're not a dir mirror and you
10047 haven't tried to establish any circuits lately. [This currently
10048 causes some dangerous behavior, because when you start up again
10049 you'll use your ancient server descriptors.]
10050 - New DirPort behavior: if you have your dirport set, you download
10051 descriptors aggressively like a directory mirror, whether or not
10052 your ORPort is set.
10053 - Get rid of the router_retry_connections notion. Now routers
10054 no longer try to rebuild long-term connections to directory
10055 authorities, and directory authorities no longer try to rebuild
10056 long-term connections to all servers. We still don't hang up
10057 connections in these two cases though -- we need to look at it
10058 more carefully to avoid flapping, and we likely need to wait til
10059 0.1.1.x is obsolete.
10060 - Drop compatibility with obsolete Tors that permit create cells
10061 to have the wrong circ_id_type.
10062 - Re-enable per-connection rate limiting. Get rid of the "OP
10063 bandwidth" concept. Lay groundwork for "bandwidth classes" --
10064 separate global buckets that apply depending on what sort of conn
10066 - Start publishing one minute or so after we find our ORPort
10067 to be reachable. This will help reduce the number of descriptors
10068 we have for ourselves floating around, since it's quite likely
10069 other things (e.g. DirPort) will change during that minute too.
10070 - Fork the v1 directory protocol into its own spec document,
10071 and mark dir-spec.txt as the currently correct (v2) spec.
10074 - When we find our DirPort to be reachable, publish a new descriptor
10075 so we'll tell the world (reported by pnx).
10076 - Publish a new descriptor after we hup/reload. This is important
10077 if our config has changed such that we'll want to start advertising
10078 our DirPort now, etc.
10079 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10080 - When we have a state file we cannot parse, tell the user and
10081 move it aside. Now we avoid situations where the user starts
10082 Tor in 1904, Tor writes a state file with that timestamp in it,
10083 the user fixes her clock, and Tor refuses to start.
10084 - Fix configure.in to not produce broken configure files with
10085 more recent versions of autoconf. Thanks to Clint for his auto*
10087 - "tor --verify-config" now exits with -1(255) or 0 depending on
10088 whether the config options are bad or good.
10089 - Resolve bug 321 when using dnsworkers: append a period to every
10090 address we resolve at the exit node, so that we do not accidentally
10091 pick up local addresses, and so that failing searches are retried
10092 in the resolver search domains. (This is already solved for
10093 eventdns.) (This breaks Blossom servers for now.)
10094 - If we are using an exit enclave and we can't connect, e.g. because
10095 its webserver is misconfigured to not listen on localhost, then
10096 back off and try connecting from somewhere else before we fail.
10099 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
10100 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
10101 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
10102 when the IP address is mapped through MapAddress to a hostname.
10103 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
10104 useless IPv6 DNS resolves.
10105 - Patch suggested by Karsten Loesing: respond to SIGNAL command
10106 before we execute the signal, in case the signal shuts us down.
10107 - Clean up AllowInvalidNodes man page entry.
10108 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
10109 - Add more asserts to track down an assert error on a windows Tor
10110 server with connection_add being called with socket == -1.
10111 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
10112 - Fix misleading log messages: an entry guard that is "unlisted",
10113 as well as not known to be "down" (because we've never heard
10114 of it), is not therefore "up".
10115 - Remove code to special-case "-cvs" ending, since it has not
10116 actually mattered since 0.0.9.
10117 - Make our socks5 handling more robust to broken socks clients:
10118 throw out everything waiting on the buffer in between socks
10119 handshake phases, since they can't possibly (so the theory
10120 goes) have predicted what we plan to respond to them.
10123 Changes in version 0.1.1.23 - 2006-07-30
10125 - Fast Tor servers, especially exit nodes, were triggering asserts
10126 due to a bug in handling the list of pending DNS resolves. Some
10127 bugs still remain here; we're hunting them.
10128 - Entry guards could crash clients by sending unexpected input.
10129 - More fixes on reachability testing: if you find yourself reachable,
10130 then don't ever make any client requests (so you stop predicting
10131 circuits), then hup or have your clock jump, then later your IP
10132 changes, you won't think circuits are working, so you won't try to
10133 test reachability, so you won't publish.
10136 - Avoid a crash if the controller does a resetconf firewallports
10137 and then a setconf fascistfirewall=1.
10138 - Avoid an integer underflow when the dir authority decides whether
10139 a router is stable: we might wrongly label it stable, and compute
10140 a slightly wrong median stability, when a descriptor is published
10142 - Fix a place where we might trigger an assert if we can't build our
10143 own server descriptor yet.
10146 Changes in version 0.1.1.22 - 2006-07-05
10148 - Fix a big bug that was causing servers to not find themselves
10149 reachable if they changed IP addresses. Since only 0.1.1.22+
10150 servers can do reachability testing correctly, now we automatically
10151 make sure to test via one of these.
10152 - Fix to allow clients and mirrors to learn directory info from
10153 descriptor downloads that get cut off partway through.
10154 - Directory authorities had a bug in deciding if a newly published
10155 descriptor was novel enough to make everybody want a copy -- a few
10156 servers seem to be publishing new descriptors many times a minute.
10158 - Fix a rare bug that was causing some servers to complain about
10159 "closing wedged cpuworkers" and skip some circuit create requests.
10160 - Make the Exit flag in directory status documents actually work.
10163 Changes in version 0.1.1.21 - 2006-06-10
10164 o Crash and assert fixes from 0.1.1.20:
10165 - Fix a rare crash on Tor servers that have enabled hibernation.
10166 - Fix a seg fault on startup for Tor networks that use only one
10167 directory authority.
10168 - Fix an assert from a race condition that occurs on Tor servers
10169 while exiting, where various threads are trying to log that they're
10170 exiting, and delete the logs, at the same time.
10171 - Make our unit tests pass again on certain obscure platforms.
10174 - Add support for building SUSE RPM packages.
10175 - Speed up initial bootstrapping for clients: if we are making our
10176 first ever connection to any entry guard, then don't mark it down
10178 - When only one Tor server in the network is labelled as a guard,
10179 and we've already picked him, we would cycle endlessly picking him
10180 again, being unhappy about it, etc. Now we specifically exclude
10181 current guards when picking a new guard.
10182 - Servers send create cells more reliably after the TLS connection
10183 is established: we were sometimes forgetting to send half of them
10184 when we had more than one pending.
10185 - If we get a create cell that asks us to extend somewhere, but the
10186 Tor server there doesn't match the expected digest, we now send
10187 a destroy cell back, rather than silently doing nothing.
10188 - Make options->RedirectExit work again.
10189 - Make cookie authentication for the controller work again.
10190 - Stop being picky about unusual characters in the arguments to
10191 mapaddress. It's none of our business.
10192 - Add a new config option "TestVia" that lets you specify preferred
10193 middle hops to use for test circuits. Perhaps this will let me
10194 debug the reachability problems better.
10196 o Log / documentation fixes:
10197 - If we're a server and some peer has a broken TLS certificate, don't
10198 log about it unless ProtocolWarnings is set, i.e., we want to hear
10199 about protocol violations by others.
10200 - Fix spelling of VirtualAddrNetwork in man page.
10201 - Add a better explanation at the top of the autogenerated torrc file
10202 about what happened to our old torrc.
10205 Changes in version 0.1.1.20 - 2006-05-23
10207 - Downgrade a log severity where servers complain that they're
10209 - Avoid a compile warning on FreeBSD.
10210 - Remove string size limit on NEWDESC messages; solve bug 291.
10211 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
10212 more thoroughly when we're running on windows.
10215 Changes in version 0.1.1.19-rc - 2006-05-03
10217 - Regenerate our local descriptor if it's dirty and we try to use
10218 it locally (e.g. if it changes during reachability detection).
10219 - If we setconf our ORPort to 0, we continued to listen on the
10220 old ORPort and receive connections.
10221 - Avoid a second warning about machine/limits.h on Debian
10223 - Be willing to add our own routerinfo into the routerlist.
10224 Now authorities will include themselves in their directories
10225 and network-statuses.
10226 - Stop trying to upload rendezvous descriptors to every
10227 directory authority: only try the v1 authorities.
10228 - Servers no longer complain when they think they're not
10229 registered with the directory authorities. There were too many
10231 - Backport dist-rpm changes so rpms can be built without errors.
10234 - Implement an option, VirtualAddrMask, to set which addresses
10235 get handed out in response to mapaddress requests. This works
10236 around a bug in tsocks where 127.0.0.0/8 is never socksified.
10239 Changes in version 0.1.1.18-rc - 2006-04-10
10241 - Work harder to download live network-statuses from all the
10242 directory authorities we know about. Improve the threshold
10243 decision logic so we're more robust to edge cases.
10244 - When fetching rendezvous descriptors, we were willing to ask
10245 v2 authorities too, which would always return 404.
10248 - Stop listing down or invalid nodes in the v1 directory. This will
10249 reduce its bulk by about 1/3, and reduce load on directory
10251 - When deciding whether a router is Fast or Guard-worthy, consider
10252 his advertised BandwidthRate and not just the BandwidthCapacity.
10253 - No longer ship INSTALL and README files -- they are useless now.
10254 - Force rpmbuild to behave and honor target_cpu.
10255 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
10256 - Start to include translated versions of the tor-doc-*.html
10257 files, along with the screenshots. Still needs more work.
10258 - Start sending back 512 and 451 errors if mapaddress fails,
10259 rather than not sending anything back at all.
10260 - When we fail to bind or listen on an incoming or outgoing
10261 socket, we should close it before failing. otherwise we just
10262 leak it. (thanks to weasel for finding.)
10263 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
10264 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
10265 - Make NoPublish (even though deprecated) work again.
10266 - Fix a minor security flaw where a versioning auth dirserver
10267 could list a recommended version many times in a row to make
10268 clients more convinced that it's recommended.
10269 - Fix crash bug if there are two unregistered servers running
10270 with the same nickname, one of them is down, and you ask for
10271 them by nickname in your EntryNodes or ExitNodes. Also, try
10272 to pick the one that's running rather than an arbitrary one.
10273 - Fix an infinite loop we could hit if we go offline for too long.
10274 - Complain when we hit WSAENOBUFS on recv() or write() too.
10275 Perhaps this will help us hunt the bug.
10276 - If you're not a versioning dirserver, don't put the string
10277 "client-versions \nserver-versions \n" in your network-status.
10278 - Lower the minimum required number of file descriptors to 1000,
10279 so we can have some overhead for Valgrind on Linux, where the
10280 default ulimit -n is 1024.
10283 - Add tor.dizum.com as the fifth authoritative directory server.
10284 - Add a new config option FetchUselessDescriptors, off by default,
10285 for when you plan to run "exitlist" on your client and you want
10286 to know about even the non-running descriptors.
10289 Changes in version 0.1.1.17-rc - 2006-03-28
10291 - Clients and servers since 0.1.1.10-alpha have been expiring
10292 connections whenever they are idle for 5 minutes and they *do*
10293 have circuits on them. Oops. With this new version, clients will
10294 discard their previous entry guard choices and avoid choosing
10295 entry guards running these flawed versions.
10296 - Fix memory leak when uncompressing concatenated zlib streams. This
10297 was causing substantial leaks over time on Tor servers.
10298 - The v1 directory was including servers as much as 48 hours old,
10299 because that's how the new routerlist->routers works. Now only
10300 include them if they're 20 hours old or less.
10303 - Resume building on irix64, netbsd 2.0, etc.
10304 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
10306 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
10307 and it is confusing some users.
10308 - Mirrors stop caching the v1 directory so often.
10309 - Make the max number of old descriptors that a cache will hold
10310 rise with the number of directory authorities, so we can scale.
10311 - Change our win32 uname() hack to be more forgiving about what
10312 win32 versions it thinks it's found.
10315 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
10317 - When the controller's *setconf commands fail, collect an error
10318 message in a string and hand it back to the controller.
10319 - Make the v2 dir's "Fast" flag based on relative capacity, just
10320 like "Stable" is based on median uptime. Name everything in the
10321 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
10322 - Log server fingerprint on startup, so new server operators don't
10323 have to go hunting around their filesystem for it.
10324 - Return a robots.txt on our dirport to discourage google indexing.
10325 - Let the controller ask for GETINFO dir/status/foo so it can ask
10326 directly rather than connecting to the dir port. Only works when
10327 dirport is set for now.
10329 o New config options rather than constants in the code:
10330 - SocksTimeout: How long do we let a socks connection wait
10331 unattached before we fail it?
10332 - CircuitBuildTimeout: Cull non-open circuits that were born
10333 at least this many seconds ago.
10334 - CircuitIdleTimeout: Cull open clean circuits that were born
10335 at least this many seconds ago.
10338 Changes in version 0.1.1.16-rc - 2006-03-18
10339 o Bugfixes on 0.1.1.15-rc:
10340 - Fix assert when the controller asks to attachstream a connect-wait
10341 or resolve-wait stream.
10342 - Now do address rewriting when the controller asks us to attach
10343 to a particular circuit too. This will let Blossom specify
10344 "moria2.exit" without having to learn what moria2's IP address is.
10345 - Make the "tor --verify-config" command-line work again, so people
10346 can automatically check if their torrc will parse.
10347 - Authoritative dirservers no longer require an open connection from
10348 a server to consider him "reachable". We need this change because
10349 when we add new auth dirservers, old servers won't know not to
10351 - Let Tor build on Sun CC again.
10352 - Fix an off-by-one buffer size in dirserv.c that magically never
10353 hit our three authorities but broke sjmurdoch's own tor network.
10354 - If we as a directory mirror don't know of any v1 directory
10355 authorities, then don't try to cache any v1 directories.
10356 - Stop warning about unknown servers in our family when they are
10357 given as hex digests.
10358 - Stop complaining as quickly to the server operator that he
10359 hasn't registered his nickname/key binding.
10360 - Various cleanups so we can add new V2 Auth Dirservers.
10361 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
10362 reflect the updated flags in our v2 dir protocol.
10363 - Resume allowing non-printable characters for exit streams (both
10364 for connecting and for resolving). Now we tolerate applications
10365 that don't follow the RFCs. But continue to block malformed names
10368 o Bugfixes on 0.1.0.x:
10369 - Fix assert bug in close_logs(): when we close and delete logs,
10370 remove them all from the global "logfiles" list.
10371 - Fix minor integer overflow in calculating when we expect to use up
10372 our bandwidth allocation before hibernating.
10373 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
10374 there are multiple SSLs installed with different versions.
10375 - When we try to be a server and Address is not explicitly set and
10376 our hostname resolves to a private IP address, try to use an
10377 interface address if it has a public address. Now Windows machines
10378 that think of themselves as localhost can work by default.
10381 - Let the controller ask for GETINFO dir/server/foo so it can ask
10382 directly rather than connecting to the dir port.
10383 - Let the controller tell us about certain router descriptors
10384 that it doesn't want Tor to use in circuits. Implement
10385 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
10386 - New config option SafeSocks to reject all application connections
10387 using unsafe socks protocols. Defaults to off.
10390 Changes in version 0.1.1.15-rc - 2006-03-11
10391 o Bugfixes and cleanups:
10392 - When we're printing strings from the network, don't try to print
10393 non-printable characters. This protects us against shell escape
10394 sequence exploits, and also against attacks to fool humans into
10395 misreading their logs.
10396 - Fix a bug where Tor would fail to establish any connections if you
10397 left it off for 24 hours and then started it: we were happy with
10398 the obsolete network statuses, but they all referred to router
10399 descriptors that were too old to fetch, so we ended up with no
10400 valid router descriptors.
10401 - Fix a seg fault in the controller's "getinfo orconn-status"
10402 command while listing status on incoming handshaking connections.
10403 Introduce a status name "NEW" for these connections.
10404 - If we get a linelist or linelist_s config option from the torrc
10405 (e.g. ExitPolicy) and it has no value, warn and skip rather than
10406 silently resetting it to its default.
10407 - Don't abandon entry guards until they've been down or gone for
10409 - Cleaner and quieter log messages.
10412 - New controller signal NEWNYM that makes new application requests
10413 use clean circuits.
10414 - Add a new circuit purpose 'controller' to let the controller ask
10415 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
10416 controller command to let you specify the purpose if you're
10417 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
10418 command to let you change a circuit's purpose after it's been
10420 - Accept "private:*" in routerdesc exit policies; not generated yet
10421 because older Tors do not understand it.
10422 - Add BSD-style contributed startup script "rc.subr" from Peter
10426 Changes in version 0.1.1.14-alpha - 2006-02-20
10427 o Bugfixes on 0.1.1.x:
10428 - Don't die if we ask for a stdout or stderr log (even implicitly)
10429 and we're set to RunAsDaemon -- just warn.
10430 - We still had a few bugs in the OR connection rotation code that
10431 caused directory servers to slowly aggregate connections to other
10432 fast Tor servers. This time for sure!
10433 - Make log entries on Win32 include the name of the function again.
10434 - We were treating a pair of exit policies if they were equal even
10435 if one said accept and the other said reject -- causing us to
10436 not always publish a new descriptor since we thought nothing
10438 - Retry pending server downloads as well as pending networkstatus
10439 downloads when we unexpectedly get a socks request.
10440 - We were ignoring the IS_FAST flag in the directory status,
10441 meaning we were willing to pick trivial-bandwidth nodes for "fast"
10443 - If the controller's SAVECONF command fails (e.g. due to file
10444 permissions), let the controller know that it failed.
10447 - If we're trying to be a Tor server and running Windows 95/98/ME
10448 as a server, explain that we'll likely crash.
10449 - When we're a server, a client asks for an old-style directory,
10450 and our write bucket is empty, don't give it to him. This way
10451 small servers can continue to serve the directory *sometimes*,
10452 without getting overloaded.
10453 - Compress exit policies even more -- look for duplicate lines
10455 - Clients now honor the "guard" flag in the router status when
10456 picking entry guards, rather than looking at is_fast or is_stable.
10457 - Retain unrecognized lines in $DATADIR/state file, so that we can
10458 be forward-compatible.
10459 - Generate 18.0.0.0/8 address policy format in descs when we can;
10460 warn when the mask is not reducible to a bit-prefix.
10461 - Let the user set ControlListenAddress in the torrc. This can be
10462 dangerous, but there are some cases (like a secured LAN) where it
10464 - Split ReachableAddresses into ReachableDirAddresses and
10465 ReachableORAddresses, so we can restrict Dir conns to port 80
10466 and OR conns to port 443.
10467 - Now we can target arch and OS in rpm builds (contributed by
10468 Phobos). Also make the resulting dist-rpm filename match the
10470 - New config options to help controllers: FetchServerDescriptors
10471 and FetchHidServDescriptors for whether to fetch server
10472 info and hidserv info or let the controller do it, and
10473 PublishServerDescriptor and PublishHidServDescriptors.
10474 - Also let the controller set the __AllDirActionsPrivate config
10475 option if you want all directory fetches/publishes to happen via
10476 Tor (it assumes your controller bootstraps your circuits).
10479 Changes in version 0.1.0.17 - 2006-02-17
10480 o Crash bugfixes on 0.1.0.x:
10481 - When servers with a non-zero DirPort came out of hibernation,
10482 sometimes they would trigger an assert.
10484 o Other important bugfixes:
10485 - On platforms that don't have getrlimit (like Windows), we were
10486 artificially constraining ourselves to a max of 1024
10487 connections. Now just assume that we can handle as many as 15000
10488 connections. Hopefully this won't cause other problems.
10490 o Backported features:
10491 - When we're a server, a client asks for an old-style directory,
10492 and our write bucket is empty, don't give it to him. This way
10493 small servers can continue to serve the directory *sometimes*,
10494 without getting overloaded.
10495 - Whenever you get a 503 in response to a directory fetch, try
10496 once more. This will become important once servers start sending
10497 503's whenever they feel busy.
10498 - Fetch a new directory every 120 minutes, not every 40 minutes.
10499 Now that we have hundreds of thousands of users running the old
10500 directory algorithm, it's starting to hurt a lot.
10501 - Bump up the period for forcing a hidden service descriptor upload
10502 from 20 minutes to 1 hour.
10505 Changes in version 0.1.1.13-alpha - 2006-02-09
10506 o Crashes in 0.1.1.x:
10507 - When you tried to setconf ORPort via the controller, Tor would
10508 crash. So people using TorCP to become a server were sad.
10509 - Solve (I hope) the stack-smashing bug that we were seeing on fast
10510 servers. The problem appears to be something do with OpenSSL's
10511 random number generation, or how we call it, or something. Let me
10512 know if the crashes continue.
10513 - Turn crypto hardware acceleration off by default, until we find
10514 somebody smart who can test it for us. (It appears to produce
10515 seg faults in at least some cases.)
10516 - Fix a rare assert error when we've tried all intro points for
10517 a hidden service and we try fetching the service descriptor again:
10518 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
10521 - Fix a major load balance bug: we were round-robining in 16 KB
10522 chunks, and servers with bandwidthrate of 20 KB, while downloading
10523 a 600 KB directory, would starve their other connections. Now we
10524 try to be a bit more fair.
10525 - Dir authorities and mirrors were never expiring the newest
10526 descriptor for each server, causing memory and directory bloat.
10527 - Fix memory-bloating and connection-bloating bug on servers: We
10528 were never closing any connection that had ever had a circuit on
10529 it, because we were checking conn->n_circuits == 0, yet we had a
10530 bug that let it go negative.
10531 - Make Tor work using squid as your http proxy again -- squid
10532 returns an error if you ask for a URL that's too long, and it uses
10533 a really generic error message. Plus, many people are behind a
10534 transparent squid so they don't even realize it.
10535 - On platforms that don't have getrlimit (like Windows), we were
10536 artificially constraining ourselves to a max of 1024
10537 connections. Now just assume that we can handle as many as 15000
10538 connections. Hopefully this won't cause other problems.
10539 - Add a new config option ExitPolicyRejectPrivate which defaults to
10540 1. This means all exit policies will begin with rejecting private
10541 addresses, unless the server operator explicitly turns it off.
10544 - Clients no longer download descriptors for non-running
10546 - Before we add new directory authorities, we should make it
10547 clear that only v1 authorities should receive/publish hidden
10548 service descriptors.
10551 - As soon as we've fetched some more directory info, immediately
10552 try to download more server descriptors. This way we don't have
10553 a 10 second pause during initial bootstrapping.
10554 - Remove even more loud log messages that the server operator can't
10556 - When we're running an obsolete or un-recommended version, make
10557 the log message more clear about what the problem is and what
10558 versions *are* still recommended.
10559 - Provide a more useful warn message when our onion queue gets full:
10560 the CPU is too slow or the exit policy is too liberal.
10561 - Don't warn when we receive a 503 from a dirserver/cache -- this
10562 will pave the way for them being able to refuse if they're busy.
10563 - When we fail to bind a listener, try to provide a more useful
10564 log message: e.g., "Is Tor already running?"
10565 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
10566 Goldberg can prove things about our handshake protocol more
10568 - MaxConn has been obsolete for a while now. Document the ConnLimit
10569 config option, which is a *minimum* number of file descriptors
10570 that must be available else Tor refuses to start.
10571 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
10572 if you log to syslog and want something other than LOG_DAEMON.
10573 - Make dirservers generate a separate "guard" flag to mean,
10574 "would make a good entry guard". Make clients parse it and vote
10575 on it. Not used by clients yet.
10576 - Implement --with-libevent-dir option to ./configure. Also, improve
10577 search techniques to find libevent, and use those for openssl too.
10578 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
10579 - Only start testing reachability once we've established a
10580 circuit. This will make startup on dirservers less noisy.
10581 - Don't try to upload hidden service descriptors until we have
10582 established a circuit.
10583 - Fix the controller's "attachstream 0" command to treat conn like
10584 it just connected, doing address remapping, handling .exit and
10585 .onion idioms, and so on. Now we're more uniform in making sure
10586 that the controller hears about new and closing connections.
10589 Changes in version 0.1.1.12-alpha - 2006-01-11
10590 o Bugfixes on 0.1.1.x:
10591 - The fix to close duplicate server connections was closing all
10592 Tor client connections if they didn't establish a circuit
10593 quickly enough. Oops.
10594 - Fix minor memory issue (double-free) that happened on exit.
10596 o Bugfixes on 0.1.0.x:
10597 - Tor didn't warn when it failed to open a log file.
10600 Changes in version 0.1.1.11-alpha - 2006-01-10
10601 o Crashes in 0.1.1.x:
10602 - Include all the assert/crash fixes from 0.1.0.16.
10603 - If you start Tor and then quit very quickly, there were some
10604 races that tried to free things that weren't allocated yet.
10605 - Fix a rare memory stomp if you're running hidden services.
10606 - Fix segfault when specifying DirServer in config without nickname.
10607 - Fix a seg fault when you finish connecting to a server but at
10608 that moment you dump his server descriptor.
10609 - Extendcircuit and Attachstream controller commands would
10610 assert/crash if you don't give them enough arguments.
10611 - Fix an assert error when we're out of space in the connection_list
10612 and we try to post a hidden service descriptor (reported by weasel).
10613 - If you specify a relative torrc path and you set RunAsDaemon in
10614 your torrc, then it chdir()'s to the new directory. If you HUP,
10615 it tries to load the new torrc location, fails, and exits.
10616 The fix: no longer allow a relative path to torrc using -f.
10619 - Implement "entry guards": automatically choose a handful of entry
10620 nodes and stick with them for all circuits. Only pick new guards
10621 when the ones you have are unsuitable, and if the old guards
10622 become suitable again, switch back. This will increase security
10623 dramatically against certain end-point attacks. The EntryNodes
10624 config option now provides some hints about which entry guards you
10625 want to use most; and StrictEntryNodes means to only use those.
10626 - New directory logic: download by descriptor digest, not by
10627 fingerprint. Caches try to download all listed digests from
10628 authorities; clients try to download "best" digests from caches.
10629 This avoids partitioning and isolating attacks better.
10630 - Make the "stable" router flag in network-status be the median of
10631 the uptimes of running valid servers, and make clients pay
10632 attention to the network-status flags. Thus the cutoff adapts
10633 to the stability of the network as a whole, making IRC, IM, etc
10634 connections more reliable.
10637 - Tor servers with dynamic IP addresses were needing to wait 18
10638 hours before they could start doing reachability testing using
10639 the new IP address and ports. This is because they were using
10640 the internal descriptor to learn what to test, yet they were only
10641 rebuilding the descriptor once they decided they were reachable.
10642 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
10643 to download certain server descriptors, throw them away, and then
10644 fetch them again after 30 minutes. Now mirrors throw away these
10645 server descriptors so clients can't get them.
10646 - We were leaving duplicate connections to other ORs open for a week,
10647 rather than closing them once we detect a duplicate. This only
10648 really affected authdirservers, but it affected them a lot.
10649 - Spread the authdirservers' reachability testing over the entire
10650 testing interval, so we don't try to do 500 TLS's at once every
10654 - If the network is down, and we try to connect to a conn because
10655 we have a circuit in mind, and we timeout (30 seconds) because the
10656 network never answers, we were expiring the circuit, but we weren't
10657 obsoleting the connection or telling the entry_guards functions.
10658 - Some Tor servers process billions of cells per day. These statistics
10659 need to be uint64_t's.
10660 - Check for integer overflows in more places, when adding elements
10661 to smartlists. This could possibly prevent a buffer overflow
10662 on malicious huge inputs. I don't see any, but I haven't looked
10664 - ReachableAddresses kept growing new "reject *:*" lines on every
10666 - When you "setconf log" via the controller, it should remove all
10667 logs. We were automatically adding back in a "log notice stdout".
10668 - Newly bootstrapped Tor networks couldn't establish hidden service
10669 circuits until they had nodes with high uptime. Be more tolerant.
10670 - We were marking servers down when they could not answer every piece
10671 of the directory request we sent them. This was far too harsh.
10672 - Fix the torify (tsocks) config file to not use Tor for localhost
10674 - Directory authorities now go to the proper authority when asking for
10675 a networkstatus, even when they want a compressed one.
10676 - Fix a harmless bug that was causing Tor servers to log
10677 "Got an end because of misc error, but we're not an AP. Closing."
10678 - Authorities were treating their own descriptor changes as cosmetic,
10679 meaning the descriptor available in the network-status and the
10680 descriptor that clients downloaded were different.
10681 - The OS X installer was adding a symlink for tor_resolve but
10682 the binary was called tor-resolve (reported by Thomas Hardly).
10683 - Workaround a problem with some http proxies where they refuse GET
10684 requests that specify "Content-Length: 0" (reported by Adrian).
10685 - Fix wrong log message when you add a "HiddenServiceNodes" config
10686 line without any HiddenServiceDir line (reported by Chris Thomas).
10689 - Write the TorVersion into the state file so we have a prayer of
10690 keeping forward and backward compatibility.
10691 - Revive the FascistFirewall config option rather than eliminating it:
10692 now it's a synonym for ReachableAddresses *:80,*:443.
10693 - Clients choose directory servers from the network status lists,
10694 not from their internal list of router descriptors. Now they can
10695 go to caches directly rather than needing to go to authorities
10697 - Directory authorities ignore router descriptors that have only
10698 cosmetic differences: do this for 0.1.0.x servers now too.
10699 - Add a new flag to network-status indicating whether the server
10700 can answer v2 directory requests too.
10701 - Authdirs now stop whining so loudly about bad descriptors that
10702 they fetch from other dirservers. So when there's a log complaint,
10703 it's for sure from a freshly uploaded descriptor.
10704 - Reduce memory requirements in our structs by changing the order
10706 - There used to be two ways to specify your listening ports in a
10707 server descriptor: on the "router" line and with a separate "ports"
10708 line. Remove support for the "ports" line.
10709 - New config option "AuthDirRejectUnlisted" for auth dirservers as
10710 a panic button: if we get flooded with unusable servers we can
10711 revert to only listing servers in the approved-routers file.
10712 - Auth dir servers can now mark a fingerprint as "!reject" or
10713 "!invalid" in the approved-routers file (as its nickname), to
10714 refuse descriptors outright or include them but marked as invalid.
10715 - Servers store bandwidth history across restarts/crashes.
10716 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
10717 get a better idea of why their circuits failed. Not used yet.
10718 - Directory mirrors now cache up to 16 unrecognized network-status
10719 docs. Now we can add new authdirservers and they'll be cached too.
10720 - When picking a random directory, prefer non-authorities if any
10722 - New controller option "getinfo desc/all-recent" to fetch the
10723 latest server descriptor for every router that Tor knows about.
10726 Changes in version 0.1.0.16 - 2006-01-02
10727 o Crash bugfixes on 0.1.0.x:
10728 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
10729 corrupting the heap, losing FDs, or crashing when we need to resize
10730 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
10731 - It turns out sparc64 platforms crash on unaligned memory access
10732 too -- so detect and avoid this.
10733 - Handle truncated compressed data correctly (by detecting it and
10735 - Fix possible-but-unlikely free(NULL) in control.c.
10736 - When we were closing connections, there was a rare case that
10737 stomped on memory, triggering seg faults and asserts.
10738 - Avoid potential infinite recursion when building a descriptor. (We
10739 don't know that it ever happened, but better to fix it anyway.)
10740 - We were neglecting to unlink marked circuits from soon-to-close OR
10741 connections, which caused some rare scribbling on freed memory.
10742 - Fix a memory stomping race bug when closing the joining point of two
10743 rendezvous circuits.
10744 - Fix an assert in time parsing found by Steven Murdoch.
10746 o Other bugfixes on 0.1.0.x:
10747 - When we're doing reachability testing, provide more useful log
10748 messages so the operator knows what to expect.
10749 - Do not check whether DirPort is reachable when we are suppressing
10750 advertising it because of hibernation.
10751 - When building with -static or on Solaris, we sometimes needed -ldl.
10752 - When we're deciding whether a stream has enough circuits around
10753 that can handle it, count the freshly dirty ones and not the ones
10754 that are so dirty they won't be able to handle it.
10755 - When we're expiring old circuits, we had a logic error that caused
10756 us to close new rendezvous circuits rather than old ones.
10757 - Give a more helpful log message when you try to change ORPort via
10758 the controller: you should upgrade Tor if you want that to work.
10759 - We were failing to parse Tor versions that start with "Tor ".
10760 - Tolerate faulty streams better: when a stream fails for reason
10761 exitpolicy, stop assuming that the router is lying about his exit
10762 policy. When a stream fails for reason misc, allow it to retry just
10763 as if it was resolvefailed. When a stream has failed three times,
10764 reset its failure count so we can try again and get all three tries.
10767 Changes in version 0.1.1.10-alpha - 2005-12-11
10768 o Correctness bugfixes on 0.1.0.x:
10769 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
10770 corrupting the heap, losing FDs, or crashing when we need to resize
10771 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
10772 - Stop doing the complex voodoo overkill checking for insecure
10773 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
10774 - When we were closing connections, there was a rare case that
10775 stomped on memory, triggering seg faults and asserts.
10776 - We were neglecting to unlink marked circuits from soon-to-close OR
10777 connections, which caused some rare scribbling on freed memory.
10778 - When we're deciding whether a stream has enough circuits around
10779 that can handle it, count the freshly dirty ones and not the ones
10780 that are so dirty they won't be able to handle it.
10781 - Recover better from TCP connections to Tor servers that are
10782 broken but don't tell you (it happens!); and rotate TLS
10783 connections once a week.
10784 - When we're expiring old circuits, we had a logic error that caused
10785 us to close new rendezvous circuits rather than old ones.
10786 - Fix a scary-looking but apparently harmless bug where circuits
10787 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
10788 servers, and never switch to state CIRCUIT_STATE_OPEN.
10789 - When building with -static or on Solaris, we sometimes needed to
10791 - Give a useful message when people run Tor as the wrong user,
10792 rather than telling them to start chowning random directories.
10793 - We were failing to inform the controller about new .onion streams.
10795 o Security bugfixes on 0.1.0.x:
10796 - Refuse server descriptors if the fingerprint line doesn't match
10797 the included identity key. Tor doesn't care, but other apps (and
10798 humans) might actually be trusting the fingerprint line.
10799 - We used to kill the circuit when we receive a relay command we
10800 don't recognize. Now we just drop it.
10801 - Start obeying our firewall options more rigorously:
10802 . If we can't get to a dirserver directly, try going via Tor.
10803 . Don't ever try to connect (as a client) to a place our
10804 firewall options forbid.
10805 . If we specify a proxy and also firewall options, obey the
10806 firewall options even when we're using the proxy: some proxies
10807 can only proxy to certain destinations.
10808 - Fix a bug found by Lasse Overlier: when we were making internal
10809 circuits (intended to be cannibalized later for rendezvous and
10810 introduction circuits), we were picking them so that they had
10811 useful exit nodes. There was no need for this, and it actually
10812 aids some statistical attacks.
10813 - Start treating internal circuits and exit circuits separately.
10814 It's important to keep them separate because internal circuits
10815 have their last hops picked like middle hops, rather than like
10816 exit hops. So exiting on them will break the user's expectations.
10818 o Bugfixes on 0.1.1.x:
10819 - Take out the mis-feature where we tried to detect IP address
10820 flapping for people with DynDNS, and chose not to upload a new
10821 server descriptor sometimes.
10822 - Try to be compatible with OpenSSL 0.9.6 again.
10823 - Log fix: when the controller is logging about .onion addresses,
10824 sometimes it didn't include the ".onion" part of the address.
10825 - Don't try to modify options->DirServers internally -- if the
10826 user didn't specify any, just add the default ones directly to
10827 the trusted dirserver list. This fixes a bug where people running
10828 controllers would use SETCONF on some totally unrelated config
10829 option, and Tor would start yelling at them about changing their
10831 - Let the controller's redirectstream command specify a port, in
10832 case the controller wants to change that too.
10833 - When we requested a pile of server descriptors, we sometimes
10834 accidentally launched a duplicate request for the first one.
10835 - Bugfix for trackhostexits: write down the fingerprint of the
10836 chosen exit, not its nickname, because the chosen exit might not
10838 - When parsing foo.exit, if foo is unknown, and we are leaving
10839 circuits unattached, set the chosen_exit field and leave the
10840 address empty. This matters because controllers got confused
10842 - Directory authorities no longer try to download server
10843 descriptors that they know they will reject.
10845 o Features and updates:
10846 - Replace balanced trees with hash tables: this should make stuff
10847 significantly faster.
10848 - Resume using the AES counter-mode implementation that we ship,
10849 rather than OpenSSL's. Ours is significantly faster.
10850 - Many other CPU and memory improvements.
10851 - Add a new config option FastFirstHopPK (on by default) so clients
10852 do a trivial crypto handshake for their first hop, since TLS has
10853 already taken care of confidentiality and authentication.
10854 - Add a new config option TestSocks so people can see if their
10855 applications are using socks4, socks4a, socks5-with-ip, or
10856 socks5-with-hostname. This way they don't have to keep mucking
10857 with tcpdump and wondering if something got cached somewhere.
10858 - Warn when listening on a public address for socks. I suspect a
10859 lot of people are setting themselves up as open socks proxies,
10860 and they have no idea that jerks on the Internet are using them,
10861 since they simply proxy the traffic into the Tor network.
10862 - Add "private:*" as an alias in configuration for policies. Now
10863 you can simplify your exit policy rather than needing to list
10864 every single internal or nonroutable network space.
10865 - Add a new controller event type that allows controllers to get
10866 all server descriptors that were uploaded to a router in its role
10867 as authoritative dirserver.
10868 - Start shipping socks-extensions.txt, tor-doc-unix.html,
10869 tor-doc-server.html, and stylesheet.css in the tarball.
10870 - Stop shipping tor-doc.html in the tarball.
10873 Changes in version 0.1.1.9-alpha - 2005-11-15
10874 o Usability improvements:
10875 - Start calling it FooListenAddress rather than FooBindAddress,
10876 since few of our users know what it means to bind an address
10878 - Reduce clutter in server logs. We're going to try to make
10879 them actually usable now. New config option ProtocolWarnings that
10880 lets you hear about how _other Tors_ are breaking the protocol. Off
10882 - Divide log messages into logging domains. Once we put some sort
10883 of interface on this, it will let people looking at more verbose
10884 log levels specify the topics they want to hear more about.
10885 - Make directory servers return better http 404 error messages
10886 instead of a generic "Servers unavailable".
10887 - Check for even more Windows version flags when writing the platform
10888 string in server descriptors, and note any we don't recognize.
10889 - Clean up more of the OpenSSL memory when exiting, so we can detect
10890 memory leaks better.
10891 - Make directory authorities be non-versioning, non-naming by
10892 default. Now we can add new directory servers without requiring
10893 their operators to pay close attention.
10894 - When logging via syslog, include the pid whenever we provide
10895 a log entry. Suggested by Todd Fries.
10897 o Performance improvements:
10898 - Directory servers now silently throw away new descriptors that
10899 haven't changed much if the timestamps are similar. We do this to
10900 tolerate older Tor servers that upload a new descriptor every 15
10901 minutes. (It seemed like a good idea at the time.)
10902 - Inline bottleneck smartlist functions; use fast versions by default.
10903 - Add a "Map from digest to void*" abstraction digestmap_t so we
10904 can do less hex encoding/decoding. Use it in router_get_by_digest()
10905 to resolve a performance bottleneck.
10906 - Allow tor_gzip_uncompress to extract as much as possible from
10907 truncated compressed data. Try to extract as many
10908 descriptors as possible from truncated http responses (when
10909 DIR_PURPOSE_FETCH_ROUTERDESC).
10910 - Make circ->onionskin a pointer, not a static array. moria2 was using
10911 125000 circuit_t's after it had been up for a few weeks, which
10912 translates to 20+ megs of wasted space.
10913 - The private half of our EDH handshake keys are now chosen out
10914 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
10916 o Security improvements:
10917 - Start making directory caches retain old routerinfos, so soon
10918 clients can start asking by digest of descriptor rather than by
10919 fingerprint of server.
10920 - Add half our entropy from RAND_poll in OpenSSL. This knows how
10921 to use egd (if present), openbsd weirdness (if present), vms/os2
10922 weirdness (if we ever port there), and more in the future.
10924 o Bugfixes on 0.1.0.x:
10925 - Do round-robin writes of at most 16 kB per write. This might be
10926 more fair on loaded Tor servers, and it might resolve our Windows
10927 crash bug. It might also slow things down.
10928 - Our TLS handshakes were generating a single public/private
10929 keypair for the TLS context, rather than making a new one for
10930 each new connections. Oops. (But we were still rotating them
10931 periodically, so it's not so bad.)
10932 - When we were cannibalizing a circuit with a particular exit
10933 node in mind, we weren't checking to see if that exit node was
10934 already present earlier in the circuit. Oops.
10935 - When a Tor server's IP changes (e.g. from a dyndns address),
10936 upload a new descriptor so clients will learn too.
10937 - Really busy servers were keeping enough circuits open on stable
10938 connections that they were wrapping around the circuit_id
10939 space. (It's only two bytes.) This exposed a bug where we would
10940 feel free to reuse a circuit_id even if it still exists but has
10941 been marked for close. Try to fix this bug. Some bug remains.
10942 - If we would close a stream early (e.g. it asks for a .exit that
10943 we know would refuse it) but the LeaveStreamsUnattached config
10944 option is set by the controller, then don't close it.
10946 o Bugfixes on 0.1.1.8-alpha:
10947 - Fix a big pile of memory leaks, some of them serious.
10948 - Do not try to download a routerdesc if we would immediately reject
10950 - Resume inserting a newline between all router descriptors when
10951 generating (old style) signed directories, since our spec says
10953 - When providing content-type application/octet-stream for
10954 server descriptors using .z, we were leaving out the
10955 content-encoding header. Oops. (Everything tolerated this just
10956 fine, but that doesn't mean we need to be part of the problem.)
10957 - Fix a potential seg fault in getconf and getinfo using version 1
10958 of the controller protocol.
10959 - Avoid crash: do not check whether DirPort is reachable when we
10960 are suppressing it because of hibernation.
10961 - Make --hash-password not crash on exit.
10964 Changes in version 0.1.1.8-alpha - 2005-10-07
10965 o New features (major):
10966 - Clients don't download or use the directory anymore. Now they
10967 download and use network-statuses from the trusted dirservers,
10968 and fetch individual server descriptors as needed from mirrors.
10969 See dir-spec.txt for all the gory details.
10970 - Be more conservative about whether to advertise our DirPort.
10971 The main change is to not advertise if we're running at capacity
10972 and either a) we could hibernate or b) our capacity is low and
10973 we're using a default DirPort.
10974 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
10976 o New features (minor):
10977 - Try to be smart about when to retry network-status and
10978 server-descriptor fetches. Still needs some tuning.
10979 - Stop parsing, storing, or using running-routers output (but
10980 mirrors still cache and serve it).
10981 - Consider a threshold of versioning dirservers (dirservers who have
10982 an opinion about which Tor versions are still recommended) before
10983 deciding whether to warn the user that he's obsolete.
10984 - Dirservers can now reject/invalidate by key and IP, with the
10985 config options "AuthDirInvalid" and "AuthDirReject". This is
10986 useful since currently we automatically list servers as running
10987 and usable even if we know they're jerks.
10988 - Provide dire warnings to any users who set DirServer; move it out
10989 of torrc.sample and into torrc.complete.
10990 - Add MyFamily to torrc.sample in the server section.
10991 - Add nicknames to the DirServer line, so we can refer to them
10992 without requiring all our users to memorize their IP addresses.
10993 - When we get an EOF or a timeout on a directory connection, note
10994 how many bytes of serverdesc we are dropping. This will help
10995 us determine whether it is smart to parse incomplete serverdesc
10997 - Add a new function to "change pseudonyms" -- that is, to stop
10998 using any currently-dirty circuits for new streams, so we don't
10999 link new actions to old actions. Currently it's only called on
11000 HUP (or SIGNAL RELOAD).
11001 - On sighup, if UseHelperNodes changed to 1, use new circuits.
11002 - Start using RAND_bytes rather than RAND_pseudo_bytes from
11003 OpenSSL. Also, reseed our entropy every hour, not just at
11004 startup. And entropy in 512-bit chunks, not 160-bit chunks.
11006 o Fixes on 0.1.1.7-alpha:
11007 - Nobody ever implemented EVENT_ADDRMAP for control protocol
11008 version 0, so don't let version 0 controllers ask for it.
11009 - If you requested something with too many newlines via the
11010 v1 controller protocol, you could crash tor.
11011 - Fix a number of memory leaks, including some pretty serious ones.
11012 - Re-enable DirPort testing again, so Tor servers will be willing
11013 to advertise their DirPort if it's reachable.
11014 - On TLS handshake, only check the other router's nickname against
11015 its expected nickname if is_named is set.
11017 o Fixes forward-ported from 0.1.0.15:
11018 - Don't crash when we don't have any spare file descriptors and we
11019 try to spawn a dns or cpu worker.
11020 - Make the numbers in read-history and write-history into uint64s,
11021 so they don't overflow and publish negatives in the descriptor.
11023 o Fixes on 0.1.0.x:
11024 - For the OS X package's modified privoxy config file, comment
11025 out the "logfile" line so we don't log everything passed
11027 - We were whining about using socks4 or socks5-with-local-lookup
11028 even when it's an IP in the "virtual" range we designed exactly
11030 - We were leaking some memory every time the client changes IPs.
11031 - Never call free() on tor_malloc()d memory. This will help us
11032 use dmalloc to detect memory leaks.
11033 - Check for named servers when looking them up by nickname;
11034 warn when we'recalling a non-named server by its nickname;
11035 don't warn twice about the same name.
11036 - Try to list MyFamily elements by key, not by nickname, and warn
11037 if we've not heard of the server.
11038 - Make windows platform detection (uname equivalent) smarter.
11039 - It turns out sparc64 doesn't like unaligned access either.
11042 Changes in version 0.1.0.15 - 2005-09-23
11043 o Bugfixes on 0.1.0.x:
11044 - Reject ports 465 and 587 (spam targets) in default exit policy.
11045 - Don't crash when we don't have any spare file descriptors and we
11046 try to spawn a dns or cpu worker.
11047 - Get rid of IgnoreVersion undocumented config option, and make us
11048 only warn, never exit, when we're running an obsolete version.
11049 - Don't try to print a null string when your server finds itself to
11050 be unreachable and the Address config option is empty.
11051 - Make the numbers in read-history and write-history into uint64s,
11052 so they don't overflow and publish negatives in the descriptor.
11053 - Fix a minor memory leak in smartlist_string_remove().
11054 - We were only allowing ourselves to upload a server descriptor at
11055 most every 20 minutes, even if it changed earlier than that.
11056 - Clean up log entries that pointed to old URLs.
11059 Changes in version 0.1.1.7-alpha - 2005-09-14
11060 o Fixes on 0.1.1.6-alpha:
11061 - Exit servers were crashing when people asked them to make a
11062 connection to an address not in their exit policy.
11063 - Looking up a non-existent stream for a v1 control connection would
11065 - Fix a seg fault if we ask a dirserver for a descriptor by
11066 fingerprint but he doesn't know about him.
11067 - SETCONF was appending items to linelists, not clearing them.
11068 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
11069 out and refuse the setconf if it would fail.
11070 - Downgrade the dirserver log messages when whining about
11074 - Add Peter Palfrader's check-tor script to tor/contrib/
11075 It lets you easily check whether a given server (referenced by
11076 nickname) is reachable by you.
11077 - Numerous changes to move towards client-side v2 directories. Not
11080 o Fixes on 0.1.0.x:
11081 - If the user gave tor an odd number of command-line arguments,
11082 we were silently ignoring the last one. Now we complain and fail.
11083 [This wins the oldest-bug prize -- this bug has been present since
11084 November 2002, as released in Tor 0.0.0.]
11085 - Do not use unaligned memory access on alpha, mips, or mipsel.
11086 It *works*, but is very slow, so we treat them as if it doesn't.
11087 - Retry directory requests if we fail to get an answer we like
11088 from a given dirserver (we were retrying before, but only if
11089 we fail to connect).
11090 - When writing the RecommendedVersions line, sort them first.
11091 - When the client asked for a rendezvous port that the hidden
11092 service didn't want to provide, we were sending an IP address
11093 back along with the end cell. Fortunately, it was zero. But stop
11095 - Correct "your server is reachable" log entries to indicate that
11096 it was self-testing that told us so.
11099 Changes in version 0.1.1.6-alpha - 2005-09-09
11100 o Fixes on 0.1.1.5-alpha:
11101 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
11102 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
11103 - Fix bug with tor_memmem finding a match at the end of the string.
11104 - Make unit tests run without segfaulting.
11105 - Resolve some solaris x86 compile warnings.
11106 - Handle duplicate lines in approved-routers files without warning.
11107 - Fix bug where as soon as a server refused any requests due to his
11108 exit policy (e.g. when we ask for localhost and he tells us that's
11109 127.0.0.1 and he won't do it), we decided he wasn't obeying his
11110 exit policy using him for any exits.
11111 - Only do openssl hardware accelerator stuff if openssl version is
11114 o New controller features/fixes:
11115 - Add a "RESETCONF" command so you can set config options like
11116 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
11117 a config option in the torrc with no value, then it clears it
11118 entirely (rather than setting it to its default).
11119 - Add a "GETINFO config-file" to tell us where torrc is.
11120 - Avoid sending blank lines when GETINFO replies should be empty.
11121 - Add a QUIT command for the controller (for using it manually).
11122 - Fix a bug in SAVECONF that was adding default dirservers and
11123 other redundant entries to the torrc file.
11125 o Start on the new directory design:
11126 - Generate, publish, cache, serve new network-status format.
11127 - Publish individual descriptors (by fingerprint, by "all", and by
11129 - Publish client and server recommended versions separately.
11130 - Allow tor_gzip_uncompress() to handle multiple concatenated
11131 compressed strings. Serve compressed groups of router
11132 descriptors. The compression logic here could be more
11134 - Distinguish v1 authorities (all currently trusted directories)
11135 from v2 authorities (all trusted directories).
11136 - Change DirServers config line to note which dirs are v1 authorities.
11137 - Add configuration option "V1AuthoritativeDirectory 1" which
11138 moria1, moria2, and tor26 should set.
11139 - Remove option when getting directory cache to see whether they
11140 support running-routers; they all do now. Replace it with one
11141 to see whether caches support v2 stuff.
11144 - Dirservers now do their own external reachability testing of each
11145 Tor server, and only list them as running if they've been found to
11146 be reachable. We also send back warnings to the server's logs if
11147 it uploads a descriptor that we already believe is unreachable.
11148 - Implement exit enclaves: if we know an IP address for the
11149 destination, and there's a running Tor server at that address
11150 which allows exit to the destination, then extend the circuit to
11151 that exit first. This provides end-to-end encryption and end-to-end
11152 authentication. Also, if the user wants a .exit address or enclave,
11153 use 4 hops rather than 3, and cannibalize a general circ for it
11155 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
11156 controller. Also, rotate dns and cpu workers if the controller
11157 changes options that will affect them; and initialize the dns
11158 worker cache tree whether or not we start out as a server.
11159 - Only upload a new server descriptor when options change, 18
11160 hours have passed, uptime is reset, or bandwidth changes a lot.
11161 - Check [X-]Forwarded-For headers in HTTP requests when generating
11162 log messages. This lets people run dirservers (and caches) behind
11163 Apache but still know which IP addresses are causing warnings.
11165 o Config option changes:
11166 - Replace (Fascist)Firewall* config options with a new
11167 ReachableAddresses option that understands address policies.
11168 For example, "ReachableAddresses *:80,*:443"
11169 - Get rid of IgnoreVersion undocumented config option, and make us
11170 only warn, never exit, when we're running an obsolete version.
11171 - Make MonthlyAccountingStart config option truly obsolete now.
11173 o Fixes on 0.1.0.x:
11174 - Reject ports 465 and 587 in the default exit policy, since
11175 people have started using them for spam too.
11176 - It turns out we couldn't bootstrap a network since we added
11177 reachability detection in 0.1.0.1-rc. Good thing the Tor network
11178 has never gone down. Add an AssumeReachable config option to let
11179 servers and dirservers bootstrap. When we're trying to build a
11180 high-uptime or high-bandwidth circuit but there aren't enough
11181 suitable servers, try being less picky rather than simply failing.
11182 - Our logic to decide if the OR we connected to was the right guy
11183 was brittle and maybe open to a mitm for unverified routers.
11184 - We weren't cannibalizing circuits correctly for
11185 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
11186 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
11187 build those from scratch. This should make hidden services faster.
11188 - Predict required circuits better, with an eye toward making hidden
11189 services faster on the service end.
11190 - Retry streams if the exit node sends back a 'misc' failure. This
11191 should result in fewer random failures. Also, after failing
11192 from resolve failed or misc, reset the num failures, so we give
11193 it a fair shake next time we try.
11194 - Clean up the rendezvous warn log msgs, and downgrade some to info.
11195 - Reduce severity on logs about dns worker spawning and culling.
11196 - When we're shutting down and we do something like try to post a
11197 server descriptor or rendezvous descriptor, don't complain that
11198 we seem to be unreachable. Of course we are, we're shutting down.
11199 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
11200 We don't use them yet, but maybe one day our DNS resolver will be
11201 able to discover them.
11202 - Make ContactInfo mandatory for authoritative directory servers.
11203 - Require server descriptors to list IPv4 addresses -- hostnames
11204 are no longer allowed. This also fixes some potential security
11205 problems with people providing hostnames as their address and then
11206 preferentially resolving them to partition users.
11207 - Change log line for unreachability to explicitly suggest /etc/hosts
11208 as the culprit. Also make it clearer what IP address and ports we're
11209 testing for reachability.
11210 - Put quotes around user-supplied strings when logging so users are
11211 more likely to realize if they add bad characters (like quotes)
11213 - Let auth dir servers start without specifying an Address config
11215 - Make unit tests (and other invocations that aren't the real Tor)
11216 run without launching listeners, creating subdirectories, and so on.
11219 Changes in version 0.1.1.5-alpha - 2005-08-08
11220 o Bugfixes included in 0.1.0.14.
11222 o Bugfixes on 0.1.0.x:
11223 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
11224 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
11225 it would silently using ignore the 6668.
11228 Changes in version 0.1.0.14 - 2005-08-08
11229 o Bugfixes on 0.1.0.x:
11230 - Fix the other half of the bug with crypto handshakes
11232 - Fix an assert trigger if you send a 'signal term' via the
11233 controller when it's listening for 'event info' messages.
11236 Changes in version 0.1.1.4-alpha - 2005-08-04
11237 o Bugfixes included in 0.1.0.13.
11240 - Improve tor_gettimeofday() granularity on windows.
11241 - Make clients regenerate their keys when their IP address changes.
11242 - Implement some more GETINFO goodness: expose helper nodes, config
11243 options, getinfo keys.
11246 Changes in version 0.1.0.13 - 2005-08-04
11247 o Bugfixes on 0.1.0.x:
11248 - Fix a critical bug in the security of our crypto handshakes.
11249 - Fix a size_t underflow in smartlist_join_strings2() that made
11250 it do bad things when you hand it an empty smartlist.
11251 - Fix Windows installer to ship Tor license (thanks to Aphex for
11252 pointing out this oversight) and put a link to the doc directory
11254 - Explicitly set no-unaligned-access for sparc: it turns out the
11255 new gcc's let you compile broken code, but that doesn't make it
11259 Changes in version 0.1.1.3-alpha - 2005-07-23
11260 o Bugfixes on 0.1.1.2-alpha:
11261 - Fix a bug in handling the controller's "post descriptor"
11263 - Fix several bugs in handling the controller's "extend circuit"
11265 - Fix a bug in handling the controller's "stream status" event.
11266 - Fix an assert failure if we have a controller listening for
11267 circuit events and we go offline.
11268 - Re-allow hidden service descriptors to publish 0 intro points.
11269 - Fix a crash when generating your hidden service descriptor if
11270 you don't have enough intro points already.
11272 o New features on 0.1.1.2-alpha:
11273 - New controller function "getinfo accounting", to ask how
11274 many bytes we've used in this time period.
11275 - Experimental support for helper nodes: a lot of the risk from
11276 a small static adversary comes because users pick new random
11277 nodes every time they rebuild a circuit. Now users will try to
11278 stick to the same small set of entry nodes if they can. Not
11279 enabled by default yet.
11281 o Bugfixes on 0.1.0.12:
11282 - If you're an auth dir server, always publish your dirport,
11283 even if you haven't yet found yourself to be reachable.
11284 - Fix a size_t underflow in smartlist_join_strings2() that made
11285 it do bad things when you hand it an empty smartlist.
11288 Changes in version 0.1.0.12 - 2005-07-18
11289 o New directory servers:
11290 - tor26 has changed IP address.
11292 o Bugfixes on 0.1.0.x:
11293 - Fix a possible double-free in tor_gzip_uncompress().
11294 - When --disable-threads is set, do not search for or link against
11295 pthreads libraries.
11296 - Don't trigger an assert if an authoritative directory server
11297 claims its dirport is 0.
11298 - Fix bug with removing Tor as an NT service: some people were
11299 getting "The service did not return an error." Thanks to Matt
11303 Changes in version 0.1.1.2-alpha - 2005-07-15
11304 o New directory servers:
11305 - tor26 has changed IP address.
11307 o Bugfixes on 0.1.0.x, crashes/leaks:
11308 - Port the servers-not-obeying-their-exit-policies fix from
11310 - Fix an fd leak in start_daemon().
11311 - On Windows, you can't always reopen a port right after you've
11312 closed it. So change retry_listeners() to only close and re-open
11313 ports that have changed.
11314 - Fix a possible double-free in tor_gzip_uncompress().
11316 o Bugfixes on 0.1.0.x, usability:
11317 - When tor_socketpair() fails in Windows, give a reasonable
11318 Windows-style errno back.
11319 - Let people type "tor --install" as well as "tor -install" when
11321 want to make it an NT service.
11322 - NT service patch from Matt Edman to improve error messages.
11323 - When the controller asks for a config option with an abbreviated
11324 name, give the full name in our response.
11325 - Correct the man page entry on TrackHostExitsExpire.
11326 - Looks like we were never delivering deflated (i.e. compressed)
11327 running-routers lists, even when asked. Oops.
11328 - When --disable-threads is set, do not search for or link against
11329 pthreads libraries.
11331 o Bugfixes on 0.1.1.x:
11332 - Fix a seg fault with autodetecting which controller version is
11336 - New hidden service descriptor format: put a version in it, and
11337 let people specify introduction/rendezvous points that aren't
11338 in "the directory" (which is subjective anyway).
11339 - Allow the DEBUG controller event to work again. Mark certain log
11340 entries as "don't tell this to controllers", so we avoid cycles.
11343 Changes in version 0.1.0.11 - 2005-06-30
11344 o Bugfixes on 0.1.0.x:
11345 - Fix major security bug: servers were disregarding their
11346 exit policies if clients behaved unexpectedly.
11347 - Make OS X init script check for missing argument, so we don't
11348 confuse users who invoke it incorrectly.
11349 - Fix a seg fault in "tor --hash-password foo".
11350 - The MAPADDRESS control command was broken.
11353 Changes in version 0.1.1.1-alpha - 2005-06-29
11355 - Make OS X init script check for missing argument, so we don't
11356 confuse users who invoke it incorrectly.
11357 - Fix a seg fault in "tor --hash-password foo".
11358 - Fix a possible way to DoS dirservers.
11359 - When we complain that your exit policy implicitly allows local or
11360 private address spaces, name them explicitly so operators can
11362 - Make the log message less scary when all the dirservers are
11363 temporarily unreachable.
11364 - We were printing the number of idle dns workers incorrectly when
11368 - Revised controller protocol (version 1) that uses ascii rather
11369 than binary. Add supporting libraries in python and java so you
11370 can use the controller from your applications without caring how
11371 our protocol works.
11372 - Spiffy new support for crypto hardware accelerators. Can somebody
11376 Changes in version 0.0.9.10 - 2005-06-16
11377 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
11378 - Refuse relay cells that claim to have a length larger than the
11379 maximum allowed. This prevents a potential attack that could read
11380 arbitrary memory (e.g. keys) from an exit server's process
11384 Changes in version 0.1.0.10 - 2005-06-14
11385 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
11386 libevent before 1.1a.
11389 Changes in version 0.1.0.9-rc - 2005-06-09
11391 - Reset buf->highwater every time buf_shrink() is called, not just on
11392 a successful shrink. This was causing significant memory bloat.
11393 - Fix buffer overflow when checking hashed passwords.
11394 - Security fix: if seeding the RNG on Win32 fails, quit.
11395 - Allow seeding the RNG on Win32 even when you're not running as
11397 - Disable threading on Solaris too. Something is wonky with it,
11398 cpuworkers, and reentrant libs.
11399 - Reenable the part of the code that tries to flush as soon as an
11400 OR outbuf has a full TLS record available. Perhaps this will make
11401 OR outbufs not grow as huge except in rare cases, thus saving lots
11402 of CPU time plus memory.
11403 - Reject malformed .onion addresses rather then passing them on as
11404 normal web requests.
11405 - Adapt patch from Adam Langley: fix possible memory leak in
11406 tor_lookup_hostname().
11407 - Initialize libevent later in the startup process, so the logs are
11408 already established by the time we start logging libevent warns.
11409 - Use correct errno on win32 if libevent fails.
11410 - Check and warn about known-bad/slow libevent versions.
11411 - Pay more attention to the ClientOnly config option.
11412 - Have torctl.in/tor.sh.in check for location of su binary (needed
11414 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
11415 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
11416 HttpProxyAuthenticator
11417 - Stop warning about sigpipes in the logs. We're going to
11418 pretend that getting these occassionally is normal and fine.
11419 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
11421 installer screens; and don't put stuff into StartupItems unless
11422 the user asks you to.
11423 - Require servers that use the default dirservers to have public IP
11424 addresses. We have too many servers that are configured with private
11425 IPs and their admins never notice the log entries complaining that
11426 their descriptors are being rejected.
11427 - Add OSX uninstall instructions. An actual uninstall script will
11431 Changes in version 0.1.0.8-rc - 2005-05-23
11433 - It turns out that kqueue on OS X 10.3.9 was causing kernel
11434 panics. Disable kqueue on all OS X Tors.
11435 - Fix RPM: remove duplicate line accidentally added to the rpm
11437 - Disable threads on openbsd too, since its gethostaddr is not
11439 - Tolerate libevent 0.8 since it still works, even though it's
11441 - Enable building on Red Hat 9.0 again.
11442 - Allow the middle hop of the testing circuit to be running any
11443 version, now that most of them have the bugfix to let them connect
11444 to unknown servers. This will allow reachability testing to work
11445 even when 0.0.9.7-0.0.9.9 become obsolete.
11446 - Handle relay cells with rh.length too large. This prevents
11447 a potential attack that could read arbitrary memory (maybe even
11448 keys) from the exit server's process.
11449 - We screwed up the dirport reachability testing when we don't yet
11450 have a cached version of the directory. Hopefully now fixed.
11451 - Clean up router_load_single_router() (used by the controller),
11452 so it doesn't seg fault on error.
11453 - Fix a minor memory leak when somebody establishes an introduction
11454 point at your Tor server.
11455 - If a socks connection ends because read fails, don't warn that
11456 you're not sending a socks reply back.
11459 - Add HttpProxyAuthenticator config option too, that works like
11460 the HttpsProxyAuthenticator config option.
11461 - Encode hashed controller passwords in hex instead of base64,
11462 to make it easier to write controllers.
11465 Changes in version 0.1.0.7-rc - 2005-05-17
11467 - Fix a bug in the OS X package installer that prevented it from
11468 installing on Tiger.
11469 - Fix a script bug in the OS X package installer that made it
11470 complain during installation.
11471 - Find libevent even if it's hiding in /usr/local/ and your
11472 CFLAGS and LDFLAGS don't tell you to look there.
11473 - Be able to link with libevent as a shared library (the default
11474 after 1.0d), even if it's hiding in /usr/local/lib and even
11475 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
11476 assuming you're running gcc. Otherwise fail and give a useful
11478 - Fix a bug in the RPM packager: set home directory for _tor to
11479 something more reasonable when first installing.
11480 - Free a minor amount of memory that is still reachable on exit.
11483 Changes in version 0.1.0.6-rc - 2005-05-14
11485 - Implement --disable-threads configure option. Disable threads on
11486 netbsd by default, because it appears to have no reentrant resolver
11488 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
11489 release (1.1) detects and disables kqueue if it's broken.
11490 - Append default exit policy before checking for implicit internal
11491 addresses. Now we don't log a bunch of complaints on startup
11492 when using the default exit policy.
11493 - Some people were putting "Address " in their torrc, and they had
11494 a buggy resolver that resolved " " to 0.0.0.0. Oops.
11495 - If DataDir is ~/.tor, and that expands to /.tor, then default to
11496 LOCALSTATEDIR/tor instead.
11497 - Fix fragmented-message bug in TorControl.py.
11498 - Resolve a minor bug which would prevent unreachable dirports
11499 from getting suppressed in the published descriptor.
11500 - When the controller gave us a new descriptor, we weren't resolving
11501 it immediately, so Tor would think its address was 0.0.0.0 until
11502 we fetched a new directory.
11503 - Fix an uppercase/lowercase case error in suppressing a bogus
11504 libevent warning on some Linuxes.
11507 - Begin scrubbing sensitive strings from logs by default. Turn off
11508 the config option SafeLogging if you need to do debugging.
11509 - Switch to a new buffer management algorithm, which tries to avoid
11510 reallocing and copying quite as much. In first tests it looks like
11511 it uses *more* memory on average, but less cpu.
11512 - First cut at support for "create-fast" cells. Clients can use
11513 these when extending to their first hop, since the TLS already
11514 provides forward secrecy and authentication. Not enabled on
11516 - When dirservers refuse a router descriptor, we now log its
11517 contactinfo, platform, and the poster's IP address.
11518 - Call tor_free_all instead of connections_free_all after forking, to
11519 save memory on systems that need to fork.
11520 - Whine at you if you're a server and you don't set your contactinfo.
11521 - Implement --verify-config command-line option to check if your torrc
11522 is valid without actually launching Tor.
11523 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
11524 rather than just rejecting it.
11527 Changes in version 0.1.0.5-rc - 2005-04-27
11529 - Stop trying to print a null pointer if an OR conn fails because
11530 we didn't like its cert.
11532 - Switch our internal buffers implementation to use a ring buffer,
11533 to hopefully improve performance for fast servers a lot.
11534 - Add HttpsProxyAuthenticator support (basic auth only), based
11535 on patch from Adam Langley.
11536 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
11537 the fast servers that have been joining lately.
11538 - Give hidden service accesses extra time on the first attempt,
11539 since 60 seconds is often only barely enough. This might improve
11541 - Improve performance for dirservers: stop re-parsing the whole
11542 directory every time you regenerate it.
11543 - Add more debugging info to help us find the weird dns freebsd
11544 pthreads bug; cleaner debug messages to help track future issues.
11547 Changes in version 0.0.9.9 - 2005-04-23
11548 o Bugfixes on 0.0.9.x:
11549 - If unofficial Tor clients connect and send weird TLS certs, our
11550 Tor server triggers an assert. This release contains a minimal
11551 backport from the broader fix that we put into 0.1.0.4-rc.
11554 Changes in version 0.1.0.4-rc - 2005-04-23
11556 - If unofficial Tor clients connect and send weird TLS certs, our
11557 Tor server triggers an assert. Stop asserting, and start handling
11558 TLS errors better in other situations too.
11559 - When the controller asks us to tell it about all the debug-level
11560 logs, it turns out we were generating debug-level logs while
11561 telling it about them, which turns into a bad loop. Now keep
11562 track of whether you're sending a debug log to the controller,
11563 and don't log when you are.
11564 - Fix the "postdescriptor" feature of the controller interface: on
11565 non-complete success, only say "done" once.
11567 - Clients are now willing to load balance over up to 2mB, not 1mB,
11568 of advertised bandwidth capacity.
11569 - Add a NoPublish config option, so you can be a server (e.g. for
11570 testing running Tor servers in other Tor networks) without
11571 publishing your descriptor to the primary dirservers.
11574 Changes in version 0.1.0.3-rc - 2005-04-08
11575 o Improvements on 0.1.0.2-rc:
11576 - Client now retries when streams end early for 'hibernating' or
11577 'resource limit' reasons, rather than failing them.
11578 - More automated handling for dirserver operators:
11579 - Automatically approve nodes running 0.1.0.2-rc or later,
11580 now that the the reachability detection stuff is working.
11581 - Now we allow two unverified servers with the same nickname
11582 but different keys. But if a nickname is verified, only that
11583 nickname+key are allowed.
11584 - If you're an authdirserver connecting to an address:port,
11585 and it's not the OR you were expecting, forget about that
11586 descriptor. If he *was* the one you were expecting, then forget
11587 about all other descriptors for that address:port.
11588 - Allow servers to publish descriptors from 12 hours in the future.
11589 Corollary: only whine about clock skew from the dirserver if
11590 he's a trusted dirserver (since now even verified servers could
11591 have quite wrong clocks).
11592 - Adjust maximum skew and age for rendezvous descriptors: let skew
11593 be 48 hours rather than 90 minutes.
11594 - Efficiency improvements:
11595 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
11596 it much faster to look up a circuit for each relay cell.
11597 - Remove most calls to assert_all_pending_dns_resolves_ok(),
11598 since they're eating our cpu on exit nodes.
11599 - Stop wasting time doing a case insensitive comparison for every
11600 dns name every time we do any lookup. Canonicalize the names to
11601 lowercase and be done with it.
11602 - Start sending 'truncated' cells back rather than destroy cells,
11603 if the circuit closes in front of you. This means we won't have
11604 to abandon partially built circuits.
11605 - Only warn once per nickname from add_nickname_list_to_smartlist
11606 per failure, so an entrynode or exitnode choice that's down won't
11608 - Put a note in the torrc about abuse potential with the default
11610 - Revise control spec and implementation to allow all log messages to
11611 be sent to controller with their severities intact (suggested by
11612 Matt Edman). Update TorControl to handle new log event types.
11613 - Provide better explanation messages when controller's POSTDESCRIPTOR
11615 - Stop putting nodename in the Platform string in server descriptors.
11616 It doesn't actually help, and it is confusing/upsetting some people.
11618 o Bugfixes on 0.1.0.2-rc:
11619 - We were printing the host mask wrong in exit policies in server
11620 descriptors. This isn't a critical bug though, since we were still
11621 obeying the exit policy internally.
11622 - Fix Tor when compiled with libevent but without pthreads: move
11623 connection_unregister() from _connection_free() to
11625 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
11626 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
11627 when we look through the connection array, we'll find any of the
11628 cpu/dnsworkers. This is no good.
11630 o Bugfixes on 0.0.9.8:
11631 - Fix possible bug on threading platforms (e.g. win32) which was
11632 leaking a file descriptor whenever a cpuworker or dnsworker died.
11633 - When using preferred entry or exit nodes, ignore whether the
11634 circuit wants uptime or capacity. They asked for the nodes, they
11636 - chdir() to your datadirectory at the *end* of the daemonize process,
11637 not the beginning. This was a problem because the first time you
11638 run tor, if your datadir isn't there, and you have runasdaemon set
11639 to 1, it will try to chdir to it before it tries to create it. Oops.
11640 - Handle changed router status correctly when dirserver reloads
11641 fingerprint file. We used to be dropping all unverified descriptors
11642 right then. The bug was hidden because we would immediately
11643 fetch a directory from another dirserver, which would include the
11644 descriptors we just dropped.
11645 - When we're connecting to an OR and he's got a different nickname/key
11646 than we were expecting, only complain loudly if we're an OP or a
11647 dirserver. Complaining loudly to the OR admins just confuses them.
11648 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
11649 artificially capped at 500kB.
11652 Changes in version 0.0.9.8 - 2005-04-07
11653 o Bugfixes on 0.0.9.x:
11654 - We have a bug that I haven't found yet. Sometimes, very rarely,
11655 cpuworkers get stuck in the 'busy' state, even though the cpuworker
11656 thinks of itself as idle. This meant that no new circuits ever got
11657 established. Here's a workaround to kill any cpuworker that's been
11658 busy for more than 100 seconds.
11661 Changes in version 0.1.0.2-rc - 2005-04-01
11662 o Bugfixes on 0.1.0.1-rc:
11663 - Fixes on reachability detection:
11664 - Don't check for reachability while hibernating.
11665 - If ORPort is reachable but DirPort isn't, still publish the
11666 descriptor, but zero out DirPort until it's found reachable.
11667 - When building testing circs for ORPort testing, use only
11668 high-bandwidth nodes, so fewer circuits fail.
11669 - Complain about unreachable ORPort separately from unreachable
11670 DirPort, so the user knows what's going on.
11671 - Make sure we only conclude ORPort reachability if we didn't
11672 initiate the conn. Otherwise we could falsely conclude that
11673 we're reachable just because we connected to the guy earlier
11674 and he used that same pipe to extend to us.
11675 - Authdirservers shouldn't do ORPort reachability detection,
11676 since they're in clique mode, so it will be rare to find a
11677 server not already connected to them.
11678 - When building testing circuits, always pick middle hops running
11679 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
11680 bug. (This is a kludge; it will go away when 0.0.9.x becomes
11682 - When we decide we're reachable, actually publish our descriptor
11684 - Fix bug in redirectstream in the controller.
11685 - Fix the state descriptor strings so logs don't claim edge streams
11686 are in a different state than they actually are.
11687 - Use recent libevent features when possible (this only really affects
11688 win32 and osx right now, because the new libevent with these
11689 features hasn't been released yet). Add code to suppress spurious
11691 - Prevent possible segfault in connection_close_unattached_ap().
11692 - Fix newlines on torrc in win32.
11693 - Improve error msgs when tor-resolve fails.
11695 o Improvements on 0.0.9.x:
11696 - New experimental script tor/contrib/ExerciseServer.py (needs more
11697 work) that uses the controller interface to build circuits and
11698 fetch pages over them. This will help us bootstrap servers that
11699 have lots of capacity but haven't noticed it yet.
11700 - New experimental script tor/contrib/PathDemo.py (needs more work)
11701 that uses the controller interface to let you choose whole paths
11703 "<hostname>.<path,separated by dots>.<length of path>.path"
11704 - When we've connected to an OR and handshaked but didn't like
11705 the result, we were closing the conn without sending destroy
11706 cells back for pending circuits. Now send those destroys.
11709 Changes in version 0.0.9.7 - 2005-04-01
11710 o Bugfixes on 0.0.9.x:
11711 - Fix another race crash bug (thanks to Glenn Fink for reporting).
11712 - Compare identity to identity, not to nickname, when extending to
11713 a router not already in the directory. This was preventing us from
11714 extending to unknown routers. Oops.
11715 - Make sure to create OS X Tor user in <500 range, so we aren't
11716 creating actual system users.
11717 - Note where connection-that-hasn't-sent-end was marked, and fix
11718 a few really loud instances of this harmless bug (it's fixed more
11722 Changes in version 0.1.0.1-rc - 2005-03-28
11724 - Add reachability testing. Your Tor server will automatically try
11725 to see if its ORPort and DirPort are reachable from the outside,
11726 and it won't upload its descriptor until it decides they are.
11727 - Handle unavailable hidden services better. Handle slow or busy
11728 hidden services better.
11729 - Add support for CONNECTing through https proxies, with "HttpsProxy"
11731 - New exit policy: accept most low-numbered ports, rather than
11732 rejecting most low-numbered ports.
11733 - More Tor controller support (still experimental). See
11734 http://tor.eff.org/doc/control-spec.txt for all the new features,
11735 including signals to emulate unix signals from any platform;
11736 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
11737 closestream; closecircuit; etc.
11738 - Make nt services work and start on startup on win32 (based on
11739 patch by Matt Edman).
11740 - Add a new AddressMap config directive to rewrite incoming socks
11741 addresses. This lets you, for example, declare an implicit
11742 required exit node for certain sites.
11743 - Add a new TrackHostExits config directive to trigger addressmaps
11744 for certain incoming socks addresses -- for sites that break when
11745 your exit keeps changing (based on patch by Mike Perry).
11746 - Redo the client-side dns cache so it's just an addressmap too.
11747 - Notice when our IP changes, and reset stats/uptime/reachability.
11748 - When an application is using socks5, give him the whole variety of
11749 potential socks5 responses (connect refused, host unreachable, etc),
11750 rather than just "success" or "failure".
11751 - A more sane version numbering system. See
11752 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
11753 - New contributed script "exitlist": a simple python script to
11754 parse directories and find Tor nodes that exit to listed
11756 - New contributed script "privoxy-tor-toggle" to toggle whether
11757 Privoxy uses Tor. Seems to be configured for Debian by default.
11758 - Report HTTP reasons to client when getting a response from directory
11759 servers -- so you can actually know what went wrong.
11760 - New config option MaxAdvertisedBandwidth which lets you advertise
11761 a low bandwidthrate (to not attract as many circuits) while still
11762 allowing a higher bandwidthrate in reality.
11764 o Robustness/stability fixes:
11765 - Make Tor use Niels Provos's libevent instead of its current
11766 poll-but-sometimes-select mess. This will let us use faster async
11767 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
11769 - pthread support now too. This was forced because when we forked,
11770 we ended up wasting a lot of duplicate ram over time. Also switch
11771 to foo_r versions of some library calls to allow reentry and
11773 - Better handling for heterogeneous / unreliable nodes:
11774 - Annotate circuits w/ whether they aim to contain high uptime nodes
11775 and/or high capacity nodes. When building circuits, choose
11777 - This means that every single node in an intro rend circuit,
11778 not just the last one, will have a minimum uptime.
11779 - New config option LongLivedPorts to indicate application streams
11780 that will want high uptime circuits.
11781 - Servers reset uptime when a dir fetch entirely fails. This
11782 hopefully reflects stability of the server's network connectivity.
11783 - If somebody starts his tor server in Jan 2004 and then fixes his
11784 clock, don't make his published uptime be a year.
11785 - Reset published uptime when you wake up from hibernation.
11786 - Introduce a notion of 'internal' circs, which are chosen without
11787 regard to the exit policy of the last hop. Intro and rendezvous
11788 circs must be internal circs, to avoid leaking information. Resolve
11789 and connect streams can use internal circs if they want.
11790 - New circuit pooling algorithm: make sure to have enough circs around
11791 to satisfy any predicted ports, and also make sure to have 2 internal
11792 circs around if we've required internal circs lately (and with high
11793 uptime if we've seen that lately too).
11794 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
11795 which describes how often we retry making new circuits if current
11796 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
11797 how long we're willing to make use of an already-dirty circuit.
11798 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
11799 circ as necessary, if there are any completed ones lying around
11800 when we try to launch one.
11801 - Make hidden services try to establish a rendezvous for 30 seconds,
11802 rather than for n (where n=3) attempts to build a circuit.
11803 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
11804 "ShutdownWaitLength".
11805 - Try to be more zealous about calling connection_edge_end when
11806 things go bad with edge conns in connection.c.
11807 - Revise tor-spec to add more/better stream end reasons.
11808 - Revise all calls to connection_edge_end to avoid sending "misc",
11809 and to take errno into account where possible.
11812 - Fix a race condition that can trigger an assert, when we have a
11813 pending create cell and an OR connection fails right then.
11814 - Fix several double-mark-for-close bugs, e.g. where we were finding
11815 a conn for a cell even if that conn is already marked for close.
11816 - Make sequence of log messages when starting on win32 with no config
11817 file more reasonable.
11818 - When choosing an exit node for a new non-internal circ, don't take
11819 into account whether it'll be useful for any pending x.onion
11820 addresses -- it won't.
11821 - Turn addr_policy_compare from a tristate to a quadstate; this should
11822 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
11823 for google.com" problem.
11824 - Make "platform" string in descriptor more accurate for Win32 servers,
11825 so it's not just "unknown platform".
11826 - Fix an edge case in parsing config options (thanks weasel).
11827 If they say "--" on the commandline, it's not an option.
11828 - Reject odd-looking addresses at the client (e.g. addresses that
11829 contain a colon), rather than having the server drop them because
11831 - tor-resolve requests were ignoring .exit if there was a working circuit
11832 they could use instead.
11833 - REUSEADDR on normal platforms means you can rebind to the port
11834 right after somebody else has let it go. But REUSEADDR on win32
11835 means to let you bind to the port _even when somebody else
11836 already has it bound_! So, don't do that on Win32.
11837 - Change version parsing logic: a version is "obsolete" if it is not
11838 recommended and (1) there is a newer recommended version in the
11839 same series, or (2) there are no recommended versions in the same
11840 series, but there are some recommended versions in a newer series.
11841 A version is "new" if it is newer than any recommended version in
11843 - Stop most cases of hanging up on a socks connection without sending
11847 - Require BandwidthRate to be at least 20kB/s for servers.
11848 - When a dirserver causes you to give a warn, mention which dirserver
11850 - New config option DirAllowPrivateAddresses for authdirservers.
11851 Now by default they refuse router descriptors that have non-IP or
11852 private-IP addresses.
11853 - Stop publishing socksport in the directory, since it's not
11854 actually meant to be public. For compatibility, publish a 0 there
11856 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
11857 smart" value, that is low for servers and high for clients.
11858 - If our clock jumps forward by 100 seconds or more, assume something
11859 has gone wrong with our network and abandon all not-yet-used circs.
11860 - Warn when exit policy implicitly allows local addresses.
11861 - If we get an incredibly skewed timestamp from a dirserver mirror
11862 that isn't a verified OR, don't warn -- it's probably him that's
11864 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
11865 cookies to disk and doesn't log each web request to disk. (Thanks
11866 to Brett Carrington for pointing this out.)
11867 - When a client asks us for a dir mirror and we don't have one,
11868 launch an attempt to get a fresh one.
11869 - If we're hibernating and we get a SIGINT, exit immediately.
11870 - Add --with-dmalloc ./configure option, to track memory leaks.
11871 - And try to free all memory on closing, so we can detect what
11873 - Cache local dns resolves correctly even when they're .exit
11875 - Give a better warning when some other server advertises an
11876 ORPort that is actually an apache running ssl.
11877 - Add "opt hibernating 1" to server descriptor to make it clearer
11878 whether the server is hibernating.
11881 Changes in version 0.0.9.6 - 2005-03-24
11882 o Bugfixes on 0.0.9.x (crashes and asserts):
11883 - Add new end stream reasons to maintainance branch. Fix bug where
11884 reason (8) could trigger an assert. Prevent bug from recurring.
11885 - Apparently win32 stat wants paths to not end with a slash.
11886 - Fix assert triggers in assert_cpath_layer_ok(), where we were
11887 blowing away the circuit that conn->cpath_layer points to, then
11888 checking to see if the circ is well-formed. Backport check to make
11889 sure we dont use the cpath on a closed connection.
11890 - Prevent circuit_resume_edge_reading_helper() from trying to package
11891 inbufs for marked-for-close streams.
11892 - Don't crash on hup if your options->address has become unresolvable.
11893 - Some systems (like OS X) sometimes accept() a connection and tell
11894 you the remote host is 0.0.0.0:0. If this happens, due to some
11895 other mis-features, we get confused; so refuse the conn for now.
11897 o Bugfixes on 0.0.9.x (other):
11898 - Fix harmless but scary "Unrecognized content encoding" warn message.
11899 - Add new stream error reason: TORPROTOCOL reason means "you are not
11900 speaking a version of Tor I understand; say bye-bye to your stream."
11901 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
11902 into the future, now that we are more tolerant of skew. This
11903 resolves a bug where a Tor server would refuse to cache a directory
11904 because all the directories it gets are too far in the future;
11905 yet the Tor server never logs any complaints about clock skew.
11906 - Mac packaging magic: make man pages useable, and do not overwrite
11907 existing torrc files.
11908 - Make OS X log happily to /var/log/tor/tor.log
11911 Changes in version 0.0.9.5 - 2005-02-22
11912 o Bugfixes on 0.0.9.x:
11913 - Fix an assert race at exit nodes when resolve requests fail.
11914 - Stop picking unverified dir mirrors--it only leads to misery.
11915 - Patch from Matt Edman to make NT services work better. Service
11916 support is still not compiled into the executable by default.
11917 - Patch from Dmitri Bely so the Tor service runs better under
11918 the win32 SYSTEM account.
11919 - Make tor-resolve actually work (?) on Win32.
11920 - Fix a sign bug when getrlimit claims to have 4+ billion
11921 file descriptors available.
11922 - Stop refusing to start when bandwidthburst == bandwidthrate.
11923 - When create cells have been on the onion queue more than five
11924 seconds, just send back a destroy and take them off the list.
11927 Changes in version 0.0.9.4 - 2005-02-03
11928 o Bugfixes on 0.0.9:
11929 - Fix an assert bug that took down most of our servers: when
11930 a server claims to have 1 GB of bandwidthburst, don't
11932 - Don't crash as badly if we have spawned the max allowed number
11933 of dnsworkers, or we're out of file descriptors.
11934 - Block more file-sharing ports in the default exit policy.
11935 - MaxConn is now automatically set to the hard limit of max
11936 file descriptors we're allowed (ulimit -n), minus a few for
11938 - Give a clearer message when servers need to raise their
11939 ulimit -n when they start running out of file descriptors.
11940 - SGI Compatibility patches from Jan Schaumann.
11941 - Tolerate a corrupt cached directory better.
11942 - When a dirserver hasn't approved your server, list which one.
11943 - Go into soft hibernation after 95% of the bandwidth is used,
11944 not 99%. This is especially important for daily hibernators who
11945 have a small accounting max. Hopefully it will result in fewer
11946 cut connections when the hard hibernation starts.
11947 - Load-balance better when using servers that claim more than
11948 800kB/s of capacity.
11949 - Make NT services work (experimental, only used if compiled in).
11952 Changes in version 0.0.9.3 - 2005-01-21
11953 o Bugfixes on 0.0.9:
11954 - Backport the cpu use fixes from main branch, so busy servers won't
11955 need as much processor time.
11956 - Work better when we go offline and then come back, or when we
11957 run Tor at boot before the network is up. We do this by
11958 optimistically trying to fetch a new directory whenever an
11959 application request comes in and we think we're offline -- the
11960 human is hopefully a good measure of when the network is back.
11961 - Backport some minimal hidserv bugfixes: keep rend circuits open as
11962 long as you keep using them; actually publish hidserv descriptors
11963 shortly after they change, rather than waiting 20-40 minutes.
11964 - Enable Mac startup script by default.
11965 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
11966 - When you update AllowUnverifiedNodes or FirewallPorts via the
11967 controller's setconf feature, we were always appending, never
11969 - When you update HiddenServiceDir via setconf, it was screwing up
11970 the order of reading the lines, making it fail.
11971 - Do not rewrite a cached directory back to the cache; otherwise we
11972 will think it is recent and not fetch a newer one on startup.
11973 - Workaround for webservers that lie about Content-Encoding: Tor
11974 now tries to autodetect compressed directories and compression
11975 itself. This lets us Proxypass dir fetches through apache.
11978 Changes in version 0.0.9.2 - 2005-01-04
11979 o Bugfixes on 0.0.9 (crashes and asserts):
11980 - Fix an assert on startup when the disk is full and you're logging
11982 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
11983 style address, then we'd crash.
11984 - Fix an assert trigger when the running-routers string we get from
11985 a dirserver is broken.
11986 - Make worker threads start and run on win32. Now win32 servers
11988 - Bandaid (not actually fix, but now it doesn't crash) an assert
11989 where the dns worker dies mysteriously and the main Tor process
11990 doesn't remember anything about the address it was resolving.
11992 o Bugfixes on 0.0.9 (Win32):
11993 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
11994 name out of the warning/assert messages.
11995 - Fix a superficial "unhandled error on read" bug on win32.
11996 - The win32 installer no longer requires a click-through for our
11997 license, since our Free Software license grants rights but does not
11999 - Win32: When connecting to a dirserver fails, try another one
12000 immediately. (This was already working for non-win32 Tors.)
12001 - Stop trying to parse $HOME on win32 when hunting for default
12003 - Make tor-resolve.c work on win32 by calling network_init().
12005 o Bugfixes on 0.0.9 (other):
12006 - Make 0.0.9.x build on Solaris again.
12007 - Due to a fencepost error, we were blowing away the \n when reporting
12008 confvalue items in the controller. So asking for multiple config
12009 values at once couldn't work.
12010 - When listing circuits that are pending on an opening OR connection,
12011 if we're an OR we were listing circuits that *end* at us as
12012 being pending on every listener, dns/cpu worker, etc. Stop that.
12013 - Dirservers were failing to create 'running-routers' or 'directory'
12014 strings if we had more than some threshold of routers. Fix them so
12015 they can handle any number of routers.
12016 - Fix a superficial "Duplicate mark for close" bug.
12017 - Stop checking for clock skew for OR connections, even for servers.
12018 - Fix a fencepost error that was chopping off the last letter of any
12019 nickname that is the maximum allowed nickname length.
12020 - Update URLs in log messages so they point to the new website.
12021 - Fix a potential problem in mangling server private keys while
12022 writing to disk (not triggered yet, as far as we know).
12023 - Include the licenses for other free software we include in Tor,
12024 now that we're shipping binary distributions more regularly.
12027 Changes in version 0.0.9.1 - 2004-12-15
12028 o Bugfixes on 0.0.9:
12029 - Make hibernation actually work.
12030 - Make HashedControlPassword config option work.
12031 - When we're reporting event circuit status to a controller,
12032 don't use the stream status code.
12035 Changes in version 0.0.9 - 2004-12-12
12037 - Clean up manpage and torrc.sample file.
12038 - Clean up severities and text of log warnings.
12040 - Make servers trigger an assert when they enter hibernation.
12043 Changes in version 0.0.9rc7 - 2004-12-08
12044 o Bugfixes on 0.0.9rc:
12045 - Fix a stack-trashing crash when an exit node begins hibernating.
12046 - Avoid looking at unallocated memory while considering which
12047 ports we need to build circuits to cover.
12048 - Stop a sigpipe: when an 'end' cell races with eof from the app,
12049 we shouldn't hold-open-until-flush if the eof arrived first.
12050 - Fix a bug with init_cookie_authentication() in the controller.
12051 - When recommending new-format log lines, if the upper bound is
12052 LOG_ERR, leave it implicit.
12054 o Bugfixes on 0.0.8.1:
12055 - Fix a whole slew of memory leaks.
12056 - Fix isspace() and friends so they still make Solaris happy
12057 but also so they don't trigger asserts on win32.
12058 - Fix parse_iso_time on platforms without strptime (eg win32).
12059 - win32: tolerate extra "readable" events better.
12060 - win32: when being multithreaded, leave parent fdarray open.
12061 - Make unit tests work on win32.
12064 Changes in version 0.0.9rc6 - 2004-12-06
12065 o Bugfixes on 0.0.9pre:
12066 - Clean up some more integer underflow opportunities (not exploitable
12068 - While hibernating, hup should not regrow our listeners.
12069 - Send an end to the streams we close when we hibernate, rather
12070 than just chopping them off.
12071 - React to eof immediately on non-open edge connections.
12073 o Bugfixes on 0.0.8.1:
12074 - Calculate timeout for waiting for a connected cell from the time
12075 we sent the begin cell, not from the time the stream started. If
12076 it took a long time to establish the circuit, we would time out
12077 right after sending the begin cell.
12078 - Fix router_compare_addr_to_addr_policy: it was not treating a port
12079 of * as always matching, so we were picking reject *:* nodes as
12080 exit nodes too. Oops.
12083 - New circuit building strategy: keep a list of ports that we've
12084 used in the past 6 hours, and always try to have 2 circuits open
12085 or on the way that will handle each such port. Seed us with port
12086 80 so web users won't complain that Tor is "slow to start up".
12087 - Make kill -USR1 dump more useful stats about circuits.
12088 - When warning about retrying or giving up, print the address, so
12089 the user knows which one it's talking about.
12090 - If you haven't used a clean circuit in an hour, throw it away,
12091 just to be on the safe side. (This means after 6 hours a totally
12092 unused Tor client will have no circuits open.)
12095 Changes in version 0.0.9rc5 - 2004-12-01
12096 o Bugfixes on 0.0.8.1:
12097 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
12098 - Let resolve conns retry/expire also, rather than sticking around
12100 - If we are using select, make sure we stay within FD_SETSIZE.
12102 o Bugfixes on 0.0.9pre:
12103 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
12104 but doesn't seem to be currently; thanks to Ilja van Sprundel for
12106 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
12107 instead. Impose minima and maxima for all *Period options; impose
12108 even tighter maxima for fetching if we are a caching dirserver.
12109 Clip rather than rejecting.
12110 - Fetch cached running-routers from servers that serve it (that is,
12111 authdirservers and servers running 0.0.9rc5-cvs or later.)
12114 - Accept *:706 (silc) in default exit policy.
12115 - Implement new versioning format for post 0.1.
12116 - Support "foo.nickname.exit" addresses, to let Alice request the
12117 address "foo" as viewed by exit node "nickname". Based on a patch
12119 - Make tor --version --version dump the cvs Id of every file.
12122 Changes in version 0.0.9rc4 - 2004-11-28
12123 o Bugfixes on 0.0.8.1:
12124 - Make windows sockets actually non-blocking (oops), and handle
12125 win32 socket errors better.
12127 o Bugfixes on 0.0.9rc1:
12128 - Actually catch the -USR2 signal.
12131 Changes in version 0.0.9rc3 - 2004-11-25
12132 o Bugfixes on 0.0.8.1:
12133 - Flush the log file descriptor after we print "Tor opening log file",
12134 so we don't see those messages days later.
12136 o Bugfixes on 0.0.9rc1:
12137 - Make tor-resolve work again.
12138 - Avoid infinite loop in tor-resolve if tor hangs up on it.
12139 - Fix an assert trigger for clients/servers handling resolves.
12142 Changes in version 0.0.9rc2 - 2004-11-24
12143 o Bugfixes on 0.0.9rc1:
12144 - I broke socks5 support while fixing the eof bug.
12145 - Allow unitless bandwidths and intervals; they default to bytes
12147 - New servers don't start out hibernating; they are active until
12148 they run out of bytes, so they have a better estimate of how
12149 long it takes, and so their operators can know they're working.
12152 Changes in version 0.0.9rc1 - 2004-11-23
12153 o Bugfixes on 0.0.8.1:
12154 - Finally fix a bug that's been plaguing us for a year:
12155 With high load, circuit package window was reaching 0. Whenever
12156 we got a circuit-level sendme, we were reading a lot on each
12157 socket, but only writing out a bit. So we would eventually reach
12158 eof. This would be noticed and acted on even when there were still
12159 bytes sitting in the inbuf.
12160 - When poll() is interrupted, we shouldn't believe the revents values.
12162 o Bugfixes on 0.0.9pre6:
12163 - Fix hibernate bug that caused pre6 to be broken.
12164 - Don't keep rephist info for routers that haven't had activity for
12165 24 hours. (This matters now that clients have keys, since we track
12167 - Never call close_temp_logs while validating log options.
12168 - Fix backslash-escaping on tor.sh.in and torctl.in.
12171 - Implement weekly/monthly/daily accounting: now you specify your
12172 hibernation properties by
12173 AccountingMax N bytes|KB|MB|GB|TB
12174 AccountingStart day|week|month [day] HH:MM
12175 Defaults to "month 1 0:00".
12176 - Let bandwidth and interval config options be specified as 5 bytes,
12177 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
12178 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
12179 get back to normal.)
12180 - If your requested entry or exit node has advertised bandwidth 0,
12182 - Be more greedy about filling up relay cells -- we try reading again
12183 once we've processed the stuff we read, in case enough has arrived
12184 to fill the last cell completely.
12185 - Apply NT service patch from Osamu Fujino. Still needs more work.
12188 Changes in version 0.0.9pre6 - 2004-11-15
12189 o Bugfixes on 0.0.8.1:
12190 - Fix assert failure on malformed socks4a requests.
12191 - Use identity comparison, not nickname comparison, to choose which
12192 half of circuit-ID-space each side gets to use. This is needed
12193 because sometimes we think of a router as a nickname, and sometimes
12194 as a hex ID, and we can't predict what the other side will do.
12195 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
12196 write() call will fail and we handle it there.
12197 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
12198 and smartlist_len, which are two major profiling offenders.
12200 o Bugfixes on 0.0.9pre5:
12201 - Fix a bug in read_all that was corrupting config files on windows.
12202 - When we're raising the max number of open file descriptors to
12203 'unlimited', don't log that we just raised it to '-1'.
12204 - Include event code with events, as required by control-spec.txt.
12205 - Don't give a fingerprint when clients do --list-fingerprint:
12206 it's misleading, because it will never be the same again.
12207 - Stop using strlcpy in tor_strndup, since it was slowing us
12209 - Remove warn on startup about missing cached-directory file.
12210 - Make kill -USR1 work again.
12211 - Hibernate if we start tor during the "wait for wakeup-time" phase
12212 of an accounting interval. Log our hibernation plans better.
12213 - Authoritative dirservers now also cache their directory, so they
12214 have it on start-up.
12217 - Fetch running-routers; cache running-routers; compress
12218 running-routers; serve compressed running-routers.z
12219 - Add NSI installer script contributed by J Doe.
12220 - Commit VC6 and VC7 workspace/project files.
12221 - Commit a tor.spec for making RPM files, with help from jbash.
12222 - Add contrib/torctl.in contributed by Glenn Fink.
12223 - Implement the control-spec's SAVECONF command, to write your
12224 configuration to torrc.
12225 - Get cookie authentication for the controller closer to working.
12226 - Include control-spec.txt in the tarball.
12227 - When set_conf changes our server descriptor, upload a new copy.
12228 But don't upload it too often if there are frequent changes.
12229 - Document authentication config in man page, and document signals
12231 - Clean up confusing parts of man page and torrc.sample.
12232 - Make expand_filename handle ~ and ~username.
12233 - Use autoconf to enable largefile support where necessary. Use
12234 ftello where available, since ftell can fail at 2GB.
12235 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
12236 log more informatively.
12237 - Give a slightly more useful output for "tor -h".
12238 - Refuse application socks connections to port 0.
12239 - Check clock skew for verified servers, but allow unverified
12240 servers and clients to have any clock skew.
12241 - Break DirFetchPostPeriod into:
12242 - DirFetchPeriod for fetching full directory,
12243 - StatusFetchPeriod for fetching running-routers,
12244 - DirPostPeriod for posting server descriptor,
12245 - RendPostPeriod for posting hidden service descriptors.
12246 - Make sure the hidden service descriptors are at a random offset
12247 from each other, to hinder linkability.
12250 Changes in version 0.0.9pre5 - 2004-11-09
12251 o Bugfixes on 0.0.9pre4:
12252 - Fix a seg fault in unit tests (doesn't affect main program).
12253 - Fix an assert bug where a hidden service provider would fail if
12254 the first hop of his rendezvous circuit was down.
12255 - Hidden service operators now correctly handle version 1 style
12256 INTRODUCE1 cells (nobody generates them still, so not a critical
12258 - If do_hup fails, actually notice.
12259 - Handle more errnos from accept() without closing the listener.
12260 Some OpenBSD machines were closing their listeners because
12261 they ran out of file descriptors.
12262 - Send resolve cells to exit routers that are running a new
12263 enough version of the resolve code to work right.
12264 - Better handling of winsock includes on non-MSV win32 compilers.
12265 - Some people had wrapped their tor client/server in a script
12266 that would restart it whenever it died. This did not play well
12267 with our "shut down if your version is obsolete" code. Now people
12268 don't fetch a new directory if their local cached version is
12270 - Make our autogen.sh work on ksh as well as bash.
12273 - Hibernation: New config option "AccountingMaxKB" lets you
12274 set how many KBytes per month you want to allow your server to
12275 consume. Rather than spreading those bytes out evenly over the
12276 month, we instead hibernate for some of the month and pop up
12277 at a deterministic time, work until the bytes are consumed, then
12278 hibernate again. Config option "MonthlyAccountingStart" lets you
12279 specify which day of the month your billing cycle starts on.
12280 - Control interface: a separate program can now talk to your
12281 client/server over a socket, and get/set config options, receive
12282 notifications of circuits and streams starting/finishing/dying,
12283 bandwidth used, etc. The next step is to get some GUIs working.
12284 Let us know if you want to help out. See doc/control-spec.txt .
12285 - Ship a contrib/tor-control.py as an example script to interact
12286 with the control port.
12287 - "tor --hash-password zzyxz" will output a salted password for
12288 use in authenticating to the control interface.
12289 - New log format in config:
12290 "Log minsev[-maxsev] stdout|stderr|syslog" or
12291 "Log minsev[-maxsev] file /var/foo"
12294 - DirPolicy config option, to let people reject incoming addresses
12295 from their dirserver.
12296 - "tor --list-fingerprint" will list your identity key fingerprint
12298 - Add "pass" target for RedirectExit, to make it easier to break
12299 out of a sequence of RedirectExit rules.
12300 - Clients now generate a TLS cert too, in preparation for having
12301 them act more like real nodes.
12302 - Ship src/win32/ in the tarball, so people can use it to build.
12303 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
12305 - New "router-status" line in directory, to better bind each verified
12306 nickname to its identity key.
12307 - Deprecate unofficial config option abbreviations, and abbreviations
12308 not on the command line.
12309 - Add a pure-C tor-resolve implementation.
12310 - Use getrlimit and friends to ensure we can reach MaxConn (currently
12311 1024) file descriptors.
12313 o Code security improvements, inspired by Ilja:
12314 - Replace sprintf with snprintf. (I think they were all safe, but
12316 - Replace strcpy/strncpy with strlcpy in more places.
12317 - Avoid strcat; use snprintf or strlcat instead.
12318 - snprintf wrapper with consistent (though not C99) overflow behavior.
12321 Changes in version 0.0.9pre4 - 2004-10-17
12322 o Bugfixes on 0.0.9pre3:
12323 - If the server doesn't specify an exit policy, use the real default
12324 exit policy, not reject *:*.
12325 - Ignore fascistfirewall when uploading/downloading hidden service
12326 descriptors, since we go through Tor for those; and when using
12327 an HttpProxy, since we assume it can reach them all.
12328 - When looking for an authoritative dirserver, use only the ones
12329 configured at boot. Don't bother looking in the directory.
12330 - The rest of the fix for get_default_conf_file() on older win32.
12331 - Make 'Routerfile' config option obsolete.
12334 - New 'MyFamily nick1,...' config option for a server to
12335 specify other servers that shouldn't be used in the same circuit
12336 with it. Only believed if nick1 also specifies us.
12337 - New 'NodeFamily nick1,nick2,...' config option for a client to
12338 specify nodes that it doesn't want to use in the same circuit.
12339 - New 'Redirectexit pattern address:port' config option for a
12340 server to redirect exit connections, e.g. to a local squid.
12343 Changes in version 0.0.9pre3 - 2004-10-13
12344 o Bugfixes on 0.0.8.1:
12345 - Better torrc example lines for dirbindaddress and orbindaddress.
12346 - Improved bounds checking on parsed ints (e.g. config options and
12347 the ones we find in directories.)
12348 - Better handling of size_t vs int, so we're more robust on 64
12350 - Fix the rest of the bug where a newly started OR would appear
12351 as unverified even after we've added his fingerprint and hupped
12353 - Fix a bug from 0.0.7: when read() failed on a stream, we would
12354 close it without sending back an end. So 'connection refused'
12355 would simply be ignored and the user would get no response.
12357 o Bugfixes on 0.0.9pre2:
12358 - Serving the cached-on-disk directory to people is bad. We now
12359 provide no directory until we've fetched a fresh one.
12360 - Workaround for bug on windows where cached-directories get crlf
12362 - Make get_default_conf_file() work on older windows too.
12363 - If we write a *:* exit policy line in the descriptor, don't write
12364 any more exit policy lines.
12367 - Use only 0.0.9pre1 and later servers for resolve cells.
12368 - Make the dirservers file obsolete.
12369 - Include a dir-signing-key token in directories to tell the
12370 parsing entity which key is being used to sign.
12371 - Remove the built-in bulky default dirservers string.
12372 - New config option "Dirserver %s:%d [fingerprint]", which can be
12373 repeated as many times as needed. If no dirservers specified,
12374 default to moria1,moria2,tor26.
12375 - Make moria2 advertise a dirport of 80, so people behind firewalls
12376 will be able to get a directory.
12377 - Http proxy support
12378 - Dirservers translate requests for http://%s:%d/x to /x
12379 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
12380 be routed through this host.
12381 - Clients ask for /tor/x rather than /x for new enough dirservers.
12382 This way we can one day coexist peacefully with apache.
12383 - Clients specify a "Host: %s%d" http header, to be compatible
12384 with more proxies, and so running squid on an exit node can work.
12387 Changes in version 0.0.8.1 - 2004-10-13
12389 - Fix a seg fault that can be triggered remotely for Tor
12390 clients/servers with an open dirport.
12391 - Fix a rare assert trigger, where routerinfos for entries in
12392 our cpath would expire while we're building the path.
12393 - Fix a bug in OutboundBindAddress so it (hopefully) works.
12394 - Fix a rare seg fault for people running hidden services on
12395 intermittent connections.
12396 - Fix a bug in parsing opt keywords with objects.
12397 - Fix a stale pointer assert bug when a stream detaches and
12399 - Fix a string format vulnerability (probably not exploitable)
12400 in reporting stats locally.
12401 - Fix an assert trigger: sometimes launching circuits can fail
12402 immediately, e.g. because too many circuits have failed recently.
12403 - Fix a compile warning on 64 bit platforms.
12406 Changes in version 0.0.9pre2 - 2004-10-03
12408 - Make fetching a cached directory work for 64-bit platforms too.
12409 - Make zlib.h a required header, not an optional header.
12412 Changes in version 0.0.9pre1 - 2004-10-01
12414 - Stop using separate defaults for no-config-file and
12415 empty-config-file. Now you have to explicitly turn off SocksPort,
12416 if you don't want it open.
12417 - Fix a bug in OutboundBindAddress so it (hopefully) works.
12418 - Improve man page to mention more of the 0.0.8 features.
12419 - Fix a rare seg fault for people running hidden services on
12420 intermittent connections.
12421 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
12423 - Fix more dns related bugs: send back resolve_failed and end cells
12424 more reliably when the resolve fails, rather than closing the
12425 circuit and then trying to send the cell. Also attach dummy resolve
12426 connections to a circuit *before* calling dns_resolve(), to fix
12427 a bug where cached answers would never be sent in RESOLVED cells.
12428 - When we run out of disk space, or other log writing error, don't
12429 crash. Just stop logging to that log and continue.
12430 - We were starting to daemonize before we opened our logs, so if
12431 there were any problems opening logs, we would complain to stderr,
12432 which wouldn't work, and then mysteriously exit.
12433 - Fix a rare bug where sometimes a verified OR would connect to us
12434 before he'd uploaded his descriptor, which would cause us to
12435 assign conn->nickname as though he's unverified. Now we look through
12436 the fingerprint list to see if he's there.
12437 - Fix a rare assert trigger, where routerinfos for entries in
12438 our cpath would expire while we're building the path.
12441 - Clients can ask dirservers for /dir.z to get a compressed version
12442 of the directory. Only works for servers running 0.0.9, of course.
12443 - Make clients cache directories and use them to seed their router
12444 lists at startup. This means clients have a datadir again.
12445 - Configuration infrastructure support for warning on obsolete
12447 - Respond to content-encoding headers by trying to uncompress as
12449 - Reply with a deflated directory when a client asks for "dir.z".
12450 We could use allow-encodings instead, but allow-encodings isn't
12451 specified in HTTP 1.0.
12452 - Raise the max dns workers from 50 to 100.
12453 - Discourage people from setting their dirfetchpostperiod more often
12454 than once per minute.
12455 - Protect dirservers from overzealous descriptor uploading -- wait
12456 10 seconds after directory gets dirty, before regenerating.
12459 Changes in version 0.0.8 - 2004-08-25
12460 o Port it to SunOS 5.9 / Athena
12463 Changes in version 0.0.8rc2 - 2004-08-20
12464 o Make it compile on cygwin again.
12465 o When picking unverified routers, skip those with low uptime and/or
12466 low bandwidth, depending on what properties you care about.
12469 Changes in version 0.0.8rc1 - 2004-08-18
12470 o Changes from 0.0.7.3:
12472 - Fix assert triggers: if the other side returns an address 0.0.0.0,
12473 don't put it into the client dns cache.
12474 - If a begin failed due to exit policy, but we believe the IP address
12475 should have been allowed, switch that router to exitpolicy reject *:*
12476 until we get our next directory.
12478 - Clients choose nodes proportional to advertised bandwidth.
12479 - Avoid using nodes with low uptime as introduction points.
12480 - Handle servers with dynamic IP addresses: don't replace
12481 options->Address with the resolved one at startup, and
12482 detect our address right before we make a routerinfo each time.
12483 - 'FascistFirewall' option to pick dirservers and ORs on specific
12484 ports; plus 'FirewallPorts' config option to tell FascistFirewall
12485 which ports are open. (Defaults to 80,443)
12486 - Be more aggressive about trying to make circuits when the network
12487 has changed (e.g. when you unsuspend your laptop).
12488 - Check for time skew on http headers; report date in response to
12490 - If the entrynode config line has only one node, don't pick it as
12492 - Add strict{entry|exit}nodes config options. If set to 1, then
12493 we refuse to build circuits that don't include the specified entry
12495 - OutboundBindAddress config option, to bind to a specific
12496 IP address for outgoing connect()s.
12497 - End truncated log entries (e.g. directories) with "[truncated]".
12499 o Patches to 0.0.8preX:
12501 - Patches to compile and run on win32 again (maybe)?
12502 - Fix crash when looking for ~/.torrc with no $HOME set.
12503 - Fix a race bug in the unit tests.
12504 - Handle verified/unverified name collisions better when new
12505 routerinfo's arrive in a directory.
12506 - Sometimes routers were getting entered into the stats before
12507 we'd assigned their identity_digest. Oops.
12508 - Only pick and establish intro points after we've gotten a
12511 - AllowUnverifiedNodes config option to let circuits choose no-name
12512 routers in entry,middle,exit,introduction,rendezvous positions.
12513 Allow middle and rendezvous positions by default.
12514 - Add a man page for tor-resolve.
12517 Changes in version 0.0.7.3 - 2004-08-12
12518 o Stop dnsworkers from triggering an assert failure when you
12519 ask them to resolve the host "".
12522 Changes in version 0.0.8pre3 - 2004-08-09
12523 o Changes from 0.0.7.2:
12524 - Allow multiple ORs with same nickname in routerlist -- now when
12525 people give us one identity key for a nickname, then later
12526 another, we don't constantly complain until the first expires.
12527 - Remember used bandwidth (both in and out), and publish 15-minute
12528 snapshots for the past day into our descriptor.
12529 - You can now fetch $DIRURL/running-routers to get just the
12530 running-routers line, not the whole descriptor list. (But
12531 clients don't use this yet.)
12532 - When people mistakenly use Tor as an http proxy, point them
12533 at the tor-doc.html rather than the INSTALL.
12534 - Remove our mostly unused -- and broken -- hex_encode()
12535 function. Use base16_encode() instead. (Thanks to Timo Lindfors
12536 for pointing out this bug.)
12537 - Rotate onion keys every 12 hours, not every 2 hours, so we have
12538 fewer problems with people using the wrong key.
12539 - Change the default exit policy to reject the default edonkey,
12540 kazaa, gnutella ports.
12541 - Add replace_file() to util.[ch] to handle win32's rename().
12543 o Changes from 0.0.8preX:
12544 - Fix two bugs in saving onion keys to disk when rotating, so
12545 hopefully we'll get fewer people using old onion keys.
12546 - Fix an assert error that was making SocksPolicy not work.
12547 - Be willing to expire routers that have an open dirport -- it's
12548 just the authoritative dirservers we want to not forget.
12549 - Reject tor-resolve requests for .onion addresses early, so we
12550 don't build a whole rendezvous circuit and then fail.
12551 - When you're warning a server that he's unverified, don't cry
12552 wolf unpredictably.
12553 - Fix a race condition: don't try to extend onto a connection
12554 that's still handshaking.
12555 - For servers in clique mode, require the conn to be open before
12556 you'll choose it for your path.
12557 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
12558 end relay cell, etc.
12559 - Measure bandwidth capacity over the last 24 hours, not just 12
12560 - Bugfix: authoritative dirservers were making and signing a new
12561 directory for each client, rather than reusing the cached one.
12564 Changes in version 0.0.8pre2 - 2004-08-04
12565 o Changes from 0.0.7.2:
12567 - Check directory signature _before_ you decide whether you're
12568 you're running an obsolete version and should exit.
12569 - Check directory signature _before_ you parse the running-routers
12570 list to decide who's running or verified.
12571 - Bugfixes and features:
12572 - Check return value of fclose while writing to disk, so we don't
12573 end up with broken files when servers run out of disk space.
12574 - Log a warning if the user uses an unsafe socks variant, so people
12575 are more likely to learn about privoxy or socat.
12576 - Dirservers now include RFC1123-style dates in the HTTP headers,
12577 which one day we will use to better detect clock skew.
12579 o Changes from 0.0.8pre1:
12580 - Make it compile without warnings again on win32.
12581 - Log a warning if you're running an unverified server, to let you
12582 know you might want to get it verified.
12583 - Only pick a default nickname if you plan to be a server.
12586 Changes in version 0.0.8pre1 - 2004-07-23
12588 - Made our unit tests compile again on OpenBSD 3.5, and tor
12589 itself compile again on OpenBSD on a sparc64.
12590 - We were neglecting milliseconds when logging on win32, so
12591 everything appeared to happen at the beginning of each second.
12593 o Protocol changes:
12594 - 'Extend' relay cell payloads now include the digest of the
12595 intended next hop's identity key. Now we can verify that we're
12596 extending to the right router, and also extend to routers we
12597 hadn't heard of before.
12600 - Tor nodes can now act as relays (with an advertised ORPort)
12601 without being manually verified by the dirserver operators.
12602 - Uploaded descriptors of unverified routers are now accepted
12603 by the dirservers, and included in the directory.
12604 - Verified routers are listed by nickname in the running-routers
12605 list; unverified routers are listed as "$<fingerprint>".
12606 - We now use hash-of-identity-key in most places rather than
12607 nickname or addr:port, for improved security/flexibility.
12608 - To avoid Sybil attacks, paths still use only verified servers.
12609 But now we have a chance to play around with hybrid approaches.
12610 - Nodes track bandwidth usage to estimate capacity (not used yet).
12611 - ClientOnly option for nodes that never want to become servers.
12612 - Directory caching.
12613 - "AuthoritativeDir 1" option for the official dirservers.
12614 - Now other nodes (clients and servers) will cache the latest
12615 directory they've pulled down.
12616 - They can enable their DirPort to serve it to others.
12617 - Clients will pull down a directory from any node with an open
12618 DirPort, and check the signature/timestamp correctly.
12619 - Authoritative dirservers now fetch directories from other
12620 authdirservers, to stay better synced.
12621 - Running-routers list tells who's down also, along with noting
12622 if they're verified (listed by nickname) or unverified (listed
12624 - Allow dirservers to serve running-router list separately.
12625 This isn't used yet.
12626 - ORs connect-on-demand to other ORs
12627 - If you get an extend cell to an OR you're not connected to,
12628 connect, handshake, and forward the create cell.
12629 - The authoritative dirservers stay connected to everybody,
12630 and everybody stays connected to 0.0.7 servers, but otherwise
12631 clients/servers expire unused connections after 5 minutes.
12632 - When servers get a sigint, they delay 30 seconds (refusing new
12633 connections) then exit. A second sigint causes immediate exit.
12634 - File and name management:
12635 - Look for .torrc if no CONFDIR "torrc" is found.
12636 - If no datadir is defined, then choose, make, and secure ~/.tor
12638 - If torrc not found, exitpolicy reject *:*.
12639 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
12640 - If no nickname is defined, derive default from hostname.
12641 - Rename secret key files, e.g. identity.key -> secret_id_key,
12642 to discourage people from mailing their identity key to tor-ops.
12643 - Refuse to build a circuit before the directory has arrived --
12644 it won't work anyway, since you won't know the right onion keys
12646 - Try other dirservers immediately if the one you try is down. This
12647 should tolerate down dirservers better now.
12648 - Parse tor version numbers so we can do an is-newer-than check
12649 rather than an is-in-the-list check.
12650 - New socks command 'resolve', to let us shim gethostbyname()
12652 - A 'tor_resolve' script to access the socks resolve functionality.
12653 - A new socks-extensions.txt doc file to describe our
12654 interpretation and extensions to the socks protocols.
12655 - Add a ContactInfo option, which gets published in descriptor.
12656 - Publish OR uptime in descriptor (and thus in directory) too.
12657 - Write tor version at the top of each log file
12658 - New docs in the tarball:
12660 - Document that you should proxy your SSL traffic too.
12663 Changes in version 0.0.7.2 - 2004-07-07
12664 o A better fix for the 0.0.0.0 problem, that will hopefully
12665 eliminate the remaining related assertion failures.
12668 Changes in version 0.0.7.1 - 2004-07-04
12669 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
12670 since internally we use 0.0.0.0 to signify "not yet resolved".
12673 Changes in version 0.0.7 - 2004-06-07
12674 o Updated the man page to reflect the new features.
12677 Changes in version 0.0.7rc2 - 2004-06-06
12678 o Changes from 0.0.7rc1:
12679 - Make it build on Win32 again.
12680 o Changes from 0.0.6.2:
12681 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
12685 Changes in version 0.0.7rc1 - 2004-06-02
12687 - On sighup, we were adding another log without removing the first
12688 one. So log messages would get duplicated n times for n sighups.
12689 - Several cases of using a connection after we'd freed it. The
12690 problem was that connections that are pending resolve are in both
12691 the pending_resolve tree, and also the circuit's resolving_streams
12692 list. When you want to remove one, you must remove it from both.
12693 - Fix a double-mark-for-close where an end cell arrived for a
12694 resolving stream, and then the resolve failed.
12695 - Check directory signatures based on name of signer, not on whom
12696 we got the directory from. This will let us cache directories more
12699 - Crank up some of our constants to handle more users.
12702 Changes in version 0.0.7pre1 - 2004-06-02
12703 o Fixes for crashes and other obnoxious bugs:
12704 - Fix an epipe bug: sometimes when directory connections failed
12705 to connect, we would give them a chance to flush before closing
12707 - When we detached from a circuit because of resolvefailed, we
12708 would immediately try the same circuit twice more, and then
12709 give up on the resolve thinking we'd tried three different
12711 - Limit the number of intro circuits we'll attempt to build for a
12712 hidden service per 15-minute period.
12713 - Check recommended-software string *early*, before actually parsing
12714 the directory. Thus we can detect an obsolete version and exit,
12715 even if the new directory format doesn't parse.
12716 o Fixes for security bugs:
12717 - Remember which nodes are dirservers when you startup, and if a
12718 random OR enables his dirport, don't automatically assume he's
12719 a trusted dirserver.
12721 - Directory connections were asking the wrong poll socket to
12722 start writing, and not asking themselves to start writing.
12723 - When we detached from a circuit because we sent a begin but
12724 didn't get a connected, we would use it again the first time;
12725 but after that we would correctly switch to a different one.
12726 - Stop warning when the first onion decrypt attempt fails; they
12727 will sometimes legitimately fail now that we rotate keys.
12728 - Override unaligned-access-ok check when $host_cpu is ia64 or
12729 arm. Apparently they allow it but the kernel whines.
12730 - Dirservers try to reconnect periodically too, in case connections
12732 - Fix some memory leaks in directory servers.
12733 - Allow backslash in Win32 filenames.
12734 - Made Tor build complain-free on FreeBSD, hopefully without
12735 breaking other BSD builds. We'll see.
12737 - Doxygen markup on all functions and global variables.
12738 - Make directory functions update routerlist, not replace it. So
12739 now directory disagreements are not so critical a problem.
12740 - Remove the upper limit on number of descriptors in a dirserver's
12741 directory (not that we were anywhere close).
12742 - Allow multiple logfiles at different severity ranges.
12743 - Allow *BindAddress to specify ":port" rather than setting *Port
12744 separately. Allow multiple instances of each BindAddress config
12745 option, so you can bind to multiple interfaces if you want.
12746 - Allow multiple exit policy lines, which are processed in order.
12747 Now we don't need that huge line with all the commas in it.
12748 - Enable accept/reject policies on SOCKS connections, so you can bind
12749 to 0.0.0.0 but still control who can use your OP.
12752 Changes in version 0.0.6.2 - 2004-05-16
12753 o Our integrity-checking digest was checking only the most recent cell,
12754 not the previous cells like we'd thought.
12755 Thanks to Stefan Mark for finding the flaw!
12758 Changes in version 0.0.6.1 - 2004-05-06
12759 o Fix two bugs in our AES counter-mode implementation (this affected
12760 onion-level stream encryption, but not TLS-level). It turns
12761 out we were doing something much more akin to a 16-character
12762 polyalphabetic cipher. Oops.
12763 Thanks to Stefan Mark for finding the flaw!
12764 o Retire moria3 as a directory server, and add tor26 as a directory
12768 Changes in version 0.0.6 - 2004-05-02
12769 [version bump only]
12772 Changes in version 0.0.6rc4 - 2004-05-01
12773 o Update the built-in dirservers list to use the new directory format
12774 o Fix a rare seg fault: if a node offering a hidden service attempts
12775 to build a circuit to Alice's rendezvous point and fails before it
12776 reaches the last hop, it retries with a different circuit, but
12778 o Handle windows socket errors correctly.
12781 Changes in version 0.0.6rc3 - 2004-04-28
12782 o Don't expire non-general excess circuits (if we had enough
12783 circuits open, we were expiring rendezvous circuits -- even
12784 when they had a stream attached. oops.)
12785 o Fetch randomness from /dev/urandom better (not via fopen/fread)
12786 o Better debugging for tls errors
12787 o Some versions of openssl have an SSL_pending function that erroneously
12788 returns bytes when there is a non-application record pending.
12789 o Set Content-Type on the directory and hidserv descriptor.
12790 o Remove IVs from cipher code, since AES-ctr has none.
12791 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
12792 o We were using an array of length zero in a few places.
12793 o win32's gethostbyname can't resolve an IP to an IP.
12794 o win32's close can't close a socket.
12797 Changes in version 0.0.6rc2 - 2004-04-26
12798 o Fix a bug where we were closing tls connections intermittently.
12799 It turns out openssl keeps its errors around -- so if an error
12800 happens, and you don't ask about it, and then another openssl
12801 operation happens and succeeds, and you ask if there was an error,
12802 it tells you about the first error. Fun fun.
12803 o Fix a bug that's been lurking since 27 may 03 (!)
12804 When passing back a destroy cell, we would use the wrong circ id.
12805 'Mostly harmless', but still worth fixing.
12806 o Since we don't support truncateds much, don't bother sending them;
12807 just close the circ.
12808 o check for <machine/limits.h> so we build on NetBSD again (I hope).
12809 o don't crash if a conn that sent a begin has suddenly lost its circuit
12810 (this was quite rare).
12813 Changes in version 0.0.6rc1 - 2004-04-25
12814 o We now rotate link (tls context) keys and onion keys.
12815 o CREATE cells now include oaep padding, so you can tell
12816 if you decrypted them correctly.
12817 o Add bandwidthburst to server descriptor.
12818 o Directories now say which dirserver signed them.
12819 o Use a tor_assert macro that logs failed assertions too.
12822 Changes in version 0.0.6pre5 - 2004-04-18
12823 o changes from 0.0.6pre4:
12824 - make tor build on broken freebsd 5.2 installs
12825 - fix a failed assert when you try an intro point, get a nack, and try
12826 a second one and it works.
12827 - when alice uses a port that the hidden service doesn't accept,
12828 it now sends back an end cell (denied by exit policy). otherwise
12829 alice would just have to wait to time out.
12830 - fix another rare bug: when we had tried all the intro
12831 points for a hidden service, we fetched the descriptor
12832 again, but we left our introcirc thinking it had already
12833 sent an intro, so it kept waiting for a response...
12834 - bugfix: when you sleep your hidden-service laptop, as soon
12835 as it wakes up it tries to upload a service descriptor, but
12836 socketpair fails for some reason (localhost not up yet?).
12837 now we simply give up on that upload, and we'll try again later.
12838 i'd still like to find the bug though.
12839 - if an intro circ waiting for an ack dies before getting one, then
12841 - we were reusing stale service descriptors and refetching usable
12845 Changes in version 0.0.6pre4 - 2004-04-14
12846 o changes from 0.0.6pre3:
12847 - when bob fails to connect to the rendezvous point, and his
12848 circ didn't fail because of the rendezvous point itself, then
12849 he retries a couple of times
12850 - we expire introduction and rendezvous circs more thoroughly
12851 (sometimes they were hanging around forever)
12852 - we expire unattached rendezvous streams that have been around
12853 too long (they were sticking around forever).
12854 - fix a measly fencepost error that was crashing everybody with
12858 Changes in version 0.0.6pre3 - 2004-04-14
12859 o changes from 0.0.6pre2:
12860 - make hup work again
12861 - fix some memory leaks for dirservers
12862 - allow more skew in rendezvous descriptor timestamps, to help
12863 handle people like blanu who don't know what time it is
12864 - normal circs are 3 hops, but some rend/intro circs are 4, if
12865 the initiator doesn't get to choose the last hop
12866 - send acks for introductions, so alice can know whether to try
12868 - bob publishes intro points more correctly
12869 o changes from 0.0.5:
12870 - fix an assert trigger that's been plaguing us since the days
12871 of 0.0.2prexx (thanks weasel!)
12872 - retry stream correctly when we fail to connect because of
12873 exit-policy-reject (should try another) or can't-resolve-address
12874 (also should try another, because dns on random internet servers
12876 - when we hup a dirserver and we've *removed* a server from the
12877 approved-routers list, now we remove that server from the
12878 in-memory directories too
12881 Changes in version 0.0.6pre2 - 2004-04-08
12882 o We fixed our base32 implementation. Now it works on all architectures.
12885 Changes in version 0.0.6pre1 - 2004-04-08
12887 - Hidden services and rendezvous points are implemented. Go to
12888 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
12889 hidden services. (This only works via a socks4a proxy such as
12890 Privoxy, and currently it's quite slow.)
12893 Changes in version 0.0.5 - 2004-03-30
12894 [version bump only]
12897 Changes in version 0.0.5rc3 - 2004-03-29
12898 o Install torrc as torrc.sample -- we no longer clobber your
12900 o Re-enable recommendedversion checking (we broke it in rc2, oops)
12901 o Add in a 'notice' log level for things the operator should hear
12902 but that aren't warnings
12905 Changes in version 0.0.5rc2 - 2004-03-29
12906 o Hold socks connection open until reply is flushed (if possible)
12907 o Make exit nodes resolve IPs to IPs immediately, rather than asking
12908 the dns farm to do it.
12909 o Fix c99 aliasing warnings in rephist.c
12910 o Don't include server descriptors that are older than 24 hours in the
12912 o Give socks 'reject' replies their whole 15s to attempt to flush,
12913 rather than seeing the 60s timeout and assuming the flush had failed.
12914 o Clean automake droppings from the cvs repository
12917 Changes in version 0.0.5rc1 - 2004-03-28
12918 o Fix mangled-state bug in directory fetching (was causing sigpipes).
12919 o Only build circuits after we've fetched the directory: clients were
12920 using only the directory servers before they'd fetched a directory.
12921 This also means longer startup time; so it goes.
12922 o Fix an assert trigger where an OP would fail to handshake, and we'd
12923 expect it to have a nickname.
12924 o Work around a tsocks bug: do a socks reject when AP connection dies
12925 early, else tsocks goes into an infinite loop.
12928 Changes in version 0.0.4 - 2004-03-26
12929 o When connecting to a dirserver or OR and the network is down,
12933 Changes in version 0.0.3 - 2004-03-26
12934 o Warn and fail if server chose a nickname with illegal characters
12935 o Port to Solaris and Sparc:
12936 - include missing header fcntl.h
12937 - have autoconf find -lsocket -lnsl automatically
12938 - deal with hardware word alignment
12939 - make uname() work (solaris has a different return convention)
12940 - switch from using signal() to sigaction()
12941 o Preliminary work on reputation system:
12942 - Keep statistics on success/fail of connect attempts; they're published
12943 by kill -USR1 currently.
12944 - Add a RunTesting option to try to learn link state by creating test
12945 circuits, even when SocksPort is off.
12946 - Remove unused open circuits when there are too many.
12949 Changes in version 0.0.2 - 2004-03-19
12950 - Include strlcpy and strlcat for safer string ops
12951 - define INADDR_NONE so we compile (but still not run) on solaris
12954 Changes in version 0.0.2pre27 - 2004-03-14
12956 - Allow internal tor networks (we were rejecting internal IPs,
12957 now we allow them if they're set explicitly).
12958 - And fix a few endian issues.
12961 Changes in version 0.0.2pre26 - 2004-03-14
12963 - If a stream times out after 15s without a connected cell, don't
12964 try that circuit again: try a new one.
12965 - Retry streams at most 4 times. Then give up.
12966 - When a dirserver gets a descriptor from an unknown router, it
12967 logs its fingerprint (so the dirserver operator can choose to
12968 accept it even without mail from the server operator).
12969 - Inform unapproved servers when we reject their descriptors.
12970 - Make tor build on Windows again. It works as a client, who knows
12972 - Clearer instructions in the torrc for how to set up a server.
12973 - Be more efficient about reading fd's when our global token bucket
12974 (used for rate limiting) becomes empty.
12976 - Stop asserting that computers always go forward in time. It's
12978 - When we sent a cell (e.g. destroy) and then marked an OR connection
12979 expired, we might close it before finishing a flush if the other
12980 side isn't reading right then.
12981 - Don't allow dirservers to start if they haven't defined
12982 RecommendedVersions
12983 - We were caching transient dns failures. Oops.
12984 - Prevent servers from publishing an internal IP as their address.
12985 - Address a strcat vulnerability in circuit.c
12988 Changes in version 0.0.2pre25 - 2004-03-04
12990 - Put the OR's IP in its router descriptor, not its fqdn. That way
12991 we'll stop being stalled by gethostbyname for nodes with flaky dns,
12994 - If the user typed in an address that didn't resolve, the server
12998 Changes in version 0.0.2pre24 - 2004-03-03
13000 - Fix an assertion failure in dns.c, where we were trying to dequeue
13001 a pending dns resolve even if it wasn't pending
13002 - Fix a spurious socks5 warning about still trying to write after the
13003 connection is finished.
13004 - Hold certain marked_for_close connections open until they're finished
13005 flushing, rather than losing bytes by closing them too early.
13006 - Correctly report the reason for ending a stream
13007 - Remove some duplicate calls to connection_mark_for_close
13008 - Put switch_id and start_daemon earlier in the boot sequence, so it
13009 will actually try to chdir() to options.DataDirectory
13010 - Make 'make test' exit(1) if a test fails; fix some unit tests
13011 - Make tor fail when you use a config option it doesn't know about,
13012 rather than warn and continue.
13013 - Make --version work
13014 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
13017 Changes in version 0.0.2pre23 - 2004-02-29
13019 - Print a statement when the first circ is finished, so the user
13020 knows it's working.
13021 - If a relay cell is unrecognized at the end of the circuit,
13022 send back a destroy. (So attacks to mutate cells are more
13024 - New config option 'excludenodes' to avoid certain nodes for circuits.
13025 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
13026 so you can collect coredumps there.
13028 - Fix a bug in tls flushing where sometimes data got wedged and
13029 didn't flush until more data got sent. Hopefully this bug was
13030 a big factor in the random delays we were seeing.
13031 - Make 'connected' cells include the resolved IP, so the client
13032 dns cache actually gets populated.
13033 - Disallow changing from ORPort=0 to ORPort>0 on hup.
13034 - When we time-out on a stream and detach from the circuit, send an
13035 end cell down it first.
13036 - Only warn about an unknown router (in exitnodes, entrynodes,
13037 excludenodes) after we've fetched a directory.
13040 Changes in version 0.0.2pre22 - 2004-02-26
13042 - Servers publish less revealing uname information in descriptors.
13043 - More memory tracking and assertions, to crash more usefully when
13045 - If the default torrc isn't there, just use some default defaults.
13046 Plus provide an internal dirservers file if they don't have one.
13047 - When the user tries to use Tor as an http proxy, give them an http
13048 501 failure explaining that we're a socks proxy.
13049 - Dump a new router.desc on hup, to help confused people who change
13050 their exit policies and then wonder why router.desc doesn't reflect
13052 - Clean up the generic tor.sh init script that we ship with.
13054 - If the exit stream is pending on the resolve, and a destroy arrives,
13055 then the stream wasn't getting removed from the pending list. I
13056 think this was the one causing recent server crashes.
13057 - Use a more robust poll on OSX 10.3, since their poll is flaky.
13058 - When it couldn't resolve any dirservers, it was useless from then on.
13059 Now it reloads the RouterFile (or default dirservers) if it has no
13061 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
13062 many users don't even *have* a /usr/local/sbin/.
13065 Changes in version 0.0.2pre21 - 2004-02-18
13067 - There's a ChangeLog file that actually reflects the changelog.
13068 - There's a 'torify' wrapper script, with an accompanying
13069 tor-tsocks.conf, that simplifies the process of using tsocks for
13070 tor. It even has a man page.
13071 - The tor binary gets installed to sbin rather than bin now.
13072 - Retry streams where the connected cell hasn't arrived in 15 seconds
13073 - Clean up exit policy handling -- get the default out of the torrc,
13074 so we can update it without forcing each server operator to fix
13076 - Allow imaps and pop3s in default exit policy
13078 - Prevent picking middleman nodes as the last node in the circuit
13081 Changes in version 0.0.2pre20 - 2004-01-30
13083 - We now have a deb package, and it's in debian unstable. Go to
13084 it, apt-getters. :)
13085 - I've split the TotalBandwidth option into BandwidthRate (how many
13086 bytes per second you want to allow, long-term) and
13087 BandwidthBurst (how many bytes you will allow at once before the cap
13088 kicks in). This better token bucket approach lets you, say, set
13089 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
13090 performance while not exceeding your monthly bandwidth quota.
13091 - Push out a tls record's worth of data once you've got it, rather
13092 than waiting until you've read everything waiting to be read. This
13093 may improve performance by pipelining better. We'll see.
13094 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
13095 from failed circuits (if they haven't been connected yet) and attach
13097 - Expire old streams that haven't managed to connect. Some day we'll
13098 have them reattach to new circuits instead.
13101 - Fix several memory leaks that were causing servers to become bloated
13103 - Fix a few very rare assert triggers. A few more remain.
13104 - Setuid to User _before_ complaining about running as root.
13107 Changes in version 0.0.2pre19 - 2004-01-07
13109 - Fix deadlock condition in dns farm. We were telling a child to die by
13110 closing the parent's file descriptor to him. But newer children were
13111 inheriting the open file descriptor from the parent, and since they
13112 weren't closing it, the socket never closed, so the child never read
13113 eof, so he never knew to exit. Similarly, dns workers were holding
13114 open other sockets, leading to all sorts of chaos.
13115 - New cleaner daemon() code for forking and backgrounding.
13116 - If you log to a file, it now prints an entry at the top of the
13117 logfile so you know it's working.
13118 - The onionskin challenge length was 30 bytes longer than necessary.
13119 - Started to patch up the spec so it's not quite so out of date.
13122 Changes in version 0.0.2pre18 - 2004-01-02
13124 - Fix endian issues with the 'integrity' field in the relay header.
13125 - Fix a potential bug where connections in state
13126 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
13129 Changes in version 0.0.2pre17 - 2003-12-30
13131 - Made --debuglogfile (or any second log file, actually) work.
13132 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
13133 adversary could force us into an infinite loop.
13136 - Each onionskin handshake now includes a hash of the computed key,
13137 to prove the server's identity and help perfect forward secrecy.
13138 - Changed cell size from 256 to 512 bytes (working toward compatibility
13140 - Changed cell length to 2 bytes, and moved it to the relay header.
13141 - Implemented end-to-end integrity checking for the payloads of
13143 - Separated streamid from 'recognized' (otherwise circuits will get
13144 messed up when we try to have streams exit from the middle). We
13145 use the integrity-checking to confirm that a cell is addressed to
13147 - Randomize the initial circid and streamid values, so an adversary who
13148 breaks into a node can't learn how many circuits or streams have
13152 Changes in version 0.0.2pre16 - 2003-12-14
13154 - Fixed a bug that made HUP trigger an assert
13155 - Fixed a bug where a circuit that immediately failed wasn't being
13156 counted as a failed circuit in counting retries.
13159 - Now we close the circuit when we get a truncated cell: otherwise we're
13160 open to an anonymity attack where a bad node in the path truncates
13161 the circuit and then we open streams at him.
13162 - Add port ranges to exit policies
13163 - Add a conservative default exit policy
13164 - Warn if you're running tor as root
13165 - on HUP, retry OR connections and close/rebind listeners
13166 - options.EntryNodes: try these nodes first when picking the first node
13167 - options.ExitNodes: if your best choices happen to include any of
13168 your preferred exit nodes, you choose among just those preferred
13170 - options.ExcludedNodes: nodes that are never picked in path building
13173 Changes in version 0.0.2pre15 - 2003-12-03
13174 o Robustness and bugfixes:
13175 - Sometimes clients would cache incorrect DNS resolves, which would
13176 really screw things up.
13177 - An OP that goes offline would slowly leak all its sockets and stop
13179 - A wide variety of bugfixes in exit node selection, exit policy
13180 handling, and processing pending streams when a new circuit is
13182 - Pick nodes for a path only from those the directory says are up
13183 - Choose randomly from all running dirservers, not always the first one
13184 - Increase allowed http header size for directory fetch.
13185 - Stop writing to stderr (if we're daemonized it will be closed).
13186 - Enable -g always, so cores will be more useful to me.
13187 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
13190 - Wrote a man page. It lists commonly used options.
13193 - Change default loglevel to warn.
13194 - Make PidFile default to null rather than littering in your CWD.
13195 - OnionRouter config option is now obsolete. Instead it just checks
13197 - Moved to a single unified torrc file for both clients and servers.
13200 Changes in version 0.0.2pre14 - 2003-11-29
13201 o Robustness and bugfixes:
13202 - Force the admin to make the DataDirectory himself
13203 - to get ownership/permissions right
13204 - so clients no longer make a DataDirectory and then never use it
13205 - fix bug where a client who was offline for 45 minutes would never
13206 pull down a directory again
13207 - fix (or at least hide really well) the dns assert bug that was
13208 causing server crashes
13209 - warnings and improved robustness wrt clockskew for certs
13210 - use the native daemon(3) to daemonize, when available
13211 - exit if bind() fails
13212 - exit if neither socksport nor orport is defined
13213 - include our own tor_timegm (Win32 doesn't have its own)
13214 - bugfix for win32 with lots of connections
13215 - fix minor bias in PRNG
13216 - make dirserver more robust to corrupt cached directory
13219 - Wrote the design document (woo)
13221 o Circuit building and exit policies:
13222 - Circuits no longer try to use nodes that the directory has told them
13224 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
13225 bitcounts (18.0.0.0/8).
13226 - Make AP connections standby for a circuit if no suitable circuit
13227 exists, rather than failing
13228 - Circuits choose exit node based on addr/port, exit policies, and
13229 which AP connections are standing by
13230 - Bump min pathlen from 2 to 3
13231 - Relay end cells have a payload to describe why the stream ended.
13232 - If the stream failed because of exit policy, try again with a new
13234 - Clients have a dns cache to remember resolved addresses.
13235 - Notice more quickly when we have no working circuits
13238 - APPort is now called SocksPort
13239 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
13241 - RecommendedVersions is now a config variable rather than
13242 hardcoded (for dirservers)
13243 - Reloads config on HUP
13244 - Usage info on -h or --help
13245 - If you set User and Group config vars, it'll setu/gid to them.
13248 Changes in version 0.0.2pre13 - 2003-10-19
13249 o General stability:
13250 - SSL_write no longer fails when it returns WANTWRITE and the number
13251 of bytes in the buf has changed by the next SSL_write call.
13252 - Fix segfault fetching directory when network is down
13253 - Fix a variety of minor memory leaks
13254 - Dirservers reload the fingerprints file on HUP, so I don't have
13255 to take down the network when I approve a new router
13256 - Default server config file has explicit Address line to specify fqdn
13259 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
13260 - Make listener connections not ever alloc bufs
13262 o Autoconf improvements:
13263 - don't clobber an external CFLAGS in ./configure
13264 - Make install now works
13265 - create var/lib/tor on make install
13266 - autocreate a tor.sh initscript to help distribs
13267 - autocreate the torrc and sample-server-torrc with correct paths
13269 o Log files and Daemonizing now work:
13270 - If --DebugLogFile is specified, log to it at -l debug
13271 - If --LogFile is specified, use it instead of commandline
13272 - If --RunAsDaemon is set, tor forks and backgrounds on startup