1 Changes in version 0.2.3.17-beta - 2012-06-1?
3 - Enable gcc and ld hardening by default. Resolves ticket 5210.
4 - Update TLS cipher list to match Firefox 8 and later. Resolves
6 - Implement the client side of proposal 198: remove support for
7 clients falsely claiming to support standard ciphersuites that
8 they can actually provide. As of modern OpenSSL versions, it's not
9 necessary to fake any standard ciphersuite, and doing so prevents
10 us from using better ciphersuites in the future, since servers
11 can't know whether an advertised ciphersuite is really supported or
12 not. Some hosts -- notably, ones with very old versions of OpenSSL
13 or where OpenSSL has been built with ECC disabled -- will stand
14 out because of this change; TBB users should not be affected.
17 - Change the default value for DynamicDHGroups (introduced in
18 0.2.3.9-alpha) to 0. This feature can make Tor relays less
19 identifiable by their use of the mod_ssl DH group, but at
20 the cost of some usability (#4721) and bridge tracing (#6087)
21 regressions. Resolves ticket 5598.
22 - Send a CRLF at the end of each STATUS_* control protocol event. This
23 bug tickled a bug in Vidalia which would make it freeze. Fixes
24 bug 6094; bugfix on 0.2.3.16-alpha.
27 - Disable writing on marked-for-close connections when they are
28 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
29 bug 5263; bugfix on 0.0.2pre13, where we first added a special
30 case for flushing marked connections.
31 - Detect SSL handshake even when the initial attempt to write the
32 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
33 - Change the AllowDotExit rules so they should actually work.
34 We now enforce AllowDotExit only immediately after receiving an
35 address via SOCKS or DNSPort: other sources are free to provide
36 .exit addresses after the resolution occurs. Fixes bug 3940;
37 bugfix on 0.2.2.1-alpha.
38 - Fix a (harmless) integer overflow in cell statistics reported by
39 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
40 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
41 right places and never depends on the consensus parameters or
42 computes adaptive timeouts when it is disabled. Fixes bug 5049;
43 bugfix on 0.2.2.14-alpha.
44 - When building Tor on Windows with -DUNICODE (not default), ensure
45 that error messages, filenames, and DNS server names are always
46 NUL-terminated when we convert them to a single-byte encoding.
47 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
48 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
49 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
50 - Fix an edge case where TestingTorNetwork is set but the authorities
51 and relays all have an uptime of zero, where the private Tor network
52 could briefly lack support for hidden services. Fixes bug 3886;
53 bugfix on 0.2.2.18-alpha.
54 - Correct the manpage's descriptions for the default values of
55 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
57 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
61 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
62 more information to it, so that we can track it down in case it
63 returns again. Mitigates bug 5235.
64 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
65 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
66 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
67 - Warn the user when HTTPProxy, but no other proxy type, is
68 configured. This can cause surprising behavior: it doesn't send
69 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
70 directory traffic only. Resolves ticket 4663.
71 - Update to the June 6 2012 Maxmind GeoLite Country database.
74 Changes in version 0.2.2.37 - 2012-06-06
75 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
76 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
80 - Work around a bug in OpenSSL that broke renegotiation with TLS
81 1.1 and TLS 1.2. Without this workaround, all attempts to speak
82 the v2 Tor connection protocol when both sides were using OpenSSL
83 1.0.1 would fail. Resolves ticket 6033.
84 - When waiting for a client to renegotiate, don't allow it to add
85 any bytes to the input buffer. This fixes a potential DoS issue.
86 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
87 - Fix an edge case where if we fetch or publish a hidden service
88 descriptor, we might build a 4-hop circuit and then use that circuit
89 for exiting afterwards -- even if the new last hop doesn't obey our
90 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
93 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
94 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
97 - Tell GCC and Clang to check for any errors in format strings passed
98 to the tor_v*(print|scan)f functions.
101 Changes in version 0.2.3.16-alpha - 2012-06-05
102 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
103 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
104 currently). It also fixes a variety of smaller bugs and other cleanups
105 that get us closer to a release candidate.
107 o Major bugfixes (general):
108 - Work around a bug in OpenSSL that broke renegotiation with TLS
109 1.1 and TLS 1.2. Without this workaround, all attempts to speak
110 the v2 Tor connection protocol when both sides were using OpenSSL
111 1.0.1 would fail. Resolves ticket 6033.
112 - When waiting for a client to renegotiate, don't allow it to add
113 any bytes to the input buffer. This fixes a potential DoS issue.
114 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
115 - Pass correct OR address to managed proxies (like obfsproxy),
116 even when ORListenAddress is used. Fixes bug 4865; bugfix on
118 - The advertised platform of a router now includes only its operating
119 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
120 service pack level (for Windows) or its CPU architecture (for Unix).
121 We also no longer include the "git-XYZ" tag in the version. Resolves
124 o Major bugfixes (clients):
125 - If we are unable to find any exit that supports our predicted ports,
126 stop calling them predicted, so that we don't loop and build
127 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
128 which introduced predicted ports.
129 - Fix an edge case where if we fetch or publish a hidden service
130 descriptor, we might build a 4-hop circuit and then use that circuit
131 for exiting afterwards -- even if the new last hop doesn't obey our
132 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
133 - Check at each new consensus whether our entry guards were picked
134 long enough ago that we should rotate them. Previously, we only
135 did this check at startup, which could lead to us holding a guard
136 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
137 - When fetching a bridge descriptor from a bridge authority,
138 always do so anonymously, whether we have been able to open
139 circuits or not. Partial fix for bug 1938; bugfix on 2.0.7-alpha.
140 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
141 but we'll need to wait for bug 6010 before it's actually usable.
143 o Major bugfixes (directory authorities):
144 - When computing weight parameters, behave more robustly in the
145 presence of a bad bwweightscale value. Previously, the authorities
146 would crash if they agreed on a sufficiently broken weight_scale
147 value: now, they use a reasonable default and carry on. Partial
148 fix for 5786; bugfix on 0.2.2.17-alpha.
149 - Check more thoroughly to prevent a rogue authority from
150 double-voting on any consensus directory parameter. Previously,
151 authorities would crash in this case if the total number of
152 votes for any parameter exceeded the number of active voters,
153 but would let it pass otherwise. Partial fix for bug 5786; bugfix
157 - Rate-limit log messages when asked to connect anonymously to
158 a private address. When these hit, they tended to hit fast and
159 often. Also, don't bother trying to connect to addresses that we
160 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
161 reply makes us think we have been lied to, even when the address the
162 client tried to connect to was "localhost." Resolves ticket 2822.
163 - Allow packagers to insert an extra string in server descriptor
164 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
165 Resolves the rest of ticket 2988.
166 - Raise the threshold of server descriptors needed (75%) and exit
167 server descriptors needed (50%) before we will declare ourselves
168 bootstrapped. This will make clients start building circuits a
169 little later, but makes the initially constructed circuits less
170 skewed and less in conflict with further directory fetches. Fixes
172 - Close any connection that sends unrecognized junk before the
173 handshake. Solves an issue noted in bug 4369.
174 - Improve log messages about managed transports. Resolves ticket 5070.
175 - Tag a bridge's descriptor as "never to be sent unencrypted".
176 This shouldn't matter, since bridges don't open non-anonymous
177 connections to the bridge authority and don't allow unencrypted
178 directory connections from clients, but we might as well make
179 sure. Closes bug 5139.
180 - Expose our view of whether we have gone dormant to the controller,
181 via a new "GETINFO dormant" value. Torbutton and other controllers
182 can use this to avoid doing periodic requests through Tor while
183 it's dormant (bug 4718). Fixes bug 5954.
184 - Tell GCC and Clang to check for any errors in format strings passed
185 to the tor_v*(print|scan)f functions.
186 - Update to the May 1 2012 Maxmind GeoLite Country database.
188 o Minor bugfixes (already included in 0.2.2.36):
189 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
190 Fixes bug 5346; bugfix on 0.0.8pre3.
191 - Correct parsing of certain date types in parse_http_time().
192 Without this patch, If-Modified-Since would behave
193 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
194 Esteban Manchado Velázques.
195 - Make our number-parsing functions always treat too-large values
196 as an error, even when those values exceed the width of the
197 underlying type. Previously, if the caller provided these
198 functions with minima or maxima set to the extreme values of the
199 underlying integer type, these functions would return those
200 values on overflow rather than treating overflow as an error.
201 Fixes part of bug 5786; bugfix on 0.0.9.
202 - If we hit the error case where routerlist_insert() replaces an
203 existing (old) server descriptor, make sure to remove that
204 server descriptor from the old_routers list. Fix related to bug
205 1776. Bugfix on 0.2.2.18-alpha.
206 - Clarify the behavior of MaxCircuitDirtiness with hidden service
207 circuits. Fixes issue 5259.
209 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
210 - Prevent a null-pointer dereference when receiving a data cell
211 for a nonexistent stream when the circuit in question has an
212 empty deliver window. We don't believe this is triggerable,
213 since we don't currently allow deliver windows to become empty,
214 but the logic is tricky enough that it's better to make the code
215 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
216 - Fix a memory leak when trying to launch a DNS request when the
217 network is disabled or the nameservers are unconfigurable. Fixes
218 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
219 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
220 - Don't hold a windows file handle open for every file mapping;
221 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
223 - Avoid O(n^2) performance characteristics when parsing a large
224 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
225 - Format more doubles with %f, not %lf. Patch from grarpamp to make
226 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
228 - Make our replacement implementation of strtok_r() compatible with
229 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
230 bugfix on 0.2.2.1-alpha.
231 - Fix a NULL-pointer dereference on a badly formed
232 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
233 bugfix on 0.2.2.9-alpha.
234 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
235 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
236 - Defensively refactor rend_mid_rendezvous() so that protocol
237 violations and length checks happen in the beginning. Fixes
239 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
240 that IPv6 stuff will compile on MSVC, and compilation issues
241 will be easier to track down. Fixes bug 5861.
243 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
244 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
245 resource exhaustion, so that clients can adjust their load to
246 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
247 started using END_STREAM_REASON_RESOURCELIMIT.
248 - Don't check for whether the address we're using for outbound
249 connections has changed until after the outbound connection has
250 completed. On Windows, getsockname() doesn't succeed until the
251 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
252 - If the configuration tries to set MyFamily on a bridge, refuse to
253 do so, and warn about the security implications. Fixes bug 4657;
254 bugfix on 0.2.0.3-alpha.
255 - If the client fails to set a reasonable set of ciphersuites
256 during its v2 handshake renegotiation, allow the renegotiation to
257 continue nevertheless (i.e. send all the required certificates).
258 Fixes bug 4591; bugfix on 0.2.0.20-rc.
259 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
260 option is set to 0 (which Vidalia version 0.2.16 now does when
261 a SAVECONF attempt fails), perform other actions that SIGHUP
262 usually causes (like reopening the logs). Fixes bug 5095; bugfix
264 - If we fail to write a microdescriptor to the disk cache, do not
265 continue replacing the old microdescriptor file. Fixes bug 2954;
266 bugfix on 0.2.2.6-alpha.
267 - Exit nodes don't need to fetch certificates for authorities that
268 they don't recognize; only directory authorities, bridges,
269 and caches need to do that. Fixes part of bug 2297; bugfix on
271 - Correctly handle checking the permissions on the parent
272 directory of a control socket in the root directory. Bug found
273 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
275 - When told to add a bridge with the same digest as a preexisting
276 bridge but a different addr:port, change the addr:port as
277 requested. Previously we would not notice the change. Fixes half
278 of bug 5603; fix on 0.2.2.26-beta.
279 - End AUTHCHALLENGE error messages (in the control protocol) with
280 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
282 o Minor bugfixes (on 0.2.3.x):
283 - Turn an assertion (that the number of handshakes received as a
284 server is not < 1) into a warning. Fixes bug 4873; bugfix on
286 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
287 we had reversed them when the answer was cached.) Fixes bug
288 5723; bugfix on 0.2.3.1-alpha.
289 - Work correctly on Linux systems with accept4 support advertised in
290 their headers, but without accept4 support in the kernel. Fix
291 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
292 - When told to add a bridge with the same addr:port as a preexisting
293 bridge but a different transport, change the transport as
294 requested. Previously we would not notice the change. Fixes half
295 of bug 5603; fix on 0.2.3.2-alpha.
296 - Avoid a "double-reply" warning when replying to a SOCKS request
297 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
298 bugfix on 0.2.3.4-alpha.
299 - Fix a bug where a bridge authority crashes if it has seen no
300 directory requests when it's time to write statistics to disk.
301 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
303 - Don't try to open non-control listeners when DisableNetwork is set.
304 Previously, we'd open all listeners, then immediately close them.
305 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
306 - Don't abort the managed proxy protocol if the managed proxy
307 sends us an unrecognized line; ignore it instead. Fixes bug
308 5910; bugfix on 0.2.3.9-alpha.
309 - Fix a compile warning in crypto.c when compiling with clang 3.1.
310 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
311 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
312 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
313 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
314 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
315 - Resolve numerous small warnings and build issues with MSVC. Resolves
318 o Documentation fixes:
319 - Improve the manual's documentation for the NT Service command-line
320 options. Addresses ticket 3964.
321 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
322 - Document the changes to the ORPort and DirPort options, and the
323 fact that {OR/Dir}ListenAddress is now unnecessary (and
324 therefore deprecated). Resolves ticket 5597.
327 - Remove the torrc.bridge file: we don't use it for anything, and
328 it had become badly desynchronized from torrc.sample. Resolves
332 Changes in version 0.2.2.36 - 2012-05-24
333 Tor 0.2.2.36 updates the addresses for two of the eight directory
334 authorities, fixes some potential anonymity and security issues,
335 and fixes several crash bugs.
337 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
338 known flaws, and nobody should be using them. You should upgrade. If
339 you're using a Linux or BSD and its packages are obsolete, stop using
340 those packages and upgrade anyway.
342 o Directory authority changes:
343 - Change IP address for maatuska (v3 directory authority).
344 - Change IP address for ides (v3 directory authority), and rename
348 - When building or running with any version of OpenSSL earlier
349 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
350 versions have a bug (CVE-2011-4576) in which their block cipher
351 padding includes uninitialized data, potentially leaking sensitive
352 information to any peer with whom they make a SSLv3 connection. Tor
353 does not use SSL v3 by default, but a hostile client or server
354 could force an SSLv3 connection in order to gain information that
355 they shouldn't have been able to get. The best solution here is to
356 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
357 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
358 to make sure that the bug can't happen.
359 - Never use a bridge or a controller-supplied node as an exit, even
360 if its exit policy allows it. Found by wanoskarnet. Fixes bug
361 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
362 and 0.2.0.3-alpha (for bridge-purpose descriptors).
363 - Only build circuits if we have a sufficient threshold of the total
364 descriptors that are marked in the consensus with the "Exit"
365 flag. This mitigates an attack proposed by wanoskarnet, in which
366 all of a client's bridges collude to restrict the exit nodes that
367 the client knows about. Fixes bug 5343.
368 - Provide controllers with a safer way to implement the cookie
369 authentication mechanism. With the old method, if another locally
370 running program could convince a controller that it was the Tor
371 process, then that program could trick the controller into telling
372 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
373 authentication method uses a challenge-response approach to prevent
374 this attack. Fixes bug 5185; implements proposal 193.
377 - Avoid logging uninitialized data when unable to decode a hidden
378 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
379 - Avoid a client-side assertion failure when receiving an INTRODUCE2
380 cell on a general purpose circuit. Fixes bug 5644; bugfix on
382 - Fix builds when the path to sed, openssl, or sha1sum contains
383 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
385 - Correct our replacements for the timeradd() and timersub() functions
386 on platforms that lack them (for example, Windows). The timersub()
387 function is used when expiring circuits, while timeradd() is
388 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
389 bugfix on 0.2.2.24-alpha.
390 - Fix the SOCKET_OK test that we use to tell when socket
391 creation fails so that it works on Win64. Fixes part of bug 4533;
392 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
395 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
396 Fixes bug 5346; bugfix on 0.0.8pre3.
397 - Make our number-parsing functions always treat too-large values
398 as an error, even when those values exceed the width of the
399 underlying type. Previously, if the caller provided these
400 functions with minima or maxima set to the extreme values of the
401 underlying integer type, these functions would return those
402 values on overflow rather than treating overflow as an error.
403 Fixes part of bug 5786; bugfix on 0.0.9.
404 - Older Linux kernels erroneously respond to strange nmap behavior
405 by having accept() return successfully with a zero-length
406 socket. When this happens, just close the connection. Previously,
407 we would try harder to learn the remote address: but there was
408 no such remote address to learn, and our method for trying to
409 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
410 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
411 - Correct parsing of certain date types in parse_http_time().
412 Without this patch, If-Modified-Since would behave
413 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
414 Esteban Manchado Velázques.
415 - Change the BridgePassword feature (part of the "bridge community"
416 design, which is not yet implemented) to use a time-independent
417 comparison. The old behavior might have allowed an adversary
418 to use timing to guess the BridgePassword value. Fixes bug 5543;
419 bugfix on 0.2.0.14-alpha.
420 - Detect and reject certain misformed escape sequences in
421 configuration values. Previously, these values would cause us
422 to crash if received in a torrc file or over an authenticated
423 control port. Bug found by Esteban Manchado Velázquez, and
424 independently by Robert Connolly from Matta Consulting who further
425 noted that it allows a post-authentication heap overflow. Patch
426 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
427 bugfix on 0.2.0.16-alpha.
428 - Fix a compile warning when using the --enable-openbsd-malloc
429 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
430 - During configure, detect when we're building with clang version
431 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
432 CFLAGS. clang doesn't support them yet.
433 - When sending an HTTP/1.1 proxy request, include a Host header.
434 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
435 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
436 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
437 - If we hit the error case where routerlist_insert() replaces an
438 existing (old) server descriptor, make sure to remove that
439 server descriptor from the old_routers list. Fix related to bug
440 1776. Bugfix on 0.2.2.18-alpha.
442 o Minor bugfixes (documentation and log messages):
443 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
444 Fixes bug 4856; bugfix on Tor 0.0.6.
445 - Update "ClientOnly" man page entry to explain that there isn't
446 really any point to messing with it. Resolves ticket 5005.
447 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
448 directory authority option (introduced in Tor 0.2.2.34).
449 - Downgrade the "We're missing a certificate" message from notice
450 to info: people kept mistaking it for a real problem, whereas it
451 is seldom the problem even when we are failing to bootstrap. Fixes
452 bug 5067; bugfix on 0.2.0.10-alpha.
453 - Correctly spell "connect" in a log message on failure to create a
454 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
455 - Clarify the behavior of MaxCircuitDirtiness with hidden service
456 circuits. Fixes issue 5259.
459 - Directory authorities now reject versions of Tor older than
460 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
461 inclusive. These versions accounted for only a small fraction of
462 the Tor network, and have numerous known security issues. Resolves
464 - Update to the May 1 2012 Maxmind GeoLite Country database.
467 - When sending or relaying a RELAY_EARLY cell, we used to convert
468 it to a RELAY cell if the connection was using the v1 link
469 protocol. This was a workaround for older versions of Tor, which
470 didn't handle RELAY_EARLY cells properly. Now that all supported
471 versions can handle RELAY_EARLY cells, and now that we're enforcing
472 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
473 remove this workaround. Addresses bug 4786.
476 Changes in version 0.2.3.15-alpha - 2012-04-30
477 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
478 the development branch build on Windows again.
480 o Minor bugfixes (on 0.2.2.x and earlier):
481 - Make sure that there are no unhandled pending TLS errors before
482 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
483 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
484 Bugfix on 0.1.0.5-rc; fixes bug 4528.
485 - Fix an assert that directory authorities could trigger on sighup
486 during some configuration state transitions. We now don't treat
487 it as a fatal error when the new descriptor we just generated in
488 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
489 - After we pick a directory mirror, we would refuse to use it if
490 it's in our ExcludeExitNodes list, resulting in mysterious failures
491 to bootstrap for people who just wanted to avoid exiting from
492 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
493 - When building with --enable-static-tor on OpenBSD, do not
494 erroneously attempt to link -lrt. Fixes bug 5103.
496 o Minor bugfixes (on 0.2.3.x):
497 - When Tor is built with kernel headers from a recent (last few
498 years) Linux kernel, do not fail to run on older (pre-2.6.28
499 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
500 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
502 - Fix compilation with miniupnpc version 1.6; patch from
503 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
504 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
505 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
506 - Fix compilation on platforms without unistd.h, or where environ
507 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
510 - Directory authorities are now a little more lenient at accepting
511 older router descriptors, or newer router descriptors that don't
512 make big changes. This should help ameliorate past and future
513 issues where routers think they have uploaded valid descriptors,
514 but the authorities don't think so. Fix for ticket 2479.
515 - Make the code that clients use to detect an address change be
516 IPv6-aware, so that it won't fill clients' logs with error
517 messages when trying to get the IPv4 address of an IPv6
518 connection. Implements ticket 5537.
521 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
522 authorities needed to use it for a while to keep the network working
523 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
524 that was six months ago. As of now, it should no longer be needed
528 Changes in version 0.2.3.14-alpha - 2012-04-23
529 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
530 candidate. It also dramatically speeds up AES: fast relays should
531 consider switching to the newer OpenSSL library.
533 o Directory authority changes:
534 - Change IP address for ides (v3 directory authority), and rename
538 - Avoid logging uninitialized data when unable to decode a hidden
539 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
540 - Avoid a client-side assertion failure when receiving an INTRODUCE2
541 cell on a general purpose circuit. Fixes bug 5644; bugfix on
543 - If authorities are unable to get a v2 consensus document from other
544 directory authorities, they no longer fall back to fetching
545 them from regular directory caches. Fixes bug 5635; bugfix on
546 0.2.2.26-beta, where routers stopped downloading v2 consensus
548 - When we start a Tor client with a normal consensus already cached,
549 be willing to download a microdescriptor consensus. Fixes bug 4011;
550 fix on 0.2.3.1-alpha.
552 o Major features (performance):
553 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
554 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
555 vectorized AES implementations as appropriate. These can be much,
556 much faster than other AES implementations.
558 o Minor bugfixes (0.2.2.x and earlier):
559 - Don't launch more than 10 service-side introduction-point circuits
560 for a hidden service in five minutes. Previously, we would consider
561 launching more introduction-point circuits if at least one second
562 had passed without any introduction-point circuits failing. Fixes
563 bug 4607; bugfix on 0.0.7pre1.
564 - Change the BridgePassword feature (part of the "bridge community"
565 design, which is not yet implemented) to use a time-independent
566 comparison. The old behavior might have allowed an adversary
567 to use timing to guess the BridgePassword value. Fixes bug 5543;
568 bugfix on 0.2.0.14-alpha.
569 - Enforce correct return behavior of tor_vsscanf() when the '%%'
570 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
571 - When sending an HTTP/1.1 proxy request, include a Host header.
572 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
573 - Don't log that we have "decided to publish new relay descriptor"
574 unless we are actually publishing a descriptor. Fixes bug 3942;
575 bugfix on 0.2.2.28-beta.
577 o Minor bugfixes (0.2.3.x):
578 - Fix a bug where a bridge authority crashes (on a failed assert)
579 if it has seen no directory requests when it's time to write
580 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
581 - Fix bug stomping on ORPort option NoListen and ignoring option
582 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
583 - In the testsuite, provide a large enough buffer in the tor_sscanf
584 unit test. Otherwise we'd overrun that buffer and crash during
585 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
587 - Make sure we create the keys directory if it doesn't exist and we're
588 about to store the dynamic Diffie-Hellman parameters. Fixes bug
589 5572; bugfix on 0.2.3.13-alpha.
590 - Fix a small memory leak when trying to decode incorrect base16
591 authenticator during SAFECOOKIE authentication. Found by
592 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
595 - Add more information to a log statement that might help track down
596 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
597 non-IP address" messages (or any Bug messages, for that matter!),
598 please let us know about it.
599 - Relays now understand an IPv6 address when they get one from a
600 directory server. Resolves ticket 4875.
601 - Resolve IPv6 addresses in bridge and entry statistics to country
602 code "??" which means we at least count them. Resolves ticket 5053;
603 improves on 0.2.3.9-alpha.
604 - Update to the April 3 2012 Maxmind GeoLite Country database.
605 - Begin a doc/state-contents.txt file to explain the contents of
606 the Tor state file. Fixes bug 2987.
608 o Default torrc changes:
609 - Stop listing "socksport 9050" in torrc.sample. We open a socks
610 port on 9050 by default anyway, so this should not change anything
612 - Stop mentioning the deprecated *ListenAddress options in
613 torrc.sample. Fixes bug 5438.
614 - Document unit of bandwidth related options in sample torrc.
618 - The "torify" script no longer supports the "tsocks" socksifier
619 tool, since tsocks doesn't support DNS and UDP right for Tor.
620 Everyone should be using torsocks instead. Fixes bugs 3530 and
621 5180. Based on a patch by "ugh".
624 - Change the symmetric cipher interface so that creating and
625 initializing a stream cipher are no longer separate functions.
626 - Remove all internal support for unpadded RSA. We never used it, and
627 it would be a bad idea to start.
630 Changes in version 0.2.3.13-alpha - 2012-03-26
631 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
632 in managed pluggable transports, as well as providing other cleanups
633 that get us closer to a release candidate.
635 o Directory authority changes:
636 - Change IP address for maatuska (v3 directory authority).
639 - Provide controllers with a safer way to implement the cookie
640 authentication mechanism. With the old method, if another locally
641 running program could convince a controller that it was the Tor
642 process, then that program could trick the controller into telling
643 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
644 authentication method uses a challenge-response approach to prevent
645 this attack. Fixes bug 5185, implements proposal 193.
646 - Never use a bridge or a controller-supplied node as an exit, even
647 if its exit policy allows it. Found by wanoskarnet. Fixes bug
648 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
649 and 0.2.0.3-alpha (for bridge-purpose descriptors).
650 - Only build circuits if we have a sufficient threshold of the total
651 descriptors that are marked in the consensus with the "Exit"
652 flag. This mitigates an attack proposed by wanoskarnet, in which
653 all of a client's bridges collude to restrict the exit nodes that
654 the client knows about. Fixes bug 5343.
656 o Major bugfixes (on Tor 0.2.3.x):
657 - Avoid an assert when managed proxies like obfsproxy are configured,
658 and we receive HUP signals or setconf attempts too rapidly. This
659 situation happens most commonly when Vidalia tries to attach to
660 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
661 bugfix on 0.2.3.6-alpha.
662 - Fix a relay-side pluggable transports bug where managed proxies were
663 unreachable from the Internet, because Tor asked them to bind on
664 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
665 - Stop discarding command-line arguments when TestingTorNetwork
666 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
667 0.2.3.9-alpha, where task 4552 added support for two layers of
669 - Resume allowing the unit tests to run in gdb. This was accidentally
670 made impossible when the DisableDebuggerAttachment option was
671 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
672 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
673 0.2.3.11-alpha. Reported by Anthony G. Basile.
675 o Minor bugfixes (on 0.2.2.x and earlier):
676 - Ensure we don't cannibalize circuits that are longer than three hops
677 already, so we don't end up making circuits with 5 or more
678 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
679 0.1.0.1-rc which introduced cannibalization.
680 - Detect and reject certain misformed escape sequences in
681 configuration values. Previously, these values would cause us
682 to crash if received in a torrc file or over an authenticated
683 control port. Bug found by Esteban Manchado Velázquez, and
684 independently by Robert Connolly from Matta Consulting who further
685 noted that it allows a post-authentication heap overflow. Patch
686 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
687 bugfix on 0.2.0.16-alpha.
688 - Fix a compile warning when using the --enable-openbsd-malloc
689 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
690 - Directory caches no longer refuse to clean out descriptors because
691 of missing v2 networkstatus documents, unless they're configured
692 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
693 0.2.2.26-beta. Patch by Daniel Bryg.
694 - Update to the latest version of the tinytest unit testing framework.
695 This includes a couple of bugfixes that can be relevant for
696 running forked unit tests on Windows, and removes all reserved
699 o Minor bugfixes (on 0.2.3.x):
700 - On a failed pipe() call, don't leak file descriptors. Fixes bug
701 4296; bugfix on 0.2.3.1-alpha.
702 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
703 until after we have received a CERTS cell. Fixes bug 4361; bugfix
704 on 0.2.3.6-alpha. Patch by "frosty".
705 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
706 option, so that the IP stack doesn't decide to use it for IPv4
707 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
708 - Ensure that variables set in Tor's environment cannot override
709 environment variables that Tor passes to a managed
710 pluggable-transport proxy. Previously, Tor would pass every
711 variable in its environment to managed proxies along with the new
712 ones, in such a way that on many operating systems, the inherited
713 environment variables would override those which Tor tried to
714 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
715 bugfix on 0.2.3.9-alpha for Windows.
718 - A wide variety of new unit tests by Esteban Manchado Velázquez.
719 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
720 - Update to the March 6 2012 Maxmind GeoLite Country database.
723 Changes in version 0.2.3.12-alpha - 2012-02-13
724 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
725 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
726 when Tor is configured to use a pluggable transport like obfsproxy.
729 - Fix builds when the path to sed, openssl, or sha1sum contains
730 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
732 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
733 connections. This change should allow busy exit relays to stop
734 running out of available sockets as quickly. Fixes bug 4950;
735 bugfix on 0.2.2.26-beta.
736 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
737 would ask the bridge for microdescriptors, which are only supported
738 in 0.2.3.x, and then fail to bootstrap when it didn't get the
739 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
740 - Properly set up obfsproxy's environment when in managed mode. The
741 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
742 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
743 5076 and 5082; bugfix on 0.2.3.6-alpha.
746 - Use the dead_strip option when building Tor on OS X. This reduces
747 binary size by almost 19% when linking openssl and libevent
748 statically, which we do for Tor Browser Bundle.
749 - Fix broken URLs in the sample torrc file, and tell readers about
750 the OutboundBindAddress, ExitPolicyRejectPrivate, and
751 PublishServerDescriptor options. Addresses bug 4652.
752 - Update to the February 7 2012 Maxmind GeoLite Country database.
755 - Downgrade the "We're missing a certificate" message from notice
756 to info: people kept mistaking it for a real problem, whereas it
757 is seldom the problem even when we are failing to bootstrap. Fixes
758 bug 5067; bugfix on 0.2.0.10-alpha.
759 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
760 managed pluggable transport server proxy's environment.
761 Previously, we would put it there, even though Tor doesn't
762 implement an 'extended server port' yet, and even though Tor
763 almost certainly isn't listening at that address. For now, we set
764 it to an empty string to avoid crashing older obfsproxies. Bugfix
766 - Log the heartbeat message every HeartbeatPeriod seconds, not every
767 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
768 0.2.3.1-alpha. Bug reported by Scott Bennett.
769 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
770 bugfix on 0.2.3.11-alpha.
771 - Update "ClientOnly" man page entry to explain that there isn't
772 really any point to messing with it. Resolves ticket 5005.
773 - Use the correct CVE number for CVE-2011-4576 in our comments and
774 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
777 o Code simplifications and refactoring:
778 - Use the _WIN32 macro throughout our code to detect Windows.
779 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
783 Changes in version 0.2.3.11-alpha - 2012-01-22
784 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
785 the last step of the plan to limit maximum circuit length, includes
786 a wide variety of hidden service performance and correctness fixes,
787 works around an OpenSSL security flaw if your distro is too stubborn
788 to upgrade, and fixes a bunch of smaller issues.
791 - Now that Tor 0.2.0.x is completely deprecated, enable the final
792 part of "Proposal 110: Avoiding infinite length circuits" by
793 refusing all circuit-extend requests that do not use a relay_early
794 cell. This change helps Tor resist a class of denial-of-service
795 attacks by limiting the maximum circuit length.
796 - Adjust the number of introduction points that a hidden service
797 will try to maintain based on how long its introduction points
798 remain in use and how many introductions they handle. Fixes
800 - Try to use system facilities for enumerating local interface
801 addresses, before falling back to our old approach (which was
802 binding a UDP socket, and calling getsockname() on it). That
803 approach was scaring OS X users whose draconian firewall
804 software warned about binding to UDP sockets, regardless of
805 whether packets were sent. Now we try to use getifaddrs(),
806 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
807 system supports. Resolves ticket 1827.
809 o Major security workaround:
810 - When building or running with any version of OpenSSL earlier
811 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
812 versions have a bug (CVE-2011-4576) in which their block cipher
813 padding includes uninitialized data, potentially leaking sensitive
814 information to any peer with whom they make a SSLv3 connection. Tor
815 does not use SSL v3 by default, but a hostile client or server
816 could force an SSLv3 connection in order to gain information that
817 they shouldn't have been able to get. The best solution here is to
818 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
819 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
820 to make sure that the bug can't happen.
823 - Fix the SOCKET_OK test that we use to tell when socket
824 creation fails so that it works on Win64. Fixes part of bug 4533;
825 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
826 - Correct our replacements for the timeradd() and timersub() functions
827 on platforms that lack them (for example, Windows). The timersub()
828 function is used when expiring circuits, while timeradd() is
829 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
830 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
831 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
832 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
833 bug at runtime, not compile time, because some distributions hack
834 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
835 on 0.2.3.9-alpha. Found by Pascal.
837 o Minor features (controller):
838 - Use absolute path names when reporting the torrc filename in the
839 control protocol, so a controller can more easily find the torrc
840 file. Resolves bug 1101.
841 - Extend the control protocol to report flags that control a circuit's
842 path selection in CIRC events and in replies to 'GETINFO
843 circuit-status'. Implements part of ticket 2411.
844 - Extend the control protocol to report the hidden service address
845 and current state of a hidden-service-related circuit in CIRC
846 events and in replies to 'GETINFO circuit-status'. Implements part
848 - When reporting the path to the cookie file to the controller,
849 give an absolute path. Resolves ticket 4881.
850 - Allow controllers to request an event notification whenever a
851 circuit is cannibalized or its purpose is changed. Implements
853 - Include the creation time of a circuit in CIRC and CIRC2
854 control-port events and the list produced by the 'GETINFO
855 circuit-status' control-port command.
857 o Minor features (directory authorities):
858 - Directory authorities now reject versions of Tor older than
859 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
860 inclusive. These versions accounted for only a small fraction of
861 the Tor network, and have numerous known security issues. Resolves
863 - Authority operators can now vote for all relays in a given
864 set of countries to be BadDir/BadExit/Invalid/Rejected.
865 - Provide two consensus parameters (FastFlagMinThreshold and
866 FastFlagMaxThreshold) to control the range of allowable bandwidths
867 for the Fast directory flag. These allow authorities to run
868 experiments on appropriate requirements for being a "Fast" node.
869 The AuthDirFastGuarantee config value still applies.
870 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
871 directory authority option (introduced in Tor 0.2.2.34).
873 o Minor features (other):
874 - Don't disable the DirPort when we cannot exceed our AccountingMax
875 limit during this interval because the effective bandwidthrate is
876 low enough. This is useful in a situation where AccountMax is only
877 used as an additional safeguard or to provide statistics.
878 - Prepend an informative header to generated dynamic_dh_params files.
879 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
880 EntryNodes will have no effect. Resolves issue 2571.
881 - Log more useful messages when we fail to disable debugger
883 - Log which authority we're missing votes from when we go to fetch
884 them from the other auths.
885 - Log (at debug level) whenever a circuit's purpose is changed.
886 - Add missing documentation for the MaxClientCircuitsPending,
887 UseMicrodescriptors, UserspaceIOCPBuffers, and
888 _UseFilteringSSLBufferevents options, all introduced during
890 - Update to the January 3 2012 Maxmind GeoLite Country database.
892 o Minor bugfixes (hidden services):
893 - Don't close hidden service client circuits which have almost
894 finished connecting to their destination when they reach
895 the normal circuit-build timeout. Previously, we would close
896 introduction circuits which are waiting for an acknowledgement
897 from the introduction point, and rendezvous circuits which have
898 been specified in an INTRODUCE1 cell sent to a hidden service,
899 after the normal CBT. Now, we mark them as 'timed out', and launch
900 another rendezvous attempt in parallel. This behavior change can
901 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
902 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
903 - Don't close hidden-service-side rendezvous circuits when they
904 reach the normal circuit-build timeout. This behaviour change can
905 be disabled using the new
906 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
907 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
908 - Make sure we never mark the wrong rendezvous circuit as having
909 had its introduction cell acknowleged by the introduction-point
910 relay. Previously, when we received an INTRODUCE_ACK cell on a
911 client-side hidden-service introduction circuit, we might have
912 marked a rendezvous circuit other than the one we specified in
913 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
914 a warning message and interfered with the hidden service
915 connection-establishment process. Fixes bug 4759; bugfix on
916 0.2.3.3-alpha, when we added the stream-isolation feature which
917 might cause Tor to open multiple rendezvous circuits for the same
919 - Don't trigger an assertion failure when we mark a new client-side
920 hidden-service introduction circuit for close during the process
921 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
924 o Minor bugfixes (log messages):
925 - Correctly spell "connect" in a log message on failure to create a
926 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
928 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
929 Fixes bug 4856; bugfix on Tor 0.0.6.
930 - Fix the log message describing how we work around discovering
931 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
932 4837; bugfix on 0.2.2.9-alpha.
933 - When logging about a disallowed .exit name, do not also call it
934 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
936 o Minor bugfixes (build fixes):
937 - During configure, detect when we're building with clang version
938 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
939 CFLAGS. clang doesn't support them yet.
940 - During configure, search for library containing cos function as
941 libm lives in libcore on some platforms (BeOS/Haiku). Linking
942 against libm was hard-coded before. Fixes the first part of bug
943 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
945 - Detect attempts to build Tor on (as yet hypothetical) versions
946 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
947 fix for bug 4533. Bugfix on 0.2.2.28-beta.
948 - Preprocessor directives should not be put inside the arguments
949 of a macro. This would break compilation with GCC releases prior
950 to version 3.3. We would never recommend such an old GCC version,
951 but it is apparently required for binary compatibility on some
952 platforms (namely, certain builds of Haiku). Fixes the other part
953 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
956 o Minor bugfixes (other):
957 - Older Linux kernels erroneously respond to strange nmap behavior
958 by having accept() return successfully with a zero-length
959 socket. When this happens, just close the connection. Previously,
960 we would try harder to learn the remote address: but there was
961 no such remote address to learn, and our method for trying to
962 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
963 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
964 - Fix null-pointer access that could occur if TLS allocation failed.
965 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
966 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
967 accidentally been reverted.
968 - Fix our implementation of crypto_random_hostname() so it can't
969 overflow on ridiculously large inputs. (No Tor version has ever
970 provided this kind of bad inputs, but let's be correct in depth.)
971 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
972 - Find more places in the code that should have been testing for
973 invalid sockets using the SOCKET_OK macro. Required for a fix
974 for bug 4533. Bugfix on 0.2.2.28-beta.
975 - Fix an assertion failure when, while running with bufferevents, a
976 connection finishes connecting after it is marked for close, but
977 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
978 - test_util_spawn_background_ok() hardcoded the expected value
979 for ENOENT to 2. This isn't portable as error numbers are
980 platform specific, and particularly the hurd has ENOENT at
981 0x40000002. Construct expected string at runtime, using the correct
982 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
983 - Reject attempts to disable DisableDebuggerAttachment while Tor is
984 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
985 - Use an appropriate-width type for sockets in tor-fw-helper on
986 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
989 - When sending or relaying a RELAY_EARLY cell, we used to convert
990 it to a RELAY cell if the connection was using the v1 link
991 protocol. This was a workaround for older versions of Tor, which
992 didn't handle RELAY_EARLY cells properly. Now that all supported
993 versions can handle RELAY_EARLY cells, and now that we're enforcing
994 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
995 remove this workaround. Addresses bug 4786.
997 o Code simplifications and refactoring:
998 - Use OpenSSL's built-in SSL_state_string_long() instead of our
999 own homebrewed ssl_state_to_string() replacement. Patch from
1000 Emile Snyder. Fixes bug 4653.
1001 - Use macros to indicate OpenSSL versions, so we don't need to worry
1002 about accidental hexadecimal bit shifts.
1003 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
1005 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
1006 - Use the smartlist_add_asprintf() alias more consistently.
1007 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
1008 invalid value, rather than just -1.
1009 - Rename a handful of old identifiers, mostly related to crypto
1010 structures and crypto functions. By convention, our "create an
1011 object" functions are called "type_new()", our "free an object"
1012 functions are called "type_free()", and our types indicate that
1013 they are types only with a final "_t". But a handful of older
1014 types and functions broke these rules, with function names like
1015 "type_create" or "subsystem_op_type", or with type names like
1019 Changes in version 0.2.3.10-alpha - 2011-12-16
1020 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
1021 Tor's buffers code. Absolutely everybody should upgrade.
1023 The bug relied on an incorrect calculation when making data continuous
1024 in one of our IO buffers, if the first chunk of the buffer was
1025 misaligned by just the wrong amount. The miscalculation would allow an
1026 attacker to overflow a piece of heap-allocated memory. To mount this
1027 attack, the attacker would need to either open a SOCKS connection to
1028 Tor's SocksPort (usually restricted to localhost), or target a Tor
1029 instance configured to make its connections through a SOCKS proxy
1030 (which Tor does not do by default).
1032 Good security practice requires that all heap-overflow bugs should be
1033 presumed to be exploitable until proven otherwise, so we are treating
1034 this as a potential code execution attack. Please upgrade immediately!
1035 This bug does not affect bufferevents-based builds of Tor. Special
1036 thanks to "Vektor" for reporting this issue to us!
1038 This release also contains a few minor bugfixes for issues discovered
1042 - Fix a heap overflow bug that could occur when trying to pull
1043 data into the first chunk of a buffer, when that chunk had
1044 already had some data drained from it. Fixes CVE-2011-2778;
1045 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1048 - If we can't attach streams to a rendezvous circuit when we
1049 finish connecting to a hidden service, clear the rendezvous
1050 circuit's stream-isolation state and try to attach streams
1051 again. Previously, we cleared rendezvous circuits' isolation
1052 state either too early (if they were freshly built) or not at all
1053 (if they had been built earlier and were cannibalized). Bugfix on
1054 0.2.3.3-alpha; fixes bug 4655.
1055 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
1056 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
1057 - Fix an assertion failure when a relay with accounting enabled
1058 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
1061 - Update to the December 6 2011 Maxmind GeoLite Country database.
1064 Changes in version 0.2.2.35 - 2011-12-16
1065 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
1066 buffers code. Absolutely everybody should upgrade.
1068 The bug relied on an incorrect calculation when making data continuous
1069 in one of our IO buffers, if the first chunk of the buffer was
1070 misaligned by just the wrong amount. The miscalculation would allow an
1071 attacker to overflow a piece of heap-allocated memory. To mount this
1072 attack, the attacker would need to either open a SOCKS connection to
1073 Tor's SocksPort (usually restricted to localhost), or target a Tor
1074 instance configured to make its connections through a SOCKS proxy
1075 (which Tor does not do by default).
1077 Good security practice requires that all heap-overflow bugs should be
1078 presumed to be exploitable until proven otherwise, so we are treating
1079 this as a potential code execution attack. Please upgrade immediately!
1080 This bug does not affect bufferevents-based builds of Tor. Special
1081 thanks to "Vektor" for reporting this issue to us!
1083 Tor 0.2.2.35 also fixes several bugs in previous versions, including
1084 crash bugs for unusual configurations, and a long-term bug that
1085 would prevent Tor from starting on Windows machines with draconian
1088 With this release, we remind everyone that 0.2.0.x has reached its
1089 formal end-of-life. Those Tor versions have many known flaws, and
1090 nobody should be using them. You should upgrade -- ideally to the
1091 0.2.2.x series. If you're using a Linux or BSD and its packages are
1092 obsolete, stop using those packages and upgrade anyway.
1094 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
1095 longer receive support after some time in early 2012.
1098 - Fix a heap overflow bug that could occur when trying to pull
1099 data into the first chunk of a buffer, when that chunk had
1100 already had some data drained from it. Fixes CVE-2011-2778;
1101 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1102 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1103 that it doesn't attempt to allocate a socketpair. This could cause
1104 some problems on Windows systems with overzealous firewalls. Fix for
1105 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1107 - If we mark an OR connection for close based on a cell we process,
1108 don't process any further cells on it. We already avoid further
1109 reads on marked-for-close connections, but now we also discard the
1110 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1111 which was the first version where we might mark a connection for
1112 close based on processing a cell on it.
1113 - Correctly sanity-check that we don't underflow on a memory
1114 allocation (and then assert) for hidden service introduction
1115 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1116 bugfix on 0.2.1.5-alpha.
1117 - Fix a memory leak when we check whether a hidden service
1118 descriptor has any usable introduction points left. Fixes bug
1119 4424. Bugfix on 0.2.2.25-alpha.
1120 - Don't crash when we're running as a relay and don't have a GeoIP
1121 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
1122 we've had in the 0.2.3.x branch already.
1123 - When running as a client, do not print a misleading (and plain
1124 wrong) log message that we're collecting "directory request"
1125 statistics: clients don't collect statistics. Also don't create a
1126 useless (because empty) stats file in the stats/ directory. Fixes
1127 bug 4353; bugfix on 0.2.2.34.
1130 - Detect failure to initialize Libevent. This fix provides better
1131 detection for future instances of bug 4457.
1132 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1133 function. This was eating up hideously large amounts of time on some
1134 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1135 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1136 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1138 - Don't warn about unused log_mutex in log.c when building with
1139 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1140 0.1.0.6-rc which introduced --disable-threads.
1141 - When configuring, starting, or stopping an NT service, stop
1142 immediately after the service configuration attempt has succeeded
1143 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1144 - When sending a NETINFO cell, include the original address
1145 received for the other side, not its canonical address. Found
1146 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1147 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
1148 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1149 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1150 occurred when a client tried to fetch a descriptor for a bridge
1151 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1152 - Backport fixes for a pair of compilation warnings on Windows.
1153 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
1154 - If we had ever tried to call tor_addr_to_str on an address of
1155 unknown type, we would have done a strdup on an uninitialized
1156 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1157 Reported by "troll_un".
1158 - Correctly detect and handle transient lookup failures from
1159 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1160 Reported by "troll_un".
1161 - Fix null-pointer access that could occur if TLS allocation failed.
1162 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1163 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1164 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1167 - Add two new config options for directory authorities:
1168 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
1169 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
1170 that is always sufficient to satisfy the bandwidth requirement for
1171 the Guard flag. Now it will be easier for researchers to simulate
1172 Tor networks with different values. Resolves ticket 4484.
1173 - When Tor ignores a hidden service specified in its configuration,
1174 include the hidden service's directory in the warning message.
1175 Previously, we would only tell the user that some hidden service
1176 was ignored. Bugfix on 0.0.6; fixes bug 4426.
1177 - Update to the December 6 2011 Maxmind GeoLite Country database.
1179 o Packaging changes:
1180 - Make it easier to automate expert package builds on Windows,
1181 by removing an absolute path from makensis.exe command.
1184 Changes in version 0.2.3.9-alpha - 2011-12-08
1185 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
1186 a "DisableNetwork" security feature that bundles can use to avoid
1187 touching the network until bridges are configured, moves forward on
1188 the pluggable transport design, fixes a flaw in the hidden service
1189 design that unnecessarily prevented clients with wrong clocks from
1190 reaching hidden services, and fixes a wide variety of other issues.
1193 - Clients can now connect to private bridges over IPv6. Bridges
1194 still need at least one IPv4 address in order to connect to
1195 other relays. Note that we don't yet handle the case where the
1196 user has two bridge lines for the same bridge (one IPv4, one
1197 IPv6). Implements parts of proposal 186.
1198 - New "DisableNetwork" config option to prevent Tor from launching any
1199 connections or accepting any connections except on a control port.
1200 Bundles and controllers can set this option before letting Tor talk
1201 to the rest of the network, for example to prevent any connections
1202 to a non-bridge address. Packages like Orbot can also use this
1203 option to instruct Tor to save power when the network is off.
1204 - Clients and bridges can now be configured to use a separate
1205 "transport" proxy. This approach makes the censorship arms race
1206 easier by allowing bridges to use protocol obfuscation plugins. It
1207 implements the "managed proxy" part of proposal 180 (ticket 3472).
1208 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
1209 implementation. It makes AES_CTR about 7% faster than our old one
1210 (which was about 10% faster than the one OpenSSL used to provide).
1211 Resolves ticket 4526.
1212 - Add a "tor2web mode" for clients that want to connect to hidden
1213 services non-anonymously (and possibly more quickly). As a safety
1214 measure to try to keep users from turning this on without knowing
1215 what they are doing, tor2web mode must be explicitly enabled at
1216 compile time, and a copy of Tor compiled to run in tor2web mode
1217 cannot be used as a normal Tor client. Implements feature 2553.
1218 - Add experimental support for running on Windows with IOCP and no
1219 kernel-space socket buffers. This feature is controlled by a new
1220 "UserspaceIOCPBuffers" config option (off by default), which has
1221 no effect unless Tor has been built with support for bufferevents,
1222 is running on Windows, and has enabled IOCP. This may, in the long
1223 run, help solve or mitigate bug 98.
1224 - Use a more secure consensus parameter voting algorithm. Now at
1225 least three directory authorities or a majority of them must
1226 vote on a given parameter before it will be included in the
1227 consensus. Implements proposal 178.
1230 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
1231 They used to check that the timestamp was within 30 minutes
1232 of their system clock, so they could cap the size of their
1233 replay-detection cache, but that approach unnecessarily refused
1234 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
1235 the v3 intro-point protocol (the first one which sent a timestamp
1236 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
1237 - Only use the EVP interface when AES acceleration is enabled,
1238 to avoid a 5-7% performance regression. Resolves issue 4525;
1239 bugfix on 0.2.3.8-alpha.
1241 o Privacy/anonymity features (bridge detection):
1242 - Make bridge SSL certificates a bit more stealthy by using random
1243 serial numbers, in the same fashion as OpenSSL when generating
1244 self-signed certificates. Implements ticket 4584.
1245 - Introduce a new config option "DynamicDHGroups", enabled by
1246 default, which provides each bridge with a unique prime DH modulus
1247 to be used during SSL handshakes. This option attempts to help
1248 against censors who might use the Apache DH modulus as a static
1249 identifier for bridges. Addresses ticket 4548.
1251 o Minor features (new/different config options):
1252 - New configuration option "DisableDebuggerAttachment" (on by default)
1253 to prevent basic debugging attachment attempts by other processes.
1254 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
1255 - Allow MapAddress directives to specify matches against super-domains,
1256 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
1257 Implements issue 933.
1258 - Slightly change behavior of "list" options (that is, config
1259 options that can appear more than once) when they appear both in
1260 torrc and on the command line. Previously, the command-line options
1261 would be appended to the ones from torrc. Now, the command-line
1262 options override the torrc options entirely. This new behavior
1263 allows the user to override list options (like exit policies and
1264 ports to listen on) from the command line, rather than simply
1265 appending to the list.
1266 - You can get the old (appending) command-line behavior for "list"
1267 options by prefixing the option name with a "+".
1268 - You can remove all the values for a "list" option from the command
1269 line without adding any new ones by prefixing the option name
1271 - Add experimental support for a "defaults" torrc file to be parsed
1272 before the regular torrc. Torrc options override the defaults file's
1273 options in the same way that the command line overrides the torrc.
1274 The SAVECONF controller command saves only those options which
1275 differ between the current configuration and the defaults file. HUP
1276 reloads both files. (Note: This is an experimental feature; its
1277 behavior will probably be refined in future 0.2.3.x-alpha versions
1278 to better meet packagers' needs.) Implements task 4552.
1281 - Try to make the introductory warning message that Tor prints on
1282 startup more useful for actually finding help and information.
1283 Resolves ticket 2474.
1284 - Running "make version" now displays the version of Tor that
1285 we're about to build. Idea from katmagic; resolves issue 4400.
1286 - Expire old or over-used hidden service introduction points.
1287 Required by fix for bug 3460.
1288 - Move the replay-detection cache for the RSA-encrypted parts of
1289 INTRODUCE2 cells to the introduction point data structures.
1290 Previously, we would use one replay-detection cache per hidden
1291 service. Required by fix for bug 3460.
1292 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
1293 public key replay-detection cache from 60 minutes to 5 minutes. This
1294 replay-detection cache is now used only to detect multiple
1295 INTRODUCE2 cells specifying the same rendezvous point, so we can
1296 avoid launching multiple simultaneous attempts to connect to it.
1298 o Minor bugfixes (on Tor 0.2.2.x and earlier):
1299 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1300 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1302 - Fix a minor formatting issue in one of tor-gencert's error messages.
1304 - Prevent a false positive from the check-spaces script, by disabling
1305 the "whitespace between function name and (" check for functions
1307 - Fix a log message suggesting that people contact a non-existent
1308 email address. Fixes bug 3448.
1309 - Fix null-pointer access that could occur if TLS allocation failed.
1310 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1311 - Report a real bootstrap problem to the controller on router
1312 identity mismatch. Previously we just said "foo", which probably
1313 made a lot of sense at the time. Fixes bug 4169; bugfix on
1315 - If we had ever tried to call tor_addr_to_str() on an address of
1316 unknown type, we would have done a strdup() on an uninitialized
1317 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1318 Reported by "troll_un".
1319 - Correctly detect and handle transient lookup failures from
1320 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1321 Reported by "troll_un".
1322 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1323 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1324 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
1325 bug 4532; found by "troll_un".
1327 o Minor bugfixes (on Tor 0.2.3.x):
1328 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
1330 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
1331 circuit for use as a hidden service client's rendezvous point.
1332 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
1333 with help from wanoskarnet.
1334 - Restore behavior of overriding SocksPort, ORPort, and similar
1335 options from the command line. Bugfix on 0.2.3.3-alpha.
1338 - Properly handle the case where the build-tree is not the same
1339 as the source tree when generating src/common/common_sha1.i,
1340 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
1341 bugfix on 0.2.0.1-alpha.
1343 o Code simplifications, cleanups, and refactorings:
1344 - Remove the pure attribute from all functions that used it
1345 previously. In many cases we assigned it incorrectly, because the
1346 functions might assert or call impure functions, and we don't have
1347 evidence that keeping the pure attribute is worthwhile. Implements
1348 changes suggested in ticket 4421.
1349 - Remove some dead code spotted by coverity. Fixes cid 432.
1350 Bugfix on 0.2.3.1-alpha, closes bug 4637.
1353 Changes in version 0.2.3.8-alpha - 2011-11-22
1354 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
1355 socketpair-related bug that has been bothering Windows users. It adds
1356 support to serve microdescriptors to controllers, so Vidalia's network
1357 map can resume listing relays (once Vidalia implements its side),
1358 and adds better support for hardware AES acceleration. Finally, it
1359 starts the process of adjusting the bandwidth cutoff for getting the
1360 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
1361 that tiny relays harm performance more than they help network capacity.
1364 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1365 that it doesn't attempt to allocate a socketpair. This could cause
1366 some problems on Windows systems with overzealous firewalls. Fix for
1367 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1369 - Correctly sanity-check that we don't underflow on a memory
1370 allocation (and then assert) for hidden service introduction
1371 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1372 bugfix on 0.2.1.5-alpha.
1373 - Remove the artificially low cutoff of 20KB to guarantee the Fast
1374 flag. In the past few years the average relay speed has picked
1375 up, and while the "top 7/8 of the network get the Fast flag" and
1376 "all relays with 20KB or more of capacity get the Fast flag" rules
1377 used to have the same result, now the top 7/8 of the network has
1378 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
1379 - Fix a rare assertion failure when checking whether a v0 hidden
1380 service descriptor has any usable introduction points left, and
1381 we don't have enough information to build a circuit to the first
1382 intro point named in the descriptor. The HS client code in
1383 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
1384 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
1385 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
1386 - Make bridge authorities not crash when they are asked for their own
1387 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
1388 - When running as a client, do not print a misleading (and plain
1389 wrong) log message that we're collecting "directory request"
1390 statistics: clients don't collect statistics. Also don't create a
1391 useless (because empty) stats file in the stats/ directory. Fixes
1392 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
1395 - Allow Tor controllers like Vidalia to obtain the microdescriptor
1396 for a relay by identity digest or nickname. Previously,
1397 microdescriptors were only available by their own digests, so a
1398 controller would have to ask for and parse the whole microdescriptor
1399 consensus in order to look up a single relay's microdesc. Fixes
1400 bug 3832; bugfix on 0.2.3.1-alpha.
1401 - Use OpenSSL's EVP interface for AES encryption, so that all AES
1402 operations can use hardware acceleration (if present). Resolves
1405 o Minor bugfixes (on 0.2.2.x and earlier):
1406 - Detect failure to initialize Libevent. This fix provides better
1407 detection for future instances of bug 4457.
1408 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1409 function. This was eating up hideously large amounts of time on some
1410 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1411 - Don't warn about unused log_mutex in log.c when building with
1412 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1413 0.1.0.6-rc which introduced --disable-threads.
1414 - Allow manual 'authenticate' commands to the controller interface
1415 from netcat (nc) as well as telnet. We were rejecting them because
1416 they didn't come with the expected whitespace at the end of the
1417 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
1418 - Fix some (not actually triggerable) buffer size checks in usage of
1419 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
1421 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
1422 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
1423 - When configuring, starting, or stopping an NT service, stop
1424 immediately after the service configuration attempt has succeeded
1425 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1426 - When sending a NETINFO cell, include the original address
1427 received for the other side, not its canonical address. Found
1428 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1429 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
1430 can pick them up when the tests aren't disabled. Bugfix on
1431 0.2.2.4-alpha which introduced tinytest.
1432 - Fix a memory leak when we check whether a hidden service
1433 descriptor has any usable introduction points left. Fixes bug
1434 4424. Bugfix on 0.2.2.25-alpha.
1435 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1436 occurred when a client tried to fetch a descriptor for a bridge
1437 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1439 o Minor bugfixes (on 0.2.3.x):
1440 - Make util unit tests build correctly with MSVC. Bugfix on
1441 0.2.3.3-alpha. Patch by Gisle Vanem.
1442 - Successfully detect AUTH_CHALLENGE cells with no recognized
1443 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
1445 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
1446 it should still send a NETINFO cell to allow the connection to
1447 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
1449 - Log less loudly when we get an invalid authentication certificate
1450 from a source other than a directory authority: it's not unusual
1451 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
1453 - Tolerate servers with more clock skew in their authentication
1454 certificates than previously. Fixes bug 4371; bugfix on
1456 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
1457 on 0.2.3.4-alpha and 0.2.3.6-alpha.
1460 - Add two new config options for directory authorities:
1461 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
1462 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
1463 that is always sufficient to satisfy the bandwidth requirement for
1464 the Guard flag. Now it will be easier for researchers to simulate
1465 Tor networks with different values. Resolves ticket 4484.
1466 - When Tor ignores a hidden service specified in its configuration,
1467 include the hidden service's directory in the warning message.
1468 Previously, we would only tell the user that some hidden service
1469 was ignored. Bugfix on 0.0.6; fixes bug 4426.
1470 - When we fail to initialize Libevent, retry with IOCP disabled so we
1471 don't need to turn on multi-threading support in Libevent, which in
1472 turn requires a working socketpair(). This is a workaround for bug
1473 4457, which affects Libevent versions from 2.0.1-alpha through
1475 - Detect when we try to build on a platform that doesn't define
1476 AF_UNSPEC to 0. We don't work there, so refuse to compile.
1477 - Update to the November 1 2011 Maxmind GeoLite Country database.
1479 o Packaging changes:
1480 - Make it easier to automate expert package builds on Windows,
1481 by removing an absolute path from makensis.exe command.
1483 o Code simplifications and refactoring:
1484 - Remove some redundant #include directives throughout the code.
1485 Patch from Andrea Gelmini.
1486 - Unconditionally use OpenSSL's AES implementation instead of our
1487 old built-in one. OpenSSL's AES has been better for a while, and
1488 relatively few servers should still be on any version of OpenSSL
1489 that doesn't have good optimized assembly AES.
1490 - Use the name "CERTS" consistently to refer to the new cell type;
1491 we were calling it CERT in some places and CERTS in others.
1494 - Numerous new unit tests for functions in util.c and address.c by
1496 - The long-disabled benchmark tests are now split into their own
1497 ./src/test/bench binary.
1498 - The benchmark tests can now use more accurate timers than
1499 gettimeofday() when such timers are available.
1502 Changes in version 0.2.3.7-alpha - 2011-10-30
1503 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
1504 the new v3 handshake. It also resolves yet another bridge address
1508 - If we mark an OR connection for close based on a cell we process,
1509 don't process any further cells on it. We already avoid further
1510 reads on marked-for-close connections, but now we also discard the
1511 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1512 which was the first version where we might mark a connection for
1513 close based on processing a cell on it.
1514 - Fix a double-free bug that would occur when we received an invalid
1515 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
1516 bugfix on 0.2.3.6-alpha.
1517 - Bridges no longer include their address in NETINFO cells on outgoing
1518 OR connections, to allow them to blend in better with clients.
1519 Removes another avenue for enumerating bridges. Reported by
1520 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
1521 cells were introduced.
1524 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
1525 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1528 Changes in version 0.2.3.6-alpha - 2011-10-26
1529 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
1530 anonymity vulnerability where an attacker can deanonymize Tor
1531 users. Everybody should upgrade.
1533 This release also features support for a new v3 connection handshake
1534 protocol, and fixes to make hidden service connections more robust.
1537 - Implement a new handshake protocol (v3) for authenticating Tors to
1538 each other over TLS. It should be more resistant to fingerprinting
1539 than previous protocols, and should require less TLS hacking for
1540 future Tor implementations. Implements proposal 176.
1541 - Allow variable-length padding cells to disguise the length of
1542 Tor's TLS records. Implements part of proposal 184.
1544 o Privacy/anonymity fixes (clients):
1545 - Clients and bridges no longer send TLS certificate chains on
1546 outgoing OR connections. Previously, each client or bridge would
1547 use the same cert chain for all outgoing OR connections until
1548 its IP address changes, which allowed any relay that the client
1549 or bridge contacted to determine which entry guards it is using.
1550 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1551 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1552 no longer considers that connection as suitable for satisfying a
1553 circuit EXTEND request. Now relays can protect clients from the
1554 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1555 - Directory authorities no longer assign the Guard flag to relays
1556 that haven't upgraded to the above "refuse EXTEND requests
1557 to client connections" fix. Now directory authorities can
1558 protect clients from the CVE-2011-2768 issue even if neither
1559 the clients nor the relays have upgraded yet. There's a new
1560 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1561 to let us transition smoothly, else tomorrow there would be no
1564 o Major bugfixes (hidden services):
1565 - Improve hidden service robustness: when an attempt to connect to
1566 a hidden service ends, be willing to refetch its hidden service
1567 descriptors from each of the HSDir relays responsible for them
1568 immediately. Previously, we would not consider refetching the
1569 service's descriptors from each HSDir for 15 minutes after the last
1570 fetch, which was inconvenient if the hidden service was not running
1571 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
1572 - When one of a hidden service's introduction points appears to be
1573 unreachable, stop trying it. Previously, we would keep trying
1574 to build circuits to the introduction point until we lost the
1575 descriptor, usually because the user gave up and restarted Tor.
1576 Partly fixes bug 3825.
1577 - Don't launch a useless circuit after failing to use one of a
1578 hidden service's introduction points. Previously, we would
1579 launch a new introduction circuit, but not set the hidden service
1580 which that circuit was intended to connect to, so it would never
1581 actually be used. A different piece of code would then create a
1582 new introduction circuit correctly. Bug reported by katmagic and
1583 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1585 o Major bugfixes (other):
1586 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1587 that they initiated. Relays could distinguish incoming bridge
1588 connections from client connections, creating another avenue for
1589 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1590 Found by "frosty_un".
1591 - Don't update the AccountingSoftLimitHitAt state file entry whenever
1592 tor gets started. This prevents a wrong average bandwidth
1593 estimate, which would cause relays to always start a new accounting
1594 interval at the earliest possible moment. Fixes bug 2003; bugfix
1595 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
1596 immensely in tracking this bug down.
1597 - Fix a crash bug when changing node restrictions while a DNS lookup
1598 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
1601 o Minor bugfixes (on 0.2.2.x and earlier):
1602 - When a hidden service turns an extra service-side introduction
1603 circuit into a general-purpose circuit, free the rend_data and
1604 intro_key fields first, so we won't leak memory if the circuit
1605 is cannibalized for use as another service-side introduction
1606 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
1607 - Rephrase the log message emitted if the TestSocks check is
1608 successful. Patch from Fabian Keil; fixes bug 4094.
1609 - Bridges now skip DNS self-tests, to act a little more stealthily.
1610 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
1611 bridges. Patch by "warms0x".
1612 - Remove a confusing dollar sign from the example fingerprint in the
1613 man page, and also make the example fingerprint a valid one. Fixes
1614 bug 4309; bugfix on 0.2.1.3-alpha.
1615 - Fix internal bug-checking logic that was supposed to catch
1616 failures in digest generation so that it will fail more robustly
1617 if we ask for a nonexistent algorithm. Found by Coverity Scan.
1618 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
1619 - Report any failure in init_keys() calls launched because our
1620 IP address has changed. Spotted by Coverity Scan. Bugfix on
1621 0.1.1.4-alpha; fixes CID 484.
1623 o Minor bugfixes (on 0.2.3.x):
1624 - Fix a bug in configure.in that kept it from building a configure
1625 script with autoconf versions earlier than 2.61. Fixes bug 2430;
1626 bugfix on 0.2.3.1-alpha.
1627 - Don't warn users that they are exposing a client port to the
1628 Internet if they have specified an RFC1918 address. Previously,
1629 we would warn if the user had specified any non-loopback
1630 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
1631 - Fix memory leaks in the failing cases of the new SocksPort and
1632 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
1633 fixes coverity CIDs 485, 486, and 487.
1636 - When a hidden service's introduction point times out, consider
1637 trying it again during the next attempt to connect to the
1638 HS. Previously, we would not try it again unless a newly fetched
1639 descriptor contained it. Required by fixes for bugs 1297 and 3825.
1640 - The next version of Windows will be called Windows 8, and it has
1641 a major version of 6, minor version of 2. Correctly identify that
1642 version instead of calling it "Very recent version". Resolves
1643 ticket 4153; reported by funkstar.
1644 - The Bridge Authority now writes statistics on how many bridge
1645 descriptors it gave out in total, and how many unique descriptors
1646 it gave out. It also lists how often the most and least commonly
1647 fetched descriptors were given out, as well as the median and
1648 25th/75th percentile. Implements tickets 4200 and 4294.
1649 - Update to the October 4 2011 Maxmind GeoLite Country database.
1651 o Code simplifications and refactoring:
1652 - Remove some old code to remember statistics about which descriptors
1653 we've served as a directory mirror. The feature wasn't used and
1654 is outdated now that microdescriptors are around.
1655 - Rename Tor functions that turn strings into addresses, so that
1656 "parse" indicates that no hostname resolution occurs, and
1657 "lookup" indicates that hostname resolution may occur. This
1658 should help prevent mistakes in the future. Fixes bug 3512.
1661 Changes in version 0.2.2.34 - 2011-10-26
1662 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
1663 can deanonymize Tor users. Everybody should upgrade.
1665 The attack relies on four components: 1) Clients reuse their TLS cert
1666 when talking to different relays, so relays can recognize a user by
1667 the identity key in her cert. 2) An attacker who knows the client's
1668 identity key can probe each guard relay to see if that identity key
1669 is connected to that guard relay right now. 3) A variety of active
1670 attacks in the literature (starting from "Low-Cost Traffic Analysis
1671 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
1672 discover the guard relays that a Tor user visiting the website is using.
1673 4) Clients typically pick three guards at random, so the set of guards
1674 for a given user could well be a unique fingerprint for her. This
1675 release fixes components #1 and #2, which is enough to block the attack;
1676 the other two remain as open research problems. Special thanks to
1677 "frosty_un" for reporting the issue to us!
1679 Clients should upgrade so they are no longer recognizable by the TLS
1680 certs they present. Relays should upgrade so they no longer allow a
1681 remote attacker to probe them to test whether unpatched clients are
1682 currently connected to them.
1684 This release also fixes several vulnerabilities that allow an attacker
1685 to enumerate bridge relays. Some bridge enumeration attacks still
1686 remain; see for example proposal 188.
1688 o Privacy/anonymity fixes (clients):
1689 - Clients and bridges no longer send TLS certificate chains on
1690 outgoing OR connections. Previously, each client or bridge would
1691 use the same cert chain for all outgoing OR connections until
1692 its IP address changes, which allowed any relay that the client
1693 or bridge contacted to determine which entry guards it is using.
1694 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1695 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1696 no longer considers that connection as suitable for satisfying a
1697 circuit EXTEND request. Now relays can protect clients from the
1698 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1699 - Directory authorities no longer assign the Guard flag to relays
1700 that haven't upgraded to the above "refuse EXTEND requests
1701 to client connections" fix. Now directory authorities can
1702 protect clients from the CVE-2011-2768 issue even if neither
1703 the clients nor the relays have upgraded yet. There's a new
1704 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1705 to let us transition smoothly, else tomorrow there would be no
1708 o Privacy/anonymity fixes (bridge enumeration):
1709 - Bridge relays now do their directory fetches inside Tor TLS
1710 connections, like all the other clients do, rather than connecting
1711 directly to the DirPort like public relays do. Removes another
1712 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
1713 - Bridges relays now build circuits for themselves in a more similar
1714 way to how clients build them. Removes another avenue for
1715 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
1716 when bridges were introduced.
1717 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1718 that they initiated. Relays could distinguish incoming bridge
1719 connections from client connections, creating another avenue for
1720 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1721 Found by "frosty_un".
1724 - Fix a crash bug when changing node restrictions while a DNS lookup
1725 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
1727 - Don't launch a useless circuit after failing to use one of a
1728 hidden service's introduction points. Previously, we would
1729 launch a new introduction circuit, but not set the hidden service
1730 which that circuit was intended to connect to, so it would never
1731 actually be used. A different piece of code would then create a
1732 new introduction circuit correctly. Bug reported by katmagic and
1733 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1736 - Change an integer overflow check in the OpenBSD_Malloc code so
1737 that GCC is less likely to eliminate it as impossible. Patch
1738 from Mansour Moufid. Fixes bug 4059.
1739 - When a hidden service turns an extra service-side introduction
1740 circuit into a general-purpose circuit, free the rend_data and
1741 intro_key fields first, so we won't leak memory if the circuit
1742 is cannibalized for use as another service-side introduction
1743 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
1744 - Bridges now skip DNS self-tests, to act a little more stealthily.
1745 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
1746 bridges. Patch by "warms0x".
1747 - Fix internal bug-checking logic that was supposed to catch
1748 failures in digest generation so that it will fail more robustly
1749 if we ask for a nonexistent algorithm. Found by Coverity Scan.
1750 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
1751 - Report any failure in init_keys() calls launched because our
1752 IP address has changed. Spotted by Coverity Scan. Bugfix on
1753 0.1.1.4-alpha; fixes CID 484.
1755 o Minor bugfixes (log messages and documentation):
1756 - Remove a confusing dollar sign from the example fingerprint in the
1757 man page, and also make the example fingerprint a valid one. Fixes
1758 bug 4309; bugfix on 0.2.1.3-alpha.
1759 - The next version of Windows will be called Windows 8, and it has
1760 a major version of 6, minor version of 2. Correctly identify that
1761 version instead of calling it "Very recent version". Resolves
1762 ticket 4153; reported by funkstar.
1763 - Downgrade log messages about circuit timeout calibration from
1764 "notice" to "info": they don't require or suggest any human
1765 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
1766 bugfix on 0.2.2.14-alpha.
1769 - Turn on directory request statistics by default and include them in
1770 extra-info descriptors. Don't break if we have no GeoIP database.
1771 Backported from 0.2.3.1-alpha; implements ticket 3951.
1772 - Update to the October 4 2011 Maxmind GeoLite Country database.
1775 Changes in version 0.2.1.31 - 2011-10-26
1776 Tor 0.2.1.31 backports important security and privacy fixes for
1777 oldstable. This release is intended only for package maintainers and
1778 others who cannot use the 0.2.2 stable series. All others should be
1779 using Tor 0.2.2.x or newer.
1781 o Security fixes (also included in 0.2.2.x):
1782 - Replace all potentially sensitive memory comparison operations
1783 with versions whose runtime does not depend on the data being
1784 compared. This will help resist a class of attacks where an
1785 adversary can use variations in timing information to learn
1786 sensitive data. Fix for one case of bug 3122. (Safe memcmp
1787 implementation by Robert Ransom based partially on code by DJB.)
1788 - Fix an assert in parsing router descriptors containing IPv6
1789 addresses. This one took down the directory authorities when
1790 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
1792 o Privacy/anonymity fixes (also included in 0.2.2.x):
1793 - Clients and bridges no longer send TLS certificate chains on
1794 outgoing OR connections. Previously, each client or bridge would
1795 use the same cert chain for all outgoing OR connections until
1796 its IP address changes, which allowed any relay that the client
1797 or bridge contacted to determine which entry guards it is using.
1798 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1799 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1800 no longer considers that connection as suitable for satisfying a
1801 circuit EXTEND request. Now relays can protect clients from the
1802 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1803 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1804 that they initiated. Relays could distinguish incoming bridge
1805 connections from client connections, creating another avenue for
1806 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1807 Found by "frosty_un".
1808 - When receiving a hidden service descriptor, check that it is for
1809 the hidden service we wanted. Previously, Tor would store any
1810 hidden service descriptors that a directory gave it, whether it
1811 wanted them or not. This wouldn't have let an attacker impersonate
1812 a hidden service, but it did let directories pre-seed a client
1813 with descriptors that it didn't want. Bugfix on 0.0.6.
1814 - Avoid linkability based on cached hidden service descriptors: forget
1815 all hidden service descriptors cached as a client when processing a
1816 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
1817 - Make the bridge directory authority refuse to answer directory
1818 requests for "all" descriptors. It used to include bridge
1819 descriptors in its answer, which was a major information leak.
1820 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
1821 - Don't attach new streams to old rendezvous circuits after SIGNAL
1822 NEWNYM. Previously, we would keep using an existing rendezvous
1823 circuit if it remained open (i.e. if it were kept open by a
1824 long-lived stream, or if a new stream were attached to it before
1825 Tor could notice that it was old and no longer in use). Bugfix on
1826 0.1.1.15-rc; fixes bug 3375.
1828 o Minor bugfixes (also included in 0.2.2.x):
1829 - When we restart our relay, we might get a successful connection
1830 from the outside before we've started our reachability tests,
1831 triggering a warning: "ORPort found reachable, but I have no
1832 routerinfo yet. Failing to inform controller of success." This
1833 bug was harmless unless Tor is running under a controller
1834 like Vidalia, in which case the controller would never get a
1835 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
1837 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
1838 enabled. Fixes bug 1526.
1839 - Remove undocumented option "-F" from tor-resolve: it hasn't done
1840 anything since 0.2.1.16-rc.
1841 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
1842 None of the cases where we did this before were wrong, but by making
1843 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
1844 - Fix a rare crash bug that could occur when a client was configured
1845 with a large number of bridges. Fixes bug 2629; bugfix on
1846 0.2.1.2-alpha. Bugfix by trac user "shitlei".
1847 - Correct the warning displayed when a rendezvous descriptor exceeds
1848 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
1850 - Fix an uncommon assertion failure when running with DNSPort under
1851 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
1852 - When warning about missing zlib development packages during compile,
1853 give the correct package names. Bugfix on 0.2.0.1-alpha.
1854 - Require that introduction point keys and onion keys have public
1855 exponent 65537. Bugfix on 0.2.0.10-alpha.
1856 - Do not crash when our configuration file becomes unreadable, for
1857 example due to a permissions change, between when we start up
1858 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
1860 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
1862 - Always NUL-terminate the sun_path field of a sockaddr_un before
1863 passing it to the kernel. (Not a security issue: kernels are
1864 smart enough to reject bad sockaddr_uns.) Found by Coverity;
1865 CID #428. Bugfix on Tor 0.2.0.3-alpha.
1866 - Don't stack-allocate the list of supplementary GIDs when we're
1867 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
1868 could take up to 256K, which is way too much stack. Found by
1869 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
1871 o Minor bugfixes (only in 0.2.1.x):
1872 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
1873 rely on them. Bugfix on 0.2.1.30.
1874 - Use git revisions instead of svn revisions when generating our
1875 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
1877 o Minor features (also included in 0.2.2.x):
1878 - Adjust the expiration time on our SSL session certificates to
1879 better match SSL certs seen in the wild. Resolves ticket 4014.
1880 - Allow nameservers with IPv6 address. Resolves bug 2574.
1881 - Update to the October 4 2011 Maxmind GeoLite Country database.
1884 Changes in version 0.2.3.5-alpha - 2011-09-28
1885 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
1886 bridge relays; fixes an assertion error that many users started hitting
1887 today; and adds the ability to refill token buckets more often than
1888 once per second, allowing significant performance improvements.
1891 - Bridge relays now do their directory fetches inside Tor TLS
1892 connections, like all the other clients do, rather than connecting
1893 directly to the DirPort like public relays do. Removes another
1894 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
1895 - Bridges relays now build circuits for themselves in a more similar
1896 way to how clients build them. Removes another avenue for
1897 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
1898 when bridges were introduced.
1901 - Fix an "Assertion md->held_by_node == 1 failed" error that could
1902 occur when the same microdescriptor was referenced by two node_t
1903 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
1905 o Major features (networking):
1906 - Add a new TokenBucketRefillInterval option to refill token buckets
1907 more frequently than once per second. This should improve network
1908 performance, alleviate queueing problems, and make traffic less
1909 bursty. Implements proposal 183; closes ticket 3630. Design by
1910 Florian Tschorsch and Björn Scheuermann; implementation by
1914 - Change an integer overflow check in the OpenBSD_Malloc code so
1915 that GCC is less likely to eliminate it as impossible. Patch
1916 from Mansour Moufid. Fixes bug 4059.
1918 o Minor bugfixes (usability):
1919 - Downgrade log messages about circuit timeout calibration from
1920 "notice" to "info": they don't require or suggest any human
1921 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
1922 bugfix on 0.2.2.14-alpha.
1924 o Minor features (diagnostics):
1925 - When the system call to create a listener socket fails, log the
1926 error message explaining why. This may help diagnose bug 4027.
1929 Changes in version 0.2.3.4-alpha - 2011-09-13
1930 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
1931 tweak to Tor's TLS handshake that makes relays and bridges that run
1932 this new version reachable from Iran again. It also fixes a few new
1933 bugs in 0.2.3.x, and teaches relays to recognize when they're not
1934 listed in the network consensus and republish.
1936 o Major bugfixes (also part of 0.2.2.33):
1937 - Avoid an assertion failure when reloading a configuration with
1938 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
1939 3923; bugfix on 0.2.2.25-alpha.
1941 o Minor features (security, also part of 0.2.2.33):
1942 - Check for replays of the public-key encrypted portion of an
1943 INTRODUCE1 cell, in addition to the current check for replays of
1944 the g^x value. This prevents a possible class of active attacks
1945 by an attacker who controls both an introduction point and a
1946 rendezvous point, and who uses the malleability of AES-CTR to
1947 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
1948 that these attacks is infeasible (requiring the attacker to send
1949 on the order of zettabytes of altered cells in a short interval),
1950 but we'd rather block them off in case there are any classes of
1951 this attack that we missed. Reported by Willem Pinckaers.
1953 o Minor features (also part of 0.2.2.33):
1954 - Adjust the expiration time on our SSL session certificates to
1955 better match SSL certs seen in the wild. Resolves ticket 4014.
1956 - Change the default required uptime for a relay to be accepted as
1957 a HSDir (hidden service directory) from 24 hours to 25 hours.
1958 Improves on 0.2.0.10-alpha; resolves ticket 2649.
1959 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
1960 authorities to abstain from voting on assignment of the HSDir
1961 consensus flag. Related to bug 2649.
1962 - Update to the September 6 2011 Maxmind GeoLite Country database.
1964 o Minor bugfixes (also part of 0.2.2.33):
1965 - Demote the 'replay detected' log message emitted when a hidden
1966 service receives the same Diffie-Hellman public key in two different
1967 INTRODUCE2 cells to info level. A normal Tor client can cause that
1968 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
1969 fixes part of bug 2442.
1970 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
1971 level. There is nothing that a hidden service's operator can do
1972 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
1974 - Clarify a log message specifying the characters permitted in
1975 HiddenServiceAuthorizeClient client names. Previously, the log
1976 message said that "[A-Za-z0-9+-_]" were permitted; that could have
1977 given the impression that every ASCII character between "+" and "_"
1978 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
1980 o Build fixes (also part of 0.2.2.33):
1981 - Clean up some code issues that prevented Tor from building on older
1982 BSDs. Fixes bug 3894; reported by "grarpamp".
1983 - Search for a platform-specific version of "ar" when cross-compiling.
1984 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
1987 - Fix a bug where the SocksPort option (for example) would get
1988 ignored and replaced by the default if a SocksListenAddress
1989 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
1993 - Relays now try regenerating and uploading their descriptor more
1994 frequently if they are not listed in the consensus, or if the
1995 version of their descriptor listed in the consensus is too
1996 old. This fix should prevent situations where a server declines
1997 to re-publish itself because it has done so too recently, even
1998 though the authorities decided not to list its recent-enough
1999 descriptor. Fix for bug 3327.
2002 - Relays now include a reason for regenerating their descriptors
2003 in an HTTP header when uploading to the authorities. This will
2004 make it easier to debug descriptor-upload issues in the future.
2005 - When starting as root and then changing our UID via the User
2006 control option, and we have a ControlSocket configured, make sure
2007 that the ControlSocket is owned by the same account that Tor will
2008 run under. Implements ticket 3421; fix by Jérémy Bobbio.
2011 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
2012 utility function used in the control-port code). This shouldn't
2013 ever happen unless Tor is completely out of memory, but if it did
2014 happen and Tor somehow recovered from it, Tor could have sent a log
2015 message to a control port in the middle of a reply to a controller
2016 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
2017 - Make 'FetchUselessDescriptors' cause all descriptor types and
2018 all consensus types (including microdescriptors) to get fetched.
2019 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
2022 - Make a new "entry connection" struct as an internal subtype of "edge
2023 connection", to simplify the code and make exit connections smaller.
2026 Changes in version 0.2.2.33 - 2011-09-13
2027 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
2028 TLS handshake that makes relays and bridges that run this new version
2029 reachable from Iran again.
2032 - Avoid an assertion failure when reloading a configuration with
2033 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2034 3923; bugfix on 0.2.2.25-alpha.
2036 o Minor features (security):
2037 - Check for replays of the public-key encrypted portion of an
2038 INTRODUCE1 cell, in addition to the current check for replays of
2039 the g^x value. This prevents a possible class of active attacks
2040 by an attacker who controls both an introduction point and a
2041 rendezvous point, and who uses the malleability of AES-CTR to
2042 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2043 that these attacks are infeasible (requiring the attacker to send
2044 on the order of zettabytes of altered cells in a short interval),
2045 but we'd rather block them off in case there are any classes of
2046 this attack that we missed. Reported by Willem Pinckaers.
2049 - Adjust the expiration time on our SSL session certificates to
2050 better match SSL certs seen in the wild. Resolves ticket 4014.
2051 - Change the default required uptime for a relay to be accepted as
2052 a HSDir (hidden service directory) from 24 hours to 25 hours.
2053 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2054 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2055 authorities to abstain from voting on assignment of the HSDir
2056 consensus flag. Related to bug 2649.
2057 - Update to the September 6 2011 Maxmind GeoLite Country database.
2059 o Minor bugfixes (documentation and log messages):
2060 - Correct the man page to explain that HashedControlPassword and
2061 CookieAuthentication can both be set, in which case either method
2062 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2063 when we decided to allow these config options to both be set. Issue
2065 - Demote the 'replay detected' log message emitted when a hidden
2066 service receives the same Diffie-Hellman public key in two different
2067 INTRODUCE2 cells to info level. A normal Tor client can cause that
2068 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2069 fixes part of bug 2442.
2070 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2071 level. There is nothing that a hidden service's operator can do
2072 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2074 - Clarify a log message specifying the characters permitted in
2075 HiddenServiceAuthorizeClient client names. Previously, the log
2076 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2077 given the impression that every ASCII character between "+" and "_"
2078 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2081 - Provide a substitute implementation of lround() for MSVC, which
2082 apparently lacks it. Patch from Gisle Vanem.
2083 - Clean up some code issues that prevented Tor from building on older
2084 BSDs. Fixes bug 3894; reported by "grarpamp".
2085 - Search for a platform-specific version of "ar" when cross-compiling.
2086 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2089 Changes in version 0.2.3.3-alpha - 2011-09-01
2090 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
2091 security, and provides client-side support for the microdescriptor
2092 and optimistic data features introduced earlier in the 0.2.3.x
2093 series. It also includes numerous critical bugfixes in the (optional)
2094 bufferevent-based networking backend.
2096 o Major features (stream isolation):
2097 - You can now configure Tor so that streams from different
2098 applications are isolated on different circuits, to prevent an
2099 attacker who sees your streams as they leave an exit node from
2100 linking your sessions to one another. To do this, choose some way
2101 to distinguish the applications: have them connect to different
2102 SocksPorts, or have one of them use SOCKS4 while the other uses
2103 SOCKS5, or have them pass different authentication strings to the
2104 SOCKS proxy. Then, use the new SocksPort syntax to configure the
2105 degree of isolation you need. This implements Proposal 171.
2106 - There's a new syntax for specifying multiple client ports (such as
2107 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
2108 multiple *Port entries with full addr:port syntax on each.
2109 The old *ListenAddress format is still supported, but you can't
2110 mix it with the new *Port syntax.
2112 o Major features (other):
2113 - Enable microdescriptor fetching by default for clients. This allows
2114 clients to download a much smaller amount of directory information.
2115 To disable it (and go back to the old-style consensus and
2116 descriptors), set "UseMicrodescriptors 0" in your torrc file.
2117 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
2118 "PortForwarding" config option), now supports Windows.
2119 - When using an exit relay running 0.2.3.x, clients can now
2120 "optimistically" send data before the exit relay reports that
2121 the stream has opened. This saves a round trip when starting
2122 connections where the client speaks first (such as web browsing).
2123 This behavior is controlled by a consensus parameter (currently
2124 disabled). To turn it on or off manually, use the "OptimisticData"
2125 torrc option. Implements proposal 181; code by Ian Goldberg.
2127 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
2128 - When using IOCP on Windows, we need to enable Libevent windows
2130 - The IOCP backend now works even when the user has not specified
2131 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
2132 Fixes part of bug 3752.
2133 - Correctly record the bytes we've read and written when using
2134 bufferevents, so that we can include them in our bandwidth history
2135 and advertised bandwidth. Fixes bug 3803.
2136 - Apply rate-limiting only at the bottom of a chain of filtering
2137 bufferevents. This prevents us from filling up internal read
2138 buffers and violating rate-limits when filtering bufferevents
2139 are enabled. Fixes part of bug 3804.
2140 - Add high-watermarks to the output buffers for filtered
2141 bufferevents. This prevents us from filling up internal write
2142 buffers and wasting CPU cycles when filtering bufferevents are
2143 enabled. Fixes part of bug 3804.
2144 - Correctly notice when data has been written from a bufferevent
2145 without flushing it completely. Fixes bug 3805.
2146 - Fix a bug where server-side tunneled bufferevent-based directory
2147 streams would get closed prematurely. Fixes bug 3814.
2148 - Fix a use-after-free error with per-connection rate-limiting
2149 buckets. Fixes bug 3888.
2151 o Major bugfixes (also part of 0.2.2.31-rc):
2152 - If we're configured to write our ControlPorts to disk, only write
2153 them after switching UID and creating the data directory. This way,
2154 we don't fail when starting up with a nonexistent DataDirectory
2155 and a ControlPortWriteToFile setting based on that directory. Fixes
2156 bug 3747; bugfix on Tor 0.2.2.26-beta.
2159 - Added a new CONF_CHANGED event so that controllers can be notified
2160 of any configuration changes made by other controllers, or by the
2161 user. Implements ticket 1692.
2162 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
2163 leak when using bufferevents, and lets Libevent worry about how to
2164 best copy data out of a buffer.
2165 - Replace files in stats/ rather than appending to them. Now that we
2166 include statistics in extra-info descriptors, it makes no sense to
2167 keep old statistics forever. Implements ticket 2930.
2169 o Minor features (build compatibility):
2170 - Limited, experimental support for building with nmake and MSVC.
2171 - Provide a substitute implementation of lround() for MSVC, which
2172 apparently lacks it. Patch from Gisle Vanem.
2174 o Minor features (also part of 0.2.2.31-rc):
2175 - Update to the August 2 2011 Maxmind GeoLite Country database.
2177 o Minor bugfixes (on 0.2.3.x-alpha):
2178 - Fix a spurious warning when parsing SOCKS requests with
2179 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
2180 - Get rid of a harmless warning that could happen on relays running
2181 with bufferevents. The warning was caused by someone doing an http
2182 request to a relay's orport. Also don't warn for a few related
2183 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
2185 o Minor bugfixes (on 2.2.x and earlier):
2186 - Correct the man page to explain that HashedControlPassword and
2187 CookieAuthentication can both be set, in which case either method
2188 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2189 when we decided to allow these config options to both be set. Issue
2191 - The "--quiet" and "--hush" options now apply not only to Tor's
2192 behavior before logs are configured, but also to Tor's behavior in
2193 the absense of configured logs. Fixes bug 3550; bugfix on
2196 o Minor bugfixes (also part of 0.2.2.31-rc):
2197 - Write several files in text mode, on OSes that distinguish text
2198 mode from binary mode (namely, Windows). These files are:
2199 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2200 that collect those statistics; 'client_keys' and 'hostname' for
2201 hidden services that use authentication; and (in the tor-gencert
2202 utility) newly generated identity and signing keys. Previously,
2203 we wouldn't specify text mode or binary mode, leading to an
2204 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2205 the DirRecordUsageByCountry option which would have triggered
2206 the assertion failure was added), although this assertion failure
2207 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2208 - Selectively disable deprecation warnings on OS X because Lion
2209 started deprecating the shipped copy of openssl. Fixes bug 3643.
2210 - Remove an extra pair of quotation marks around the error
2211 message in control-port STATUS_GENERAL BUG events. Bugfix on
2212 0.1.2.6-alpha; fixes bug 3732.
2213 - When unable to format an address as a string, report its value
2214 as "???" rather than reusing the last formatted address. Bugfix
2217 o Code simplifications and refactoring:
2218 - Rewrite the listener-selection logic so that parsing which ports
2219 we want to listen on is now separate from binding to the ports
2223 - Building Tor with bufferevent support now requires Libevent
2224 2.0.13-stable or later. Previous versions of Libevent had bugs in
2225 SSL-related bufferevents and related issues that would make Tor
2226 work badly with bufferevents. Requiring 2.0.13-stable also allows
2227 Tor with bufferevents to take advantage of Libevent APIs
2228 introduced after 2.0.8-rc.
2231 Changes in version 0.2.2.32 - 2011-08-27
2232 The Tor 0.2.2 release series is dedicated to the memory of Andreas
2233 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
2234 a founder of the PETS community, a leader in our field, a mentor,
2235 and a friend. He left us with these words: "I had the possibility
2236 to contribute to this world that is not as it should be. I hope I
2237 could help in some areas to make the world a better place, and that
2238 I could also encourage other people to be engaged in improving the
2239 world. Please, stay engaged. This world needs you, your love, your
2240 initiative -- now I cannot be part of that anymore."
2242 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
2243 ready. More than two years in the making, this release features improved
2244 client performance and hidden service reliability, better compatibility
2245 for Android, correct behavior for bridges that listen on more than
2246 one address, more extensible and flexible directory object handling,
2247 better reporting of network statistics, improved code security, and
2248 many many other features and bugfixes.
2251 Changes in version 0.2.2.31-rc - 2011-08-17
2252 Tor 0.2.2.31-rc is the second and hopefully final release candidate
2253 for the Tor 0.2.2.x series.
2256 - Remove an extra pair of quotation marks around the error
2257 message in control-port STATUS_GENERAL BUG events. Bugfix on
2258 0.1.2.6-alpha; fixes bug 3732.
2259 - If we're configured to write our ControlPorts to disk, only write
2260 them after switching UID and creating the data directory. This way,
2261 we don't fail when starting up with a nonexistent DataDirectory
2262 and a ControlPortWriteToFile setting based on that directory. Fixes
2263 bug 3747; bugfix on Tor 0.2.2.26-beta.
2266 - Update to the August 2 2011 Maxmind GeoLite Country database.
2269 - Allow GETINFO fingerprint to return a fingerprint even when
2270 we have not yet built a router descriptor. Fixes bug 3577;
2271 bugfix on 0.2.0.1-alpha.
2272 - Write several files in text mode, on OSes that distinguish text
2273 mode from binary mode (namely, Windows). These files are:
2274 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2275 that collect those statistics; 'client_keys' and 'hostname' for
2276 hidden services that use authentication; and (in the tor-gencert
2277 utility) newly generated identity and signing keys. Previously,
2278 we wouldn't specify text mode or binary mode, leading to an
2279 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2280 the DirRecordUsageByCountry option which would have triggered
2281 the assertion failure was added), although this assertion failure
2282 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2283 - Selectively disable deprecation warnings on OS X because Lion
2284 started deprecating the shipped copy of openssl. Fixes bug 3643.
2285 - When unable to format an address as a string, report its value
2286 as "???" rather than reusing the last formatted address. Bugfix
2290 Changes in version 0.2.3.2-alpha - 2011-07-18
2291 Tor 0.2.3.2-alpha introduces two new experimental features:
2292 microdescriptors and pluggable transports. It also continues cleaning
2293 up a variety of recently introduced features.
2296 - Clients can now use microdescriptors instead of regular descriptors
2297 to build circuits. Microdescriptors are authority-generated
2298 summaries of regular descriptors' contents, designed to change
2299 very rarely (see proposal 158 for details). This feature is
2300 designed to save bandwidth, especially for clients on slow internet
2301 connections. It's off by default for now, since nearly no caches
2302 support it, but it will be on-by-default for clients in a future
2303 version. You can use the UseMicrodescriptors option to turn it on.
2304 - Tor clients using bridges can now be configured to use a separate
2305 'transport' proxy for each bridge. This approach helps to resist
2306 censorship by allowing bridges to use protocol obfuscation
2307 plugins. It implements part of proposal 180. Implements ticket 2841.
2308 - While we're trying to bootstrap, record how many TLS connections
2309 fail in each state, and report which states saw the most failures
2310 in response to any bootstrap failures. This feature may speed up
2311 diagnosis of censorship events. Implements ticket 3116.
2313 o Major bugfixes (on 0.2.3.1-alpha):
2314 - When configuring a large set of nodes in EntryNodes (as with
2315 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
2316 random subset to be guards, and choose them in random
2317 order. Fixes bug 2798.
2318 - Tor could crash when remembering a consensus in a non-used consensus
2319 flavor without having a current consensus set. Fixes bug 3361.
2320 - Comparing an unknown address to a microdescriptor's shortened exit
2321 policy would always give a "rejected" result. Fixes bug 3599.
2322 - Using microdescriptors as a client no longer prevents Tor from
2323 uploading and downloading hidden service descriptors. Fixes
2327 - Allow nameservers with IPv6 address. Resolves bug 2574.
2328 - Accept attempts to include a password authenticator in the
2329 handshake, as supported by SOCKS5. This handles SOCKS clients that
2330 don't know how to omit a password when authenticating. Resolves
2332 - When configuring a large set of nodes in EntryNodes, and there are
2333 enough of them listed as Guard so that we don't need to consider
2334 the non-guard entries, prefer the ones listed with the Guard flag.
2335 - Check for and recover from inconsistency in the microdescriptor
2336 cache. This will make it harder for us to accidentally free a
2337 microdescriptor without removing it from the appropriate data
2338 structures. Fixes issue 3135; issue noted by "wanoskarnet".
2339 - Log SSL state transitions at log level DEBUG, log domain
2340 HANDSHAKE. This can be useful for debugging censorship events.
2341 Implements ticket 3264.
2342 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
2343 implements ticket 3439.
2345 o Minor bugfixes (on 0.2.3.1-alpha):
2346 - Do not free all general-purpose regular descriptors just
2347 because microdescriptor use is enabled. Fixes bug 3113.
2348 - Correctly link libevent_openssl when --enable-static-libevent
2349 is passed to configure. Fixes bug 3118.
2350 - Bridges should not complain during their heartbeat log messages that
2351 they are unlisted in the consensus: that's more or less the point
2352 of being a bridge. Fixes bug 3183.
2353 - Report a SIGNAL event to controllers when acting on a delayed
2354 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
2355 event to the controller if we acted on a SIGNAL NEWNYM command
2356 immediately, and otherwise not report a SIGNAL event for the
2357 command at all. Fixes bug 3349.
2358 - Fix a crash when handling the SIGNAL controller command or
2359 reporting ERR-level status events with bufferevents enabled. Found
2360 by Robert Ransom. Fixes bug 3367.
2361 - Always ship the tor-fw-helper manpage in our release tarballs.
2362 Fixes bug 3389. Reported by Stephen Walker.
2363 - Fix a class of double-mark-for-close bugs when bufferevents
2364 are enabled. Fixes bug 3403.
2365 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
2366 - Add SIGNAL to the list returned by the 'GETINFO events/names'
2367 control-port command. Fixes part of bug 3465.
2368 - Prevent using negative indices during unit test runs when read_all()
2369 fails. Spotted by coverity.
2370 - Fix a rare memory leak when checking the nodelist without it being
2371 present. Found by coverity.
2372 - Only try to download a microdescriptor-flavored consensus from
2373 a directory cache that provides them.
2375 o Minor bugfixes (on 0.2.2.x and earlier):
2376 - Assert that hidden-service-related operations are not performed
2377 using single-hop circuits. Previously, Tor would assert that
2378 client-side streams are not attached to single-hop circuits,
2379 but not that other sensitive operations on the client and service
2380 side are not performed using single-hop circuits. Fixes bug 3332;
2382 - Don't publish a new relay descriptor when we reload our onion key,
2383 unless the onion key has actually changed. Fixes bug 3263 and
2384 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
2385 - Allow GETINFO fingerprint to return a fingerprint even when
2386 we have not yet built a router descriptor. Fixes bug 3577;
2387 bugfix on 0.2.0.1-alpha.
2388 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
2389 on 0.2.2.4-alpha; fixes bug 3427.
2391 o Code simplification and refactoring:
2392 - Use tor_sscanf() in place of scanf() in more places through the
2393 code. This makes us a little more locale-independent, and
2394 should help shut up code-analysis tools that can't tell
2395 a safe sscanf string from a dangerous one.
2396 - Use tt_assert(), not tor_assert(), for checking for test failures.
2397 This makes the unit tests more able to go on in the event that
2399 - Split connection_about_to_close() into separate functions for each
2403 - On Windows, we now define the _WIN32_WINNT macros only if they
2404 are not already defined. This lets the person building Tor decide,
2405 if they want, to require a later version of Windows.
2408 Changes in version 0.2.2.30-rc - 2011-07-07
2409 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
2410 series. It fixes a few smaller bugs, but generally appears stable.
2411 Please test it and let us know whether it is!
2414 - Send a SUCCEEDED stream event to the controller when a reverse
2415 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
2416 discovered by katmagic.
2417 - Always NUL-terminate the sun_path field of a sockaddr_un before
2418 passing it to the kernel. (Not a security issue: kernels are
2419 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2420 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2421 - Don't stack-allocate the list of supplementary GIDs when we're
2422 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2423 could take up to 256K, which is way too much stack. Found by
2424 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2425 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
2426 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
2427 fixes part of bug 3465.
2428 - Fix a memory leak when receiving a descriptor for a hidden
2429 service we didn't ask for. Found by Coverity; CID #30. Bugfix
2433 - Update to the July 1 2011 Maxmind GeoLite Country database.
2436 Changes in version 0.2.2.29-beta - 2011-06-20
2437 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
2438 have bridge lines in their torrc but don't want to use them; gets
2439 us closer to having the control socket feature working on Debian;
2440 and fixes a variety of smaller bugs.
2443 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
2444 When we changed the default behavior to "use bridges if any
2445 are listed in the torrc", we surprised users who had bridges
2446 in their torrc files but who didn't actually want to use them.
2447 Partial resolution for bug 3354.
2450 - Don't attach new streams to old rendezvous circuits after SIGNAL
2451 NEWNYM. Previously, we would keep using an existing rendezvous
2452 circuit if it remained open (i.e. if it were kept open by a
2453 long-lived stream, or if a new stream were attached to it before
2454 Tor could notice that it was old and no longer in use). Bugfix on
2455 0.1.1.15-rc; fixes bug 3375.
2458 - Fix a bug when using ControlSocketsGroupWritable with User. The
2459 directory's group would be checked against the current group, not
2460 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
2461 bugfix on 0.2.2.26-beta.
2462 - Make connection_printf_to_buf()'s behaviour sane. Its callers
2463 expect it to emit a CRLF iff the format string ends with CRLF;
2464 it actually emitted a CRLF iff (a) the format string ended with
2465 CRLF or (b) the resulting string was over 1023 characters long or
2466 (c) the format string did not end with CRLF *and* the resulting
2467 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
2468 fixes part of bug 3407.
2469 - Make send_control_event_impl()'s behaviour sane. Its callers
2470 expect it to always emit a CRLF at the end of the string; it
2471 might have emitted extra control characters as well. Bugfix on
2472 0.1.1.9-alpha; fixes another part of bug 3407.
2473 - Make crypto_rand_int() check the value of its input correctly.
2474 Previously, it accepted values up to UINT_MAX, but could return a
2475 negative number if given a value above INT_MAX+1. Found by George
2476 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
2477 - Avoid a segfault when reading a malformed circuit build state
2478 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
2480 - When asked about a DNS record type we don't support via a
2481 client DNSPort, reply with NOTIMPL rather than an empty
2482 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
2483 - Fix a rare memory leak during stats writing. Found by coverity.
2486 - Update to the June 1 2011 Maxmind GeoLite Country database.
2488 o Code simplifications and refactoring:
2489 - Remove some dead code as indicated by coverity.
2490 - Remove a few dead assignments during router parsing. Found by
2492 - Add some forgotten return value checks during unit tests. Found
2494 - Don't use 1-bit wide signed bit fields. Found by coverity.
2497 Changes in version 0.2.2.28-beta - 2011-06-04
2498 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
2499 fixed a big bug in whether relays stay in the consensus consistently,
2500 we moved closer to handling bridges and hidden services correctly,
2501 and we started the process of better handling the dreaded "my Vidalia
2502 died, and now my Tor demands a password when I try to reconnect to it"
2506 - Don't decide to make a new descriptor when receiving a HUP signal.
2507 This bug has caused a lot of 0.2.2.x relays to disappear from the
2508 consensus periodically. Fixes the most common case of triggering
2509 bug 1810; bugfix on 0.2.2.7-alpha.
2510 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
2511 - Don't try to build descriptors if "ORPort auto" is set and we
2512 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
2514 - Resolve a crash that occurred when setting BridgeRelay to 1 with
2515 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
2516 - Apply circuit timeouts to opened hidden-service-related circuits
2517 based on the correct start time. Previously, we would apply the
2518 circuit build timeout based on time since the circuit's creation;
2519 it was supposed to be applied based on time since the circuit
2520 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
2521 - Use the same circuit timeout for client-side introduction
2522 circuits as for other four-hop circuits, rather than the timeout
2523 for single-hop directory-fetch circuits; the shorter timeout may
2524 have been appropriate with the static circuit build timeout in
2525 0.2.1.x and earlier, but caused many hidden service access attempts
2526 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
2527 on 0.2.2.2-alpha; fixes another part of bug 1297.
2528 - In ticket 2511 we fixed a case where you could use an unconfigured
2529 bridge if you had configured it as a bridge the last time you ran
2530 Tor. Now fix another edge case: if you had configured it as a bridge
2531 but then switched to a different bridge via the controller, you
2532 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
2536 - Add an __OwningControllerProcess configuration option and a
2537 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
2538 that when it exits, Tor will shut down. Implements feature 3049.
2539 - If "UseBridges 1" is set and no bridges are configured, Tor will
2540 now refuse to build any circuits until some bridges are set.
2541 If "UseBridges auto" is set, Tor will use bridges if they are
2542 configured and we are not running as a server, but otherwise will
2543 make circuits as usual. The new default is "auto". Patch by anonym,
2544 so the Tails LiveCD can stop automatically revealing you as a Tor
2548 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2549 - Remove a trailing asterisk from "exit-policy/default" in the
2550 output of the control port command "GETINFO info/names". Bugfix
2552 - Use a wide type to hold sockets when built for 64-bit Windows builds.
2554 - Warn when the user configures two HiddenServiceDir lines that point
2555 to the same directory. Bugfix on 0.0.6 (the version introducing
2556 HiddenServiceDir); fixes bug 3289.
2557 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
2558 part of bug 2748; bugfix on 0.2.0.10-alpha.
2559 - Log malformed requests for rendezvous descriptors as protocol
2560 warnings, not warnings. Also, use a more informative log message
2561 in case someone sees it at log level warning without prior
2562 info-level messages. Fixes the other part of bug 2748; bugfix
2564 - Clear the table recording the time of the last request for each
2565 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
2566 Previously, we would clear our HS descriptor cache on SIGNAL
2567 NEWNYM, but if we had previously retrieved a descriptor (or tried
2568 to) from every directory responsible for it, we would refuse to
2569 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
2571 - Fix a log message that said "bits" while displaying a value in
2572 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
2574 - When checking for 1024-bit keys, check for 1024 bits, not 128
2575 bytes. This allows Tor to correctly discard keys of length 1017
2576 through 1023. Bugfix on 0.0.9pre5.
2579 - Relays now log the reason for publishing a new relay descriptor,
2580 so we have a better chance of hunting down instances of bug 1810.
2581 Resolves ticket 3252.
2582 - Revise most log messages that refer to nodes by nickname to
2583 instead use the "$key=nickname at address" format. This should be
2584 more useful, especially since nicknames are less and less likely
2585 to be unique. Resolves ticket 3045.
2586 - Log (at info level) when purging pieces of hidden-service-client
2587 state because of SIGNAL NEWNYM.
2590 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2591 anything since 0.2.1.16-rc.
2594 Changes in version 0.2.2.27-beta - 2011-05-18
2595 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
2596 release, and also adds a few more general bugfixes.
2599 - Fix a crash bug when changing bridges in a running Tor process.
2600 Fixes bug 3213; bugfix on 0.2.2.26-beta.
2601 - When the controller configures a new bridge, don't wait 10 to 60
2602 seconds before trying to fetch its descriptor. Bugfix on
2603 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
2606 - Require that onion keys have exponent 65537 in microdescriptors too.
2607 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
2608 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
2609 Changed the limit to 512 characters by removing base64 newlines.
2610 Fixes bug 2752. Fix by Michael Yakubovich.
2611 - When a client starts or stops using bridges, never use a circuit
2612 that was built before the configuration change. This behavior could
2613 put at risk a user who uses bridges to ensure that her traffic
2614 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
2618 Changes in version 0.2.2.26-beta - 2011-05-17
2619 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
2620 also introduces a new "socksport auto" approach that should make it
2621 easier to run multiple Tors on the same system, and does a lot of
2622 cleanup to get us closer to a release candidate.
2624 o Security/privacy fixes:
2625 - Replace all potentially sensitive memory comparison operations
2626 with versions whose runtime does not depend on the data being
2627 compared. This will help resist a class of attacks where an
2628 adversary can use variations in timing information to learn
2629 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2630 implementation by Robert Ransom based partially on code by DJB.)
2631 - When receiving a hidden service descriptor, check that it is for
2632 the hidden service we wanted. Previously, Tor would store any
2633 hidden service descriptors that a directory gave it, whether it
2634 wanted them or not. This wouldn't have let an attacker impersonate
2635 a hidden service, but it did let directories pre-seed a client
2636 with descriptors that it didn't want. Bugfix on 0.0.6.
2637 - On SIGHUP, do not clear out all TrackHostExits mappings, client
2638 DNS cache entries, and virtual address mappings: that's what
2639 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
2642 - The options SocksPort, ControlPort, and so on now all accept a
2643 value "auto" that opens a socket on an OS-selected port. A
2644 new ControlPortWriteToFile option tells Tor to write its
2645 actual control port or ports to a chosen file. If the option
2646 ControlPortFileGroupReadable is set, the file is created as
2647 group-readable. Now users can run two Tor clients on the same
2648 system without needing to manually mess with parameters. Resolves
2649 part of ticket 3076.
2650 - Set SO_REUSEADDR on all sockets, not just listeners. This should
2651 help busy exit nodes avoid running out of useable ports just
2652 because all the ports have been used in the near past. Resolves
2656 - New "GETINFO net/listeners/(type)" controller command to return
2657 a list of addresses and ports that are bound for listeners for a
2658 given connection type. This is useful when the user has configured
2659 "SocksPort auto" and the controller needs to know which port got
2660 chosen. Resolves another part of ticket 3076.
2661 - Add a new ControlSocketsGroupWritable configuration option: when
2662 it is turned on, ControlSockets are group-writeable by the default
2663 group of the current user. Patch by Jérémy Bobbio; implements
2665 - Tor now refuses to create a ControlSocket in a directory that is
2666 world-readable (or group-readable if ControlSocketsGroupWritable
2667 is 0). This is necessary because some operating systems do not
2668 enforce permissions on an AF_UNIX sockets. Permissions on the
2669 directory holding the socket, however, seems to work everywhere.
2670 - Rate-limit a warning about failures to download v2 networkstatus
2671 documents. Resolves part of bug 1352.
2672 - Backport code from 0.2.3.x that allows directory authorities to
2673 clean their microdescriptor caches. Needed to resolve bug 2230.
2674 - When an HTTPS proxy reports "403 Forbidden", we now explain
2675 what it means rather than calling it an unexpected status code.
2676 Closes bug 2503. Patch from Michael Yakubovich.
2677 - Update to the May 1 2011 Maxmind GeoLite Country database.
2680 - Authorities now clean their microdesc cache periodically and when
2681 reading from disk initially, not only when adding new descriptors.
2682 This prevents a bug where we could lose microdescriptors. Bugfix
2683 on 0.2.2.6-alpha. Fixes bug 2230.
2684 - Do not crash when our configuration file becomes unreadable, for
2685 example due to a permissions change, between when we start up
2686 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2688 - Avoid a bug that would keep us from replacing a microdescriptor
2689 cache on Windows. (We would try to replace the file while still
2690 holding it open. That's fine on Unix, but Windows doesn't let us
2691 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
2692 - Add missing explanations for the authority-related torrc options
2693 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
2694 man page. Resolves issue 2379.
2695 - As an authority, do not upload our own vote or signature set to
2696 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
2697 it would get flagged as a duplicate. Resolves bug 3026.
2698 - Accept hidden service descriptors if we think we might be a hidden
2699 service directory, regardless of what our consensus says. This
2700 helps robustness, since clients and hidden services can sometimes
2701 have a more up-to-date view of the network consensus than we do,
2702 and if they think that the directory authorities list us a HSDir,
2703 we might actually be one. Related to bug 2732; bugfix on
2705 - When a controller changes TrackHostExits, remove mappings for
2706 hosts that should no longer have their exits tracked. Bugfix on
2708 - When a controller changes VirtualAddrNetwork, remove any mappings
2709 for hosts that were automapped to the old network. Bugfix on
2711 - When a controller changes one of the AutomapHosts* options, remove
2712 any mappings for hosts that should no longer be automapped. Bugfix
2714 - Do not reset the bridge descriptor download status every time we
2715 re-parse our configuration or get a configuration change. Fixes
2716 bug 3019; bugfix on 0.2.0.3-alpha.
2718 o Minor bugfixes (code cleanup):
2719 - When loading the microdesc journal, remember its current size.
2720 In 0.2.2, this helps prevent the microdesc journal from growing
2721 without limit on authorities (who are the only ones to use it in
2722 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
2723 Fix posted by "cypherpunks."
2724 - The microdesc journal is supposed to get rebuilt only if it is
2725 at least _half_ the length of the store, not _twice_ the length
2726 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
2727 - Fix a potential null-pointer dereference while computing a
2728 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
2730 - Avoid a possible null-pointer dereference when rebuilding the mdesc
2731 cache without actually having any descriptors to cache. Bugfix on
2732 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
2733 - If we fail to compute the identity digest of a v3 legacy keypair,
2734 warn, and don't use a buffer-full of junk instead. Bugfix on
2735 0.2.1.1-alpha; fixes bug 3106.
2736 - Resolve an untriggerable issue in smartlist_string_num_isin(),
2737 where if the function had ever in the future been used to check
2738 for the presence of a too-large number, it would have given an
2739 incorrect result. (Fortunately, we only used it for 16-bit
2740 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
2741 - Require that introduction point keys and onion handshake keys
2742 have a public exponent of 65537. Starts to fix bug 3207; bugfix
2746 - Caches no longer download and serve v2 networkstatus documents
2747 unless FetchV2Networkstatus flag is set: these documents haven't
2748 haven't been used by clients or relays since 0.2.0.x. Resolves
2752 Changes in version 0.2.3.1-alpha - 2011-05-05
2753 Tor 0.2.3.1-alpha adds some new experimental features, including support
2754 for an improved network IO backend, IOCP networking on Windows,
2755 microdescriptor caching, "fast-start" support for streams, and automatic
2756 home router configuration. There are also numerous internal improvements
2757 to try to make the code easier for developers to work with.
2759 This is the first alpha release in a new series, so expect there to be
2760 bugs. Users who would rather test out a more stable branch should
2761 stay with 0.2.2.x for now.
2764 - Tor can now optionally build with the "bufferevents" buffered IO
2765 backend provided by Libevent 2. To use this feature, make sure you
2766 have the latest possible version of Libevent, and pass the
2767 --enable-bufferevents flag to configure when building Tor from
2768 source. This feature will make our networking code more flexible,
2769 let us stack layers on each other, and let us use more efficient
2770 zero-copy transports where available.
2771 - As an experimental feature, Tor can use IOCP for networking on Windows.
2772 Once this code is tuned and optimized, it promises much better
2773 performance than the select-based backend we've used in the past. To
2774 try this feature, you must build Tor with Libevent 2, configure Tor
2775 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
2776 your torrc. There are known bugs here: only try this if you can help
2777 debug it as it breaks.
2778 - The EntryNodes option can now include country codes like {de} or IP
2779 addresses or network masks. Previously we had disallowed these options
2780 because we didn't have an efficient way to keep the list up to
2781 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
2782 - Exit nodes now accept and queue data on not-yet-connected streams.
2783 Previously, the client wasn't allowed to send data until the stream was
2784 connected, which slowed down all connections. This change will enable
2785 clients to perform a "fast-start" on streams and send data without
2786 having to wait for a confirmation that the stream has opened. (Patch
2787 from Ian Goldberg; implements the server side of Proposal 174.)
2788 - Tor now has initial support for automatic port mapping on the many
2789 home routers that support NAT-PMP or UPnP. (Not yet supported on
2790 Windows). To build the support code, you'll need to have libnatpnp
2791 library and/or the libminiupnpc library, and you'll need to enable the
2792 feature specifically by passing "--enable-upnp" and/or
2793 "--enable-natpnp" to configure. To turn it on, use the new
2794 PortForwarding option.
2795 - Caches now download, cache, and serve multiple "flavors" of the
2796 consensus, including a flavor that describes microdescriptors.
2797 - Caches now download, cache, and serve microdescriptors -- small
2798 summaries of router descriptors that are authenticated by all of the
2799 directory authorities. Once enough caches are running this code,
2800 clients will be able to save significant amounts of directory bandwidth
2801 by downloading microdescriptors instead of router descriptors.
2804 - Make logging resolution configurable with a new LogTimeGranularity
2805 option, and change the default from 1 millisecond to 1 second.
2806 Implements enhancement 1668.
2807 - We log which torrc file we're using on startup. Implements ticket
2809 - Ordinarily, Tor does not count traffic from private addresses (like
2810 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
2811 There is now a new option, CountPrivateBandwidth, to disable this
2812 behavior. Patch from Daniel Cagara.
2813 - New --enable-static-tor configure option for building Tor as
2814 statically as possible. Idea, general hackery and thoughts from
2815 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
2817 - If you set the NumCPUs option to 0, Tor will now try to detect how
2818 many CPUs you have. This is the new default behavior.
2819 - Turn on directory request statistics by default and include them in
2820 extra-info descriptors. Don't break if we have no GeoIP database.
2821 - Relays that set "ConnDirectionStatistics 1" write statistics on the
2822 bidirectional use of connections to disk every 24 hours.
2823 - Add a GeoIP file digest to the extra-info descriptor. Implements
2825 - The NodeFamily option -- which let you declare that you want to
2826 consider nodes to be part of a family whether they list themselves
2827 that way or not -- now allows IP address ranges and country codes.
2828 - Add a new 'Heartbeat' log message type to periodically log a message
2829 describing Tor's status at level Notice. This feature is meant for
2830 operators who log at notice, and want to make sure that their Tor
2831 server is still working. Implementation by George Kadianakis.
2833 o Minor bugfixes (on 0.2.2.25-alpha):
2834 - When loading the microdesc journal, remember its current size.
2835 In 0.2.2, this helps prevent the microdesc journal from growing
2836 without limit on authorities (who are the only ones to use it in
2837 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
2838 Fix posted by "cypherpunks."
2839 - The microdesc journal is supposed to get rebuilt only if it is
2840 at least _half_ the length of the store, not _twice_ the length
2841 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
2842 - If as an authority we fail to compute the identity digest of a v3
2843 legacy keypair, warn, and don't use a buffer-full of junk instead.
2844 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
2845 - Authorities now clean their microdesc cache periodically and when
2846 reading from disk initially, not only when adding new descriptors.
2847 This prevents a bug where we could lose microdescriptors. Bugfix
2850 o Minor features (controller):
2851 - Add a new SIGNAL event to the controller interface so that
2852 controllers can be notified when Tor handles a signal. Resolves
2853 issue 1955. Patch by John Brooks.
2854 - Add a new GETINFO option to get total bytes read and written. Patch
2855 from pipe, revised by atagar. Resolves ticket 2345.
2856 - Implement some GETINFO controller fields to provide information about
2857 the Tor process's pid, euid, username, and resource limits.
2860 - Our build system requires automake 1.6 or later to create the
2861 Makefile.in files. Previously, you could have used 1.4.
2862 This only affects developers and people building Tor from git;
2863 people who build Tor from the source distribution without changing
2864 the Makefile.am files should be fine.
2865 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
2866 so on. This is more robust against some of the failure modes
2867 associated with running the autotools pieces on their own.
2869 o Minor packaging issues:
2870 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
2871 already created. Patch from Andreas Stieger. Fixes bug 2573.
2873 o Code simplifications and refactoring:
2874 - A major revision to our internal node-selecting and listing logic.
2875 Tor already had at least two major ways to look at the question of
2876 "which Tor servers do we know about": a list of router descriptors,
2877 and a list of entries in the current consensus. With
2878 microdescriptors, we're adding a third. Having so many systems
2879 without an abstraction layer over them was hurting the codebase.
2880 Now, we have a new "node_t" abstraction that presents a consistent
2881 interface to a client's view of a Tor node, and holds (nearly) all
2882 of the mutable state formerly in routerinfo_t and routerstatus_t.
2883 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
2884 no longer link against Libevent: they never used it, but
2885 our library structure used to force them to link it.
2888 - Remove some old code to work around even older versions of Tor that
2889 used forked processes to handle DNS requests. Such versions of Tor
2890 are no longer in use as servers.
2892 o Documentation fixes:
2893 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
2894 - Add missing documentation for the authority-related torrc options
2895 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
2899 Changes in version 0.2.2.25-alpha - 2011-04-29
2900 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
2901 robust, routers no longer overreport their bandwidth, Win7 should crash
2902 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
2903 now prevents hidden service-related activity from being linkable. It
2904 provides more information to Vidalia so you can see if your bridge is
2905 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
2906 StrictNodes configuration options to make them more reliable, more
2907 understandable, and more regularly applied. If you use those options,
2908 please see the revised documentation for them in the manual page.
2911 - Relays were publishing grossly inflated bandwidth values because
2912 they were writing their state files wrong--now they write the
2913 correct value. Also, resume reading bandwidth history from the
2914 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
2915 - Improve hidden service robustness: When we find that we have
2916 extended a hidden service's introduction circuit to a relay not
2917 listed as an introduction point in the HS descriptor we currently
2918 have, retry with an introduction point from the current
2919 descriptor. Previously we would just give up. Fixes bugs 1024 and
2920 1930; bugfix on 0.2.0.10-alpha.
2921 - Clients now stop trying to use an exit node associated with a given
2922 destination by TrackHostExits if they fail to reach that exit node.
2923 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
2924 - Fix crash bug on platforms where gmtime and localtime can return
2925 NULL. Windows 7 users were running into this one. Fixes part of bug
2926 2077. Bugfix on all versions of Tor. Found by boboper.
2928 o Security and stability fixes:
2929 - Don't double-free a parsable, but invalid, microdescriptor, even if
2930 it is followed in the blob we're parsing by an unparsable
2931 microdescriptor. Fixes an issue reported in a comment on bug 2954.
2932 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
2933 - If the Nickname configuration option isn't given, Tor would pick a
2934 nickname based on the local hostname as the nickname for a relay.
2935 Because nicknames are not very important in today's Tor and the
2936 "Unnamed" nickname has been implemented, this is now problematic
2937 behavior: It leaks information about the hostname without being
2938 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
2939 introduced the Unnamed nickname. Reported by tagnaq.
2940 - Fix an uncommon assertion failure when running with DNSPort under
2941 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
2942 - Avoid linkability based on cached hidden service descriptors: forget
2943 all hidden service descriptors cached as a client when processing a
2944 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
2947 - Export GeoIP information on bridge usage to controllers even if we
2948 have not yet been running for 24 hours. Now Vidalia bridge operators
2949 can get more accurate and immediate feedback about their
2950 contributions to the network.
2952 o Major features and bugfixes (node selection):
2953 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
2954 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
2955 options. Previously, we had been ambiguous in describing what
2956 counted as an "exit" node, and what operations exactly "StrictNodes
2957 0" would permit. This created confusion when people saw nodes built
2958 through unexpected circuits, and made it hard to tell real bugs from
2959 surprises. Now the intended behavior is:
2960 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
2961 a node that delivers user traffic outside the Tor network.
2962 . "Entry", in the context of EntryNodes, means a node used as the
2963 first hop of a multihop circuit. It doesn't include direct
2964 connections to directory servers.
2965 . "ExcludeNodes" applies to all nodes.
2966 . "StrictNodes" changes the behavior of ExcludeNodes only. When
2967 StrictNodes is set, Tor should avoid all nodes listed in
2968 ExcludeNodes, even when it will make user requests fail. When
2969 StrictNodes is *not* set, then Tor should follow ExcludeNodes
2970 whenever it can, except when it must use an excluded node to
2971 perform self-tests, connect to a hidden service, provide a
2972 hidden service, fulfill a .exit request, upload directory
2973 information, or fetch directory information.
2974 Collectively, the changes to implement the behavior fix bug 1090.
2975 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
2976 a node is listed in both, it's treated as excluded.
2977 - ExcludeNodes now applies to directory nodes -- as a preference if
2978 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
2979 Don't exclude all the directory authorities and set StrictNodes to 1
2980 unless you really want your Tor to break.
2981 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
2982 - ExcludeExitNodes now overrides .exit requests.
2983 - We don't use bridges listed in ExcludeNodes.
2984 - When StrictNodes is 1:
2985 . We now apply ExcludeNodes to hidden service introduction points
2986 and to rendezvous points selected by hidden service users. This
2987 can make your hidden service less reliable: use it with caution!
2988 . If we have used ExcludeNodes on ourself, do not try relay
2989 reachability self-tests.
2990 . If we have excluded all the directory authorities, we will not
2991 even try to upload our descriptor if we're a relay.
2992 . Do not honor .exit requests to an excluded node.
2993 - Remove a misfeature that caused us to ignore the Fast/Stable flags
2994 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
2995 - When the set of permitted nodes changes, we now remove any mappings
2996 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
2998 - We never cannibalize a circuit that had excluded nodes on it, even
2999 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
3000 - Revert a change where we would be laxer about attaching streams to
3001 circuits than when building the circuits. This was meant to prevent
3002 a set of bugs where streams were never attachable, but our improved
3003 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
3004 - Keep track of how many times we launch a new circuit to handle a
3005 given stream. Too many launches could indicate an inconsistency
3006 between our "launch a circuit to handle this stream" logic and our
3007 "attach this stream to one of the available circuits" logic.
3008 - Improve log messages related to excluded nodes.
3011 - Fix a spurious warning when moving from a short month to a long
3012 month on relays with month-based BandwidthAccounting. Bugfix on
3013 0.2.2.17-alpha; fixes bug 3020.
3014 - When a client finds that an origin circuit has run out of 16-bit
3015 stream IDs, we now mark it as unusable for new streams. Previously,
3016 we would try to close the entire circuit. Bugfix on 0.0.6.
3017 - Add a forgotten cast that caused a compile warning on OS X 10.6.
3018 Bugfix on 0.2.2.24-alpha.
3019 - Be more careful about reporting the correct error from a failed
3020 connect() system call. Under some circumstances, it was possible to
3021 look at an incorrect value for errno when sending the end reason.
3022 Bugfix on 0.1.0.1-rc.
3023 - Correctly handle an "impossible" overflow cases in connection byte
3024 counting, where we write or read more than 4GB on an edge connection
3025 in a single second. Bugfix on 0.1.2.8-beta.
3026 - Correct the warning displayed when a rendezvous descriptor exceeds
3027 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3029 - Clients and hidden services now use HSDir-flagged relays for hidden
3030 service descriptor downloads and uploads even if the relays have no
3031 DirPort set and the client has disabled TunnelDirConns. This will
3032 eventually allow us to give the HSDir flag to relays with no
3033 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
3034 - Downgrade "no current certificates known for authority" message from
3035 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
3036 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
3037 2917. Bugfix on 0.1.1.1-alpha.
3038 - Only limit the lengths of single HS descriptors, even when multiple
3039 HS descriptors are published to an HSDir relay in a single POST
3040 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
3041 - Write the current time into the LastWritten line in our state file,
3042 rather than the time from the previous write attempt. Also, stop
3043 trying to use a time of -1 in our log statements. Fixes bug 3039;
3044 bugfix on 0.2.2.14-alpha.
3045 - Be more consistent in our treatment of file system paths. "~" should
3046 get expanded to the user's home directory in the Log config option.
3047 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
3048 feature for the -f and --DataDirectory options.
3051 - Make sure every relay writes a state file at least every 12 hours.
3052 Previously, a relay could go for weeks without writing its state
3053 file, and on a crash could lose its bandwidth history, capacity
3054 estimates, client country statistics, and so on. Addresses bug 3012.
3055 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
3056 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
3057 clients are already deprecated because of security bugs.
3058 - Don't allow v0 hidden service authorities to act as clients.
3059 Required by fix for bug 3000.
3060 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
3061 by fix for bug 3000.
3062 - Ensure that no empty [dirreq-](read|write)-history lines are added
3063 to an extrainfo document. Implements ticket 2497.
3065 o Code simplification and refactoring:
3066 - Remove workaround code to handle directory responses from servers
3067 that had bug 539 (they would send HTTP status 503 responses _and_
3068 send a body too). Since only server versions before
3069 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
3070 keep the workaround in place.
3071 - Remove the old 'fuzzy time' logic. It was supposed to be used for
3072 handling calculations where we have a known amount of clock skew and
3073 an allowed amount of unknown skew. But we only used it in three
3074 places, and we never adjusted the known/unknown skew values. This is
3075 still something we might want to do someday, but if we do, we'll
3076 want to do it differently.
3077 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3078 None of the cases where we did this before were wrong, but by making
3079 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3080 - Use GetTempDir to find the proper temporary directory location on
3081 Windows when generating temporary files for the unit tests. Patch by
3085 Changes in version 0.2.2.24-alpha - 2011-04-08
3086 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
3087 prevented Tor clients from effectively using "multihomed" bridges,
3088 that is, bridges that listen on multiple ports or IP addresses so users
3089 can continue to use some of their addresses even if others get blocked.
3092 - Fix a bug where bridge users who configure the non-canonical
3093 address of a bridge automatically switch to its canonical
3094 address. If a bridge listens at more than one address, it should be
3095 able to advertise those addresses independently and any non-blocked
3096 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
3098 - If you configured Tor to use bridge A, and then quit and
3099 configured Tor to use bridge B instead, it would happily continue
3100 to use bridge A if it's still reachable. While this behavior is
3101 a feature if your goal is connectivity, in some scenarios it's a
3102 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
3103 - Directory authorities now use data collected from their own
3104 uptime observations when choosing whether to assign the HSDir flag
3105 to relays, instead of trusting the uptime value the relay reports in
3106 its descriptor. This change helps prevent an attack where a small
3107 set of nodes with frequently-changing identity keys can blackhole
3108 a hidden service. (Only authorities need upgrade; others will be
3109 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
3112 - When we restart our relay, we might get a successful connection
3113 from the outside before we've started our reachability tests,
3114 triggering a warning: "ORPort found reachable, but I have no
3115 routerinfo yet. Failing to inform controller of success." This
3116 bug was harmless unless Tor is running under a controller
3117 like Vidalia, in which case the controller would never get a
3118 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3120 - Make directory authorities more accurate at recording when
3121 relays that have failed several reachability tests became
3122 unreachable, so we can provide more accuracy at assigning Stable,
3123 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
3124 - Fix an issue that prevented static linking of libevent on
3125 some platforms (notably Linux). Fixes bug 2698; bugfix on
3126 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
3127 the --with-static-libevent configure option).
3128 - We now ask the other side of a stream (the client or the exit)
3129 for more data on that stream when the amount of queued data on
3130 that stream dips low enough. Previously, we wouldn't ask the
3131 other side for more data until either it sent us more data (which
3132 it wasn't supposed to do if it had exhausted its window!) or we
3133 had completely flushed all our queued data. This flow control fix
3134 should improve throughput. Fixes bug 2756; bugfix on the earliest
3135 released versions of Tor (svn commit r152).
3136 - Avoid a double-mark-for-free warning when failing to attach a
3137 transparent proxy connection. (We thought we had fixed this in
3138 0.2.2.23-alpha, but it turns out our fix was checking the wrong
3139 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
3140 bug) and 0.2.2.23-alpha (the incorrect fix).
3141 - When warning about missing zlib development packages during compile,
3142 give the correct package names. Bugfix on 0.2.0.1-alpha.
3145 - Directory authorities now log the source of a rejected POSTed v3
3147 - Make compilation with clang possible when using
3148 --enable-gcc-warnings by removing two warning options that clang
3149 hasn't implemented yet and by fixing a few warnings. Implements
3151 - When expiring circuits, use microsecond timers rather than
3152 one-second timers. This can avoid an unpleasant situation where a
3153 circuit is launched near the end of one second and expired right
3154 near the beginning of the next, and prevent fluctuations in circuit
3156 - Use computed circuit-build timeouts to decide when to launch
3157 parallel introduction circuits for hidden services. (Previously,
3158 we would retry after 15 seconds.)
3159 - Update to the April 1 2011 Maxmind GeoLite Country database.
3162 - Create the /var/run/tor directory on startup on OpenSUSE if it is
3163 not already created. Patch from Andreas Stieger. Fixes bug 2573.
3165 o Documentation changes:
3166 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
3167 - Resolve all doxygen warnings except those for missing documentation.
3169 - Add doxygen documentation for more functions, fields, and types.
3172 Changes in version 0.2.2.23-alpha - 2011-03-08
3173 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
3174 they restart they don't lose their bandwidth capacity estimate. This
3175 release also fixes a diverse set of user-facing bugs, ranging from
3176 relays overrunning their rate limiting to clients falsely warning about
3177 clock skew to bridge descriptor leaks by our bridge directory authority.
3180 - Stop sending a CLOCK_SKEW controller status event whenever
3181 we fetch directory information from a relay that has a wrong clock.
3182 Instead, only inform the controller when it's a trusted authority
3183 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3184 the rest of bug 1074.
3185 - Fix an assert in parsing router descriptors containing IPv6
3186 addresses. This one took down the directory authorities when
3187 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3188 - Make the bridge directory authority refuse to answer directory
3189 requests for "all" descriptors. It used to include bridge
3190 descriptors in its answer, which was a major information leak.
3191 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3192 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3193 Tor would ignore their RelayBandwidthBurst setting,
3194 potentially using more bandwidth than expected. Bugfix on
3195 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3196 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3197 hidserv" in her torrc. The 'hidserv' argument never controlled
3198 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3201 - Relays now save observed peak bandwidth throughput rates to their
3202 state file (along with total usage, which was already saved)
3203 so that they can determine their correct estimated bandwidth on
3204 restart. Resolves bug 1863, where Tor relays would reset their
3205 estimated bandwidth to 0 after restarting.
3206 - Directory authorities now take changes in router IP address and
3207 ORPort into account when determining router stability. Previously,
3208 if a router changed its IP or ORPort, the authorities would not
3209 treat it as having any downtime for the purposes of stability
3210 calculation, whereas clients would experience downtime since the
3211 change could take a while to propagate to them. Resolves issue 1035.
3212 - Enable Address Space Layout Randomization (ASLR) and Data Execution
3213 Prevention (DEP) by default on Windows to make it harder for
3214 attackers to exploit vulnerabilities. Patch from John Brooks.
3216 o Minor bugfixes (on 0.2.1.x and earlier):
3217 - Fix a rare crash bug that could occur when a client was configured
3218 with a large number of bridges. Fixes bug 2629; bugfix on
3219 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3220 - Avoid a double mark-for-free warning when failing to attach a
3221 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
3223 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
3224 found by "cypherpunks". This bug was introduced before the first
3225 Tor release, in svn commit r110.
3226 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
3227 don't mention them in the manpage. Fixes bug 2450; issue
3228 spotted by keb and G-Lo.
3229 - Fix a bug in bandwidth history state parsing that could have been
3230 triggered if a future version of Tor ever changed the timing
3231 granularity at which bandwidth history is measured. Bugfix on
3233 - When a relay decides that its DNS is too broken for it to serve
3234 as an exit server, it advertised itself as a non-exit, but
3235 continued to act as an exit. This could create accidental
3236 partitioning opportunities for users. Instead, if a relay is
3237 going to advertise reject *:* as its exit policy, it should
3238 really act with exit policy "reject *:*". Fixes bug 2366.
3239 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
3240 - In the special case where you configure a public exit relay as your
3241 bridge, Tor would be willing to use that exit relay as the last
3242 hop in your circuit as well. Now we fail that circuit instead.
3243 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
3244 - Fix a bug with our locking implementation on Windows that couldn't
3245 correctly detect when a file was already locked. Fixes bug 2504,
3246 bugfix on 0.2.1.6-alpha.
3247 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
3248 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
3250 - Set target port in get_interface_address6() correctly. Bugfix
3251 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
3252 - Directory authorities are now more robust to hops back in time
3253 when calculating router stability. Previously, if a run of uptime
3254 or downtime appeared to be negative, the calculation could give
3255 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
3257 - Fix an assert that got triggered when using the TestingTorNetwork
3258 configuration option and then issuing a GETINFO config-text control
3259 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
3261 o Minor bugfixes (on 0.2.2.x):
3262 - Clients should not weight BadExit nodes as Exits in their node
3263 selection. Similarly, directory authorities should not count BadExit
3264 bandwidth as Exit bandwidth when computing bandwidth-weights.
3265 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
3266 - Correctly clear our dir_read/dir_write history when there is an
3267 error parsing any bw history value from the state file. Bugfix on
3269 - Resolve a bug in verifying signatures of directory objects
3270 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
3271 Fixes bug 2409. Found by "piebeer".
3272 - Bridge authorities no longer crash on SIGHUP when they try to
3273 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
3277 - Log less aggressively about circuit timeout changes, and improve
3278 some other circuit timeout messages. Resolves bug 2004.
3279 - Log a little more clearly about the times at which we're no longer
3280 accepting new connections. Resolves bug 2181.
3281 - Reject attempts at the client side to open connections to private
3282 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
3283 a randomly chosen exit node. Attempts to do so are always
3284 ill-defined, generally prevented by exit policies, and usually
3285 in error. This will also help to detect loops in transparent
3286 proxy configurations. You can disable this feature by setting
3287 "ClientRejectInternalAddresses 0" in your torrc.
3288 - Always treat failure to allocate an RSA key as an unrecoverable
3290 - Update to the March 1 2011 Maxmind GeoLite Country database.
3292 o Minor features (log subsystem):
3293 - Add documentation for configuring logging at different severities in
3294 different log domains. We've had this feature since 0.2.1.1-alpha,
3295 but for some reason it never made it into the manpage. Fixes
3297 - Make it simpler to specify "All log domains except for A and B".
3298 Previously you needed to say "[*,~A,~B]". Now you can just say
3300 - Add a "LogMessageDomains 1" option to include the domains of log
3301 messages along with the messages. Without this, there's no way
3302 to use log domains without reading the source or doing a lot
3305 o Packaging changes:
3306 - Stop shipping the Tor specs files and development proposal documents
3307 in the tarball. They are now in a separate git repository at
3308 git://git.torproject.org/torspec.git
3311 Changes in version 0.2.1.30 - 2011-02-23
3312 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
3313 change is a slight tweak to Tor's TLS handshake that makes relays
3314 and bridges that run this new version reachable from Iran again.
3315 We don't expect this tweak will win the arms race long-term, but it
3316 buys us time until we roll out a better solution.
3319 - Stop sending a CLOCK_SKEW controller status event whenever
3320 we fetch directory information from a relay that has a wrong clock.
3321 Instead, only inform the controller when it's a trusted authority
3322 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3323 the rest of bug 1074.
3324 - Fix a bounds-checking error that could allow an attacker to
3325 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3327 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3328 Tor would ignore their RelayBandwidthBurst setting,
3329 potentially using more bandwidth than expected. Bugfix on
3330 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3331 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3332 hidserv" in her torrc. The 'hidserv' argument never controlled
3333 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3336 - Adjust our TLS Diffie-Hellman parameters to match those used by
3338 - Update to the February 1 2011 Maxmind GeoLite Country database.
3341 - Check for and reject overly long directory certificates and
3342 directory tokens before they have a chance to hit any assertions.
3343 Bugfix on 0.2.1.28. Found by "doorss".
3344 - Bring the logic that gathers routerinfos and assesses the
3345 acceptability of circuits into line. This prevents a Tor OP from
3346 getting locked in a cycle of choosing its local OR as an exit for a
3347 path (due to a .exit request) and then rejecting the circuit because
3348 its OR is not listed yet. It also prevents Tor clients from using an
3349 OR running in the same instance as an exit (due to a .exit request)
3350 if the OR does not meet the same requirements expected of an OR
3351 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
3353 o Packaging changes:
3354 - Stop shipping the Tor specs files and development proposal documents
3355 in the tarball. They are now in a separate git repository at
3356 git://git.torproject.org/torspec.git
3357 - Do not include Git version tags as though they are SVN tags when
3358 generating a tarball from inside a repository that has switched
3359 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3362 Changes in version 0.2.2.22-alpha - 2011-01-25
3363 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
3364 main other change is a slight tweak to Tor's TLS handshake that makes
3365 relays and bridges that run this new version reachable from Iran again.
3366 We don't expect this tweak will win the arms race long-term, but it
3367 will buy us a bit more time until we roll out a better solution.
3370 - Fix a bounds-checking error that could allow an attacker to
3371 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3373 - Don't assert when changing from bridge to relay or vice versa
3374 via the controller. The assert happened because we didn't properly
3375 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
3376 bug 2433. Reported by bastik.
3379 - Adjust our TLS Diffie-Hellman parameters to match those used by
3381 - Provide a log message stating which geoip file we're parsing
3382 instead of just stating that we're parsing the geoip file.
3383 Implements ticket 2432.
3386 - Check for and reject overly long directory certificates and
3387 directory tokens before they have a chance to hit any assertions.
3388 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
3391 Changes in version 0.2.2.21-alpha - 2011-01-15
3392 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
3393 continues our recent code security audit work. The main fix resolves
3394 a remote heap overflow vulnerability that can allow remote code
3395 execution (CVE-2011-0427). Other fixes address a variety of assert
3396 and crash bugs, most of which we think are hard to exploit remotely.
3398 o Major bugfixes (security), also included in 0.2.1.29:
3399 - Fix a heap overflow bug where an adversary could cause heap
3400 corruption. This bug probably allows remote code execution
3401 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3403 - Prevent a denial-of-service attack by disallowing any
3404 zlib-compressed data whose compression factor is implausibly
3405 high. Fixes part of bug 2324; reported by "doorss".
3406 - Zero out a few more keys in memory before freeing them. Fixes
3407 bug 2384 and part of bug 2385. These key instances found by
3408 "cypherpunks", based on Andrew Case's report about being able
3409 to find sensitive data in Tor's memory space if you have enough
3410 permissions. Bugfix on 0.0.2pre9.
3412 o Major bugfixes (crashes), also included in 0.2.1.29:
3413 - Prevent calls to Libevent from inside Libevent log handlers.
3414 This had potential to cause a nasty set of crashes, especially
3415 if running Libevent with debug logging enabled, and running
3416 Tor with a controller watching for low-severity log messages.
3417 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3418 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3419 underflow errors there too. Fixes the other part of bug 2324.
3420 - Fix a bug where we would assert if we ever had a
3421 cached-descriptors.new file (or another file read directly into
3422 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3423 on 0.2.1.25. Found by doorss.
3424 - Fix some potential asserts and parsing issues with grossly
3425 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3428 o Minor bugfixes (other), also included in 0.2.1.29:
3429 - Fix a bug with handling misformed replies to reverse DNS lookup
3430 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3431 bug reported by doorss.
3432 - Fix compilation on mingw when a pthreads compatibility library
3433 has been installed. (We don't want to use it, so we shouldn't
3434 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3435 - Fix a bug where we would declare that we had run out of virtual
3436 addresses when the address space was only half-exhausted. Bugfix
3438 - Correctly handle the case where AutomapHostsOnResolve is set but
3439 no virtual addresses are available. Fixes bug 2328; bugfix on
3440 0.1.2.1-alpha. Bug found by doorss.
3441 - Correctly handle wrapping around when we run out of virtual
3442 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
3444 o Minor features, also included in 0.2.1.29:
3445 - Update to the January 1 2011 Maxmind GeoLite Country database.
3446 - Introduce output size checks on all of our decryption functions.
3448 o Build changes, also included in 0.2.1.29:
3449 - Tor does not build packages correctly with Automake 1.6 and earlier;
3450 added a check to Makefile.am to make sure that we're building with
3451 Automake 1.7 or later.
3452 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
3453 because we built it with a too-old version of automake. Thus that
3454 release broke ./configure --enable-openbsd-malloc, which is popular
3455 among really fast exit relays on Linux.
3457 o Major bugfixes, new in 0.2.2.21-alpha:
3458 - Prevent crash/heap corruption when the cbtnummodes consensus
3459 parameter is set to 0 or large values. Fixes bug 2317; bugfix
3462 o Major features, new in 0.2.2.21-alpha:
3463 - Introduce minimum/maximum values that clients will believe
3464 from the consensus. Now we'll have a better chance to avoid crashes
3465 or worse when a consensus param has a weird value.
3467 o Minor features, new in 0.2.2.21-alpha:
3468 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
3469 used on bridges, and it makes bridge scanning somewhat easier.
3470 - If writing the state file to disk fails, wait up to an hour before
3471 retrying again, rather than trying again each second. Fixes bug
3472 2346; bugfix on Tor 0.1.1.3-alpha.
3473 - Make Libevent log messages get delivered to controllers later,
3474 and not from inside the Libevent log handler. This prevents unsafe
3475 reentrant Libevent calls while still letting the log messages
3477 - Detect platforms that brokenly use a signed size_t, and refuse to
3478 build there. Found and analyzed by doorss and rransom.
3479 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
3482 o Minor bugfixes, new in 0.2.2.21-alpha:
3483 - Handle SOCKS messages longer than 128 bytes long correctly, rather
3484 than waiting forever for them to finish. Fixes bug 2330; bugfix
3485 on 0.2.0.16-alpha. Found by doorss.
3486 - Add assertions to check for overflow in arguments to
3487 base32_encode() and base32_decode(); fix a signed-unsigned
3488 comparison there too. These bugs are not actually reachable in Tor,
3489 but it's good to prevent future errors too. Found by doorss.
3490 - Correctly detect failures to create DNS requests when using Libevent
3491 versions before v2. (Before Libevent 2, we used our own evdns
3492 implementation. Its return values for Libevent's evdns_resolve_*()
3493 functions are not consistent with those from Libevent.) Fixes bug
3494 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
3496 o Documentation, new in 0.2.2.21-alpha:
3497 - Document the default socks host and port (127.0.0.1:9050) for
3501 Changes in version 0.2.1.29 - 2011-01-15
3502 Tor 0.2.1.29 continues our recent code security audit work. The main
3503 fix resolves a remote heap overflow vulnerability that can allow remote
3504 code execution. Other fixes address a variety of assert and crash bugs,
3505 most of which we think are hard to exploit remotely.
3507 o Major bugfixes (security):
3508 - Fix a heap overflow bug where an adversary could cause heap
3509 corruption. This bug probably allows remote code execution
3510 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3512 - Prevent a denial-of-service attack by disallowing any
3513 zlib-compressed data whose compression factor is implausibly
3514 high. Fixes part of bug 2324; reported by "doorss".
3515 - Zero out a few more keys in memory before freeing them. Fixes
3516 bug 2384 and part of bug 2385. These key instances found by
3517 "cypherpunks", based on Andrew Case's report about being able
3518 to find sensitive data in Tor's memory space if you have enough
3519 permissions. Bugfix on 0.0.2pre9.
3521 o Major bugfixes (crashes):
3522 - Prevent calls to Libevent from inside Libevent log handlers.
3523 This had potential to cause a nasty set of crashes, especially
3524 if running Libevent with debug logging enabled, and running
3525 Tor with a controller watching for low-severity log messages.
3526 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3527 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3528 underflow errors there too. Fixes the other part of bug 2324.
3529 - Fix a bug where we would assert if we ever had a
3530 cached-descriptors.new file (or another file read directly into
3531 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3532 on 0.2.1.25. Found by doorss.
3533 - Fix some potential asserts and parsing issues with grossly
3534 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3537 o Minor bugfixes (other):
3538 - Fix a bug with handling misformed replies to reverse DNS lookup
3539 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3540 bug reported by doorss.
3541 - Fix compilation on mingw when a pthreads compatibility library
3542 has been installed. (We don't want to use it, so we shouldn't
3543 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3544 - Fix a bug where we would declare that we had run out of virtual
3545 addresses when the address space was only half-exhausted. Bugfix
3547 - Correctly handle the case where AutomapHostsOnResolve is set but
3548 no virtual addresses are available. Fixes bug 2328; bugfix on
3549 0.1.2.1-alpha. Bug found by doorss.
3550 - Correctly handle wrapping around to when we run out of virtual
3551 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
3552 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
3553 because we built it with a too-old version of automake. Thus that
3554 release broke ./configure --enable-openbsd-malloc, which is popular
3555 among really fast exit relays on Linux.
3558 - Update to the January 1 2011 Maxmind GeoLite Country database.
3559 - Introduce output size checks on all of our decryption functions.
3562 - Tor does not build packages correctly with Automake 1.6 and earlier;
3563 added a check to Makefile.am to make sure that we're building with
3564 Automake 1.7 or later.
3567 Changes in version 0.2.2.20-alpha - 2010-12-17
3568 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
3569 exploitable bugs. We also fix a variety of other significant bugs,
3570 change the IP address for one of our directory authorities, and update
3571 the minimum version that Tor relays must run to join the network.
3574 - Fix a remotely exploitable bug that could be used to crash instances
3575 of Tor remotely by overflowing on the heap. Remote-code execution
3576 hasn't been confirmed, but can't be ruled out. Everyone should
3577 upgrade. Bugfix on the 0.1.1 series and later.
3578 - Fix a bug that could break accounting on 64-bit systems with large
3579 time_t values, making them hibernate for impossibly long intervals.
3580 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
3581 - Fix a logic error in directory_fetches_from_authorities() that
3582 would cause all _non_-exits refusing single-hop-like circuits
3583 to fetch from authorities, when we wanted to have _exits_ fetch
3584 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
3586 - Fix a stream fairness bug that would cause newer streams on a given
3587 circuit to get preference when reading bytes from the origin or
3588 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
3589 introduced before the first Tor release, in svn revision r152.
3591 o Directory authority changes:
3592 - Change IP address and ports for gabelmoo (v3 directory authority).
3595 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
3596 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
3597 - Fix an off-by-one error in calculating some controller command
3598 argument lengths. Fortunately, this mistake is harmless since
3599 the controller code does redundant NUL termination too. Found by
3600 boboper. Bugfix on 0.1.1.1-alpha.
3601 - Do not dereference NULL if a bridge fails to build its
3602 extra-info descriptor. Found by an anonymous commenter on
3603 Trac. Bugfix on 0.2.2.19-alpha.
3606 - Update to the December 1 2010 Maxmind GeoLite Country database.
3607 - Directory authorities now reject relays running any versions of
3608 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
3609 known bugs that keep RELAY_EARLY cells from working on rendezvous
3610 circuits. Followup to fix for bug 2081.
3611 - Directory authorities now reject relays running any version of Tor
3612 older than 0.2.0.26-rc. That version is the earliest that fetches
3613 current directory information correctly. Fixes bug 2156.
3614 - Report only the top 10 ports in exit-port stats in order not to
3615 exceed the maximum extra-info descriptor length of 50 KB. Implements
3619 Changes in version 0.2.1.28 - 2010-12-17
3620 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
3621 exploitable bugs. We also took this opportunity to change the IP address
3622 for one of our directory authorities, and to update the geoip database
3626 - Fix a remotely exploitable bug that could be used to crash instances
3627 of Tor remotely by overflowing on the heap. Remote-code execution
3628 hasn't been confirmed, but can't be ruled out. Everyone should
3629 upgrade. Bugfix on the 0.1.1 series and later.
3631 o Directory authority changes:
3632 - Change IP address and ports for gabelmoo (v3 directory authority).
3635 - Update to the December 1 2010 Maxmind GeoLite Country database.
3638 Changes in version 0.2.1.27 - 2010-11-23
3639 Yet another OpenSSL security patch broke its compatibility with Tor:
3640 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
3641 also took this opportunity to fix several crash bugs, integrate a new
3642 directory authority, and update the bundled GeoIP database.
3645 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
3646 No longer set the tlsext_host_name extension on server SSL objects;
3647 but continue to set it on client SSL objects. Our goal in setting
3648 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
3649 bugfix on 0.2.1.1-alpha.
3650 - Do not log messages to the controller while shrinking buffer
3651 freelists. Doing so would sometimes make the controller connection
3652 try to allocate a buffer chunk, which would mess up the internals
3653 of the freelist and cause an assertion failure. Fixes bug 1125;
3654 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
3655 - Learn our external IP address when we're a relay or bridge, even if
3656 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
3657 where we introduced bridge relays that don't need to publish to
3658 be useful. Fixes bug 2050.
3659 - Do even more to reject (and not just ignore) annotations on
3660 router descriptors received anywhere but from the cache. Previously
3661 we would ignore such annotations at first, but cache them to disk
3662 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
3663 - When you're using bridges and your network goes away and your
3664 bridges get marked as down, recover when you attempt a new socks
3665 connection (if the network is back), rather than waiting up to an
3666 hour to try fetching new descriptors for your bridges. Bugfix on
3667 0.2.0.3-alpha; fixes bug 1981.
3670 - Move to the November 2010 Maxmind GeoLite country db (rather
3671 than the June 2009 ip-to-country GeoIP db) for our statistics that
3672 count how many users relays are seeing from each country. Now we'll
3673 have more accurate data, especially for many African countries.
3675 o New directory authorities:
3676 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
3680 - Fix an assertion failure that could occur in directory caches or
3681 bridge users when using a very short voting interval on a testing
3682 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
3684 - Enforce multiplicity rules when parsing annotations. Bugfix on
3685 0.2.0.8-alpha. Found by piebeer.
3686 - Allow handshaking OR connections to take a full KeepalivePeriod
3687 seconds to handshake. Previously, we would close them after
3688 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
3689 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
3691 - When building with --enable-gcc-warnings on OpenBSD, disable
3692 warnings in system headers. This makes --enable-gcc-warnings
3693 pass on OpenBSD 4.8.
3696 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
3697 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
3698 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
3699 Servers can start sending this code when enough clients recognize
3700 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
3701 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
3702 Patch from mingw-san.
3705 - Remove the old debian/ directory from the main Tor distribution.
3706 The official Tor-for-debian git repository lives at the URL
3707 https://git.torproject.org/debian/tor.git
3708 - Stop shipping the old doc/website/ directory in the tarball. We
3709 changed the website format in late 2010, and what we shipped in
3710 0.2.1.26 really wasn't that useful anyway.
3713 Changes in version 0.2.2.19-alpha - 2010-11-22
3714 Yet another OpenSSL security patch broke its compatibility with Tor:
3715 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
3718 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
3719 No longer set the tlsext_host_name extension on server SSL objects;
3720 but continue to set it on client SSL objects. Our goal in setting
3721 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
3722 bugfix on 0.2.1.1-alpha.
3725 - Try harder not to exceed the maximum length of 50 KB when writing
3726 statistics to extra-info descriptors. This bug was triggered by very
3727 fast relays reporting exit-port, entry, and dirreq statistics.
3728 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
3729 - Publish a router descriptor even if generating an extra-info
3730 descriptor fails. Previously we would not publish a router
3731 descriptor without an extra-info descriptor; this can cause fast
3732 exit relays collecting exit-port statistics to drop from the
3733 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
3736 Changes in version 0.2.2.18-alpha - 2010-11-16
3737 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
3738 us lately, makes unpublished bridge relays able to detect their IP
3739 address, and fixes a wide variety of other bugs to get us much closer
3740 to a stable release.
3743 - Do even more to reject (and not just ignore) annotations on
3744 router descriptors received anywhere but from the cache. Previously
3745 we would ignore such annotations at first, but cache them to disk
3746 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
3747 - Do not log messages to the controller while shrinking buffer
3748 freelists. Doing so would sometimes make the controller connection
3749 try to allocate a buffer chunk, which would mess up the internals
3750 of the freelist and cause an assertion failure. Fixes bug 1125;
3751 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
3752 - Learn our external IP address when we're a relay or bridge, even if
3753 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
3754 where we introduced bridge relays that don't need to publish to
3755 be useful. Fixes bug 2050.
3756 - Maintain separate TLS contexts and certificates for incoming and
3757 outgoing connections in bridge relays. Previously we would use the
3758 same TLS contexts and certs for incoming and outgoing connections.
3759 Bugfix on 0.2.0.3-alpha; addresses bug 988.
3760 - Maintain separate identity keys for incoming and outgoing TLS
3761 contexts in bridge relays. Previously we would use the same
3762 identity keys for incoming and outgoing TLS contexts. Bugfix on
3763 0.2.0.3-alpha; addresses the other half of bug 988.
3764 - Avoid an assertion failure when we as an authority receive a
3765 duplicate upload of a router descriptor that we already have,
3766 but which we previously considered an obsolete descriptor.
3767 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
3768 - Avoid a crash bug triggered by looking at a dangling pointer while
3769 setting the network status consensus. Found by Robert Ransom.
3770 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
3771 - Fix a logic error where servers that _didn't_ act as exits would
3772 try to keep their server lists more aggressively up to date than
3773 exits, when it was supposed to be the other way around. Bugfix
3776 o Minor bugfixes (on Tor 0.2.1.x and earlier):
3777 - When we're trying to guess whether we know our IP address as
3778 a relay, we would log various ways that we failed to guess
3779 our address, but never log that we ended up guessing it
3780 successfully. Now add a log line to help confused and anxious
3781 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
3782 - Bring the logic that gathers routerinfos and assesses the
3783 acceptability of circuits into line. This prevents a Tor OP from
3784 getting locked in a cycle of choosing its local OR as an exit for a
3785 path (due to a .exit request) and then rejecting the circuit because
3786 its OR is not listed yet. It also prevents Tor clients from using an
3787 OR running in the same instance as an exit (due to a .exit request)
3788 if the OR does not meet the same requirements expected of an OR
3789 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
3790 - Correctly describe errors that occur when generating a TLS object.
3791 Previously we would attribute them to a failure while generating a
3792 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
3794 - Enforce multiplicity rules when parsing annotations. Bugfix on
3795 0.2.0.8-alpha. Found by piebeer.
3796 - Fix warnings that newer versions of autoconf produced during
3797 ./autogen.sh. These warnings appear to be harmless in our case,
3798 but they were extremely verbose. Fixes bug 2020.
3800 o Minor bugfixes (on Tor 0.2.2.x):
3801 - Enable protection of small arrays whenever we build with gcc
3802 hardening features, not only when also building with warnings
3803 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
3806 - Make hidden services work better in private Tor networks by not
3807 requiring any uptime to join the hidden service descriptor
3808 DHT. Implements ticket 2088.
3809 - Rate-limit the "your application is giving Tor only an IP address"
3810 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
3811 - When AllowSingleHopExits is set, print a warning to explain to the
3812 relay operator why most clients are avoiding her relay.
3813 - Update to the November 1 2010 Maxmind GeoLite Country database.
3815 o Code simplifications and refactoring:
3816 - When we fixed bug 1038 we had to put in a restriction not to send
3817 RELAY_EARLY cells on rend circuits. This was necessary as long
3818 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
3819 active. Now remove this obsolete check. Resolves bug 2081.
3820 - Some options used different conventions for uppercasing of acronyms
3821 when comparing manpage and source. Fix those in favor of the
3822 manpage, as it makes sense to capitalize acronyms.
3823 - Remove the torrc.complete file. It hasn't been kept up to date
3824 and users will have better luck checking out the manpage.
3825 - Remove the obsolete "NoPublish" option; it has been flagged
3826 as obsolete and has produced a warning since 0.1.1.18-rc.
3827 - Remove everything related to building the expert bundle for OS X.
3828 It has confused many users, doesn't work right on OS X 10.6,
3829 and is hard to get rid of once installed. Resolves bug 1274.
3832 Changes in version 0.2.2.17-alpha - 2010-09-30
3833 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
3834 to use one-hop circuits (which can put the exit relays at higher risk,
3835 plus unbalance the network); fixes a big bug in bandwidth accounting
3836 for relays that want to limit their monthly bandwidth use; fixes a
3837 big pile of bugs in how clients tolerate temporary network failure;
3838 and makes our adaptive circuit build timeout feature (which improves
3839 client performance if your network is fast while not breaking things
3840 if your network is slow) better handle bad networks.
3843 - Exit relays now try harder to block exit attempts from unknown
3844 relays, to make it harder for people to use them as one-hop proxies
3845 a la tortunnel. Controlled by the refuseunknownexits consensus
3846 parameter (currently enabled), or you can override it on your
3847 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
3849 o Major bugfixes (0.2.1.x and earlier):
3850 - Fix a bug in bandwidth accounting that could make us use twice
3851 the intended bandwidth when our interval start changes due to
3852 daylight saving time. Now we tolerate skew in stored vs computed
3853 interval starts: if the start of the period changes by no more than
3854 50% of the period's duration, we remember bytes that we transferred
3855 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
3856 - Always search the Windows system directory for system DLLs, and
3857 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
3858 - When you're using bridges and your network goes away and your
3859 bridges get marked as down, recover when you attempt a new socks
3860 connection (if the network is back), rather than waiting up to an
3861 hour to try fetching new descriptors for your bridges. Bugfix on
3862 0.2.0.3-alpha; fixes bug 1981.
3864 o Major bugfixes (on 0.2.2.x):
3865 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
3867 - Fix a segfault that could happen when operating a bridge relay with
3868 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
3869 - The consensus bandwidth-weights (used by clients to choose fast
3870 relays) entered an unexpected edge case in September where
3871 Exits were much scarcer than Guards, resulting in bad weight
3872 recommendations. Now we compute them using new constraints that
3873 should succeed in all cases. Also alter directory authorities to
3874 not include the bandwidth-weights line if they fail to produce
3875 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
3876 - When weighting bridges during path selection, we used to trust
3877 the bandwidths they provided in their descriptor, only capping them
3878 at 10MB/s. This turned out to be problematic for two reasons:
3879 Bridges could claim to handle a lot more traffic then they
3880 actually would, thus making more clients pick them and have a
3881 pretty effective DoS attack. The other issue is that new bridges
3882 that might not have a good estimate for their bw capacity yet
3883 would not get used at all unless no other bridges are available
3884 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
3886 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
3887 - Ignore cannibalized circuits when recording circuit build times.
3888 This should provide for a minor performance improvement for hidden
3889 service users using 0.2.2.14-alpha, and should remove two spurious
3890 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
3891 - Simplify the logic that causes us to decide if the network is
3892 unavailable for purposes of recording circuit build times. If we
3893 receive no cells whatsoever for the entire duration of a circuit's
3894 full measured lifetime, the network is probably down. Also ignore
3895 one-hop directory fetching circuit timeouts when calculating our
3896 circuit build times. These changes should hopefully reduce the
3897 cases where we see ridiculous circuit build timeouts for people
3898 with spotty wireless connections. Fixes part of bug 1772; bugfix
3900 - Prevent the circuit build timeout from becoming larger than
3901 the maximum build time we have ever seen. Also, prevent the time
3902 period for measurement circuits from becoming larger than twice that
3903 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
3906 - When we run out of directory information such that we can't build
3907 circuits, but then get enough that we can build circuits, log when
3908 we actually construct a circuit, so the user has a better chance of
3909 knowing what's going on. Fixes bug 1362.
3910 - Be more generous with how much bandwidth we'd use up (with
3911 accounting enabled) before entering "soft hibernation". Previously,
3912 we'd refuse new connections and circuits once we'd used up 95% of
3913 our allotment. Now, we use up 95% of our allotment, AND make sure
3914 that we have no more than 500MB (or 3 hours of expected traffic,
3915 whichever is lower) remaining before we enter soft hibernation.
3916 - If we've configured EntryNodes and our network goes away and/or all
3917 our entrynodes get marked down, optimistically retry them all when
3918 a new socks application request appears. Fixes bug 1882.
3919 - Add some more defensive programming for architectures that can't
3920 handle unaligned integer accesses. We don't know of any actual bugs
3921 right now, but that's the best time to fix them. Fixes bug 1943.
3922 - Support line continuations in the torrc config file. If a line
3923 ends with a single backslash character, the newline is ignored, and
3924 the configuration value is treated as continuing on the next line.
3927 o Minor bugfixes (on 0.2.1.x and earlier):
3928 - For bandwidth accounting, calculate our expected bandwidth rate
3929 based on the time during which we were active and not in
3930 soft-hibernation during the last interval. Previously, we were
3931 also considering the time spent in soft-hibernation. If this
3932 was a long time, we would wind up underestimating our bandwidth
3933 by a lot, and skewing our wakeup time towards the start of the
3934 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
3936 o Minor bugfixes (on 0.2.2.x):
3937 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
3938 which were disabled by the circuit build timeout changes in
3939 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
3940 - Make sure we don't warn about missing bandwidth weights when
3941 choosing bridges or other relays not in the consensus. Bugfix on
3942 0.2.2.10-alpha; fixes bug 1805.
3943 - In our logs, do not double-report signatures from unrecognized
3944 authorities both as "from unknown authority" and "not
3945 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
3948 Changes in version 0.2.2.16-alpha - 2010-09-17
3949 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
3950 evident at exit relays), and also continues to resolve all the little
3951 bugs that have been filling up trac lately.
3953 o Major bugfixes (stream-level fairness):
3954 - When receiving a circuit-level SENDME for a blocked circuit, try
3955 to package cells fairly from all the streams that had previously
3956 been blocked on that circuit. Previously, we had started with the
3957 oldest stream, and allowed each stream to potentially exhaust
3958 the circuit's package window. This gave older streams on any
3959 given circuit priority over newer ones. Fixes bug 1937. Detected
3960 originally by Camilo Viecco. This bug was introduced before the
3961 first Tor release, in svn commit r152: it is the new winner of
3962 the longest-lived bug prize.
3963 - When the exit relay got a circuit-level sendme cell, it started
3964 reading on the exit streams, even if had 500 cells queued in the
3965 circuit queue already, so the circuit queue just grew and grew in
3966 some cases. We fix this by not re-enabling reading on receipt of a
3967 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
3968 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
3970 - Newly created streams were allowed to read cells onto circuits,
3971 even if the circuit's cell queue was blocked and waiting to drain.
3972 This created potential unfairness, as older streams would be
3973 blocked, but newer streams would gladly fill the queue completely.
3974 We add code to detect this situation and prevent any stream from
3975 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
3979 - Update to the September 1 2010 Maxmind GeoLite Country database.
3980 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
3981 not. This would lead to a cookie that is still not group readable.
3982 Closes bug 1843. Suggested by katmagic.
3983 - When logging a rate-limited warning, we now mention how many messages
3984 got suppressed since the last warning.
3985 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
3986 do individual connection-level rate limiting of clients. The torrc
3987 config options with the same names trump the consensus params, if
3988 both are present. Replaces the old "bwconnrate" and "bwconnburst"
3989 consensus params which were broken from 0.2.2.7-alpha through
3990 0.2.2.14-alpha. Closes bug 1947.
3991 - When a router changes IP address or port, authorities now launch
3992 a new reachability test for it. Implements ticket 1899.
3993 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
3994 2 no signature, 4 required" messages about consensus signatures
3995 easier to read, and make sure they get logged at the same severity
3996 as the messages explaining which keys are which. Fixes bug 1290.
3997 - Don't warn when we have a consensus that we can't verify because
3998 of missing certificates, unless those certificates are ones
3999 that we have been trying and failing to download. Fixes bug 1145.
4000 - If you configure your bridge with a known identity fingerprint,
4001 and the bridge authority is unreachable (as it is in at least
4002 one country now), fall back to directly requesting the descriptor
4003 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
4005 - When building with --enable-gcc-warnings on OpenBSD, disable
4006 warnings in system headers. This makes --enable-gcc-warnings
4007 pass on OpenBSD 4.8.
4009 o Minor bugfixes (on 0.2.1.x and earlier):
4010 - Authorities will now attempt to download consensuses if their
4011 own efforts to make a live consensus have failed. This change
4012 means authorities that restart will fetch a valid consensus, and
4013 it means authorities that didn't agree with the current consensus
4014 will still fetch and serve it if it has enough signatures. Bugfix
4015 on 0.2.0.9-alpha; fixes bug 1300.
4016 - Ensure DNS requests launched by "RESOLVE" commands from the
4017 controller respect the __LeaveStreamsUnattached setconf options. The
4018 same goes for requests launched via DNSPort or transparent
4019 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
4020 - Allow handshaking OR connections to take a full KeepalivePeriod
4021 seconds to handshake. Previously, we would close them after
4022 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4023 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4025 - Rate-limit "Failed to hand off onionskin" warnings.
4026 - Never relay a cell for a circuit we have already destroyed.
4027 Between marking a circuit as closeable and finally closing it,
4028 it may have been possible for a few queued cells to get relayed,
4029 even though they would have been immediately dropped by the next
4030 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
4031 - Never queue a cell for a circuit that's already been marked
4033 - Never vote for a server as "Running" if we have a descriptor for
4034 it claiming to be hibernating, and that descriptor was published
4035 more recently than our last contact with the server. Bugfix on
4036 0.2.0.3-alpha; fixes bug 911.
4037 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
4040 o Minor bugfixes (on 0.2.2.x):
4041 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
4042 down if a directory fetch fails and you've configured either
4043 bridges or EntryNodes. The intent was to mark the relay as down
4044 _unless_ you're using bridges or EntryNodes, since if you are
4045 then you could quickly run out of entry points.
4046 - Fix the Windows directory-listing code. A bug introduced in
4047 0.2.2.14-alpha could make Windows directory servers forget to load
4048 some of their cached v2 networkstatus files.
4049 - Really allow clients to use relays as bridges. Fixes bug 1776;
4050 bugfix on 0.2.2.15-alpha.
4051 - Demote a warn to info that happens when the CellStatistics option
4052 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
4053 Reported by Moritz Bartl.
4054 - On Windows, build correctly either with or without Unicode support.
4055 This is necessary so that Tor can support fringe platforms like
4056 Windows 98 (which has no Unicode), or Windows CE (which has no
4057 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
4060 - Add a unit test for cross-platform directory-listing code.
4063 Changes in version 0.2.2.15-alpha - 2010-08-18
4064 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
4065 fixes a variety of other bugs that were preventing performance
4066 experiments from moving forward, fixes several bothersome memory leaks,
4067 and generally closes a lot of smaller bugs that have been filling up
4071 - Stop assigning the HSDir flag to relays that disable their
4072 DirPort (and thus will refuse to answer directory requests). This
4073 fix should dramatically improve the reachability of hidden services:
4074 hidden services and hidden service clients pick six HSDir relays
4075 to store and retrieve the hidden service descriptor, and currently
4076 about half of the HSDir relays will refuse to work. Bugfix on
4077 0.2.0.10-alpha; fixes part of bug 1693.
4078 - The PerConnBWRate and Burst config options, along with the
4079 bwconnrate and bwconnburst consensus params, initialized each conn's
4080 token bucket values only when the connection is established. Now we
4081 update them if the config options change, and update them every time
4082 we get a new consensus. Otherwise we can encounter an ugly edge
4083 case where we initialize an OR conn to client-level bandwidth,
4084 but then later the relay joins the consensus and we leave it
4085 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
4086 - Fix a regression that caused Tor to rebind its ports if it receives
4087 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
4090 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
4091 should give us approximately 40-50% more Guard-flagged nodes,
4092 improving the anonymity the Tor network can provide and also
4093 decreasing the dropoff in throughput that relays experience when
4094 they first get the Guard flag.
4095 - Allow enabling or disabling the *Statistics config options while
4099 - Update to the August 1 2010 Maxmind GeoLite Country database.
4100 - Have the controller interface give a more useful message than
4101 "Internal Error" in response to failed GETINFO requests.
4102 - Warn when the same option is provided more than once in a torrc
4103 file, on the command line, or in a single SETCONF statement, and
4104 the option is one that only accepts a single line. Closes bug 1384.
4105 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4106 Patch from mingw-san.
4107 - Add support for the country code "{??}" in torrc options like
4108 ExcludeNodes, to indicate all routers of unknown country. Closes
4110 - Relays report the number of bytes spent on answering directory
4111 requests in extra-info descriptors similar to {read,write}-history.
4112 Implements enhancement 1790.
4114 o Minor bugfixes (on 0.2.1.x and earlier):
4115 - Complain if PublishServerDescriptor is given multiple arguments that
4116 include 0 or 1. This configuration will be rejected in the future.
4117 Bugfix on 0.2.0.1-alpha; closes bug 1107.
4118 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
4119 Bugfix on 0.2.0.13-alpha; closes bug 928.
4120 - Change "Application request when we're believed to be offline."
4121 notice to "Application request when we haven't used client
4122 functionality lately.", to clarify that it's not an error. Bugfix
4123 on 0.0.9.3; fixes bug 1222.
4124 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
4125 would return "551 Internal error" rather than "552 Unrecognized key
4126 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
4127 - Users can't configure a regular relay to be their bridge. It didn't
4128 work because when Tor fetched the bridge descriptor, it found
4129 that it already had it, and didn't realize that the purpose of the
4130 descriptor had changed. Now we replace routers with a purpose other
4131 than bridge with bridge descriptors when fetching them. Bugfix on
4132 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
4133 refetch the descriptor with router purpose 'general', disabling
4135 - Fix a rare bug in rend_fn unit tests: we would fail a test when
4136 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
4137 on 0.2.0.10-alpha; fixes bug 1808.
4138 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
4139 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
4140 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
4141 Servers can start sending this code when enough clients recognize
4142 it. Also update the spec to reflect this new reason. Bugfix on
4143 0.1.0.1-rc; fixes part of bug 1793.
4144 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
4145 when we switch from being a public relay to a bridge. Otherwise
4146 there will still be clients that see the relay in their consensus,
4147 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
4149 - Instead of giving an assertion failure on an internal mismatch
4150 on estimated freelist size, just log a BUG warning and try later.
4151 Mitigates but does not fix bug 1125.
4152 - Fix an assertion failure that could occur in caches or bridge users
4153 when using a very short voting interval on a testing network.
4154 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
4156 o Minor bugfixes (on 0.2.2.x):
4157 - Alter directory authorities to always consider Exit-flagged nodes
4158 as potential Guard nodes in their votes. The actual decision to
4159 use Exits as Guards is done in the consensus bandwidth weights.
4160 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
4161 - When the controller is reporting the purpose of circuits that
4162 didn't finish building before the circuit build timeout, it was
4163 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
4164 - Our libevent version parsing code couldn't handle versions like
4165 1.4.14b-stable and incorrectly warned the user about using an
4166 old and broken version of libevent. Treat 1.4.14b-stable like
4167 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
4169 - Don't use substitution references like $(VAR:MOD) when
4170 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
4171 '$(:x)' to 'x' rather than the empty string. This bites us in
4172 doc/ when configured with --disable-asciidoc. Bugfix on
4173 0.2.2.9-alpha; fixes bug 1773.
4174 - Remove a spurious hidden service server-side log notice about
4175 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
4177 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
4179 - Correctly report written bytes on linked connections. Found while
4180 implementing 1790. Bugfix on 0.2.2.4-alpha.
4181 - Fix three memory leaks: one in circuit_build_times_parse_state(),
4182 one in dirvote_add_signatures_to_pending_consensus(), and one every
4183 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
4184 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
4186 o Code simplifications and refactoring:
4187 - Take a first step towards making or.h smaller by splitting out
4188 function definitions for all source files in src/or/. Leave
4189 structures and defines in or.h for now.
4190 - Remove a bunch of unused function declarations as well as a block of
4191 #if 0'd code from the unit tests. Closes bug 1824.
4192 - New unit tests for exit-port history statistics; refactored exit
4193 statistics code to be more easily tested.
4194 - Remove the old debian/ directory from the main Tor distribution.
4195 The official Tor-for-debian git repository lives at the URL
4196 https://git.torproject.org/debian/tor.git
4199 Changes in version 0.2.2.14-alpha - 2010-07-12
4200 Tor 0.2.2.14-alpha greatly improves client-side handling of
4201 circuit build timeouts, which are used to estimate speed and improve
4202 performance. We also move to a much better GeoIP database, port Tor to
4203 Windows CE, introduce new compile flags that improve code security,
4204 add an eighth v3 directory authority, and address a lot of more
4208 - Tor directory authorities no longer crash when started with a
4209 cached-microdesc-consensus file in their data directory. Bugfix
4210 on 0.2.2.6-alpha; fixes bug 1532.
4211 - Treat an unset $HOME like an empty $HOME rather than triggering an
4212 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
4213 - Ignore negative and large circuit build timeout values that can
4214 happen during a suspend or hibernate. These values caused various
4215 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
4216 - Alter calculation of Pareto distribution parameter 'Xm' for
4217 Circuit Build Timeout learning to use the weighted average of the
4218 top N=3 modes (because we have three entry guards). Considering
4219 multiple modes should improve the timeout calculation in some cases,
4220 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
4222 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
4223 right censored distribution model. This approach improves over the
4224 synthetic timeout generation approach that was producing insanely
4225 high timeout values. Now we calculate build timeouts using truncated
4226 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
4227 - Do not close circuits that are under construction when they reach
4228 the circuit build timeout. Instead, leave them building (but do not
4229 use them) for up until the time corresponding to the 95th percentile
4230 on the Pareto CDF or 60 seconds, whichever is greater. This is done
4231 to provide better data for the new Pareto model. This percentile
4232 can be controlled by the consensus.
4235 - Move to the June 2010 Maxmind GeoLite country db (rather than the
4236 June 2009 ip-to-country GeoIP db) for our statistics that count
4237 how many users relays are seeing from each country. Now we have
4238 more accurate data for many African countries.
4239 - Port Tor to build and run correctly on Windows CE systems, using
4240 the wcecompat library. Contributed by Valerio Lupi.
4241 - New "--enable-gcc-hardening" ./configure flag (off by default)
4242 to turn on gcc compile time hardening options. It ensures
4243 that signed ints have defined behavior (-fwrapv), enables
4244 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
4245 with canaries (-fstack-protector-all), turns on ASLR protection if
4246 supported by the kernel (-fPIE, -pie), and adds additional security
4247 related warnings. Verified to work on Mac OS X and Debian Lenny.
4248 - New "--enable-linker-hardening" ./configure flag (off by default)
4249 to turn on ELF specific hardening features (relro, now). This does
4250 not work with Mac OS X or any other non-ELF binary format.
4252 o New directory authorities:
4253 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
4257 - New config option "WarnUnsafeSocks 0" disables the warning that
4258 occurs whenever Tor receives a socks handshake using a version of
4259 the socks protocol that can only provide an IP address (rather
4260 than a hostname). Setups that do DNS locally over Tor are fine,
4261 and we shouldn't spam the logs in that case.
4262 - Convert the HACKING file to asciidoc, and add a few new sections
4263 to it, explaining how we use Git, how we make changelogs, and
4264 what should go in a patch.
4265 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
4266 event, to give information on the current rate of circuit timeouts
4267 over our stored history.
4268 - Add ability to disable circuit build time learning via consensus
4269 parameter and via a LearnCircuitBuildTimeout config option. Also
4270 automatically disable circuit build time calculation if we are
4271 either a AuthoritativeDirectory, or if we fail to write our state
4272 file. Fixes bug 1296.
4273 - More gracefully handle corrupt state files, removing asserts
4274 in favor of saving a backup and resetting state.
4275 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
4279 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4281 - When a2x fails, mention that the user could disable manpages instead
4282 of trying to fix their asciidoc installation.
4283 - Where available, use Libevent 2.0's periodic timers so that our
4284 once-per-second cleanup code gets called even more closely to
4285 once per second than it would otherwise. Fixes bug 943.
4286 - If you run a bridge that listens on multiple IP addresses, and
4287 some user configures a bridge address that uses a different IP
4288 address than your bridge writes in its router descriptor, and the
4289 user doesn't specify an identity key, their Tor would discard the
4290 descriptor because "it isn't one of our configured bridges", and
4291 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
4292 Bugfix on 0.2.0.3-alpha.
4293 - If OpenSSL fails to make a duplicate of a private or public key, log
4294 an error message and try to exit cleanly. May help with debugging
4295 if bug 1209 ever remanifests.
4296 - Save a couple bytes in memory allocation every time we escape
4297 certain characters in a string. Patch from Florian Zumbiehl.
4298 - Make it explicit that we don't cannibalize one-hop circuits. This
4299 happens in the wild, but doesn't turn out to be a problem because
4300 we fortunately don't use those circuits. Many thanks to outofwords
4301 for the initial analysis and to swissknife who confirmed that
4302 two-hop circuits are actually created.
4303 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
4304 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
4305 - Eliminate a case where a circuit build time warning was displayed
4306 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
4309 Changes in version 0.2.1.26 - 2010-05-02
4310 Tor 0.2.1.26 addresses the recent connection and memory overload
4311 problems we've been seeing on relays, especially relays with their
4312 DirPort open. If your relay has been crashing, or you turned it off
4313 because it used too many resources, give this release a try.
4315 This release also fixes yet another instance of broken OpenSSL libraries
4316 that was causing some relays to drop out of the consensus.
4319 - Teach relays to defend themselves from connection overload. Relays
4320 now close idle circuits early if it looks like they were intended
4321 for directory fetches. Relays are also more aggressive about closing
4322 TLS connections that have no circuits on them. Such circuits are
4323 unlikely to be re-used, and tens of thousands of them were piling
4324 up at the fast relays, causing the relays to run out of sockets
4325 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4326 their directory fetches over TLS).
4327 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4328 that claim to be earlier than 0.9.8m, but which have in reality
4329 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4330 behavior. Possible fix for some cases of bug 1346.
4331 - Directory mirrors were fetching relay descriptors only from v2
4332 directory authorities, rather than v3 authorities like they should.
4333 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4334 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4337 - Finally get rid of the deprecated and now harmful notion of "clique
4338 mode", where directory authorities maintain TLS connections to
4342 - In the util/threads test, no longer free the test_mutex before all
4343 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4344 - The master thread could starve the worker threads quite badly on
4345 certain systems, causing them to run only partially in the allowed
4346 window. This resulted in test failures. Now the master thread sleeps
4347 occasionally for a few microseconds while the two worker-threads
4348 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4351 Changes in version 0.2.2.13-alpha - 2010-04-24
4352 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
4353 problems we've been seeing on relays, especially relays with their
4354 DirPort open. If your relay has been crashing, or you turned it off
4355 because it used too many resources, give this release a try.
4358 - Teach relays to defend themselves from connection overload. Relays
4359 now close idle circuits early if it looks like they were intended
4360 for directory fetches. Relays are also more aggressive about closing
4361 TLS connections that have no circuits on them. Such circuits are
4362 unlikely to be re-used, and tens of thousands of them were piling
4363 up at the fast relays, causing the relays to run out of sockets
4364 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4365 their directory fetches over TLS).
4368 - Finally get rid of the deprecated and now harmful notion of "clique
4369 mode", where directory authorities maintain TLS connections to
4371 - Directory authorities now do an immediate reachability check as soon
4372 as they hear about a new relay. This change should slightly reduce
4373 the time between setting up a relay and getting listed as running
4374 in the consensus. It should also improve the time between setting
4375 up a bridge and seeing use by bridge users.
4376 - Directory authorities no longer launch a TLS connection to every
4377 relay as they startup. Now that we have 2k+ descriptors cached,
4378 the resulting network hiccup is becoming a burden. Besides,
4379 authorities already avoid voting about Running for the first half
4380 hour of their uptime.
4383 Changes in version 0.2.2.12-alpha - 2010-04-20
4384 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
4385 handle and vote on descriptors. It was causing relays to drop out of
4389 - Many relays have been falling out of the consensus lately because
4390 not enough authorities know about their descriptor for them to get
4391 a majority of votes. When we deprecated the v2 directory protocol,
4392 we got rid of the only way that v3 authorities can hear from each
4393 other about other descriptors. Now authorities examine every v3
4394 vote for new descriptors, and fetch them from that authority. Bugfix
4396 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
4397 and a warning in or.h related to bandwidth_weight_rule_t that
4398 prevented clean compile on OS X. Fixes bug 1363; bugfix on
4400 - Fix a segfault on relays when DirReqStatistics is enabled
4401 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
4405 - Demote a confusing TLS warning that relay operators might get when
4406 someone tries to talk to their OrPort. It is neither the operator's
4407 fault nor can they do anything about it. Fixes bug 1364; bugfix
4411 Changes in version 0.2.2.11-alpha - 2010-04-15
4412 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
4413 libraries that was causing some relays to drop out of the consensus.
4416 - Directory mirrors were fetching relay descriptors only from v2
4417 directory authorities, rather than v3 authorities like they should.
4418 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4419 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4420 - Fix a parsing error that made every possible value of
4421 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
4422 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
4423 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
4424 about the option without breaking older ones.
4425 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4426 that claim to be earlier than 0.9.8m, but which have in reality
4427 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4428 behavior. Possible fix for some cases of bug 1346.
4431 - Experiment with a more aggressive approach to preventing clients
4432 from making one-hop exit streams. Exit relays who want to try it
4433 out can set "RefuseUnknownExits 1" in their torrc, and then look
4434 for "Attempt by %s to open a stream" log messages. Let us know
4436 - Add support for statically linking zlib by specifying
4437 --enable-static-zlib, to go with our support for statically linking
4438 openssl and libevent. Resolves bug 1358.
4441 - Fix a segfault that happens whenever a Tor client that is using
4442 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
4444 - When we cleaned up the contrib/tor-exit-notice.html file, we left
4445 out the first line. Fixes bug 1295.
4446 - When building the manpage from a tarball, we required asciidoc, but
4447 the asciidoc -> roff/html conversion was already done for the
4448 tarball. Make 'make' complain only when we need asciidoc (either
4449 because we're compiling directly from git, or because we altered
4450 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
4451 - When none of the directory authorities vote on any params, Tor
4452 segfaulted when trying to make the consensus from the votes. We
4453 didn't trigger the bug in practice, because authorities do include
4454 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
4457 - In the util/threads test, no longer free the test_mutex before all
4458 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4459 - The master thread could starve the worker threads quite badly on
4460 certain systems, causing them to run only partially in the allowed
4461 window. This resulted in test failures. Now the master thread sleeps
4462 occasionally for a few microseconds while the two worker-threads
4463 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4466 Changes in version 0.2.2.10-alpha - 2010-03-07
4467 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
4468 could prevent relays from guessing their IP address correctly. It also
4469 starts the groundwork for another client-side performance boost, since
4470 currently we're not making efficient use of relays that have both the
4471 Guard flag and the Exit flag.
4474 - Fix a regression from our patch for bug 1244 that caused relays
4475 to guess their IP address incorrectly if they didn't set Address
4476 in their torrc and/or their address fails to resolve. Bugfix on
4477 0.2.2.9-alpha; fixes bug 1269.
4479 o Major features (performance):
4480 - Directory authorities now compute consensus weightings that instruct
4481 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
4482 and no flag. Clients that use these weightings will distribute
4483 network load more evenly across these different relay types. The
4484 weightings are in the consensus so we can change them globally in
4485 the future. Extra thanks to "outofwords" for finding some nasty
4486 security bugs in the first implementation of this feature.
4488 o Minor features (performance):
4489 - Always perform router selections using weighted relay bandwidth,
4490 even if we don't need a high capacity circuit at the time. Non-fast
4491 circuits now only differ from fast ones in that they can use relays
4492 not marked with the Fast flag. This "feature" could turn out to
4493 be a horrible bug; we should investigate more before it goes into
4497 - Allow disabling building of the manpages. Skipping the manpage
4498 speeds up the build considerably.
4500 o Minor bugfixes (on 0.2.2.x):
4501 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
4502 Bugfix on 0.2.2.9-alpha.
4503 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
4504 config option. Bugfix on 0.2.2.7-alpha.
4505 - Ship the asciidoc-helper file in the tarball, so that people can
4506 build from source if they want to, and touching the .1.txt files
4507 doesn't break the build. Bugfix on 0.2.2.9-alpha.
4509 o Minor bugfixes (on 0.2.1.x or earlier):
4510 - Fix a dereference-then-NULL-check sequence when publishing
4511 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4513 - Fix another dereference-then-NULL-check sequence. Bugfix on
4514 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4515 - Make sure we treat potentially not NUL-terminated strings correctly.
4516 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4518 o Code simplifications and refactoring:
4519 - Fix some urls in the exit notice file and make it XHTML1.1 strict
4520 compliant. Based on a patch from Christian Kujau.
4521 - Don't use sed in asciidoc-helper anymore.
4522 - Make the build process fail if asciidoc cannot be found and
4523 building with asciidoc isn't disabled.
4526 Changes in version 0.2.2.9-alpha - 2010-02-22
4527 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
4528 location of a directory authority, and cleans up a bunch of small bugs.
4530 o Directory authority changes:
4531 - Change IP address for dannenberg (v3 directory authority), and
4532 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4533 service directory authority) from the list.
4536 - Make Tor work again on the latest OS X: when deciding whether to
4537 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4538 version at run-time, not compile time. We need to do this because
4539 Apple doesn't update its dev-tools headers when it updates its
4540 libraries in a security patch.
4541 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4542 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4543 a memory leak when requesting a hidden service descriptor we've
4544 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4546 - Authorities could be tricked into giving out the Exit flag to relays
4547 that didn't allow exiting to any ports. This bug could screw
4548 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
4549 1238. Bug discovered by Martin Kowalczyk.
4550 - When freeing a session key, zero it out completely. We only zeroed
4551 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4552 patched by ekir. Fixes bug 1254.
4555 - Fix static compilation by listing the openssl libraries in the right
4556 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
4557 - Resume handling .exit hostnames in a special way: originally we
4558 stripped the .exit part and used the requested exit relay. In
4559 0.2.2.1-alpha we stopped treating them in any special way, meaning
4560 if you use a .exit address then Tor will pass it on to the exit
4561 relay. Now we reject the .exit stream outright, since that behavior
4562 might be more expected by the user. Found and diagnosed by Scott
4563 Bennett and Downie on or-talk.
4564 - Don't spam the controller with events when we have no file
4565 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
4566 for log messages was already solved from bug 748.)
4567 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
4569 - Make the DNSPort option work with libevent 2.x. Don't alter the
4570 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
4571 - Emit a GUARD DROPPED controller event for a case we missed.
4572 - Make more fields in the controller protocol case-insensitive, since
4573 control-spec.txt said they were.
4574 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4575 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4576 - Fix a spec conformance issue: the network-status-version token
4577 must be the first token in a v3 consensus or vote. Discovered by
4578 parakeep. Bugfix on 0.2.0.3-alpha.
4580 o Code simplifications and refactoring:
4581 - Generate our manpage and HTML documentation using Asciidoc. This
4582 change should make it easier to maintain the documentation, and
4584 - Remove the --enable-iphone option. According to reports from Marco
4585 Bonetti, Tor builds fine without any special tweaking on recent
4586 iPhone SDK versions.
4587 - Removed some unnecessary files from the source distribution. The
4588 AUTHORS file has now been merged into the people page on the
4589 website. The roadmaps and design doc can now be found in the
4590 projects directory in svn.
4591 - Enabled various circuit build timeout constants to be controlled
4592 by consensus parameters. Also set better defaults for these
4593 parameters based on experimentation on broadband and simulated
4597 - The 'EXTENDCIRCUIT' control port command can now be used with
4598 a circ id of 0 and no path. This feature will cause Tor to build
4599 a new 'fast' general purpose circuit using its own path selection
4601 - Added a BUILDTIMEOUT_SET controller event to describe changes
4602 to the circuit build timeout.
4603 - Future-proof the controller protocol a bit by ignoring keyword
4604 arguments we do not recognize.
4605 - Expand homedirs passed to tor-checkkey. This should silence a
4606 coverity complaint about passing a user-supplied string into
4607 open() without checking it.
4610 Changes in version 0.2.1.25 - 2010-03-16
4611 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
4612 prevent relays from guessing their IP address correctly. It also fixes
4613 several minor potential security bugs.
4616 - Fix a regression from our patch for bug 1244 that caused relays
4617 to guess their IP address incorrectly if they didn't set Address
4618 in their torrc and/or their address fails to resolve. Bugfix on
4619 0.2.1.23; fixes bug 1269.
4620 - When freeing a session key, zero it out completely. We only zeroed
4621 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4622 patched by ekir. Fixes bug 1254.
4625 - Fix a dereference-then-NULL-check sequence when publishing
4626 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4628 - Fix another dereference-then-NULL-check sequence. Bugfix on
4629 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4630 - Make sure we treat potentially not NUL-terminated strings correctly.
4631 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4635 Changes in version 0.2.1.24 - 2010-02-21
4636 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
4640 - Work correctly out-of-the-box with even more vendor-patched versions
4641 of OpenSSL. In particular, make it so Debian and OS X don't need
4642 customized patches to run/build.
4645 Changes in version 0.2.1.23 - 2010-02-13
4646 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
4647 again on the latest OS X, and updates the location of a directory
4650 o Major bugfixes (performance):
4651 - We were selecting our guards uniformly at random, and then weighting
4652 which of our guards we'd use uniformly at random. This imbalance
4653 meant that Tor clients were severely limited on throughput (and
4654 probably latency too) by the first hop in their circuit. Now we
4655 select guards weighted by currently advertised bandwidth. We also
4656 automatically discard guards picked using the old algorithm. Fixes
4657 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4660 - Make Tor work again on the latest OS X: when deciding whether to
4661 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4662 version at run-time, not compile time. We need to do this because
4663 Apple doesn't update its dev-tools headers when it updates its
4664 libraries in a security patch.
4665 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4666 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4667 a memory leak when requesting a hidden service descriptor we've
4668 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4671 o Directory authority changes:
4672 - Change IP address for dannenberg (v3 directory authority), and
4673 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4674 service directory authority) from the list.
4677 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4678 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4681 - Avoid a mad rush at the beginning of each month when each client
4682 rotates half of its guards. Instead we spread the rotation out
4683 throughout the month, but we still avoid leaving a precise timestamp
4684 in the state file about when we first picked the guard. Improves
4685 over the behavior introduced in 0.1.2.17.
4688 Changes in version 0.2.2.8-alpha - 2010-01-26
4689 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
4690 causing bridge relays to disappear. If you're running a bridge,
4694 - Fix a memory corruption bug on bridges that occured during the
4695 inclusion of stats data in extra-info descriptors. Also fix the
4696 interface for geoip_get_bridge_stats* to prevent similar bugs in
4697 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
4698 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
4701 - Ignore OutboundBindAddress when connecting to localhost.
4702 Connections to localhost need to come _from_ localhost, or else
4703 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
4707 Changes in version 0.2.2.7-alpha - 2010-01-19
4708 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
4709 as laying the groundwork for further relay-side performance fixes. It
4710 also starts cleaning up client behavior with respect to the EntryNodes,
4711 ExitNodes, and StrictNodes config options.
4713 This release also rotates two directory authority keys, due to a
4714 security breach of some of the Torproject servers.
4716 o Directory authority changes:
4717 - Rotate keys (both v3 identity and relay identity) for moria1
4720 o Major features (performance):
4721 - We were selecting our guards uniformly at random, and then weighting
4722 which of our guards we'd use uniformly at random. This imbalance
4723 meant that Tor clients were severely limited on throughput (and
4724 probably latency too) by the first hop in their circuit. Now we
4725 select guards weighted by currently advertised bandwidth. We also
4726 automatically discard guards picked using the old algorithm. Fixes
4727 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4728 - When choosing which cells to relay first, relays can now favor
4729 circuits that have been quiet recently, to provide lower latency
4730 for low-volume circuits. By default, relays enable or disable this
4731 feature based on a setting in the consensus. You can override
4732 this default by using the new "CircuitPriorityHalflife" config
4733 option. Design and code by Ian Goldberg, Can Tang, and Chris
4735 - Add separate per-conn write limiting to go with the per-conn read
4736 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
4737 but never per-conn write limits.
4738 - New consensus params "bwconnrate" and "bwconnburst" to let us
4739 rate-limit client connections as they enter the network. It's
4740 controlled in the consensus so we can turn it on and off for
4741 experiments. It's starting out off. Based on proposal 163.
4743 o Major features (relay selection options):
4744 - Switch to a StrictNodes config option, rather than the previous
4745 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
4746 "StrictExcludeNodes" option.
4747 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
4748 change during a config reload, mark and discard all our origin
4749 circuits. This fix should address edge cases where we change the
4750 config options and but then choose a circuit that we created before
4752 - If EntryNodes or ExitNodes are set, be more willing to use an
4753 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
4755 - Make EntryNodes config option much more aggressive even when
4756 StrictNodes is not set. Before it would prepend your requested
4757 entrynodes to your list of guard nodes, but feel free to use others
4758 after that. Now it chooses only from your EntryNodes if any of
4759 those are available, and only falls back to others if a) they're
4760 all down and b) StrictNodes is not set.
4761 - Now we refresh your entry guards from EntryNodes at each consensus
4762 fetch -- rather than just at startup and then they slowly rot as
4763 the network changes.
4766 - Stop bridge directory authorities from answering dbg-stability.txt
4767 directory queries, which would let people fetch a list of all
4768 bridge identities they track. Bugfix on 0.2.1.6-alpha.
4771 - Log a notice when we get a new control connection. Now it's easier
4772 for security-conscious users to recognize when a local application
4773 is knocking on their controller door. Suggested by bug 1196.
4774 - New config option "CircuitStreamTimeout" to override our internal
4775 timeout schedule for how many seconds until we detach a stream from
4776 a circuit and try a new circuit. If your network is particularly
4777 slow, you might want to set this to a number like 60.
4778 - New controller command "getinfo config-text". It returns the
4779 contents that Tor would write if you send it a SAVECONF command,
4780 so the controller can write the file to disk itself.
4781 - New options for SafeLogging to allow scrubbing only log messages
4782 generated while acting as a relay.
4783 - Ship the bridges spec file in the tarball too.
4784 - Avoid a mad rush at the beginning of each month when each client
4785 rotates half of its guards. Instead we spread the rotation out
4786 throughout the month, but we still avoid leaving a precise timestamp
4787 in the state file about when we first picked the guard. Improves
4788 over the behavior introduced in 0.1.2.17.
4790 o Minor bugfixes (compiling):
4791 - Fix compilation on OS X 10.3, which has a stub mlockall() but
4792 hides it. Bugfix on 0.2.2.6-alpha.
4793 - Fix compilation on Solaris by removing support for the
4794 DisableAllSwap config option. Solaris doesn't have an rlimit for
4795 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
4798 o Minor bugfixes (crashes):
4799 - Do not segfault when writing buffer stats when we haven't observed
4800 a single circuit to report about. Found by Fabian Lanze. Bugfix on
4802 - If we're in the pathological case where there's no exit bandwidth
4803 but there is non-exit bandwidth, or no guard bandwidth but there
4804 is non-guard bandwidth, don't crash during path selection. Bugfix
4806 - Fix an impossible-to-actually-trigger buffer overflow in relay
4807 descriptor generation. Bugfix on 0.1.0.15.
4809 o Minor bugfixes (privacy):
4810 - Fix an instance where a Tor directory mirror might accidentally
4811 log the IP address of a misbehaving Tor client. Bugfix on
4813 - Don't list Windows capabilities in relay descriptors. We never made
4814 use of them, and maybe it's a bad idea to publish them. Bugfix
4817 o Minor bugfixes (other):
4818 - Resolve an edge case in path weighting that could make us misweight
4819 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
4820 - Fix statistics on client numbers by country as seen by bridges that
4821 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
4822 intervals instead of variable 12-to-48-hour intervals.
4823 - After we free an internal connection structure, overwrite it
4824 with a different memory value than we use for overwriting a freed
4825 internal circuit structure. Should help with debugging. Suggested
4827 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
4831 - Remove the HSAuthorityRecordStats option that version 0 hidden
4832 service authorities could have used to track statistics of overall
4833 hidden service usage.
4836 Changes in version 0.2.1.22 - 2010-01-19
4837 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
4838 authorities -- it would tell you its whole history of bridge descriptors
4839 if you make the right directory request. This stable update also
4840 rotates two of the seven v3 directory authority keys and locations.
4842 o Directory authority changes:
4843 - Rotate keys (both v3 identity and relay identity) for moria1
4847 - Stop bridge directory authorities from answering dbg-stability.txt
4848 directory queries, which would let people fetch a list of all
4849 bridge identities they track. Bugfix on 0.2.1.6-alpha.
4852 Changes in version 0.2.1.21 - 2009-12-21
4853 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
4854 library. If you use Tor on Linux / Unix and you're getting SSL
4855 renegotiation errors, upgrading should help. We also recommend an
4856 upgrade if you're an exit relay.
4859 - Work around a security feature in OpenSSL 0.9.8l that prevents our
4860 handshake from working unless we explicitly tell OpenSSL that we
4861 are using SSL renegotiation safely. We are, of course, but OpenSSL
4862 0.9.8l won't work unless we say we are.
4863 - Avoid crashing if the client is trying to upload many bytes and the
4864 circuit gets torn down at the same time, or if the flip side
4865 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
4868 - Do not refuse to learn about authority certs and v2 networkstatus
4869 documents that are older than the latest consensus. This bug might
4870 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
4871 Spotted and fixed by xmux.
4872 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
4873 trigger platform-specific option misparsing case found by Coverity
4875 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
4876 trigger assert. Fixes bug 1173.
4879 Changes in version 0.2.2.6-alpha - 2009-11-19
4880 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
4881 support for the new lower-footprint "microdescriptor" directory design,
4882 future-proofing our consensus format against new hash functions or
4883 other changes, and an Android port. It also makes Tor compatible with
4884 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
4887 - Directory authorities can now create, vote on, and serve multiple
4888 parallel formats of directory data as part of their voting process.
4889 Partially implements Proposal 162: "Publish the consensus in
4891 - Directory authorities can now agree on and publish small summaries
4892 of router information that clients can use in place of regular
4893 server descriptors. This transition will eventually allow clients
4894 to use far less bandwidth for downloading information about the
4895 network. Begins the implementation of Proposal 158: "Clients
4896 download consensus + microdescriptors".
4897 - The directory voting system is now extensible to use multiple hash
4898 algorithms for signatures and resource selection. Newer formats
4899 are signed with SHA256, with a possibility for moving to a better
4900 hash algorithm in the future.
4901 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
4902 current and future memory pages via mlockall(). On supported
4903 platforms (modern Linux and probably BSD but not Windows or OS X),
4904 this should effectively disable any and all attempts to page out
4905 memory. This option requires that you start your Tor as root --
4906 if you use DisableAllSwap, please consider using the User option
4907 to properly reduce the privileges of your Tor.
4908 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
4909 to help Tor build correctly for Android phones.
4912 - Work around a security feature in OpenSSL 0.9.8l that prevents our
4913 handshake from working unless we explicitly tell OpenSSL that we
4914 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
4915 won't work unless we say we are.
4918 - Fix a crash bug when trying to initialize the evdns module in
4919 Libevent 2. Bugfix on 0.2.1.16-rc.
4920 - Stop logging at severity 'warn' when some other Tor client tries
4921 to establish a circuit with us using weak DH keys. It's a protocol
4922 violation, but that doesn't mean ordinary users need to hear about
4923 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
4924 - Do not refuse to learn about authority certs and v2 networkstatus
4925 documents that are older than the latest consensus. This bug might
4926 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
4927 Spotted and fixed by xmux.
4928 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
4929 - If all authorities restart at once right before a consensus vote,
4930 nobody will vote about "Running", and clients will get a consensus
4931 with no usable relays. Instead, authorities refuse to build a
4932 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
4933 - If your relay can't keep up with the number of incoming create
4934 cells, it would log one warning per failure into your logs. Limit
4935 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
4936 - Bridges now use "reject *:*" as their default exit policy. Bugfix
4937 on 0.2.0.3-alpha; fixes bug 1113.
4938 - Fix a memory leak on directory authorities during voting that was
4939 introduced in 0.2.2.1-alpha. Found via valgrind.
4942 Changes in version 0.2.1.20 - 2009-10-15
4943 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
4944 services at once, prepares for more performance improvements, and
4945 fixes a bunch of smaller bugs.
4947 The Windows and OS X bundles also include a more recent Vidalia,
4948 and switch from Privoxy to Polipo.
4950 The OS X installers are now drag and drop. It's best to un-install
4951 Tor/Vidalia and then install this new bundle, rather than upgrade. If
4952 you want to upgrade, you'll need to update the paths for Tor and Polipo
4953 in the Vidalia Settings window.
4956 - Send circuit or stream sendme cells when our window has decreased
4957 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
4958 by Karsten when testing the "reduce circuit window" performance
4959 patch. Bugfix on the 54th commit on Tor -- from July 2002,
4960 before the release of Tor 0.0.0. This is the new winner of the
4962 - Fix a remotely triggerable memory leak when a consensus document
4963 contains more than one signature from the same voter. Bugfix on
4965 - Avoid segfault in rare cases when finishing an introduction circuit
4966 as a client and finding out that we don't have an introduction key
4967 for it. Fixes bug 1073. Reported by Aaron Swartz.
4970 - Tor now reads the "circwindow" parameter out of the consensus,
4971 and uses that value for its circuit package window rather than the
4972 default of 1000 cells. Begins the implementation of proposal 168.
4974 o New directory authorities:
4975 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
4977 - Move moria1 and tonga to alternate IP addresses.
4980 - Fix a signed/unsigned compile warning in 0.2.1.19.
4981 - Fix possible segmentation fault on directory authorities. Bugfix on
4983 - Fix an extremely rare infinite recursion bug that could occur if
4984 we tried to log a message after shutting down the log subsystem.
4985 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
4986 - Fix an obscure bug where hidden services on 64-bit big-endian
4987 systems might mis-read the timestamp in v3 introduce cells, and
4988 refuse to connect back to the client. Discovered by "rotor".
4989 Bugfix on 0.2.1.6-alpha.
4990 - We were triggering a CLOCK_SKEW controller status event whenever
4991 we connect via the v2 connection protocol to any relay that has
4992 a wrong clock. Instead, we should only inform the controller when
4993 it's a trusted authority that claims our clock is wrong. Bugfix
4994 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
4995 - We were telling the controller about CHECKING_REACHABILITY and
4996 REACHABILITY_FAILED status events whenever we launch a testing
4997 circuit or notice that one has failed. Instead, only tell the
4998 controller when we want to inform the user of overall success or
4999 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5001 - Don't warn when we're using a circuit that ends with a node
5002 excluded in ExcludeExitNodes, but the circuit is not used to access
5003 the outside world. This should help fix bug 1090. Bugfix on
5005 - Work around a small memory leak in some versions of OpenSSL that
5006 stopped the memory used by the hostname TLS extension from being
5010 - Add a "getinfo status/accepted-server-descriptor" controller
5011 command, which is the recommended way for controllers to learn
5012 whether our server descriptor has been successfully received by at
5013 least on directory authority. Un-recommend good-server-descriptor
5014 getinfo and status events until we have a better design for them.
5017 Changes in version 0.2.2.5-alpha - 2009-10-11
5018 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
5021 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
5023 o Directory authorities:
5024 - Temporarily (just for this release) move dizum to an alternate
5028 Changes in version 0.2.2.4-alpha - 2009-10-10
5029 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
5030 introduces a new unit test framework, shifts directry authority
5031 addresses around to reduce the impact from recent blocking events,
5032 and fixes a few smaller bugs.
5035 - Fix several more asserts in the circuit_build_times code, for
5036 example one that causes Tor to fail to start once we have
5037 accumulated 5000 build times in the state file. Bugfixes on
5038 0.2.2.2-alpha; fixes bug 1108.
5040 o New directory authorities:
5041 - Move moria1 and Tonga to alternate IP addresses.
5044 - Log SSL state transitions at debug level during handshake, and
5045 include SSL states in error messages. This may help debug future
5046 SSL handshake issues.
5047 - Add a new "Handshake" log domain for activities that happen
5048 during the TLS handshake.
5049 - Revert to the "June 3 2009" ip-to-country file. The September one
5050 seems to have removed most US IP addresses.
5051 - Directory authorities now reject Tor relays with versions less than
5052 0.1.2.14. This step cuts out four relays from the current network,
5053 none of which are very big.
5056 - Fix a couple of smaller issues with gathering statistics. Bugfixes
5058 - Fix two memory leaks in the error case of
5059 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
5060 - Don't count one-hop circuits when we're estimating how long it
5061 takes circuits to build on average. Otherwise we'll set our circuit
5062 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
5063 - Directory authorities no longer change their opinion of, or vote on,
5064 whether a router is Running, unless they have themselves been
5065 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
5068 o Code simplifications and refactoring:
5069 - Revise our unit tests to use the "tinytest" framework, so we
5070 can run tests in their own processes, have smarter setup/teardown
5071 code, and so on. The unit test code has moved to its own
5072 subdirectory, and has been split into multiple modules.
5075 Changes in version 0.2.2.3-alpha - 2009-09-23
5076 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
5079 - Fix an overzealous assert in our new circuit build timeout code.
5080 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
5083 - If the networkstatus consensus tells us that we should use a
5084 negative circuit package window, ignore it. Otherwise we'll
5085 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
5088 Changes in version 0.2.2.2-alpha - 2009-09-21
5089 Tor 0.2.2.2-alpha introduces our latest performance improvement for
5090 clients: Tor tracks the average time it takes to build a circuit, and
5091 avoids using circuits that take too long to build. For fast connections,
5092 this feature can cut your expected latency in half. For slow or flaky
5093 connections, it could ruin your Tor experience. Let us know if it does!
5096 - Tor now tracks how long it takes to build client-side circuits
5097 over time, and adapts its timeout to local network performance.
5098 Since a circuit that takes a long time to build will also provide
5099 bad performance, we get significant latency improvements by
5100 discarding the slowest 20% of circuits. Specifically, Tor creates
5101 circuits more aggressively than usual until it has enough data
5102 points for a good timeout estimate. Implements proposal 151.
5103 We are especially looking for reports (good and bad) from users with
5104 both EDGE and broadband connections that can move from broadband
5105 to EDGE and find out if the build-time data in the .tor/state gets
5106 reset without loss of Tor usability. You should also see a notice
5107 log message telling you that Tor has reset its timeout.
5108 - Directory authorities can now vote on arbitary integer values as
5109 part of the consensus process. This is designed to help set
5110 network-wide parameters. Implements proposal 167.
5111 - Tor now reads the "circwindow" parameter out of the consensus,
5112 and uses that value for its circuit package window rather than the
5113 default of 1000 cells. Begins the implementation of proposal 168.
5116 - Fix a remotely triggerable memory leak when a consensus document
5117 contains more than one signature from the same voter. Bugfix on
5121 - Fix an extremely rare infinite recursion bug that could occur if
5122 we tried to log a message after shutting down the log subsystem.
5123 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5124 - Fix parsing for memory or time units given without a space between
5125 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
5126 - A networkstatus vote must contain exactly one signature. Spec
5127 conformance issue. Bugfix on 0.2.0.3-alpha.
5128 - Fix an obscure bug where hidden services on 64-bit big-endian
5129 systems might mis-read the timestamp in v3 introduce cells, and
5130 refuse to connect back to the client. Discovered by "rotor".
5131 Bugfix on 0.2.1.6-alpha.
5132 - We were triggering a CLOCK_SKEW controller status event whenever
5133 we connect via the v2 connection protocol to any relay that has
5134 a wrong clock. Instead, we should only inform the controller when
5135 it's a trusted authority that claims our clock is wrong. Bugfix
5136 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5137 - We were telling the controller about CHECKING_REACHABILITY and
5138 REACHABILITY_FAILED status events whenever we launch a testing
5139 circuit or notice that one has failed. Instead, only tell the
5140 controller when we want to inform the user of overall success or
5141 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5143 - Don't warn when we're using a circuit that ends with a node
5144 excluded in ExcludeExitNodes, but the circuit is not used to access
5145 the outside world. This should help fix bug 1090, but more problems
5146 remain. Bugfix on 0.2.1.6-alpha.
5147 - Work around a small memory leak in some versions of OpenSSL that
5148 stopped the memory used by the hostname TLS extension from being
5150 - Make our 'torify' script more portable; if we have only one of
5151 'torsocks' or 'tsocks' installed, don't complain to the user;
5152 and explain our warning about tsocks better.
5155 - Add a "getinfo status/accepted-server-descriptor" controller
5156 command, which is the recommended way for controllers to learn
5157 whether our server descriptor has been successfully received by at
5158 least on directory authority. Un-recommend good-server-descriptor
5159 getinfo and status events until we have a better design for them.
5160 - Update to the "September 4 2009" ip-to-country file.
5163 Changes in version 0.2.2.1-alpha - 2009-08-26
5164 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
5165 Tor clients to bootstrap on networks where only port 80 is reachable,
5166 makes it more straightforward to support hardware crypto accelerators,
5167 and starts the groundwork for gathering stats safely at relays.
5170 - Start the process of disabling ".exit" address notation, since it
5171 can be used for a variety of esoteric application-level attacks
5172 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
5175 o New directory authorities:
5176 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5180 - New AccelName and AccelDir options add support for dynamic OpenSSL
5181 hardware crypto acceleration engines.
5182 - Tor now supports tunneling all of its outgoing connections over
5183 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
5184 configuration options. Code by Christopher Davis.
5187 - Send circuit or stream sendme cells when our window has decreased
5188 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5189 by Karsten when testing the "reduce circuit window" performance
5190 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5191 before the release of Tor 0.0.0. This is the new winner of the
5194 o New options for gathering stats safely:
5195 - Directory mirrors that set "DirReqStatistics 1" write statistics
5196 about directory requests to disk every 24 hours. As compared to the
5197 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
5198 1) stats are written to disk exactly every 24 hours; 2) estimated
5199 shares of v2 and v3 requests are determined as mean values, not at
5200 the end of a measurement period; 3) unresolved requests are listed
5201 with country code '??'; 4) directories also measure download times.
5202 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
5203 number of exit streams and transferred bytes per port to disk every
5205 - Relays that set "CellStatistics 1" write statistics on how long
5206 cells spend in their circuit queues to disk every 24 hours.
5207 - Entry nodes that set "EntryStatistics 1" write statistics on the
5208 rough number and origins of connecting clients to disk every 24
5210 - Relays that write any of the above statistics to disk and set
5211 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
5212 their extra-info documents.
5215 - New --digests command-line switch to output the digests of the
5216 source files Tor was built with.
5217 - The "torify" script now uses torsocks where available.
5218 - The memarea code now uses a sentinel value at the end of each area
5219 to make sure nothing writes beyond the end of an area. This might
5220 help debug some conceivable causes of bug 930.
5221 - Time and memory units in the configuration file can now be set to
5222 fractional units. For example, "2.5 GB" is now a valid value for
5224 - Certain Tor clients (such as those behind check.torproject.org) may
5225 want to fetch the consensus in an extra early manner. To enable this
5226 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
5227 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
5228 as only certain clients who must have this information sooner should
5230 - Instead of adding the svn revision to the Tor version string, report
5231 the git commit (when we're building from a git checkout).
5234 - If any of the v3 certs we download are unparseable, we should
5235 actually notice the failure so we don't retry indefinitely. Bugfix
5236 on 0.2.0.x; reported by "rotator".
5237 - If the cached cert file is unparseable, warn but don't exit.
5238 - Fix possible segmentation fault on directory authorities. Bugfix on
5240 - When Tor fails to parse a descriptor of any kind, dump it to disk.
5241 Might help diagnosing bug 1051.
5243 o Deprecated and removed features:
5244 - The controller no longer accepts the old obsolete "addr-mappings/"
5245 or "unregistered-servers-" GETINFO values.
5246 - Hidden services no longer publish version 0 descriptors, and clients
5247 do not request or use version 0 descriptors. However, the old hidden
5248 service authorities still accept and serve version 0 descriptors
5249 when contacted by older hidden services/clients.
5250 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
5251 always on; using them is necessary for correct forward-compatible
5253 - Remove support for .noconnect style addresses. Nobody was using
5254 them, and they provided another avenue for detecting Tor users
5255 via application-level web tricks.
5257 o Packaging changes:
5258 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
5259 installer bundles. See
5260 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
5261 for details of what's new in Vidalia 0.2.3.
5262 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
5263 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
5264 configuration file, rather than the old Privoxy.
5265 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
5266 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
5267 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
5268 better compatibility with OS X 10.6, aka Snow Leopard.
5269 - OS X Vidalia Bundle: The multi-package installer is now replaced
5270 by a simple drag and drop to the /Applications folder. This change
5271 occurred with the upgrade to Vidalia 0.2.3.
5274 Changes in version 0.2.1.19 - 2009-07-28
5275 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
5276 services on Tor 0.2.1.3-alpha through 0.2.1.18.
5279 - Make accessing hidden services on 0.2.1.x work right again.
5280 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
5281 part of patch provided by "optimist".
5284 - When a relay/bridge is writing out its identity key fingerprint to
5285 the "fingerprint" file and to its logs, write it without spaces. Now
5286 it will look like the fingerprints in our bridges documentation,
5287 and confuse fewer users.
5290 - Relays no longer publish a new server descriptor if they change
5291 their MaxAdvertisedBandwidth config option but it doesn't end up
5292 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
5293 fixes bug 1026. Patch from Sebastian.
5294 - Avoid leaking memory every time we get a create cell but we have
5295 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
5296 fixes bug 1034. Reported by BarkerJr.
5299 Changes in version 0.2.1.18 - 2009-07-24
5300 Tor 0.2.1.18 lays the foundations for performance improvements,
5301 adds status events to help users diagnose bootstrap problems, adds
5302 optional authentication/authorization for hidden services, fixes a
5303 variety of potential anonymity problems, and includes a huge pile of
5304 other features and bug fixes.
5307 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
5310 Changes in version 0.2.1.17-rc - 2009-07-07
5311 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
5312 candidate for the 0.2.1.x series. It lays the groundwork for further
5313 client performance improvements, and also fixes a big bug with directory
5314 authorities that were causing them to assign Guard and Stable flags
5317 The Windows bundles also finally include the geoip database that we
5318 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
5319 should actually install Torbutton rather than giving you a cryptic
5320 failure message (oops).
5323 - Clients now use the bandwidth values in the consensus, rather than
5324 the bandwidth values in each relay descriptor. This approach opens
5325 the door to more accurate bandwidth estimates once the directory
5326 authorities start doing active measurements. Implements more of
5330 - When Tor clients restart after 1-5 days, they discard all their
5331 cached descriptors as too old, but they still use the cached
5332 consensus document. This approach is good for robustness, but
5333 bad for performance: since they don't know any bandwidths, they
5334 end up choosing at random rather than weighting their choice by
5335 speed. Fixed by the above feature of putting bandwidths in the
5336 consensus. Bugfix on 0.2.0.x.
5337 - Directory authorities were neglecting to mark relays down in their
5338 internal histories if the relays fall off the routerlist without
5339 ever being found unreachable. So there were relays in the histories
5340 that haven't been seen for eight months, and are listed as being
5341 up for eight months. This wreaked havoc on the "median wfu"
5342 and "median mtbf" calculations, in turn making Guard and Stable
5343 flags very wrong, hurting network performance. Fixes bugs 696 and
5344 969. Bugfix on 0.2.0.6-alpha.
5347 - Serve the DirPortFrontPage page even when we have been approaching
5348 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
5349 - The control port would close the connection before flushing long
5350 replies, such as the network consensus, if a QUIT command was issued
5351 before the reply had completed. Now, the control port flushes all
5352 pending replies before closing the connection. Also fixed a spurious
5353 warning when a QUIT command is issued after a malformed or rejected
5354 AUTHENTICATE command, but before the connection was closed. Patch
5355 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
5356 - When we can't find an intro key for a v2 hidden service descriptor,
5357 fall back to the v0 hidden service descriptor and log a bug message.
5358 Workaround for bug 1024.
5359 - Fix a log message that did not respect the SafeLogging option.
5363 - If we're a relay and we change our IP address, be more verbose
5364 about the reason that made us change. Should help track down
5365 further bugs for relays on dynamic IP addresses.
5368 Changes in version 0.2.0.35 - 2009-06-24
5370 - Avoid crashing in the presence of certain malformed descriptors.
5371 Found by lark, and by automated fuzzing.
5372 - Fix an edge case where a malicious exit relay could convince a
5373 controller that the client's DNS question resolves to an internal IP
5374 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5377 - Finally fix the bug where dynamic-IP relays disappear when their
5378 IP address changes: directory mirrors were mistakenly telling
5379 them their old address if they asked via begin_dir, so they
5380 never got an accurate answer about their new address, so they
5381 just vanished after a day. For belt-and-suspenders, relays that
5382 don't set Address in their config now avoid using begin_dir for
5383 all direct connections. Should fix bugs 827, 883, and 900.
5384 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5385 that would occur on some exit nodes when DNS failures and timeouts
5386 occurred in certain patterns. Fix for bug 957.
5389 - When starting with a cache over a few days old, do not leak
5390 memory for the obsolete router descriptors in it. Bugfix on
5391 0.2.0.33; fixes bug 672.
5392 - Hidden service clients didn't use a cached service descriptor that
5393 was older than 15 minutes, but wouldn't fetch a new one either,
5394 because there was already one in the cache. Now, fetch a v2
5395 descriptor unless the same descriptor was added to the cache within
5396 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5399 Changes in version 0.2.1.16-rc - 2009-06-20
5400 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
5401 a bunch of minor bugs.
5404 - Fix an edge case where a malicious exit relay could convince a
5405 controller that the client's DNS question resolves to an internal IP
5406 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5408 o Major performance improvements (on 0.2.0.x):
5409 - Disable and refactor some debugging checks that forced a linear scan
5410 over the whole server-side DNS cache. These accounted for over 50%
5411 of CPU time on a relatively busy exit node's gprof profile. Found
5413 - Disable some debugging checks that appeared in exit node profile
5417 - Update to the "June 3 2009" ip-to-country file.
5418 - Do not have tor-resolve automatically refuse all .onion addresses;
5419 if AutomapHostsOnResolve is set in your torrc, this will work fine.
5421 o Minor bugfixes (on 0.2.0.x):
5422 - Log correct error messages for DNS-related network errors on
5424 - Fix a race condition that could cause crashes or memory corruption
5425 when running as a server with a controller listening for log
5427 - Avoid crashing when we have a policy specified in a DirPolicy or
5428 SocksPolicy or ReachableAddresses option with ports set on it,
5429 and we re-load the policy. May fix bug 996.
5430 - Hidden service clients didn't use a cached service descriptor that
5431 was older than 15 minutes, but wouldn't fetch a new one either,
5432 because there was already one in the cache. Now, fetch a v2
5433 descriptor unless the same descriptor was added to the cache within
5434 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5436 o Minor bugfixes (on 0.2.1.x):
5437 - Don't warn users about low port and hibernation mix when they
5438 provide a *ListenAddress directive to fix that. Bugfix on
5440 - When switching back and forth between bridge mode, do not start
5441 gathering GeoIP data until two hours have passed.
5442 - Do not complain that the user has requested an excluded node as
5443 an exit when the node is not really an exit. This could happen
5444 because the circuit was for testing, or an introduction point.
5448 Changes in version 0.2.1.15-rc - 2009-05-25
5449 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
5450 series. It fixes a major bug on fast exit relays, as well as a variety
5453 o Major bugfixes (on 0.2.0.x):
5454 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5455 that would occur on some exit nodes when DNS failures and timeouts
5456 occurred in certain patterns. Fix for bug 957.
5458 o Minor bugfixes (on 0.2.0.x):
5459 - Actually return -1 in the error case for read_bandwidth_usage().
5460 Harmless bug, since we currently don't care about the return value
5461 anywhere. Bugfix on 0.2.0.9-alpha.
5462 - Provide a more useful log message if bug 977 (related to buffer
5463 freelists) ever reappears, and do not crash right away.
5464 - Fix an assertion failure on 64-bit platforms when we allocated
5465 memory right up to the end of a memarea, then realigned the memory
5466 one step beyond the end. Fixes a possible cause of bug 930.
5467 - Protect the count of open sockets with a mutex, so we can't
5468 corrupt it when two threads are closing or opening sockets at once.
5469 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
5470 - Don't allow a bridge to publish its router descriptor to a
5471 non-bridge directory authority. Fixes part of bug 932.
5472 - When we change to or from being a bridge, reset our counts of
5473 client usage by country. Fixes bug 932.
5474 - Fix a bug that made stream bandwidth get misreported to the
5476 - Stop using malloc_usable_size() to use more area than we had
5477 actually allocated: it was safe, but made valgrind really unhappy.
5478 - Fix a memory leak when v3 directory authorities load their keys
5479 and cert from disk. Bugfix on 0.2.0.1-alpha.
5481 o Minor bugfixes (on 0.2.1.x):
5482 - Fix use of freed memory when deciding to mark a non-addable
5483 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
5486 Changes in version 0.2.1.14-rc - 2009-04-12
5487 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
5488 series. It begins fixing some major performance problems, and also
5489 finally addresses the bug that was causing relays on dynamic IP
5490 addresses to fall out of the directory.
5493 - Clients replace entry guards that were chosen more than a few months
5494 ago. This change should significantly improve client performance,
5495 especially once more people upgrade, since relays that have been
5496 a guard for a long time are currently overloaded.
5498 o Major bugfixes (on 0.2.0):
5499 - Finally fix the bug where dynamic-IP relays disappear when their
5500 IP address changes: directory mirrors were mistakenly telling
5501 them their old address if they asked via begin_dir, so they
5502 never got an accurate answer about their new address, so they
5503 just vanished after a day. For belt-and-suspenders, relays that
5504 don't set Address in their config now avoid using begin_dir for
5505 all direct connections. Should fix bugs 827, 883, and 900.
5506 - Relays were falling out of the networkstatus consensus for
5507 part of a day if they changed their local config but the
5508 authorities discarded their new descriptor as "not sufficiently
5509 different". Now directory authorities accept a descriptor as changed
5510 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
5512 - Avoid crashing in the presence of certain malformed descriptors.
5513 Found by lark, and by automated fuzzing.
5516 - When generating circuit events with verbose nicknames for
5517 controllers, try harder to look up nicknames for routers on a
5518 circuit. (Previously, we would look in the router descriptors we had
5519 for nicknames, but not in the consensus.) Partial fix for bug 941.
5520 - If the bridge config line doesn't specify a port, assume 443.
5521 This makes bridge lines a bit smaller and easier for users to
5523 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
5524 bytes (aka 20KB/s), to match our documentation. Also update
5525 directory authorities so they always assign the Fast flag to relays
5526 with 20KB/s of capacity. Now people running relays won't suddenly
5527 find themselves not seeing any use, if the network gets faster
5529 - Update to the "April 3 2009" ip-to-country file.
5532 - Avoid trying to print raw memory to the logs when we decide to
5533 give up on downloading a given relay descriptor. Bugfix on
5535 - In tor-resolve, when the Tor client to use is specified by
5536 <hostname>:<port>, actually use the specified port rather than
5537 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
5538 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
5539 - When starting with a cache over a few days old, do not leak
5540 memory for the obsolete router descriptors in it. Bugfix on
5542 - Avoid double-free on list of successfully uploaded hidden
5543 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
5544 - Change memarea_strndup() implementation to work even when
5545 duplicating a string at the end of a page. This bug was
5546 harmless for now, but could have meant crashes later. Fix by
5547 lark. Bugfix on 0.2.1.1-alpha.
5548 - Limit uploaded directory documents to be 16M rather than 500K.
5549 The directory authorities were refusing v3 consensus votes from
5550 other authorities, since the votes are now 504K. Fixes bug 959;
5551 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
5552 - Directory authorities should never send a 503 "busy" response to
5553 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
5557 Changes in version 0.2.1.13-alpha - 2009-03-09
5558 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
5559 cleanups. We're finally getting close to a release candidate.
5562 - Correctly update the list of which countries we exclude as
5563 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
5564 lark. Bugfix on 0.2.1.6-alpha.
5566 o Minor bugfixes (on 0.2.0.x and earlier):
5567 - Automatically detect MacOSX versions earlier than 10.4.0, and
5568 disable kqueue from inside Tor when running with these versions.
5569 We previously did this from the startup script, but that was no
5570 help to people who didn't use the startup script. Resolves bug 863.
5571 - When we had picked an exit node for a connection, but marked it as
5572 "optional", and it turned out we had no onion key for the exit,
5573 stop wanting that exit and try again. This situation may not
5574 be possible now, but will probably become feasible with proposal
5575 158. Spotted by rovv. Fixes another case of bug 752.
5576 - Clients no longer cache certificates for authorities they do not
5577 recognize. Bugfix on 0.2.0.9-alpha.
5578 - When we can't transmit a DNS request due to a network error, retry
5579 it after a while, and eventually transmit a failing response to
5580 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
5581 - If the controller claimed responsibility for a stream, but that
5582 stream never finished making its connection, it would live
5583 forever in circuit_wait state. Now we close it after SocksTimeout
5584 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
5585 - Drop begin cells to a hidden service if they come from the middle
5586 of a circuit. Patch from lark.
5587 - When we erroneously receive two EXTEND cells for the same circuit
5588 ID on the same connection, drop the second. Patch from lark.
5589 - Fix a crash that occurs on exit nodes when a nameserver request
5590 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
5591 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
5593 - Do not assume that a stack-allocated character array will be
5594 64-bit aligned on platforms that demand that uint64_t access is
5595 aligned. Possible fix for bug 604.
5596 - Parse dates and IPv4 addresses in a locale- and libc-independent
5597 manner, to avoid platform-dependent behavior on malformed input.
5598 - Build correctly when configured to build outside the main source
5599 path. Patch from Michael Gold.
5600 - We were already rejecting relay begin cells with destination port
5601 of 0. Now also reject extend cells with destination port or address
5602 of 0. Suggested by lark.
5604 o Minor bugfixes (on 0.2.1.x):
5605 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
5606 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
5607 - If we're an exit node, scrub the IP address to which we are exiting
5608 in the logs. Bugfix on 0.2.1.8-alpha.
5611 - On Linux, use the prctl call to re-enable core dumps when the user
5613 - New controller event NEWCONSENSUS that lists the networkstatus
5614 lines for every recommended relay. Now controllers like Torflow
5615 can keep up-to-date on which relays they should be using.
5616 - Update to the "February 26 2009" ip-to-country file.
5619 Changes in version 0.2.0.34 - 2009-02-08
5620 Tor 0.2.0.34 features several more security-related fixes. You should
5621 upgrade, especially if you run an exit relay (remote crash) or a
5622 directory authority (remote infinite loop), or you're on an older
5623 (pre-XP) or not-recently-patched Windows (remote exploit).
5625 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
5626 have many known flaws, and nobody should be using them. You should
5627 upgrade. If you're using a Linux or BSD and its packages are obsolete,
5628 stop using those packages and upgrade anyway.
5631 - Fix an infinite-loop bug on handling corrupt votes under certain
5632 circumstances. Bugfix on 0.2.0.8-alpha.
5633 - Fix a temporary DoS vulnerability that could be performed by
5634 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5635 - Avoid a potential crash on exit nodes when processing malformed
5636 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
5637 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
5638 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
5641 - Fix compilation on systems where time_t is a 64-bit integer.
5642 Patch from Matthias Drochner.
5643 - Don't consider expiring already-closed client connections. Fixes
5644 bug 893. Bugfix on 0.0.2pre20.
5647 Changes in version 0.2.1.12-alpha - 2009-02-08
5648 Tor 0.2.1.12-alpha features several more security-related fixes. You
5649 should upgrade, especially if you run an exit relay (remote crash) or
5650 a directory authority (remote infinite loop), or you're on an older
5651 (pre-XP) or not-recently-patched Windows (remote exploit). It also
5652 includes a big pile of minor bugfixes and cleanups.
5655 - Fix an infinite-loop bug on handling corrupt votes under certain
5656 circumstances. Bugfix on 0.2.0.8-alpha.
5657 - Fix a temporary DoS vulnerability that could be performed by
5658 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5659 - Avoid a potential crash on exit nodes when processing malformed
5660 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
5663 - Let controllers actually ask for the "clients_seen" event for
5664 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
5665 reported by Matt Edman.
5666 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
5668 - Fix a bug in address parsing that was preventing bridges or hidden
5669 service targets from being at IPv6 addresses.
5670 - Solve a bug that kept hardware crypto acceleration from getting
5671 enabled when accounting was turned on. Fixes bug 907. Bugfix on
5673 - Remove a bash-ism from configure.in to build properly on non-Linux
5674 platforms. Bugfix on 0.2.1.1-alpha.
5675 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
5676 headers. Bugfix on 0.2.0.10-alpha.
5677 - Don't consider expiring already-closed client connections. Fixes
5678 bug 893. Bugfix on 0.0.2pre20.
5679 - Fix another interesting corner-case of bug 891 spotted by rovv:
5680 Previously, if two hosts had different amounts of clock drift, and
5681 one of them created a new connection with just the wrong timing,
5682 the other might decide to deprecate the new connection erroneously.
5683 Bugfix on 0.1.1.13-alpha.
5684 - Resolve a very rare crash bug that could occur when the user forced
5685 a nameserver reconfiguration during the middle of a nameserver
5686 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
5687 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
5688 Bugfix on 0.2.1.7-alpha.
5689 - If we're using bridges and our network goes away, be more willing
5690 to forgive our bridges and try again when we get an application
5691 request. Bugfix on 0.2.0.x.
5694 - Support platforms where time_t is 64 bits long. (Congratulations,
5695 NetBSD!) Patch from Matthias Drochner.
5696 - Add a 'getinfo status/clients-seen' controller command, in case
5697 controllers want to hear clients_seen events but connect late.
5700 - Disable GCC's strict alias optimization by default, to avoid the
5701 likelihood of its introducing subtle bugs whenever our code violates
5702 the letter of C99's alias rules.
5705 Changes in version 0.2.0.33 - 2009-01-21
5706 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
5707 useful to users. It also finally fixes a bug where a relay or client
5708 that's been off for many days would take a long time to bootstrap.
5710 This update also fixes an important security-related bug reported by
5711 Ilja van Sprundel. You should upgrade. (We'll send out more details
5712 about the bug once people have had some time to upgrade.)
5715 - Fix a heap-corruption bug that may be remotely triggerable on
5716 some platforms. Reported by Ilja van Sprundel.
5719 - When a stream at an exit relay is in state "resolving" or
5720 "connecting" and it receives an "end" relay cell, the exit relay
5721 would silently ignore the end cell and not close the stream. If
5722 the client never closes the circuit, then the exit relay never
5723 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
5725 - When sending CREATED cells back for a given circuit, use a 64-bit
5726 connection ID to find the right connection, rather than an addr:port
5727 combination. Now that we can have multiple OR connections between
5728 the same ORs, it is no longer possible to use addr:port to uniquely
5729 identify a connection.
5730 - Bridge relays that had DirPort set to 0 would stop fetching
5731 descriptors shortly after startup, and then briefly resume
5732 after a new bandwidth test and/or after publishing a new bridge
5733 descriptor. Bridge users that try to bootstrap from them would
5734 get a recent networkstatus but would get descriptors from up to
5735 18 hours earlier, meaning most of the descriptors were obsolete
5736 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
5737 - Prevent bridge relays from serving their 'extrainfo' document
5738 to anybody who asks, now that extrainfo docs include potentially
5739 sensitive aggregated client geoip summaries. Bugfix on
5741 - If the cached networkstatus consensus is more than five days old,
5742 discard it rather than trying to use it. In theory it could be
5743 useful because it lists alternate directory mirrors, but in practice
5744 it just means we spend many minutes trying directory mirrors that
5745 are long gone from the network. Also discard router descriptors as
5746 we load them if they are more than five days old, since the onion
5747 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
5750 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
5751 could make gcc generate non-functional binary search code. Bugfix
5753 - Build correctly on platforms without socklen_t.
5754 - Compile without warnings on solaris.
5755 - Avoid potential crash on internal error during signature collection.
5756 Fixes bug 864. Patch from rovv.
5757 - Correct handling of possible malformed authority signing key
5758 certificates with internal signature types. Fixes bug 880.
5759 Bugfix on 0.2.0.3-alpha.
5760 - Fix a hard-to-trigger resource leak when logging credential status.
5762 - When we can't initialize DNS because the network is down, do not
5763 automatically stop Tor from starting. Instead, we retry failed
5764 dns_init() every 10 minutes, and change the exit policy to reject
5765 *:* until one succeeds. Fixes bug 691.
5766 - Use 64 bits instead of 32 bits for connection identifiers used with
5767 the controller protocol, to greatly reduce risk of identifier reuse.
5768 - When we're choosing an exit node for a circuit, and we have
5769 no pending streams, choose a good general exit rather than one that
5770 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
5771 - Fix another case of assuming, when a specific exit is requested,
5772 that we know more than the user about what hosts it allows.
5773 Fixes one case of bug 752. Patch from rovv.
5774 - Clip the MaxCircuitDirtiness config option to a minimum of 10
5775 seconds. Warn the user if lower values are given in the
5776 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
5777 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
5778 user if lower values are given in the configuration. Bugfix on
5779 0.1.1.17-rc. Patch by Sebastian.
5780 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
5781 the cache because we already had a v0 descriptor with the same ID.
5782 Bugfix on 0.2.0.18-alpha.
5783 - Fix a race condition when freeing keys shared between main thread
5784 and CPU workers that could result in a memory leak. Bugfix on
5785 0.1.0.1-rc. Fixes bug 889.
5786 - Send a valid END cell back when a client tries to connect to a
5787 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
5788 840. Patch from rovv.
5789 - Check which hops rendezvous stream cells are associated with to
5790 prevent possible guess-the-streamid injection attacks from
5791 intermediate hops. Fixes another case of bug 446. Based on patch
5793 - If a broken client asks a non-exit router to connect somewhere,
5794 do not even do the DNS lookup before rejecting the connection.
5795 Fixes another case of bug 619. Patch from rovv.
5796 - When a relay gets a create cell it can't decrypt (e.g. because it's
5797 using the wrong onion key), we were dropping it and letting the
5798 client time out. Now actually answer with a destroy cell. Fixes
5799 bug 904. Bugfix on 0.0.2pre8.
5801 o Minor bugfixes (hidden services):
5802 - Do not throw away existing introduction points on SIGHUP. Bugfix on
5803 0.0.6pre1. Patch by Karsten. Fixes bug 874.
5806 - Report the case where all signatures in a detached set are rejected
5807 differently than the case where there is an error handling the
5809 - When we realize that another process has modified our cached
5810 descriptors, print out a more useful error message rather than
5811 triggering an assertion. Fixes bug 885. Patch from Karsten.
5812 - Implement the 0x20 hack to better resist DNS poisoning: set the
5813 case on outgoing DNS requests randomly, and reject responses that do
5814 not match the case correctly. This logic can be disabled with the
5815 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
5816 of servers that do not reliably preserve case in replies. See
5817 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
5819 - Check DNS replies for more matching fields to better resist DNS
5821 - Never use OpenSSL compression: it wastes RAM and CPU trying to
5822 compress cells, which are basically all encrypted, compressed, or
5826 Changes in version 0.2.1.11-alpha - 2009-01-20
5827 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
5828 week it will take a long time to bootstrap again" bug. It also fixes
5829 an important security-related bug reported by Ilja van Sprundel. You
5830 should upgrade. (We'll send out more details about the bug once people
5831 have had some time to upgrade.)
5834 - Fix a heap-corruption bug that may be remotely triggerable on
5835 some platforms. Reported by Ilja van Sprundel.
5838 - Discard router descriptors as we load them if they are more than
5839 five days old. Otherwise if Tor is off for a long time and then
5840 starts with cached descriptors, it will try to use the onion
5841 keys in those obsolete descriptors when building circuits. Bugfix
5842 on 0.2.0.x. Fixes bug 887.
5845 - Try to make sure that the version of Libevent we're running with
5846 is binary-compatible with the one we built with. May address bug
5848 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
5849 for bug 905. Bugfix on 0.2.1.7-alpha.
5850 - Add a new --enable-local-appdata configuration switch to change
5851 the default location of the datadir on win32 from APPDATA to
5852 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
5853 entirely. Patch from coderman.
5856 - Make outbound DNS packets respect the OutboundBindAddress setting.
5857 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
5858 - When our circuit fails at the first hop (e.g. we get a destroy
5859 cell back), avoid using that OR connection anymore, and also
5860 tell all the one-hop directory requests waiting for it that they
5861 should fail. Bugfix on 0.2.1.3-alpha.
5862 - In the torify(1) manpage, mention that tsocks will leak your
5866 Changes in version 0.2.1.10-alpha - 2009-01-06
5867 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
5868 would make the bridge relay not so useful if it had DirPort set to 0,
5869 and one that could let an attacker learn a little bit of information
5870 about the bridge's users), and a bug that would cause your Tor relay
5871 to ignore a circuit create request it can't decrypt (rather than reply
5872 with an error). It also fixes a wide variety of other bugs.
5875 - If the cached networkstatus consensus is more than five days old,
5876 discard it rather than trying to use it. In theory it could
5877 be useful because it lists alternate directory mirrors, but in
5878 practice it just means we spend many minutes trying directory
5879 mirrors that are long gone from the network. Helps bug 887 a bit;
5881 - Bridge relays that had DirPort set to 0 would stop fetching
5882 descriptors shortly after startup, and then briefly resume
5883 after a new bandwidth test and/or after publishing a new bridge
5884 descriptor. Bridge users that try to bootstrap from them would
5885 get a recent networkstatus but would get descriptors from up to
5886 18 hours earlier, meaning most of the descriptors were obsolete
5887 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
5888 - Prevent bridge relays from serving their 'extrainfo' document
5889 to anybody who asks, now that extrainfo docs include potentially
5890 sensitive aggregated client geoip summaries. Bugfix on
5894 - New controller event "clients_seen" to report a geoip-based summary
5895 of which countries we've seen clients from recently. Now controllers
5896 like Vidalia can show bridge operators that they're actually making
5898 - Build correctly against versions of OpenSSL 0.9.8 or later built
5899 without support for deprecated functions.
5900 - Update to the "December 19 2008" ip-to-country file.
5902 o Minor bugfixes (on 0.2.0.x):
5903 - Authorities now vote for the Stable flag for any router whose
5904 weighted MTBF is at least 5 days, regardless of the mean MTBF.
5905 - Do not remove routers as too old if we do not have any consensus
5906 document. Bugfix on 0.2.0.7-alpha.
5907 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
5908 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
5909 - When an exit relay resolves a stream address to a local IP address,
5910 do not just keep retrying that same exit relay over and
5911 over. Instead, just close the stream. Addresses bug 872. Bugfix
5912 on 0.2.0.32. Patch from rovv.
5913 - If a hidden service sends us an END cell, do not consider
5914 retrying the connection; just close it. Patch from rovv.
5915 - When we made bridge authorities stop serving bridge descriptors over
5916 unencrypted links, we also broke DirPort reachability testing for
5917 bridges. So bridges with a non-zero DirPort were printing spurious
5918 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
5919 - When a relay gets a create cell it can't decrypt (e.g. because it's
5920 using the wrong onion key), we were dropping it and letting the
5921 client time out. Now actually answer with a destroy cell. Fixes
5922 bug 904. Bugfix on 0.0.2pre8.
5923 - Squeeze 2-5% out of client performance (according to oprofile) by
5924 improving the implementation of some policy-manipulation functions.
5926 o Minor bugfixes (on 0.2.1.x):
5927 - Make get_interface_address() function work properly again; stop
5928 guessing the wrong parts of our address as our address.
5929 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
5930 send on that circuit. Otherwise we might violate the proposal-110
5931 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
5933 - When we're sending non-EXTEND cells to the first hop in a circuit,
5934 for example to use an encrypted directory connection, we don't need
5935 to use RELAY_EARLY cells: the first hop knows what kind of cell
5936 it is, and nobody else can even see the cell type. Conserving
5937 RELAY_EARLY cells makes it easier to cannibalize circuits like
5939 - Stop logging nameserver addresses in reverse order.
5940 - If we are retrying a directory download slowly over and over, do
5941 not automatically give up after the 254th failure. Bugfix on
5943 - Resume reporting accurate "stream end" reasons to the local control
5944 port. They were lost in the changes for Proposal 148. Bugfix on
5947 o Deprecated and removed features:
5948 - The old "tor --version --version" command, which would print out
5949 the subversion "Id" of most of the source files, is now removed. It
5950 turned out to be less useful than we'd expected, and harder to
5953 o Code simplifications and refactoring:
5954 - Change our header file guard macros to be less likely to conflict
5955 with system headers. Adam Langley noticed that we were conflicting
5956 with log.h on Android.
5957 - Tool-assisted documentation cleanup. Nearly every function or
5958 static variable in Tor should have its own documentation now.
5961 Changes in version 0.2.1.9-alpha - 2008-12-25
5962 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
5964 o New directory authorities:
5965 - gabelmoo (the authority run by Karsten Loesing) now has a new
5969 - Never use a connection with a mismatched address to extend a
5970 circuit, unless that connection is canonical. A canonical
5971 connection is one whose address is authenticated by the router's
5972 identity key, either in a NETINFO cell or in a router descriptor.
5973 - Avoid a possible memory corruption bug when receiving hidden service
5974 descriptors. Bugfix on 0.2.1.6-alpha.
5977 - Fix a logic error that would automatically reject all but the first
5978 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
5979 part of bug 813/868. Bug spotted by coderman.
5980 - When a stream at an exit relay is in state "resolving" or
5981 "connecting" and it receives an "end" relay cell, the exit relay
5982 would silently ignore the end cell and not close the stream. If
5983 the client never closes the circuit, then the exit relay never
5984 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
5986 - When we can't initialize DNS because the network is down, do not
5987 automatically stop Tor from starting. Instead, retry failed
5988 dns_init() every 10 minutes, and change the exit policy to reject
5989 *:* until one succeeds. Fixes bug 691.
5992 - Give a better error message when an overzealous init script says
5993 "sudo -u username tor --user username". Makes Bug 882 easier for
5995 - When a directory authority gives us a new guess for our IP address,
5996 log which authority we used. Hopefully this will help us debug
5997 the recent complaints about bad IP address guesses.
5998 - Detect svn revision properly when we're using git-svn.
5999 - Try not to open more than one descriptor-downloading connection
6000 to an authority at once. This should reduce load on directory
6001 authorities. Fixes bug 366.
6002 - Add cross-certification to newly generated certificates, so that
6003 a signing key is enough information to look up a certificate.
6004 Partial implementation of proposal 157.
6005 - Start serving certificates by <identity digest, signing key digest>
6006 pairs. Partial implementation of proposal 157.
6007 - Clients now never report any stream end reason except 'MISC'.
6008 Implements proposal 148.
6009 - On platforms with a maximum syslog string length, truncate syslog
6010 messages to that length ourselves, rather than relying on the
6011 system to do it for us.
6012 - Optimize out calls to time(NULL) that occur for every IO operation,
6013 or for every cell. On systems where time() is a slow syscall,
6014 this fix will be slightly helpful.
6015 - Exit servers can now answer resolve requests for ip6.arpa addresses.
6016 - When we download a descriptor that we then immediately (as
6017 a directory authority) reject, do not retry downloading it right
6018 away. Should save some bandwidth on authorities. Fix for bug
6019 888. Patch by Sebastian Hahn.
6020 - When a download gets us zero good descriptors, do not notify
6021 Tor that new directory information has arrived.
6022 - Avoid some nasty corner cases in the logic for marking connections
6023 as too old or obsolete or noncanonical for circuits. Partial
6026 o Minor features (controller):
6027 - New CONSENSUS_ARRIVED event to note when a new consensus has
6028 been fetched and validated.
6029 - When we realize that another process has modified our cached
6030 descriptors file, print out a more useful error message rather
6031 than triggering an assertion. Fixes bug 885. Patch from Karsten.
6032 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
6033 controllers to prevent SIGHUP from reloading the
6034 configuration. Fixes bug 856.
6037 - Resume using the correct "REASON=" stream when telling the
6038 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
6039 - When a canonical connection appears later in our internal list
6040 than a noncanonical one for a given OR ID, always use the
6041 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
6043 - Clip the MaxCircuitDirtiness config option to a minimum of 10
6044 seconds. Warn the user if lower values are given in the
6045 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
6046 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
6047 user if lower values are given in the configuration. Bugfix on
6048 0.1.1.17-rc. Patch by Sebastian.
6049 - Fix a race condition when freeing keys shared between main thread
6050 and CPU workers that could result in a memory leak. Bugfix on
6051 0.1.0.1-rc. Fixes bug 889.
6053 o Minor bugfixes (hidden services):
6054 - Do not throw away existing introduction points on SIGHUP (bugfix on
6055 0.0.6pre1); also, do not stall hidden services because we're
6056 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
6057 by John Brooks. Patch by Karsten. Fixes bug 874.
6058 - Fix a memory leak when we decline to add a v2 rendezvous
6059 descriptor to the cache because we already had a v0 descriptor
6060 with the same ID. Bugfix on 0.2.0.18-alpha.
6062 o Deprecated and removed features:
6063 - RedirectExits has been removed. It was deprecated since
6065 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
6066 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
6067 - Cell pools are now always enabled; --disable-cell-pools is ignored.
6069 o Code simplifications and refactoring:
6070 - Rename the confusing or_is_obsolete field to the more appropriate
6071 is_bad_for_new_circs, and move it to or_connection_t where it
6073 - Move edge-only flags from connection_t to edge_connection_t: not
6074 only is this better coding, but on machines of plausible alignment,
6075 it should save 4-8 bytes per connection_t. "Every little bit helps."
6076 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
6077 for consistency; keep old option working for backward compatibility.
6078 - Simplify the code for finding connections to use for a circuit.
6081 Changes in version 0.2.1.8-alpha - 2008-12-08
6082 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
6083 builds better on unusual platforms like Solaris and old OS X, and
6084 fixes a variety of other issues.
6087 - New DirPortFrontPage option that takes an html file and publishes
6088 it as "/" on the DirPort. Now relay operators can provide a
6089 disclaimer without needing to set up a separate webserver. There's
6090 a sample disclaimer in contrib/tor-exit-notice.html.
6093 - When the client is choosing entry guards, now it selects at most
6094 one guard from a given relay family. Otherwise we could end up with
6095 all of our entry points into the network run by the same operator.
6096 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
6099 - Fix a DOS opportunity during the voting signature collection process
6100 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6101 - Fix a possible segfault when establishing an exit connection. Bugfix
6105 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
6107 - Made Tor a little less aggressive about deleting expired
6108 certificates. Partial fix for bug 854.
6109 - Stop doing unaligned memory access that generated bus errors on
6110 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
6111 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
6112 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
6113 - Make USR2 log-level switch take effect immediately. Bugfix on
6115 - If one win32 nameserver fails to get added, continue adding the
6116 rest, and don't automatically fail.
6117 - Use fcntl() for locking when flock() is not available. Should fix
6118 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
6119 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6120 could make gcc generate non-functional binary search code. Bugfix
6122 - Build correctly on platforms without socklen_t.
6123 - Avoid potential crash on internal error during signature collection.
6124 Fixes bug 864. Patch from rovv.
6125 - Do not use C's stdio library for writing to log files. This will
6126 improve logging performance by a minute amount, and will stop
6127 leaking fds when our disk is full. Fixes bug 861.
6128 - Stop erroneous use of O_APPEND in cases where we did not in fact
6129 want to re-seek to the end of a file before every last write().
6130 - Correct handling of possible malformed authority signing key
6131 certificates with internal signature types. Fixes bug 880. Bugfix
6133 - Fix a hard-to-trigger resource leak when logging credential status.
6137 - Directory mirrors no longer fetch the v1 directory or
6138 running-routers files. They are obsolete, and nobody asks for them
6139 anymore. This is the first step to making v1 authorities obsolete.
6141 o Minor features (controller):
6142 - Return circuit purposes in response to GETINFO circuit-status. Fixes
6146 Changes in version 0.2.0.32 - 2008-11-20
6147 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
6148 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6149 a smaller security flaw that might allow an attacker to access local
6150 services, further improves hidden service performance, and fixes a
6151 variety of other issues.
6154 - The "User" and "Group" config options did not clear the
6155 supplementary group entries for the Tor process. The "User" option
6156 is now more robust, and we now set the groups to the specified
6157 user's primary group. The "Group" option is now ignored. For more
6158 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6159 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6160 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
6161 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6162 consistently obeyed: if an exit relay refuses a stream because its
6163 exit policy doesn't allow it, we would remember what IP address
6164 the relay said the destination address resolves to, even if it's
6165 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6168 - Fix a DOS opportunity during the voting signature collection process
6169 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6171 o Major bugfixes (hidden services):
6172 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6173 we were failing the whole hidden service request when the v0
6174 descriptor fetch fails, even if the v2 fetch is still pending and
6175 might succeed. Similarly, if the last v2 fetch fails, we were
6176 failing the whole hidden service request even if a v0 fetch is
6177 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6178 - When extending a circuit to a hidden service directory to upload a
6179 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6180 requests failed, because the router descriptor has not been
6181 downloaded yet. In these cases, do not attempt to upload the
6182 rendezvous descriptor, but wait until the router descriptor is
6183 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
6184 descriptor from a hidden service directory for which the router
6185 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
6189 - Fix several infrequent memory leaks spotted by Coverity.
6190 - When testing for libevent functions, set the LDFLAGS variable
6191 correctly. Found by Riastradh.
6192 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6193 bootstrapping with tunneled directory connections. Bugfix on
6194 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6195 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6196 and we know that server B rejects most-but-not all connections to
6197 port 80, we would previously reject the connection. Now, we assume
6198 the user knows what they were asking for. Fixes bug 752. Bugfix
6199 on 0.0.9rc5. Diagnosed by BarkerJr.
6200 - If we overrun our per-second write limits a little, count this as
6201 having used up our write allocation for the second, and choke
6202 outgoing directory writes. Previously, we had only counted this when
6203 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
6204 Bugfix on 0.2.0.x (??).
6205 - Remove the old v2 directory authority 'lefkada' from the default
6206 list. It has been gone for many months.
6207 - Stop doing unaligned memory access that generated bus errors on
6208 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
6209 - Make USR2 log-level switch take effect immediately. Bugfix on
6212 o Minor bugfixes (controller):
6213 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
6214 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
6217 Changes in version 0.2.1.7-alpha - 2008-11-08
6218 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
6219 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6220 a smaller security flaw that might allow an attacker to access local
6221 services, adds better defense against DNS poisoning attacks on exit
6222 relays, further improves hidden service performance, and fixes a
6223 variety of other issues.
6226 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6227 consistently obeyed: if an exit relay refuses a stream because its
6228 exit policy doesn't allow it, we would remember what IP address
6229 the relay said the destination address resolves to, even if it's
6230 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6231 - The "User" and "Group" config options did not clear the
6232 supplementary group entries for the Tor process. The "User" option
6233 is now more robust, and we now set the groups to the specified
6234 user's primary group. The "Group" option is now ignored. For more
6235 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6236 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6237 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
6238 - Do not use or believe expired v3 authority certificates. Patch
6239 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
6242 - Now NodeFamily and MyFamily config options allow spaces in
6243 identity fingerprints, so it's easier to paste them in.
6244 Suggested by Lucky Green.
6245 - Implement the 0x20 hack to better resist DNS poisoning: set the
6246 case on outgoing DNS requests randomly, and reject responses that do
6247 not match the case correctly. This logic can be disabled with the
6248 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
6249 of servers that do not reliably preserve case in replies. See
6250 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
6252 - Preserve case in replies to DNSPort requests in order to support
6253 the 0x20 hack for resisting DNS poisoning attacks.
6255 o Hidden service performance improvements:
6256 - When the client launches an introduction circuit, retry with a
6257 new circuit after 30 seconds rather than 60 seconds.
6258 - Launch a second client-side introduction circuit in parallel
6259 after a delay of 15 seconds (based on work by Christian Wilms).
6260 - Hidden services start out building five intro circuits rather
6261 than three, and when the first three finish they publish a service
6262 descriptor using those. Now we publish our service descriptor much
6263 faster after restart.
6266 - Minor fix in the warning messages when you're having problems
6267 bootstrapping; also, be more forgiving of bootstrap problems when
6268 we're still making incremental progress on a given bootstrap phase.
6269 - When we're choosing an exit node for a circuit, and we have
6270 no pending streams, choose a good general exit rather than one that
6271 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
6272 - Send a valid END cell back when a client tries to connect to a
6273 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
6274 840. Patch from rovv.
6275 - If a broken client asks a non-exit router to connect somewhere,
6276 do not even do the DNS lookup before rejecting the connection.
6277 Fixes another case of bug 619. Patch from rovv.
6278 - Fix another case of assuming, when a specific exit is requested,
6279 that we know more than the user about what hosts it allows.
6280 Fixes another case of bug 752. Patch from rovv.
6281 - Check which hops rendezvous stream cells are associated with to
6282 prevent possible guess-the-streamid injection attacks from
6283 intermediate hops. Fixes another case of bug 446. Based on patch
6285 - Avoid using a negative right-shift when comparing 32-bit
6286 addresses. Possible fix for bug 845 and bug 811.
6287 - Make the assert_circuit_ok() function work correctly on circuits that
6288 have already been marked for close.
6289 - Fix read-off-the-end-of-string error in unit tests when decoding
6290 introduction points.
6291 - Fix uninitialized size field for memory area allocation: may improve
6292 memory performance during directory parsing.
6293 - Treat duplicate certificate fetches as failures, so that we do
6294 not try to re-fetch an expired certificate over and over and over.
6295 - Do not say we're fetching a certificate when we'll in fact skip it
6296 because of a pending download.
6299 Changes in version 0.2.1.6-alpha - 2008-09-30
6300 Tor 0.2.1.6-alpha further improves performance and robustness of
6301 hidden services, starts work on supporting per-country relay selection,
6302 and fixes a variety of smaller issues.
6305 - Implement proposal 121: make it possible to build hidden services
6306 that only certain clients are allowed to connect to. This is
6307 enforced at several points, so that unauthorized clients are unable
6308 to send INTRODUCE cells to the service, or even (depending on the
6309 type of authentication) to learn introduction points. This feature
6310 raises the bar for certain kinds of active attacks against hidden
6311 services. Code by Karsten Loesing.
6312 - Relays now store and serve v2 hidden service descriptors by default,
6313 i.e., the new default value for HidServDirectoryV2 is 1. This is
6314 the last step in proposal 114, which aims to make hidden service
6315 lookups more reliable.
6316 - Start work to allow node restrictions to include country codes. The
6317 syntax to exclude nodes in a country with country code XX is
6318 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
6319 refinement to decide what config options should take priority if
6320 you ask to both use a particular node and exclude it.
6321 - Allow ExitNodes list to include IP ranges and country codes, just
6322 like the Exclude*Nodes lists. Patch from Robert Hogan.
6325 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
6326 Tor to fail to start if you had it configured to use a bridge
6327 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
6328 - When extending a circuit to a hidden service directory to upload a
6329 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6330 requests failed, because the router descriptor had not been
6331 downloaded yet. In these cases, we now wait until the router
6332 descriptor is downloaded, and then retry. Likewise, clients
6333 now skip over a hidden service directory if they don't yet have
6334 its router descriptor, rather than futilely requesting it and
6335 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
6337 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6338 we were failing the whole hidden service request when the v0
6339 descriptor fetch fails, even if the v2 fetch is still pending and
6340 might succeed. Similarly, if the last v2 fetch fails, we were
6341 failing the whole hidden service request even if a v0 fetch is
6342 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6343 - DNS replies need to have names matching their requests, but
6344 these names should be in the questions section, not necessarily
6345 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
6348 - Update to the "September 1 2008" ip-to-country file.
6349 - Allow ports 465 and 587 in the default exit policy again. We had
6350 rejected them in 0.1.0.15, because back in 2005 they were commonly
6351 misconfigured and ended up as spam targets. We hear they are better
6352 locked down these days.
6353 - Use a lockfile to make sure that two Tor processes are not
6354 simultaneously running with the same datadir.
6355 - Serve the latest v3 networkstatus consensus via the control
6356 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
6357 - Better logging about stability/reliability calculations on directory
6359 - Drop the requirement to have an open dir port for storing and
6360 serving v2 hidden service descriptors.
6361 - Directory authorities now serve a /tor/dbg-stability.txt URL to
6362 help debug WFU and MTBF calculations.
6363 - Implement most of Proposal 152: allow specialized servers to permit
6364 single-hop circuits, and clients to use those servers to build
6365 single-hop circuits when using a specialized controller. Patch
6366 from Josh Albrecht. Resolves feature request 768.
6367 - Add a -p option to tor-resolve for specifying the SOCKS port: some
6368 people find host:port too confusing.
6369 - Make TrackHostExit mappings expire a while after their last use, not
6370 after their creation. Patch from Robert Hogan.
6371 - Provide circuit purposes along with circuit events to the controller.
6374 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
6376 - Fixed some memory leaks -- some quite frequent, some almost
6377 impossible to trigger -- based on results from Coverity.
6378 - When testing for libevent functions, set the LDFLAGS variable
6379 correctly. Found by Riastradh.
6380 - Fix an assertion bug in parsing policy-related options; possible fix
6382 - Catch and report a few more bootstrapping failure cases when Tor
6383 fails to establish a TCP connection. Cleanup on 0.2.1.x.
6384 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6385 bootstrapping with tunneled directory connections. Bugfix on
6386 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6387 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6388 and we know that server B rejects most-but-not all connections to
6389 port 80, we would previously reject the connection. Now, we assume
6390 the user knows what they were asking for. Fixes bug 752. Bugfix
6391 on 0.0.9rc5. Diagnosed by BarkerJr.
6392 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
6393 service directories if they have no advertised dir port. Bugfix
6395 - If we overrun our per-second write limits a little, count this as
6396 having used up our write allocation for the second, and choke
6397 outgoing directory writes. Previously, we had only counted this when
6398 we had met our limits precisely. Fixes bug 824. Patch by rovv.
6399 Bugfix on 0.2.0.x (??).
6400 - Avoid a "0 divided by 0" calculation when calculating router uptime
6401 at directory authorities. Bugfix on 0.2.0.8-alpha.
6402 - Make DNS resolved controller events into "CLOSED", not
6403 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
6405 - Fix a bug where an unreachable relay would establish enough
6406 reachability testing circuits to do a bandwidth test -- if
6407 we already have a connection to the middle hop of the testing
6408 circuit, then it could establish the last hop by using the existing
6409 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
6410 circuits no longer use entry guards in 0.2.1.3-alpha.
6411 - If we have correct permissions on $datadir, we complain to stdout
6412 and fail to start. But dangerous permissions on
6413 $datadir/cached-status/ would cause us to open a log and complain
6414 there. Now complain to stdout and fail to start in both cases. Fixes
6415 bug 820, reported by seeess.
6416 - Remove the old v2 directory authority 'lefkada' from the default
6417 list. It has been gone for many months.
6419 o Code simplifications and refactoring:
6420 - Revise the connection_new functions so that a more typesafe variant
6421 exists. This will work better with Coverity, and let us find any
6422 actual mistakes we're making here.
6423 - Refactor unit testing logic so that dmalloc can be used sensibly
6424 with unit tests to check for memory leaks.
6425 - Move all hidden-service related fields from connection and circuit
6426 structure to substructures: this way they won't eat so much memory.
6429 Changes in version 0.2.0.31 - 2008-09-03
6430 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
6431 a big bug we're seeing where in rare cases traffic from one Tor stream
6432 gets mixed into another stream, and fixes a variety of smaller issues.
6435 - Make sure that two circuits can never exist on the same connection
6436 with the same circuit ID, even if one is marked for close. This
6437 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
6438 - Relays now reject risky extend cells: if the extend cell includes
6439 a digest of all zeroes, or asks to extend back to the relay that
6440 sent the extend cell, tear down the circuit. Ideas suggested
6442 - If not enough of our entry guards are available so we add a new
6443 one, we might use the new one even if it overlapped with the
6444 current circuit's exit relay (or its family). Anonymity bugfix
6445 pointed out by rovv.
6448 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6449 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6450 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6451 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6452 - Pick size of default geoip filename string correctly on windows.
6453 Fixes bug 806. Bugfix on 0.2.0.30.
6454 - Make the autoconf script accept the obsolete --with-ssl-dir
6455 option as an alias for the actually-working --with-openssl-dir
6456 option. Fix the help documentation to recommend --with-openssl-dir.
6457 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6458 - When using the TransPort option on OpenBSD, and using the User
6459 option to change UID and drop privileges, make sure to open
6460 /dev/pf before dropping privileges. Fixes bug 782. Patch from
6461 Christopher Davis. Bugfix on 0.1.2.1-alpha.
6462 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6463 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6464 on the client side when connecting to a hidden service. Bugfix
6465 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6466 - When closing an application-side connection because its circuit is
6467 getting torn down, generate the stream event correctly. Bugfix on
6468 0.1.2.x. Anonymous patch.
6471 Changes in version 0.2.1.5-alpha - 2008-08-31
6472 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
6473 in a lot of the infrastructure for adding authorization to hidden
6474 services, lays the groundwork for having clients read their load
6475 balancing information out of the networkstatus consensus rather than
6476 the individual router descriptors, addresses two potential anonymity
6477 issues, and fixes a variety of smaller issues.
6480 - Convert many internal address representations to optionally hold
6482 - Generate and accept IPv6 addresses in many protocol elements.
6483 - Make resolver code handle nameservers located at ipv6 addresses.
6484 - Begin implementation of proposal 121 ("Client authorization for
6485 hidden services"): configure hidden services with client
6486 authorization, publish descriptors for them, and configure
6487 authorization data for hidden services at clients. The next
6488 step is to actually access hidden services that perform client
6490 - More progress toward proposal 141: Network status consensus
6491 documents and votes now contain bandwidth information for each
6492 router and a summary of that router's exit policy. Eventually this
6493 will be used by clients so that they do not have to download every
6494 known descriptor before building circuits.
6496 o Major bugfixes (on 0.2.0.x and before):
6497 - When sending CREATED cells back for a given circuit, use a 64-bit
6498 connection ID to find the right connection, rather than an addr:port
6499 combination. Now that we can have multiple OR connections between
6500 the same ORs, it is no longer possible to use addr:port to uniquely
6501 identify a connection.
6502 - Relays now reject risky extend cells: if the extend cell includes
6503 a digest of all zeroes, or asks to extend back to the relay that
6504 sent the extend cell, tear down the circuit. Ideas suggested
6506 - If not enough of our entry guards are available so we add a new
6507 one, we might use the new one even if it overlapped with the
6508 current circuit's exit relay (or its family). Anonymity bugfix
6509 pointed out by rovv.
6512 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6513 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6514 - When using the TransPort option on OpenBSD, and using the User
6515 option to change UID and drop privileges, make sure to open /dev/pf
6516 before dropping privileges. Fixes bug 782. Patch from Christopher
6517 Davis. Bugfix on 0.1.2.1-alpha.
6518 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6519 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6520 - Add a missing safe_str() call for a debug log message.
6521 - Use 64 bits instead of 32 bits for connection identifiers used with
6522 the controller protocol, to greatly reduce risk of identifier reuse.
6523 - Make the autoconf script accept the obsolete --with-ssl-dir
6524 option as an alias for the actually-working --with-openssl-dir
6525 option. Fix the help documentation to recommend --with-openssl-dir.
6526 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6529 - Rate-limit too-many-sockets messages: when they happen, they happen
6530 a lot. Resolves bug 748.
6531 - Resist DNS poisoning a little better by making sure that names in
6532 answer sections match.
6533 - Print the SOCKS5 error message string as well as the error code
6534 when a tor-resolve request fails. Patch from Jacob.
6537 Changes in version 0.2.1.4-alpha - 2008-08-04
6538 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
6541 - The address part of exit policies was not correctly written
6542 to router descriptors. This generated router descriptors that failed
6543 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
6545 - Tor triggered a false assert when extending a circuit to a relay
6546 but we already have a connection open to that relay. Noticed by
6547 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
6550 - Fix a hidden service logging bug: in some edge cases, the router
6551 descriptor of a previously picked introduction point becomes
6552 obsolete and we need to give up on it rather than continually
6553 complaining that it has become obsolete. Observed by xiando. Bugfix
6557 - Take out the TestVia config option, since it was a workaround for
6558 a bug that was fixed in Tor 0.1.1.21.
6561 Changes in version 0.2.1.3-alpha - 2008-08-03
6562 Tor 0.2.1.3-alpha implements most of the pieces to prevent
6563 infinite-length circuit attacks (see proposal 110); fixes a bug that
6564 might cause exit relays to corrupt streams they send back; allows
6565 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
6566 ExcludeExitNodes config options; and fixes a big pile of bugs.
6568 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
6569 - Send a bootstrap problem "warn" event on the first problem if the
6570 reason is NO_ROUTE (that is, our network is down).
6573 - Implement most of proposal 110: The first K cells to be sent
6574 along a circuit are marked as special "early" cells; only K "early"
6575 cells will be allowed. Once this code is universal, we can block
6576 certain kinds of DOS attack by requiring that EXTEND commands must
6577 be sent using an "early" cell.
6580 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6581 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6582 on the client side when connecting to a hidden service. Bugfix
6583 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6584 - Ensure that two circuits can never exist on the same connection
6585 with the same circuit ID, even if one is marked for close. This
6586 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
6589 - When relays do their initial bandwidth measurement, don't limit
6590 to just our entry guards for the test circuits. Otherwise we tend
6591 to have multiple test circuits going through a single entry guard,
6592 which makes our bandwidth test less accurate. Fixes part of bug 654;
6593 patch contributed by Josh Albrecht.
6594 - Add an ExcludeExitNodes option so users can list a set of nodes
6595 that should be be excluded from the exit node position, but
6596 allowed elsewhere. Implements proposal 151.
6597 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
6598 ExcludeNodes and ExcludeExitNodes lists.
6599 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
6600 be more efficient. Formerly it was quadratic in the number of
6601 servers; now it should be linear. Fixes bug 509.
6602 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
6603 and n_conn_id_digest fields into a separate structure that's
6604 only needed when the circuit has not yet attached to an n_conn.
6607 - Change the contrib/tor.logrotate script so it makes the new
6608 logs as "_tor:_tor" rather than the default, which is generally
6609 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
6610 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
6611 warnings (occasionally), but it can also cause the compiler to
6612 eliminate error-checking code. Suggested by Peter Gutmann.
6613 - When a hidden service is giving up on an introduction point candidate
6614 that was not included in the last published rendezvous descriptor,
6615 don't reschedule publication of the next descriptor. Fixes bug 763.
6617 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
6618 HiddenServiceExcludeNodes as obsolete: they never worked properly,
6619 and nobody claims to be using them. Fixes bug 754. Bugfix on
6620 0.1.0.1-rc. Patch from Christian Wilms.
6621 - Fix a small alignment and memory-wasting bug on buffer chunks.
6624 o Minor bugfixes (controller):
6625 - When closing an application-side connection because its circuit
6626 is getting torn down, generate the stream event correctly.
6627 Bugfix on 0.1.2.x. Anonymous patch.
6630 - Remove all backward-compatibility code to support relays running
6631 versions of Tor so old that they no longer work at all on the
6635 Changes in version 0.2.0.30 - 2008-07-15
6637 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
6638 warnings (occasionally), but it can also cause the compiler to
6639 eliminate error-checking code. Suggested by Peter Gutmann.
6642 Changes in version 0.2.0.29-rc - 2008-07-08
6643 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
6644 hidden-service performance bugs, and fixes a bunch of smaller bugs.
6647 - If you have more than one bridge but don't know their keys,
6648 you would only launch a request for the descriptor of the first one
6649 on your list. (Tor considered launching requests for the others, but
6650 found that it already had a connection on the way for $0000...0000
6651 so it didn't open another.) Bugfix on 0.2.0.x.
6652 - If you have more than one bridge but don't know their keys, and the
6653 connection to one of the bridges failed, you would cancel all
6654 pending bridge connections. (After all, they all have the same
6655 digest.) Bugfix on 0.2.0.x.
6656 - When a hidden service was trying to establish an introduction point,
6657 and Tor had built circuits preemptively for such purposes, we
6658 were ignoring all the preemptive circuits and launching a new one
6659 instead. Bugfix on 0.2.0.14-alpha.
6660 - When a hidden service was trying to establish an introduction point,
6661 and Tor *did* manage to reuse one of the preemptively built
6662 circuits, it didn't correctly remember which one it used,
6663 so it asked for another one soon after, until there were no
6664 more preemptive circuits, at which point it launched one from
6665 scratch. Bugfix on 0.0.9.x.
6666 - Make directory servers include the X-Your-Address-Is: http header in
6667 their responses even for begin_dir conns. Now clients who only
6668 ever use begin_dir connections still have a way to learn their IP
6669 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
6672 - Fix a macro/CPP interaction that was confusing some compilers:
6673 some GCCs don't like #if/#endif pairs inside macro arguments.
6675 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
6676 Fixes bug 704; fix from Steven Murdoch.
6677 - When opening /dev/null in finish_daemonize(), do not pass the
6678 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
6679 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
6680 - Correctly detect transparent proxy support on Linux hosts that
6681 require in.h to be included before netfilter_ipv4.h. Patch
6683 - Disallow session resumption attempts during the renegotiation
6684 stage of the v2 handshake protocol. Clients should never be trying
6685 session resumption at this point, but apparently some did, in
6686 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
6687 found by Geoff Goodell.
6690 Changes in version 0.2.1.2-alpha - 2008-06-20
6691 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
6692 make it easier to set up your own private Tor network; fixes several
6693 big bugs with using more than one bridge relay; fixes a big bug with
6694 offering hidden services quickly after Tor starts; and uses a better
6695 API for reporting potential bootstrapping problems to the controller.
6698 - New TestingTorNetwork config option to allow adjustment of
6699 previously constant values that, while reasonable, could slow
6700 bootstrapping. Implements proposal 135. Patch from Karsten.
6703 - If you have more than one bridge but don't know their digests,
6704 you would only learn a request for the descriptor of the first one
6705 on your list. (Tor considered launching requests for the others, but
6706 found that it already had a connection on the way for $0000...0000
6707 so it didn't open another.) Bugfix on 0.2.0.x.
6708 - If you have more than one bridge but don't know their digests,
6709 and the connection to one of the bridges failed, you would cancel
6710 all pending bridge connections. (After all, they all have the
6711 same digest.) Bugfix on 0.2.0.x.
6712 - When establishing a hidden service, introduction points that
6713 originate from cannibalized circuits are completely ignored and not
6714 included in rendezvous service descriptors. This might be another
6715 reason for delay in making a hidden service available. Bugfix
6716 from long ago (0.0.9.x?)
6719 - Allow OpenSSL to use dynamic locks if it wants.
6720 - When building a consensus, do not include routers that are down.
6721 This will cut down 30% to 40% on consensus size. Implements
6723 - In directory authorities' approved-routers files, allow
6724 fingerprints with or without space.
6725 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
6726 controller can query our current bootstrap state in case it attaches
6727 partway through and wants to catch up.
6728 - Send an initial "Starting" bootstrap status event, so we have a
6729 state to start out in.
6732 - Asking for a conditional consensus at .../consensus/<fingerprints>
6733 would crash a dirserver if it did not already have a
6734 consensus. Bugfix on 0.2.1.1-alpha.
6735 - Clean up some macro/CPP interactions: some GCC versions don't like
6736 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
6739 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
6740 - Directory authorities shouldn't complain about bootstrapping
6741 problems just because they do a lot of reachability testing and
6742 some of the connection attempts fail.
6743 - Start sending "count" and "recommendation" key/value pairs in
6744 bootstrap problem status events, so the controller can hear about
6745 problems even before Tor decides they're worth reporting for sure.
6746 - If you're using bridges, generate "bootstrap problem" warnings
6747 as soon as you run out of working bridges, rather than waiting
6748 for ten failures -- which will never happen if you have less than
6750 - If we close our OR connection because there's been a circuit
6751 pending on it for too long, we were telling our bootstrap status
6752 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
6755 Changes in version 0.2.1.1-alpha - 2008-06-13
6756 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
6757 were making the Tor process bloat especially on Linux; makes our TLS
6758 handshake blend in better; sends "bootstrap phase" status events to
6759 the controller, so it can keep the user informed of progress (and
6760 problems) fetching directory information and establishing circuits;
6761 and adds a variety of smaller features.
6764 - More work on making our TLS handshake blend in: modify the list
6765 of ciphers advertised by OpenSSL in client mode to even more
6766 closely resemble a common web browser. We cheat a little so that
6767 we can advertise ciphers that the locally installed OpenSSL doesn't
6769 - Start sending "bootstrap phase" status events to the controller,
6770 so it can keep the user informed of progress fetching directory
6771 information and establishing circuits. Also inform the controller
6772 if we think we're stuck at a particular bootstrap phase. Implements
6774 - Resume using OpenSSL's RAND_poll() for better (and more portable)
6775 cross-platform entropy collection again. We used to use it, then
6776 stopped using it because of a bug that could crash systems that
6777 called RAND_poll when they had a lot of fds open. It looks like the
6778 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
6779 at startup, and to call RAND_poll() when we reseed later only if
6780 we have a non-buggy OpenSSL version.
6783 - When we choose to abandon a new entry guard because we think our
6784 older ones might be better, close any circuits pending on that
6785 new entry guard connection. This fix should make us recover much
6786 faster when our network is down and then comes back. Bugfix on
6787 0.1.2.8-beta; found by lodger.
6789 o Memory fixes and improvements:
6790 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
6791 to avoid unused RAM in buffer chunks and memory pools.
6792 - Speed up parsing and cut down on memory fragmentation by using
6793 stack-style allocations for parsing directory objects. Previously,
6794 this accounted for over 40% of allocations from within Tor's code
6795 on a typical directory cache.
6796 - Use a Bloom filter rather than a digest-based set to track which
6797 descriptors we need to keep around when we're cleaning out old
6798 router descriptors. This speeds up the computation significantly,
6799 and may reduce fragmentation.
6800 - Reduce the default smartlist size from 32 to 16; it turns out that
6801 most smartlists hold around 8-12 elements tops.
6802 - Make dumpstats() log the fullness and size of openssl-internal
6804 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
6805 patch to their OpenSSL, turn it on to save memory on servers. This
6806 patch will (with any luck) get included in a mainline distribution
6808 - Never use OpenSSL compression: it wastes RAM and CPU trying to
6809 compress cells, which are basically all encrypted, compressed,
6813 - Stop reloading the router list from disk for no reason when we
6814 run out of reachable directory mirrors. Once upon a time reloading
6815 it would set the 'is_running' flag back to 1 for them. It hasn't
6816 done that for a long time.
6817 - In very rare situations new hidden service descriptors were
6818 published earlier than 30 seconds after the last change to the
6819 service. (We currently think that a hidden service descriptor
6820 that's been stable for 30 seconds is worth publishing.)
6823 - Allow separate log levels to be configured for different logging
6824 domains. For example, this allows one to log all notices, warnings,
6825 or errors, plus all memory management messages of level debug or
6826 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
6827 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
6828 and stop using a warning that had become unfixably verbose under
6830 - New --hush command-line option similar to --quiet. While --quiet
6831 disables all logging to the console on startup, --hush limits the
6832 output to messages of warning and error severity.
6833 - Servers support a new URL scheme for consensus downloads that
6834 allows the client to specify which authorities are trusted.
6835 The server then only sends the consensus if the client will trust
6836 it. Otherwise a 404 error is sent back. Clients use this
6837 new scheme when the server supports it (meaning it's running
6838 0.2.1.1-alpha or later). Implements proposal 134.
6839 - New configure/torrc options (--enable-geoip-stats,
6840 DirRecordUsageByCountry) to record how many IPs we've served
6841 directory info to in each country code, how many status documents
6842 total we've sent to each country code, and what share of the total
6843 directory requests we should expect to see.
6844 - Use the TLS1 hostname extension to more closely resemble browser
6846 - Lots of new unit tests.
6847 - Add a macro to implement the common pattern of iterating through
6848 two parallel lists in lockstep.
6851 Changes in version 0.2.0.28-rc - 2008-06-13
6852 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
6853 performance bug, and fixes a bunch of smaller bugs.
6856 - Fix a bug where, when we were choosing the 'end stream reason' to
6857 put in our relay end cell that we send to the exit relay, Tor
6858 clients on Windows were sometimes sending the wrong 'reason'. The
6859 anonymity problem is that exit relays may be able to guess whether
6860 the client is running Windows, thus helping partition the anonymity
6861 set. Down the road we should stop sending reasons to exit relays,
6862 or otherwise prevent future versions of this bug.
6865 - While setting up a hidden service, some valid introduction circuits
6866 were overlooked and abandoned. This might be the reason for
6867 the long delay in making a hidden service available. Bugfix on
6871 - Update to the "June 9 2008" ip-to-country file.
6872 - Run 'make test' as part of 'make dist', so we stop releasing so
6873 many development snapshots that fail their unit tests.
6876 - When we're checking if we have enough dir info for each relay
6877 to begin establishing circuits, make sure that we actually have
6878 the descriptor listed in the consensus, not just any descriptor.
6880 - Bridge relays no longer print "xx=0" in their extrainfo document
6881 for every single country code in the geoip db. Bugfix on
6883 - Only warn when we fail to load the geoip file if we were planning to
6884 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
6885 - If we change our MaxAdvertisedBandwidth and then reload torrc,
6886 Tor won't realize it should publish a new relay descriptor. Fixes
6887 bug 688, reported by mfr. Bugfix on 0.1.2.x.
6888 - When we haven't had any application requests lately, don't bother
6889 logging that we have expired a bunch of descriptors. Bugfix
6891 - Make relay cells written on a connection count as non-padding when
6892 tracking how long a connection has been in use. Bugfix on
6893 0.2.0.1-alpha. Spotted by lodger.
6894 - Fix unit tests in 0.2.0.27-rc.
6895 - Fix compile on Windows.
6898 Changes in version 0.2.0.27-rc - 2008-06-03
6899 Tor 0.2.0.27-rc adds a few features we left out of the earlier
6900 release candidates. In particular, we now include an IP-to-country
6901 GeoIP database, so controllers can easily look up what country a
6902 given relay is in, and so bridge relays can give us some sanitized
6903 summaries about which countries are making use of bridges. (See proposal
6904 126-geoip-fetching.txt for details.)
6907 - Include an IP-to-country GeoIP file in the tarball, so bridge
6908 relays can report sanitized summaries of the usage they're seeing.
6911 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
6912 Robert Hogan. Fixes the first part of bug 681.
6913 - Make bridge authorities never serve extrainfo docs.
6914 - Add support to detect Libevent versions in the 1.4.x series
6916 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
6917 - Include a new contrib/tor-exit-notice.html file that exit relay
6918 operators can put on their website to help reduce abuse queries.
6921 - When tunneling an encrypted directory connection, and its first
6922 circuit fails, do not leave it unattached and ask the controller
6923 to deal. Fixes the second part of bug 681.
6924 - Make bridge authorities correctly expire old extrainfo documents
6928 Changes in version 0.2.0.26-rc - 2008-05-13
6929 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
6930 in Debian's OpenSSL packages. All users running any 0.2.0.x version
6931 should upgrade, whether they're running Debian or not.
6933 o Major security fixes:
6934 - Use new V3 directory authority keys on the tor26, gabelmoo, and
6935 moria1 V3 directory authorities. The old keys were generated with
6936 a vulnerable version of Debian's OpenSSL package, and must be
6937 considered compromised. Other authorities' keys were not generated
6938 with an affected version of OpenSSL.
6941 - List authority signatures as "unrecognized" based on DirServer
6942 lines, not on cert cache. Bugfix on 0.2.0.x.
6945 - Add a new V3AuthUseLegacyKey option to make it easier for
6946 authorities to change their identity keys if they have to.
6949 Changes in version 0.2.0.25-rc - 2008-04-23
6950 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
6953 - Remember to initialize threading before initializing logging.
6954 Otherwise, many BSD-family implementations will crash hard on
6955 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
6958 - Authorities correctly free policies on bad servers on
6959 exit. Fixes bug 672. Bugfix on 0.2.0.x.
6962 Changes in version 0.2.0.24-rc - 2008-04-22
6963 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
6964 v3 directory authority, makes relays with dynamic IP addresses and no
6965 DirPort notice more quickly when their IP address changes, fixes a few
6966 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
6968 o New directory authorities:
6969 - Take lefkada out of the list of v3 directory authorities, since
6970 it has been down for months.
6971 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
6975 - Detect address changes more quickly on non-directory mirror
6976 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
6978 o Minor features (security):
6979 - Reject requests for reverse-dns lookup of names that are in
6980 a private address space. Patch from lodger.
6981 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
6984 o Minor bugfixes (crashes):
6985 - Avoid a rare assert that can trigger when Tor doesn't have much
6986 directory information yet and it tries to fetch a v2 hidden
6987 service descriptor. Fixes bug 651, reported by nwf.
6988 - Initialize log mutex before initializing dmalloc. Otherwise,
6989 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
6990 - Use recursive pthread mutexes in order to avoid deadlock when
6991 logging debug-level messages to a controller. Bug spotted by nwf,
6992 bugfix on 0.2.0.16-alpha.
6994 o Minor bugfixes (resource management):
6995 - Keep address policies from leaking memory: start their refcount
6996 at 1, not 2. Bugfix on 0.2.0.16-alpha.
6997 - Free authority certificates on exit, so they don't look like memory
6998 leaks. Bugfix on 0.2.0.19-alpha.
6999 - Free static hashtables for policy maps and for TLS connections on
7000 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
7001 - Avoid allocating extra space when computing consensuses on 64-bit
7002 platforms. Bug spotted by aakova.
7004 o Minor bugfixes (misc):
7005 - Do not read the configuration file when we've only been told to
7006 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
7007 based on patch from Sebastian Hahn.
7008 - Exit relays that are used as a client can now reach themselves
7009 using the .exit notation, rather than just launching an infinite
7010 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
7011 - When attempting to open a logfile fails, tell us why.
7012 - Fix a dumb bug that was preventing us from knowing that we should
7013 preemptively build circuits to handle expected directory requests.
7014 Fixes bug 660. Bugfix on 0.1.2.x.
7015 - Warn less verbosely about clock skew from netinfo cells from
7016 untrusted sources. Fixes bug 663.
7017 - Make controller stream events for DNS requests more consistent,
7018 by adding "new stream" events for DNS requests, and removing
7019 spurious "stream closed" events" for cached reverse resolves.
7020 Patch from mwenge. Fixes bug 646.
7021 - Correctly notify one-hop connections when a circuit build has
7022 failed. Possible fix for bug 669. Found by lodger.
7025 Changes in version 0.2.0.23-rc - 2008-03-24
7026 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
7027 makes bootstrapping faster if the first directory mirror you contact
7028 is down. The bundles also include the new Vidalia 0.1.2 release.
7031 - When a tunneled directory request is made to a directory server
7032 that's down, notice after 30 seconds rather than 120 seconds. Also,
7033 fail any begindir streams that are pending on it, so they can
7034 retry elsewhere. This was causing multi-minute delays on bootstrap.
7037 Changes in version 0.2.0.22-rc - 2008-03-18
7038 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
7039 enables encrypted directory connections by default for non-relays, fixes
7040 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
7041 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
7044 - Enable encrypted directory connections by default for non-relays,
7045 so censor tools that block Tor directory connections based on their
7046 plaintext patterns will no longer work. This means Tor works in
7047 certain censored countries by default again.
7050 - Make sure servers always request certificates from clients during
7051 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
7052 - Do not enter a CPU-eating loop when a connection is closed in
7053 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
7054 diagnosed by lodger; bugfix on 0.2.0.20-rc.
7055 - Fix assertion failure that could occur when a blocked circuit
7056 became unblocked, and it had pending client DNS requests. Bugfix
7057 on 0.2.0.1-alpha. Fixes bug 632.
7059 o Minor bugfixes (on 0.1.2.x):
7060 - Generate "STATUS_SERVER" events rather than misspelled
7061 "STATUS_SEVER" events. Caught by mwenge.
7062 - When counting the number of bytes written on a TLS connection,
7063 look at the BIO actually used for writing to the network, not
7064 at the BIO used (sometimes) to buffer data for the network.
7065 Looking at different BIOs could result in write counts on the
7066 order of ULONG_MAX. Fixes bug 614.
7067 - On Windows, correctly detect errors when listing the contents of
7068 a directory. Fix from lodger.
7070 o Minor bugfixes (on 0.2.0.x):
7071 - Downgrade "sslv3 alert handshake failure" message to INFO.
7072 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
7073 left BandwidthRate and BandwidthBurst at the default, we would be
7074 silently limited by those defaults. Now raise them to match the
7075 RelayBandwidth* values.
7076 - Fix the SVK version detection logic to work correctly on a branch.
7077 - Make --enable-openbsd-malloc work correctly on Linux with alpha
7078 CPUs. Fixes bug 625.
7079 - Logging functions now check that the passed severity is sane.
7080 - Use proper log levels in the testsuite call of
7081 get_interface_address6().
7082 - When using a nonstandard malloc, do not use the platform values for
7083 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
7084 - Make the openbsd malloc code use 8k pages on alpha CPUs and
7086 - Detect mismatched page sizes when using --enable-openbsd-malloc.
7087 - Avoid double-marked-for-close warning when certain kinds of invalid
7088 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
7089 for bug 617. Bugfix on 0.2.0.1-alpha.
7090 - Make sure that the "NULL-means-reject *:*" convention is followed by
7091 all the policy manipulation functions, avoiding some possible crash
7092 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
7093 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
7094 actually works, and doesn't warn about every single reverse lookup.
7095 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
7098 - Only log guard node status when guard node status has changed.
7099 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
7100 make "INFO" 75% less verbose.
7103 Changes in version 0.2.0.21-rc - 2008-03-02
7104 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
7105 makes Tor work well with Vidalia again, fixes a rare assert bug,
7106 and fixes a pair of more minor bugs. The bundles also include Vidalia
7107 0.1.0 and Torbutton 1.1.16.
7110 - The control port should declare that it requires password auth
7111 when HashedControlSessionPassword is set too. Patch from Matt Edman;
7112 bugfix on 0.2.0.20-rc. Fixes bug 615.
7113 - Downgrade assert in connection_buckets_decrement() to a log message.
7114 This may help us solve bug 614, and in any case will make its
7115 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
7116 - We were sometimes miscounting the number of bytes read from the
7117 network, causing our rate limiting to not be followed exactly.
7118 Bugfix on 0.2.0.16-alpha. Reported by lodger.
7121 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
7122 OpenSSL versions should have been working fine. Diagnosis and patch
7123 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
7124 Bugfix on 0.2.0.20-rc.
7127 Changes in version 0.2.0.20-rc - 2008-02-24
7128 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
7129 makes more progress towards normalizing Tor's TLS handshake, makes
7130 hidden services work better again, helps relays bootstrap if they don't
7131 know their IP address, adds optional support for linking in openbsd's
7132 allocator or tcmalloc, allows really fast relays to scale past 15000
7133 sockets, and fixes a bunch of minor bugs reported by Veracode.
7136 - Enable the revised TLS handshake based on the one designed by
7137 Steven Murdoch in proposal 124, as revised in proposal 130. It
7138 includes version negotiation for OR connections as described in
7139 proposal 105. The new handshake is meant to be harder for censors
7140 to fingerprint, and it adds the ability to detect certain kinds of
7141 man-in-the-middle traffic analysis attacks. The version negotiation
7142 feature will allow us to improve Tor's link protocol more safely
7144 - Choose which bridge to use proportional to its advertised bandwidth,
7145 rather than uniformly at random. This should speed up Tor for
7146 bridge users. Also do this for people who set StrictEntryNodes.
7147 - When a TrackHostExits-chosen exit fails too many times in a row,
7148 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
7151 - Resolved problems with (re-)fetching hidden service descriptors.
7152 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
7154 - If we only ever used Tor for hidden service lookups or posts, we
7155 would stop building circuits and start refusing connections after
7156 24 hours, since we falsely believed that Tor was dormant. Reported
7157 by nwf; bugfix on 0.1.2.x.
7158 - Servers that don't know their own IP address should go to the
7159 authorities for their first directory fetch, even if their DirPort
7160 is off or if they don't know they're reachable yet. This will help
7161 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
7162 - When counting the number of open sockets, count not only the number
7163 of sockets we have received from the socket() call, but also
7164 the number we've gotten from accept() and socketpair(). This bug
7165 made us fail to count all sockets that we were using for incoming
7166 connections. Bugfix on 0.2.0.x.
7167 - Fix code used to find strings within buffers, when those strings
7168 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
7169 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
7170 - Add a new __HashedControlSessionPassword option for controllers
7171 to use for one-off session password hashes that shouldn't get
7172 saved to disk by SAVECONF --- Vidalia users were accumulating a
7173 pile of HashedControlPassword lines in their torrc files, one for
7174 each time they had restarted Tor and then clicked Save. Make Tor
7175 automatically convert "HashedControlPassword" to this new option but
7176 only when it's given on the command line. Partial fix for bug 586.
7178 o Minor features (performance):
7179 - Tune parameters for cell pool allocation to minimize amount of
7181 - Add OpenBSD malloc code from phk as an optional malloc
7182 replacement on Linux: some glibc libraries do very poorly
7183 with Tor's memory allocation patterns. Pass
7184 --enable-openbsd-malloc to get the replacement malloc code.
7185 - Add a --with-tcmalloc option to the configure script to link
7186 against tcmalloc (if present). Does not yet search for
7187 non-system include paths.
7188 - Stop imposing an arbitrary maximum on the number of file descriptors
7189 used for busy servers. Bug reported by Olaf Selke; patch from
7192 o Minor features (other):
7193 - When SafeLogging is disabled, log addresses along with all TLS
7195 - When building with --enable-gcc-warnings, check for whether Apple's
7196 warning "-Wshorten-64-to-32" is available.
7197 - Add a --passphrase-fd argument to the tor-gencert command for
7200 o Minor bugfixes (memory leaks and code problems):
7201 - We were leaking a file descriptor if Tor started with a zero-length
7202 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
7203 - Detect size overflow in zlib code. Reported by Justin Ferguson and
7205 - We were comparing the raw BridgePassword entry with a base64'ed
7206 version of it, when handling a "/tor/networkstatus-bridges"
7207 directory request. Now compare correctly. Noticed by Veracode.
7208 - Recover from bad tracked-since value in MTBF-history file.
7210 - Alter the code that tries to recover from unhandled write
7211 errors, to not try to flush onto a socket that's given us
7212 unhandled errors. Bugfix on 0.1.2.x.
7213 - Make Unix controlsockets work correctly on OpenBSD. Patch from
7214 tup. Bugfix on 0.2.0.3-alpha.
7216 o Minor bugfixes (other):
7217 - If we have an extra-info document for our server, always make
7218 it available on the control port, even if we haven't gotten
7219 a copy of it from an authority yet. Patch from mwenge.
7220 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
7221 - Directory mirrors no longer include a guess at the client's IP
7222 address if the connection appears to be coming from the same /24
7223 network; it was producing too many wrong guesses.
7224 - Make the new hidden service code respect the SafeLogging setting.
7225 Bugfix on 0.2.0.x. Patch from Karsten.
7226 - When starting as an authority, do not overwrite all certificates
7227 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
7228 - If we're trying to flush the last bytes on a connection (for
7229 example, when answering a directory request), reset the
7230 time-to-give-up timeout every time we manage to write something
7231 on the socket. Bugfix on 0.1.2.x.
7232 - Change the behavior of "getinfo status/good-server-descriptor"
7233 so it doesn't return failure when any authority disappears.
7234 - Even though the man page said that "TrackHostExits ." should
7235 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
7236 - Report TLS "zero return" case as a "clean close" and "IO error"
7237 as a "close". Stop calling closes "unexpected closes": existing
7238 Tors don't use SSL_close(), so having a connection close without
7239 the TLS shutdown handshake is hardly unexpected.
7240 - Send NAMESERVER_STATUS messages for a single failed nameserver
7243 o Code simplifications and refactoring:
7244 - Remove the tor_strpartition function: its logic was confused,
7245 and it was only used for one thing that could be implemented far
7249 Changes in version 0.2.0.19-alpha - 2008-02-09
7250 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
7251 handshake, makes path selection for relays more secure and IP address
7252 guessing more robust, and generally fixes a lot of bugs in preparation
7253 for calling the 0.2.0 branch stable.
7256 - Do not include recognizeable strings in the commonname part of
7257 Tor's x509 certificates.
7260 - If we're a relay, avoid picking ourselves as an introduction point,
7261 a rendezvous point, or as the final hop for internal circuits. Bug
7262 reported by taranis and lodger. Bugfix on 0.1.2.x.
7263 - Patch from "Andrew S. Lists" to catch when we contact a directory
7264 mirror at IP address X and he says we look like we're coming from
7265 IP address X. Bugfix on 0.1.2.x.
7267 o Minor features (security):
7268 - Be more paranoid about overwriting sensitive memory on free(),
7269 as a defensive programming tactic to ensure forward secrecy.
7271 o Minor features (directory authority):
7272 - Actually validate the options passed to AuthDirReject,
7273 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
7274 - Reject router descriptors with out-of-range bandwidthcapacity or
7275 bandwidthburst values.
7277 o Minor features (controller):
7278 - Reject controller commands over 1MB in length. This keeps rogue
7279 processes from running us out of memory.
7281 o Minor features (misc):
7282 - Give more descriptive well-formedness errors for out-of-range
7283 hidden service descriptor/protocol versions.
7284 - Make memory debugging information describe more about history
7285 of cell allocation, so we can help reduce our memory use.
7287 o Deprecated features (controller):
7288 - The status/version/num-versioning and status/version/num-concurring
7289 GETINFO options are no longer useful in the v3 directory protocol:
7290 treat them as deprecated, and warn when they're used.
7293 - When our consensus networkstatus has been expired for a while, stop
7294 being willing to build circuits using it. Fixes bug 401. Bugfix
7296 - Directory caches now fetch certificates from all authorities
7297 listed in a networkstatus consensus, even when they do not
7298 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
7299 - When connecting to a bridge without specifying its key, insert
7300 the connection into the identity-to-connection map as soon as
7301 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
7302 - Detect versions of OS X where malloc_good_size() is present in the
7303 library but never actually declared. Resolves bug 587. Bugfix
7305 - Stop incorrectly truncating zlib responses to directory authority
7306 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
7307 - Stop recommending that every server operator send mail to tor-ops.
7308 Resolves bug 597. Bugfix on 0.1.2.x.
7309 - Don't trigger an assert if we start a directory authority with a
7310 private IP address (like 127.0.0.1).
7311 - Avoid possible failures when generating a directory with routers
7312 with over-long versions strings, or too many flags set. Bugfix
7314 - If an attempt to launch a DNS resolve request over the control
7315 port fails because we have overrun the limit on the number of
7316 connections, tell the controller that the request has failed.
7317 - Avoid using too little bandwidth when our clock skips a few
7318 seconds. Bugfix on 0.1.2.x.
7319 - Fix shell error when warning about missing packages in configure
7320 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
7321 - Do not become confused when receiving a spurious VERSIONS-like
7322 cell from a confused v1 client. Bugfix on 0.2.0.x.
7323 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
7324 introduction points for a hidden service have failed. Patch from
7325 Karsten Loesing. Bugfix on 0.2.0.x.
7327 o Code simplifications and refactoring:
7328 - Remove some needless generality from cpuworker code, for improved
7330 - Stop overloading the circuit_t.onionskin field for both "onionskin
7331 from a CREATE cell that we are waiting for a cpuworker to be
7332 assigned" and "onionskin from an EXTEND cell that we are going to
7333 send to an OR as soon as we are connected". Might help with bug 600.
7334 - Add an in-place version of aes_crypt() so that we can avoid doing a
7335 needless memcpy() call on each cell payload.
7338 Changes in version 0.2.0.18-alpha - 2008-01-25
7339 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
7340 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
7341 that can warn or reject connections to ports generally associated with
7342 vulnerable-plaintext protocols.
7344 o New directory authorities:
7345 - Set up dannenberg (run by CCC) as the sixth v3 directory
7349 - Fix a major memory leak when attempting to use the v2 TLS
7350 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
7351 - We accidentally enabled the under-development v2 TLS handshake
7352 code, which was causing log entries like "TLS error while
7353 renegotiating handshake". Disable it again. Resolves bug 590.
7354 - We were computing the wrong Content-Length: header for directory
7355 responses that need to be compressed on the fly, causing clients
7356 asking for those items to always fail. Bugfix on 0.2.0.x; partially
7360 - Avoid going directly to the directory authorities even if you're a
7361 relay, if you haven't found yourself reachable yet or if you've
7362 decided not to advertise your dirport yet. Addresses bug 556.
7363 - If we've gone 12 hours since our last bandwidth check, and we
7364 estimate we have less than 50KB bandwidth capacity but we could
7365 handle more, do another bandwidth test.
7366 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
7367 Tor can warn and/or refuse connections to ports commonly used with
7368 vulnerable-plaintext protocols. Currently we warn on ports 23,
7369 109, 110, and 143, but we don't reject any.
7372 - When we setconf ClientOnly to 1, close any current OR and Dir
7373 listeners. Reported by mwenge.
7374 - When we get a consensus that's been signed by more people than
7375 we expect, don't log about it; it's not a big deal. Reported
7379 - Don't answer "/tor/networkstatus-bridges" directory requests if
7380 the request isn't encrypted.
7381 - Make "ClientOnly 1" config option disable directory ports too.
7382 - Patches from Karsten Loesing to make v2 hidden services more
7383 robust: work even when there aren't enough HSDir relays available;
7384 retry when a v2 rend desc fetch fails; but don't retry if we
7385 already have a usable v0 rend desc.
7388 Changes in version 0.2.0.17-alpha - 2008-01-17
7389 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
7392 - Make the tor-gencert man page get included correctly in the tarball.
7395 Changes in version 0.2.0.16-alpha - 2008-01-17
7396 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
7397 Loesing, and generally cleans up a lot of features and minor bugs.
7399 o New directory authorities:
7400 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
7403 o Major performance improvements:
7404 - Switch our old ring buffer implementation for one more like that
7405 used by free Unix kernels. The wasted space in a buffer with 1mb
7406 of data will now be more like 8k than 1mb. The new implementation
7407 also avoids realloc();realloc(); patterns that can contribute to
7408 memory fragmentation.
7411 - Configuration files now accept C-style strings as values. This
7412 helps encode characters not allowed in the current configuration
7413 file format, such as newline or #. Addresses bug 557.
7414 - Although we fixed bug 539 (where servers would send HTTP status 503
7415 responses _and_ send a body too), there are still servers out
7416 there that haven't upgraded. Therefore, make clients parse such
7417 bodies when they receive them.
7418 - When we're not serving v2 directory information, there is no reason
7419 to actually keep any around. Remove the obsolete files and directory
7420 on startup if they are very old and we aren't going to serve them.
7422 o Minor performance improvements:
7423 - Reference-count and share copies of address policy entries; only 5%
7424 of them were actually distinct.
7425 - Never walk through the list of logs if we know that no log is
7426 interested in a given message.
7429 - When an authority has not signed a consensus, do not try to
7430 download a nonexistent "certificate with key 00000000". Bugfix
7431 on 0.2.0.x. Fixes bug 569.
7432 - Fix a rare assert error when we're closing one of our threads:
7433 use a mutex to protect the list of logs, so we never write to the
7434 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
7435 bug 575, which is kind of the revenge of bug 222.
7436 - Patch from Karsten Loesing to complain less at both the client
7437 and the relay when a relay used to have the HSDir flag but doesn't
7438 anymore, and we try to upload a hidden service descriptor.
7439 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
7441 - Do not try to download missing certificates until we have tried
7442 to check our fallback consensus. Fixes bug 583.
7443 - Make bridges round reported GeoIP stats info up to the nearest
7444 estimate, not down. Now we can distinguish between "0 people from
7445 this country" and "1 person from this country".
7446 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
7447 - Avoid possible segfault if key generation fails in
7448 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
7449 - Avoid segfault in the case where a badly behaved v2 versioning
7450 directory sends a signed networkstatus with missing client-versions.
7452 - Avoid segfaults on certain complex invocations of
7453 router_get_by_hexdigest(). Bugfix on 0.1.2.
7454 - Correct bad index on array access in parse_http_time(). Bugfix
7456 - Fix possible bug in vote generation when server versions are present
7457 but client versions are not.
7458 - Fix rare bug on REDIRECTSTREAM control command when called with no
7459 port set: it could erroneously report an error when none had
7461 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
7462 compressing large objects and find ourselves with more than 4k
7463 left over. Bugfix on 0.2.0.
7464 - Fix a small memory leak when setting up a hidden service.
7465 - Fix a few memory leaks that could in theory happen under bizarre
7467 - Fix an assert if we post a general-purpose descriptor via the
7468 control port but that descriptor isn't mentioned in our current
7469 network consensus. Bug reported by Jon McLachlan; bugfix on
7472 o Minor features (controller):
7473 - Get NS events working again. Patch from tup.
7474 - The GETCONF command now escapes and quotes configuration values
7475 that don't otherwise fit into the torrc file.
7476 - The SETCONF command now handles quoted values correctly.
7478 o Minor features (directory authorities):
7479 - New configuration options to override default maximum number of
7480 servers allowed on a single IP address. This is important for
7481 running a test network on a single host.
7482 - Actually implement the -s option to tor-gencert.
7483 - Add a manual page for tor-gencert.
7485 o Minor features (bridges):
7486 - Bridge authorities no longer serve bridge descriptors over
7487 unencrypted connections.
7489 o Minor features (other):
7490 - Add hidden services and DNSPorts to the list of things that make
7491 Tor accept that it has running ports. Change starting Tor with no
7492 ports from a fatal error to a warning; we might change it back if
7493 this turns out to confuse anybody. Fixes bug 579.
7496 Changes in version 0.1.2.19 - 2008-01-17
7497 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
7498 exit policy a little bit more conservative so it's safer to run an
7499 exit relay on a home system, and fixes a variety of smaller issues.
7502 - Exit policies now reject connections that are addressed to a
7503 relay's public (external) IP address too, unless
7504 ExitPolicyRejectPrivate is turned off. We do this because too
7505 many relays are running nearby to services that trust them based
7509 - When the clock jumps forward a lot, do not allow the bandwidth
7510 buckets to become negative. Fixes bug 544.
7511 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7512 on every successful resolve. Reported by Mike Perry.
7513 - Purge old entries from the "rephist" database and the hidden
7514 service descriptor database even when DirPort is zero.
7515 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7516 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7517 crashing or mis-answering these requests.
7518 - When we decide to send a 503 response to a request for servers, do
7519 not then also send the server descriptors: this defeats the whole
7520 purpose. Fixes bug 539.
7523 - Changing the ExitPolicyRejectPrivate setting should cause us to
7524 rebuild our server descriptor.
7525 - Fix handling of hex nicknames when answering controller requests for
7526 networkstatus by name, or when deciding whether to warn about
7527 unknown routers in a config option. (Patch from mwenge.)
7528 - Fix a couple of hard-to-trigger autoconf problems that could result
7529 in really weird results on platforms whose sys/types.h files define
7530 nonstandard integer types.
7531 - Don't try to create the datadir when running --verify-config or
7532 --hash-password. Resolves bug 540.
7533 - If we were having problems getting a particular descriptor from the
7534 directory caches, and then we learned about a new descriptor for
7535 that router, we weren't resetting our failure count. Reported
7537 - Although we fixed bug 539 (where servers would send HTTP status 503
7538 responses _and_ send a body too), there are still servers out there
7539 that haven't upgraded. Therefore, make clients parse such bodies
7540 when they receive them.
7541 - Run correctly on systems where rlim_t is larger than unsigned long.
7542 This includes some 64-bit systems.
7543 - Run correctly on platforms (like some versions of OS X 10.5) where
7544 the real limit for number of open files is OPEN_FILES, not rlim_max
7545 from getrlimit(RLIMIT_NOFILES).
7546 - Avoid a spurious free on base64 failure.
7547 - Avoid segfaults on certain complex invocations of
7548 router_get_by_hexdigest().
7549 - Fix rare bug on REDIRECTSTREAM control command when called with no
7550 port set: it could erroneously report an error when none had
7554 Changes in version 0.2.0.15-alpha - 2007-12-25
7555 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
7556 features added in 0.2.0.13-alpha.
7559 - Fix several remotely triggerable asserts based on DirPort requests
7560 for a v2 or v3 networkstatus object before we were prepared. This
7561 was particularly bad for 0.2.0.13 and later bridge relays, who
7562 would never have a v2 networkstatus and would thus always crash
7563 when used. Bugfixes on 0.2.0.x.
7564 - Estimate the v3 networkstatus size more accurately, rather than
7565 estimating it at zero bytes and giving it artificially high priority
7566 compared to other directory requests. Bugfix on 0.2.0.x.
7569 - Fix configure.in logic for cross-compilation.
7570 - When we load a bridge descriptor from the cache, and it was
7571 previously unreachable, mark it as retriable so we won't just
7572 ignore it. Also, try fetching a new copy immediately. Bugfixes
7574 - The bridge GeoIP stats were counting other relays, for example
7575 self-reachability and authority-reachability tests.
7578 - Support compilation to target iPhone; patch from cjacker huang.
7579 To build for iPhone, pass the --enable-iphone option to configure.
7582 Changes in version 0.2.0.14-alpha - 2007-12-23
7584 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
7585 without a datadirectory from a previous Tor install. Reported
7587 - Fix a crash when we fetch a descriptor that turns out to be
7588 unexpected (it used to be in our networkstatus when we started
7589 fetching it, but it isn't in our current networkstatus), and we
7590 aren't using bridges. Bugfix on 0.2.0.x.
7591 - Fix a crash when accessing hidden services: it would work the first
7592 time you use a given introduction point for your service, but
7593 on subsequent requests we'd be using garbage memory. Fixed by
7594 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
7595 - Fix a crash when we load a bridge descriptor from disk but we don't
7596 currently have a Bridge line for it in our torrc. Bugfix on
7600 - If bridge authorities set BridgePassword, they will serve a
7601 snapshot of known bridge routerstatuses from their DirPort to
7602 anybody who knows that password. Unset by default.
7605 - Make the unit tests build again.
7606 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
7607 - Make PublishServerDescriptor default to 1, so the default doesn't
7608 have to change as we invent new directory protocol versions.
7609 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
7610 be included unless sys/time.h is already included. Fixes
7611 bug 553. Bugfix on 0.2.0.x.
7612 - If we receive a general-purpose descriptor and then receive an
7613 identical bridge-purpose descriptor soon after, don't discard
7614 the next one as a duplicate.
7617 - If BridgeRelay is set to 1, then the default for
7618 PublishServerDescriptor is now "bridge" rather than "v2,v3".
7619 - If the user sets RelayBandwidthRate but doesn't set
7620 RelayBandwidthBurst, then make them equal rather than erroring out.
7623 Changes in version 0.2.0.13-alpha - 2007-12-21
7624 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
7625 Goodell, fixes many more bugs, and adds a lot of infrastructure for
7628 o New directory authorities:
7629 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
7633 - Only update guard status (usable / not usable) once we have
7634 enough directory information. This was causing us to always pick
7635 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
7636 causing us to discard all our guards on startup if we hadn't been
7637 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
7638 - Purge old entries from the "rephist" database and the hidden
7639 service descriptor databases even when DirPort is zero. Bugfix
7641 - We were ignoring our RelayBandwidthRate for the first 30 seconds
7642 after opening a circuit -- even a relayed circuit. Bugfix on
7644 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7645 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7646 crashing or mis-answering these types of requests.
7647 - Relays were publishing their server descriptor to v1 and v2
7648 directory authorities, but they didn't try publishing to v3-only
7649 authorities. Fix this; and also stop publishing to v1 authorities.
7651 - When we were reading router descriptors from cache, we were ignoring
7652 the annotations -- so for example we were reading in bridge-purpose
7653 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
7654 - When we decided to send a 503 response to a request for servers, we
7655 were then also sending the server descriptors: this defeats the
7656 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
7659 - Bridge relays now behave like clients with respect to time
7660 intervals for downloading new consensus documents -- otherwise they
7661 stand out. Bridge users now wait until the end of the interval,
7662 so their bridge relay will be sure to have a new consensus document.
7663 - Three new config options (AlternateDirAuthority,
7664 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
7665 user selectively replace the default directory authorities by type,
7666 rather than the all-or-nothing replacement that DirServer offers.
7667 - Tor can now be configured to read a GeoIP file from disk in one
7668 of two formats. This can be used by controllers to map IP addresses
7669 to countries. Eventually, it may support exit-by-country.
7670 - When possible, bridge relays remember which countries users
7671 are coming from, and report aggregate information in their
7672 extra-info documents, so that the bridge authorities can learn
7673 where Tor is blocked.
7674 - Bridge directory authorities now do reachability testing on the
7675 bridges they know. They provide router status summaries to the
7676 controller via "getinfo ns/purpose/bridge", and also dump summaries
7677 to a file periodically.
7678 - Stop fetching directory info so aggressively if your DirPort is
7679 on but your ORPort is off; stop fetching v2 dir info entirely.
7680 You can override these choices with the new FetchDirInfoEarly
7684 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
7685 consensus documents when there are too many relays at a single
7686 IP address. Now clear it in v2 network status documents too, and
7687 also clear it in routerinfo_t when the relay is no longer listed
7688 in the relevant networkstatus document.
7689 - Don't crash if we get an unexpected value for the
7690 PublishServerDescriptor config option. Reported by Matt Edman;
7691 bugfix on 0.2.0.9-alpha.
7692 - Our new v2 hidden service descriptor format allows descriptors
7693 that have no introduction points. But Tor crashed when we tried
7694 to build a descriptor with no intro points (and it would have
7695 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
7697 - Fix building with dmalloc 5.5.2 with glibc.
7698 - Reject uploaded descriptors and extrainfo documents if they're
7699 huge. Otherwise we'll cache them all over the network and it'll
7700 clog everything up. Reported by Aljosha Judmayer.
7701 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
7702 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
7703 - When the DANGEROUS_VERSION controller status event told us we're
7704 running an obsolete version, it used the string "OLD" to describe
7705 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
7706 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
7707 - If we can't expand our list of entry guards (e.g. because we're
7708 using bridges or we have StrictEntryNodes set), don't mark relays
7709 down when they fail a directory request. Otherwise we're too quick
7710 to mark all our entry points down. Bugfix on 0.1.2.x.
7711 - Fix handling of hex nicknames when answering controller requests for
7712 networkstatus by name, or when deciding whether to warn about unknown
7713 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
7714 - Fix a couple of hard-to-trigger autoconf problems that could result
7715 in really weird results on platforms whose sys/types.h files define
7716 nonstandard integer types. Bugfix on 0.1.2.x.
7717 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
7718 - Don't crash on name lookup when we have no current consensus. Fixes
7719 bug 538; bugfix on 0.2.0.x.
7720 - Only Tors that want to mirror the v2 directory info should
7721 create the "cached-status" directory in their datadir. (All Tors
7722 used to create it.) Bugfix on 0.2.0.9-alpha.
7723 - Directory authorities should only automatically download Extra Info
7724 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
7727 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
7728 consumers. (We already do this on HUP.)
7729 - Authorities and caches fetch the v2 networkstatus documents
7730 less often, now that v3 is encouraged.
7731 - Add a new config option BridgeRelay that specifies you want to
7732 be a bridge relay. Right now the only difference is that it makes
7733 you answer begin_dir requests, and it makes you cache dir info,
7734 even if your DirPort isn't on.
7735 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
7736 ask about source, timestamp of arrival, purpose, etc. We need
7737 something like this to help Vidalia not do GeoIP lookups on bridge
7739 - Allow multiple HashedControlPassword config lines, to support
7740 multiple controller passwords.
7741 - Authorities now decide whether they're authoritative for a given
7742 router based on the router's purpose.
7743 - New config options AuthDirBadDir and AuthDirListBadDirs for
7744 authorities to mark certain relays as "bad directories" in the
7745 networkstatus documents. Also supports the "!baddir" directive in
7746 the approved-routers file.
7749 Changes in version 0.2.0.12-alpha - 2007-11-16
7750 This twelfth development snapshot fixes some more build problems as
7751 well as a few minor bugs.
7754 - Make it build on OpenBSD again. Patch from tup.
7755 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
7756 package-building for Red Hat, OS X, etc.
7758 o Minor bugfixes (on 0.1.2.x):
7759 - Changing the ExitPolicyRejectPrivate setting should cause us to
7760 rebuild our server descriptor.
7762 o Minor bugfixes (on 0.2.0.x):
7763 - When we're lacking a consensus, don't try to perform rendezvous
7764 operations. Reported by Karsten Loesing.
7765 - Fix a small memory leak whenever we decide against using a
7766 newly picked entry guard. Reported by Mike Perry.
7767 - When authorities detected more than two relays running on the same
7768 IP address, they were clearing all the status flags but forgetting
7769 to clear the "hsdir" flag. So clients were being told that a
7770 given relay was the right choice for a v2 hsdir lookup, yet they
7771 never had its descriptor because it was marked as 'not running'
7773 - If we're trying to fetch a bridge descriptor and there's no way
7774 the bridge authority could help us (for example, we don't know
7775 a digest, or there is no bridge authority), don't be so eager to
7776 fall back to asking the bridge authority.
7777 - If we're using bridges or have strictentrynodes set, and our
7778 chosen exit is in the same family as all our bridges/entry guards,
7779 then be flexible about families.
7782 - When we negotiate a v2 link-layer connection (not yet implemented),
7783 accept RELAY_EARLY cells and turn them into RELAY cells if we've
7784 negotiated a v1 connection for their next step. Initial code for
7788 Changes in version 0.2.0.11-alpha - 2007-11-12
7789 This eleventh development snapshot fixes some build problems with
7790 the previous snapshot. It also includes a more secure-by-default exit
7791 policy for relays, fixes an enormous memory leak for exit relays, and
7792 fixes another bug where servers were falling out of the directory list.
7795 - Exit policies now reject connections that are addressed to a
7796 relay's public (external) IP address too, unless
7797 ExitPolicyRejectPrivate is turned off. We do this because too
7798 many relays are running nearby to services that trust them based
7799 on network address. Bugfix on 0.1.2.x.
7802 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7803 on every successful resolve. Reported by Mike Perry; bugfix
7805 - On authorities, never downgrade to old router descriptors simply
7806 because they're listed in the consensus. This created a catch-22
7807 where we wouldn't list a new descriptor because there was an
7808 old one in the consensus, and we couldn't get the new one in the
7809 consensus because we wouldn't list it. Possible fix for bug 548.
7810 Also, this might cause bug 543 to appear on authorities; if so,
7811 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
7813 o Packaging fixes on 0.2.0.10-alpha:
7814 - We were including instructions about what to do with the
7815 src/config/fallback-consensus file, but we weren't actually
7816 including it in the tarball. Disable all of that for now.
7819 - Allow people to say PreferTunnelledDirConns rather than
7820 PreferTunneledDirConns, for those alternate-spellers out there.
7823 - Don't reevaluate all the information from our consensus document
7824 just because we've downloaded a v2 networkstatus that we intend
7825 to cache. Fixes bug 545; bugfix on 0.2.0.x.
7828 Changes in version 0.2.0.10-alpha - 2007-11-10
7829 This tenth development snapshot adds a third v3 directory authority
7830 run by Mike Perry, adds most of Karsten Loesing's new hidden service
7831 descriptor format, fixes a bad crash bug and new bridge bugs introduced
7832 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
7833 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
7834 addresses many more minor issues.
7836 o New directory authorities:
7837 - Set up ides (run by Mike Perry) as the third v3 directory authority.
7840 - Allow tunnelled directory connections to ask for an encrypted
7841 "begin_dir" connection or an anonymized "uses a full Tor circuit"
7842 connection independently. Now we can make anonymized begin_dir
7843 connections for (e.g.) more secure hidden service posting and
7845 - More progress on proposal 114: code from Karsten Loesing to
7846 implement new hidden service descriptor format.
7847 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
7848 accommodate the growing number of servers that use the default
7849 and are reaching it.
7850 - Directory authorities use a new formula for selecting which nodes
7851 to advertise as Guards: they must be in the top 7/8 in terms of
7852 how long we have known about them, and above the median of those
7853 nodes in terms of weighted fractional uptime.
7854 - Make "not enough dir info yet" warnings describe *why* Tor feels
7855 it doesn't have enough directory info yet.
7858 - Stop servers from crashing if they set a Family option (or
7859 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
7861 - Make bridge users work again -- the move to v3 directories in
7862 0.2.0.9-alpha had introduced a number of bugs that made bridges
7863 no longer work for clients.
7864 - When the clock jumps forward a lot, do not allow the bandwidth
7865 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
7867 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
7868 - When the consensus lists a router descriptor that we previously were
7869 mirroring, but that we considered non-canonical, reload the
7870 descriptor as canonical. This fixes bug 543 where Tor servers
7871 would start complaining after a few days that they don't have
7872 enough directory information to build a circuit.
7873 - Consider replacing the current consensus when certificates arrive
7874 that make the pending consensus valid. Previously, we were only
7875 considering replacement when the new certs _didn't_ help.
7876 - Fix an assert error on startup if we didn't already have the
7877 consensus and certs cached in our datadirectory: we were caching
7878 the consensus in consensus_waiting_for_certs but then free'ing it
7880 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
7881 Request) if we need more v3 certs but we've already got pending
7882 requests for all of them.
7883 - Correctly back off from failing certificate downloads. Fixes
7885 - Authorities don't vote on the Running flag if they have been running
7886 for less than 30 minutes themselves. Fixes bug 547, where a newly
7887 started authority would vote that everyone was down.
7890 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
7891 it, it had no AES, and it hasn't seen any security patches since
7895 - Clients now hold circuitless TLS connections open for 1.5 times
7896 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
7897 rebuild a new circuit over them within that timeframe. Previously,
7898 they held them open only for KeepalivePeriod (5 minutes).
7899 - Use "If-Modified-Since" to avoid retrieving consensus
7900 networkstatuses that we already have.
7901 - When we have no consensus, check FallbackNetworkstatusFile (defaults
7902 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
7903 we start knowing some directory caches.
7904 - When we receive a consensus from the future, warn about skew.
7905 - Improve skew reporting: try to give the user a better log message
7906 about how skewed they are, and how much this matters.
7907 - When we have a certificate for an authority, believe that
7908 certificate's claims about the authority's IP address.
7909 - New --quiet command-line option to suppress the default console log.
7910 Good in combination with --hash-password.
7911 - Authorities send back an X-Descriptor-Not-New header in response to
7912 an accepted-but-discarded descriptor upload. Partially implements
7914 - Make the log message for "tls error. breaking." more useful.
7915 - Better log messages about certificate downloads, to attempt to
7916 track down the second incarnation of bug 546.
7918 o Minor features (bridges):
7919 - If bridge users set UpdateBridgesFromAuthority, but the digest
7920 they ask for is a 404 from the bridge authority, they now fall
7921 back to trying the bridge directly.
7922 - Bridges now use begin_dir to publish their server descriptor to
7923 the bridge authority, even when they haven't set TunnelDirConns.
7925 o Minor features (controller):
7926 - When reporting clock skew, and we know that the clock is _at least
7927 as skewed_ as some value, but we don't know the actual value,
7928 report the value as a "minimum skew."
7931 - Update linux-tor-prio.sh script to allow QoS based on the uid of
7932 the Tor process. Patch from Marco Bonetti with tweaks from Mike
7936 - Refuse to start if both ORPort and UseBridges are set. Bugfix
7937 on 0.2.0.x, suggested by Matt Edman.
7938 - Don't stop fetching descriptors when FetchUselessDescriptors is
7939 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
7940 reported by tup and ioerror.
7941 - Better log message on vote from unknown authority.
7942 - Don't log "Launching 0 request for 0 router" message.
7944 o Minor bugfixes (memory leaks):
7945 - Stop leaking memory every time we parse a v3 certificate. Bugfix
7947 - Stop leaking memory every time we load a v3 certificate. Bugfix
7948 on 0.2.0.1-alpha. Fixes bug 536.
7949 - Stop leaking a cached networkstatus on exit. Bugfix on
7951 - Stop leaking voter information every time we free a consensus.
7952 Bugfix on 0.2.0.3-alpha.
7953 - Stop leaking signed data every time we check a voter signature.
7954 Bugfix on 0.2.0.3-alpha.
7955 - Stop leaking a signature every time we fail to parse a consensus or
7956 a vote. Bugfix on 0.2.0.3-alpha.
7957 - Stop leaking v2_download_status_map on shutdown. Bugfix on
7959 - Stop leaking conn->nickname every time we make a connection to a
7960 Tor relay without knowing its expected identity digest (e.g. when
7961 using bridges). Bugfix on 0.2.0.3-alpha.
7963 - Minor bugfixes (portability):
7964 - Run correctly on platforms where rlim_t is larger than unsigned
7965 long, and/or where the real limit for number of open files is
7966 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
7967 particular, these may be needed for OS X 10.5.
7970 Changes in version 0.1.2.18 - 2007-10-28
7971 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
7972 hidden service introduction that were causing huge delays, and a big
7973 bug that was causing some servers to disappear from the network status
7974 lists for a few hours each day.
7976 o Major bugfixes (crashes):
7977 - If a connection is shut down abruptly because of something that
7978 happened inside connection_flushed_some(), do not call
7979 connection_finished_flushing(). Should fix bug 451:
7980 "connection_stop_writing: Assertion conn->write_event failed"
7981 Bugfix on 0.1.2.7-alpha.
7982 - Fix possible segfaults in functions called from
7983 rend_process_relay_cell().
7985 o Major bugfixes (hidden services):
7986 - Hidden services were choosing introduction points uniquely by
7987 hexdigest, but when constructing the hidden service descriptor
7988 they merely wrote the (potentially ambiguous) nickname.
7989 - Clients now use the v2 intro format for hidden service
7990 connections: they specify their chosen rendezvous point by identity
7991 digest rather than by (potentially ambiguous) nickname. These
7992 changes could speed up hidden service connections dramatically.
7994 o Major bugfixes (other):
7995 - Stop publishing a new server descriptor just because we get a
7996 HUP signal. This led (in a roundabout way) to some servers getting
7997 dropped from the networkstatus lists for a few hours each day.
7998 - When looking for a circuit to cannibalize, consider family as well
7999 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8000 circuit cannibalization).
8001 - When a router wasn't listed in a new networkstatus, we were leaving
8002 the flags for that router alone -- meaning it remained Named,
8003 Running, etc -- even though absence from the networkstatus means
8004 that it shouldn't be considered to exist at all anymore. Now we
8005 clear all the flags for routers that fall out of the networkstatus
8006 consensus. Fixes bug 529.
8009 - Don't try to access (or alter) the state file when running
8010 --list-fingerprint or --verify-config or --hash-password. Resolves
8012 - When generating information telling us how to extend to a given
8013 router, do not try to include the nickname if it is
8014 absent. Resolves bug 467.
8015 - Fix a user-triggerable segfault in expand_filename(). (There isn't
8016 a way to trigger this remotely.)
8017 - When sending a status event to the controller telling it that an
8018 OR address is reachable, set the port correctly. (Previously we
8019 were reporting the dir port.)
8020 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8021 command. Bugfix on 0.1.2.17.
8022 - When loading bandwidth history, do not believe any information in
8023 the future. Fixes bug 434.
8024 - When loading entry guard information, do not believe any information
8026 - When we have our clock set far in the future and generate an
8027 onion key, then re-set our clock to be correct, we should not stop
8028 the onion key from getting rotated.
8029 - On some platforms, accept() can return a broken address. Detect
8030 this more quietly, and deal accordingly. Fixes bug 483.
8031 - It's not actually an error to find a non-pending entry in the DNS
8032 cache when canceling a pending resolve. Don't log unless stuff
8033 is fishy. Resolves bug 463.
8034 - Don't reset trusted dir server list when we set a configuration
8035 option. Patch from Robert Hogan.
8036 - Don't try to create the datadir when running --verify-config or
8037 --hash-password. Resolves bug 540.
8040 Changes in version 0.2.0.9-alpha - 2007-10-24
8041 This ninth development snapshot switches clients to the new v3 directory
8042 system; allows servers to be listed in the network status even when they
8043 have the same nickname as a registered server; and fixes many other
8044 bugs including a big one that was causing some servers to disappear
8045 from the network status lists for a few hours each day.
8047 o Major features (directory system):
8048 - Clients now download v3 consensus networkstatus documents instead
8049 of v2 networkstatus documents. Clients and caches now base their
8050 opinions about routers on these consensus documents. Clients only
8051 download router descriptors listed in the consensus.
8052 - Authorities now list servers who have the same nickname as
8053 a different named server, but list them with a new flag,
8054 "Unnamed". Now we can list servers that happen to pick the same
8055 nickname as a server that registered two years ago and then
8056 disappeared. Partially implements proposal 122.
8057 - If the consensus lists a router as "Unnamed", the name is assigned
8058 to a different router: do not identify the router by that name.
8059 Partially implements proposal 122.
8060 - Authorities can now come to a consensus on which method to use to
8061 compute the consensus. This gives us forward compatibility.
8064 - Stop publishing a new server descriptor just because we HUP or
8065 when we find our DirPort to be reachable but won't actually publish
8066 it. New descriptors without any real changes are dropped by the
8067 authorities, and can screw up our "publish every 18 hours" schedule.
8069 - When a router wasn't listed in a new networkstatus, we were leaving
8070 the flags for that router alone -- meaning it remained Named,
8071 Running, etc -- even though absence from the networkstatus means
8072 that it shouldn't be considered to exist at all anymore. Now we
8073 clear all the flags for routers that fall out of the networkstatus
8074 consensus. Fixes bug 529; bugfix on 0.1.2.x.
8075 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
8076 extrainfo documents and then discard them immediately for not
8077 matching the latest router. Bugfix on 0.2.0.1-alpha.
8079 o Minor features (v3 directory protocol):
8080 - Allow tor-gencert to generate a new certificate without replacing
8082 - Allow certificates to include an address.
8083 - When we change our directory-cache settings, reschedule all voting
8084 and download operations.
8085 - Reattempt certificate downloads immediately on failure, as long as
8086 we haven't failed a threshold number of times yet.
8087 - Delay retrying consensus downloads while we're downloading
8088 certificates to verify the one we just got. Also, count getting a
8089 consensus that we already have (or one that isn't valid) as a failure,
8090 and count failing to get the certificates after 20 minutes as a
8092 - Build circuits and download descriptors even if our consensus is a
8093 little expired. (This feature will go away once authorities are
8096 o Minor features (router descriptor cache):
8097 - If we find a cached-routers file that's been sitting around for more
8098 than 28 days unmodified, then most likely it's a leftover from
8099 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
8101 - When we (as a cache) download a descriptor because it was listed
8102 in a consensus, remember when the consensus was supposed to expire,
8103 and don't expire the descriptor until then.
8105 o Minor features (performance):
8106 - Call routerlist_remove_old_routers() much less often. This should
8107 speed startup, especially on directory caches.
8108 - Don't try to launch new descriptor downloads quite so often when we
8109 already have enough directory information to build circuits.
8110 - Base64 decoding was actually showing up on our profile when parsing
8111 the initial descriptor file; switch to an in-process all-at-once
8112 implementation that's about 3.5x times faster than calling out to
8115 o Minor features (compilation):
8116 - Detect non-ASCII platforms (if any still exist) and refuse to
8117 build there: some of our code assumes that 'A' is 65 and so on.
8119 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
8120 - Make the "next period" votes into "current period" votes immediately
8121 after publishing the consensus; avoid a heisenbug that made them
8122 stick around indefinitely.
8123 - When we discard a vote as a duplicate, do not report this as
8125 - Treat missing v3 keys or certificates as an error when running as a
8126 v3 directory authority.
8127 - When we're configured to be a v3 authority, but we're only listed
8128 as a non-v3 authority in our DirServer line for ourself, correct
8130 - If an authority doesn't have a qualified hostname, just put
8131 its address in the vote. This fixes the problem where we referred to
8132 "moria on moria:9031."
8133 - Distinguish between detached signatures for the wrong period, and
8134 detached signatures for a divergent vote.
8135 - Fix a small memory leak when computing a consensus.
8136 - When there's no concensus, we were forming a vote every 30
8137 minutes, but writing the "valid-after" line in our vote based
8138 on our configured V3AuthVotingInterval: so unless the intervals
8139 matched up, we immediately rejected our own vote because it didn't
8140 start at the voting interval that caused us to construct a vote.
8142 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
8143 - Delete unverified-consensus when the real consensus is set.
8144 - Consider retrying a consensus networkstatus fetch immediately
8145 after one fails: don't wait 60 seconds to notice.
8146 - When fetching a consensus as a cache, wait until a newer consensus
8147 should exist before trying to replace the current one.
8148 - Use a more forgiving schedule for retrying failed consensus
8149 downloads than for other types.
8151 o Minor bugfixes (other directory issues):
8152 - Correct the implementation of "download votes by digest." Bugfix on
8154 - Authorities no longer send back "400 you're unreachable please fix
8155 it" errors to Tor servers that aren't online all the time. We're
8156 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
8158 o Minor bugfixes (controller):
8159 - Don't reset trusted dir server list when we set a configuration
8160 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
8161 - Respond to INT and TERM SIGNAL commands before we execute the
8162 signal, in case the signal shuts us down. We had a patch in
8163 0.1.2.1-alpha that tried to do this by queueing the response on
8164 the connection's buffer before shutting down, but that really
8165 isn't the same thing at all. Bug located by Matt Edman.
8167 o Minor bugfixes (misc):
8168 - Correctly check for bad options to the "PublishServerDescriptor"
8169 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
8170 - Stop leaking memory on failing case of base32_decode, and make
8171 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
8172 - Don't try to download extrainfo documents when we're trying to
8173 fetch enough directory info to build a circuit: having enough
8174 info should get priority. Bugfix on 0.2.0.x.
8175 - Don't complain that "your server has not managed to confirm that its
8176 ports are reachable" if we haven't been able to build any circuits
8177 yet. Bug found by spending four hours without a v3 consensus. Bugfix
8179 - Detect the reason for failing to mmap a descriptor file we just
8180 wrote, and give a more useful log message. Fixes bug 533. Bugfix
8183 o Code simplifications and refactoring:
8184 - Remove support for the old bw_accounting file: we've been storing
8185 bandwidth accounting information in the state file since
8186 0.1.2.5-alpha. This may result in bandwidth accounting errors
8187 if you try to upgrade from 0.1.1.x or earlier, or if you try to
8188 downgrade to 0.1.1.x or earlier.
8189 - New convenience code to locate a file within the DataDirectory.
8190 - Move non-authority functionality out of dirvote.c.
8191 - Refactor the arguments for router_pick_{directory_|trusteddir}server
8192 so that they all take the same named flags.
8195 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
8196 Unix users an easy way to script their Tor process (e.g. by
8197 adjusting bandwidth based on the time of the day).
8200 Changes in version 0.2.0.8-alpha - 2007-10-12
8201 This eighth development snapshot fixes a crash bug that's been bothering
8202 us since February 2007, lets bridge authorities store a list of bridge
8203 descriptors they've seen, gets v3 directory voting closer to working,
8204 starts caching v3 directory consensus documents on directory mirrors,
8205 and fixes a variety of smaller issues including some minor memory leaks.
8207 o Major features (router descriptor cache):
8208 - Store routers in a file called cached-descriptors instead of in
8209 cached-routers. Initialize cached-descriptors from cached-routers
8210 if the old format is around. The new format allows us to store
8211 annotations along with descriptors.
8212 - Use annotations to record the time we received each descriptor, its
8213 source, and its purpose.
8214 - Disable the SETROUTERPURPOSE controller command: it is now
8216 - Controllers should now specify cache=no or cache=yes when using
8217 the +POSTDESCRIPTOR command.
8218 - Bridge authorities now write bridge descriptors to disk, meaning
8219 we can export them to other programs and begin distributing them
8222 o Major features (directory authorities):
8223 - When a v3 authority is missing votes or signatures, it now tries
8225 - Directory authorities track weighted fractional uptime as well as
8226 weighted mean-time-between failures. WFU is suitable for deciding
8227 whether a node is "usually up", while MTBF is suitable for deciding
8228 whether a node is "likely to stay up." We need both, because
8229 "usually up" is a good requirement for guards, while "likely to
8230 stay up" is a good requirement for long-lived connections.
8232 o Major features (v3 directory system):
8233 - Caches now download v3 network status documents as needed,
8234 and download the descriptors listed in them.
8235 - All hosts now attempt to download and keep fresh v3 authority
8236 certificates, and re-attempt after failures.
8237 - More internal-consistency checks for vote parsing.
8239 o Major bugfixes (crashes):
8240 - If a connection is shut down abruptly because of something that
8241 happened inside connection_flushed_some(), do not call
8242 connection_finished_flushing(). Should fix bug 451. Bugfix on
8245 o Major bugfixes (performance):
8246 - Fix really bad O(n^2) performance when parsing a long list of
8247 routers: Instead of searching the entire list for an "extra-info "
8248 string which usually wasn't there, once for every routerinfo
8249 we read, just scan lines forward until we find one we like.
8251 - When we add data to a write buffer in response to the data on that
8252 write buffer getting low because of a flush, do not consider the
8253 newly added data as a candidate for immediate flushing, but rather
8254 make it wait until the next round of writing. Otherwise, we flush
8255 and refill recursively, and a single greedy TLS connection can
8256 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
8258 o Minor features (v3 authority system):
8259 - Add more ways for tools to download the votes that lead to the
8261 - Send a 503 when low on bandwidth and a vote, consensus, or
8262 certificate is requested.
8263 - If-modified-since is now implemented properly for all kinds of
8264 certificate requests.
8266 o Minor bugfixes (network statuses):
8267 - Tweak the implementation of proposal 109 slightly: allow at most
8268 two Tor servers on the same IP address, except if it's the location
8269 of a directory authority, in which case allow five. Bugfix on
8272 o Minor bugfixes (controller):
8273 - When sending a status event to the controller telling it that an
8274 OR address is reachable, set the port correctly. (Previously we
8275 were reporting the dir port.) Bugfix on 0.1.2.x.
8277 o Minor bugfixes (v3 directory system):
8278 - Fix logic to look up a cert by its signing key digest. Bugfix on
8280 - Only change the reply to a vote to "OK" if it's not already
8281 set. This gets rid of annoying "400 OK" log messages, which may
8282 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
8283 - When we get a valid consensus, recompute the voting schedule.
8284 - Base the valid-after time of a vote on the consensus voting
8285 schedule, not on our preferred schedule.
8286 - Make the return values and messages from signature uploads and
8287 downloads more sensible.
8288 - Fix a memory leak when serving votes and consensus documents, and
8289 another when serving certificates.
8291 o Minor bugfixes (performance):
8292 - Use a slightly simpler string hashing algorithm (copying Python's
8293 instead of Java's) and optimize our digest hashing algorithm to take
8294 advantage of 64-bit platforms and to remove some possibly-costly
8296 - Fix a minor memory leak whenever we parse guards from our state
8297 file. Bugfix on 0.2.0.7-alpha.
8298 - Fix a minor memory leak whenever we write out a file. Bugfix on
8300 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8301 command. Bugfix on 0.2.0.5-alpha.
8303 o Minor bugfixes (portability):
8304 - On some platforms, accept() can return a broken address. Detect
8305 this more quietly, and deal accordingly. Fixes bug 483.
8306 - Stop calling tor_strlower() on uninitialized memory in some cases.
8307 Bugfix in 0.2.0.7-alpha.
8309 o Minor bugfixes (usability):
8310 - Treat some 403 responses from directory servers as INFO rather than
8311 WARN-severity events.
8312 - It's not actually an error to find a non-pending entry in the DNS
8313 cache when canceling a pending resolve. Don't log unless stuff is
8314 fishy. Resolves bug 463.
8316 o Minor bugfixes (anonymity):
8317 - Never report that we've used more bandwidth than we're willing to
8318 relay: it leaks how much non-relay traffic we're using. Resolves
8320 - When looking for a circuit to cannibalize, consider family as well
8321 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8322 circuit cannibalization).
8324 o Code simplifications and refactoring:
8325 - Make a bunch of functions static. Remove some dead code.
8326 - Pull out about a third of the really big routerlist.c; put it in a
8327 new module, networkstatus.c.
8328 - Merge the extra fields in local_routerstatus_t back into
8329 routerstatus_t: we used to need one routerstatus_t for each
8330 authority's opinion, plus a local_routerstatus_t for the locally
8331 computed consensus opinion. To save space, we put the locally
8332 modified fields into local_routerstatus_t, and only the common
8333 stuff into routerstatus_t. But once v3 directories are in use,
8334 clients and caches will no longer need to hold authority opinions;
8335 thus, the rationale for keeping the types separate is now gone.
8336 - Make the code used to reschedule and reattempt downloads more
8338 - Turn all 'Are we a directory server/mirror?' logic into a call to
8340 - Remove the code to generate the oldest (v1) directory format.
8341 The code has been disabled since 0.2.0.5-alpha.
8344 Changes in version 0.2.0.7-alpha - 2007-09-21
8345 This seventh development snapshot makes bridges work again, makes bridge
8346 authorities work for the first time, fixes two huge performance flaws
8347 in hidden services, and fixes a variety of minor issues.
8349 o New directory authorities:
8350 - Set up moria1 and tor26 as the first v3 directory authorities. See
8351 doc/spec/dir-spec.txt for details on the new directory design.
8353 o Major bugfixes (crashes):
8354 - Fix possible segfaults in functions called from
8355 rend_process_relay_cell(). Bugfix on 0.1.2.x.
8357 o Major bugfixes (bridges):
8358 - Fix a bug that made servers send a "404 Not found" in response to
8359 attempts to fetch their server descriptor. This caused Tor servers
8360 to take many minutes to establish reachability for their DirPort,
8361 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
8362 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
8363 users configure that and specify a bridge with an identity
8364 fingerprint, now they will lookup the bridge descriptor at the
8365 default bridge authority via a one-hop tunnel, but once circuits
8366 are established they will switch to a three-hop tunnel for later
8367 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
8369 o Major bugfixes (hidden services):
8370 - Hidden services were choosing introduction points uniquely by
8371 hexdigest, but when constructing the hidden service descriptor
8372 they merely wrote the (potentially ambiguous) nickname.
8373 - Clients now use the v2 intro format for hidden service
8374 connections: they specify their chosen rendezvous point by identity
8375 digest rather than by (potentially ambiguous) nickname. Both
8376 are bugfixes on 0.1.2.x, and they could speed up hidden service
8377 connections dramatically. Thanks to Karsten Loesing.
8379 o Minor features (security):
8380 - As a client, do not believe any server that tells us that an
8381 address maps to an internal address space.
8382 - Make it possible to enable HashedControlPassword and
8383 CookieAuthentication at the same time.
8385 o Minor features (guard nodes):
8386 - Tag every guard node in our state file with the version that
8387 we believe added it, or with our own version if we add it. This way,
8388 if a user temporarily runs an old version of Tor and then switches
8389 back to a new one, she doesn't automatically lose her guards.
8391 o Minor features (speed):
8392 - When implementing AES counter mode, update only the portions of the
8393 counter buffer that need to change, and don't keep separate
8394 network-order and host-order counters when they are the same (i.e.,
8395 on big-endian hosts.)
8397 o Minor features (controller):
8398 - Accept LF instead of CRLF on controller, since some software has a
8399 hard time generating real Internet newlines.
8400 - Add GETINFO values for the server status events
8401 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
8405 - Routers no longer include bandwidth-history lines in their
8406 descriptors; this information is already available in extra-info
8407 documents, and including it in router descriptors took up 60%
8408 (!) of compressed router descriptor downloads. Completes
8409 implementation of proposal 104.
8410 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
8411 and TorControl.py, as they use the old v0 controller protocol,
8412 and are obsoleted by TorFlow anyway.
8413 - Drop support for v1 rendezvous descriptors, since we never used
8414 them anyway, and the code has probably rotted by now. Based on
8415 patch from Karsten Loesing.
8416 - On OSX, stop warning the user that kqueue support in libevent is
8417 "experimental", since it seems to have worked fine for ages.
8420 - When generating information telling us how to extend to a given
8421 router, do not try to include the nickname if it is absent. Fixes
8422 bug 467. Bugfix on 0.2.0.3-alpha.
8423 - Fix a user-triggerable (but not remotely-triggerable) segfault
8424 in expand_filename(). Bugfix on 0.1.2.x.
8425 - Fix a memory leak when freeing incomplete requests from DNSPort.
8426 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
8427 - Don't try to access (or alter) the state file when running
8428 --list-fingerprint or --verify-config or --hash-password. (Resolves
8429 bug 499.) Bugfix on 0.1.2.x.
8430 - Servers used to decline to publish their DirPort if their
8431 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
8432 were below a threshold. Now they only look at BandwidthRate and
8433 RelayBandwidthRate. Bugfix on 0.1.2.x.
8434 - Remove an optimization in the AES counter-mode code that assumed
8435 that the counter never exceeded 2^68. When the counter can be set
8436 arbitrarily as an IV (as it is by Karsten's new hidden services
8437 code), this assumption no longer holds. Bugfix on 0.1.2.x.
8438 - Resume listing "AUTHORITY" flag for authorities in network status.
8439 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
8441 o Code simplifications and refactoring:
8442 - Revamp file-writing logic so we don't need to have the entire
8443 contents of a file in memory at once before we write to disk. Tor,
8445 - Turn "descriptor store" into a full-fledged type.
8446 - Move all NT services code into a separate source file.
8447 - Unify all code that computes medians, percentile elements, etc.
8448 - Get rid of a needless malloc when parsing address policies.
8451 Changes in version 0.1.2.17 - 2007-08-30
8452 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
8453 X bundles. Vidalia 0.0.14 makes authentication required for the
8454 ControlPort in the default configuration, which addresses important
8455 security risks. Everybody who uses Vidalia (or another controller)
8458 In addition, this Tor update fixes major load balancing problems with
8459 path selection, which should speed things up a lot once many people
8462 o Major bugfixes (security):
8463 - We removed support for the old (v0) control protocol. It has been
8464 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
8465 become more of a headache than it's worth.
8467 o Major bugfixes (load balancing):
8468 - When choosing nodes for non-guard positions, weight guards
8469 proportionally less, since they already have enough load. Patch
8471 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8472 will allow fast Tor servers to get more attention.
8473 - When we're upgrading from an old Tor version, forget our current
8474 guards and pick new ones according to the new weightings. These
8475 three load balancing patches could raise effective network capacity
8476 by a factor of four. Thanks to Mike Perry for measurements.
8478 o Major bugfixes (stream expiration):
8479 - Expire not-yet-successful application streams in all cases if
8480 they've been around longer than SocksTimeout. Right now there are
8481 some cases where the stream will live forever, demanding a new
8482 circuit every 15 seconds. Fixes bug 454; reported by lodger.
8484 o Minor features (controller):
8485 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8486 is valid before any authentication has been received. It tells
8487 a controller what kind of authentication is expected, and what
8488 protocol is spoken. Implements proposal 119.
8490 o Minor bugfixes (performance):
8491 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
8492 greatly speeding up loading cached-routers from disk on startup.
8493 - Disable sentinel-based debugging for buffer code: we squashed all
8494 the bugs that this was supposed to detect a long time ago, and now
8495 its only effect is to change our buffer sizes from nice powers of
8496 two (which platform mallocs tend to like) to values slightly over
8497 powers of two (which make some platform mallocs sad).
8499 o Minor bugfixes (misc):
8500 - If exit bandwidth ever exceeds one third of total bandwidth, then
8501 use the correct formula to weight exit nodes when choosing paths.
8502 Based on patch from Mike Perry.
8503 - Choose perfectly fairly among routers when choosing by bandwidth and
8504 weighting by fraction of bandwidth provided by exits. Previously, we
8505 would choose with only approximate fairness, and correct ourselves
8506 if we ran off the end of the list.
8507 - If we require CookieAuthentication but we fail to write the
8508 cookie file, we would warn but not exit, and end up in a state
8509 where no controller could authenticate. Now we exit.
8510 - If we require CookieAuthentication, stop generating a new cookie
8511 every time we change any piece of our config.
8512 - Refuse to start with certain directory authority keys, and
8513 encourage people using them to stop.
8514 - Terminate multi-line control events properly. Original patch
8516 - Fix a minor memory leak when we fail to find enough suitable
8517 servers to choose a circuit.
8518 - Stop leaking part of the descriptor when we run into a particularly
8519 unparseable piece of it.
8522 Changes in version 0.2.0.6-alpha - 2007-08-26
8523 This sixth development snapshot features a new Vidalia version in the
8524 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
8525 the ControlPort in the default configuration, which addresses important
8528 In addition, this snapshot fixes major load balancing problems
8529 with path selection, which should speed things up a lot once many
8530 people have upgraded. The directory authorities also use a new
8531 mean-time-between-failure approach to tracking which servers are stable,
8532 rather than just looking at the most recent uptime.
8534 o New directory authorities:
8535 - Set up Tonga as the default bridge directory authority.
8538 - Directory authorities now track servers by weighted
8539 mean-times-between-failures. When we have 4 or more days of data,
8540 use measured MTBF rather than declared uptime to decide whether
8541 to call a router Stable. Implements proposal 108.
8543 o Major bugfixes (load balancing):
8544 - When choosing nodes for non-guard positions, weight guards
8545 proportionally less, since they already have enough load. Patch
8547 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8548 will allow fast Tor servers to get more attention.
8549 - When we're upgrading from an old Tor version, forget our current
8550 guards and pick new ones according to the new weightings. These
8551 three load balancing patches could raise effective network capacity
8552 by a factor of four. Thanks to Mike Perry for measurements.
8554 o Major bugfixes (descriptor parsing):
8555 - Handle unexpected whitespace better in malformed descriptors. Bug
8556 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
8559 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
8560 GETINFO for Torstat to use until it can switch to using extrainfos.
8561 - Optionally (if built with -DEXPORTMALLINFO) export the output
8562 of mallinfo via http, as tor/mallinfo.txt. Only accessible
8566 - Do not intermix bridge routers with controller-added
8567 routers. (Bugfix on 0.2.0.x)
8568 - Do not fail with an assert when accept() returns an unexpected
8569 address family. Addresses but does not wholly fix bug 483. (Bugfix
8571 - Let directory authorities startup even when they can't generate
8572 a descriptor immediately, e.g. because they don't know their
8574 - Stop putting the authentication cookie in a file called "0"
8575 in your working directory if you don't specify anything for the
8576 new CookieAuthFile option. Reported by Matt Edman.
8577 - Make it possible to read the PROTOCOLINFO response in a way that
8578 conforms to our control-spec. Reported by Matt Edman.
8579 - Fix a minor memory leak when we fail to find enough suitable
8580 servers to choose a circuit. Bugfix on 0.1.2.x.
8581 - Stop leaking part of the descriptor when we run into a particularly
8582 unparseable piece of it. Bugfix on 0.1.2.x.
8583 - Unmap the extrainfo cache file on exit.
8586 Changes in version 0.2.0.5-alpha - 2007-08-19
8587 This fifth development snapshot fixes compilation on Windows again;
8588 fixes an obnoxious client-side bug that slowed things down and put
8589 extra load on the network; gets us closer to using the v3 directory
8590 voting scheme; makes it easier for Tor controllers to use cookie-based
8591 authentication; and fixes a variety of other bugs.
8594 - Version 1 directories are no longer generated in full. Instead,
8595 authorities generate and serve "stub" v1 directories that list
8596 no servers. This will stop Tor versions 0.1.0.x and earlier from
8597 working, but (for security reasons) nobody should be running those
8600 o Major bugfixes (compilation, 0.2.0.x):
8601 - Try to fix Win32 compilation again: improve checking for IPv6 types.
8602 - Try to fix MSVC compilation: build correctly on platforms that do
8603 not define s6_addr16 or s6_addr32.
8604 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
8607 o Major bugfixes (stream expiration):
8608 - Expire not-yet-successful application streams in all cases if
8609 they've been around longer than SocksTimeout. Right now there are
8610 some cases where the stream will live forever, demanding a new
8611 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
8614 o Minor features (directory servers):
8615 - When somebody requests a list of statuses or servers, and we have
8616 none of those, return a 404 rather than an empty 200.
8618 o Minor features (directory voting):
8619 - Store v3 consensus status consensuses on disk, and reload them
8622 o Minor features (security):
8623 - Warn about unsafe ControlPort configurations.
8624 - Refuse to start with certain directory authority keys, and
8625 encourage people using them to stop.
8627 o Minor features (controller):
8628 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8629 is valid before any authentication has been received. It tells
8630 a controller what kind of authentication is expected, and what
8631 protocol is spoken. Implements proposal 119.
8632 - New config option CookieAuthFile to choose a new location for the
8633 cookie authentication file, and config option
8634 CookieAuthFileGroupReadable to make it group-readable.
8636 o Minor features (unit testing):
8637 - Add command-line arguments to unit-test executable so that we can
8638 invoke any chosen test from the command line rather than having
8639 to run the whole test suite at once; and so that we can turn on
8640 logging for the unit tests.
8642 o Minor bugfixes (on 0.1.2.x):
8643 - If we require CookieAuthentication but we fail to write the
8644 cookie file, we would warn but not exit, and end up in a state
8645 where no controller could authenticate. Now we exit.
8646 - If we require CookieAuthentication, stop generating a new cookie
8647 every time we change any piece of our config.
8648 - When loading bandwidth history, do not believe any information in
8649 the future. Fixes bug 434.
8650 - When loading entry guard information, do not believe any information
8652 - When we have our clock set far in the future and generate an
8653 onion key, then re-set our clock to be correct, we should not stop
8654 the onion key from getting rotated.
8655 - Clean up torrc sample config file.
8656 - Do not automatically run configure from autogen.sh. This
8657 non-standard behavior tended to annoy people who have built other
8660 o Minor bugfixes (on 0.2.0.x):
8661 - Fix a bug with AutomapHostsOnResolve that would always cause
8662 the second request to fail. Bug reported by Kate. Bugfix on
8664 - Fix a bug in ADDRMAP controller replies that would sometimes
8665 try to print a NULL. Patch from tup.
8666 - Read v3 directory authority keys from the right location.
8667 - Numerous bugfixes to directory voting code.
8670 Changes in version 0.1.2.16 - 2007-08-01
8671 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
8672 remote attacker in certain situations to rewrite the user's torrc
8673 configuration file. This can completely compromise anonymity of users
8674 in most configurations, including those running the Vidalia bundles,
8675 TorK, etc. Or worse.
8677 o Major security fixes:
8678 - Close immediately after missing authentication on control port;
8679 do not allow multiple authentication attempts.
8682 Changes in version 0.2.0.4-alpha - 2007-08-01
8683 This fourth development snapshot fixes a critical security vulnerability
8684 for most users, specifically those running Vidalia, TorK, etc. Everybody
8685 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
8687 o Major security fixes:
8688 - Close immediately after missing authentication on control port;
8689 do not allow multiple authentication attempts.
8691 o Major bugfixes (compilation):
8692 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
8695 o Minor features (performance):
8696 - Be even more aggressive about releasing RAM from small
8697 empty buffers. Thanks to our free-list code, this shouldn't be too
8698 performance-intensive.
8699 - Disable sentinel-based debugging for buffer code: we squashed all
8700 the bugs that this was supposed to detect a long time ago, and
8701 now its only effect is to change our buffer sizes from nice
8702 powers of two (which platform mallocs tend to like) to values
8703 slightly over powers of two (which make some platform mallocs sad).
8704 - Log malloc statistics from mallinfo() on platforms where it
8708 Changes in version 0.2.0.3-alpha - 2007-07-29
8709 This third development snapshot introduces new experimental
8710 blocking-resistance features and a preliminary version of the v3
8711 directory voting design, and includes many other smaller features
8715 - The first pieces of our "bridge" design for blocking-resistance
8716 are implemented. People can run bridge directory authorities;
8717 people can run bridges; and people can configure their Tor clients
8718 with a set of bridges to use as the first hop into the Tor network.
8719 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
8721 - Create listener connections before we setuid to the configured
8722 User and Group. Now non-Windows users can choose port values
8723 under 1024, start Tor as root, and have Tor bind those ports
8724 before it changes to another UID. (Windows users could already
8726 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
8727 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
8728 on "vserver" accounts. (Patch from coderman.)
8729 - Be even more aggressive about separating local traffic from relayed
8730 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
8732 o Major features (experimental):
8733 - First cut of code for "v3 dir voting": directory authorities will
8734 vote on a common network status document rather than each publishing
8735 their own opinion. This code needs more testing and more corner-case
8736 handling before it's ready for use.
8739 - Directory authorities now call routers Fast if their bandwidth is
8740 at least 100KB/s, and consider their bandwidth adequate to be a
8741 Guard if it is at least 250KB/s, no matter the medians. This fix
8742 complements proposal 107. [Bugfix on 0.1.2.x]
8743 - Directory authorities now never mark more than 3 servers per IP as
8744 Valid and Running. (Implements proposal 109, by Kevin Bauer and
8746 - Minor change to organizationName and commonName generation
8747 procedures in TLS certificates during Tor handshakes, to invalidate
8748 some earlier censorware approaches. This is not a long-term
8749 solution, but applying it will give us a bit of time to look into
8750 the epidemiology of countermeasures as they spread.
8752 o Major bugfixes (directory):
8753 - Rewrite directory tokenization code to never run off the end of
8754 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
8756 o Minor features (controller):
8757 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
8758 match requests to applications. (Patch from Robert Hogan.)
8759 - Report address and port correctly on connections to DNSPort. (Patch
8761 - Add a RESOLVE command to launch hostname lookups. (Original patch
8763 - Add GETINFO status/enough-dir-info to let controllers tell whether
8764 Tor has downloaded sufficient directory information. (Patch
8766 - You can now use the ControlSocket option to tell Tor to listen for
8767 controller connections on Unix domain sockets on systems that
8768 support them. (Patch from Peter Palfrader.)
8769 - STREAM NEW events are generated for DNSPort requests and for
8770 tunneled directory connections. (Patch from Robert Hogan.)
8771 - New "GETINFO address-mappings/*" command to get address mappings
8772 with expiry information. "addr-mappings/*" is now deprecated.
8775 o Minor features (misc):
8776 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
8778 - The tor-gencert tool for v3 directory authorities now creates all
8779 files as readable to the file creator only, and write-protects
8780 the authority identity key.
8781 - When dumping memory usage, list bytes used in buffer memory
8783 - When running with dmalloc, dump more stats on hup and on exit.
8784 - Directory authorities now fail quickly and (relatively) harmlessly
8785 if they generate a network status document that is somehow
8788 o Traffic load balancing improvements:
8789 - If exit bandwidth ever exceeds one third of total bandwidth, then
8790 use the correct formula to weight exit nodes when choosing paths.
8791 (Based on patch from Mike Perry.)
8792 - Choose perfectly fairly among routers when choosing by bandwidth and
8793 weighting by fraction of bandwidth provided by exits. Previously, we
8794 would choose with only approximate fairness, and correct ourselves
8795 if we ran off the end of the list. [Bugfix on 0.1.2.x]
8797 o Performance improvements:
8798 - Be more aggressive with freeing buffer RAM or putting it on the
8800 - Use Critical Sections rather than Mutexes for synchronizing threads
8801 on win32; Mutexes are heavier-weight, and designed for synchronizing
8804 o Deprecated and removed features:
8805 - RedirectExits is now deprecated.
8806 - Stop allowing address masks that do not correspond to bit prefixes.
8807 We have warned about these for a really long time; now it's time
8808 to reject them. (Patch from croup.)
8810 o Minor bugfixes (directory):
8811 - Fix another crash bug related to extra-info caching. (Bug found by
8812 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
8813 - Directories no longer return a "304 not modified" when they don't
8814 have the networkstatus the client asked for. Also fix a memory
8815 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
8816 - We had accidentally labelled 0.1.2.x directory servers as not
8817 suitable for begin_dir requests, and had labelled no directory
8818 servers as suitable for uploading extra-info documents. [Bugfix
8821 o Minor bugfixes (dns):
8822 - Fix a crash when DNSPort is set more than once. (Patch from Robert
8823 Hogan.) [Bugfix on 0.2.0.2-alpha]
8824 - Add DNSPort connections to the global connection list, so that we
8825 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
8827 - Fix a dangling reference that could lead to a crash when DNSPort is
8828 changed or closed (Patch from Robert Hogan.) [Bugfix on
8831 o Minor bugfixes (controller):
8832 - Provide DNS expiry times in GMT, not in local time. For backward
8833 compatibility, ADDRMAP events only provide GMT expiry in an extended
8834 field. "GETINFO address-mappings" always does the right thing.
8835 - Use CRLF line endings properly in NS events.
8836 - Terminate multi-line control events properly. (Original patch
8837 from tup.) [Bugfix on 0.1.2.x-alpha]
8838 - Do not include spaces in SOURCE_ADDR fields in STREAM
8839 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
8842 Changes in version 0.1.2.15 - 2007-07-17
8843 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
8844 problems, fixes compilation on BSD, and fixes a variety of other
8845 bugs. Everybody should upgrade.
8847 o Major bugfixes (compilation):
8848 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
8850 o Major bugfixes (crashes):
8851 - Try even harder not to dereference the first character after
8852 an mmap(). Reported by lodger.
8853 - Fix a crash bug in directory authorities when we re-number the
8854 routerlist while inserting a new router.
8855 - When the cached-routers file is an even multiple of the page size,
8856 don't run off the end and crash. (Fixes bug 455; based on idea
8858 - Fix eventdns.c behavior on Solaris: It is critical to include
8859 orconfig.h _before_ sys/types.h, so that we can get the expected
8860 definition of _FILE_OFFSET_BITS.
8862 o Major bugfixes (security):
8863 - Fix a possible buffer overrun when using BSD natd support. Bug
8865 - When sending destroy cells from a circuit's origin, don't include
8866 the reason for tearing down the circuit. The spec says we didn't,
8867 and now we actually don't. Reported by lodger.
8868 - Keep streamids from different exits on a circuit separate. This
8869 bug may have allowed other routers on a given circuit to inject
8870 cells into streams. Reported by lodger; fixes bug 446.
8871 - If there's a never-before-connected-to guard node in our list,
8872 never choose any guards past it. This way we don't expand our
8873 guard list unless we need to.
8875 o Minor bugfixes (guard nodes):
8876 - Weight guard selection by bandwidth, so that low-bandwidth nodes
8877 don't get overused as guards.
8879 o Minor bugfixes (directory):
8880 - Correctly count the number of authorities that recommend each
8881 version. Previously, we were under-counting by 1.
8882 - Fix a potential crash bug when we load many server descriptors at
8883 once and some of them make others of them obsolete. Fixes bug 458.
8885 o Minor bugfixes (hidden services):
8886 - Stop tearing down the whole circuit when the user asks for a
8887 connection to a port that the hidden service didn't configure.
8890 o Minor bugfixes (misc):
8891 - On Windows, we were preventing other processes from reading
8892 cached-routers while Tor was running. Reported by janbar.
8893 - Fix a possible (but very unlikely) bug in picking routers by
8894 bandwidth. Add a log message to confirm that it is in fact
8895 unlikely. Patch from lodger.
8896 - Backport a couple of memory leak fixes.
8897 - Backport miscellaneous cosmetic bugfixes.
8900 Changes in version 0.2.0.2-alpha - 2007-06-02
8901 o Major bugfixes on 0.2.0.1-alpha:
8902 - Fix an assertion failure related to servers without extra-info digests.
8903 Resolves bugs 441 and 442.
8905 o Minor features (directory):
8906 - Support "If-Modified-Since" when answering HTTP requests for
8907 directories, running-routers documents, and network-status documents.
8908 (There's no need to support it for router descriptors, since those
8909 are downloaded by descriptor digest.)
8911 o Minor build issues:
8912 - Clear up some MIPSPro compiler warnings.
8913 - When building from a tarball on a machine that happens to have SVK
8914 installed, report the micro-revision as whatever version existed
8915 in the tarball, not as "x".
8918 Changes in version 0.2.0.1-alpha - 2007-06-01
8919 This early development snapshot provides new features for people running
8920 Tor as both a client and a server (check out the new RelayBandwidth
8921 config options); lets Tor run as a DNS proxy; and generally moves us
8922 forward on a lot of fronts.
8924 o Major features, server usability:
8925 - New config options RelayBandwidthRate and RelayBandwidthBurst:
8926 a separate set of token buckets for relayed traffic. Right now
8927 relayed traffic is defined as answers to directory requests, and
8928 OR connections that don't have any local circuits on them.
8930 o Major features, client usability:
8931 - A client-side DNS proxy feature to replace the need for
8932 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
8933 for DNS requests on port 9999, use the Tor network to resolve them
8934 anonymously, and send the reply back like a regular DNS server.
8935 The code still only implements a subset of DNS.
8936 - Make PreferTunneledDirConns and TunnelDirConns work even when
8937 we have no cached directory info. This means Tor clients can now
8938 do all of their connections protected by TLS.
8940 o Major features, performance and efficiency:
8941 - Directory authorities accept and serve "extra info" documents for
8942 routers. These documents contain fields from router descriptors
8943 that aren't usually needed, and that use a lot of excess
8944 bandwidth. Once these fields are removed from router descriptors,
8945 the bandwidth savings should be about 60%. [Partially implements
8947 - Servers upload extra-info documents to any authority that accepts
8948 them. Authorities (and caches that have been configured to download
8949 extra-info documents) download them as needed. [Partially implements
8951 - Change the way that Tor buffers data that it is waiting to write.
8952 Instead of queueing data cells in an enormous ring buffer for each
8953 client->OR or OR->OR connection, we now queue cells on a separate
8954 queue for each circuit. This lets us use less slack memory, and
8955 will eventually let us be smarter about prioritizing different kinds
8957 - Use memory pools to allocate cells with better speed and memory
8958 efficiency, especially on platforms where malloc() is inefficient.
8959 - Stop reading on edge connections when their corresponding circuit
8960 buffers are full; start again as the circuits empty out.
8962 o Major features, other:
8963 - Add an HSAuthorityRecordStats option that hidden service authorities
8964 can use to track statistics of overall hidden service usage without
8965 logging information that would be very useful to an attacker.
8966 - Start work implementing multi-level keys for directory authorities:
8967 Add a standalone tool to generate key certificates. (Proposal 103.)
8970 - Directory authorities now call routers Stable if they have an
8971 uptime of at least 30 days, even if that's not the median uptime
8972 in the network. Implements proposal 107, suggested by Kevin Bauer
8975 o Minor fixes (resource management):
8976 - Count the number of open sockets separately from the number
8977 of active connection_t objects. This will let us avoid underusing
8978 our allocated connection limit.
8979 - We no longer use socket pairs to link an edge connection to an
8980 anonymous directory connection or a DirPort test connection.
8981 Instead, we track the link internally and transfer the data
8982 in-process. This saves two sockets per "linked" connection (at the
8983 client and at the server), and avoids the nasty Windows socketpair()
8985 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
8986 for every single inactive connection_t. Free items from the
8987 4k/16k-buffer free lists when they haven't been used for a while.
8989 o Minor features (build):
8990 - Make autoconf search for libevent, openssl, and zlib consistently.
8991 - Update deprecated macros in configure.in.
8992 - When warning about missing headers, tell the user to let us
8993 know if the compile succeeds anyway, so we can downgrade the
8995 - Include the current subversion revision as part of the version
8996 string: either fetch it directly if we're in an SVN checkout, do
8997 some magic to guess it if we're in an SVK checkout, or use
8998 the last-detected version if we're building from a .tar.gz.
8999 Use this version consistently in log messages.
9001 o Minor features (logging):
9002 - Always prepend "Bug: " to any log message about a bug.
9003 - Put a platform string (e.g. "Linux i686") in the startup log
9004 message, so when people paste just their logs, we know if it's
9005 OpenBSD or Windows or what.
9006 - When logging memory usage, break down memory used in buffers by
9009 o Minor features (directory system):
9010 - New config option V2AuthoritativeDirectory that all directory
9011 authorities should set. This will let future authorities choose
9012 not to serve V2 directory information.
9013 - Directory authorities allow multiple router descriptors and/or extra
9014 info documents to be uploaded in a single go. This will make
9015 implementing proposal 104 simpler.
9017 o Minor features (controller):
9018 - Add a new config option __DisablePredictedCircuits designed for
9019 use by the controller, when we don't want Tor to build any circuits
9021 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
9022 so we can exit from the middle of the circuit.
9023 - Implement "getinfo status/circuit-established".
9024 - Implement "getinfo status/version/..." so a controller can tell
9025 whether the current version is recommended, and whether any versions
9026 are good, and how many authorities agree. (Patch from shibz.)
9028 o Minor features (hidden services):
9029 - Allow multiple HiddenServicePort directives with the same virtual
9030 port; when they occur, the user is sent round-robin to one
9031 of the target ports chosen at random. Partially fixes bug 393 by
9032 adding limited ad-hoc round-robining.
9034 o Minor features (other):
9036 - Add a new AutomapHostsOnResolve option: when it is enabled, any
9037 resolve request for hosts matching a given pattern causes Tor to
9038 generate an internal virtual address mapping for that host. This
9039 allows DNSPort to work sensibly with hidden service users. By
9040 default, .exit and .onion addresses are remapped; the list of
9041 patterns can be reconfigured with AutomapHostsSuffixes.
9042 - Add an "-F" option to tor-resolve to force a resolve for a .onion
9043 address. Thanks to the AutomapHostsOnResolve option, this is no
9044 longer a completely silly thing to do.
9045 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
9046 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
9047 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
9048 minus 1 byte: the actual maximum declared bandwidth.
9051 - Removed support for the old binary "version 0" controller protocol.
9052 This has been deprecated since 0.1.1, and warnings have been issued
9053 since 0.1.2. When we encounter a v0 control message, we now send
9054 back an error and close the connection.
9055 - Remove the old "dns worker" server DNS code: it hasn't been default
9056 since 0.1.2.2-alpha, and all the servers seem to be using the new
9059 o Minor bugfixes (portability):
9060 - Even though Windows is equally happy with / and \ as path separators,
9061 try to use \ consistently on Windows and / consistently on Unix: it
9062 makes the log messages nicer.
9063 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
9064 - Read resolv.conf files correctly on platforms where read() returns
9065 partial results on small file reads.
9067 o Minor bugfixes (directory):
9068 - Correctly enforce that elements of directory objects do not appear
9069 more often than they are allowed to appear.
9070 - When we are reporting the DirServer line we just parsed, we were
9071 logging the second stanza of the key fingerprint, not the first.
9073 o Minor bugfixes (logging):
9074 - When we hit an EOF on a log (probably because we're shutting down),
9075 don't try to remove the log from the list: just mark it as
9076 unusable. (Bulletproofs against bug 222.)
9078 o Minor bugfixes (other):
9079 - In the exitlist script, only consider the most recently published
9080 server descriptor for each server. Also, when the user requests
9081 a list of servers that _reject_ connections to a given address,
9082 explicitly exclude the IPs that also have servers that accept
9083 connections to that address. (Resolves bug 405.)
9084 - Stop allowing hibernating servers to be "stable" or "fast".
9085 - On Windows, we were preventing other processes from reading
9086 cached-routers while Tor was running. (Reported by janbar)
9087 - Make the NodeFamilies config option work. (Reported by
9088 lodger -- it has never actually worked, even though we added it
9090 - Check return values from pthread_mutex functions.
9091 - Don't save non-general-purpose router descriptors to the disk cache,
9092 because we have no way of remembering what their purpose was when
9094 - Add even more asserts to hunt down bug 417.
9095 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
9096 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
9097 Add a log message to confirm that it is in fact unlikely.
9099 o Minor bugfixes (controller):
9100 - Make 'getinfo fingerprint' return a 551 error if we're not a
9101 server, so we match what the control spec claims we do. Reported
9103 - Fix a typo in an error message when extendcircuit fails that
9104 caused us to not follow the \r\n-based delimiter protocol. Reported
9107 o Code simplifications and refactoring:
9108 - Stop passing around circuit_t and crypt_path_t pointers that are
9109 implicit in other procedure arguments.
9110 - Drop the old code to choke directory connections when the
9111 corresponding OR connections got full: thanks to the cell queue
9112 feature, OR conns don't get full any more.
9113 - Make dns_resolve() handle attaching connections to circuits
9114 properly, so the caller doesn't have to.
9115 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
9116 - Keep the connection array as a dynamic smartlist_t, rather than as
9117 a fixed-sized array. This is important, as the number of connections
9118 is becoming increasingly decoupled from the number of sockets.
9121 Changes in version 0.1.2.14 - 2007-05-25
9122 Tor 0.1.2.14 changes the addresses of two directory authorities (this
9123 change especially affects those who serve or use hidden services),
9124 and fixes several other crash- and security-related bugs.
9126 o Directory authority changes:
9127 - Two directory authorities (moria1 and moria2) just moved to new
9128 IP addresses. This change will particularly affect those who serve
9129 or use hidden services.
9131 o Major bugfixes (crashes):
9132 - If a directory server runs out of space in the connection table
9133 as it's processing a begin_dir request, it will free the exit stream
9134 but leave it attached to the circuit, leading to unpredictable
9135 behavior. (Reported by seeess, fixes bug 425.)
9136 - Fix a bug in dirserv_remove_invalid() that would cause authorities
9137 to corrupt memory under some really unlikely scenarios.
9138 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
9139 - Avoid segfaults when reading from mmaped descriptor file. (Reported
9142 o Major bugfixes (security):
9143 - When choosing an entry guard for a circuit, avoid using guards
9144 that are in the same family as the chosen exit -- not just guards
9145 that are exactly the chosen exit. (Reported by lodger.)
9147 o Major bugfixes (resource management):
9148 - If a directory authority is down, skip it when deciding where to get
9149 networkstatus objects or descriptors. Otherwise we keep asking
9150 every 10 seconds forever. Fixes bug 384.
9151 - Count it as a failure if we fetch a valid network-status but we
9152 don't want to keep it. Otherwise we'll keep fetching it and keep
9153 not wanting to keep it. Fixes part of bug 422.
9154 - If all of our dirservers have given us bad or no networkstatuses
9155 lately, then stop hammering them once per minute even when we
9156 think they're failed. Fixes another part of bug 422.
9159 - Actually set the purpose correctly for descriptors inserted with
9161 - When we have k non-v2 authorities in our DirServer config,
9162 we ignored the last k authorities in the list when updating our
9164 - Correctly back-off from requesting router descriptors that we are
9165 having a hard time downloading.
9166 - Read resolv.conf files correctly on platforms where read() returns
9167 partial results on small file reads.
9168 - Don't rebuild the entire router store every time we get 32K of
9169 routers: rebuild it when the journal gets very large, or when
9170 the gaps in the store get very large.
9173 - When routers publish SVN revisions in their router descriptors,
9174 authorities now include those versions correctly in networkstatus
9176 - Warn when using a version of libevent before 1.3b to run a server on
9177 OSX or BSD: these versions interact badly with userspace threads.
9180 Changes in version 0.1.2.13 - 2007-04-24
9181 This release features some major anonymity fixes, such as safer path
9182 selection; better client performance; faster bootstrapping, better
9183 address detection, and better DNS support for servers; write limiting as
9184 well as read limiting to make servers easier to run; and a huge pile of
9185 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
9187 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
9188 of the Freenode IRC network, remembering his patience and vision for
9189 free speech on the Internet.
9192 - Fix a memory leak when we ask for "all" networkstatuses and we
9193 get one we don't recognize.
9194 - Add more asserts to hunt down bug 417.
9195 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
9198 Changes in version 0.1.2.12-rc - 2007-03-16
9200 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
9201 directory information requested inside Tor connections (i.e. via
9202 begin_dir cells). It only triggered when the same connection was
9203 serving other data at the same time. Reported by seeess.
9206 - When creating a circuit via the controller, send a 'launched'
9207 event when we're done, so we follow the spec better.
9210 Changes in version 0.1.2.11-rc - 2007-03-15
9211 o Minor bugfixes (controller), reported by daejees:
9212 - Correct the control spec to match how the code actually responds
9213 to 'getinfo addr-mappings/*'.
9214 - The control spec described a GUARDS event, but the code
9215 implemented a GUARD event. Standardize on GUARD, but let people
9219 Changes in version 0.1.2.10-rc - 2007-03-07
9220 o Major bugfixes (Windows):
9221 - Do not load the NT services library functions (which may not exist)
9222 just to detect if we're a service trying to shut down. Now we run
9223 on Win98 and friends again.
9225 o Minor bugfixes (other):
9226 - Clarify a couple of log messages.
9227 - Fix a misleading socks5 error number.
9230 Changes in version 0.1.2.9-rc - 2007-03-02
9231 o Major bugfixes (Windows):
9232 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
9233 of the usual GCC "%llu". This prevents a bug when saving 64-bit
9234 int configuration values: the high-order 32 bits would get
9235 truncated. In particular, we were being bitten by the default
9236 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
9237 and maybe also bug 397.)
9239 o Minor bugfixes (performance):
9240 - Use OpenSSL's AES implementation on platforms where it's faster.
9241 This could save us as much as 10% CPU usage.
9243 o Minor bugfixes (server):
9244 - Do not rotate onion key immediately after setting it for the first
9247 o Minor bugfixes (directory authorities):
9248 - Stop calling servers that have been hibernating for a long time
9249 "stable". Also, stop letting hibernating or obsolete servers affect
9250 uptime and bandwidth cutoffs.
9251 - Stop listing hibernating servers in the v1 directory.
9253 o Minor bugfixes (hidden services):
9254 - Upload hidden service descriptors slightly less often, to reduce
9255 load on authorities.
9257 o Minor bugfixes (other):
9258 - Fix an assert that could trigger if a controller quickly set then
9259 cleared EntryNodes. Bug found by Udo van den Heuvel.
9260 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
9262 - Fix a potential race condition in the rpm installer. Found by
9264 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
9265 of 2 as indicating that the server is completely bad; it sometimes
9266 means that the server is just bad for the request in question. (may fix
9267 the last of bug 326.)
9268 - Disable encrypted directory connections when we don't have a server
9269 descriptor for the destination. We'll get this working again in
9273 Changes in version 0.1.2.8-beta - 2007-02-26
9274 o Major bugfixes (crashes):
9275 - Stop crashing when the controller asks us to resetconf more than
9276 one config option at once. (Vidalia 0.0.11 does this.)
9277 - Fix a crash that happened on Win98 when we're given command-line
9278 arguments: don't try to load NT service functions from advapi32.dll
9279 except when we need them. (Bug introduced in 0.1.2.7-alpha;
9281 - Fix a longstanding obscure crash bug that could occur when
9282 we run out of DNS worker processes. (Resolves bug 390.)
9284 o Major bugfixes (hidden services):
9285 - Correctly detect whether hidden service descriptor downloads are
9286 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
9288 o Major bugfixes (accounting):
9289 - When we start during an accounting interval before it's time to wake
9290 up, remember to wake up at the correct time. (May fix bug 342.)
9292 o Minor bugfixes (controller):
9293 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
9294 clear the corresponding on_circuit variable, and remember later
9295 that we don't need to send a redundant CLOSED event. Resolves part
9297 - Report events where a resolve succeeded or where we got a socks
9298 protocol error correctly, rather than calling both of them
9300 - Change reported stream target addresses to IP consistently when
9301 we finally get the IP from an exit node.
9302 - Send log messages to the controller even if they happen to be very
9305 o Minor bugfixes (other):
9306 - Display correct results when reporting which versions are
9307 recommended, and how recommended they are. (Resolves bug 383.)
9308 - Improve our estimates for directory bandwidth to be less random:
9309 guess that an unrecognized directory will have the average bandwidth
9310 from all known directories, not that it will have the average
9311 bandwidth from those directories earlier than it on the list.
9312 - If we start a server with ClientOnly 1, then set ClientOnly to 0
9313 and hup, stop triggering an assert based on an empty onion_key.
9314 - On platforms with no working mmap() equivalent, don't warn the
9315 user when cached-routers doesn't exist.
9316 - Warn the user when mmap() [or its equivalent] fails for some reason
9317 other than file-not-found.
9318 - Don't warn the user when cached-routers.new doesn't exist: that's
9319 perfectly fine when starting up for the first time.
9320 - When EntryNodes are configured, rebuild the guard list to contain,
9321 in order: the EntryNodes that were guards before; the rest of the
9322 EntryNodes; the nodes that were guards before.
9323 - Mask out all signals in sub-threads; only the libevent signal
9324 handler should be processing them. This should prevent some crashes
9325 on some machines using pthreads. (Patch from coderman.)
9326 - Fix switched arguments on memset in the implementation of
9327 tor_munmap() for systems with no mmap() call.
9328 - When Tor receives a router descriptor that it asked for, but
9329 no longer wants (because it has received fresh networkstatuses
9330 in the meantime), do not warn the user. Cache the descriptor if
9331 we're a cache; drop it if we aren't.
9332 - Make earlier entry guards _really_ get retried when the network
9334 - On a malformed DNS reply, always give an error to the corresponding
9336 - Build with recent libevents on platforms that do not define the
9337 nonstandard types "u_int8_t" and friends.
9339 o Minor features (controller):
9340 - Warn the user when an application uses the obsolete binary v0
9341 control protocol. We're planning to remove support for it during
9342 the next development series, so it's good to give people some
9344 - Add STREAM_BW events to report per-entry-stream bandwidth
9345 use. (Patch from Robert Hogan.)
9346 - Rate-limit SIGNEWNYM signals in response to controllers that
9347 impolitely generate them for every single stream. (Patch from
9348 mwenge; closes bug 394.)
9349 - Make REMAP stream events have a SOURCE (cache or exit), and
9350 make them generated in every case where we get a successful
9351 connected or resolved cell.
9353 o Minor bugfixes (performance):
9354 - Call router_have_min_dir_info half as often. (This is showing up in
9355 some profiles, but not others.)
9356 - When using GCC, make log_debug never get called at all, and its
9357 arguments never get evaluated, when no debug logs are configured.
9358 (This is showing up in some profiles, but not others.)
9361 - Remove some never-implemented options. Mark PathlenCoinWeight as
9363 - Implement proposal 106: Stop requiring clients to have well-formed
9364 certificates; stop checking nicknames in certificates. (Clients
9365 have certificates so that they can look like Tor servers, but in
9366 the future we might want to allow them to look like regular TLS
9367 clients instead. Nicknames in certificates serve no purpose other
9368 than making our protocol easier to recognize on the wire.)
9369 - Revise messages on handshake failure again to be even more clear about
9370 which are incoming connections and which are outgoing.
9371 - Discard any v1 directory info that's over 1 month old (for
9372 directories) or over 1 week old (for running-routers lists).
9373 - Do not warn when individual nodes in the configuration's EntryNodes,
9374 ExitNodes, etc are down: warn only when all possible nodes
9375 are down. (Fixes bug 348.)
9376 - Always remove expired routers and networkstatus docs before checking
9377 whether we have enough information to build circuits. (Fixes
9379 - Put a lower-bound on MaxAdvertisedBandwidth.
9382 Changes in version 0.1.2.7-alpha - 2007-02-06
9383 o Major bugfixes (rate limiting):
9384 - Servers decline directory requests much more aggressively when
9385 they're low on bandwidth. Otherwise they end up queueing more and
9386 more directory responses, which can't be good for latency.
9387 - But never refuse directory requests from local addresses.
9388 - Fix a memory leak when sending a 503 response for a networkstatus
9390 - Be willing to read or write on local connections (e.g. controller
9391 connections) even when the global rate limiting buckets are empty.
9392 - If our system clock jumps back in time, don't publish a negative
9393 uptime in the descriptor. Also, don't let the global rate limiting
9394 buckets go absurdly negative.
9395 - Flush local controller connection buffers periodically as we're
9396 writing to them, so we avoid queueing 4+ megabytes of data before
9399 o Major bugfixes (NT services):
9400 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
9401 command-line flag so that admins can override the default by saying
9402 "tor --service install --user "SomeUser"". This will not affect
9403 existing installed services. Also, warn the user that the service
9404 will look for its configuration file in the service user's
9405 %appdata% directory. (We can't do the 'hardwire the user's appdata
9406 directory' trick any more, since we may not have read access to that
9409 o Major bugfixes (other):
9410 - Previously, we would cache up to 16 old networkstatus documents
9411 indefinitely, if they came from nontrusted authorities. Now we
9412 discard them if they are more than 10 days old.
9413 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
9415 - Detect and reject malformed DNS responses containing circular
9417 - If exits are rare enough that we're not marking exits as guards,
9418 ignore exit bandwidth when we're deciding the required bandwidth
9420 - When we're handling a directory connection tunneled over Tor,
9421 don't fill up internal memory buffers with all the data we want
9422 to tunnel; instead, only add it if the OR connection that will
9423 eventually receive it has some room for it. (This can lead to
9424 slowdowns in tunneled dir connections; a better solution will have
9427 o Minor bugfixes (dns):
9428 - Add some defensive programming to eventdns.c in an attempt to catch
9429 possible memory-stomping bugs.
9430 - Detect and reject DNS replies containing IPv4 or IPv6 records with
9431 an incorrect number of bytes. (Previously, we would ignore the
9433 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
9434 in the correct order, and doesn't crash.
9435 - Free memory held in recently-completed DNS lookup attempts on exit.
9436 This was not a memory leak, but may have been hiding memory leaks.
9437 - Handle TTL values correctly on reverse DNS lookups.
9438 - Treat failure to parse resolv.conf as an error.
9440 o Minor bugfixes (other):
9441 - Fix crash with "tor --list-fingerprint" (reported by seeess).
9442 - When computing clock skew from directory HTTP headers, consider what
9443 time it was when we finished asking for the directory, not what
9445 - Expire socks connections if they spend too long waiting for the
9446 handshake to finish. Previously we would let them sit around for
9447 days, if the connecting application didn't close them either.
9448 - And if the socks handshake hasn't started, don't send a
9449 "DNS resolve socks failed" handshake reply; just close it.
9450 - Stop using C functions that OpenBSD's linker doesn't like.
9451 - Don't launch requests for descriptors unless we have networkstatuses
9452 from at least half of the authorities. This delays the first
9453 download slightly under pathological circumstances, but can prevent
9454 us from downloading a bunch of descriptors we don't need.
9455 - Do not log IPs with TLS failures for incoming TLS
9456 connections. (Fixes bug 382.)
9457 - If the user asks to use invalid exit nodes, be willing to use
9459 - Stop using the reserved ac_cv namespace in our configure script.
9460 - Call stat() slightly less often; use fstat() when possible.
9461 - Refactor the way we handle pending circuits when an OR connection
9462 completes or fails, in an attempt to fix a rare crash bug.
9463 - Only rewrite a conn's address based on X-Forwarded-For: headers
9464 if it's a parseable public IP address; and stop adding extra quotes
9465 to the resulting address.
9468 - Weight directory requests by advertised bandwidth. Now we can
9469 let servers enable write limiting but still allow most clients to
9470 succeed at their directory requests. (We still ignore weights when
9471 choosing a directory authority; I hope this is a feature.)
9474 - Create a new file ReleaseNotes which was the old ChangeLog. The
9475 new ChangeLog file now includes the summaries for all development
9477 - Check for addresses with invalid characters at the exit as well
9478 as at the client, and warn less verbosely when they fail. You can
9479 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
9480 - Adapt a patch from goodell to let the contrib/exitlist script
9481 take arguments rather than require direct editing.
9482 - Inform the server operator when we decide not to advertise a
9483 DirPort due to AccountingMax enabled or a low BandwidthRate. It
9484 was confusing Zax, so now we're hopefully more helpful.
9485 - Bring us one step closer to being able to establish an encrypted
9486 directory tunnel without knowing a descriptor first. Still not
9487 ready yet. As part of the change, now assume we can use a
9488 create_fast cell if we don't know anything about a router.
9489 - Allow exit nodes to use nameservers running on ports other than 53.
9490 - Servers now cache reverse DNS replies.
9491 - Add an --ignore-missing-torrc command-line option so that we can
9492 get the "use sensible defaults if the configuration file doesn't
9493 exist" behavior even when specifying a torrc location on the command
9496 o Minor features (controller):
9497 - Track reasons for OR connection failure; make these reasons
9498 available via the controller interface. (Patch from Mike Perry.)
9499 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
9500 can learn when clients are sending malformed hostnames to Tor.
9501 - Clean up documentation for controller status events.
9502 - Add a REMAP status to stream events to note that a stream's
9503 address has changed because of a cached address or a MapAddress
9507 Changes in version 0.1.2.6-alpha - 2007-01-09
9509 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
9510 connection handles more than 4 gigs in either direction, we crash.
9511 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
9512 advertised exit node, somebody might try to exit from us when
9513 we're bootstrapping and before we've built our descriptor yet.
9514 Refuse the connection rather than crashing.
9517 - Warn if we (as a server) find that we've resolved an address that we
9518 weren't planning to resolve.
9519 - Warn that using select() on any libevent version before 1.1 will be
9520 unnecessarily slow (even for select()).
9521 - Flush ERR-level controller status events just like we currently
9522 flush ERR-level log events, so that a Tor shutdown doesn't prevent
9523 the controller from learning about current events.
9525 o Minor features (more controller status events):
9526 - Implement EXTERNAL_ADDRESS server status event so controllers can
9527 learn when our address changes.
9528 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
9529 can learn when directories reject our descriptor.
9530 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
9531 can learn when a client application is speaking a non-socks protocol
9533 - Implement DANGEROUS_SOCKS client status event so controllers
9534 can learn when a client application is leaking DNS addresses.
9535 - Implement BUG general status event so controllers can learn when
9536 Tor is unhappy about its internal invariants.
9537 - Implement CLOCK_SKEW general status event so controllers can learn
9538 when Tor thinks the system clock is set incorrectly.
9539 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
9540 server status events so controllers can learn when their descriptors
9541 are accepted by a directory.
9542 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
9543 server status events so controllers can learn about Tor's progress in
9544 deciding whether it's reachable from the outside.
9545 - Implement BAD_LIBEVENT general status event so controllers can learn
9546 when we have a version/method combination in libevent that needs to
9548 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
9549 and DNS_USELESS server status events so controllers can learn
9550 about changes to DNS server status.
9552 o Minor features (directory):
9553 - Authorities no longer recommend exits as guards if this would shift
9554 too much load to the exit nodes.
9557 Changes in version 0.1.2.5-alpha - 2007-01-06
9559 - Enable write limiting as well as read limiting. Now we sacrifice
9560 capacity if we're pushing out lots of directory traffic, rather
9561 than overrunning the user's intended bandwidth limits.
9562 - Include TLS overhead when counting bandwidth usage; previously, we
9563 would count only the bytes sent over TLS, but not the bytes used
9565 - Support running the Tor service with a torrc not in the same
9566 directory as tor.exe and default to using the torrc located in
9567 the %appdata%\Tor\ of the user who installed the service. Patch
9569 - Servers now check for the case when common DNS requests are going to
9570 wildcarded addresses (i.e. all getting the same answer), and change
9571 their exit policy to reject *:* if it's happening.
9572 - Implement BEGIN_DIR cells, so we can connect to the directory
9573 server via TLS to do encrypted directory requests rather than
9574 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
9575 config options if you like.
9577 o Minor features (config and docs):
9578 - Start using the state file to store bandwidth accounting data:
9579 the bw_accounting file is now obsolete. We'll keep generating it
9580 for a while for people who are still using 0.1.2.4-alpha.
9581 - Try to batch changes to the state file so that we do as few
9582 disk writes as possible while still storing important things in
9584 - The state file and the bw_accounting file get saved less often when
9585 the AvoidDiskWrites config option is set.
9586 - Make PIDFile work on Windows (untested).
9587 - Add internal descriptions for a bunch of configuration options:
9588 accessible via controller interface and in comments in saved
9590 - Reject *:563 (NNTPS) in the default exit policy. We already reject
9591 NNTP by default, so this seems like a sensible addition.
9592 - Clients now reject hostnames with invalid characters. This should
9593 avoid some inadvertent info leaks. Add an option
9594 AllowNonRFC953Hostnames to disable this behavior, in case somebody
9595 is running a private network with hosts called @, !, and #.
9596 - Add a maintainer script to tell us which options are missing
9597 documentation: "make check-docs".
9598 - Add a new address-spec.txt document to describe our special-case
9599 addresses: .exit, .onion, and .noconnnect.
9601 o Minor features (DNS):
9602 - Ongoing work on eventdns infrastructure: now it has dns server
9603 and ipv6 support. One day Tor will make use of it.
9604 - Add client-side caching for reverse DNS lookups.
9605 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
9606 - When we change nameservers or IP addresses, reset and re-launch
9607 our tests for DNS hijacking.
9609 o Minor features (directory):
9610 - Authorities now specify server versions in networkstatus. This adds
9611 about 2% to the size of compressed networkstatus docs, and allows
9612 clients to tell which servers support BEGIN_DIR and which don't.
9613 The implementation is forward-compatible with a proposed future
9614 protocol version scheme not tied to Tor versions.
9615 - DirServer configuration lines now have an orport= option so
9616 clients can open encrypted tunnels to the authorities without
9617 having downloaded their descriptors yet. Enabled for moria1,
9618 moria2, tor26, and lefkada now in the default configuration.
9619 - Directory servers are more willing to send a 503 "busy" if they
9620 are near their write limit, especially for v1 directory requests.
9621 Now they can use their limited bandwidth for actual Tor traffic.
9622 - Clients track responses with status 503 from dirservers. After a
9623 dirserver has given us a 503, we try not to use it until an hour has
9624 gone by, or until we have no dirservers that haven't given us a 503.
9625 - When we get a 503 from a directory, and we're not a server, we don't
9626 count the failure against the total number of failures allowed
9627 for the thing we're trying to download.
9628 - Report X-Your-Address-Is correctly from tunneled directory
9629 connections; don't report X-Your-Address-Is when it's an internal
9630 address; and never believe reported remote addresses when they're
9632 - Protect against an unlikely DoS attack on directory servers.
9633 - Add a BadDirectory flag to network status docs so that authorities
9634 can (eventually) tell clients about caches they believe to be
9637 o Minor features (controller):
9638 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
9639 - Reimplement GETINFO so that info/names stays in sync with the
9641 - Implement "GETINFO fingerprint".
9642 - Implement "SETEVENTS GUARD" so controllers can get updates on
9643 entry guard status as it changes.
9645 o Minor features (clean up obsolete pieces):
9646 - Remove some options that have been deprecated since at least
9647 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
9648 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
9650 - We no longer look for identity and onion keys in "identity.key" and
9651 "onion.key" -- these were replaced by secret_id_key and
9652 secret_onion_key in 0.0.8pre1.
9653 - We no longer require unrecognized directory entries to be
9656 o Major bugfixes (security):
9657 - Stop sending the HttpProxyAuthenticator string to directory
9658 servers when directory connections are tunnelled through Tor.
9659 - Clients no longer store bandwidth history in the state file.
9660 - Do not log introduction points for hidden services if SafeLogging
9662 - When generating bandwidth history, round down to the nearest
9663 1k. When storing accounting data, round up to the nearest 1k.
9664 - When we're running as a server, remember when we last rotated onion
9665 keys, so that we will rotate keys once they're a week old even if
9666 we never stay up for a week ourselves.
9668 o Major bugfixes (other):
9669 - Fix a longstanding bug in eventdns that prevented the count of
9670 timed-out resolves from ever being reset. This bug caused us to
9671 give up on a nameserver the third time it timed out, and try it
9672 10 seconds later... and to give up on it every time it timed out
9674 - Take out the '5 second' timeout from the connection retry
9675 schedule. Now the first connect attempt will wait a full 10
9676 seconds before switching to a new circuit. Perhaps this will help
9677 a lot. Based on observations from Mike Perry.
9678 - Fix a bug on the Windows implementation of tor_mmap_file() that
9679 would prevent the cached-routers file from ever loading. Reported
9683 - Fix an assert failure when a directory authority sets
9684 AuthDirRejectUnlisted and then receives a descriptor from an
9685 unlisted router. Reported by seeess.
9686 - Avoid a double-free when parsing malformed DirServer lines.
9687 - Fix a bug when a BSD-style PF socket is first used. Patch from
9689 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
9690 to resolve an address at a given exit node even when they ask for
9692 - Servers no longer ever list themselves in their "family" line,
9693 even if configured to do so. This makes it easier to configure
9694 family lists conveniently.
9695 - When running as a server, don't fall back to 127.0.0.1 when no
9696 nameservers are configured in /etc/resolv.conf; instead, make the
9697 user fix resolv.conf or specify nameservers explicitly. (Resolves
9699 - Stop accepting certain malformed ports in configured exit policies.
9700 - Don't re-write the fingerprint file every restart, unless it has
9702 - Stop warning when a single nameserver fails: only warn when _all_ of
9703 our nameservers have failed. Also, when we only have one nameserver,
9704 raise the threshold for deciding that the nameserver is dead.
9705 - Directory authorities now only decide that routers are reachable
9706 if their identity keys are as expected.
9707 - When the user uses bad syntax in the Log config line, stop
9708 suggesting other bad syntax as a replacement.
9709 - Correctly detect ipv6 DNS capability on OpenBSD.
9711 o Minor bugfixes (controller):
9712 - Report the circuit number correctly in STREAM CLOSED events. Bug
9713 reported by Mike Perry.
9714 - Do not report bizarre values for results of accounting GETINFOs
9715 when the last second's write or read exceeds the allotted bandwidth.
9716 - Report "unrecognized key" rather than an empty string when the
9717 controller tries to fetch a networkstatus that doesn't exist.
9720 Changes in version 0.1.1.26 - 2006-12-14
9721 o Security bugfixes:
9722 - Stop sending the HttpProxyAuthenticator string to directory
9723 servers when directory connections are tunnelled through Tor.
9724 - Clients no longer store bandwidth history in the state file.
9725 - Do not log introduction points for hidden services if SafeLogging
9729 - Fix an assert failure when a directory authority sets
9730 AuthDirRejectUnlisted and then receives a descriptor from an
9731 unlisted router (reported by seeess).
9734 Changes in version 0.1.2.4-alpha - 2006-12-03
9736 - Add support for using natd; this allows FreeBSDs earlier than
9737 5.1.2 to have ipfw send connections through Tor without using
9738 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
9741 - Make all connections to addresses of the form ".noconnect"
9742 immediately get closed. This lets application/controller combos
9743 successfully test whether they're talking to the same Tor by
9744 watching for STREAM events.
9745 - Make cross.sh cross-compilation script work even when autogen.sh
9746 hasn't been run. (Patch from Michael Mohr.)
9747 - Statistics dumped by -USR2 now include a breakdown of public key
9748 operations, for profiling.
9751 - Fix a major leak when directory authorities parse their
9752 approved-routers list, a minor memory leak when we fail to pick
9753 an exit node, and a few rare leaks on errors.
9754 - Handle TransPort connections even when the server sends data before
9755 the client sends data. Previously, the connection would just hang
9756 until the client sent data. (Patch from tup based on patch from
9758 - Avoid assert failure when our cached-routers file is empty on
9762 - Don't log spurious warnings when we see a circuit close reason we
9763 don't recognize; it's probably just from a newer version of Tor.
9764 - Have directory authorities allow larger amounts of drift in uptime
9765 without replacing the server descriptor: previously, a server that
9766 restarted every 30 minutes could have 48 "interesting" descriptors
9768 - Start linking to the Tor specification and Tor reference manual
9769 correctly in the Windows installer.
9770 - Add Vidalia to the OS X uninstaller script, so when we uninstall
9771 Tor/Privoxy we also uninstall Vidalia.
9772 - Resume building on Irix64, and fix a lot of warnings from its
9774 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
9775 when we're running as a client.
9778 Changes in version 0.1.1.25 - 2006-11-04
9780 - When a client asks us to resolve (rather than connect to)
9781 an address, and we have a cached answer, give them the cached
9782 answer. Previously, we would give them no answer at all.
9783 - We were building exactly the wrong circuits when we predict
9784 hidden service requirements, meaning Tor would have to build all
9785 its circuits on demand.
9786 - If none of our live entry guards have a high uptime, but we
9787 require a guard with a high uptime, try adding a new guard before
9788 we give up on the requirement. This patch should make long-lived
9789 connections more stable on average.
9790 - When testing reachability of our DirPort, don't launch new
9791 tests when there's already one in progress -- unreachable
9792 servers were stacking up dozens of testing streams.
9794 o Security bugfixes:
9795 - When the user sends a NEWNYM signal, clear the client-side DNS
9796 cache too. Otherwise we continue to act on previous information.
9799 - Avoid a memory corruption bug when creating a hash table for
9801 - Avoid possibility of controller-triggered crash when misusing
9802 certain commands from a v0 controller on platforms that do not
9803 handle printf("%s",NULL) gracefully.
9804 - Avoid infinite loop on unexpected controller input.
9805 - Don't log spurious warnings when we see a circuit close reason we
9806 don't recognize; it's probably just from a newer version of Tor.
9807 - Add Vidalia to the OS X uninstaller script, so when we uninstall
9808 Tor/Privoxy we also uninstall Vidalia.
9811 Changes in version 0.1.2.3-alpha - 2006-10-29
9813 - Prepare for servers to publish descriptors less often: never
9814 discard a descriptor simply for being too old until either it is
9815 recommended by no authorities, or until we get a better one for
9816 the same router. Make caches consider retaining old recommended
9817 routers for even longer.
9818 - If most authorities set a BadExit flag for a server, clients
9819 don't think of it as a general-purpose exit. Clients only consider
9820 authorities that advertise themselves as listing bad exits.
9821 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
9822 headers for content, so that we can work better in the presence of
9823 caching HTTP proxies.
9824 - Allow authorities to list nodes as bad exits by fingerprint or by
9827 o Minor features, controller:
9828 - Add a REASON field to CIRC events; for backward compatibility, this
9829 field is sent only to controllers that have enabled the extended
9830 event format. Also, add additional reason codes to explain why
9831 a given circuit has been destroyed or truncated. (Patches from
9833 - Add a REMOTE_REASON field to extended CIRC events to tell the
9834 controller about why a remote OR told us to close a circuit.
9835 - Stream events also now have REASON and REMOTE_REASON fields,
9836 working much like those for circuit events.
9837 - There's now a GETINFO ns/... field so that controllers can ask Tor
9838 about the current status of a router.
9839 - A new event type "NS" to inform a controller when our opinion of
9840 a router's status has changed.
9841 - Add a GETINFO events/names and GETINFO features/names so controllers
9842 can tell which events and features are supported.
9843 - A new CLEARDNSCACHE signal to allow controllers to clear the
9844 client-side DNS cache without expiring circuits.
9846 o Security bugfixes:
9847 - When the user sends a NEWNYM signal, clear the client-side DNS
9848 cache too. Otherwise we continue to act on previous information.
9851 - Avoid sending junk to controllers or segfaulting when a controller
9852 uses EVENT_NEW_DESC with verbose nicknames.
9853 - Stop triggering asserts if the controller tries to extend hidden
9854 service circuits (reported by mwenge).
9855 - Avoid infinite loop on unexpected controller input.
9856 - When the controller does a "GETINFO network-status", tell it
9857 about even those routers whose descriptors are very old, and use
9858 long nicknames where appropriate.
9859 - Change NT service functions to be loaded on demand. This lets us
9860 build with MinGW without breaking Tor for Windows 98 users.
9861 - Do DirPort reachability tests less often, since a single test
9862 chews through many circuits before giving up.
9863 - In the hidden service example in torrc.sample, stop recommending
9864 esoteric and discouraged hidden service options.
9865 - When stopping an NT service, wait up to 10 sec for it to actually
9866 stop. Patch from Matt Edman; resolves bug 295.
9867 - Fix handling of verbose nicknames with ORCONN controller events:
9868 make them show up exactly when requested, rather than exactly when
9870 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
9871 printing a duplicate "$" in the keys we send (reported by mwenge).
9872 - Correctly set maximum connection limit on Cygwin. (This time
9874 - Try to detect Windows correctly when cross-compiling.
9875 - Detect the size of the routers file correctly even if it is
9876 corrupted (on systems without mmap) or not page-aligned (on systems
9877 with mmap). This bug was harmless.
9878 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
9879 to open a stream fails; now we do in more cases. This should
9880 make clients able to find a good exit faster in some cases, since
9881 unhandleable requests will now get an error rather than timing out.
9882 - Resolve two memory leaks when rebuilding the on-disk router cache
9883 (reported by fookoowa).
9884 - Clean up minor code warnings suggested by the MIPSpro C compiler,
9885 and reported by some Centos users.
9886 - Controller signals now work on non-Unix platforms that don't define
9887 SIGUSR1 and SIGUSR2 the way we expect.
9888 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
9889 values before failing, and always enables eventdns.
9890 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
9891 Try to fix this in configure.in by checking for most functions
9892 before we check for libevent.
9895 Changes in version 0.1.2.2-alpha - 2006-10-07
9897 - Make our async eventdns library on-by-default for Tor servers,
9898 and plan to deprecate the separate dnsworker threads.
9899 - Add server-side support for "reverse" DNS lookups (using PTR
9900 records so clients can determine the canonical hostname for a given
9901 IPv4 address). Only supported by servers using eventdns; servers
9902 now announce in their descriptors whether they support eventdns.
9903 - Specify and implement client-side SOCKS5 interface for reverse DNS
9904 lookups (see doc/socks-extensions.txt).
9905 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
9906 connect to directory servers through Tor. Previously, clients needed
9907 to find Tor exits to make private connections to directory servers.
9908 - Avoid choosing Exit nodes for entry or middle hops when the
9909 total bandwidth available from non-Exit nodes is much higher than
9910 the total bandwidth available from Exit nodes.
9911 - Workaround for name servers (like Earthlink's) that hijack failing
9912 DNS requests and replace the no-such-server answer with a "helpful"
9913 redirect to an advertising-driven search portal. Also work around
9914 DNS hijackers who "helpfully" decline to hijack known-invalid
9915 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
9916 lets you turn it off.
9917 - Send out a burst of long-range padding cells once we've established
9918 that we're reachable. Spread them over 4 circuits, so hopefully
9919 a few will be fast. This exercises our bandwidth and bootstraps
9920 us into the directory more quickly.
9922 o New/improved config options:
9923 - Add new config option "ResolvConf" to let the server operator
9924 choose an alternate resolve.conf file when using eventdns.
9925 - Add an "EnforceDistinctSubnets" option to control our "exclude
9926 servers on the same /16" behavior. It's still on by default; this
9927 is mostly for people who want to operate private test networks with
9928 all the machines on the same subnet.
9929 - If one of our entry guards is on the ExcludeNodes list, or the
9930 directory authorities don't think it's a good guard, treat it as
9931 if it were unlisted: stop using it as a guard, and throw it off
9932 the guards list if it stays that way for a long time.
9933 - Allow directory authorities to be marked separately as authorities
9934 for the v1 directory protocol, the v2 directory protocol, and
9935 as hidden service directories, to make it easier to retire old
9936 authorities. V1 authorities should set "HSAuthoritativeDir 1"
9937 to continue being hidden service authorities too.
9938 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
9940 o Minor features, controller:
9941 - Fix CIRC controller events so that controllers can learn the
9942 identity digests of non-Named servers used in circuit paths.
9943 - Let controllers ask for more useful identifiers for servers. Instead
9944 of learning identity digests for un-Named servers and nicknames
9945 for Named servers, the new identifiers include digest, nickname,
9946 and indication of Named status. Off by default; see control-spec.txt
9947 for more information.
9948 - Add a "getinfo address" controller command so it can display Tor's
9949 best guess to the user.
9950 - New controller event to alert the controller when our server
9951 descriptor has changed.
9952 - Give more meaningful errors on controller authentication failure.
9954 o Minor features, other:
9955 - When asked to resolve a hostname, don't use non-exit servers unless
9956 requested to do so. This allows servers with broken DNS to be
9957 useful to the network.
9958 - Divide eventdns log messages into warn and info messages.
9959 - Reserve the nickname "Unnamed" for routers that can't pick
9960 a hostname: any router can call itself Unnamed; directory
9961 authorities will never allocate Unnamed to any particular router;
9962 clients won't believe that any router is the canonical Unnamed.
9963 - Only include function names in log messages for info/debug messages.
9964 For notice/warn/err, the content of the message should be clear on
9965 its own, and printing the function name only confuses users.
9966 - Avoid some false positives during reachability testing: don't try
9967 to test via a server that's on the same /24 as us.
9968 - If we fail to build a circuit to an intended enclave, and it's
9969 not mandatory that we use that enclave, stop wanting it.
9970 - When eventdns is enabled, allow multithreaded builds on NetBSD and
9971 OpenBSD. (We had previously disabled threads on these platforms
9972 because they didn't have working thread-safe resolver functions.)
9974 o Major bugfixes, anonymity/security:
9975 - If a client asked for a server by name, and there's a named server
9976 in our network-status but we don't have its descriptor yet, we
9977 could return an unnamed server instead.
9978 - Fix NetBSD bug that could allow someone to force uninitialized RAM
9979 to be sent to a server's DNS resolver. This only affects NetBSD
9980 and other platforms that do not bounds-check tolower().
9981 - Reject (most) attempts to use Tor circuits with length one. (If
9982 many people start using Tor as a one-hop proxy, exit nodes become
9983 a more attractive target for compromise.)
9984 - Just because your DirPort is open doesn't mean people should be
9985 able to remotely teach you about hidden service descriptors. Now
9986 only accept rendezvous posts if you've got HSAuthoritativeDir set.
9988 o Major bugfixes, other:
9989 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
9990 - When a client asks the server to resolve (not connect to)
9991 an address, and it has a cached answer, give them the cached answer.
9992 Previously, the server would give them no answer at all.
9993 - Allow really slow clients to not hang up five minutes into their
9994 directory downloads (suggested by Adam J. Richter).
9995 - We were building exactly the wrong circuits when we anticipated
9996 hidden service requirements, meaning Tor would have to build all
9997 its circuits on demand.
9998 - Avoid crashing when we mmap a router cache file of size 0.
9999 - When testing reachability of our DirPort, don't launch new
10000 tests when there's already one in progress -- unreachable
10001 servers were stacking up dozens of testing streams.
10003 o Minor bugfixes, correctness:
10004 - If we're a directory mirror and we ask for "all" network status
10005 documents, we would discard status documents from authorities
10006 we don't recognize.
10007 - Avoid a memory corruption bug when creating a hash table for
10009 - Avoid controller-triggered crash when misusing certain commands
10010 from a v0 controller on platforms that do not handle
10011 printf("%s",NULL) gracefully.
10012 - Don't crash when a controller sends a third argument to an
10013 "extendcircuit" request.
10014 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10015 response; fix error code when "getinfo dir/status/" fails.
10016 - Avoid crash when telling controller stream-status and a stream
10018 - Patch from Adam Langley to fix assert() in eventdns.c.
10019 - Fix a debug log message in eventdns to say "X resolved to Y"
10020 instead of "X resolved to X".
10021 - Make eventdns give strings for DNS errors, not just error numbers.
10022 - Track unreachable entry guards correctly: don't conflate
10023 'unreachable by us right now' with 'listed as down by the directory
10024 authorities'. With the old code, if a guard was unreachable by
10025 us but listed as running, it would clog our guard list forever.
10026 - Behave correctly in case we ever have a network with more than
10027 2GB/s total advertised capacity.
10028 - Make TrackExitHosts case-insensitive, and fix the behavior of
10029 ".suffix" TrackExitHosts items to avoid matching in the middle of
10031 - Finally fix the openssl warnings from newer gccs that believe that
10032 ignoring a return value is okay, but casting a return value and
10033 then ignoring it is a sign of madness.
10034 - Prevent the contrib/exitlist script from printing the same
10035 result more than once.
10036 - Patch from Steve Hildrey: Generate network status correctly on
10037 non-versioning dirservers.
10038 - Don't listen to the X-Your-Address-Is hint if you did the lookup
10039 via Tor; otherwise you'll think you're the exit node's IP address.
10041 o Minor bugfixes, performance:
10042 - Two small performance improvements on parsing descriptors.
10043 - Major performance improvement on inserting descriptors: change
10044 algorithm from O(n^2) to O(n).
10045 - Make the common memory allocation path faster on machines where
10046 malloc(0) returns a pointer.
10047 - Start remembering X-Your-Address-Is directory hints even if you're
10048 a client, so you can become a server more smoothly.
10049 - Avoid duplicate entries on MyFamily line in server descriptor.
10051 o Packaging, features:
10052 - Remove architecture from OS X builds. The official builds are
10053 now universal binaries.
10054 - The Debian package now uses --verify-config when (re)starting,
10055 to distinguish configuration errors from other errors.
10056 - Update RPMs to require libevent 1.1b.
10058 o Packaging, bugfixes:
10059 - Patches so Tor builds with MinGW on Windows.
10060 - Patches so Tor might run on Cygwin again.
10061 - Resume building on non-gcc compilers and ancient gcc. Resume
10062 building with the -O0 compile flag. Resume building cleanly on
10064 - Run correctly on OS X platforms with case-sensitive filesystems.
10065 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
10066 - Add autoconf checks so Tor can build on Solaris x86 again.
10069 - Documented (and renamed) ServerDNSSearchDomains and
10070 ServerDNSResolvConfFile options.
10071 - Be clearer that the *ListenAddress directives can be repeated
10075 Changes in version 0.1.1.24 - 2006-09-29
10077 - Allow really slow clients to not hang up five minutes into their
10078 directory downloads (suggested by Adam J. Richter).
10079 - Fix major performance regression from 0.1.0.x: instead of checking
10080 whether we have enough directory information every time we want to
10081 do something, only check when the directory information has changed.
10082 This should improve client CPU usage by 25-50%.
10083 - Don't crash if, after a server has been running for a while,
10084 it can't resolve its hostname.
10087 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10088 - Don't crash when the controller receives a third argument to an
10089 "extendcircuit" request.
10090 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10091 response; fix error code when "getinfo dir/status/" fails.
10092 - Fix configure.in to not produce broken configure files with
10093 more recent versions of autoconf. Thanks to Clint for his auto*
10095 - Fix security bug on NetBSD that could allow someone to force
10096 uninitialized RAM to be sent to a server's DNS resolver. This
10097 only affects NetBSD and other platforms that do not bounds-check
10099 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
10100 methods: these are known to be buggy.
10101 - If we're a directory mirror and we ask for "all" network status
10102 documents, we would discard status documents from authorities
10103 we don't recognize.
10106 Changes in version 0.1.2.1-alpha - 2006-08-27
10108 - Add "eventdns" async dns library from Adam Langley, tweaked to
10109 build on OSX and Windows. Only enabled if you pass the
10110 --enable-eventdns argument to configure.
10111 - Allow servers with no hostname or IP address to learn their
10112 IP address by asking the directory authorities. This code only
10113 kicks in when you would normally have exited with a "no address"
10114 error. Nothing's authenticated, so use with care.
10115 - Rather than waiting a fixed amount of time between retrying
10116 application connections, we wait only 5 seconds for the first,
10117 10 seconds for the second, and 15 seconds for each retry after
10118 that. Hopefully this will improve the expected user experience.
10119 - Patch from Tup to add support for transparent AP connections:
10120 this basically bundles the functionality of trans-proxy-tor
10121 into the Tor mainline. Now hosts with compliant pf/netfilter
10122 implementations can redirect TCP connections straight to Tor
10123 without diverting through SOCKS. Needs docs.
10124 - Busy directory servers save lots of memory by spooling server
10125 descriptors, v1 directories, and v2 networkstatus docs to buffers
10126 as needed rather than en masse. Also mmap the cached-routers
10127 files, so we don't need to keep the whole thing in memory too.
10128 - Automatically avoid picking more than one node from the same
10129 /16 network when constructing a circuit.
10130 - Revise and clean up the torrc.sample that we ship with; add
10131 a section for BandwidthRate and BandwidthBurst.
10134 - Split circuit_t into origin_circuit_t and or_circuit_t, and
10135 split connection_t into edge, or, dir, control, and base structs.
10136 These will save quite a bit of memory on busy servers, and they'll
10137 also help us track down bugs in the code and bugs in the spec.
10138 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
10139 or later. Log when we are doing this, so we can diagnose it when
10140 it fails. (Also, recommend libevent 1.1b for kqueue and
10141 win32 methods; deprecate libevent 1.0b harder; make libevent
10142 recommendation system saner.)
10143 - Start being able to build universal binaries on OS X (thanks
10145 - Export the default exit policy via the control port, so controllers
10146 don't need to guess what it is / will be later.
10147 - Add a man page entry for ProtocolWarnings.
10148 - Add TestVia config option to the man page.
10149 - Remove even more protocol-related warnings from Tor server logs,
10150 such as bad TLS handshakes and malformed begin cells.
10151 - Stop fetching descriptors if you're not a dir mirror and you
10152 haven't tried to establish any circuits lately. [This currently
10153 causes some dangerous behavior, because when you start up again
10154 you'll use your ancient server descriptors.]
10155 - New DirPort behavior: if you have your dirport set, you download
10156 descriptors aggressively like a directory mirror, whether or not
10157 your ORPort is set.
10158 - Get rid of the router_retry_connections notion. Now routers
10159 no longer try to rebuild long-term connections to directory
10160 authorities, and directory authorities no longer try to rebuild
10161 long-term connections to all servers. We still don't hang up
10162 connections in these two cases though -- we need to look at it
10163 more carefully to avoid flapping, and we likely need to wait til
10164 0.1.1.x is obsolete.
10165 - Drop compatibility with obsolete Tors that permit create cells
10166 to have the wrong circ_id_type.
10167 - Re-enable per-connection rate limiting. Get rid of the "OP
10168 bandwidth" concept. Lay groundwork for "bandwidth classes" --
10169 separate global buckets that apply depending on what sort of conn
10171 - Start publishing one minute or so after we find our ORPort
10172 to be reachable. This will help reduce the number of descriptors
10173 we have for ourselves floating around, since it's quite likely
10174 other things (e.g. DirPort) will change during that minute too.
10175 - Fork the v1 directory protocol into its own spec document,
10176 and mark dir-spec.txt as the currently correct (v2) spec.
10179 - When we find our DirPort to be reachable, publish a new descriptor
10180 so we'll tell the world (reported by pnx).
10181 - Publish a new descriptor after we hup/reload. This is important
10182 if our config has changed such that we'll want to start advertising
10183 our DirPort now, etc.
10184 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10185 - When we have a state file we cannot parse, tell the user and
10186 move it aside. Now we avoid situations where the user starts
10187 Tor in 1904, Tor writes a state file with that timestamp in it,
10188 the user fixes her clock, and Tor refuses to start.
10189 - Fix configure.in to not produce broken configure files with
10190 more recent versions of autoconf. Thanks to Clint for his auto*
10192 - "tor --verify-config" now exits with -1(255) or 0 depending on
10193 whether the config options are bad or good.
10194 - Resolve bug 321 when using dnsworkers: append a period to every
10195 address we resolve at the exit node, so that we do not accidentally
10196 pick up local addresses, and so that failing searches are retried
10197 in the resolver search domains. (This is already solved for
10198 eventdns.) (This breaks Blossom servers for now.)
10199 - If we are using an exit enclave and we can't connect, e.g. because
10200 its webserver is misconfigured to not listen on localhost, then
10201 back off and try connecting from somewhere else before we fail.
10204 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
10205 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
10206 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
10207 when the IP address is mapped through MapAddress to a hostname.
10208 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
10209 useless IPv6 DNS resolves.
10210 - Patch suggested by Karsten Loesing: respond to SIGNAL command
10211 before we execute the signal, in case the signal shuts us down.
10212 - Clean up AllowInvalidNodes man page entry.
10213 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
10214 - Add more asserts to track down an assert error on a windows Tor
10215 server with connection_add being called with socket == -1.
10216 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
10217 - Fix misleading log messages: an entry guard that is "unlisted",
10218 as well as not known to be "down" (because we've never heard
10219 of it), is not therefore "up".
10220 - Remove code to special-case "-cvs" ending, since it has not
10221 actually mattered since 0.0.9.
10222 - Make our socks5 handling more robust to broken socks clients:
10223 throw out everything waiting on the buffer in between socks
10224 handshake phases, since they can't possibly (so the theory
10225 goes) have predicted what we plan to respond to them.
10228 Changes in version 0.1.1.23 - 2006-07-30
10230 - Fast Tor servers, especially exit nodes, were triggering asserts
10231 due to a bug in handling the list of pending DNS resolves. Some
10232 bugs still remain here; we're hunting them.
10233 - Entry guards could crash clients by sending unexpected input.
10234 - More fixes on reachability testing: if you find yourself reachable,
10235 then don't ever make any client requests (so you stop predicting
10236 circuits), then hup or have your clock jump, then later your IP
10237 changes, you won't think circuits are working, so you won't try to
10238 test reachability, so you won't publish.
10241 - Avoid a crash if the controller does a resetconf firewallports
10242 and then a setconf fascistfirewall=1.
10243 - Avoid an integer underflow when the dir authority decides whether
10244 a router is stable: we might wrongly label it stable, and compute
10245 a slightly wrong median stability, when a descriptor is published
10247 - Fix a place where we might trigger an assert if we can't build our
10248 own server descriptor yet.
10251 Changes in version 0.1.1.22 - 2006-07-05
10253 - Fix a big bug that was causing servers to not find themselves
10254 reachable if they changed IP addresses. Since only 0.1.1.22+
10255 servers can do reachability testing correctly, now we automatically
10256 make sure to test via one of these.
10257 - Fix to allow clients and mirrors to learn directory info from
10258 descriptor downloads that get cut off partway through.
10259 - Directory authorities had a bug in deciding if a newly published
10260 descriptor was novel enough to make everybody want a copy -- a few
10261 servers seem to be publishing new descriptors many times a minute.
10263 - Fix a rare bug that was causing some servers to complain about
10264 "closing wedged cpuworkers" and skip some circuit create requests.
10265 - Make the Exit flag in directory status documents actually work.
10268 Changes in version 0.1.1.21 - 2006-06-10
10269 o Crash and assert fixes from 0.1.1.20:
10270 - Fix a rare crash on Tor servers that have enabled hibernation.
10271 - Fix a seg fault on startup for Tor networks that use only one
10272 directory authority.
10273 - Fix an assert from a race condition that occurs on Tor servers
10274 while exiting, where various threads are trying to log that they're
10275 exiting, and delete the logs, at the same time.
10276 - Make our unit tests pass again on certain obscure platforms.
10279 - Add support for building SUSE RPM packages.
10280 - Speed up initial bootstrapping for clients: if we are making our
10281 first ever connection to any entry guard, then don't mark it down
10283 - When only one Tor server in the network is labelled as a guard,
10284 and we've already picked him, we would cycle endlessly picking him
10285 again, being unhappy about it, etc. Now we specifically exclude
10286 current guards when picking a new guard.
10287 - Servers send create cells more reliably after the TLS connection
10288 is established: we were sometimes forgetting to send half of them
10289 when we had more than one pending.
10290 - If we get a create cell that asks us to extend somewhere, but the
10291 Tor server there doesn't match the expected digest, we now send
10292 a destroy cell back, rather than silently doing nothing.
10293 - Make options->RedirectExit work again.
10294 - Make cookie authentication for the controller work again.
10295 - Stop being picky about unusual characters in the arguments to
10296 mapaddress. It's none of our business.
10297 - Add a new config option "TestVia" that lets you specify preferred
10298 middle hops to use for test circuits. Perhaps this will let me
10299 debug the reachability problems better.
10301 o Log / documentation fixes:
10302 - If we're a server and some peer has a broken TLS certificate, don't
10303 log about it unless ProtocolWarnings is set, i.e., we want to hear
10304 about protocol violations by others.
10305 - Fix spelling of VirtualAddrNetwork in man page.
10306 - Add a better explanation at the top of the autogenerated torrc file
10307 about what happened to our old torrc.
10310 Changes in version 0.1.1.20 - 2006-05-23
10312 - Downgrade a log severity where servers complain that they're
10314 - Avoid a compile warning on FreeBSD.
10315 - Remove string size limit on NEWDESC messages; solve bug 291.
10316 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
10317 more thoroughly when we're running on windows.
10320 Changes in version 0.1.1.19-rc - 2006-05-03
10322 - Regenerate our local descriptor if it's dirty and we try to use
10323 it locally (e.g. if it changes during reachability detection).
10324 - If we setconf our ORPort to 0, we continued to listen on the
10325 old ORPort and receive connections.
10326 - Avoid a second warning about machine/limits.h on Debian
10328 - Be willing to add our own routerinfo into the routerlist.
10329 Now authorities will include themselves in their directories
10330 and network-statuses.
10331 - Stop trying to upload rendezvous descriptors to every
10332 directory authority: only try the v1 authorities.
10333 - Servers no longer complain when they think they're not
10334 registered with the directory authorities. There were too many
10336 - Backport dist-rpm changes so rpms can be built without errors.
10339 - Implement an option, VirtualAddrMask, to set which addresses
10340 get handed out in response to mapaddress requests. This works
10341 around a bug in tsocks where 127.0.0.0/8 is never socksified.
10344 Changes in version 0.1.1.18-rc - 2006-04-10
10346 - Work harder to download live network-statuses from all the
10347 directory authorities we know about. Improve the threshold
10348 decision logic so we're more robust to edge cases.
10349 - When fetching rendezvous descriptors, we were willing to ask
10350 v2 authorities too, which would always return 404.
10353 - Stop listing down or invalid nodes in the v1 directory. This will
10354 reduce its bulk by about 1/3, and reduce load on directory
10356 - When deciding whether a router is Fast or Guard-worthy, consider
10357 his advertised BandwidthRate and not just the BandwidthCapacity.
10358 - No longer ship INSTALL and README files -- they are useless now.
10359 - Force rpmbuild to behave and honor target_cpu.
10360 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
10361 - Start to include translated versions of the tor-doc-*.html
10362 files, along with the screenshots. Still needs more work.
10363 - Start sending back 512 and 451 errors if mapaddress fails,
10364 rather than not sending anything back at all.
10365 - When we fail to bind or listen on an incoming or outgoing
10366 socket, we should close it before failing. otherwise we just
10367 leak it. (thanks to weasel for finding.)
10368 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
10369 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
10370 - Make NoPublish (even though deprecated) work again.
10371 - Fix a minor security flaw where a versioning auth dirserver
10372 could list a recommended version many times in a row to make
10373 clients more convinced that it's recommended.
10374 - Fix crash bug if there are two unregistered servers running
10375 with the same nickname, one of them is down, and you ask for
10376 them by nickname in your EntryNodes or ExitNodes. Also, try
10377 to pick the one that's running rather than an arbitrary one.
10378 - Fix an infinite loop we could hit if we go offline for too long.
10379 - Complain when we hit WSAENOBUFS on recv() or write() too.
10380 Perhaps this will help us hunt the bug.
10381 - If you're not a versioning dirserver, don't put the string
10382 "client-versions \nserver-versions \n" in your network-status.
10383 - Lower the minimum required number of file descriptors to 1000,
10384 so we can have some overhead for Valgrind on Linux, where the
10385 default ulimit -n is 1024.
10388 - Add tor.dizum.com as the fifth authoritative directory server.
10389 - Add a new config option FetchUselessDescriptors, off by default,
10390 for when you plan to run "exitlist" on your client and you want
10391 to know about even the non-running descriptors.
10394 Changes in version 0.1.1.17-rc - 2006-03-28
10396 - Clients and servers since 0.1.1.10-alpha have been expiring
10397 connections whenever they are idle for 5 minutes and they *do*
10398 have circuits on them. Oops. With this new version, clients will
10399 discard their previous entry guard choices and avoid choosing
10400 entry guards running these flawed versions.
10401 - Fix memory leak when uncompressing concatenated zlib streams. This
10402 was causing substantial leaks over time on Tor servers.
10403 - The v1 directory was including servers as much as 48 hours old,
10404 because that's how the new routerlist->routers works. Now only
10405 include them if they're 20 hours old or less.
10408 - Resume building on irix64, netbsd 2.0, etc.
10409 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
10411 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
10412 and it is confusing some users.
10413 - Mirrors stop caching the v1 directory so often.
10414 - Make the max number of old descriptors that a cache will hold
10415 rise with the number of directory authorities, so we can scale.
10416 - Change our win32 uname() hack to be more forgiving about what
10417 win32 versions it thinks it's found.
10420 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
10422 - When the controller's *setconf commands fail, collect an error
10423 message in a string and hand it back to the controller.
10424 - Make the v2 dir's "Fast" flag based on relative capacity, just
10425 like "Stable" is based on median uptime. Name everything in the
10426 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
10427 - Log server fingerprint on startup, so new server operators don't
10428 have to go hunting around their filesystem for it.
10429 - Return a robots.txt on our dirport to discourage google indexing.
10430 - Let the controller ask for GETINFO dir/status/foo so it can ask
10431 directly rather than connecting to the dir port. Only works when
10432 dirport is set for now.
10434 o New config options rather than constants in the code:
10435 - SocksTimeout: How long do we let a socks connection wait
10436 unattached before we fail it?
10437 - CircuitBuildTimeout: Cull non-open circuits that were born
10438 at least this many seconds ago.
10439 - CircuitIdleTimeout: Cull open clean circuits that were born
10440 at least this many seconds ago.
10443 Changes in version 0.1.1.16-rc - 2006-03-18
10444 o Bugfixes on 0.1.1.15-rc:
10445 - Fix assert when the controller asks to attachstream a connect-wait
10446 or resolve-wait stream.
10447 - Now do address rewriting when the controller asks us to attach
10448 to a particular circuit too. This will let Blossom specify
10449 "moria2.exit" without having to learn what moria2's IP address is.
10450 - Make the "tor --verify-config" command-line work again, so people
10451 can automatically check if their torrc will parse.
10452 - Authoritative dirservers no longer require an open connection from
10453 a server to consider him "reachable". We need this change because
10454 when we add new auth dirservers, old servers won't know not to
10456 - Let Tor build on Sun CC again.
10457 - Fix an off-by-one buffer size in dirserv.c that magically never
10458 hit our three authorities but broke sjmurdoch's own tor network.
10459 - If we as a directory mirror don't know of any v1 directory
10460 authorities, then don't try to cache any v1 directories.
10461 - Stop warning about unknown servers in our family when they are
10462 given as hex digests.
10463 - Stop complaining as quickly to the server operator that he
10464 hasn't registered his nickname/key binding.
10465 - Various cleanups so we can add new V2 Auth Dirservers.
10466 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
10467 reflect the updated flags in our v2 dir protocol.
10468 - Resume allowing non-printable characters for exit streams (both
10469 for connecting and for resolving). Now we tolerate applications
10470 that don't follow the RFCs. But continue to block malformed names
10473 o Bugfixes on 0.1.0.x:
10474 - Fix assert bug in close_logs(): when we close and delete logs,
10475 remove them all from the global "logfiles" list.
10476 - Fix minor integer overflow in calculating when we expect to use up
10477 our bandwidth allocation before hibernating.
10478 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
10479 there are multiple SSLs installed with different versions.
10480 - When we try to be a server and Address is not explicitly set and
10481 our hostname resolves to a private IP address, try to use an
10482 interface address if it has a public address. Now Windows machines
10483 that think of themselves as localhost can work by default.
10486 - Let the controller ask for GETINFO dir/server/foo so it can ask
10487 directly rather than connecting to the dir port.
10488 - Let the controller tell us about certain router descriptors
10489 that it doesn't want Tor to use in circuits. Implement
10490 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
10491 - New config option SafeSocks to reject all application connections
10492 using unsafe socks protocols. Defaults to off.
10495 Changes in version 0.1.1.15-rc - 2006-03-11
10496 o Bugfixes and cleanups:
10497 - When we're printing strings from the network, don't try to print
10498 non-printable characters. This protects us against shell escape
10499 sequence exploits, and also against attacks to fool humans into
10500 misreading their logs.
10501 - Fix a bug where Tor would fail to establish any connections if you
10502 left it off for 24 hours and then started it: we were happy with
10503 the obsolete network statuses, but they all referred to router
10504 descriptors that were too old to fetch, so we ended up with no
10505 valid router descriptors.
10506 - Fix a seg fault in the controller's "getinfo orconn-status"
10507 command while listing status on incoming handshaking connections.
10508 Introduce a status name "NEW" for these connections.
10509 - If we get a linelist or linelist_s config option from the torrc
10510 (e.g. ExitPolicy) and it has no value, warn and skip rather than
10511 silently resetting it to its default.
10512 - Don't abandon entry guards until they've been down or gone for
10514 - Cleaner and quieter log messages.
10517 - New controller signal NEWNYM that makes new application requests
10518 use clean circuits.
10519 - Add a new circuit purpose 'controller' to let the controller ask
10520 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
10521 controller command to let you specify the purpose if you're
10522 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
10523 command to let you change a circuit's purpose after it's been
10525 - Accept "private:*" in routerdesc exit policies; not generated yet
10526 because older Tors do not understand it.
10527 - Add BSD-style contributed startup script "rc.subr" from Peter
10531 Changes in version 0.1.1.14-alpha - 2006-02-20
10532 o Bugfixes on 0.1.1.x:
10533 - Don't die if we ask for a stdout or stderr log (even implicitly)
10534 and we're set to RunAsDaemon -- just warn.
10535 - We still had a few bugs in the OR connection rotation code that
10536 caused directory servers to slowly aggregate connections to other
10537 fast Tor servers. This time for sure!
10538 - Make log entries on Win32 include the name of the function again.
10539 - We were treating a pair of exit policies if they were equal even
10540 if one said accept and the other said reject -- causing us to
10541 not always publish a new descriptor since we thought nothing
10543 - Retry pending server downloads as well as pending networkstatus
10544 downloads when we unexpectedly get a socks request.
10545 - We were ignoring the IS_FAST flag in the directory status,
10546 meaning we were willing to pick trivial-bandwidth nodes for "fast"
10548 - If the controller's SAVECONF command fails (e.g. due to file
10549 permissions), let the controller know that it failed.
10552 - If we're trying to be a Tor server and running Windows 95/98/ME
10553 as a server, explain that we'll likely crash.
10554 - When we're a server, a client asks for an old-style directory,
10555 and our write bucket is empty, don't give it to him. This way
10556 small servers can continue to serve the directory *sometimes*,
10557 without getting overloaded.
10558 - Compress exit policies even more -- look for duplicate lines
10560 - Clients now honor the "guard" flag in the router status when
10561 picking entry guards, rather than looking at is_fast or is_stable.
10562 - Retain unrecognized lines in $DATADIR/state file, so that we can
10563 be forward-compatible.
10564 - Generate 18.0.0.0/8 address policy format in descs when we can;
10565 warn when the mask is not reducible to a bit-prefix.
10566 - Let the user set ControlListenAddress in the torrc. This can be
10567 dangerous, but there are some cases (like a secured LAN) where it
10569 - Split ReachableAddresses into ReachableDirAddresses and
10570 ReachableORAddresses, so we can restrict Dir conns to port 80
10571 and OR conns to port 443.
10572 - Now we can target arch and OS in rpm builds (contributed by
10573 Phobos). Also make the resulting dist-rpm filename match the
10575 - New config options to help controllers: FetchServerDescriptors
10576 and FetchHidServDescriptors for whether to fetch server
10577 info and hidserv info or let the controller do it, and
10578 PublishServerDescriptor and PublishHidServDescriptors.
10579 - Also let the controller set the __AllDirActionsPrivate config
10580 option if you want all directory fetches/publishes to happen via
10581 Tor (it assumes your controller bootstraps your circuits).
10584 Changes in version 0.1.0.17 - 2006-02-17
10585 o Crash bugfixes on 0.1.0.x:
10586 - When servers with a non-zero DirPort came out of hibernation,
10587 sometimes they would trigger an assert.
10589 o Other important bugfixes:
10590 - On platforms that don't have getrlimit (like Windows), we were
10591 artificially constraining ourselves to a max of 1024
10592 connections. Now just assume that we can handle as many as 15000
10593 connections. Hopefully this won't cause other problems.
10595 o Backported features:
10596 - When we're a server, a client asks for an old-style directory,
10597 and our write bucket is empty, don't give it to him. This way
10598 small servers can continue to serve the directory *sometimes*,
10599 without getting overloaded.
10600 - Whenever you get a 503 in response to a directory fetch, try
10601 once more. This will become important once servers start sending
10602 503's whenever they feel busy.
10603 - Fetch a new directory every 120 minutes, not every 40 minutes.
10604 Now that we have hundreds of thousands of users running the old
10605 directory algorithm, it's starting to hurt a lot.
10606 - Bump up the period for forcing a hidden service descriptor upload
10607 from 20 minutes to 1 hour.
10610 Changes in version 0.1.1.13-alpha - 2006-02-09
10611 o Crashes in 0.1.1.x:
10612 - When you tried to setconf ORPort via the controller, Tor would
10613 crash. So people using TorCP to become a server were sad.
10614 - Solve (I hope) the stack-smashing bug that we were seeing on fast
10615 servers. The problem appears to be something do with OpenSSL's
10616 random number generation, or how we call it, or something. Let me
10617 know if the crashes continue.
10618 - Turn crypto hardware acceleration off by default, until we find
10619 somebody smart who can test it for us. (It appears to produce
10620 seg faults in at least some cases.)
10621 - Fix a rare assert error when we've tried all intro points for
10622 a hidden service and we try fetching the service descriptor again:
10623 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
10626 - Fix a major load balance bug: we were round-robining in 16 KB
10627 chunks, and servers with bandwidthrate of 20 KB, while downloading
10628 a 600 KB directory, would starve their other connections. Now we
10629 try to be a bit more fair.
10630 - Dir authorities and mirrors were never expiring the newest
10631 descriptor for each server, causing memory and directory bloat.
10632 - Fix memory-bloating and connection-bloating bug on servers: We
10633 were never closing any connection that had ever had a circuit on
10634 it, because we were checking conn->n_circuits == 0, yet we had a
10635 bug that let it go negative.
10636 - Make Tor work using squid as your http proxy again -- squid
10637 returns an error if you ask for a URL that's too long, and it uses
10638 a really generic error message. Plus, many people are behind a
10639 transparent squid so they don't even realize it.
10640 - On platforms that don't have getrlimit (like Windows), we were
10641 artificially constraining ourselves to a max of 1024
10642 connections. Now just assume that we can handle as many as 15000
10643 connections. Hopefully this won't cause other problems.
10644 - Add a new config option ExitPolicyRejectPrivate which defaults to
10645 1. This means all exit policies will begin with rejecting private
10646 addresses, unless the server operator explicitly turns it off.
10649 - Clients no longer download descriptors for non-running
10651 - Before we add new directory authorities, we should make it
10652 clear that only v1 authorities should receive/publish hidden
10653 service descriptors.
10656 - As soon as we've fetched some more directory info, immediately
10657 try to download more server descriptors. This way we don't have
10658 a 10 second pause during initial bootstrapping.
10659 - Remove even more loud log messages that the server operator can't
10661 - When we're running an obsolete or un-recommended version, make
10662 the log message more clear about what the problem is and what
10663 versions *are* still recommended.
10664 - Provide a more useful warn message when our onion queue gets full:
10665 the CPU is too slow or the exit policy is too liberal.
10666 - Don't warn when we receive a 503 from a dirserver/cache -- this
10667 will pave the way for them being able to refuse if they're busy.
10668 - When we fail to bind a listener, try to provide a more useful
10669 log message: e.g., "Is Tor already running?"
10670 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
10671 Goldberg can prove things about our handshake protocol more
10673 - MaxConn has been obsolete for a while now. Document the ConnLimit
10674 config option, which is a *minimum* number of file descriptors
10675 that must be available else Tor refuses to start.
10676 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
10677 if you log to syslog and want something other than LOG_DAEMON.
10678 - Make dirservers generate a separate "guard" flag to mean,
10679 "would make a good entry guard". Make clients parse it and vote
10680 on it. Not used by clients yet.
10681 - Implement --with-libevent-dir option to ./configure. Also, improve
10682 search techniques to find libevent, and use those for openssl too.
10683 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
10684 - Only start testing reachability once we've established a
10685 circuit. This will make startup on dirservers less noisy.
10686 - Don't try to upload hidden service descriptors until we have
10687 established a circuit.
10688 - Fix the controller's "attachstream 0" command to treat conn like
10689 it just connected, doing address remapping, handling .exit and
10690 .onion idioms, and so on. Now we're more uniform in making sure
10691 that the controller hears about new and closing connections.
10694 Changes in version 0.1.1.12-alpha - 2006-01-11
10695 o Bugfixes on 0.1.1.x:
10696 - The fix to close duplicate server connections was closing all
10697 Tor client connections if they didn't establish a circuit
10698 quickly enough. Oops.
10699 - Fix minor memory issue (double-free) that happened on exit.
10701 o Bugfixes on 0.1.0.x:
10702 - Tor didn't warn when it failed to open a log file.
10705 Changes in version 0.1.1.11-alpha - 2006-01-10
10706 o Crashes in 0.1.1.x:
10707 - Include all the assert/crash fixes from 0.1.0.16.
10708 - If you start Tor and then quit very quickly, there were some
10709 races that tried to free things that weren't allocated yet.
10710 - Fix a rare memory stomp if you're running hidden services.
10711 - Fix segfault when specifying DirServer in config without nickname.
10712 - Fix a seg fault when you finish connecting to a server but at
10713 that moment you dump his server descriptor.
10714 - Extendcircuit and Attachstream controller commands would
10715 assert/crash if you don't give them enough arguments.
10716 - Fix an assert error when we're out of space in the connection_list
10717 and we try to post a hidden service descriptor (reported by weasel).
10718 - If you specify a relative torrc path and you set RunAsDaemon in
10719 your torrc, then it chdir()'s to the new directory. If you HUP,
10720 it tries to load the new torrc location, fails, and exits.
10721 The fix: no longer allow a relative path to torrc using -f.
10724 - Implement "entry guards": automatically choose a handful of entry
10725 nodes and stick with them for all circuits. Only pick new guards
10726 when the ones you have are unsuitable, and if the old guards
10727 become suitable again, switch back. This will increase security
10728 dramatically against certain end-point attacks. The EntryNodes
10729 config option now provides some hints about which entry guards you
10730 want to use most; and StrictEntryNodes means to only use those.
10731 - New directory logic: download by descriptor digest, not by
10732 fingerprint. Caches try to download all listed digests from
10733 authorities; clients try to download "best" digests from caches.
10734 This avoids partitioning and isolating attacks better.
10735 - Make the "stable" router flag in network-status be the median of
10736 the uptimes of running valid servers, and make clients pay
10737 attention to the network-status flags. Thus the cutoff adapts
10738 to the stability of the network as a whole, making IRC, IM, etc
10739 connections more reliable.
10742 - Tor servers with dynamic IP addresses were needing to wait 18
10743 hours before they could start doing reachability testing using
10744 the new IP address and ports. This is because they were using
10745 the internal descriptor to learn what to test, yet they were only
10746 rebuilding the descriptor once they decided they were reachable.
10747 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
10748 to download certain server descriptors, throw them away, and then
10749 fetch them again after 30 minutes. Now mirrors throw away these
10750 server descriptors so clients can't get them.
10751 - We were leaving duplicate connections to other ORs open for a week,
10752 rather than closing them once we detect a duplicate. This only
10753 really affected authdirservers, but it affected them a lot.
10754 - Spread the authdirservers' reachability testing over the entire
10755 testing interval, so we don't try to do 500 TLS's at once every
10759 - If the network is down, and we try to connect to a conn because
10760 we have a circuit in mind, and we timeout (30 seconds) because the
10761 network never answers, we were expiring the circuit, but we weren't
10762 obsoleting the connection or telling the entry_guards functions.
10763 - Some Tor servers process billions of cells per day. These statistics
10764 need to be uint64_t's.
10765 - Check for integer overflows in more places, when adding elements
10766 to smartlists. This could possibly prevent a buffer overflow
10767 on malicious huge inputs. I don't see any, but I haven't looked
10769 - ReachableAddresses kept growing new "reject *:*" lines on every
10771 - When you "setconf log" via the controller, it should remove all
10772 logs. We were automatically adding back in a "log notice stdout".
10773 - Newly bootstrapped Tor networks couldn't establish hidden service
10774 circuits until they had nodes with high uptime. Be more tolerant.
10775 - We were marking servers down when they could not answer every piece
10776 of the directory request we sent them. This was far too harsh.
10777 - Fix the torify (tsocks) config file to not use Tor for localhost
10779 - Directory authorities now go to the proper authority when asking for
10780 a networkstatus, even when they want a compressed one.
10781 - Fix a harmless bug that was causing Tor servers to log
10782 "Got an end because of misc error, but we're not an AP. Closing."
10783 - Authorities were treating their own descriptor changes as cosmetic,
10784 meaning the descriptor available in the network-status and the
10785 descriptor that clients downloaded were different.
10786 - The OS X installer was adding a symlink for tor_resolve but
10787 the binary was called tor-resolve (reported by Thomas Hardly).
10788 - Workaround a problem with some http proxies where they refuse GET
10789 requests that specify "Content-Length: 0" (reported by Adrian).
10790 - Fix wrong log message when you add a "HiddenServiceNodes" config
10791 line without any HiddenServiceDir line (reported by Chris Thomas).
10794 - Write the TorVersion into the state file so we have a prayer of
10795 keeping forward and backward compatibility.
10796 - Revive the FascistFirewall config option rather than eliminating it:
10797 now it's a synonym for ReachableAddresses *:80,*:443.
10798 - Clients choose directory servers from the network status lists,
10799 not from their internal list of router descriptors. Now they can
10800 go to caches directly rather than needing to go to authorities
10802 - Directory authorities ignore router descriptors that have only
10803 cosmetic differences: do this for 0.1.0.x servers now too.
10804 - Add a new flag to network-status indicating whether the server
10805 can answer v2 directory requests too.
10806 - Authdirs now stop whining so loudly about bad descriptors that
10807 they fetch from other dirservers. So when there's a log complaint,
10808 it's for sure from a freshly uploaded descriptor.
10809 - Reduce memory requirements in our structs by changing the order
10811 - There used to be two ways to specify your listening ports in a
10812 server descriptor: on the "router" line and with a separate "ports"
10813 line. Remove support for the "ports" line.
10814 - New config option "AuthDirRejectUnlisted" for auth dirservers as
10815 a panic button: if we get flooded with unusable servers we can
10816 revert to only listing servers in the approved-routers file.
10817 - Auth dir servers can now mark a fingerprint as "!reject" or
10818 "!invalid" in the approved-routers file (as its nickname), to
10819 refuse descriptors outright or include them but marked as invalid.
10820 - Servers store bandwidth history across restarts/crashes.
10821 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
10822 get a better idea of why their circuits failed. Not used yet.
10823 - Directory mirrors now cache up to 16 unrecognized network-status
10824 docs. Now we can add new authdirservers and they'll be cached too.
10825 - When picking a random directory, prefer non-authorities if any
10827 - New controller option "getinfo desc/all-recent" to fetch the
10828 latest server descriptor for every router that Tor knows about.
10831 Changes in version 0.1.0.16 - 2006-01-02
10832 o Crash bugfixes on 0.1.0.x:
10833 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
10834 corrupting the heap, losing FDs, or crashing when we need to resize
10835 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
10836 - It turns out sparc64 platforms crash on unaligned memory access
10837 too -- so detect and avoid this.
10838 - Handle truncated compressed data correctly (by detecting it and
10840 - Fix possible-but-unlikely free(NULL) in control.c.
10841 - When we were closing connections, there was a rare case that
10842 stomped on memory, triggering seg faults and asserts.
10843 - Avoid potential infinite recursion when building a descriptor. (We
10844 don't know that it ever happened, but better to fix it anyway.)
10845 - We were neglecting to unlink marked circuits from soon-to-close OR
10846 connections, which caused some rare scribbling on freed memory.
10847 - Fix a memory stomping race bug when closing the joining point of two
10848 rendezvous circuits.
10849 - Fix an assert in time parsing found by Steven Murdoch.
10851 o Other bugfixes on 0.1.0.x:
10852 - When we're doing reachability testing, provide more useful log
10853 messages so the operator knows what to expect.
10854 - Do not check whether DirPort is reachable when we are suppressing
10855 advertising it because of hibernation.
10856 - When building with -static or on Solaris, we sometimes needed -ldl.
10857 - When we're deciding whether a stream has enough circuits around
10858 that can handle it, count the freshly dirty ones and not the ones
10859 that are so dirty they won't be able to handle it.
10860 - When we're expiring old circuits, we had a logic error that caused
10861 us to close new rendezvous circuits rather than old ones.
10862 - Give a more helpful log message when you try to change ORPort via
10863 the controller: you should upgrade Tor if you want that to work.
10864 - We were failing to parse Tor versions that start with "Tor ".
10865 - Tolerate faulty streams better: when a stream fails for reason
10866 exitpolicy, stop assuming that the router is lying about his exit
10867 policy. When a stream fails for reason misc, allow it to retry just
10868 as if it was resolvefailed. When a stream has failed three times,
10869 reset its failure count so we can try again and get all three tries.
10872 Changes in version 0.1.1.10-alpha - 2005-12-11
10873 o Correctness bugfixes on 0.1.0.x:
10874 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
10875 corrupting the heap, losing FDs, or crashing when we need to resize
10876 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
10877 - Stop doing the complex voodoo overkill checking for insecure
10878 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
10879 - When we were closing connections, there was a rare case that
10880 stomped on memory, triggering seg faults and asserts.
10881 - We were neglecting to unlink marked circuits from soon-to-close OR
10882 connections, which caused some rare scribbling on freed memory.
10883 - When we're deciding whether a stream has enough circuits around
10884 that can handle it, count the freshly dirty ones and not the ones
10885 that are so dirty they won't be able to handle it.
10886 - Recover better from TCP connections to Tor servers that are
10887 broken but don't tell you (it happens!); and rotate TLS
10888 connections once a week.
10889 - When we're expiring old circuits, we had a logic error that caused
10890 us to close new rendezvous circuits rather than old ones.
10891 - Fix a scary-looking but apparently harmless bug where circuits
10892 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
10893 servers, and never switch to state CIRCUIT_STATE_OPEN.
10894 - When building with -static or on Solaris, we sometimes needed to
10896 - Give a useful message when people run Tor as the wrong user,
10897 rather than telling them to start chowning random directories.
10898 - We were failing to inform the controller about new .onion streams.
10900 o Security bugfixes on 0.1.0.x:
10901 - Refuse server descriptors if the fingerprint line doesn't match
10902 the included identity key. Tor doesn't care, but other apps (and
10903 humans) might actually be trusting the fingerprint line.
10904 - We used to kill the circuit when we receive a relay command we
10905 don't recognize. Now we just drop it.
10906 - Start obeying our firewall options more rigorously:
10907 . If we can't get to a dirserver directly, try going via Tor.
10908 . Don't ever try to connect (as a client) to a place our
10909 firewall options forbid.
10910 . If we specify a proxy and also firewall options, obey the
10911 firewall options even when we're using the proxy: some proxies
10912 can only proxy to certain destinations.
10913 - Fix a bug found by Lasse Overlier: when we were making internal
10914 circuits (intended to be cannibalized later for rendezvous and
10915 introduction circuits), we were picking them so that they had
10916 useful exit nodes. There was no need for this, and it actually
10917 aids some statistical attacks.
10918 - Start treating internal circuits and exit circuits separately.
10919 It's important to keep them separate because internal circuits
10920 have their last hops picked like middle hops, rather than like
10921 exit hops. So exiting on them will break the user's expectations.
10923 o Bugfixes on 0.1.1.x:
10924 - Take out the mis-feature where we tried to detect IP address
10925 flapping for people with DynDNS, and chose not to upload a new
10926 server descriptor sometimes.
10927 - Try to be compatible with OpenSSL 0.9.6 again.
10928 - Log fix: when the controller is logging about .onion addresses,
10929 sometimes it didn't include the ".onion" part of the address.
10930 - Don't try to modify options->DirServers internally -- if the
10931 user didn't specify any, just add the default ones directly to
10932 the trusted dirserver list. This fixes a bug where people running
10933 controllers would use SETCONF on some totally unrelated config
10934 option, and Tor would start yelling at them about changing their
10936 - Let the controller's redirectstream command specify a port, in
10937 case the controller wants to change that too.
10938 - When we requested a pile of server descriptors, we sometimes
10939 accidentally launched a duplicate request for the first one.
10940 - Bugfix for trackhostexits: write down the fingerprint of the
10941 chosen exit, not its nickname, because the chosen exit might not
10943 - When parsing foo.exit, if foo is unknown, and we are leaving
10944 circuits unattached, set the chosen_exit field and leave the
10945 address empty. This matters because controllers got confused
10947 - Directory authorities no longer try to download server
10948 descriptors that they know they will reject.
10950 o Features and updates:
10951 - Replace balanced trees with hash tables: this should make stuff
10952 significantly faster.
10953 - Resume using the AES counter-mode implementation that we ship,
10954 rather than OpenSSL's. Ours is significantly faster.
10955 - Many other CPU and memory improvements.
10956 - Add a new config option FastFirstHopPK (on by default) so clients
10957 do a trivial crypto handshake for their first hop, since TLS has
10958 already taken care of confidentiality and authentication.
10959 - Add a new config option TestSocks so people can see if their
10960 applications are using socks4, socks4a, socks5-with-ip, or
10961 socks5-with-hostname. This way they don't have to keep mucking
10962 with tcpdump and wondering if something got cached somewhere.
10963 - Warn when listening on a public address for socks. I suspect a
10964 lot of people are setting themselves up as open socks proxies,
10965 and they have no idea that jerks on the Internet are using them,
10966 since they simply proxy the traffic into the Tor network.
10967 - Add "private:*" as an alias in configuration for policies. Now
10968 you can simplify your exit policy rather than needing to list
10969 every single internal or nonroutable network space.
10970 - Add a new controller event type that allows controllers to get
10971 all server descriptors that were uploaded to a router in its role
10972 as authoritative dirserver.
10973 - Start shipping socks-extensions.txt, tor-doc-unix.html,
10974 tor-doc-server.html, and stylesheet.css in the tarball.
10975 - Stop shipping tor-doc.html in the tarball.
10978 Changes in version 0.1.1.9-alpha - 2005-11-15
10979 o Usability improvements:
10980 - Start calling it FooListenAddress rather than FooBindAddress,
10981 since few of our users know what it means to bind an address
10983 - Reduce clutter in server logs. We're going to try to make
10984 them actually usable now. New config option ProtocolWarnings that
10985 lets you hear about how _other Tors_ are breaking the protocol. Off
10987 - Divide log messages into logging domains. Once we put some sort
10988 of interface on this, it will let people looking at more verbose
10989 log levels specify the topics they want to hear more about.
10990 - Make directory servers return better http 404 error messages
10991 instead of a generic "Servers unavailable".
10992 - Check for even more Windows version flags when writing the platform
10993 string in server descriptors, and note any we don't recognize.
10994 - Clean up more of the OpenSSL memory when exiting, so we can detect
10995 memory leaks better.
10996 - Make directory authorities be non-versioning, non-naming by
10997 default. Now we can add new directory servers without requiring
10998 their operators to pay close attention.
10999 - When logging via syslog, include the pid whenever we provide
11000 a log entry. Suggested by Todd Fries.
11002 o Performance improvements:
11003 - Directory servers now silently throw away new descriptors that
11004 haven't changed much if the timestamps are similar. We do this to
11005 tolerate older Tor servers that upload a new descriptor every 15
11006 minutes. (It seemed like a good idea at the time.)
11007 - Inline bottleneck smartlist functions; use fast versions by default.
11008 - Add a "Map from digest to void*" abstraction digestmap_t so we
11009 can do less hex encoding/decoding. Use it in router_get_by_digest()
11010 to resolve a performance bottleneck.
11011 - Allow tor_gzip_uncompress to extract as much as possible from
11012 truncated compressed data. Try to extract as many
11013 descriptors as possible from truncated http responses (when
11014 DIR_PURPOSE_FETCH_ROUTERDESC).
11015 - Make circ->onionskin a pointer, not a static array. moria2 was using
11016 125000 circuit_t's after it had been up for a few weeks, which
11017 translates to 20+ megs of wasted space.
11018 - The private half of our EDH handshake keys are now chosen out
11019 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
11021 o Security improvements:
11022 - Start making directory caches retain old routerinfos, so soon
11023 clients can start asking by digest of descriptor rather than by
11024 fingerprint of server.
11025 - Add half our entropy from RAND_poll in OpenSSL. This knows how
11026 to use egd (if present), openbsd weirdness (if present), vms/os2
11027 weirdness (if we ever port there), and more in the future.
11029 o Bugfixes on 0.1.0.x:
11030 - Do round-robin writes of at most 16 kB per write. This might be
11031 more fair on loaded Tor servers, and it might resolve our Windows
11032 crash bug. It might also slow things down.
11033 - Our TLS handshakes were generating a single public/private
11034 keypair for the TLS context, rather than making a new one for
11035 each new connections. Oops. (But we were still rotating them
11036 periodically, so it's not so bad.)
11037 - When we were cannibalizing a circuit with a particular exit
11038 node in mind, we weren't checking to see if that exit node was
11039 already present earlier in the circuit. Oops.
11040 - When a Tor server's IP changes (e.g. from a dyndns address),
11041 upload a new descriptor so clients will learn too.
11042 - Really busy servers were keeping enough circuits open on stable
11043 connections that they were wrapping around the circuit_id
11044 space. (It's only two bytes.) This exposed a bug where we would
11045 feel free to reuse a circuit_id even if it still exists but has
11046 been marked for close. Try to fix this bug. Some bug remains.
11047 - If we would close a stream early (e.g. it asks for a .exit that
11048 we know would refuse it) but the LeaveStreamsUnattached config
11049 option is set by the controller, then don't close it.
11051 o Bugfixes on 0.1.1.8-alpha:
11052 - Fix a big pile of memory leaks, some of them serious.
11053 - Do not try to download a routerdesc if we would immediately reject
11055 - Resume inserting a newline between all router descriptors when
11056 generating (old style) signed directories, since our spec says
11058 - When providing content-type application/octet-stream for
11059 server descriptors using .z, we were leaving out the
11060 content-encoding header. Oops. (Everything tolerated this just
11061 fine, but that doesn't mean we need to be part of the problem.)
11062 - Fix a potential seg fault in getconf and getinfo using version 1
11063 of the controller protocol.
11064 - Avoid crash: do not check whether DirPort is reachable when we
11065 are suppressing it because of hibernation.
11066 - Make --hash-password not crash on exit.
11069 Changes in version 0.1.1.8-alpha - 2005-10-07
11070 o New features (major):
11071 - Clients don't download or use the directory anymore. Now they
11072 download and use network-statuses from the trusted dirservers,
11073 and fetch individual server descriptors as needed from mirrors.
11074 See dir-spec.txt for all the gory details.
11075 - Be more conservative about whether to advertise our DirPort.
11076 The main change is to not advertise if we're running at capacity
11077 and either a) we could hibernate or b) our capacity is low and
11078 we're using a default DirPort.
11079 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
11081 o New features (minor):
11082 - Try to be smart about when to retry network-status and
11083 server-descriptor fetches. Still needs some tuning.
11084 - Stop parsing, storing, or using running-routers output (but
11085 mirrors still cache and serve it).
11086 - Consider a threshold of versioning dirservers (dirservers who have
11087 an opinion about which Tor versions are still recommended) before
11088 deciding whether to warn the user that he's obsolete.
11089 - Dirservers can now reject/invalidate by key and IP, with the
11090 config options "AuthDirInvalid" and "AuthDirReject". This is
11091 useful since currently we automatically list servers as running
11092 and usable even if we know they're jerks.
11093 - Provide dire warnings to any users who set DirServer; move it out
11094 of torrc.sample and into torrc.complete.
11095 - Add MyFamily to torrc.sample in the server section.
11096 - Add nicknames to the DirServer line, so we can refer to them
11097 without requiring all our users to memorize their IP addresses.
11098 - When we get an EOF or a timeout on a directory connection, note
11099 how many bytes of serverdesc we are dropping. This will help
11100 us determine whether it is smart to parse incomplete serverdesc
11102 - Add a new function to "change pseudonyms" -- that is, to stop
11103 using any currently-dirty circuits for new streams, so we don't
11104 link new actions to old actions. Currently it's only called on
11105 HUP (or SIGNAL RELOAD).
11106 - On sighup, if UseHelperNodes changed to 1, use new circuits.
11107 - Start using RAND_bytes rather than RAND_pseudo_bytes from
11108 OpenSSL. Also, reseed our entropy every hour, not just at
11109 startup. And entropy in 512-bit chunks, not 160-bit chunks.
11111 o Fixes on 0.1.1.7-alpha:
11112 - Nobody ever implemented EVENT_ADDRMAP for control protocol
11113 version 0, so don't let version 0 controllers ask for it.
11114 - If you requested something with too many newlines via the
11115 v1 controller protocol, you could crash tor.
11116 - Fix a number of memory leaks, including some pretty serious ones.
11117 - Re-enable DirPort testing again, so Tor servers will be willing
11118 to advertise their DirPort if it's reachable.
11119 - On TLS handshake, only check the other router's nickname against
11120 its expected nickname if is_named is set.
11122 o Fixes forward-ported from 0.1.0.15:
11123 - Don't crash when we don't have any spare file descriptors and we
11124 try to spawn a dns or cpu worker.
11125 - Make the numbers in read-history and write-history into uint64s,
11126 so they don't overflow and publish negatives in the descriptor.
11128 o Fixes on 0.1.0.x:
11129 - For the OS X package's modified privoxy config file, comment
11130 out the "logfile" line so we don't log everything passed
11132 - We were whining about using socks4 or socks5-with-local-lookup
11133 even when it's an IP in the "virtual" range we designed exactly
11135 - We were leaking some memory every time the client changes IPs.
11136 - Never call free() on tor_malloc()d memory. This will help us
11137 use dmalloc to detect memory leaks.
11138 - Check for named servers when looking them up by nickname;
11139 warn when we'recalling a non-named server by its nickname;
11140 don't warn twice about the same name.
11141 - Try to list MyFamily elements by key, not by nickname, and warn
11142 if we've not heard of the server.
11143 - Make windows platform detection (uname equivalent) smarter.
11144 - It turns out sparc64 doesn't like unaligned access either.
11147 Changes in version 0.1.0.15 - 2005-09-23
11148 o Bugfixes on 0.1.0.x:
11149 - Reject ports 465 and 587 (spam targets) in default exit policy.
11150 - Don't crash when we don't have any spare file descriptors and we
11151 try to spawn a dns or cpu worker.
11152 - Get rid of IgnoreVersion undocumented config option, and make us
11153 only warn, never exit, when we're running an obsolete version.
11154 - Don't try to print a null string when your server finds itself to
11155 be unreachable and the Address config option is empty.
11156 - Make the numbers in read-history and write-history into uint64s,
11157 so they don't overflow and publish negatives in the descriptor.
11158 - Fix a minor memory leak in smartlist_string_remove().
11159 - We were only allowing ourselves to upload a server descriptor at
11160 most every 20 minutes, even if it changed earlier than that.
11161 - Clean up log entries that pointed to old URLs.
11164 Changes in version 0.1.1.7-alpha - 2005-09-14
11165 o Fixes on 0.1.1.6-alpha:
11166 - Exit servers were crashing when people asked them to make a
11167 connection to an address not in their exit policy.
11168 - Looking up a non-existent stream for a v1 control connection would
11170 - Fix a seg fault if we ask a dirserver for a descriptor by
11171 fingerprint but he doesn't know about him.
11172 - SETCONF was appending items to linelists, not clearing them.
11173 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
11174 out and refuse the setconf if it would fail.
11175 - Downgrade the dirserver log messages when whining about
11179 - Add Peter Palfrader's check-tor script to tor/contrib/
11180 It lets you easily check whether a given server (referenced by
11181 nickname) is reachable by you.
11182 - Numerous changes to move towards client-side v2 directories. Not
11185 o Fixes on 0.1.0.x:
11186 - If the user gave tor an odd number of command-line arguments,
11187 we were silently ignoring the last one. Now we complain and fail.
11188 [This wins the oldest-bug prize -- this bug has been present since
11189 November 2002, as released in Tor 0.0.0.]
11190 - Do not use unaligned memory access on alpha, mips, or mipsel.
11191 It *works*, but is very slow, so we treat them as if it doesn't.
11192 - Retry directory requests if we fail to get an answer we like
11193 from a given dirserver (we were retrying before, but only if
11194 we fail to connect).
11195 - When writing the RecommendedVersions line, sort them first.
11196 - When the client asked for a rendezvous port that the hidden
11197 service didn't want to provide, we were sending an IP address
11198 back along with the end cell. Fortunately, it was zero. But stop
11200 - Correct "your server is reachable" log entries to indicate that
11201 it was self-testing that told us so.
11204 Changes in version 0.1.1.6-alpha - 2005-09-09
11205 o Fixes on 0.1.1.5-alpha:
11206 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
11207 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
11208 - Fix bug with tor_memmem finding a match at the end of the string.
11209 - Make unit tests run without segfaulting.
11210 - Resolve some solaris x86 compile warnings.
11211 - Handle duplicate lines in approved-routers files without warning.
11212 - Fix bug where as soon as a server refused any requests due to his
11213 exit policy (e.g. when we ask for localhost and he tells us that's
11214 127.0.0.1 and he won't do it), we decided he wasn't obeying his
11215 exit policy using him for any exits.
11216 - Only do openssl hardware accelerator stuff if openssl version is
11219 o New controller features/fixes:
11220 - Add a "RESETCONF" command so you can set config options like
11221 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
11222 a config option in the torrc with no value, then it clears it
11223 entirely (rather than setting it to its default).
11224 - Add a "GETINFO config-file" to tell us where torrc is.
11225 - Avoid sending blank lines when GETINFO replies should be empty.
11226 - Add a QUIT command for the controller (for using it manually).
11227 - Fix a bug in SAVECONF that was adding default dirservers and
11228 other redundant entries to the torrc file.
11230 o Start on the new directory design:
11231 - Generate, publish, cache, serve new network-status format.
11232 - Publish individual descriptors (by fingerprint, by "all", and by
11234 - Publish client and server recommended versions separately.
11235 - Allow tor_gzip_uncompress() to handle multiple concatenated
11236 compressed strings. Serve compressed groups of router
11237 descriptors. The compression logic here could be more
11239 - Distinguish v1 authorities (all currently trusted directories)
11240 from v2 authorities (all trusted directories).
11241 - Change DirServers config line to note which dirs are v1 authorities.
11242 - Add configuration option "V1AuthoritativeDirectory 1" which
11243 moria1, moria2, and tor26 should set.
11244 - Remove option when getting directory cache to see whether they
11245 support running-routers; they all do now. Replace it with one
11246 to see whether caches support v2 stuff.
11249 - Dirservers now do their own external reachability testing of each
11250 Tor server, and only list them as running if they've been found to
11251 be reachable. We also send back warnings to the server's logs if
11252 it uploads a descriptor that we already believe is unreachable.
11253 - Implement exit enclaves: if we know an IP address for the
11254 destination, and there's a running Tor server at that address
11255 which allows exit to the destination, then extend the circuit to
11256 that exit first. This provides end-to-end encryption and end-to-end
11257 authentication. Also, if the user wants a .exit address or enclave,
11258 use 4 hops rather than 3, and cannibalize a general circ for it
11260 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
11261 controller. Also, rotate dns and cpu workers if the controller
11262 changes options that will affect them; and initialize the dns
11263 worker cache tree whether or not we start out as a server.
11264 - Only upload a new server descriptor when options change, 18
11265 hours have passed, uptime is reset, or bandwidth changes a lot.
11266 - Check [X-]Forwarded-For headers in HTTP requests when generating
11267 log messages. This lets people run dirservers (and caches) behind
11268 Apache but still know which IP addresses are causing warnings.
11270 o Config option changes:
11271 - Replace (Fascist)Firewall* config options with a new
11272 ReachableAddresses option that understands address policies.
11273 For example, "ReachableAddresses *:80,*:443"
11274 - Get rid of IgnoreVersion undocumented config option, and make us
11275 only warn, never exit, when we're running an obsolete version.
11276 - Make MonthlyAccountingStart config option truly obsolete now.
11278 o Fixes on 0.1.0.x:
11279 - Reject ports 465 and 587 in the default exit policy, since
11280 people have started using them for spam too.
11281 - It turns out we couldn't bootstrap a network since we added
11282 reachability detection in 0.1.0.1-rc. Good thing the Tor network
11283 has never gone down. Add an AssumeReachable config option to let
11284 servers and dirservers bootstrap. When we're trying to build a
11285 high-uptime or high-bandwidth circuit but there aren't enough
11286 suitable servers, try being less picky rather than simply failing.
11287 - Our logic to decide if the OR we connected to was the right guy
11288 was brittle and maybe open to a mitm for unverified routers.
11289 - We weren't cannibalizing circuits correctly for
11290 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
11291 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
11292 build those from scratch. This should make hidden services faster.
11293 - Predict required circuits better, with an eye toward making hidden
11294 services faster on the service end.
11295 - Retry streams if the exit node sends back a 'misc' failure. This
11296 should result in fewer random failures. Also, after failing
11297 from resolve failed or misc, reset the num failures, so we give
11298 it a fair shake next time we try.
11299 - Clean up the rendezvous warn log msgs, and downgrade some to info.
11300 - Reduce severity on logs about dns worker spawning and culling.
11301 - When we're shutting down and we do something like try to post a
11302 server descriptor or rendezvous descriptor, don't complain that
11303 we seem to be unreachable. Of course we are, we're shutting down.
11304 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
11305 We don't use them yet, but maybe one day our DNS resolver will be
11306 able to discover them.
11307 - Make ContactInfo mandatory for authoritative directory servers.
11308 - Require server descriptors to list IPv4 addresses -- hostnames
11309 are no longer allowed. This also fixes some potential security
11310 problems with people providing hostnames as their address and then
11311 preferentially resolving them to partition users.
11312 - Change log line for unreachability to explicitly suggest /etc/hosts
11313 as the culprit. Also make it clearer what IP address and ports we're
11314 testing for reachability.
11315 - Put quotes around user-supplied strings when logging so users are
11316 more likely to realize if they add bad characters (like quotes)
11318 - Let auth dir servers start without specifying an Address config
11320 - Make unit tests (and other invocations that aren't the real Tor)
11321 run without launching listeners, creating subdirectories, and so on.
11324 Changes in version 0.1.1.5-alpha - 2005-08-08
11325 o Bugfixes included in 0.1.0.14.
11327 o Bugfixes on 0.1.0.x:
11328 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
11329 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
11330 it would silently using ignore the 6668.
11333 Changes in version 0.1.0.14 - 2005-08-08
11334 o Bugfixes on 0.1.0.x:
11335 - Fix the other half of the bug with crypto handshakes
11337 - Fix an assert trigger if you send a 'signal term' via the
11338 controller when it's listening for 'event info' messages.
11341 Changes in version 0.1.1.4-alpha - 2005-08-04
11342 o Bugfixes included in 0.1.0.13.
11345 - Improve tor_gettimeofday() granularity on windows.
11346 - Make clients regenerate their keys when their IP address changes.
11347 - Implement some more GETINFO goodness: expose helper nodes, config
11348 options, getinfo keys.
11351 Changes in version 0.1.0.13 - 2005-08-04
11352 o Bugfixes on 0.1.0.x:
11353 - Fix a critical bug in the security of our crypto handshakes.
11354 - Fix a size_t underflow in smartlist_join_strings2() that made
11355 it do bad things when you hand it an empty smartlist.
11356 - Fix Windows installer to ship Tor license (thanks to Aphex for
11357 pointing out this oversight) and put a link to the doc directory
11359 - Explicitly set no-unaligned-access for sparc: it turns out the
11360 new gcc's let you compile broken code, but that doesn't make it
11364 Changes in version 0.1.1.3-alpha - 2005-07-23
11365 o Bugfixes on 0.1.1.2-alpha:
11366 - Fix a bug in handling the controller's "post descriptor"
11368 - Fix several bugs in handling the controller's "extend circuit"
11370 - Fix a bug in handling the controller's "stream status" event.
11371 - Fix an assert failure if we have a controller listening for
11372 circuit events and we go offline.
11373 - Re-allow hidden service descriptors to publish 0 intro points.
11374 - Fix a crash when generating your hidden service descriptor if
11375 you don't have enough intro points already.
11377 o New features on 0.1.1.2-alpha:
11378 - New controller function "getinfo accounting", to ask how
11379 many bytes we've used in this time period.
11380 - Experimental support for helper nodes: a lot of the risk from
11381 a small static adversary comes because users pick new random
11382 nodes every time they rebuild a circuit. Now users will try to
11383 stick to the same small set of entry nodes if they can. Not
11384 enabled by default yet.
11386 o Bugfixes on 0.1.0.12:
11387 - If you're an auth dir server, always publish your dirport,
11388 even if you haven't yet found yourself to be reachable.
11389 - Fix a size_t underflow in smartlist_join_strings2() that made
11390 it do bad things when you hand it an empty smartlist.
11393 Changes in version 0.1.0.12 - 2005-07-18
11394 o New directory servers:
11395 - tor26 has changed IP address.
11397 o Bugfixes on 0.1.0.x:
11398 - Fix a possible double-free in tor_gzip_uncompress().
11399 - When --disable-threads is set, do not search for or link against
11400 pthreads libraries.
11401 - Don't trigger an assert if an authoritative directory server
11402 claims its dirport is 0.
11403 - Fix bug with removing Tor as an NT service: some people were
11404 getting "The service did not return an error." Thanks to Matt
11408 Changes in version 0.1.1.2-alpha - 2005-07-15
11409 o New directory servers:
11410 - tor26 has changed IP address.
11412 o Bugfixes on 0.1.0.x, crashes/leaks:
11413 - Port the servers-not-obeying-their-exit-policies fix from
11415 - Fix an fd leak in start_daemon().
11416 - On Windows, you can't always reopen a port right after you've
11417 closed it. So change retry_listeners() to only close and re-open
11418 ports that have changed.
11419 - Fix a possible double-free in tor_gzip_uncompress().
11421 o Bugfixes on 0.1.0.x, usability:
11422 - When tor_socketpair() fails in Windows, give a reasonable
11423 Windows-style errno back.
11424 - Let people type "tor --install" as well as "tor -install" when
11426 want to make it an NT service.
11427 - NT service patch from Matt Edman to improve error messages.
11428 - When the controller asks for a config option with an abbreviated
11429 name, give the full name in our response.
11430 - Correct the man page entry on TrackHostExitsExpire.
11431 - Looks like we were never delivering deflated (i.e. compressed)
11432 running-routers lists, even when asked. Oops.
11433 - When --disable-threads is set, do not search for or link against
11434 pthreads libraries.
11436 o Bugfixes on 0.1.1.x:
11437 - Fix a seg fault with autodetecting which controller version is
11441 - New hidden service descriptor format: put a version in it, and
11442 let people specify introduction/rendezvous points that aren't
11443 in "the directory" (which is subjective anyway).
11444 - Allow the DEBUG controller event to work again. Mark certain log
11445 entries as "don't tell this to controllers", so we avoid cycles.
11448 Changes in version 0.1.0.11 - 2005-06-30
11449 o Bugfixes on 0.1.0.x:
11450 - Fix major security bug: servers were disregarding their
11451 exit policies if clients behaved unexpectedly.
11452 - Make OS X init script check for missing argument, so we don't
11453 confuse users who invoke it incorrectly.
11454 - Fix a seg fault in "tor --hash-password foo".
11455 - The MAPADDRESS control command was broken.
11458 Changes in version 0.1.1.1-alpha - 2005-06-29
11460 - Make OS X init script check for missing argument, so we don't
11461 confuse users who invoke it incorrectly.
11462 - Fix a seg fault in "tor --hash-password foo".
11463 - Fix a possible way to DoS dirservers.
11464 - When we complain that your exit policy implicitly allows local or
11465 private address spaces, name them explicitly so operators can
11467 - Make the log message less scary when all the dirservers are
11468 temporarily unreachable.
11469 - We were printing the number of idle dns workers incorrectly when
11473 - Revised controller protocol (version 1) that uses ascii rather
11474 than binary. Add supporting libraries in python and java so you
11475 can use the controller from your applications without caring how
11476 our protocol works.
11477 - Spiffy new support for crypto hardware accelerators. Can somebody
11481 Changes in version 0.0.9.10 - 2005-06-16
11482 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
11483 - Refuse relay cells that claim to have a length larger than the
11484 maximum allowed. This prevents a potential attack that could read
11485 arbitrary memory (e.g. keys) from an exit server's process
11489 Changes in version 0.1.0.10 - 2005-06-14
11490 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
11491 libevent before 1.1a.
11494 Changes in version 0.1.0.9-rc - 2005-06-09
11496 - Reset buf->highwater every time buf_shrink() is called, not just on
11497 a successful shrink. This was causing significant memory bloat.
11498 - Fix buffer overflow when checking hashed passwords.
11499 - Security fix: if seeding the RNG on Win32 fails, quit.
11500 - Allow seeding the RNG on Win32 even when you're not running as
11502 - Disable threading on Solaris too. Something is wonky with it,
11503 cpuworkers, and reentrant libs.
11504 - Reenable the part of the code that tries to flush as soon as an
11505 OR outbuf has a full TLS record available. Perhaps this will make
11506 OR outbufs not grow as huge except in rare cases, thus saving lots
11507 of CPU time plus memory.
11508 - Reject malformed .onion addresses rather then passing them on as
11509 normal web requests.
11510 - Adapt patch from Adam Langley: fix possible memory leak in
11511 tor_lookup_hostname().
11512 - Initialize libevent later in the startup process, so the logs are
11513 already established by the time we start logging libevent warns.
11514 - Use correct errno on win32 if libevent fails.
11515 - Check and warn about known-bad/slow libevent versions.
11516 - Pay more attention to the ClientOnly config option.
11517 - Have torctl.in/tor.sh.in check for location of su binary (needed
11519 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
11520 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
11521 HttpProxyAuthenticator
11522 - Stop warning about sigpipes in the logs. We're going to
11523 pretend that getting these occassionally is normal and fine.
11524 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
11526 installer screens; and don't put stuff into StartupItems unless
11527 the user asks you to.
11528 - Require servers that use the default dirservers to have public IP
11529 addresses. We have too many servers that are configured with private
11530 IPs and their admins never notice the log entries complaining that
11531 their descriptors are being rejected.
11532 - Add OSX uninstall instructions. An actual uninstall script will
11536 Changes in version 0.1.0.8-rc - 2005-05-23
11538 - It turns out that kqueue on OS X 10.3.9 was causing kernel
11539 panics. Disable kqueue on all OS X Tors.
11540 - Fix RPM: remove duplicate line accidentally added to the rpm
11542 - Disable threads on openbsd too, since its gethostaddr is not
11544 - Tolerate libevent 0.8 since it still works, even though it's
11546 - Enable building on Red Hat 9.0 again.
11547 - Allow the middle hop of the testing circuit to be running any
11548 version, now that most of them have the bugfix to let them connect
11549 to unknown servers. This will allow reachability testing to work
11550 even when 0.0.9.7-0.0.9.9 become obsolete.
11551 - Handle relay cells with rh.length too large. This prevents
11552 a potential attack that could read arbitrary memory (maybe even
11553 keys) from the exit server's process.
11554 - We screwed up the dirport reachability testing when we don't yet
11555 have a cached version of the directory. Hopefully now fixed.
11556 - Clean up router_load_single_router() (used by the controller),
11557 so it doesn't seg fault on error.
11558 - Fix a minor memory leak when somebody establishes an introduction
11559 point at your Tor server.
11560 - If a socks connection ends because read fails, don't warn that
11561 you're not sending a socks reply back.
11564 - Add HttpProxyAuthenticator config option too, that works like
11565 the HttpsProxyAuthenticator config option.
11566 - Encode hashed controller passwords in hex instead of base64,
11567 to make it easier to write controllers.
11570 Changes in version 0.1.0.7-rc - 2005-05-17
11572 - Fix a bug in the OS X package installer that prevented it from
11573 installing on Tiger.
11574 - Fix a script bug in the OS X package installer that made it
11575 complain during installation.
11576 - Find libevent even if it's hiding in /usr/local/ and your
11577 CFLAGS and LDFLAGS don't tell you to look there.
11578 - Be able to link with libevent as a shared library (the default
11579 after 1.0d), even if it's hiding in /usr/local/lib and even
11580 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
11581 assuming you're running gcc. Otherwise fail and give a useful
11583 - Fix a bug in the RPM packager: set home directory for _tor to
11584 something more reasonable when first installing.
11585 - Free a minor amount of memory that is still reachable on exit.
11588 Changes in version 0.1.0.6-rc - 2005-05-14
11590 - Implement --disable-threads configure option. Disable threads on
11591 netbsd by default, because it appears to have no reentrant resolver
11593 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
11594 release (1.1) detects and disables kqueue if it's broken.
11595 - Append default exit policy before checking for implicit internal
11596 addresses. Now we don't log a bunch of complaints on startup
11597 when using the default exit policy.
11598 - Some people were putting "Address " in their torrc, and they had
11599 a buggy resolver that resolved " " to 0.0.0.0. Oops.
11600 - If DataDir is ~/.tor, and that expands to /.tor, then default to
11601 LOCALSTATEDIR/tor instead.
11602 - Fix fragmented-message bug in TorControl.py.
11603 - Resolve a minor bug which would prevent unreachable dirports
11604 from getting suppressed in the published descriptor.
11605 - When the controller gave us a new descriptor, we weren't resolving
11606 it immediately, so Tor would think its address was 0.0.0.0 until
11607 we fetched a new directory.
11608 - Fix an uppercase/lowercase case error in suppressing a bogus
11609 libevent warning on some Linuxes.
11612 - Begin scrubbing sensitive strings from logs by default. Turn off
11613 the config option SafeLogging if you need to do debugging.
11614 - Switch to a new buffer management algorithm, which tries to avoid
11615 reallocing and copying quite as much. In first tests it looks like
11616 it uses *more* memory on average, but less cpu.
11617 - First cut at support for "create-fast" cells. Clients can use
11618 these when extending to their first hop, since the TLS already
11619 provides forward secrecy and authentication. Not enabled on
11621 - When dirservers refuse a router descriptor, we now log its
11622 contactinfo, platform, and the poster's IP address.
11623 - Call tor_free_all instead of connections_free_all after forking, to
11624 save memory on systems that need to fork.
11625 - Whine at you if you're a server and you don't set your contactinfo.
11626 - Implement --verify-config command-line option to check if your torrc
11627 is valid without actually launching Tor.
11628 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
11629 rather than just rejecting it.
11632 Changes in version 0.1.0.5-rc - 2005-04-27
11634 - Stop trying to print a null pointer if an OR conn fails because
11635 we didn't like its cert.
11637 - Switch our internal buffers implementation to use a ring buffer,
11638 to hopefully improve performance for fast servers a lot.
11639 - Add HttpsProxyAuthenticator support (basic auth only), based
11640 on patch from Adam Langley.
11641 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
11642 the fast servers that have been joining lately.
11643 - Give hidden service accesses extra time on the first attempt,
11644 since 60 seconds is often only barely enough. This might improve
11646 - Improve performance for dirservers: stop re-parsing the whole
11647 directory every time you regenerate it.
11648 - Add more debugging info to help us find the weird dns freebsd
11649 pthreads bug; cleaner debug messages to help track future issues.
11652 Changes in version 0.0.9.9 - 2005-04-23
11653 o Bugfixes on 0.0.9.x:
11654 - If unofficial Tor clients connect and send weird TLS certs, our
11655 Tor server triggers an assert. This release contains a minimal
11656 backport from the broader fix that we put into 0.1.0.4-rc.
11659 Changes in version 0.1.0.4-rc - 2005-04-23
11661 - If unofficial Tor clients connect and send weird TLS certs, our
11662 Tor server triggers an assert. Stop asserting, and start handling
11663 TLS errors better in other situations too.
11664 - When the controller asks us to tell it about all the debug-level
11665 logs, it turns out we were generating debug-level logs while
11666 telling it about them, which turns into a bad loop. Now keep
11667 track of whether you're sending a debug log to the controller,
11668 and don't log when you are.
11669 - Fix the "postdescriptor" feature of the controller interface: on
11670 non-complete success, only say "done" once.
11672 - Clients are now willing to load balance over up to 2mB, not 1mB,
11673 of advertised bandwidth capacity.
11674 - Add a NoPublish config option, so you can be a server (e.g. for
11675 testing running Tor servers in other Tor networks) without
11676 publishing your descriptor to the primary dirservers.
11679 Changes in version 0.1.0.3-rc - 2005-04-08
11680 o Improvements on 0.1.0.2-rc:
11681 - Client now retries when streams end early for 'hibernating' or
11682 'resource limit' reasons, rather than failing them.
11683 - More automated handling for dirserver operators:
11684 - Automatically approve nodes running 0.1.0.2-rc or later,
11685 now that the the reachability detection stuff is working.
11686 - Now we allow two unverified servers with the same nickname
11687 but different keys. But if a nickname is verified, only that
11688 nickname+key are allowed.
11689 - If you're an authdirserver connecting to an address:port,
11690 and it's not the OR you were expecting, forget about that
11691 descriptor. If he *was* the one you were expecting, then forget
11692 about all other descriptors for that address:port.
11693 - Allow servers to publish descriptors from 12 hours in the future.
11694 Corollary: only whine about clock skew from the dirserver if
11695 he's a trusted dirserver (since now even verified servers could
11696 have quite wrong clocks).
11697 - Adjust maximum skew and age for rendezvous descriptors: let skew
11698 be 48 hours rather than 90 minutes.
11699 - Efficiency improvements:
11700 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
11701 it much faster to look up a circuit for each relay cell.
11702 - Remove most calls to assert_all_pending_dns_resolves_ok(),
11703 since they're eating our cpu on exit nodes.
11704 - Stop wasting time doing a case insensitive comparison for every
11705 dns name every time we do any lookup. Canonicalize the names to
11706 lowercase and be done with it.
11707 - Start sending 'truncated' cells back rather than destroy cells,
11708 if the circuit closes in front of you. This means we won't have
11709 to abandon partially built circuits.
11710 - Only warn once per nickname from add_nickname_list_to_smartlist
11711 per failure, so an entrynode or exitnode choice that's down won't
11713 - Put a note in the torrc about abuse potential with the default
11715 - Revise control spec and implementation to allow all log messages to
11716 be sent to controller with their severities intact (suggested by
11717 Matt Edman). Update TorControl to handle new log event types.
11718 - Provide better explanation messages when controller's POSTDESCRIPTOR
11720 - Stop putting nodename in the Platform string in server descriptors.
11721 It doesn't actually help, and it is confusing/upsetting some people.
11723 o Bugfixes on 0.1.0.2-rc:
11724 - We were printing the host mask wrong in exit policies in server
11725 descriptors. This isn't a critical bug though, since we were still
11726 obeying the exit policy internally.
11727 - Fix Tor when compiled with libevent but without pthreads: move
11728 connection_unregister() from _connection_free() to
11730 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
11731 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
11732 when we look through the connection array, we'll find any of the
11733 cpu/dnsworkers. This is no good.
11735 o Bugfixes on 0.0.9.8:
11736 - Fix possible bug on threading platforms (e.g. win32) which was
11737 leaking a file descriptor whenever a cpuworker or dnsworker died.
11738 - When using preferred entry or exit nodes, ignore whether the
11739 circuit wants uptime or capacity. They asked for the nodes, they
11741 - chdir() to your datadirectory at the *end* of the daemonize process,
11742 not the beginning. This was a problem because the first time you
11743 run tor, if your datadir isn't there, and you have runasdaemon set
11744 to 1, it will try to chdir to it before it tries to create it. Oops.
11745 - Handle changed router status correctly when dirserver reloads
11746 fingerprint file. We used to be dropping all unverified descriptors
11747 right then. The bug was hidden because we would immediately
11748 fetch a directory from another dirserver, which would include the
11749 descriptors we just dropped.
11750 - When we're connecting to an OR and he's got a different nickname/key
11751 than we were expecting, only complain loudly if we're an OP or a
11752 dirserver. Complaining loudly to the OR admins just confuses them.
11753 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
11754 artificially capped at 500kB.
11757 Changes in version 0.0.9.8 - 2005-04-07
11758 o Bugfixes on 0.0.9.x:
11759 - We have a bug that I haven't found yet. Sometimes, very rarely,
11760 cpuworkers get stuck in the 'busy' state, even though the cpuworker
11761 thinks of itself as idle. This meant that no new circuits ever got
11762 established. Here's a workaround to kill any cpuworker that's been
11763 busy for more than 100 seconds.
11766 Changes in version 0.1.0.2-rc - 2005-04-01
11767 o Bugfixes on 0.1.0.1-rc:
11768 - Fixes on reachability detection:
11769 - Don't check for reachability while hibernating.
11770 - If ORPort is reachable but DirPort isn't, still publish the
11771 descriptor, but zero out DirPort until it's found reachable.
11772 - When building testing circs for ORPort testing, use only
11773 high-bandwidth nodes, so fewer circuits fail.
11774 - Complain about unreachable ORPort separately from unreachable
11775 DirPort, so the user knows what's going on.
11776 - Make sure we only conclude ORPort reachability if we didn't
11777 initiate the conn. Otherwise we could falsely conclude that
11778 we're reachable just because we connected to the guy earlier
11779 and he used that same pipe to extend to us.
11780 - Authdirservers shouldn't do ORPort reachability detection,
11781 since they're in clique mode, so it will be rare to find a
11782 server not already connected to them.
11783 - When building testing circuits, always pick middle hops running
11784 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
11785 bug. (This is a kludge; it will go away when 0.0.9.x becomes
11787 - When we decide we're reachable, actually publish our descriptor
11789 - Fix bug in redirectstream in the controller.
11790 - Fix the state descriptor strings so logs don't claim edge streams
11791 are in a different state than they actually are.
11792 - Use recent libevent features when possible (this only really affects
11793 win32 and osx right now, because the new libevent with these
11794 features hasn't been released yet). Add code to suppress spurious
11796 - Prevent possible segfault in connection_close_unattached_ap().
11797 - Fix newlines on torrc in win32.
11798 - Improve error msgs when tor-resolve fails.
11800 o Improvements on 0.0.9.x:
11801 - New experimental script tor/contrib/ExerciseServer.py (needs more
11802 work) that uses the controller interface to build circuits and
11803 fetch pages over them. This will help us bootstrap servers that
11804 have lots of capacity but haven't noticed it yet.
11805 - New experimental script tor/contrib/PathDemo.py (needs more work)
11806 that uses the controller interface to let you choose whole paths
11808 "<hostname>.<path,separated by dots>.<length of path>.path"
11809 - When we've connected to an OR and handshaked but didn't like
11810 the result, we were closing the conn without sending destroy
11811 cells back for pending circuits. Now send those destroys.
11814 Changes in version 0.0.9.7 - 2005-04-01
11815 o Bugfixes on 0.0.9.x:
11816 - Fix another race crash bug (thanks to Glenn Fink for reporting).
11817 - Compare identity to identity, not to nickname, when extending to
11818 a router not already in the directory. This was preventing us from
11819 extending to unknown routers. Oops.
11820 - Make sure to create OS X Tor user in <500 range, so we aren't
11821 creating actual system users.
11822 - Note where connection-that-hasn't-sent-end was marked, and fix
11823 a few really loud instances of this harmless bug (it's fixed more
11827 Changes in version 0.1.0.1-rc - 2005-03-28
11829 - Add reachability testing. Your Tor server will automatically try
11830 to see if its ORPort and DirPort are reachable from the outside,
11831 and it won't upload its descriptor until it decides they are.
11832 - Handle unavailable hidden services better. Handle slow or busy
11833 hidden services better.
11834 - Add support for CONNECTing through https proxies, with "HttpsProxy"
11836 - New exit policy: accept most low-numbered ports, rather than
11837 rejecting most low-numbered ports.
11838 - More Tor controller support (still experimental). See
11839 http://tor.eff.org/doc/control-spec.txt for all the new features,
11840 including signals to emulate unix signals from any platform;
11841 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
11842 closestream; closecircuit; etc.
11843 - Make nt services work and start on startup on win32 (based on
11844 patch by Matt Edman).
11845 - Add a new AddressMap config directive to rewrite incoming socks
11846 addresses. This lets you, for example, declare an implicit
11847 required exit node for certain sites.
11848 - Add a new TrackHostExits config directive to trigger addressmaps
11849 for certain incoming socks addresses -- for sites that break when
11850 your exit keeps changing (based on patch by Mike Perry).
11851 - Redo the client-side dns cache so it's just an addressmap too.
11852 - Notice when our IP changes, and reset stats/uptime/reachability.
11853 - When an application is using socks5, give him the whole variety of
11854 potential socks5 responses (connect refused, host unreachable, etc),
11855 rather than just "success" or "failure".
11856 - A more sane version numbering system. See
11857 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
11858 - New contributed script "exitlist": a simple python script to
11859 parse directories and find Tor nodes that exit to listed
11861 - New contributed script "privoxy-tor-toggle" to toggle whether
11862 Privoxy uses Tor. Seems to be configured for Debian by default.
11863 - Report HTTP reasons to client when getting a response from directory
11864 servers -- so you can actually know what went wrong.
11865 - New config option MaxAdvertisedBandwidth which lets you advertise
11866 a low bandwidthrate (to not attract as many circuits) while still
11867 allowing a higher bandwidthrate in reality.
11869 o Robustness/stability fixes:
11870 - Make Tor use Niels Provos's libevent instead of its current
11871 poll-but-sometimes-select mess. This will let us use faster async
11872 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
11874 - pthread support now too. This was forced because when we forked,
11875 we ended up wasting a lot of duplicate ram over time. Also switch
11876 to foo_r versions of some library calls to allow reentry and
11878 - Better handling for heterogeneous / unreliable nodes:
11879 - Annotate circuits w/ whether they aim to contain high uptime nodes
11880 and/or high capacity nodes. When building circuits, choose
11882 - This means that every single node in an intro rend circuit,
11883 not just the last one, will have a minimum uptime.
11884 - New config option LongLivedPorts to indicate application streams
11885 that will want high uptime circuits.
11886 - Servers reset uptime when a dir fetch entirely fails. This
11887 hopefully reflects stability of the server's network connectivity.
11888 - If somebody starts his tor server in Jan 2004 and then fixes his
11889 clock, don't make his published uptime be a year.
11890 - Reset published uptime when you wake up from hibernation.
11891 - Introduce a notion of 'internal' circs, which are chosen without
11892 regard to the exit policy of the last hop. Intro and rendezvous
11893 circs must be internal circs, to avoid leaking information. Resolve
11894 and connect streams can use internal circs if they want.
11895 - New circuit pooling algorithm: make sure to have enough circs around
11896 to satisfy any predicted ports, and also make sure to have 2 internal
11897 circs around if we've required internal circs lately (and with high
11898 uptime if we've seen that lately too).
11899 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
11900 which describes how often we retry making new circuits if current
11901 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
11902 how long we're willing to make use of an already-dirty circuit.
11903 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
11904 circ as necessary, if there are any completed ones lying around
11905 when we try to launch one.
11906 - Make hidden services try to establish a rendezvous for 30 seconds,
11907 rather than for n (where n=3) attempts to build a circuit.
11908 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
11909 "ShutdownWaitLength".
11910 - Try to be more zealous about calling connection_edge_end when
11911 things go bad with edge conns in connection.c.
11912 - Revise tor-spec to add more/better stream end reasons.
11913 - Revise all calls to connection_edge_end to avoid sending "misc",
11914 and to take errno into account where possible.
11917 - Fix a race condition that can trigger an assert, when we have a
11918 pending create cell and an OR connection fails right then.
11919 - Fix several double-mark-for-close bugs, e.g. where we were finding
11920 a conn for a cell even if that conn is already marked for close.
11921 - Make sequence of log messages when starting on win32 with no config
11922 file more reasonable.
11923 - When choosing an exit node for a new non-internal circ, don't take
11924 into account whether it'll be useful for any pending x.onion
11925 addresses -- it won't.
11926 - Turn addr_policy_compare from a tristate to a quadstate; this should
11927 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
11928 for google.com" problem.
11929 - Make "platform" string in descriptor more accurate for Win32 servers,
11930 so it's not just "unknown platform".
11931 - Fix an edge case in parsing config options (thanks weasel).
11932 If they say "--" on the commandline, it's not an option.
11933 - Reject odd-looking addresses at the client (e.g. addresses that
11934 contain a colon), rather than having the server drop them because
11936 - tor-resolve requests were ignoring .exit if there was a working circuit
11937 they could use instead.
11938 - REUSEADDR on normal platforms means you can rebind to the port
11939 right after somebody else has let it go. But REUSEADDR on win32
11940 means to let you bind to the port _even when somebody else
11941 already has it bound_! So, don't do that on Win32.
11942 - Change version parsing logic: a version is "obsolete" if it is not
11943 recommended and (1) there is a newer recommended version in the
11944 same series, or (2) there are no recommended versions in the same
11945 series, but there are some recommended versions in a newer series.
11946 A version is "new" if it is newer than any recommended version in
11948 - Stop most cases of hanging up on a socks connection without sending
11952 - Require BandwidthRate to be at least 20kB/s for servers.
11953 - When a dirserver causes you to give a warn, mention which dirserver
11955 - New config option DirAllowPrivateAddresses for authdirservers.
11956 Now by default they refuse router descriptors that have non-IP or
11957 private-IP addresses.
11958 - Stop publishing socksport in the directory, since it's not
11959 actually meant to be public. For compatibility, publish a 0 there
11961 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
11962 smart" value, that is low for servers and high for clients.
11963 - If our clock jumps forward by 100 seconds or more, assume something
11964 has gone wrong with our network and abandon all not-yet-used circs.
11965 - Warn when exit policy implicitly allows local addresses.
11966 - If we get an incredibly skewed timestamp from a dirserver mirror
11967 that isn't a verified OR, don't warn -- it's probably him that's
11969 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
11970 cookies to disk and doesn't log each web request to disk. (Thanks
11971 to Brett Carrington for pointing this out.)
11972 - When a client asks us for a dir mirror and we don't have one,
11973 launch an attempt to get a fresh one.
11974 - If we're hibernating and we get a SIGINT, exit immediately.
11975 - Add --with-dmalloc ./configure option, to track memory leaks.
11976 - And try to free all memory on closing, so we can detect what
11978 - Cache local dns resolves correctly even when they're .exit
11980 - Give a better warning when some other server advertises an
11981 ORPort that is actually an apache running ssl.
11982 - Add "opt hibernating 1" to server descriptor to make it clearer
11983 whether the server is hibernating.
11986 Changes in version 0.0.9.6 - 2005-03-24
11987 o Bugfixes on 0.0.9.x (crashes and asserts):
11988 - Add new end stream reasons to maintainance branch. Fix bug where
11989 reason (8) could trigger an assert. Prevent bug from recurring.
11990 - Apparently win32 stat wants paths to not end with a slash.
11991 - Fix assert triggers in assert_cpath_layer_ok(), where we were
11992 blowing away the circuit that conn->cpath_layer points to, then
11993 checking to see if the circ is well-formed. Backport check to make
11994 sure we dont use the cpath on a closed connection.
11995 - Prevent circuit_resume_edge_reading_helper() from trying to package
11996 inbufs for marked-for-close streams.
11997 - Don't crash on hup if your options->address has become unresolvable.
11998 - Some systems (like OS X) sometimes accept() a connection and tell
11999 you the remote host is 0.0.0.0:0. If this happens, due to some
12000 other mis-features, we get confused; so refuse the conn for now.
12002 o Bugfixes on 0.0.9.x (other):
12003 - Fix harmless but scary "Unrecognized content encoding" warn message.
12004 - Add new stream error reason: TORPROTOCOL reason means "you are not
12005 speaking a version of Tor I understand; say bye-bye to your stream."
12006 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
12007 into the future, now that we are more tolerant of skew. This
12008 resolves a bug where a Tor server would refuse to cache a directory
12009 because all the directories it gets are too far in the future;
12010 yet the Tor server never logs any complaints about clock skew.
12011 - Mac packaging magic: make man pages useable, and do not overwrite
12012 existing torrc files.
12013 - Make OS X log happily to /var/log/tor/tor.log
12016 Changes in version 0.0.9.5 - 2005-02-22
12017 o Bugfixes on 0.0.9.x:
12018 - Fix an assert race at exit nodes when resolve requests fail.
12019 - Stop picking unverified dir mirrors--it only leads to misery.
12020 - Patch from Matt Edman to make NT services work better. Service
12021 support is still not compiled into the executable by default.
12022 - Patch from Dmitri Bely so the Tor service runs better under
12023 the win32 SYSTEM account.
12024 - Make tor-resolve actually work (?) on Win32.
12025 - Fix a sign bug when getrlimit claims to have 4+ billion
12026 file descriptors available.
12027 - Stop refusing to start when bandwidthburst == bandwidthrate.
12028 - When create cells have been on the onion queue more than five
12029 seconds, just send back a destroy and take them off the list.
12032 Changes in version 0.0.9.4 - 2005-02-03
12033 o Bugfixes on 0.0.9:
12034 - Fix an assert bug that took down most of our servers: when
12035 a server claims to have 1 GB of bandwidthburst, don't
12037 - Don't crash as badly if we have spawned the max allowed number
12038 of dnsworkers, or we're out of file descriptors.
12039 - Block more file-sharing ports in the default exit policy.
12040 - MaxConn is now automatically set to the hard limit of max
12041 file descriptors we're allowed (ulimit -n), minus a few for
12043 - Give a clearer message when servers need to raise their
12044 ulimit -n when they start running out of file descriptors.
12045 - SGI Compatibility patches from Jan Schaumann.
12046 - Tolerate a corrupt cached directory better.
12047 - When a dirserver hasn't approved your server, list which one.
12048 - Go into soft hibernation after 95% of the bandwidth is used,
12049 not 99%. This is especially important for daily hibernators who
12050 have a small accounting max. Hopefully it will result in fewer
12051 cut connections when the hard hibernation starts.
12052 - Load-balance better when using servers that claim more than
12053 800kB/s of capacity.
12054 - Make NT services work (experimental, only used if compiled in).
12057 Changes in version 0.0.9.3 - 2005-01-21
12058 o Bugfixes on 0.0.9:
12059 - Backport the cpu use fixes from main branch, so busy servers won't
12060 need as much processor time.
12061 - Work better when we go offline and then come back, or when we
12062 run Tor at boot before the network is up. We do this by
12063 optimistically trying to fetch a new directory whenever an
12064 application request comes in and we think we're offline -- the
12065 human is hopefully a good measure of when the network is back.
12066 - Backport some minimal hidserv bugfixes: keep rend circuits open as
12067 long as you keep using them; actually publish hidserv descriptors
12068 shortly after they change, rather than waiting 20-40 minutes.
12069 - Enable Mac startup script by default.
12070 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
12071 - When you update AllowUnverifiedNodes or FirewallPorts via the
12072 controller's setconf feature, we were always appending, never
12074 - When you update HiddenServiceDir via setconf, it was screwing up
12075 the order of reading the lines, making it fail.
12076 - Do not rewrite a cached directory back to the cache; otherwise we
12077 will think it is recent and not fetch a newer one on startup.
12078 - Workaround for webservers that lie about Content-Encoding: Tor
12079 now tries to autodetect compressed directories and compression
12080 itself. This lets us Proxypass dir fetches through apache.
12083 Changes in version 0.0.9.2 - 2005-01-04
12084 o Bugfixes on 0.0.9 (crashes and asserts):
12085 - Fix an assert on startup when the disk is full and you're logging
12087 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
12088 style address, then we'd crash.
12089 - Fix an assert trigger when the running-routers string we get from
12090 a dirserver is broken.
12091 - Make worker threads start and run on win32. Now win32 servers
12093 - Bandaid (not actually fix, but now it doesn't crash) an assert
12094 where the dns worker dies mysteriously and the main Tor process
12095 doesn't remember anything about the address it was resolving.
12097 o Bugfixes on 0.0.9 (Win32):
12098 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
12099 name out of the warning/assert messages.
12100 - Fix a superficial "unhandled error on read" bug on win32.
12101 - The win32 installer no longer requires a click-through for our
12102 license, since our Free Software license grants rights but does not
12104 - Win32: When connecting to a dirserver fails, try another one
12105 immediately. (This was already working for non-win32 Tors.)
12106 - Stop trying to parse $HOME on win32 when hunting for default
12108 - Make tor-resolve.c work on win32 by calling network_init().
12110 o Bugfixes on 0.0.9 (other):
12111 - Make 0.0.9.x build on Solaris again.
12112 - Due to a fencepost error, we were blowing away the \n when reporting
12113 confvalue items in the controller. So asking for multiple config
12114 values at once couldn't work.
12115 - When listing circuits that are pending on an opening OR connection,
12116 if we're an OR we were listing circuits that *end* at us as
12117 being pending on every listener, dns/cpu worker, etc. Stop that.
12118 - Dirservers were failing to create 'running-routers' or 'directory'
12119 strings if we had more than some threshold of routers. Fix them so
12120 they can handle any number of routers.
12121 - Fix a superficial "Duplicate mark for close" bug.
12122 - Stop checking for clock skew for OR connections, even for servers.
12123 - Fix a fencepost error that was chopping off the last letter of any
12124 nickname that is the maximum allowed nickname length.
12125 - Update URLs in log messages so they point to the new website.
12126 - Fix a potential problem in mangling server private keys while
12127 writing to disk (not triggered yet, as far as we know).
12128 - Include the licenses for other free software we include in Tor,
12129 now that we're shipping binary distributions more regularly.
12132 Changes in version 0.0.9.1 - 2004-12-15
12133 o Bugfixes on 0.0.9:
12134 - Make hibernation actually work.
12135 - Make HashedControlPassword config option work.
12136 - When we're reporting event circuit status to a controller,
12137 don't use the stream status code.
12140 Changes in version 0.0.9 - 2004-12-12
12142 - Clean up manpage and torrc.sample file.
12143 - Clean up severities and text of log warnings.
12145 - Make servers trigger an assert when they enter hibernation.
12148 Changes in version 0.0.9rc7 - 2004-12-08
12149 o Bugfixes on 0.0.9rc:
12150 - Fix a stack-trashing crash when an exit node begins hibernating.
12151 - Avoid looking at unallocated memory while considering which
12152 ports we need to build circuits to cover.
12153 - Stop a sigpipe: when an 'end' cell races with eof from the app,
12154 we shouldn't hold-open-until-flush if the eof arrived first.
12155 - Fix a bug with init_cookie_authentication() in the controller.
12156 - When recommending new-format log lines, if the upper bound is
12157 LOG_ERR, leave it implicit.
12159 o Bugfixes on 0.0.8.1:
12160 - Fix a whole slew of memory leaks.
12161 - Fix isspace() and friends so they still make Solaris happy
12162 but also so they don't trigger asserts on win32.
12163 - Fix parse_iso_time on platforms without strptime (eg win32).
12164 - win32: tolerate extra "readable" events better.
12165 - win32: when being multithreaded, leave parent fdarray open.
12166 - Make unit tests work on win32.
12169 Changes in version 0.0.9rc6 - 2004-12-06
12170 o Bugfixes on 0.0.9pre:
12171 - Clean up some more integer underflow opportunities (not exploitable
12173 - While hibernating, hup should not regrow our listeners.
12174 - Send an end to the streams we close when we hibernate, rather
12175 than just chopping them off.
12176 - React to eof immediately on non-open edge connections.
12178 o Bugfixes on 0.0.8.1:
12179 - Calculate timeout for waiting for a connected cell from the time
12180 we sent the begin cell, not from the time the stream started. If
12181 it took a long time to establish the circuit, we would time out
12182 right after sending the begin cell.
12183 - Fix router_compare_addr_to_addr_policy: it was not treating a port
12184 of * as always matching, so we were picking reject *:* nodes as
12185 exit nodes too. Oops.
12188 - New circuit building strategy: keep a list of ports that we've
12189 used in the past 6 hours, and always try to have 2 circuits open
12190 or on the way that will handle each such port. Seed us with port
12191 80 so web users won't complain that Tor is "slow to start up".
12192 - Make kill -USR1 dump more useful stats about circuits.
12193 - When warning about retrying or giving up, print the address, so
12194 the user knows which one it's talking about.
12195 - If you haven't used a clean circuit in an hour, throw it away,
12196 just to be on the safe side. (This means after 6 hours a totally
12197 unused Tor client will have no circuits open.)
12200 Changes in version 0.0.9rc5 - 2004-12-01
12201 o Bugfixes on 0.0.8.1:
12202 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
12203 - Let resolve conns retry/expire also, rather than sticking around
12205 - If we are using select, make sure we stay within FD_SETSIZE.
12207 o Bugfixes on 0.0.9pre:
12208 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
12209 but doesn't seem to be currently; thanks to Ilja van Sprundel for
12211 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
12212 instead. Impose minima and maxima for all *Period options; impose
12213 even tighter maxima for fetching if we are a caching dirserver.
12214 Clip rather than rejecting.
12215 - Fetch cached running-routers from servers that serve it (that is,
12216 authdirservers and servers running 0.0.9rc5-cvs or later.)
12219 - Accept *:706 (silc) in default exit policy.
12220 - Implement new versioning format for post 0.1.
12221 - Support "foo.nickname.exit" addresses, to let Alice request the
12222 address "foo" as viewed by exit node "nickname". Based on a patch
12224 - Make tor --version --version dump the cvs Id of every file.
12227 Changes in version 0.0.9rc4 - 2004-11-28
12228 o Bugfixes on 0.0.8.1:
12229 - Make windows sockets actually non-blocking (oops), and handle
12230 win32 socket errors better.
12232 o Bugfixes on 0.0.9rc1:
12233 - Actually catch the -USR2 signal.
12236 Changes in version 0.0.9rc3 - 2004-11-25
12237 o Bugfixes on 0.0.8.1:
12238 - Flush the log file descriptor after we print "Tor opening log file",
12239 so we don't see those messages days later.
12241 o Bugfixes on 0.0.9rc1:
12242 - Make tor-resolve work again.
12243 - Avoid infinite loop in tor-resolve if tor hangs up on it.
12244 - Fix an assert trigger for clients/servers handling resolves.
12247 Changes in version 0.0.9rc2 - 2004-11-24
12248 o Bugfixes on 0.0.9rc1:
12249 - I broke socks5 support while fixing the eof bug.
12250 - Allow unitless bandwidths and intervals; they default to bytes
12252 - New servers don't start out hibernating; they are active until
12253 they run out of bytes, so they have a better estimate of how
12254 long it takes, and so their operators can know they're working.
12257 Changes in version 0.0.9rc1 - 2004-11-23
12258 o Bugfixes on 0.0.8.1:
12259 - Finally fix a bug that's been plaguing us for a year:
12260 With high load, circuit package window was reaching 0. Whenever
12261 we got a circuit-level sendme, we were reading a lot on each
12262 socket, but only writing out a bit. So we would eventually reach
12263 eof. This would be noticed and acted on even when there were still
12264 bytes sitting in the inbuf.
12265 - When poll() is interrupted, we shouldn't believe the revents values.
12267 o Bugfixes on 0.0.9pre6:
12268 - Fix hibernate bug that caused pre6 to be broken.
12269 - Don't keep rephist info for routers that haven't had activity for
12270 24 hours. (This matters now that clients have keys, since we track
12272 - Never call close_temp_logs while validating log options.
12273 - Fix backslash-escaping on tor.sh.in and torctl.in.
12276 - Implement weekly/monthly/daily accounting: now you specify your
12277 hibernation properties by
12278 AccountingMax N bytes|KB|MB|GB|TB
12279 AccountingStart day|week|month [day] HH:MM
12280 Defaults to "month 1 0:00".
12281 - Let bandwidth and interval config options be specified as 5 bytes,
12282 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
12283 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
12284 get back to normal.)
12285 - If your requested entry or exit node has advertised bandwidth 0,
12287 - Be more greedy about filling up relay cells -- we try reading again
12288 once we've processed the stuff we read, in case enough has arrived
12289 to fill the last cell completely.
12290 - Apply NT service patch from Osamu Fujino. Still needs more work.
12293 Changes in version 0.0.9pre6 - 2004-11-15
12294 o Bugfixes on 0.0.8.1:
12295 - Fix assert failure on malformed socks4a requests.
12296 - Use identity comparison, not nickname comparison, to choose which
12297 half of circuit-ID-space each side gets to use. This is needed
12298 because sometimes we think of a router as a nickname, and sometimes
12299 as a hex ID, and we can't predict what the other side will do.
12300 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
12301 write() call will fail and we handle it there.
12302 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
12303 and smartlist_len, which are two major profiling offenders.
12305 o Bugfixes on 0.0.9pre5:
12306 - Fix a bug in read_all that was corrupting config files on windows.
12307 - When we're raising the max number of open file descriptors to
12308 'unlimited', don't log that we just raised it to '-1'.
12309 - Include event code with events, as required by control-spec.txt.
12310 - Don't give a fingerprint when clients do --list-fingerprint:
12311 it's misleading, because it will never be the same again.
12312 - Stop using strlcpy in tor_strndup, since it was slowing us
12314 - Remove warn on startup about missing cached-directory file.
12315 - Make kill -USR1 work again.
12316 - Hibernate if we start tor during the "wait for wakeup-time" phase
12317 of an accounting interval. Log our hibernation plans better.
12318 - Authoritative dirservers now also cache their directory, so they
12319 have it on start-up.
12322 - Fetch running-routers; cache running-routers; compress
12323 running-routers; serve compressed running-routers.z
12324 - Add NSI installer script contributed by J Doe.
12325 - Commit VC6 and VC7 workspace/project files.
12326 - Commit a tor.spec for making RPM files, with help from jbash.
12327 - Add contrib/torctl.in contributed by Glenn Fink.
12328 - Implement the control-spec's SAVECONF command, to write your
12329 configuration to torrc.
12330 - Get cookie authentication for the controller closer to working.
12331 - Include control-spec.txt in the tarball.
12332 - When set_conf changes our server descriptor, upload a new copy.
12333 But don't upload it too often if there are frequent changes.
12334 - Document authentication config in man page, and document signals
12336 - Clean up confusing parts of man page and torrc.sample.
12337 - Make expand_filename handle ~ and ~username.
12338 - Use autoconf to enable largefile support where necessary. Use
12339 ftello where available, since ftell can fail at 2GB.
12340 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
12341 log more informatively.
12342 - Give a slightly more useful output for "tor -h".
12343 - Refuse application socks connections to port 0.
12344 - Check clock skew for verified servers, but allow unverified
12345 servers and clients to have any clock skew.
12346 - Break DirFetchPostPeriod into:
12347 - DirFetchPeriod for fetching full directory,
12348 - StatusFetchPeriod for fetching running-routers,
12349 - DirPostPeriod for posting server descriptor,
12350 - RendPostPeriod for posting hidden service descriptors.
12351 - Make sure the hidden service descriptors are at a random offset
12352 from each other, to hinder linkability.
12355 Changes in version 0.0.9pre5 - 2004-11-09
12356 o Bugfixes on 0.0.9pre4:
12357 - Fix a seg fault in unit tests (doesn't affect main program).
12358 - Fix an assert bug where a hidden service provider would fail if
12359 the first hop of his rendezvous circuit was down.
12360 - Hidden service operators now correctly handle version 1 style
12361 INTRODUCE1 cells (nobody generates them still, so not a critical
12363 - If do_hup fails, actually notice.
12364 - Handle more errnos from accept() without closing the listener.
12365 Some OpenBSD machines were closing their listeners because
12366 they ran out of file descriptors.
12367 - Send resolve cells to exit routers that are running a new
12368 enough version of the resolve code to work right.
12369 - Better handling of winsock includes on non-MSV win32 compilers.
12370 - Some people had wrapped their tor client/server in a script
12371 that would restart it whenever it died. This did not play well
12372 with our "shut down if your version is obsolete" code. Now people
12373 don't fetch a new directory if their local cached version is
12375 - Make our autogen.sh work on ksh as well as bash.
12378 - Hibernation: New config option "AccountingMaxKB" lets you
12379 set how many KBytes per month you want to allow your server to
12380 consume. Rather than spreading those bytes out evenly over the
12381 month, we instead hibernate for some of the month and pop up
12382 at a deterministic time, work until the bytes are consumed, then
12383 hibernate again. Config option "MonthlyAccountingStart" lets you
12384 specify which day of the month your billing cycle starts on.
12385 - Control interface: a separate program can now talk to your
12386 client/server over a socket, and get/set config options, receive
12387 notifications of circuits and streams starting/finishing/dying,
12388 bandwidth used, etc. The next step is to get some GUIs working.
12389 Let us know if you want to help out. See doc/control-spec.txt .
12390 - Ship a contrib/tor-control.py as an example script to interact
12391 with the control port.
12392 - "tor --hash-password zzyxz" will output a salted password for
12393 use in authenticating to the control interface.
12394 - New log format in config:
12395 "Log minsev[-maxsev] stdout|stderr|syslog" or
12396 "Log minsev[-maxsev] file /var/foo"
12399 - DirPolicy config option, to let people reject incoming addresses
12400 from their dirserver.
12401 - "tor --list-fingerprint" will list your identity key fingerprint
12403 - Add "pass" target for RedirectExit, to make it easier to break
12404 out of a sequence of RedirectExit rules.
12405 - Clients now generate a TLS cert too, in preparation for having
12406 them act more like real nodes.
12407 - Ship src/win32/ in the tarball, so people can use it to build.
12408 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
12410 - New "router-status" line in directory, to better bind each verified
12411 nickname to its identity key.
12412 - Deprecate unofficial config option abbreviations, and abbreviations
12413 not on the command line.
12414 - Add a pure-C tor-resolve implementation.
12415 - Use getrlimit and friends to ensure we can reach MaxConn (currently
12416 1024) file descriptors.
12418 o Code security improvements, inspired by Ilja:
12419 - Replace sprintf with snprintf. (I think they were all safe, but
12421 - Replace strcpy/strncpy with strlcpy in more places.
12422 - Avoid strcat; use snprintf or strlcat instead.
12423 - snprintf wrapper with consistent (though not C99) overflow behavior.
12426 Changes in version 0.0.9pre4 - 2004-10-17
12427 o Bugfixes on 0.0.9pre3:
12428 - If the server doesn't specify an exit policy, use the real default
12429 exit policy, not reject *:*.
12430 - Ignore fascistfirewall when uploading/downloading hidden service
12431 descriptors, since we go through Tor for those; and when using
12432 an HttpProxy, since we assume it can reach them all.
12433 - When looking for an authoritative dirserver, use only the ones
12434 configured at boot. Don't bother looking in the directory.
12435 - The rest of the fix for get_default_conf_file() on older win32.
12436 - Make 'Routerfile' config option obsolete.
12439 - New 'MyFamily nick1,...' config option for a server to
12440 specify other servers that shouldn't be used in the same circuit
12441 with it. Only believed if nick1 also specifies us.
12442 - New 'NodeFamily nick1,nick2,...' config option for a client to
12443 specify nodes that it doesn't want to use in the same circuit.
12444 - New 'Redirectexit pattern address:port' config option for a
12445 server to redirect exit connections, e.g. to a local squid.
12448 Changes in version 0.0.9pre3 - 2004-10-13
12449 o Bugfixes on 0.0.8.1:
12450 - Better torrc example lines for dirbindaddress and orbindaddress.
12451 - Improved bounds checking on parsed ints (e.g. config options and
12452 the ones we find in directories.)
12453 - Better handling of size_t vs int, so we're more robust on 64
12455 - Fix the rest of the bug where a newly started OR would appear
12456 as unverified even after we've added his fingerprint and hupped
12458 - Fix a bug from 0.0.7: when read() failed on a stream, we would
12459 close it without sending back an end. So 'connection refused'
12460 would simply be ignored and the user would get no response.
12462 o Bugfixes on 0.0.9pre2:
12463 - Serving the cached-on-disk directory to people is bad. We now
12464 provide no directory until we've fetched a fresh one.
12465 - Workaround for bug on windows where cached-directories get crlf
12467 - Make get_default_conf_file() work on older windows too.
12468 - If we write a *:* exit policy line in the descriptor, don't write
12469 any more exit policy lines.
12472 - Use only 0.0.9pre1 and later servers for resolve cells.
12473 - Make the dirservers file obsolete.
12474 - Include a dir-signing-key token in directories to tell the
12475 parsing entity which key is being used to sign.
12476 - Remove the built-in bulky default dirservers string.
12477 - New config option "Dirserver %s:%d [fingerprint]", which can be
12478 repeated as many times as needed. If no dirservers specified,
12479 default to moria1,moria2,tor26.
12480 - Make moria2 advertise a dirport of 80, so people behind firewalls
12481 will be able to get a directory.
12482 - Http proxy support
12483 - Dirservers translate requests for http://%s:%d/x to /x
12484 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
12485 be routed through this host.
12486 - Clients ask for /tor/x rather than /x for new enough dirservers.
12487 This way we can one day coexist peacefully with apache.
12488 - Clients specify a "Host: %s%d" http header, to be compatible
12489 with more proxies, and so running squid on an exit node can work.
12492 Changes in version 0.0.8.1 - 2004-10-13
12494 - Fix a seg fault that can be triggered remotely for Tor
12495 clients/servers with an open dirport.
12496 - Fix a rare assert trigger, where routerinfos for entries in
12497 our cpath would expire while we're building the path.
12498 - Fix a bug in OutboundBindAddress so it (hopefully) works.
12499 - Fix a rare seg fault for people running hidden services on
12500 intermittent connections.
12501 - Fix a bug in parsing opt keywords with objects.
12502 - Fix a stale pointer assert bug when a stream detaches and
12504 - Fix a string format vulnerability (probably not exploitable)
12505 in reporting stats locally.
12506 - Fix an assert trigger: sometimes launching circuits can fail
12507 immediately, e.g. because too many circuits have failed recently.
12508 - Fix a compile warning on 64 bit platforms.
12511 Changes in version 0.0.9pre2 - 2004-10-03
12513 - Make fetching a cached directory work for 64-bit platforms too.
12514 - Make zlib.h a required header, not an optional header.
12517 Changes in version 0.0.9pre1 - 2004-10-01
12519 - Stop using separate defaults for no-config-file and
12520 empty-config-file. Now you have to explicitly turn off SocksPort,
12521 if you don't want it open.
12522 - Fix a bug in OutboundBindAddress so it (hopefully) works.
12523 - Improve man page to mention more of the 0.0.8 features.
12524 - Fix a rare seg fault for people running hidden services on
12525 intermittent connections.
12526 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
12528 - Fix more dns related bugs: send back resolve_failed and end cells
12529 more reliably when the resolve fails, rather than closing the
12530 circuit and then trying to send the cell. Also attach dummy resolve
12531 connections to a circuit *before* calling dns_resolve(), to fix
12532 a bug where cached answers would never be sent in RESOLVED cells.
12533 - When we run out of disk space, or other log writing error, don't
12534 crash. Just stop logging to that log and continue.
12535 - We were starting to daemonize before we opened our logs, so if
12536 there were any problems opening logs, we would complain to stderr,
12537 which wouldn't work, and then mysteriously exit.
12538 - Fix a rare bug where sometimes a verified OR would connect to us
12539 before he'd uploaded his descriptor, which would cause us to
12540 assign conn->nickname as though he's unverified. Now we look through
12541 the fingerprint list to see if he's there.
12542 - Fix a rare assert trigger, where routerinfos for entries in
12543 our cpath would expire while we're building the path.
12546 - Clients can ask dirservers for /dir.z to get a compressed version
12547 of the directory. Only works for servers running 0.0.9, of course.
12548 - Make clients cache directories and use them to seed their router
12549 lists at startup. This means clients have a datadir again.
12550 - Configuration infrastructure support for warning on obsolete
12552 - Respond to content-encoding headers by trying to uncompress as
12554 - Reply with a deflated directory when a client asks for "dir.z".
12555 We could use allow-encodings instead, but allow-encodings isn't
12556 specified in HTTP 1.0.
12557 - Raise the max dns workers from 50 to 100.
12558 - Discourage people from setting their dirfetchpostperiod more often
12559 than once per minute.
12560 - Protect dirservers from overzealous descriptor uploading -- wait
12561 10 seconds after directory gets dirty, before regenerating.
12564 Changes in version 0.0.8 - 2004-08-25
12565 o Port it to SunOS 5.9 / Athena
12568 Changes in version 0.0.8rc2 - 2004-08-20
12569 o Make it compile on cygwin again.
12570 o When picking unverified routers, skip those with low uptime and/or
12571 low bandwidth, depending on what properties you care about.
12574 Changes in version 0.0.8rc1 - 2004-08-18
12575 o Changes from 0.0.7.3:
12577 - Fix assert triggers: if the other side returns an address 0.0.0.0,
12578 don't put it into the client dns cache.
12579 - If a begin failed due to exit policy, but we believe the IP address
12580 should have been allowed, switch that router to exitpolicy reject *:*
12581 until we get our next directory.
12583 - Clients choose nodes proportional to advertised bandwidth.
12584 - Avoid using nodes with low uptime as introduction points.
12585 - Handle servers with dynamic IP addresses: don't replace
12586 options->Address with the resolved one at startup, and
12587 detect our address right before we make a routerinfo each time.
12588 - 'FascistFirewall' option to pick dirservers and ORs on specific
12589 ports; plus 'FirewallPorts' config option to tell FascistFirewall
12590 which ports are open. (Defaults to 80,443)
12591 - Be more aggressive about trying to make circuits when the network
12592 has changed (e.g. when you unsuspend your laptop).
12593 - Check for time skew on http headers; report date in response to
12595 - If the entrynode config line has only one node, don't pick it as
12597 - Add strict{entry|exit}nodes config options. If set to 1, then
12598 we refuse to build circuits that don't include the specified entry
12600 - OutboundBindAddress config option, to bind to a specific
12601 IP address for outgoing connect()s.
12602 - End truncated log entries (e.g. directories) with "[truncated]".
12604 o Patches to 0.0.8preX:
12606 - Patches to compile and run on win32 again (maybe)?
12607 - Fix crash when looking for ~/.torrc with no $HOME set.
12608 - Fix a race bug in the unit tests.
12609 - Handle verified/unverified name collisions better when new
12610 routerinfo's arrive in a directory.
12611 - Sometimes routers were getting entered into the stats before
12612 we'd assigned their identity_digest. Oops.
12613 - Only pick and establish intro points after we've gotten a
12616 - AllowUnverifiedNodes config option to let circuits choose no-name
12617 routers in entry,middle,exit,introduction,rendezvous positions.
12618 Allow middle and rendezvous positions by default.
12619 - Add a man page for tor-resolve.
12622 Changes in version 0.0.7.3 - 2004-08-12
12623 o Stop dnsworkers from triggering an assert failure when you
12624 ask them to resolve the host "".
12627 Changes in version 0.0.8pre3 - 2004-08-09
12628 o Changes from 0.0.7.2:
12629 - Allow multiple ORs with same nickname in routerlist -- now when
12630 people give us one identity key for a nickname, then later
12631 another, we don't constantly complain until the first expires.
12632 - Remember used bandwidth (both in and out), and publish 15-minute
12633 snapshots for the past day into our descriptor.
12634 - You can now fetch $DIRURL/running-routers to get just the
12635 running-routers line, not the whole descriptor list. (But
12636 clients don't use this yet.)
12637 - When people mistakenly use Tor as an http proxy, point them
12638 at the tor-doc.html rather than the INSTALL.
12639 - Remove our mostly unused -- and broken -- hex_encode()
12640 function. Use base16_encode() instead. (Thanks to Timo Lindfors
12641 for pointing out this bug.)
12642 - Rotate onion keys every 12 hours, not every 2 hours, so we have
12643 fewer problems with people using the wrong key.
12644 - Change the default exit policy to reject the default edonkey,
12645 kazaa, gnutella ports.
12646 - Add replace_file() to util.[ch] to handle win32's rename().
12648 o Changes from 0.0.8preX:
12649 - Fix two bugs in saving onion keys to disk when rotating, so
12650 hopefully we'll get fewer people using old onion keys.
12651 - Fix an assert error that was making SocksPolicy not work.
12652 - Be willing to expire routers that have an open dirport -- it's
12653 just the authoritative dirservers we want to not forget.
12654 - Reject tor-resolve requests for .onion addresses early, so we
12655 don't build a whole rendezvous circuit and then fail.
12656 - When you're warning a server that he's unverified, don't cry
12657 wolf unpredictably.
12658 - Fix a race condition: don't try to extend onto a connection
12659 that's still handshaking.
12660 - For servers in clique mode, require the conn to be open before
12661 you'll choose it for your path.
12662 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
12663 end relay cell, etc.
12664 - Measure bandwidth capacity over the last 24 hours, not just 12
12665 - Bugfix: authoritative dirservers were making and signing a new
12666 directory for each client, rather than reusing the cached one.
12669 Changes in version 0.0.8pre2 - 2004-08-04
12670 o Changes from 0.0.7.2:
12672 - Check directory signature _before_ you decide whether you're
12673 you're running an obsolete version and should exit.
12674 - Check directory signature _before_ you parse the running-routers
12675 list to decide who's running or verified.
12676 - Bugfixes and features:
12677 - Check return value of fclose while writing to disk, so we don't
12678 end up with broken files when servers run out of disk space.
12679 - Log a warning if the user uses an unsafe socks variant, so people
12680 are more likely to learn about privoxy or socat.
12681 - Dirservers now include RFC1123-style dates in the HTTP headers,
12682 which one day we will use to better detect clock skew.
12684 o Changes from 0.0.8pre1:
12685 - Make it compile without warnings again on win32.
12686 - Log a warning if you're running an unverified server, to let you
12687 know you might want to get it verified.
12688 - Only pick a default nickname if you plan to be a server.
12691 Changes in version 0.0.8pre1 - 2004-07-23
12693 - Made our unit tests compile again on OpenBSD 3.5, and tor
12694 itself compile again on OpenBSD on a sparc64.
12695 - We were neglecting milliseconds when logging on win32, so
12696 everything appeared to happen at the beginning of each second.
12698 o Protocol changes:
12699 - 'Extend' relay cell payloads now include the digest of the
12700 intended next hop's identity key. Now we can verify that we're
12701 extending to the right router, and also extend to routers we
12702 hadn't heard of before.
12705 - Tor nodes can now act as relays (with an advertised ORPort)
12706 without being manually verified by the dirserver operators.
12707 - Uploaded descriptors of unverified routers are now accepted
12708 by the dirservers, and included in the directory.
12709 - Verified routers are listed by nickname in the running-routers
12710 list; unverified routers are listed as "$<fingerprint>".
12711 - We now use hash-of-identity-key in most places rather than
12712 nickname or addr:port, for improved security/flexibility.
12713 - To avoid Sybil attacks, paths still use only verified servers.
12714 But now we have a chance to play around with hybrid approaches.
12715 - Nodes track bandwidth usage to estimate capacity (not used yet).
12716 - ClientOnly option for nodes that never want to become servers.
12717 - Directory caching.
12718 - "AuthoritativeDir 1" option for the official dirservers.
12719 - Now other nodes (clients and servers) will cache the latest
12720 directory they've pulled down.
12721 - They can enable their DirPort to serve it to others.
12722 - Clients will pull down a directory from any node with an open
12723 DirPort, and check the signature/timestamp correctly.
12724 - Authoritative dirservers now fetch directories from other
12725 authdirservers, to stay better synced.
12726 - Running-routers list tells who's down also, along with noting
12727 if they're verified (listed by nickname) or unverified (listed
12729 - Allow dirservers to serve running-router list separately.
12730 This isn't used yet.
12731 - ORs connect-on-demand to other ORs
12732 - If you get an extend cell to an OR you're not connected to,
12733 connect, handshake, and forward the create cell.
12734 - The authoritative dirservers stay connected to everybody,
12735 and everybody stays connected to 0.0.7 servers, but otherwise
12736 clients/servers expire unused connections after 5 minutes.
12737 - When servers get a sigint, they delay 30 seconds (refusing new
12738 connections) then exit. A second sigint causes immediate exit.
12739 - File and name management:
12740 - Look for .torrc if no CONFDIR "torrc" is found.
12741 - If no datadir is defined, then choose, make, and secure ~/.tor
12743 - If torrc not found, exitpolicy reject *:*.
12744 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
12745 - If no nickname is defined, derive default from hostname.
12746 - Rename secret key files, e.g. identity.key -> secret_id_key,
12747 to discourage people from mailing their identity key to tor-ops.
12748 - Refuse to build a circuit before the directory has arrived --
12749 it won't work anyway, since you won't know the right onion keys
12751 - Try other dirservers immediately if the one you try is down. This
12752 should tolerate down dirservers better now.
12753 - Parse tor version numbers so we can do an is-newer-than check
12754 rather than an is-in-the-list check.
12755 - New socks command 'resolve', to let us shim gethostbyname()
12757 - A 'tor_resolve' script to access the socks resolve functionality.
12758 - A new socks-extensions.txt doc file to describe our
12759 interpretation and extensions to the socks protocols.
12760 - Add a ContactInfo option, which gets published in descriptor.
12761 - Publish OR uptime in descriptor (and thus in directory) too.
12762 - Write tor version at the top of each log file
12763 - New docs in the tarball:
12765 - Document that you should proxy your SSL traffic too.
12768 Changes in version 0.0.7.2 - 2004-07-07
12769 o A better fix for the 0.0.0.0 problem, that will hopefully
12770 eliminate the remaining related assertion failures.
12773 Changes in version 0.0.7.1 - 2004-07-04
12774 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
12775 since internally we use 0.0.0.0 to signify "not yet resolved".
12778 Changes in version 0.0.7 - 2004-06-07
12779 o Updated the man page to reflect the new features.
12782 Changes in version 0.0.7rc2 - 2004-06-06
12783 o Changes from 0.0.7rc1:
12784 - Make it build on Win32 again.
12785 o Changes from 0.0.6.2:
12786 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
12790 Changes in version 0.0.7rc1 - 2004-06-02
12792 - On sighup, we were adding another log without removing the first
12793 one. So log messages would get duplicated n times for n sighups.
12794 - Several cases of using a connection after we'd freed it. The
12795 problem was that connections that are pending resolve are in both
12796 the pending_resolve tree, and also the circuit's resolving_streams
12797 list. When you want to remove one, you must remove it from both.
12798 - Fix a double-mark-for-close where an end cell arrived for a
12799 resolving stream, and then the resolve failed.
12800 - Check directory signatures based on name of signer, not on whom
12801 we got the directory from. This will let us cache directories more
12804 - Crank up some of our constants to handle more users.
12807 Changes in version 0.0.7pre1 - 2004-06-02
12808 o Fixes for crashes and other obnoxious bugs:
12809 - Fix an epipe bug: sometimes when directory connections failed
12810 to connect, we would give them a chance to flush before closing
12812 - When we detached from a circuit because of resolvefailed, we
12813 would immediately try the same circuit twice more, and then
12814 give up on the resolve thinking we'd tried three different
12816 - Limit the number of intro circuits we'll attempt to build for a
12817 hidden service per 15-minute period.
12818 - Check recommended-software string *early*, before actually parsing
12819 the directory. Thus we can detect an obsolete version and exit,
12820 even if the new directory format doesn't parse.
12821 o Fixes for security bugs:
12822 - Remember which nodes are dirservers when you startup, and if a
12823 random OR enables his dirport, don't automatically assume he's
12824 a trusted dirserver.
12826 - Directory connections were asking the wrong poll socket to
12827 start writing, and not asking themselves to start writing.
12828 - When we detached from a circuit because we sent a begin but
12829 didn't get a connected, we would use it again the first time;
12830 but after that we would correctly switch to a different one.
12831 - Stop warning when the first onion decrypt attempt fails; they
12832 will sometimes legitimately fail now that we rotate keys.
12833 - Override unaligned-access-ok check when $host_cpu is ia64 or
12834 arm. Apparently they allow it but the kernel whines.
12835 - Dirservers try to reconnect periodically too, in case connections
12837 - Fix some memory leaks in directory servers.
12838 - Allow backslash in Win32 filenames.
12839 - Made Tor build complain-free on FreeBSD, hopefully without
12840 breaking other BSD builds. We'll see.
12842 - Doxygen markup on all functions and global variables.
12843 - Make directory functions update routerlist, not replace it. So
12844 now directory disagreements are not so critical a problem.
12845 - Remove the upper limit on number of descriptors in a dirserver's
12846 directory (not that we were anywhere close).
12847 - Allow multiple logfiles at different severity ranges.
12848 - Allow *BindAddress to specify ":port" rather than setting *Port
12849 separately. Allow multiple instances of each BindAddress config
12850 option, so you can bind to multiple interfaces if you want.
12851 - Allow multiple exit policy lines, which are processed in order.
12852 Now we don't need that huge line with all the commas in it.
12853 - Enable accept/reject policies on SOCKS connections, so you can bind
12854 to 0.0.0.0 but still control who can use your OP.
12857 Changes in version 0.0.6.2 - 2004-05-16
12858 o Our integrity-checking digest was checking only the most recent cell,
12859 not the previous cells like we'd thought.
12860 Thanks to Stefan Mark for finding the flaw!
12863 Changes in version 0.0.6.1 - 2004-05-06
12864 o Fix two bugs in our AES counter-mode implementation (this affected
12865 onion-level stream encryption, but not TLS-level). It turns
12866 out we were doing something much more akin to a 16-character
12867 polyalphabetic cipher. Oops.
12868 Thanks to Stefan Mark for finding the flaw!
12869 o Retire moria3 as a directory server, and add tor26 as a directory
12873 Changes in version 0.0.6 - 2004-05-02
12874 [version bump only]
12877 Changes in version 0.0.6rc4 - 2004-05-01
12878 o Update the built-in dirservers list to use the new directory format
12879 o Fix a rare seg fault: if a node offering a hidden service attempts
12880 to build a circuit to Alice's rendezvous point and fails before it
12881 reaches the last hop, it retries with a different circuit, but
12883 o Handle windows socket errors correctly.
12886 Changes in version 0.0.6rc3 - 2004-04-28
12887 o Don't expire non-general excess circuits (if we had enough
12888 circuits open, we were expiring rendezvous circuits -- even
12889 when they had a stream attached. oops.)
12890 o Fetch randomness from /dev/urandom better (not via fopen/fread)
12891 o Better debugging for tls errors
12892 o Some versions of openssl have an SSL_pending function that erroneously
12893 returns bytes when there is a non-application record pending.
12894 o Set Content-Type on the directory and hidserv descriptor.
12895 o Remove IVs from cipher code, since AES-ctr has none.
12896 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
12897 o We were using an array of length zero in a few places.
12898 o win32's gethostbyname can't resolve an IP to an IP.
12899 o win32's close can't close a socket.
12902 Changes in version 0.0.6rc2 - 2004-04-26
12903 o Fix a bug where we were closing tls connections intermittently.
12904 It turns out openssl keeps its errors around -- so if an error
12905 happens, and you don't ask about it, and then another openssl
12906 operation happens and succeeds, and you ask if there was an error,
12907 it tells you about the first error. Fun fun.
12908 o Fix a bug that's been lurking since 27 may 03 (!)
12909 When passing back a destroy cell, we would use the wrong circ id.
12910 'Mostly harmless', but still worth fixing.
12911 o Since we don't support truncateds much, don't bother sending them;
12912 just close the circ.
12913 o check for <machine/limits.h> so we build on NetBSD again (I hope).
12914 o don't crash if a conn that sent a begin has suddenly lost its circuit
12915 (this was quite rare).
12918 Changes in version 0.0.6rc1 - 2004-04-25
12919 o We now rotate link (tls context) keys and onion keys.
12920 o CREATE cells now include oaep padding, so you can tell
12921 if you decrypted them correctly.
12922 o Add bandwidthburst to server descriptor.
12923 o Directories now say which dirserver signed them.
12924 o Use a tor_assert macro that logs failed assertions too.
12927 Changes in version 0.0.6pre5 - 2004-04-18
12928 o changes from 0.0.6pre4:
12929 - make tor build on broken freebsd 5.2 installs
12930 - fix a failed assert when you try an intro point, get a nack, and try
12931 a second one and it works.
12932 - when alice uses a port that the hidden service doesn't accept,
12933 it now sends back an end cell (denied by exit policy). otherwise
12934 alice would just have to wait to time out.
12935 - fix another rare bug: when we had tried all the intro
12936 points for a hidden service, we fetched the descriptor
12937 again, but we left our introcirc thinking it had already
12938 sent an intro, so it kept waiting for a response...
12939 - bugfix: when you sleep your hidden-service laptop, as soon
12940 as it wakes up it tries to upload a service descriptor, but
12941 socketpair fails for some reason (localhost not up yet?).
12942 now we simply give up on that upload, and we'll try again later.
12943 i'd still like to find the bug though.
12944 - if an intro circ waiting for an ack dies before getting one, then
12946 - we were reusing stale service descriptors and refetching usable
12950 Changes in version 0.0.6pre4 - 2004-04-14
12951 o changes from 0.0.6pre3:
12952 - when bob fails to connect to the rendezvous point, and his
12953 circ didn't fail because of the rendezvous point itself, then
12954 he retries a couple of times
12955 - we expire introduction and rendezvous circs more thoroughly
12956 (sometimes they were hanging around forever)
12957 - we expire unattached rendezvous streams that have been around
12958 too long (they were sticking around forever).
12959 - fix a measly fencepost error that was crashing everybody with
12963 Changes in version 0.0.6pre3 - 2004-04-14
12964 o changes from 0.0.6pre2:
12965 - make hup work again
12966 - fix some memory leaks for dirservers
12967 - allow more skew in rendezvous descriptor timestamps, to help
12968 handle people like blanu who don't know what time it is
12969 - normal circs are 3 hops, but some rend/intro circs are 4, if
12970 the initiator doesn't get to choose the last hop
12971 - send acks for introductions, so alice can know whether to try
12973 - bob publishes intro points more correctly
12974 o changes from 0.0.5:
12975 - fix an assert trigger that's been plaguing us since the days
12976 of 0.0.2prexx (thanks weasel!)
12977 - retry stream correctly when we fail to connect because of
12978 exit-policy-reject (should try another) or can't-resolve-address
12979 (also should try another, because dns on random internet servers
12981 - when we hup a dirserver and we've *removed* a server from the
12982 approved-routers list, now we remove that server from the
12983 in-memory directories too
12986 Changes in version 0.0.6pre2 - 2004-04-08
12987 o We fixed our base32 implementation. Now it works on all architectures.
12990 Changes in version 0.0.6pre1 - 2004-04-08
12992 - Hidden services and rendezvous points are implemented. Go to
12993 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
12994 hidden services. (This only works via a socks4a proxy such as
12995 Privoxy, and currently it's quite slow.)
12998 Changes in version 0.0.5 - 2004-03-30
12999 [version bump only]
13002 Changes in version 0.0.5rc3 - 2004-03-29
13003 o Install torrc as torrc.sample -- we no longer clobber your
13005 o Re-enable recommendedversion checking (we broke it in rc2, oops)
13006 o Add in a 'notice' log level for things the operator should hear
13007 but that aren't warnings
13010 Changes in version 0.0.5rc2 - 2004-03-29
13011 o Hold socks connection open until reply is flushed (if possible)
13012 o Make exit nodes resolve IPs to IPs immediately, rather than asking
13013 the dns farm to do it.
13014 o Fix c99 aliasing warnings in rephist.c
13015 o Don't include server descriptors that are older than 24 hours in the
13017 o Give socks 'reject' replies their whole 15s to attempt to flush,
13018 rather than seeing the 60s timeout and assuming the flush had failed.
13019 o Clean automake droppings from the cvs repository
13022 Changes in version 0.0.5rc1 - 2004-03-28
13023 o Fix mangled-state bug in directory fetching (was causing sigpipes).
13024 o Only build circuits after we've fetched the directory: clients were
13025 using only the directory servers before they'd fetched a directory.
13026 This also means longer startup time; so it goes.
13027 o Fix an assert trigger where an OP would fail to handshake, and we'd
13028 expect it to have a nickname.
13029 o Work around a tsocks bug: do a socks reject when AP connection dies
13030 early, else tsocks goes into an infinite loop.
13033 Changes in version 0.0.4 - 2004-03-26
13034 o When connecting to a dirserver or OR and the network is down,
13038 Changes in version 0.0.3 - 2004-03-26
13039 o Warn and fail if server chose a nickname with illegal characters
13040 o Port to Solaris and Sparc:
13041 - include missing header fcntl.h
13042 - have autoconf find -lsocket -lnsl automatically
13043 - deal with hardware word alignment
13044 - make uname() work (solaris has a different return convention)
13045 - switch from using signal() to sigaction()
13046 o Preliminary work on reputation system:
13047 - Keep statistics on success/fail of connect attempts; they're published
13048 by kill -USR1 currently.
13049 - Add a RunTesting option to try to learn link state by creating test
13050 circuits, even when SocksPort is off.
13051 - Remove unused open circuits when there are too many.
13054 Changes in version 0.0.2 - 2004-03-19
13055 - Include strlcpy and strlcat for safer string ops
13056 - define INADDR_NONE so we compile (but still not run) on solaris
13059 Changes in version 0.0.2pre27 - 2004-03-14
13061 - Allow internal tor networks (we were rejecting internal IPs,
13062 now we allow them if they're set explicitly).
13063 - And fix a few endian issues.
13066 Changes in version 0.0.2pre26 - 2004-03-14
13068 - If a stream times out after 15s without a connected cell, don't
13069 try that circuit again: try a new one.
13070 - Retry streams at most 4 times. Then give up.
13071 - When a dirserver gets a descriptor from an unknown router, it
13072 logs its fingerprint (so the dirserver operator can choose to
13073 accept it even without mail from the server operator).
13074 - Inform unapproved servers when we reject their descriptors.
13075 - Make tor build on Windows again. It works as a client, who knows
13077 - Clearer instructions in the torrc for how to set up a server.
13078 - Be more efficient about reading fd's when our global token bucket
13079 (used for rate limiting) becomes empty.
13081 - Stop asserting that computers always go forward in time. It's
13083 - When we sent a cell (e.g. destroy) and then marked an OR connection
13084 expired, we might close it before finishing a flush if the other
13085 side isn't reading right then.
13086 - Don't allow dirservers to start if they haven't defined
13087 RecommendedVersions
13088 - We were caching transient dns failures. Oops.
13089 - Prevent servers from publishing an internal IP as their address.
13090 - Address a strcat vulnerability in circuit.c
13093 Changes in version 0.0.2pre25 - 2004-03-04
13095 - Put the OR's IP in its router descriptor, not its fqdn. That way
13096 we'll stop being stalled by gethostbyname for nodes with flaky dns,
13099 - If the user typed in an address that didn't resolve, the server
13103 Changes in version 0.0.2pre24 - 2004-03-03
13105 - Fix an assertion failure in dns.c, where we were trying to dequeue
13106 a pending dns resolve even if it wasn't pending
13107 - Fix a spurious socks5 warning about still trying to write after the
13108 connection is finished.
13109 - Hold certain marked_for_close connections open until they're finished
13110 flushing, rather than losing bytes by closing them too early.
13111 - Correctly report the reason for ending a stream
13112 - Remove some duplicate calls to connection_mark_for_close
13113 - Put switch_id and start_daemon earlier in the boot sequence, so it
13114 will actually try to chdir() to options.DataDirectory
13115 - Make 'make test' exit(1) if a test fails; fix some unit tests
13116 - Make tor fail when you use a config option it doesn't know about,
13117 rather than warn and continue.
13118 - Make --version work
13119 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
13122 Changes in version 0.0.2pre23 - 2004-02-29
13124 - Print a statement when the first circ is finished, so the user
13125 knows it's working.
13126 - If a relay cell is unrecognized at the end of the circuit,
13127 send back a destroy. (So attacks to mutate cells are more
13129 - New config option 'excludenodes' to avoid certain nodes for circuits.
13130 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
13131 so you can collect coredumps there.
13133 - Fix a bug in tls flushing where sometimes data got wedged and
13134 didn't flush until more data got sent. Hopefully this bug was
13135 a big factor in the random delays we were seeing.
13136 - Make 'connected' cells include the resolved IP, so the client
13137 dns cache actually gets populated.
13138 - Disallow changing from ORPort=0 to ORPort>0 on hup.
13139 - When we time-out on a stream and detach from the circuit, send an
13140 end cell down it first.
13141 - Only warn about an unknown router (in exitnodes, entrynodes,
13142 excludenodes) after we've fetched a directory.
13145 Changes in version 0.0.2pre22 - 2004-02-26
13147 - Servers publish less revealing uname information in descriptors.
13148 - More memory tracking and assertions, to crash more usefully when
13150 - If the default torrc isn't there, just use some default defaults.
13151 Plus provide an internal dirservers file if they don't have one.
13152 - When the user tries to use Tor as an http proxy, give them an http
13153 501 failure explaining that we're a socks proxy.
13154 - Dump a new router.desc on hup, to help confused people who change
13155 their exit policies and then wonder why router.desc doesn't reflect
13157 - Clean up the generic tor.sh init script that we ship with.
13159 - If the exit stream is pending on the resolve, and a destroy arrives,
13160 then the stream wasn't getting removed from the pending list. I
13161 think this was the one causing recent server crashes.
13162 - Use a more robust poll on OSX 10.3, since their poll is flaky.
13163 - When it couldn't resolve any dirservers, it was useless from then on.
13164 Now it reloads the RouterFile (or default dirservers) if it has no
13166 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
13167 many users don't even *have* a /usr/local/sbin/.
13170 Changes in version 0.0.2pre21 - 2004-02-18
13172 - There's a ChangeLog file that actually reflects the changelog.
13173 - There's a 'torify' wrapper script, with an accompanying
13174 tor-tsocks.conf, that simplifies the process of using tsocks for
13175 tor. It even has a man page.
13176 - The tor binary gets installed to sbin rather than bin now.
13177 - Retry streams where the connected cell hasn't arrived in 15 seconds
13178 - Clean up exit policy handling -- get the default out of the torrc,
13179 so we can update it without forcing each server operator to fix
13181 - Allow imaps and pop3s in default exit policy
13183 - Prevent picking middleman nodes as the last node in the circuit
13186 Changes in version 0.0.2pre20 - 2004-01-30
13188 - We now have a deb package, and it's in debian unstable. Go to
13189 it, apt-getters. :)
13190 - I've split the TotalBandwidth option into BandwidthRate (how many
13191 bytes per second you want to allow, long-term) and
13192 BandwidthBurst (how many bytes you will allow at once before the cap
13193 kicks in). This better token bucket approach lets you, say, set
13194 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
13195 performance while not exceeding your monthly bandwidth quota.
13196 - Push out a tls record's worth of data once you've got it, rather
13197 than waiting until you've read everything waiting to be read. This
13198 may improve performance by pipelining better. We'll see.
13199 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
13200 from failed circuits (if they haven't been connected yet) and attach
13202 - Expire old streams that haven't managed to connect. Some day we'll
13203 have them reattach to new circuits instead.
13206 - Fix several memory leaks that were causing servers to become bloated
13208 - Fix a few very rare assert triggers. A few more remain.
13209 - Setuid to User _before_ complaining about running as root.
13212 Changes in version 0.0.2pre19 - 2004-01-07
13214 - Fix deadlock condition in dns farm. We were telling a child to die by
13215 closing the parent's file descriptor to him. But newer children were
13216 inheriting the open file descriptor from the parent, and since they
13217 weren't closing it, the socket never closed, so the child never read
13218 eof, so he never knew to exit. Similarly, dns workers were holding
13219 open other sockets, leading to all sorts of chaos.
13220 - New cleaner daemon() code for forking and backgrounding.
13221 - If you log to a file, it now prints an entry at the top of the
13222 logfile so you know it's working.
13223 - The onionskin challenge length was 30 bytes longer than necessary.
13224 - Started to patch up the spec so it's not quite so out of date.
13227 Changes in version 0.0.2pre18 - 2004-01-02
13229 - Fix endian issues with the 'integrity' field in the relay header.
13230 - Fix a potential bug where connections in state
13231 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
13234 Changes in version 0.0.2pre17 - 2003-12-30
13236 - Made --debuglogfile (or any second log file, actually) work.
13237 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
13238 adversary could force us into an infinite loop.
13241 - Each onionskin handshake now includes a hash of the computed key,
13242 to prove the server's identity and help perfect forward secrecy.
13243 - Changed cell size from 256 to 512 bytes (working toward compatibility
13245 - Changed cell length to 2 bytes, and moved it to the relay header.
13246 - Implemented end-to-end integrity checking for the payloads of
13248 - Separated streamid from 'recognized' (otherwise circuits will get
13249 messed up when we try to have streams exit from the middle). We
13250 use the integrity-checking to confirm that a cell is addressed to
13252 - Randomize the initial circid and streamid values, so an adversary who
13253 breaks into a node can't learn how many circuits or streams have
13257 Changes in version 0.0.2pre16 - 2003-12-14
13259 - Fixed a bug that made HUP trigger an assert
13260 - Fixed a bug where a circuit that immediately failed wasn't being
13261 counted as a failed circuit in counting retries.
13264 - Now we close the circuit when we get a truncated cell: otherwise we're
13265 open to an anonymity attack where a bad node in the path truncates
13266 the circuit and then we open streams at him.
13267 - Add port ranges to exit policies
13268 - Add a conservative default exit policy
13269 - Warn if you're running tor as root
13270 - on HUP, retry OR connections and close/rebind listeners
13271 - options.EntryNodes: try these nodes first when picking the first node
13272 - options.ExitNodes: if your best choices happen to include any of
13273 your preferred exit nodes, you choose among just those preferred
13275 - options.ExcludedNodes: nodes that are never picked in path building
13278 Changes in version 0.0.2pre15 - 2003-12-03
13279 o Robustness and bugfixes:
13280 - Sometimes clients would cache incorrect DNS resolves, which would
13281 really screw things up.
13282 - An OP that goes offline would slowly leak all its sockets and stop
13284 - A wide variety of bugfixes in exit node selection, exit policy
13285 handling, and processing pending streams when a new circuit is
13287 - Pick nodes for a path only from those the directory says are up
13288 - Choose randomly from all running dirservers, not always the first one
13289 - Increase allowed http header size for directory fetch.
13290 - Stop writing to stderr (if we're daemonized it will be closed).
13291 - Enable -g always, so cores will be more useful to me.
13292 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
13295 - Wrote a man page. It lists commonly used options.
13298 - Change default loglevel to warn.
13299 - Make PidFile default to null rather than littering in your CWD.
13300 - OnionRouter config option is now obsolete. Instead it just checks
13302 - Moved to a single unified torrc file for both clients and servers.
13305 Changes in version 0.0.2pre14 - 2003-11-29
13306 o Robustness and bugfixes:
13307 - Force the admin to make the DataDirectory himself
13308 - to get ownership/permissions right
13309 - so clients no longer make a DataDirectory and then never use it
13310 - fix bug where a client who was offline for 45 minutes would never
13311 pull down a directory again
13312 - fix (or at least hide really well) the dns assert bug that was
13313 causing server crashes
13314 - warnings and improved robustness wrt clockskew for certs
13315 - use the native daemon(3) to daemonize, when available
13316 - exit if bind() fails
13317 - exit if neither socksport nor orport is defined
13318 - include our own tor_timegm (Win32 doesn't have its own)
13319 - bugfix for win32 with lots of connections
13320 - fix minor bias in PRNG
13321 - make dirserver more robust to corrupt cached directory
13324 - Wrote the design document (woo)
13326 o Circuit building and exit policies:
13327 - Circuits no longer try to use nodes that the directory has told them
13329 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
13330 bitcounts (18.0.0.0/8).
13331 - Make AP connections standby for a circuit if no suitable circuit
13332 exists, rather than failing
13333 - Circuits choose exit node based on addr/port, exit policies, and
13334 which AP connections are standing by
13335 - Bump min pathlen from 2 to 3
13336 - Relay end cells have a payload to describe why the stream ended.
13337 - If the stream failed because of exit policy, try again with a new
13339 - Clients have a dns cache to remember resolved addresses.
13340 - Notice more quickly when we have no working circuits
13343 - APPort is now called SocksPort
13344 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
13346 - RecommendedVersions is now a config variable rather than
13347 hardcoded (for dirservers)
13348 - Reloads config on HUP
13349 - Usage info on -h or --help
13350 - If you set User and Group config vars, it'll setu/gid to them.
13353 Changes in version 0.0.2pre13 - 2003-10-19
13354 o General stability:
13355 - SSL_write no longer fails when it returns WANTWRITE and the number
13356 of bytes in the buf has changed by the next SSL_write call.
13357 - Fix segfault fetching directory when network is down
13358 - Fix a variety of minor memory leaks
13359 - Dirservers reload the fingerprints file on HUP, so I don't have
13360 to take down the network when I approve a new router
13361 - Default server config file has explicit Address line to specify fqdn
13364 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
13365 - Make listener connections not ever alloc bufs
13367 o Autoconf improvements:
13368 - don't clobber an external CFLAGS in ./configure
13369 - Make install now works
13370 - create var/lib/tor on make install
13371 - autocreate a tor.sh initscript to help distribs
13372 - autocreate the torrc and sample-server-torrc with correct paths
13374 o Log files and Daemonizing now work:
13375 - If --DebugLogFile is specified, log to it at -l debug
13376 - If --LogFile is specified, use it instead of commandline
13377 - If --RunAsDaemon is set, tor forks and backgrounds on startup